Fresh gentoo installation, on my way to build Plasma environment. "~amd64" keyword is being used. qtwebengine fails to build with: FAILED: obj/content/browser/browser/network_handler.o ... {standard input}: Assembler messages: {standard input}:12209: Warning: end of file not at end of a line; newline inserted {standard input}:12210: Error: expecting operand after ','; got nothing x86_64-pc-linux-gnu-g++: fatal error: Killed signal terminated program cc1plus compilation terminated. ... ninja: build stopped: subcommand failed. Reproducible: Always Steps to Reproduce: 1. Try to emerge dev-qt/qtwebengine-5.15.0 2. Build fails Actual Results: Build fails Expected Results: Build succeeds Just in case, looking at https://bugs.gentoo.org/740580 , I tried to build qtwebengine with bison-3.7.1, bison-3.7 and bison-3.6.4 (last attempt, logs provided are from this one) - it did not help. # emerge -pqv '=dev-qt/qtwebengine-5.15.0::gentoo' [ebuild N ] dev-qt/qtwebengine-5.15.0 USE="alsa pulseaudio system-ffmpeg system-icu widgets -bindist -debug -designer -geolocation -jumbo-build -kerberos -test" Other info will be added as attachments.
Created attachment 659154 [details] emerge-info # emerge --info '=dev-qt/qtwebengine-5.15.0::gentoo'
Created attachment 659156 [details] build log (gzipped)
Created attachment 659160 [details] ebuild environment
> x86_64-pc-linux-gnu-g++: fatal error: Killed signal terminated program cc1plus In almost every cases that means you ran out of ram while building. Try lower MAKEOPTS=-jX value, and if you were building on tmpfs, don't. Seeing you have none could also add a bit of swap but don't overly rely on this given it's slow. Use forums / irc or similar if need more help, this isn't for the bug tracker.
please test and reopen, if still present.
Sorry for posting bugreport for my local issue. Probably, I expected something about OOM killer in the error message. After your advice, I've checked dmesg, and yes - OOM message was there. Tried to merge qtwebengine with -j1 - it took me 55+ hours, but build succeeded. Thanks for help.
*** This bug has been marked as a duplicate of bug 663770 ***
