Created attachment 399358 [details] emerge build log firefox-31.4.0 fails to build on a ppc system with 1GB RAM and 4GB swap space due to memory exhaustion: +++++ [...] INPUT("../../../gfx/ots/src/prep.o") INPUT("../../../gfx/ots/src/vhea.o") INPUT("../../../gfx/ots/src/vmtx.o") /usr/lib/gcc/powerpc-unknown-linux-gnu/4.8.3/../../../../powerpc-unknown-linux-gnu/bin/ld: failed to set dynamic section sizes: Memory exhausted collect2: error: ld returned 1 exit status /var/tmp/portage/www-client/firefox-31.4.0/work/mozilla-esr31/config/rules.mk:882: recipe for target 'libxul.so' failed make[5]: *** [libxul.so] Error 1 make[5]: Leaving directory '/var/tmp/portage/www-client/firefox-31.4.0/work/mozilla-esr31/obj-powerpc-unknown-linux-gnu/toolkit /library/build' /var/tmp/portage/www-client/firefox-31.4.0/work/mozilla-esr31/config/recurse.mk:95: recipe for target 'toolkit/library/build/li bs' failed make[4]: *** [toolkit/library/build/libs] Error 2 make[4]: Leaving directory '/var/tmp/portage/www-client/firefox-31.4.0/work/mozilla-esr31/obj-powerpc-unknown-linux-gnu' /var/tmp/portage/www-client/firefox-31.4.0/work/mozilla-esr31/config/recurse.mk:39: recipe for target 'libs' failed [...] +++++ The relevant files are attached.
Created attachment 399360 [details] emerge environment
Created attachment 399362 [details] emerge info
Created attachment 399364 [details] emerge -pqv output
You could try dropping -ggdb3 from CFLAGS.
(In reply to Michael Palimaka (kensington) from comment #4) > You could try dropping -ggdb3 from CFLAGS. Sure I could. But how would I get debugging symbols without the -g option?
(In reply to Thomas Jürges from comment #5) > (In reply to Michael Palimaka (kensington) from comment #4) > > You could try dropping -ggdb3 from CFLAGS. > > Sure I could. But how would I get debugging symbols without the -g option I am not sure what you are expecting from the mozilla team here. Your using a very out dated system with a very modern piece of software that has extensive linking. If you would tell me why you actually need the debugging symbols, I could provide you with the symbols.
(In reply to Jory A. Pratt from comment #6) > I am not sure what you are expecting from the mozilla team here. What I am expecting is very simple: Firefox is marked as stable on ppc hence I expect a clean build process without any hiccups. If my system is not supported due to the lack of something, I expect to be informed before the build process starts and not by an error in some link stage. > Your using > a very out dated system with a very modern piece of software that has > extensive linking. I can see that the linking took some time and did not work as expected. Hence this ticket. What is your point? That linking firefox or one of its helper libraries does not work on ppc hardware? > If you would tell me why you actually need the debugging > symbols, I could provide you with the symbols. Well, I need debugging symbols for the same reason everybody else needs debugging symbols. Because in case of a problem I would like to be able to debug the issue. So you are going to build firefox with the exact configuration (USE flags, relevant parts from make.conf) that I have set? Please be my guest. Like I said, I like to have all packages emerged with debugging symbols at hand just in case. Bottom line is that I am trying to emerge firefox on a supposedly supported platform with debugging symbols. And it appears to me that you are telling me that ppc is not supported anymore. If so then be so kind and mark the ppc arch as unsupported.
If you feel I have closed your bug and it is still a current issue, please reopen and update it completely. We will not work bugs that have no ebuild in tree any longer or can not be reproduced with a current system. Thank You for your support and understanding The Mozilla Team
