ALHP/ALHP.GO
6
40
Fork 10
Code Issues 34 Pull Requests Projects Releases Wiki Activity

Firefox build fails #222

New Issue
Open
opened 2023-12-17 13:41:24 +01:00 by BS86 · 9 comments
BS86 commented 2023-12-17 13:41:24 +01:00
Copy Link

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
Copy Link

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

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
Copy Link

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
Copy Link

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)

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
Copy Link

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
anonfunc commented 2024-07-06 13:23:04 +02:00
Owner
Copy Link

And it seems we run into the next llvm bug with the new version. 🫥

Guess it will be fixed with llvm 19.

And it seems we run into the [next llvm bug](https://github.com/llvm/llvm-project/issues/87894) with the new version. 🫥 Guess it will be fixed with llvm 19.
😆 1
BS86 commented 2024-07-06 15:43:40 +02:00
Author
Copy Link

at least Arch also sees the problem of their ultra late llvm/clang updates:
https://gitlab.archlinux.org/archlinux/packaging/packages/llvm/-/issues/3

at least Arch also sees the problem of their ultra late llvm/clang updates: https://gitlab.archlinux.org/archlinux/packaging/packages/llvm/-/issues/3
👍 2
BS86 commented 2025-01-12 20:03:19 +01:00
Author
Copy Link

@anonfunc llvm/clang 19 seems to finally fix the firefox build, at least I could now build it in a clean chroot with v4 optimizations.

@anonfunc llvm/clang 19 seems to finally fix the firefox build, at least I could now build it in a clean chroot with v4 optimizations.
❤️ 1
anonfunc commented 2025-01-12 23:58:35 +01:00
Owner
Copy Link

@BS86 I'll trigger the rebuilds.

@BS86 I'll trigger the rebuilds.
BS86 commented 2025-01-13 18:54:12 +01:00
Author
Copy Link

sorry false alarm. Just realized that something undid my changes to the build scripts in /usr/share/devtools/makepkg.conf.d without generating pacnew's or pacsave's -.-

With v4 optimizations it still fails, this time with:

12:01.19    Compiling glean v62.0.0
12:01.24 warning: Unified_cpp_gfx_thebes1.cpp: function control flow change detected (hash mismatch) _ZN17gfxGraphiteShaper8ShutdownEv Hash = 742261418966908927 up to 10 count discarded [-Wbackend-plugin]
12:01.88    Compiling minidump-analyzer v0.1.0 (/build/firefox/src/firefox-134.0/toolkit/crashreporter/minidump-analyzer)
12:02.86 1 warning generated.
12:03.14    Compiling mozilla-central-workspace-hack v0.1.0 (/build/firefox/src/firefox-134.0/build/workspace-hack)
12:44.88     Finished `release` profile [optimized] target(s) in 1m 04s
12:45.10 toolkit/crashreporter/client/app/crashreporter
12:45.11 make[2]: *** [/build/firefox/src/firefox-134.0/config/recurse.mk:34: compile] Error 2
12:45.11 make[1]: *** [/build/firefox/src/firefox-134.0/config/rules.mk:359: default] Error 2
12:45.11 make: *** [client.mk:60: build] Error 2
12:45.21 W 150 compiler warnings present.
 Config object not found by mach.
sorry false alarm. Just realized that something undid my changes to the build scripts in /usr/share/devtools/makepkg.conf.d without generating pacnew's or pacsave's -.- With v4 optimizations it still fails, this time with: ``` 12:01.19 Compiling glean v62.0.0 12:01.24 warning: Unified_cpp_gfx_thebes1.cpp: function control flow change detected (hash mismatch) _ZN17gfxGraphiteShaper8ShutdownEv Hash = 742261418966908927 up to 10 count discarded [-Wbackend-plugin] 12:01.88 Compiling minidump-analyzer v0.1.0 (/build/firefox/src/firefox-134.0/toolkit/crashreporter/minidump-analyzer) 12:02.86 1 warning generated. 12:03.14 Compiling mozilla-central-workspace-hack v0.1.0 (/build/firefox/src/firefox-134.0/build/workspace-hack) 12:44.88 Finished `release` profile [optimized] target(s) in 1m 04s 12:45.10 toolkit/crashreporter/client/app/crashreporter 12:45.11 make[2]: *** [/build/firefox/src/firefox-134.0/config/recurse.mk:34: compile] Error 2 12:45.11 make[1]: *** [/build/firefox/src/firefox-134.0/config/rules.mk:359: default] Error 2 12:45.11 make: *** [client.mk:60: build] Error 2 12:45.21 W 150 compiler warnings present. Config object not found by mach. ```
👍 1
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
blocked upstream
bug
Something is not working
build-failure
package build fails
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
informational
Provides information about something
invalid
Something is wrong
invalid/corrupt package
Package needs to be rebuild
packaging issue
priority: high
High priority
question
More information is needed
support
wontfix
This won't be fixed
No Label
blocked upstream
build-failure
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
anonfunc
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ALHP/ALHP.GO#222
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?