As part of a long-distance upgrade of more than 200 packages on a Pentium4 machine, emerge of =www-client/chromium -7.0.517.44 failed. Rebooting and re-emerging did not help. The problem persists. Reproducible: Always Steps to Reproduce: 1. emerge -puND world (or emerge chromium) 2. 3. Actual Results: ld failed Expected Results: ld successful
Created attachment 256709 [details] emerge --info
Created attachment 256710 [details] emerge -pqv
Created attachment 256712 [details] Build log
> collect2: ld terminated with signal 9 [Killed] Looks like you ran out of memory when linking the final binary?
(In reply to comment #4) > > collect2: ld terminated with signal 9 [Killed] > > Looks like you ran out of memory when linking the final binary? > If that's the case, I suggest building without debug symbols (-ggdb). That will cut the linker's memory usage by 50-75%.
> ... I suggest building without debug symbols (-ggdb). That will > cut the linker's memory usage by 50-75%. Makes sense, I'm going to try that and will report on the effect. The reason why I set CFLAGS="... -ggdb" is that I would want to build KDE with -ggdb and FEATURES="splitdebug" so that I am able to contribute via DrKonqi. Is there a way to switch between different CFLAGS settings (you know what I mean when I say "/etc/portage/package.cflags"), or do I seem to fight windmills here?
(In reply to comment #6) > Is there a way to switch between different CFLAGS settings (you know what I > mean when I say "/etc/portage/package.cflags"), or do I seem to fight windmills > here? > You can do this by utilizing package.env. For example: mkdir -p /etc/portage/env echo 'CFLAGS="..."' > /etc/portage/env/nodebug echo 'CXXFLAGS=${CFLAGS}' >> /etc/portage/env/nodebug echo "www-client/chromium nodebug" >> /etc/portage/package.env See portage(5) for more info.
Thanks for all the advice! Removing "-ggdd" for the compilation did do the job. I will use the /etc/portage/env trick. Closing the “bug”.
*** Bug 597144 has been marked as a duplicate of this bug. ***
