Summary: | emerge sys-devel/gcc-4.7.3-r1 fails: 12151 Killed build/genattrtab | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | John L. Poole <prestopoole> |
Component: | [OLD] GCC Porting | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build.log
environment |
Description
John L. Poole
2013-11-07 15:59:23 UTC
Created attachment 362740 [details]
build.log
Created attachment 362742 [details]
environment
for posterity, the image is gentoo.2013-01.x86-64.20130102.img.tar.bz2 from http://www.stacklet.com/downloads/images/lister/Gentoo/2013-06/x86-64 You ran out of RAM. Install more or try some of the usual workarounds (remove -pipe from C*FLAGS, for instance). Thank you. I had 512 RAM allocated in the XEN configuration file (this is my first foray into XEN) and the Gentoo build was my first "guest" image; I altered the RAM to 4096 and it compiled. Is there something in the logs that indicate exceeding the memory, or is sudden death without any indication when memory is set low something one just learns as a symptom? my most recent entry above mistakenly said GCC compiled when, in fact, binutils had successfully compiled (I was adding a comment here thinking this bug was Bug #490696). I noted the confusion in Bug #490696 and indicated therein that I was in the processing of compiling GCC. I can now declare that GCC has compiled successfully. Thank you, again. |