gcc 10.2.0 will not compile on a 32bit machine. Gave the VM 3GiB RAM, compiling with -j1 so only one process is active and still: cc1plus: out of memory allocating 24088860 bytes after a total of 53628928 bytes make[4]: *** [Makefile:678: aatree.lo] Error 1 make[4]: Leaving directory '/var/tmp/portage/sys-devel/gcc-10.2.0-r1/work/build/i686-pc-linux-gnu/libitm' make[3]: *** [Makefile:836: all-recursive] Error 1 make[3]: Leaving directory '/var/tmp/portage/sys-devel/gcc-10.2.0-r1/work/build/i686-pc-linux-gnu/libitm' make[2]: *** [Makefile:518: all] Error 2 make[2]: Leaving directory '/var/tmp/portage/sys-devel/gcc-10.2.0-r1/work/build/i686-pc-linux-gnu/libitm' make[1]: *** [Makefile:19493: all-target-libitm] Error 2 make[1]: Leaving directory '/var/tmp/portage/sys-devel/gcc-10.2.0-r1/work/build' make: *** [Makefile:20826: bootstrap-lean] Error 2
Please attach the entire build log to this bug report. Please post your `emerge --info' output in a comment.
Please provide 'emerge --info' output and 'build.log'. > cc1plus: out of memory allocating 24088860 bytes after a total of 53628928 bytes make[4]: *** [Makefile:678: aatree.lo] Error 1 50MB does not look like a lot of RAM. Are you building in tmpfs?
@Sergei: No tmpfs and actually encountering the same problem with gcc 9.3.0 on the same machine and ALSO after adding 1GB of swap. (this is 9.3.0) cc1plus: out of memory allocating 24082176 bytes after a total of 50462720 bytes make[4]: *** [Makefile:678: alloc_c.lo] Error 1 make[4]: Leaving directory '/var/tmp/portage/sys-devel/gcc-9.3.0-r1/work/build/i686-pc-linux-gnu/libitm' make[3]: *** [Makefile:836: all-recursive] Error 1 make[3]: Leaving directory '/var/tmp/portage/sys-devel/gcc-9.3.0-r1/work/build/i686-pc-linux-gnu/libitm' make[2]: *** [Makefile:518: all] Error 2 make[2]: Leaving directory '/var/tmp/portage/sys-devel/gcc-9.3.0-r1/work/build/i686-pc-linux-gnu/libitm' make[1]: *** [Makefile:19064: all-target-libitm] Error 2 Machine could compile a 9.2.0. Will provide the log and emerge info ASAP.
see also https://bugs.gentoo.org/750236
Can you post 'emerge --info' here as well? I see that in linked bug you are using x86 (and I completely missed initial topic which said it's a 32-bit build).
It's the same machine. And yes, originally the 32bit info was in the subject. ;-)
If you rerun failed comman manually in $WORKDIR does it fail the same way?
(In reply to Sergei Trofimovich from comment #7) > If you rerun failed comman manually in $WORKDIR does it fail the same way? Yes. Current state of the matter is that none of our Gentoo 32bit KVM machines is able to compile a GCC >9.2.0 (9.2.0 working fine). Currently we're contemplating migrating these machines to 64bit and leaving 32bit behind, so it's no pressing issue, but we're also not intending to invest more energy into finding the root cause. Therefore please adjust the state of the ticket at your discretion.
