Summary: | x86_64-pc-linux-gnu-g++: Internal error: Killed (program cc1plus) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | James Ashley <james.ashley> |
Component: | [OLD] Core system | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Build log |
Description
James Ashley
2012-08-30 22:44:46 UTC
It looks like I lied about its reproducibility. When I re-ran the emerge, it worked up until this error: x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I/var/tmp/portage/sys-devel/binutils-2.22-r1/work/binutils-2.22/gold -I/var/tmp/portage/sys-devel/binuti ls-2.22-r1/work/binutils-2.22/gold -I/var/tmp/portage/sys-devel/binutils-2.22-r1/work/binutils-2.22/gold/../include -I/var/tmp/portage/sys-devel/binut ils-2.22-r1/work/binutils-2.22/gold/../elfcpp -DLOCALEDIR="\"/usr/share/binutils-data/x86_64-pc-linux-gnu/2.22/locale\"" -DBINDIR="\"/usr/x86_64-pc-li nux-gnu/binutils-bin/2.22\"" -DTOOLBINDIR="\"/usr/x86_64-pc-linux-gnu/bin\"" -W -Wall -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -frandom-seed=re loc.o -O2 -pipe -MT reloc.o -MD -MP -MF .deps/reloc.Tpo -c -o reloc.o /var/tmp/portage/sys-devel/binutils-2.22-r1/work/binutils-2.22/gold/reloc.cc {standard input}: Assembler messages: {standard input}:54471: Warning: end of file not at end of a line; newline inserted {standard input}:54547: Error: undefined symbol `.LLSDACSE6047' in operation {standard input}:54573: Error: undefined symbol `.LFB' in operation x86_64-pc-linux-gnu-g++: Internal error: Killed (program cc1plus) Please submit a full bug report. (which is farther along) And I to include the emerge -pqv: [ebuild U ] sys-devel/binutils-2.22-r1 [2.20.1-r1] USE="cxx%* nls zlib%* -multislot -multitarget -static-libs% -test -vanilla" I ran it again and kept an eye on top. The behavior I saw there was: 4 instances of cc1plus, each averaging about 15% of "memory". Compilation paused for several minutes on options.cc. Nothing seemed to be using much CPU (the 4 cc1plus processes were sitting at around 2-3%) or RAM, but available memory shrunk to basically 0. Eventually, it moved on to output.cc. Some RAM was restored, but not much. A few minutes later one instance of cc1plus died. This time, the accompanying error message was: {standard input}: Assembler messages: {standard input}:33536: Warning: end of file not at end of a line; newline inserted {standard input}:33918: Error: suffix or operands invalid for `cmp' {standard input}:33918: Error: open CFI at the end of file; missing .cfi_endproc directive x86_64-pc-linux-gnu-g++: Internal error: Killed (program cc01plus) Please submit a full bug report. It spent a few more minutes at make[4]: *** [output.o] Error 1 make[4]: *** Waiting for unfinished jobs.... When one of the cc1plus processes did show a huge increase in its memory footprint (it quickly ballooned out to ~60%), until it exited. Then the cleanup happened. It took much longer than I would have expected, but it probably isn't related. mv -f .deps/object.Tpo .deps/object.Po mv -f .deps/layout.Tpo .deps/layout.Po mv -f .deps/incremental.Tpo .deps/incremental.Po Both of these build logs are available if anyone thinks they might help. I don't see anything particularly interesting or different. I've never had memory issues when emerging before, but it's always possible that binutils now simply takes more than I have available (256 MB RAM, 512 MB swap). So, despite the error messages, I'm not convinced this is an actual bug. (And I really suspect it's an issue with different versions of things in my toolchain not playing nicely together). This just keeps getting stranger. Setting MAKEFLAGS=-j2 seems to have fixed the problem. (I *did* search the forums before I opened this; it just wasn't a successful search). So maybe the "bug" is really just the error message. Which, for an out-of-memory situation, probably isn't worth fixing. I'm sorry for wasting time/bandwidth. You ran out of RAM. |