U need to enable "jumbo-build" in chromium use flags- emerge should be 2x times faster - and maybe ver70 is even 3x times faster with that, no idea why exaclty in v70 is much faster.
Its just normal ebuild from gentoo repository._________________ Installation aborted to prevent system self-destruction

U need to enable "jumbo-build" in chromium use flags- emerge should be 2x times faster - and maybe ver70 is even 3x times faster with that, no idea why exaclty in v70 is much faster.
Its just normal ebuild from gentoo repository.

Do you have any special env setting to build chromium 70.0.3538.110?
Since 70 i am not able anymore to use the USE jumbo-build (which was working fine with previous (<70) versions) now i exhaust all the memory (32gb ram and 8gb swap)

these were my previous compilation times:

In March is when i switched to jumbo-build
In July when i got the new ryzen 2700

then with latest chromium i was not able to use jumbo-build anymore... compiling now without it... (still compiling )

So -j9 with 16 gb of ram is not a good combination for that... ergo, I ordered 2 pairs of 8 gb dimms. They will be delivered on Wednesday. I'll try again when I am using 32 gb of ram.

Just to compile Chromium?

Chromium compile locked my system with -j9 and jumbo-build, so 16gb of ram was insufficient. I originally assumed 16 would be plenty, but I was wrong. I also switched to liquid cooling because of Gentoo. Where as before idle was at 30°C and peaking around 80°C with the stock fan, now it idles around 15°C and peaks out around 43°C.

As I've mentioned before, Gentoo is making Amazon, Newegg, and Visa happy._________________Time is a great teacher, but unfortunately it kills all its pupils.

i'm in the same boat as you guys now, this is the first time my i7 with 8gb of ram started locking up building with jumbo build, sucks because i only found out about using it like at the time of the last release, meaning i only was able to utilize it once before now i cant even build it anymore xD

note that building this failed with jb disabled, after about 7 hours i got a weird "chromedriver" error way way late in the build process resulting in death, this wraps up my time with chromium, i'll be moving on.. even package mask wouldn't stick and wanted me to upgrade chromium every time, several avenues of masking it actually... to make my life easier, simply uninstalled.

Last edited by sao98021 on Mon Dec 10, 2018 12:01 pm; edited 3 times in total

Unfortunately I need this browser for work and I don't want to get all the precompiled Google stuff on my laptop.

Thats a bit strange, I have 48 Gigs RAM, 0 swap(even disabled in kernel, CONFIG-SWAP=n) but: 2G on tmpfs in /tmp , 16G tmpfs on /var/tmp/portage and 3 Gigs for my own ccache (outside portage) compiles
and MAKEOPTS="-j16" and it never locked for me. Anyway your ram + swap is already 48 Gigs ( and I guess at least 5 gigs is used by portage in my tmpfs- merge says - Checking for at least 5 GiB disk space at "/var/tmp/portage/www-client/chromium-71.0.3578.80/temp")

EDIT: it seems im using clang to compile
I have in /etc/portage/package.env/default:
www-client/chromium clang
and in /etc/portage/env/clang
CC="clang"
CXX="clang++"
CFLAGS="-march=znver1 -O2 -pipe"
CXXFLAGS="${CFLAGS}"
LDFLAGS="-Wl,-O2 -Wl,--as-needed"

Seems I switched like 2 years when it failed to compile with gcc7.x and forgot ...

Zapcc has his own command so I guess its probably just pure clang 5.0, not real zapcc.

EDIT3:
I disabled clang env and tried with gcc and it failed to compile (died in lack of ram), when it died free -g -s1 reported that used was 42G, buff/cache was 4 ( during compile it was 7), and was something in shared._________________ Installation aborted to prevent system self-destruction

EDIT3:
I disabled clang env and tried with gcc and it failed to compile (died in lack of ram), when it died free -g -s1 reported that used was 42G, buff/cache was 4 ( during compile it was 7), and was something in shared.

Unfortunately I need this browser for work and I don't want to get all the precompiled Google stuff on my laptop.

Hi, what is your "jumbo_file_merge_limit" value? I have only 16 GB of ram with no swap, and I've tuned env settings for chrome as suggested in this thread and build succeded.
It failed with default settings though (it seems it's 200).