lto-wrapper: fatal error: /usr/bin/x86_64-pc-linux-gnu-g++ returned 1 exit status Build output attached.
Created attachment 617130 [details] emerge --info
Created attachment 617132 [details] Build log
Created attachment 617134 [details] emerge -pqv
Created attachment 617136 [details] Build environment
I had a similar issue (I found this bz while looking for a solution). The sandbox showed debug allocation errors but I run with overcommit_memory=1 in the kernel so memory can't run out, the only thing that can happen is that the sandbox gets killed by the OOM killer and that didn't happen. So I tried also to upgrade to sandbox 2.18 but it's not enough. After a few tries of 'MAKEOPTS="-j1" emerge -1 firefox' it built ok. Your log shows a task getting killed, not just userland allocation errors from the sandbox so it's more likely MAKEOPTS=-j1 helps. Overall it doesn't seem a reproducible failure but sandbox upgrade and MAKEOPTS=j1 seem to help.
Could you please share system information? Wondering how much memory you have.
The system is very old and quite constrained. # uname -a Linux brick 5.5.11-pentoo #1 SMP Thu Mar 26 22:09:26 EDT 2020 i686 Intel(R) Pentium(R) 4 CPU 2.20GHz GenuineIntel GNU/Linux Omitting a lot of details, the system is: Manufacturer: "Dell Computer Corporation" Product: "Dimension 2400" Total RAM capacity is 4 GB. I did not previously use the overcommit_memory tweak you suggested, but tried that last night. I already had MAKEOPTS="-j1" configured. I upgraded sandbox to 2.18 and then tried again to emerge Firefox, and failed again with the 'out of memory' error. Total swap space configured at the moment: brick ~ # swapon -s Filename Type Size Used Priority /dev/sda3 partition 7340028 128512 -2 /swapfile file 3145724 0 -3 It may be time to accept defeat with Firefox. I'm able to get Chromium to build, though I have to cheat by rashly claiming to know what I'm doing: I_KNOW_WHAT_I_AM_DOING=1 FEATURES="-collision-detect -protect-owned" emerge --autounmask-write y --keep-going --backtrack=30 --verbose-conflicts -uDN world -vt Also this being a very old system, it takes *forever* for these things to build, so there will be delays in reporting back here. That said, for my small home network, the system is doing an OK job of running zeek and a handful of useful things, so I'm not quite ready to toss it aside.
Can you please retry with latest >=www-client/firefox-78.3.1 and tell us if you are still experiencing this problem?
(In reply to Thomas Deutschmann from comment #8) > Can you please retry with latest >=www-client/firefox-78.3.1 and tell us if > you are still experiencing this problem? The problem no longer exists. I have 78.3.1 successfully installed.
Thank you for the follow up!
