I got an access violation emerging dev-perl/mod_perl-1.99.11 . Here is the process I went through, with a possible solution. Thanks to rac for following me through the mud on this one. emerge info is below. 1) ACCEPT_KEYWORDS="~x86" emerge mod_php , got an access violation: make[3]: Leaving directory `/var/tmp/portage/mod_perl-1.99.11/work/mod_perl-1.99_11/xs/ModPerl/Const' make[2]: Leaving directory `/var/tmp/portage/mod_perl-1.99.11/work/mod_perl-1.99_11/xs/ModPerl' make[1]: Leaving directory `/var/tmp/portage/mod_perl-1.99.11/work/mod_perl-1.99_11/xs' /usr/bin/perl -MExtUtils::Install -e \ "-e qq{.mypacklist} && uninstall(qq{.mypacklist}, 1, 0)" unlink /usr/lib/perl5/vendor_perl/5.8.0/i686-linux/Apache/test.pm ACCESS DENIED chmod: /usr/lib/perl5/vendor_perl/5.8.0/i686-linux/Apache/test.pm ACCESS DENIED unlink: /usr/lib/perl5/vendor_perl/5.8.0/i686-linux/Apache/test.pm Cannot forceunlink /usr/lib/perl5/vendor_perl/5.8.0/i686-linux/Apache/test.pm: Permission denied at -e line 1 make: *** [nuke_Apache__test] Error 255 !!! ERROR: dev-perl/mod_perl-1.99.11 failed. !!! Function src_install, Line 104, Exitcode 2 !!! (no error message) --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-mod_perl-1.99.11-15910.log" chmod: /usr/lib/perl5/vendor_perl/5.8.0/i686-linux/Apache/test.pm unlink: /usr/lib/perl5/vendor_perl/5.8.0/i686-linux/Apache/test.pm -------------------------------------------------------------------------------- The specified log file contains this: chmod: /usr/lib/perl5/vendor_perl/5.8.0/i686-linux/Apache/test.pm unlink: /usr/lib/perl5/vendor_perl/5.8.0/i686-linux/Apache/test.pm 2) Commented out make test as per rac, got a similar error. 3) Moved test.pm to test.pm.kludge as per rac. This worked. rac suspected a conflict with an earlier version of mod_perl . Indeed, I had 1.27-r4 . What I find odd is that I have two systems. One is ~x86 , the other is not. I emerged the same version of mod_perl on the ~x86 system around a week ago, no problems. The machine these tests were done on was not an ~x86 machine, in fact I was pulling ACCEPT_KEYWORDS="~x86" just to get mod_perl-1.99.11 . On the other machine, that is the ~x86 machine, I had not installed any version of mod_perl earlier than 1.99.11. And that is when I did not have these access violations. So perhaps rac is correct about earlier versions causing problems with 1.99.11. ///////////////////////////////////////////////// emerge info from the first machine, the one where I had access violations: Portage 2.0.49-r20 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r3, 2.6.1) ================================================================= System uname: 2.6.1 i686 Pentium III (Katmai) Gentoo Base System version 1.4.3.10 distcc 2.11.1 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.3 [enabled] ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-mcpu=pentium3 -O2 -pipe -fomit-frame-pointer -mmmx -msse -mfpmath=sse,387" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-mcpu=pentium3 -O2 -pipe -fomit-frame-pointer -mmmx -msse -mfpmath=sse,387" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs buildpkg ccache distcc sandbox" GENTOO_MIRRORS="ftp://gentoo.noved.org/ http://gentoo.noved.org/" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="X apache2 apm arts avi berkdb crypt encode foomaticdb gdbm gif gnome gpm gtk gtk2 imlib jpeg kde kerberos ldap libg++ libwww mad mikmod mmx motif mpeg mysql ncurses oggvorbis pam pdflib perl png python qt quicktime readline sdl slang snmp spell ssl tcpd tiff truetype x86 xml2 xv zlib" emerge info from the second system, that is, the ~x86 system where I did not have access violations, and did not have an earlier version of mod_perl installed: Portage 2.0.49-r18 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1, 2.6.1) ================================================================= System uname: 2.6.1 i686 Pentium III (Katmai) Gentoo Base System version 1.4.3.8p1 distcc 2.12 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.3 [enabled] ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-mcpu=pentium3 -O2 -pipe -fomit-frame-pointer -mmmx -msse -mfpmath=sse,387" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-mcpu=pentium3 -O2 -pipe -fomit-frame-pointer -mmmx -msse -mfpmath=sse,387" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs buildpkg ccache distcc notitles sandbox userpriv" GENTOO_MIRRORS="ftp://gentoo.noved.org/ http://gentoo.noved.org/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="X apache2 apm avi berkdb cdr crypt cups encode esd foomaticdb gdbm gif gnome gpm gtk gtk2 imlib jpeg kde kerberos ldap libg++ libwww mad mikmod mmx motif mpeg mysql ncurses nls oggvorbis opengl oss pam pdflib perl png python qt quicktime readline sdl slang snmp spell sse ssl svga tcpd tiff truetype x86 xml2 xmms xv zlib"
Double check that an old version of mod_perl didn't sneak past you. I ran into this exact problem too, searched in /var/db/pkg and found an old mod_perl installed. Unmerged the old one and 1.99.11 installed without incident.
Thanks for the advice. It's been quite a while since i was dealing with this, it was mainly beause rac asked me to enter in for future search fodder.
Any word on this, or if it's even relevant anymore?
I haven't been able to reproduce this recently, will check again though. :)
I ran into this today. I unmerged mod_perl-1.27-r4 and then mod_perl-1.99.11 emerged ok.
mod_perl-2.0.1 is in the tree and I haven't seen this come up. Can you confirm?
I no longer have a system I can test this on, sorry. Thanks for the reply.
no prob, will go ahead and close this out since it hasn't cropped up in the 2.X series. Sorry for the delay in posting, been catching up on the backlog of perl bugs lately.
I tried to install 2.0.1-r1 today and got this same error message.
Do you have an old copy of Apache-Test (not that the block should have let you) or mod_perl-1.9X installed still? If so, would you mind removing them and trying 2.0.1 again?
*I think* as a temporary fix to get the module installed anyhow: just in the install.pl of Apache::Test module, comment the lines which write nuke_apache__test target. may be something like this ? install.pl contents: nuke_Apache__test: return <<EOF; nuke_Apache__test: #\t\$(FULLPERL) -MExtUtils::Install -e \\ #\t"-e qq{$cleanup_packlist} && uninstall(qq{$cleanup_packlist}, 1, 0)" EOF } Please let me know if it works at mnikhil@gmail.com BTW, is this ticket resolved ? Note to Site Administrators, please put the site onto https and not http :) Regards.
