Firefox build fails

BS86 commented

2023-12-17 13:41:24 +01:00

I tried building Firefox on my own (with v4 and -03 optimized build) but it failed, too. It always got killed by OOM in the link phase (ld-lld using crazy amounts of RAM - 32GB are not enough)
Applying the "fix" from here lead to a working build:
https://bbs.archlinux.org/viewtopic.php?id=290946

Change:
ac_add_options --enable-lto=cross,full
to
ac_add_options --enable-lto=cross

not sure if that is also the case and fix for the build fails here

I tried building Firefox on my own (with v4 and -03 optimized build) but it failed, too. It always got killed by OOM in the link phase (`ld-lld` using crazy amounts of RAM - 32GB are not enough) Applying the "fix" from here lead to a working build: https://bbs.archlinux.org/viewtopic.php?id=290946 Change: `ac_add_options --enable-lto=cross,full` to `ac_add_options --enable-lto=cross` not sure if that is also the case and fix for the build fails here

firefox.patch

432 B

anonfunc commented

2023-12-19 00:18:04 +01:00

Owner

I am pretty certain our ff build is not oom reaped. It takes about 56gig to build currently, and we have that available.

anonfunc added the

build-failure

label 2023-12-19 00:18:19 +01:00

anonfunc commented

2023-12-20 05:04:09 +01:00

Owner

Upstream llvm issue: https://github.com/llvm/llvm-project/issues/68929

Seems like the fix already made it to main, but is not released yet.

Upstream `llvm` issue: https://github.com/llvm/llvm-project/issues/68929 Seems like the fix already made it to main, but is not released yet.

👍 1

anonfunc added the

blocked upstream

label 2023-12-20 05:04:15 +01:00

BS86 commented

2023-12-23 18:37:13 +01:00

Author

might be a long wait then - seeing how Arch waits about half a year until releasing new clang/llvm versions - but on the other hand, that might also make it possible that the fix itself makes it into the next version that is released on Arch (if it is included in another 17.x release - if it is only released with 18.x, we won't see it for another year at least xD)

BS86 commented

2024-02-21 17:55:04 +01:00

Author

well, llvm/clang 18 is already in RC state and Arch didn't even roll out llvm/clang 17 yet xD
let's see when this is fixed and coming to Arch ...

well, llvm/clang 18 is already in RC state and Arch didn't even roll out llvm/clang 17 yet xD let's see when this is fixed and coming to Arch ...

😆 1

Firefox build fails #222