Summary: | sys-devel/gcc-4.4.5 - {standard input}:145813: Error: suffix or operands invalid for `movq' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marc Richter <richter_marc> |
Component: | New packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | CC: | gentoo, jmbsvicetto |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | It's the buildlog from the failing emerge |
Description
Marc Richter
2011-02-28 16:06:40 UTC
These are the last lines of the compile: /var/tmp/portage/sys-devel/gcc-4.4.5/work/build/./prev-gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-4.4.5/work/build/./prev-gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -c -DEFAULT_PIE_SSP -DEFAULT_RELRO -DEFAULT_BIND_NOW -O2 -pipe -march=core2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototype s -Wmissing-prototypes -Wcast-qual -Wold-style-definition -Wc++-compat -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H -I. -I. -I/var/tmp/portage/sys-devel/gcc-4.4.5/work/gcc-4.4.5/gcc -I/var/tmp/portage/sys-devel/gcc-4.4.5 /work/gcc-4.4.5/gcc/. -I/var/tmp/portage/sys-devel/gcc-4.4.5/work/gcc-4.4.5/gcc/../include -I/var/tmp/portage/sys-devel/gcc-4.4.5/work/gcc-4.4.5/gcc/../libcpp/include -I/var/tmp/portage/sys-devel/gcc-4.4.5/work/gcc-4.4.5/gcc/../libdecnumber -I/var/tmp/portage/sys-devel/gcc-4.4.5/work/gcc- 4.4.5/gcc/../libdecnumber/bid -I../libdecnumber /var/tmp/portage/sys-devel/gcc-4.4.5/work/gcc-4.4.5/gcc/bitmap.c -o bitmap.o /var/tmp/portage/sys-devel/gcc-4.4.5/work/build/./prev-gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-4.4.5/work/build/./prev-gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -c -DEFAULT_PIE_SSP -DEFAULT_RELRO -DEFAULT_BIND_NOW -O2 -pipe -march=core2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wcast-qual -Wold-style-definition -Wc++-compat -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H -I. -I. -I/var/tmp/portage/sys-devel/gcc-4.4.5/work/gcc-4.4.5/gcc -I/var/tmp/portage/sys-devel/gcc-4.4.5/work/gcc-4.4.5/gcc/. -I/var/tmp/portage/sys-devel/gcc-4.4.5/work/gcc-4.4.5/gcc/../include -I/var/tmp/portage/sys-devel/gcc-4.4.5/work/gcc-4.4.5/gcc/../libcpp/include -I/var/tmp/portage/sys-devel/gcc-4.4.5/work/gcc-4.4.5/gcc/../libdecnumber -I/var/tmp/portage/sys-devel/gcc-4.4.5/work/gcc-4.4.5/gcc/../libdecnumber/bid -I../libdecnumber /var/tmp/portage/sys-devel/gcc-4.4.5/work/gcc-4.4.5/gcc/bt-load.c -o bt-load.o /var/tmp/portage/sys-devel/gcc-4.4.5/work/build/./prev-gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-4.4.5/work/build/./prev-gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -c -DEFAULT_PIE_SSP -DEFAULT_RELRO -DEFAULT_BIND_NOW -O2 -pipe -march=core2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wcast-qual -Wold-style-definition -Wc++-compat -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H -I. -I. -I/var/tmp/portage/sys-devel/gcc-4.4.5/work/gcc-4.4.5/gcc -I/var/tmp/portage/sys-devel/gcc-4.4.5/work/gcc-4.4.5/gcc/. -I/var/tmp/portage/sys-devel/gcc-4.4.5/work/gcc-4.4.5/gcc/../include -I/var/tmp/portage/sys-devel/gcc-4.4.5/work/gcc-4.4.5/gcc/../libcpp/include -I/var/tmp/portage/sys-devel/gcc-4.4.5/work/gcc-4.4.5/gcc/../libdecnumber -I/var/tmp/portage/sys-devel/gcc-4.4.5/work/gcc-4.4.5/gcc/../libdecnumber/bid -I../libdecnumber /var/tmp/portage/sys-devel/gcc-4.4.5/work/gcc-4.4.5/gcc/builtins.c -o builtins.o {standard input}: Assembler messages: {standard input}:145803: Warning: end of file not at end of a line; newline inserted {standard input}:145813: Error: suffix or operands invalid for `movq' {standard input}:145813: Error: open CFI at the end of file; missing .cfi_endproc directive xgcc: Internal error: Killed (program cc1) Please submit a full bug report. See <http://bugs.gentoo.org/> for instructions. make[3]: *** [insn-attrtab.o] Error 1 make[3]: *** Waiting for unfinished jobs.... rm gcc.pod make[3]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.4.5/work/build/gcc' make[2]: *** [all-stage3-gcc] Error 2 make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.4.5/work/build' make[1]: *** [stage3-bubble] Error 2 make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.4.5/work/build' make: *** [bootstrap-lean] Error 2 emake failed Please attach the full build log to this bug report. Can you reproduce the same error? (In reply to comment #2) > Please attach the full build log to this bug report. > Can you reproduce the same error? > Sure - it happens everytime I issue "emerge --update --deep --newuse --verbose world". Please find the complete Build Log attached (sorry, I don't know how to strip the color codes). There's one more thing I can offer to help fixing this bug: Since this is a rented virtual Machine Server, and the machine is fresh installed without any personalized files in it, I could give you a root login to investigate the situation easily. Please let me know if this is needed. Created attachment 264209 [details]
It's the buildlog from the failing emerge
I get a different failure: {standard input}: Assembler messages: {standard input}:134323: Warning: end of file not at end of a line; newline inserted {standard input}:134411: Error: open CFI at the end of file; missing .cfi_endproc directive xgcc: Internal error: Killed (program cc1) Please submit a full bug report. See <http://bugs.gentoo.org/> for instructions. make[3]: *** [insn-attrtab.o] Error 1 make[3]: *** Waiting for unfinished jobs.... rm gcc.pod make[3]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.4.5/work/build/gcc' make[2]: *** [all-stage2-gcc] Error 2 make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.4.5/work/build' make[1]: *** [stage2-bubble] Error 2 make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.4.5/work/build' make: *** [bootstrap-lean] Error 2 emake failed * ERROR: sys-devel/gcc-4.4.5 failed: * emake failed with bootstrap-lean * * Call stack: * ebuild.sh, line 56: Called src_compile * environment, line 5017: Called toolchain_src_compile * environment, line 5612: Called gcc_src_compile * environment, line 3161: Called gcc_do_make * environment, line 2943: Called die * The specific snippet of code: * emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}" LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET} || die "emake failed with ${GCC_MAKE_TARGET}"; {standard input}: Assembler messages: {standard input}:145803: Warning: end of file not at end of a line; newline inserted {standard input}:145813: Error: suffix or operands invalid for `movq' {standard input}:145813: Error: open CFI at the end of file; missing .cfi_endproc directive xgcc: Internal error: Killed (program cc1) xgcc: Internal error: Killed (program cc1) almost never a bug in the compiler or package in question, but rather a problem with the system. look at `dmesg` to see the problem. maybe you need more ram, or swap, or lose the -pipe. *** This bug has been marked as a duplicate of bug 20600 *** SpanKY, marking this bug a dupe of that metabug was premature. You're thinking it's the OOM killer at work, but nope, I have nothing in my dmesg indicating that any process was killed due to OOM. (In reply to comment #7) > xgcc: Internal error: Killed (program cc1) > > almost never a bug in the compiler or package in question, but rather a problem > with the system. look at `dmesg` to see the problem. maybe you need more ram, > or swap, or lose the -pipe. > > *** This bug has been marked as a duplicate of bug 20600 *** > It seems as if you are right! Somehow I messed up my fstab during installation and so no swap was activated! The output of dmesg proves, that the compile gets out of RAM: Out of memory: Kill process 17905 (cc1) score 417 or sacrifice child Killed process 17905 (cc1) total-vm:445372kB, anon-rss:425360kB, file-rss:456kB Sorry, this was a stupid one. Thank you for your help! Then apparently that I received a different error message does in fact indicate that I have a different bug. I'll try building again, and if I still encounter the problem, I'll open a new bug report. (In reply to comment #10) > Then apparently that I received a different error message does in fact indicate > that I have a different bug. I'll try building again, and if I still encounter > the problem, I'll open a new bug report. > Embarrassment! I dmesg'd the wrong box. Yeah, it was an OOM. Phooey. i dont *always* talk out my ass. sometimes i know what i'm talking about ;). |