[Solved] www-client/firefox-128.4.0 fail to merge

Fitap · Last edited by Fitap on Sat Nov 02, 2024 12:34 am; edited 1 time in total

Hi there,
Here you are the log www-client/firefox-128.4.0

logrusx · Advocate Joined: 22 Feb 2018 Posts: 2541

Frautoincnam · Guru Joined: 19 May 2017 Posts: 330

flysideways · Guru Joined: 29 Jan 2005 Posts: 500

I just finished an update on an 8GB Pi 5 with -j4 set, it did go to swap during the firefox emerge and it took 50% longer than the prior firefox emerges. It showed 1.6GB in swap.

Fitap · Posted: Fri Nov 01, 2024 10:28 pm Post subject:

Hu · Administrator Joined: 06 Mar 2007 Posts: 22892

As logrusx suspected, dmesg shows that various processes, including compiler processes, were killed due to out-of-memory. You do not have sufficient virtual memory to run this build with these settings. Add more virtual memory, or run fewer programs at once. The latter is likely easier.

Fitap

Fitap · Posted: Sat Nov 02, 2024 12:34 am Post subject:

Juippisi · Developer Joined: 30 Sep 2005 Posts: 757 Location: /home

Note that we flipped the default use flag +clang off for these releases and it now uses GCC by default to build. GCC does take more memory than clang, although the real difference should come when +lto is enabled (and in your case it's not). However you can most likely get away using less memory if you enable +clang on firefox on your own. There's also the jumbo-build use flag which will help reducing memory usage if you turn it off, but it'll drastically increase the compilation time of firefox too.

logrusx · Advocate Joined: 22 Feb 2018 Posts: 2541

There is a file merge limit, for jumbo-build. Even values like 10 or 15 give huge difference. You should be able to dig it in the forums.

Best Regards,
Georgi

Juippisi · Developer Joined: 30 Sep 2005 Posts: 757 Location: /home