The perl 5.6.1-r8 craps out when building a system from scratch with: [... rest snipped...] /var/tmp/portage/perl-5.6.1-r8/image//usr/share/man/man1/xsubpp.1 make[1]: Leaving directory `/var/tmp/portage/perl-5.6.1-r8/work/perl-5.6.1' Can't locate lib.pm in @INC (@INC contains: /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 .) at installhtml line 5. BEGIN failed--compilation aborted at installhtml line 5. Can't locate lib.pm in @INC (@INC contains: /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 .) at Makefile.PL line 10. BEGIN failed--compilation aborted at Makefile.PL line 10. make: *** No rule to make target `install'. Stop. !!! ERROR: The ebuild did not complete successfully. !!! Function src_install, Line -136, Exitcode 2 !!! (no error message) myhost portage # maybe this could be fixed by adding a "-I${D}/usr/lib/perl5/${PV}" directive to ./perl installhtml and the rest but I didn't have time to play around with it. A better way IMHO would be to defer these actions to the pkg_postinst
Actually thinking about it pkg_postinst won't be too easy to pull off maybe a chrooted command will work?
Wondering if this isn't the MakeMaker fix breaking - maybe if we exported ${D}/usr/bin into the path and ${D}/usr/lib into the lib path...? that way perl and it's files could be seen by the makemaker build...not sure about the chrooted command in pkg_postinstall - just don't know anything about those mechanics, too bad we can't force an emerge afterwards for MakeMaker (pipe dream)
*** Bug 9092 has been marked as a duplicate of this bug. ***
Changing the command to this: ./perl -I${D}/usr/lib/perl5/${PV} -I${D}/usr/lib/perl5/${PV}/${CHOST%%-*}-linux installhtml --recurse --htmldir=${D}/usr/share/doc/${PF}/html makes the command succeed, although there are a tremendous amount of warnings about unresolvable pages. After this change, the following command that tries to build MakeMaker fails with the same bad @INC issue. I commented every line after the installhtml line out and the ebuild will then succesfully install. I browsed the html files a bit and they seem okay.
*** Bug 9105 has been marked as a duplicate of this bug. ***
*** Bug 9099 has been marked as a duplicate of this bug. ***
*** Bug 9067 has been marked as a duplicate of this bug. ***
OK, so attention everyone. mcummings informs me that ExtUtils-MakeMaker is absolutely required so that all the previous perl libinc woes were solved (previous == before -r8). So, with -r8 we tried making MakeMaker a part of perl. That obviously failed. Instead, what I have done is make MakeMaker a part of the required gentoo basic system along with perl. So, please emerge rsync, emerge -u system. That should pull in perl's -r7 again, along with MakeMaker, and we should hopefully all be happy. Please test and report here.
so people. success stories? failure stories? someone say something!
In the process of testing now... perl has built fine along with ExtUtils-MakeMaker Cheers, looks like thats fixed it.
closing this report, as users in #gentoo have stopped complaining of perl issues, and the only feedback in this report has been positive. Please re-open if the problem persists.
I just tried emerging perl-5.6.1-r8 on sparc64 again, and it still fails on the same error. I have perl-5.6.1-r7 already installed, along with dev-perl/ExtUtils-MakeMaker-6.05, any ideas?
you shouldnt be installing -r8 ... see comment #8 ... basically if you already have -r7 installed and you never made it to -r8, then just `emerge perl` to force a re-install of it
in fact, I have just removed -r8 from the portage tree
Alright, duly noted.
