When I do "emerge apps-games/frozen-bubble-0.9.3-r1.ebuild", it fails with this error: >>> md5 ;-) frozen-bubble-0.9.3.tar.bz2 >>> Unpacking source... >>> Unpacking frozen-bubble-0.9.3.tar.bz2 >>> Source unpacked. Can't locate SDL.pm in @INC (@INC contains: /usr/lib/perl5/5.6.1/powerpc-linux / usr/lib/perl5/5.6.1 /usr/lib/perl5/site_perl/5.6.1/powerpc-linux /usr/lib/perl5/ site_perl/5.6.1 /usr/lib/perl5/site_perl .) at -e line 1. BEGIN failed--compilation aborted at -e line 1. *** I need perl-SDL installed make: *** [dirs] Error 1 !!! ERROR: The ebuild did not complete successfully. !!! Function src_compile, Line 2, Exitcode 2 !!! (no error message) So, I went ahead and did "emerge dev-perl/sdl-perl" figuring that would solve the problem. It didn't. I did some poking around and found the problem. Aparently the SDL.pm gets installed in the wrong place. If I do "qpkg -l sdl-perl | grep SDL.pm", I get: /usr/lib/site_perl/5.6.1/powerpc-linux/SDL.pm Notice that this is not one of the paths that shows up in the error message above. Aparently there are multiple "site_perl" directories lying around. If it's not supposed to be that way, the sdl-perl emerge might be putting things in the wrong directory. If it is the correct directory, it ought to be added to perl's default path.
perl-sdl is not the only emerge which puts stuff in "/usr/lib/site_perl/5.6.1/powerpc-linux/". On my system, I have additional files in that directory, such as: /usr/lib/site_perl/5.6.1/powerpc-linux/Image/Magick.pm /usr/lib/site_perl/5.6.1/powerpc-linux/XML/Parser.pm I used "qpkg -f" to find which ebuild they came from and it implicated "dev-perl/XML-Parser" and "media-gfx/imagemagick." These packages might need to be looked at as well, to make sure they aren't broken too.
This bug is the same as in bug #8725.
This has been a documented and addressed problem in both other bugs and the mailing lists. You will need to *either* emerge dev-utils/ExtUtils-MakeMaker OR emerge perl -r7. There was a problem with the MakeMaker module that came with the default perl - among other things, it was placing sandbox-created ebuilds into /usr/lib/site_perl instead of /usr/lib/perl5/site_perl. Emerging either of the two above will correct this problem for FUTURE emerges. You will need to re- emerge the offending applications again to resolve the problem with their current location. This should have been caught by the perl-modules eclass, but on randomly rare occasions it wasn't. Sorry for the inconvenience, let me know if you you continue to have problems.
Bug 9067 fixes this *** This bug has been marked as a duplicate of 9067 ***
