Jump to content
Read the Funtoo Newsletter: Summer 2023 ×
  • 0

tengine passenger fails to build

uudruid74

Asked by uudruid74,

 Share

Question

uudruid74 Rookie

uudruid74

Posted
Posted

OK, I'm new to tengine and passenger and just kinda blindly following the How-To's at this point.  I don't know if I really need passenger yet, but I'm thinking something is going to need it eventually.  Here's where I'm at (and I tried to set Ruby to 19 via eselect, didn't help):

>>>  '/var/tmp/portage/www-servers/tengine-2.1.0-r1/temp/build.log'

 * Messages for package www-servers/tengine-2.1.0-r1:

 * tengine group already exist.
 * group creation step skipped.
 * tengine user already exist.
 * user creation step skipped.
 * ERROR: www-servers/tengine-2.1.0-r1 failed (prepare phase):
 *   Passenger premake for /usr/bin/ruby19 failed!
 *
 * Call stack:
 *     ebuild.sh, line   93:  Called src_prepare
 *   environment, line 5730:  Called _ruby_each_implementation 'passenger_premake'
 *   environment, line  581:  Called _ruby_invoke_environment 'ruby19' 'passenger_premake'
 *   environment, line  676:  Called passenger_premake
 *   environment, line 4594:  Called die
 * The specific snippet of code:
 *       rake -m nginx || die "Passenger premake for ${RUBY} failed!"
 *
 * If you need support, post the output of `emerge --info '=www-servers/tengine-2.1.0-r1'`,
 * the complete build log and the output of `emerge -pqv '=www-servers/tengine-2.1.0-r1'`.
 * The complete build log is located at '/var/tmp/portage/www-servers/tengine-2.1.0-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/www-servers/tengine-2.1.0-r1/temp/environment'.
 * Working directory: '/var/tmp/portage/www-servers/tengine-2.1.0-r1/work/ruby19/tengine-2.1.0/passenger-release-5.0.6'
 * S: '/var/tmp/portage/www-servers/tengine-2.1.0-r1/work/ruby19/tengine-2.1.0'

Should I post the contents of any files?

 

Link to comment
Share on other sites

9 answers to this question

Recommended Posts

  • 0
uudruid74 Rookie

uudruid74

Posted
  • Author
Posted

I think I see what is happening.  The HOW-TO mentions to specify it to be external, like this:

TENGINE_EXTERNAL_MODULES_HTTP="passenger"

and I just realized that external could mean that the build is external to tengine, so I have to build it separately.  Sure enough, passenger has a separate ebuild, which wants to pull in apache!   But, it tried to build passenger when I emerged tengine, so I'll assume that was correct and the passenger ebuild is just for apache.

 

Well ... it finished successfully!   How odd.  I could have sworn I tried ruby22.  And BTW, 'eselect' is likely the preferred way to manage your Ruby version rather than a manual symlink.  It lets you switch back and forth.  Anyway, thanks for the help!

Link to comment
Share on other sites
  • 0
uudruid74 Rookie

uudruid74

Posted
  • Author
Posted

NO, wait!  WTF am I smoking?  I must have been looking at the wrong screen or soemthing.  I see a failure message.   And it looks like its complaining about ruby21 now.   And I try it again and it complains about ruby19!!   What is IT smoking?

navi ~ # ls -l /usr/bin/ruby
lrwxrwxrwx 1 root root 6 Jun 29 19:30 /usr/bin/ruby -> ruby22
navi ~ #  ls -l /usr/bin/gem
lrwxrwxrwx 1 root root 5 Jun 29 19:30 /usr/bin/gem -> gem22

Emerge:

>>> Failed to emerge www-servers/tengine-2.1.0-r1, Log file:

>>>  '/var/tmp/portage/www-servers/tengine-2.1.0-r1/temp/build.log'

 * Messages for package www-servers/tengine-2.1.0-r1:

 * tengine group already exist.
 * group creation step skipped.
 * tengine user already exist.
 * user creation step skipped.
 * ERROR: www-servers/tengine-2.1.0-r1 failed (prepare phase):
 *   Passenger premake for /usr/bin/ruby19 failed!
 *
 * Call stack:
 *     ebuild.sh, line   93:  Called src_prepare
 *   environment, line 5724:  Called _ruby_each_implementation 'passenger_premake'
 *   environment, line  581:  Called _ruby_invoke_environment 'ruby19' 'passenger_premake'
 *   environment, line  676:  Called passenger_premake
 *   environment, line 4588:  Called die
 * The specific snippet of code:
 *       rake -m nginx || die "Passenger premake for ${RUBY} failed!"
 *
 * If you need support, post the output of `emerge --info '=www-servers/tengine-2.1.0-r1'`,
 * the complete build log and the output of `emerge -pqv '=www-servers/tengine-2.1.0-r1'`.
 * The complete build log is located at '/var/tmp/portage/www-servers/tengine-2.1.0-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/www-servers/tengine-2.1.0-r1/temp/environment'.
 * Working directory: '/var/tmp/portage/www-servers/tengine-2.1.0-r1/work/ruby19/tengine-2.1.0/passenger-release-5.0.6'
 * S: '/var/tmp/portage/www-servers/tengine-2.1.0-r1/work/ruby19/tengine-2.1.0'

I am not permitted to upload this type of file (build.log).  So here's a paste

 

http://paste.ubuntu.com/11796523/

 

Why is the spellchecker underlining EVERYTHING?

 

 

Link to comment
Share on other sites
  • 0
666threesixes666 Newbie

666threesixes666

Posted
Posted

yeah, its not the ebuild passenger....  its a use flag that pulls in tengine specific passenger.

 

"Your compiler failed with the exit status 4. This probably means that it ran out of memory."

 

i was having problems with this message until i updated world.....

 

so add that line to make.conf if you haven't already, update world, then try emerge -av tengine again =)

Link to comment
Share on other sites
  • 0
uudruid74 Rookie

uudruid74

Posted
  • Author
Posted

yeah, its not the ebuild passenger....  its a use flag that pulls in tengine specific passenger.

 

"Your compiler failed with the exit status 4. This probably means that it ran out of memory."

 

i was having problems with this message until i updated world.....

 

so add that line to make.conf if you haven't already, update world, then try emerge -av tengine again =)

 

 

Ugh ... 4 GB isn't enough ??  World fails when it hits tengine again.   Trying to do @preserved-rebuild, but I don't see anything that would help a memory problem.  I guess I'll have to turn on swap to a file.  I don't have X or anything running that would eat up RAM. 

 

@preserved-rebuild fails building courier-imap.   Adding swap is not an option.

Link to comment
Share on other sites
  • 0
uudruid74 Rookie

uudruid74

Posted
  • Author
Posted

Let's go again, this time its trying to rebuild stuff that's supposed to work.   It all worked fine before! And courier-unicode is installed at the latest version.   I'm doing an -auDNv courier-imap to upgrade depends before @preserved-rebuild since world failed.

 

First line appears to be an ebuild bug??

configure: error: The Courier Unicode Library appears not to be installed. You may need to install a separate development subpackage, in addition to the main package

!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/net-mail/courier-imap-4.16.0/work/courier-imap-4.16.0/config.log
 * ERROR: net-mail/courier-imap-4.16.0 failed (configure phase):
 *   econf failed
 *
 * Call stack:
 *          ebuild.sh, line   93:  Called src_configure
 *        environment, line 2685:  Called econf '--disable-root-check' '--bindir=/usr/sbin' '--sysconfdir=/etc/courier-imap' '--libexecdir=/usr/lib64/courier-imap' '--localstatedir=/var/lib/courier-imap' '--with-authdaemonvar=/var/lib/courier-imap/authdaemon' '--enable-workarounds-for-imap-client-bugs' '--with-mailuser=mail' '--with-mailgroup=mail' '--with-fam' '--with-ipv6' '--without-gnutls' '--with-db=gdbm'
 *   phase-helpers.sh, line  526:  Called die
 * The specific snippet of code:
 *                      die "econf failed"
 *
 * If you need support, post the output of `emerge --info '=net-mail/courier-imap-4.16.0'`,
 * the complete build log and the output of `emerge -pqv '=net-mail/courier-imap-4.16.0'`.
 * The complete build log is located at '/var/tmp/portage/net-mail/courier-imap-4.16.0/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/net-mail/courier-imap-4.16.0/temp/environment'.
 * Working directory: '/var/tmp/portage/net-mail/courier-imap-4.16.0/work/courier-imap-4.16.0'
 * S: '/var/tmp/portage/net-mail/courier-imap-4.16.0/work/courier-imap-4.16.0'

>>> Failed to emerge net-mail/courier-imap-4.16.0, Log file:

>>>  '/var/tmp/portage/net-mail/courier-imap-4.16.0/temp/build.log'

 * Messages for package net-mail/courier-imap-4.16.0:

 * ERROR: net-mail/courier-imap-4.16.0 failed (configure phase):
 *   econf failed
 *
 * Call stack:
 *          ebuild.sh, line   93:  Called src_configure
 *        environment, line 2685:  Called econf '--disable-root-check' '--bindir=/usr/sbin' '--sysconfdir=/etc/courier-imap' '--libexecdir=/usr/lib64/courier-imap' '--localstatedir=/var/lib/courier-imap' '--with-authdaemonvar=/var/lib/courier-imap/authdaemon' '--enable-workarounds-for-imap-client-bugs' '--with-mailuser=mail' '--with-mailgroup=mail' '--with-fam' '--with-ipv6' '--without-gnutls' '--with-db=gdbm'
 *   phase-helpers.sh, line  526:  Called die
 * The specific snippet of code:
 *                      die "econf failed"
 *
 * If you need support, post the output of `emerge --info '=net-mail/courier-imap-4.16.0'`,
 * the complete build log and the output of `emerge -pqv '=net-mail/courier-imap-4.16.0'`.
 * The complete build log is located at '/var/tmp/portage/net-mail/courier-imap-4.16.0/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/net-mail/courier-imap-4.16.0/temp/environment'.
 * Working directory: '/var/tmp/portage/net-mail/courier-imap-4.16.0/work/courier-imap-4.16.0'
 * S: '/var/tmp/portage/net-mail/courier-imap-4.16.0/work/courier-imap-4.16.0'

Trying emerge @system to see what happens.  Something is borked somewhere.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to question listing
×
×
  • Create New...