I am trying to build Apache 2 with ldap support. ldap is set in my use flags and emerge -pv apache gives the following -: [ebuild R ] net-www/apache-2.0.48-r1 +berkdb +gdbm +ldap So everything looks fine. However, the /etc/apache2/extramodules/mod_ldap.so and mod_auth_ldap.so do not get built. Reproducible: Always Steps to Reproduce: 1. emerge apache 2. check if mod_ldap exists 3. Actual Results: no mod_ldap or mod_auth_ldap Expected Results: Built mod_ldap mod_auth_ldap
They most certainly do here. You'll need to attach useful output here before anybody can try to help you. Build errors? Build output? What OpenLDAP is installed? Etc.
Not getting any build errors. This is the contents of /etc/apache2/extramodules after the build -: tsunami root # ls /etc/apache2/extramodules/ -l total 3808 - -rwxr-xr-x 1 root root 3628176 Jan 18 20:50 libphp4.so - -rwxr-xr-x 1 root root 203067 Jan 18 22:12 mod_ssl.so I am using the following OpenLDAP -: [ebuild R ] net-nds/openldap-2.0.27-r4 This has also happened to a couple of other people -: http://forums.gentoo.org/viewtopic.php?t=126062&highlight=
need: 'emerge info' output config.log file "emerge apache" logfile
From apache-2.0.48-r1.ebuild @ line 121: --- local myconf use !mips && use ldap && \ myconf="--with-ldap --enable-auth-ldap=shared --enable-ldap=shared" --- After these lines the myconf variable is still empty. By putting 'myconf="--with-ldap..."' on a line of its own the parameters are sent to ./configure and the modules are built. Not a solution but maybe a useful hint :)
emerge info output -: Gentoo Base System version 1.4.3.10 Portage 2.0.49-r21 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r9, 2.6.1-rc1) ================================================================= System uname: 2.6.1-rc1 i686 Pentium II (Deschutes) distcc 2.11.1 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-mcpu=i686 -O2 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-mcpu=i686 -O2 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distcc sandbox" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j4" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="apache2 apm arts avi berkdb crypt cups encode foomaticdb gdbm gif gpm imlib jpeg kde ldap libg++ libwww mad maildir mikmod motif mpeg mys ql ncurses nls nptl oggvorbis opengl oss pam pdflib perl php php4 png python quicktime readline sdl slang spell ssh ssl svga tcpd truetype x86 xml2 xmms xv zlib" Apache build output added as attachment (apache.txt)
Created attachment 24306 [details] Apache build output Output of the emerge apache process.
Per Hakan Ahlstrom's previous comment In apache-2.0.48-r1.ebuild @ line 121: --- local myconf use !mips && use ldap && \ myconf="--with-ldap --enable-auth-ldap=shared --enable-ldap=shared" --- If taking out 'use !mips', myconf will get the correct value. Seems 'use !mips' should be true though. I am new to ebuild. Any advice on why it is not?
If 'use !mips' is the problem, what is the justification for it being there? enti boot # grep mips /usr/portage/net-nds/openldap/openldap-2.* enti boot # this shows that the openldap ebuild doesnt have any problems with mips. a search on gentoo for 'apache enable-auth-ldap mips' returns only gentoo ebuilds and this article: http://groups.yahoo.com/group/new-httpd/message/42840 is this the basis for the !mips code? i realize there prolly aren't lots of people trying to build apache2 with ldap support on mips, but only one person having problems? "Why did you build and install apr and apr-util rather than using the ones bundled with Apache? I'm not sure that version 0.9.1 had the APU_BINDIR variable (I'd have to check... Justin would probably know). We're not at the point yet where we have declared a particular version number of apr and apr-util to work with Apache 2.0.44 (or any other 2.0.x release) other than the one bundled with it. --Cliff" i feel the !mips should be removed. this failure to build without any notification to the user seems poor. for now i will remove the !mips from my own, but i feel this should be remedied in some manner.
yes it belongs there because guess what, ldap support doesnt work on mips however, the bug here is with apache ... proper syntax is `! use mips` ... negated use flag request is Bug 30360
The "use !mips" is only a problem because it that syntax was added in a newer version of portage that is ~x86 only at the moment. I've modified the logic now to work with older versions of portage.
so i take it i need to be running portage-2.0.50_pre9 for this to work properly?
forget that last comment.