Hi rac ;), I was searching for a nice thingy to test yesterday and your new perl ebuild looked like it would solve my trouble with apache2 + mod_perl (different @INC values (i586 versus i686)). Well in short, it doesn't ;D. First of all, it looks a lot like Martin's problem in Bug # 23416 (even if we're talking about different Apache's). Perl -V gives me a complete different @INC that I get from my failing Apache2 (see output below). Also - to my surprise - after rebuilding perl, apache2 and mod_perl last night (including your wonderful rebuilding-script), File-Safe was - again - installed. Is this normal behavior ? <OUTPUT perl -V> Characteristics of this binary (from libperl): Compile-time options: USE_LARGE_FILES Built under linux Compiled at Jul 1 2003 00:47:18 @INC: /etc/perl /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 /usr/lib/perl5/5.8.0/i686-linux /usr/lib/perl5/5.8.0 /usr/local/lib/site_perl <OUTPUT /etc/init.d/apache2 start> * Starting apache2... [Tue Jul 01 13:08:56 2003] [error] Can't locate Apache2.pm in @INC (@INC contains: /usr/lib/perl5/5.8.0/i586-linux /usr/lib/perl5/5.8.0 /usr/lib/perl5/site_perl/5.8.0/i586-linux /usr/lib/perl5/site_perl/5.8.0 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.0/i586-linux /usr/lib/perl5/vendor_perl/5.8.0 /usr/lib/perl5/vendor_perl . /etc/apache2/ /etc/apache2/lib/perl) at /etc/apache2/conf/modules.d/apache2-mod_perl-startup.pl line 1. BEGIN failed--compilation aborted at /etc/apache2/conf/modules.d/apache2-mod_perl-startup.pl line 1. Compilation failed in require at (eval 1) line 1. </OUTPUT> Reason why :) <SNIP> 26 Jun 2003; <rac@gentoo.org> perl-5.8.0-r12.ebuild: Add block depends on ExtUtils-MakeMaker and File-Spec, because we need to get those uninstalled before they steal our files again # <rac@gentoo.org> (24 Jun 2003) # very untested, changes @INC order =dev-lang/perl-5.8.0-r12 </SNIP> Keep up the good work, Rogi
I don't really know how this happens, but you somehow have a confused compiler. You need to get rid of all the i586 directories, although without crippling your compiler, and then perhaps remerging gcc. Then recompile affected apps (apache, perl, mod_perl).
Hmmm, doesn't sound good... 'll try ASAP to know 4 sure.. Thanx for the advice, Rogi
A new day, a new fresh gcc, perl and all the works...No more i586 (recompiled the stuff qpkg was telling me) but still the same trouble :( Any more ideas Robert ? Rogi
Additionally File-Spec keeps showing up in my world...Should I inject it or emerge it (after reading the Changelog I'm not sure what to do with this ebuild... Rogi
I still don't understand the i586 thing - as for File-Spec, I would recommend injecting it - it will overwrite files in your perl core otherwise. If you do choose to install it, if you unmerge it, you will need to remerge perl to get it back, because portage will get confused as to who owns it.
:D !! Rac, you can close this bugger...I think it was recompiling libperl (instead of just perl) and/or 5.8.1_RC1 that did the trick, but after that it works now... <SNIP output> [Fri Jul 11 12:39:29 2003] [notice] Apache/2.0.47 (Gentoo/Linux) mod_perl/1.99_09 Perl/v5.8.1 mod_ssl/2.0.47 OpenSSL/0.9.7b PHP/4.3.2 configured -- resuming normal operations </SNIP output> /me happy, Rogi
Still a problem here; File-Spec wants to be re-installed - why is this?
btw !<dev-perl/ExtUtils-MakeMaker-6.05-r6 !<dev-perl/File-Spec-0.84-r1 blocking update of perl after changing to >=dev-perl/ExtUtils-MakeMaker-6.05-r6 >=dev-perl/File-Spec-0.84-r1 and the next !< too what is comletely the same, all works fine P.S. portage-2.0.48-r5
File-Spec should be safe from overwriting core files now that we have vendordir support, so injecting is no longer recommended.
