When I attempt to upgrade to www-client/chromium-5.0.375.3, the compilation fails. Reproducible: Always Steps to Reproduce: 1. emerge www-client/chromium-5.0.375.3 2. Observe the build failure
Created attachment 228209 [details] emerge --info output
$ emerge -pqv =www-client/chromium-5.0.375.3 [ebuild U ] www-client/chromium-5.0.375.3 [5.0.307.9] USE="mp3%* plugins-symlink x264%* (-ffmpeg%*)"
Created attachment 228211 [details] build log
Looks like some new build scripts use perl now? Can you try to emerge virtual/perl-version and try again? Thanks
I think you need to have perl version >= 5.10.0 do compile this version of chromium. You will need to unmask a few packages (if you haven't done this before): echo -e "dev-lang/perl\nsys-devel/libperl\napp-admin/perl-cleaner" >> /etc/portage/package.keywords Then install perl 5.10.1 or newer: emerge -a =perl-5.10.1 After this, try installing chromium again.
(In reply to comment #5) > I think you need to have perl version >= 5.10.0 do compile this version of > chromium. > > You will need to unmask a few packages (if you haven't done this before): > > echo -e "dev-lang/perl\nsys-devel/libperl\napp-admin/perl-cleaner" >> > /etc/portage/package.keywords > > Then install perl 5.10.1 or newer: > > emerge -a =perl-5.10.1 > > After this, try installing chromium again. Thanks a lot, it's working now! Is there some way to know which versions of dependencies are needed if a package fails to compile like this, or do I just have to look at the build error?
(In reply to comment #5) > I think you need to have perl version >= 5.10.0 do compile this version of > chromium. I have perl-5.8.8 and no virtual/perl-version (and neither perl-core/version), and compile succeeded for me. Maybe you just have broken perl (and the update fixed the mess)?
After checking, perl-version only became a dual-life module in perl 5.10, so in perl 5.8 you only need perl itself (Pawel can you run a locate on version.pm? you should have one in /usr/lib/perl5/5.8.8 I think) And in this case that does mean you had a broken perl setup, perl-cleaner can help in cases like that too
(In reply to comment #8) > After checking, perl-version only became a dual-life module in perl 5.10, so in > perl 5.8 you only need perl itself (Pawel can you run a locate on version.pm? > you should have one in /usr/lib/perl5/5.8.8 I think) According to locate I don't have version.pm on my system.
Ok so probably a broken perl setup then (failed 5.10 update/perl-cleaner not run maybe?)
OK, I also installed using perl v5.8.8 today without any problems and without version.pm file :) The build log says version.pm is needed in this line: $VERSION = '1.95'; but I see only a declaration here. It means Balanced.pm file which caused the build failure must have had something else in this line. It is interesting that my Balanced.pm file is located in /usr/lib/perl5/5.8.8/Text directory, and the one from build log is somewhere else.
I'm closing this report, but feel free to re-open if you have more evidence that there is something to fix here.