GD perl library with ebuild GD-1.32-r1.ebuild is installed to directory /usr/lib/site_perl/5.6.1/i686-linux mod_perl @INC variable has these paths: /var/tmp/portage/mod_perl-1.27/image/usr/lib/site_perl/5.6.1/i686-linux /usr/lib/perl5/5.6.1/i686-linux/ /usr/lib/perl5/5.6.1/ /usr/lib/perl5/site_perl/5.6.1/i686-linux/ /usr/lib/perl5/site_perl/5.6.1 /usr/lib/perl5/site_perl/ and few others (. /etc/apache and so on) As you can see, /usr/lib/site_perl is not mentioned here... So mod_perl has this error: `Can't locate GD.pm in @INC ...
Roman, At least a few hours after this is posted, please emerge rsync again and try again. The MakeMaker fix is back in place and should correct this. Please let me know if this does not work for you. If you want to be sure that the mirror you synched from is up to date, please check the time stamp on /usr/portage/dev-perl/ExtUtils-MakeMaker - r1 should have a timestamp from today. Alternatively, you can verify that the MakeMaker module is a depend in the /usr/portage/eclass/perl-module.eclass file - both should have fairly recent time stamps (the eclass within the last day or so). Michael
OK, I've revised timestamps and ebuilds and all seems ok. All from 17.9.2002 I reemerged PERL (5.6.1) and reemerged DG, still GD is installed to /usr/lib/site_perl !!! It has to be installed to /usr/lib/perl5/site_perl ... Thanx for your time to ivestigate this error, I need solution fairly quick, 'cause it's on production server...
Created attachment 3992 [details] Replacement -r1 file Please replace your /usr/portage/dev-perl/GD/GD-1.32-r1.ebuild file with this attachment and try again. If this works for you, I will commit this as a replacement. I added a call to perl_module-src-prep to the GD ebuild, which would be the portion where it tells GD where to install =:) If this does not work for you, there are still a few things we can try, but this will eliminate the possiblity that it is the GD ebuild itself.
Forgot to say - in all of this, re-emerging perl is not necessary, and may cause more harm than good (since you will lose the MakerMaker patch that way). The MakeMaker that came with perl 5.6.1 was buggy to say the least. To counter this, the module eclass checks and install the ExtUtils-MakeMaker patch to replace the bad copy. However, if that ebuild was already emerged previously, and you re-installed perl, portage isn't "smart" enough to re-install the patch - it thinks it's already applied. If the attached ebuild does not work for you, I would recommend emerge dev-perl/ExtUtils-MakeMaker to patch your perl up again manually. But don't try that unless the above does not work right. I have test that ebuild against both my perl 5.6.1 box and perl 5.8.0 box, and in both cases it installed to the right path (and the 5.6.1 box is a "fresh" build). Michael
Nice, your ebuild works excellent!!! Now all works... So if you know this solution, applay it to portage tree and you can close this bug as solved... Thanx you very much for so quick solution of this error...
FYI, when I commit this, it will be a version bump since the previous version installed fine but failed quietyl (I need to catch any user that installed it but doesn't realize it didn't work), so within a day or so you will see an upgrade following the version bump. It will actually be the version you downloaded today, so it's your call on whether you want to upgrade again. Mike
OK, this has been commited. Enjoy, and thanks for your patience!
no problem with me... upgrade will be binary compatible, so go for it...
