| View previous topic :: View next topic |
| Author |
Message |
Fitap
Guru
Joined: 13 Mar 2011
Posts: 450
Location: Rosario, Argentina
|
 Posted: Fri Nov 01, 2024 3:12 pm Post subject: [Solved] www-client/firefox-128.4.0 fail to merge |
 |
|
Hi there,
Here you are the log www-client/firefox-128.4.0
Last edited by Fitap on Sat Nov 02, 2024 12:34 am; edited 1 time in total |
|
| Back to top |
|
 |
logrusx
Advocate
Joined: 22 Feb 2018
Posts: 2374
|
| Posted: Fri Nov 01, 2024 3:24 pm Post subject: |
|
|
| Code: | 8 6:13.60 x86_64-pc-linux-gnu-g++: fatal error: Killed signal terminated program cc1plus
|
Most likely OOM killed the process. What does this say:
Try with capital OOM as well as I don't remember which case it exactly is.
What are your MAKEOPTS as well as EMERGE_DEAFULT_OPTS?
Share your emerge --info
You may try to resume it with
| Code: | | FEATURES="keepwork" emerge --resume |
but if there are more packages scheduled, terminate after firefox and resume without keepwork. Then manually clean your /var/tmp/portage or whatever PORTAGE_TMPDIR is.
Best Regards,
Georgi |
|
| Back to top |
|
|
Frautoincnam
Guru
Joined: 19 May 2017
Posts: 324
|
| Posted: Fri Nov 01, 2024 5:31 pm Post subject: Re: www-client/firefox-128.4.0 fail to merge |
|
|
Same here.
bug filled
Not a memory space problem
| Code: | $ LANG=C free -g
total used free shared buff/cache available
Mem: 31 7 7 0 16 23
Swap: 32 0 31 |
Edit:
I could emerge it with FEATURES="-distcc" |
|
| Back to top |
|
|
flysideways
Guru
Joined: 29 Jan 2005
Posts: 490
|
| Posted: Fri Nov 01, 2024 8:52 pm Post subject: |
|
|
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.
| Code: | funf ~ # qlop -mtv firefox
2024-02-24T01:24:38 >>> www-client/firefox-115.8.0: 1:55:33
2024-03-23T04:19:30 >>> www-client/firefox-115.9.0: 2:00:47
2024-03-25T07:46:53 >>> www-client/firefox-115.9.1: 2:00:34
2024-04-17T06:12:41 >>> www-client/firefox-115.10.0: 2:03:27
2024-06-02T03:29:18 >>> www-client/firefox-115.11.0: 1:51:02
2024-08-10T08:11:16 >>> www-client/firefox-128.1.0: 2:06:02
2024-09-03T07:40:55 >>> www-client/firefox-128.2.0: 2:05:07
2024-09-28T11:27:22 >>> www-client/firefox-128.2.0: 2:06:00
2024-10-06T17:08:48 >>> www-client/firefox-128.3.0: 1:53:05
2024-10-11T17:21:46 >>> www-client/firefox-128.3.1: 1:53:29
2024-11-01T12:02:44 >>> www-client/firefox-128.4.0: 3:08:46
|
|
|
| Back to top |
|
|
Fitap
Guru
Joined: 13 Mar 2011
Posts: 450
Location: Rosario, Argentina
|
| Posted: Fri Nov 01, 2024 10:28 pm Post subject: |
|
|
| logrusx wrote: | | Code: | 8 6:13.60 x86_64-pc-linux-gnu-g++: fatal error: Killed signal terminated program cc1plus
|
Most likely OOM killed the process. What does this say:
Try with capital OOM as well as I don't remember which case it exactly is.
What are your MAKEOPTS as well as EMERGE_DEAFULT_OPTS?
Share your emerge --info
You may try to resume it with
| Code: | | FEATURES="keepwork" emerge --resume |
but if there are more packages scheduled, terminate after firefox and resume without keepwork. Then manually clean your /var/tmp/portage or whatever PORTAGE_TMPDIR is.
Best Regards,
Georgi |
Thanks logrusx
emerge --info
dmesg | grep oom |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22592
|
| Posted: Fri Nov 01, 2024 10:47 pm Post subject: |
|
|
| 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. |
|
| Back to top |
|
|
Fitap
Guru
Joined: 13 Mar 2011
Posts: 450
Location: Rosario, Argentina
|
| Posted: Fri Nov 01, 2024 11:25 pm Post subject: Re: www-client/firefox-128.4.0 fail to merge |
|
|
| Frautoincnam wrote: |
Same here.
bug filled
Not a memory space problem
| Code: | $ LANG=C free -g
total used free shared buff/cache available
Mem: 31 7 7 0 16 23
Swap: 32 0 31 |
Edit:
I could emerge it with FEATURES="-distcc" |
Thanks Frautoincnam for response.
Did added "-distcc" in FEATURES but I get same issue. |
|
| Back to top |
|
|
Fitap
Guru
Joined: 13 Mar 2011
Posts: 450
Location: Rosario, Argentina
|
| Posted: Sat Nov 02, 2024 12:34 am Post subject: |
|
|
| Hu wrote: | | 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. |
Ok.
| Code: | MAKEOPTS="-j6"
PORTAGE_TMPDIR="/var/tmp/notmpfs"
|
|
|
| Back to top |
|
|
Juippisi
Developer
Joined: 30 Sep 2005
Posts: 748
Location: /home
|
| Posted: Sat Nov 02, 2024 6:41 am Post subject: |
|
|
| 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. |
|
| Back to top |
|
|
logrusx
Advocate
Joined: 22 Feb 2018
Posts: 2374
|
| Posted: Sat Nov 02, 2024 8:12 am Post subject: |
|
|
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 |
|
| Back to top |
|
|
|
Portage & Programming
