I tried to emerge AxKit on a freshly installed Gentoo system, but mod_perl doesn't compile. It gives to following error: gcc -fpic -O3 -march=pentium3 -funroll-loops -fprefetch-loop-arrays -pipe -I/usr/lib/perl5/5.8.0/i686-linux/CORE -DPERL5 -fno-strict-aliasing -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DMOD_PERL_VERSION=\"1.27\" -DMOD_PERL_STRING_VERSION=\"mod_perl/1.27\" -I/usr/include/apache -DMOD_PERL -O3 -march=pentium3 -funroll-loops -fprefetch-loop-arrays -pipe -DHARD_SERVER_LIMIT=512 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX=22 -DTARGET=\"apache\" -I/usr/include/db4 -DDEV_RANDOM=/dev/random -DUSE_HSREGEX -DEAPI -DEAPI_MM -O3 -march=pentium3 -funroll-loops -fprefetch-loop-arrays -pipe -c Connection.c && mv Connection.o Connection.lo Connection.c: In function `XS_Apache__Connection_remote_addr': Connection.c:124: incompatible types in assignment make[1]: *** [Connection.lo] Error 1 make[1]: *** Waiting for unfinished jobs.... make[1]: Entering directory `/var/tmp/portage/mod_perl-1.27-r4/work/mod_perl-1.27/Apache' cp Apache.pm ../blib/lib/Apache.pm Manifying ../blib/man3/Apache.3pm make[1]: Leaving directory `/var/tmp/portage/mod_perl-1.27-r4/work/mod_perl-1.27/apaci' make: *** [apxs_libperl] Error 2 make: *** Waiting for unfinished jobs.... make[1]: Leaving directory `/var/tmp/portage/mod_perl-1.27-r4/work/mod_perl-1.27/Apache' !!! ERROR: dev-perl/mod_perl-1.27-r4 failed. !!! Function src_compile, Line 48, Exitcode 2 !!! (no error message) Reproducible: Always Steps to Reproduce: 1. Install a fresh Gentoo 1.4 2. emerge AxKit
The IPv6 patch is the trouble maker. Compiling with USE="-ipv6" works fine.
Same error for me. mod_perl-1.99.10 has no problems. # emerge info Portage 2.0.49-r15 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1, 2.4.22) ================================================================= System uname: 2.4.22 i686 AMD Athlon(TM) XP 2000+ Gentoo Base System version 1.4.3.10p1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -pipe -march=athlon-xp -fforce-addr -fomit-frame-pointer -falign-functions=4 -mfpmath=sse" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O3 -pipe -march=athlon-xp -fforce-addr -fomit-frame-pointer -falign-functions=4 -mfpmath=sse" DISTDIR="/usr/portage/distfiles" FEATURES="sandbox ccache autoaddcvs" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="x86 oss apm avi crypt encode foomaticdb jpeg libg++ mad mikmod mpeg ncurses nls pdflib png quicktime spell truetype xmms xv zlib gdbm berkdb slang readline arts tetex bonobo svga X sdl gpm tcpd pam libwww ssl perl python esd imlib oggvorbis gnome gtk qt kde motif opengl gphoto2 3dnow aalib apache2 cdr cscope cups curl directfb dga doc dvb faad fbcon flash gd ggi gif gtk2 guile jikes kerberos imap lcms ldap mcal memlimit mmx mozaccess mozilla moznoirc mozp3p mozsvg mpi mysql odbc offensive parse-clocks ppds prelude samba scanner skey slp snmp socks5 sse tcltk tiff v4l vim-with-x wmf wxwindows X509 xchattext xml xml2 xvid"
I've been seeing the same problem with mod_perl since 1.27-r2 - nothing after r1 will build for me. Excluding the IPv6 patch with USE="-ipv6" is a workaround, but not a fix. Any movement on resolving this bug?
*** Bug 56281 has been marked as a duplicate of this bug. ***
Just bumped into this while building a server. Anyone looked at it by chance?
I ran across this problem too, and here's what I think it is. We are trying to build an IPV6 enabled mod_perl-1.x.x against a non-IPV6 enabled Apache. Just turn off IPV6!!! You don't really need an IPV6 enabled mod_perl against a non-IPV6 Apache, do you? Incidentally, you can get mod_perl to build anyway by a couple of lines modified in the modperl-ipv6 patch (I did this before realizing the *reason* why the patch failed... the Apache headers weren't using IPV6 friendly semantics (sockaddr_storage instead of sockaddr_in, etc.) because Apache wasn't patched for IPV6... doh! If someone really wants to do this anyway, I'll post the patch, it's fairly trivial. But what could we possibly gain from this, given the above? Probably better just to turn the IPV6 use-flag off for this until an IPV6 patched Apache-1 hits portage. Apache patches anyone? Comments?
Part of the problem is that nobody has selected USE=ipv6, it was thrust upon us in some past upgrade of portage. Check out bugzilla, this upgrade broke other packages. If we explicitly disable ipv6 in our USE flags, then --newuse will rebuild the 20 or so packages that have been built since ipv6 was introduced as a default flag. Checking out the ChangeLogs for mod_perl and apache show that ipv6 was added to mod_perl 1 at release mod_perl-1.27-r2 on 01 Mar 2003, but it was removed from apache 1 at release apache-1.3.27-r34 on 26 Mar 2003. So the packages have been out of sync with each other since 26 Mar 2003. Perhaps the simplest solution is to turn off ipv6 inside the stable ebuild for mod_perl 1 and wait for mod_perl 2 to be released.
The IPv6 patches have been dropped and mod_perl-1.2* now compiles and cleanly.
