When compiling www-client/chromium-20.0.1132.57 with dev-libs/elfutils-0.108-r1 installed, the compilation fails with following error: LD_LIBRARY_PATH=/var/tmp/portage/www-client/chromium-20.0.1132.57/work/chromium-20.0.1132.57/out/Release/lib.host:/var/tmp/portage/www-client/chromium-20.0.1132.57/work/chromium-20.0.1132.57/out/Release/lib.target:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH; cd native_client/src/trusted/service_runtime/linux; mkdir -p /var/tmp/portage/www-client/chromium-20.0.1132.57/work/chromium-20.0.1132.57/out/Release; python nacl_bootstrap_munge_phdr.py "/var/tmp/portage/www-client/chromium-20.0.1132.57/work/chromium-20.0.1132.57/out/Release/nacl_bootstrap_munge_phdr" "/var/tmp/portage/www-client/chromium-20.0.1132.57/work/chromium-20.0.1132.57/out/Release/nacl_bootstrap_raw" "/var/tmp/portage/www-client/chromium-20.0.1132.57/work/chromium-20.0.1132.57/out/Release/nacl_helper_bootstrap" nacl_bootstrap_munge_phdr: elf32_updatenull.c:174: __elf64_updatenull: Assertion `shdr != ((void *)0)' failed. Traceback (most recent call last): File "nacl_bootstrap_munge_phdr.py", line 39, in <module> sys.exit(Main(sys.argv)) File "nacl_bootstrap_munge_phdr.py", line 33, in Main subprocess.check_call([munger, tmpfile, segment_num]) File "/usr/lib64/python2.6/subprocess.py", line 488, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['/var/tmp/portage/www-client/chromium-20.0.1132.57/work/chromium-20.0.1132.57/out/Release/nacl_bootstrap_munge_phdr', '/var/tmp/portage/www-client/chromium-20.0.1132.57/work/chromium-20.0.1132.57/out/Release/nacl_helper_bootstrap.tmp', '2']' returned non-zero exit status -6 make: *** [out/Release/nacl_helper_bootstrap] Error 1 make: *** Waiting for unfinished jobs.... The solution is to upgrade to newer dev-libs/elfutils (tried dev-libs/elfutils-0.149 successfully, don't know what is minimal requirement.) Not sure if it's the nacl itself requiring that or just chromium.
How did you end up with such an ancient version? It was removed from the tree over 5 years ago.
Also, chromium-20 was removed from the tree a week or 2 ago...
Probably nothing ever depended on newer version of elfutils all those 5 years (I mean, nothing I needed to install). That's nothing, I first installed Gentoo in 2005 and on THAT computer, I still have several packages from that year, including libIDL-0.8.2, libxml1.8.17-r2, libowfat-0.14 and libtool-1.4.3-r3 (although THAT's slotted and I also have libtool-2.2.10 installed). Also, yes, I emerge --synced and started upgrade. Took two or three weeks before I finished all those revdep-rebuilds and finally emerged libjpeg-turbo and therefore chromium :-). I have also something other to do that upgrading gentoo and this is not my only instalation.
Uh. Sorry. I meant 2004, not 2005.
Dependency updated. Generally you should keep your system up-to-date (or at least update everything without leaving old packages not updated), but if this change prevents people hitting problems like this, good.
Actually I consider big advantage when if I'm satisfied with how application work I'm not forced to upgrade it and risk I don't like the change (not speaking about deleting of application). Obviously this approach have problems with libraries (or, generally, runtime dependencies). Unfortunately, most attempts on --update --deep not only tries to update too much, but often ends in error. For example, why should mplayer depend on rdoc or trigger the deadlock between rdoc and hoe? So, I must depend on the fact important libraries either get some GLSA or new version is dragged in by versioned dependency ... It's true I should look at least on these 5+ years old packages ... In any case, thanks for making Gentoo work even without periodical emerge world ...
