In my make.conf : ACCEPT_KEYWORDS="~x86" Trying to emerge AxKit, I get this : cd "src/modules/perl" && make -f Makefile.modperl install make[1]: Entering directory `/var/tmp/portage/mod_perl-1.99.07/work/mod_perl-1.99_07/src/modules/perl' test -f mod_perl.so && \ cp mod_perl.so /var/tmp/portage/mod_perl-1.99.07/image//usr/lib/apache2-extramodules make[1]: Leaving directory `/var/tmp/portage/mod_perl-1.99.07/work/mod_perl-1.99_07/src/modules/perl' make: *** Pas de r
In my make.conf : ACCEPT_KEYWORDS="~x86" Trying to emerge AxKit, I get this : cd "src/modules/perl" && make -f Makefile.modperl install make[1]: Entering directory `/var/tmp/portage/mod_perl-1.99.07/work/mod_perl-1.99_07/src/modules/perl' test -f mod_perl.so && \ cp mod_perl.so /var/tmp/portage/mod_perl-1.99.07/image//usr/lib/apache2-extramodules make[1]: Leaving directory `/var/tmp/portage/mod_perl-1.99.07/work/mod_perl-1.99_07/src/modules/perl' make: *** Pas de règle pour fabriquer la cible « pure_vendor_install », nécessaire pour « pure_install ». Arrêt. !!! ERROR: dev-perl/mod_perl-1.99.07 failed. !!! Function src_install, Line 38, Exitcode 2 !!! (no error message)
I can just confirm same thing trying to install mod_perl with apache-2.0.43r1 gives error: make[1]: Entering directory `/var/tmp/portage/mod_perl-1.99.07/work/mod_perl-1.99_07/src/modules/perl' test -f mod_perl.so && \ cp mod_perl.so /var/tmp/portage/mod_perl-1.99.07/image//usr/lib/apache2-extramodules make[1]: Leaving directory `/var/tmp/portage/mod_perl-1.99.07/work/mod_perl-1.99_07/src/modules/perl' make: *** No rule to make target `pure_vendor_install', needed by `pure_install'. Stop. !!! ERROR: dev-perl/mod_perl-1.99.07 failed. !!! Function src_install, Line 38, Exitcode 2 !!! (no error message)
mcummings: any idea what that's about? im afraid i dont think there is anything to "fix" in the mod_perl ebuild. it works just fine here. looks like a sneaky perl issue or other.
Have a look at this threed: http://forums.gentoo.org/viewtopic.php?t=25049 it trow some lights on it I think, it's just over my head to do something with it... The end of this threed may as well be helpful: http://forums.gentoo.org/viewtopic.php?t=24957 Notting to fix? Are you looking at the right ebuild? There must be "something" missing (some kind of rule as I understand) otherwise it would have compiled.
moonwalker@astro.nu: yes, im sure im looking at the right ebuild. no, im not sure what the fix is, which is why i've asked mcummings to take a peek. as ive already said, it builds/installs just fine here. but you probably dont have the same version of perl on your system as i do. an another note, it might be good to have mod_perl-2 in its own SLOT.. if that is possible. mcummings will have to verify because perl is not exactly my cup of tea.
OK, I've tested mod_perl on apache2 with the following conditions: mod_perl-1.99, on a "clean" (no mod_perl) system - installs fine mod_perl-1.27 on a "clean" system - installs fine mod_perl 1.99 on a system containing mod_perl-1.27 - installs fine. I think we can say that this issue isn't mod_perl specific (the errors you are getting refer to some env var's for perl in general). My first suggestion would be, for sanity's sake, to do the following: emerge sync emerge ExtUtils-MakeMaker then if you are game, try emerging mod_perl. The ExtUtils-MakeMaker install should already be on your systems (this is a part of both the profiles and perl- modules eclass, so you can't avoid it too easily anymore, though it can be skirted accidently). A relevant question is how old is your perl install (which -r do you have and which version of perl (5.6.1, 5.8) are you running) vs. how old your systems are. Did you upgrade perl recently, but the box has been around for 6+ months? Please try the above and report back here. I suspect this will get you covered, but it will at least eliminate some factors. Thanks, Mike
Gentoo Base System version 1.4.2.5 This is perl, v5.6.1 built for i686-linux emerge ExtUtils-MakeMaker emerge mod_perl And it compiled and installed ok. So I close it since it seems to not be a real bug. Thanks for looking at it. Sorry for the burden. And if should not have closed it, blame me :)
OK, there is still a problem with this ebuild I'm afraid. It's installing into @INC *almost* correctly, but it is placing it into an Apache2 subdir that isn't handled by perl. Will start work on this shortly, sorry Ludovic
The current problem is actually with the perl ebuild. I've rewritten the ebuild to include the vendor paths - this is what mod_perl 2 is looking for when it installs into @INC, and if not present it mis-installs. Terribly sorry for this, There are two ways to fix this, the first the easiest overall. emerge sync emerge perl emerge ExtUtils-MakeMaker emerge mod_perl the revamped -r8 (if you see -r9, very sorry, that was a mistake on my part) includes the vendor paths. The second way would be to create the vendor dirs, then edit the Config.pm for perl to point to them. I can walk you through that too if you would like, but it's slightly messy. Michael
Updating makefile... make[1]: Leaving directory `/var/tmp/portage/perl-5.8.0-r3/work/perl-5.8.0/x2p' Now you must run 'make'. If you compile perl5 on a different machine or from a different object directory, copy the Policy.sh file from this object directory to the new one before you run Configure -- this will help you with most of the policy defaults. make: *** Pas de r
Updating makefile... make[1]: Leaving directory `/var/tmp/portage/perl-5.8.0-r3/work/perl-5.8.0/x2p' Now you must run 'make'. If you compile perl5 on a different machine or from a different object directory, copy the Policy.sh file from this object directory to the new one before you run Configure -- this will help you with most of the policy defaults. make: *** Pas de règle pour fabriquer la cible « <interne> », nécessaire pour « miniperlmain.o ». Arrêt. !!! ERROR: sys-devel/perl-5.8.0-r3 failed. !!! Function src_compile, Line 109, Exitcode 2 !!! Unable toe make Gods aren't with me this week :(
this has been fixed - there was an issue with emake in the ebuild, resolved with a make
To actually get the fixed ebuild (perl-5.6.1-r8) you have to edit /usr/portage/profiles/package.mask as it's still are masked. Then next step are of course to see how well this plays with perl-5.8.0? Maybe a good idea to take a look at it already now, so we don't have to go all over this again :-)
hold that thought! sync again. it's unmasked now, not to mention a one line change in the 5.6.1-r8 ebuild. You would still need to re-emerge ExtUtils- MakeMaker until -r9 comes out with the next version of portage. 5.8 will be available again shortly, working through some postconfig items
Well not sure if I sync'ed before or after your message, but as 5.6.1-r8 gave some mystic dependency problems (maybe becouse of my ACCEPTED_KEYWORDS) I emerged 5.8.0-r3 and then mod_perl-1.99 compiled just fine.
#emerge sync fine ;p #emerge perl fine #emerge ExtUtils-MakeMaker fine #emerge mod_perl fine (perl-5.8.0-r3) #emerge Axkit failed Calculating dependencies ...done! >>> emerge (1 of 2) dev-perl/libapreq-1.0-r2 to / >>> md5 ;-) libapreq-1.0.tar.gz >>> Unpacking source... >>> Unpacking libapreq-1.0.tar.gz >>> Source unpacked. Can't locate mod_perl.pm in @INC (@INC contains: /usr/lib/perl5/5.8.0/i686-linux /usr/lib/perl5/5.8.0 /usr/lib/perl5/site_perl/5.8.0/i686-linux /usr/lib/perl5/site_perl/5.8.0 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.0/i686-linux /usr/lib/perl5/vendor_perl/5.8.0 /usr/lib/perl5/vendor_perl .) at Makefile.PL line 12. BEGIN failed--compilation aborted at Makefile.PL line 12. make: *** Pas de cibles sp
#emerge sync fine ;p #emerge perl fine #emerge ExtUtils-MakeMaker fine #emerge mod_perl fine (perl-5.8.0-r3) #emerge Axkit failed Calculating dependencies ...done! >>> emerge (1 of 2) dev-perl/libapreq-1.0-r2 to / >>> md5 ;-) libapreq-1.0.tar.gz >>> Unpacking source... >>> Unpacking libapreq-1.0.tar.gz >>> Source unpacked. Can't locate mod_perl.pm in @INC (@INC contains: /usr/lib/perl5/5.8.0/i686-linux /usr/lib/perl5/5.8.0 /usr/lib/perl5/site_perl/5.8.0/i686-linux /usr/lib/perl5/site_perl/5.8.0 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.0/i686-linux /usr/lib/perl5/vendor_perl/5.8.0 /usr/lib/perl5/vendor_perl .) at Makefile.PL line 12. BEGIN failed--compilation aborted at Makefile.PL line 12. make: *** Pas de cibles spécifiées et aucun makefile n'a été trouvé. Arrêt. !!! ERROR: dev-perl/libapreq-1.0-r2 failed. !!! Function perl-module_src_compile, Line 32, Exitcode 2 !!! compilation failed Characteristics of this binary (from libperl): Compile-time options: USE_LARGE_FILES Built under linux Compiled at Dec 12 2002 18:53:49 @INC: /usr/lib/perl5/5.8.0/i686-linux /usr/lib/perl5/5.8.0 /usr/lib/perl5/site_perl/5.8.0/i686-linux /usr/lib/perl5/site_perl/5.8.0 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.0/i686-linux /usr/lib/perl5/vendor_perl/5.8.0 /usr/lib/perl5/vendor_perl . Should I try with perl-5.6.1-r8 rather ?
Your version of perl shouldn't be affected in this case. Hmmm...can you see where the mod_perl was installed? It should be listed in /var/db/pkg/dev- perl/mod_perl*/CONTENTS
Created attachment 6465 [details] mod perl CONTENTS file
We're barking up the wrong tree. The AxKit ebuild is hardcoded for a non- slotted apache. OK, will start work on this shortly, unless woodchip wants to step in.
Spanky, The mod_perl issues have been resolved, but there is a problem with the hard coded dirs for apache you added now that apache is slotted. Throwing your way.
what is said issue ? woodchip has stated that /home/httpd is correct for hardcoding ...
re-open if something wasnt addressed ... i really have no idea what this is really about and the irc conversations didnt clear anything up for *me* :p
