Created attachment 467134 [details] build.log There's not much to say here, The complete build log is 38MiB, so I've included only the last 400 lines of it (I recall that previously I was requested not to post to other sites...).
Created attachment 467136 [details] emerge info
Created attachment 467138 [details] environment file
from the log: x86_64-pc-linux-gnu-g++: internal compiler error: Killed (program cc1plus) Can you check dmesg or something whether it was killed due to OOM? PS: If full build.log is too large to attach, you may attached compressed build.log; the ending as-is seems to be sufficient in this case after looking, though.
If the build got killed due to OOM, you might try reducing the number of jobs in MAKEOPTS.
Hey guys thanks for the quick replies. Seeing the errors, I had a hunch it might be memory related but I had no clue how to check it out. Thanks to you referring me to dmesg I can confirm: Out of memory: Kill process 29063 (cc1plus) score 114 or sacrifice child [ 7525.265830] Killed process 29063 (cc1plus) total-vm:1202824kB, anon-rss:1050028kB, file-rss:960kB, shmem-rss:0kB Can you believe that? this Chromium is a monster! if 8 GiB of RAM isn't enough. I reduced to 6 jobs (from 9 initially) and monitored the RAM - it didn't get past the 4 GiB and compilation was successful. P.S. for the record, I feel I must also leave my remark regarding: "you may attached compressed build.log" Well, compressing a 38MiB obviously wouldn't be enough to reach 1000KB, that means I'll also have to split the file as well, and to be honest, I know I sound lazy and maybe even ungrateful - which I'm not by the way, but that's just too much work for me. The truth is I really hate filling bug reports, I'm sure you guys hate getting them too...
(In reply to jhon from comment #5) > P.S. for the record, I feel I must also leave my remark regarding: "you may > attached compressed build.log" > > Well, compressing a 38MiB obviously wouldn't be enough to reach 1000KB, that > means I'll also have to split the file as well, and to be honest, I know I > sound lazy and maybe even ungrateful - which I'm not by the way, but that's > just too much work for me. > The truth is I really hate filling bug reports, I'm sure you guys hate > getting them too... I said it was fine in this case :) I don't have the 38MiB log to see if a simple xz on it makes it small enough, but if the problem was obvious, that's no problem. The start of the build.log can sometimes be nice though too, it has some information that "emerge --info <package>" would give (if the emerge were actually successful). In this case as we saw, it wasn't necessary, as I suspected and said :) PS: You should be able to change the MAKEOPTS per-package via /etc/portage/env/ + /etc/portage/package.env/
Chromium build logs actually compress surprisingly well; I usually end up with a 700KB xz file from a 50MB log file.
> "PS: You should be able to change the MAKEOPTS per-package via /etc/portage/env/ + /etc/portage/package.env/" > "Chromium build logs actually compress surprisingly well; I usually end up with a 700KB xz file from a 50MB log file." Awesome guys, I'll look into that "package.env" Nonetheless, Chromium is a MONSTER :P
