Bug 130078 – Apache emerge error

• Product: Gentoo Linux
• Status: RESOLVED TEST-REQUEST

[Description David Corbin 2006-04-15 10:15:30 UTC]

While I attempt to emerge apache, I get this:

------ console ------
checking for times... (cached) yes
checking which MPM to use...
configure: error: the selected mpm --  -- is not supported

!!! ERROR: net-www/apache-2.0.55-r1 failed.
!!! Function src_compile, Line 161, Exitcode 1
----end cut---

I've tried this with mpm-worker, mpm-prefork, no mpm explictly specified.

----emerge --info---------
Portage 2.0.54 (default-linux/x86/2005.0, gcc-3.3.6, glibc-2.3.5-r3, 2.6.7 i686)
=================================================================
System uname: 2.6.7 i686 AMD Athlon(tm) XP 1700+
Gentoo Base System version 1.6.14
dev-lang/python:     2.3.5, 2.4.2
sys-apps/sandbox:    1.2.12
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.4.3-r4, 1.5.22
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i386-pc-linux-gnu"
CFLAGS="-O2 -mcpu=i686 -fomit-frame-pointer"
CHOST="i386-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/eselect/compiler /etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -mcpu=i686 -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict"
GENTOO_MIRRORS="ftp:///ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://mirror.datapipe.net/gentoo ftp://mirrors.sec.informatik.tu-darmstadt.de/gentoo/ http://ftp.du.se/pub/os/gentoo"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 X acl alsa apache2 apm arts audiofile avi berkdb bitmap-fonts bzip2 cgi courier crypt cups dri eds emboss encode exim expat fastcgi foomaticdb fortran gd gdbm gif glut gmp gnome gpm gstreamer gtk gtk2 imlib ipv6 isdnlog jpeg kde lcms libg++ libwww mad mhash mikmod mng motif mp3 mpeg mpm-worker mysql ncurses nls ogg oggvorbis opengl oss pam pcre pdflib perl php png pppd python qt quicktime readline ruby sdl slang spell ssl tcltk tcpd tiff truetype truetype-fonts type1-fonts vorbis xml2 xmms xv zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS, PORTDIR_OVERLAY

[Comment 1 Michael Stewart (vericgar) (RETIRED) 2006-04-15 11:07:51 UTC]

Please attach your config.layout and config.log - they should be in /var/tmp/portage/apache-2.0.55-r1/work/httpd-2.0.55

[Comment 2 David Corbin 2006-04-15 12:41:34 UTC]

Created attachment 84732 [details]
config.log

[Comment 3 David Corbin 2006-04-15 12:41:53 UTC]

Created attachment 84733 [details]
config.layout

[Comment 4 Michael Stewart (vericgar) (RETIRED) 2006-04-16 12:20:15 UTC]

With no mpm-* USE-flag set, do you see either of these messages when you try emerging:

einfo "No MPM style was specified, defaulting to mpm-prefork."

einfo "Threads specified without a mpm-specification, using mpm-worker."

[Comment 5 David Corbin 2006-04-16 13:24:38 UTC]

Yes, I get this message: "No MPM style was specified, defaulting to mpm-prefork."

[Comment 6 Michael Stewart (vericgar) (RETIRED) 2006-04-16 14:02:55 UTC]

what version of bash are you running?

bash --version

[Comment 7 David Corbin 2006-04-16 14:40:25 UTC]

GNU bash, version 3.1.16(1)-release (i386-pc-linux-gnu)
Copyright (C) 2005 Free Software Foundation, Inc.


(I think I'm up to date for 'stable' gentoo)...

[Comment 8 David Corbin 2006-05-04 04:56:12 UTC]

Hardly an expert, but after hacking at it a bit, it appears that the mpm environment variable is being set in 'setup', but when compile is invoked, it's been "cleared", or lost.  I added 'select_mpms' right before the configure and things seemed to do much better.

[Comment 9 Michael Stewart (vericgar) (RETIRED) 2006-05-15 19:54:35 UTC]

I have hopefully fixed this with apache 2.0.58 (as I couldn't reproduce it, I can't test it). Please see if this version resolves the issue for you.