| Git Clone URL: | https://aur.archlinux.org/librewolf.git (read-only, click to copy) |
|---|---|
| Package Base: | librewolf |
| Description: | Community-maintained fork of Firefox, focused on privacy, security and freedom. |
| Upstream URL: | https://librewolf.net/ |
| Keywords: | browser web |
| Licenses: | GPL, MPL, LGPL |
| Submitter: | lsf |
| Maintainer: | lsf |
| Last Packager: | lsf |
| Votes: | 147 |
| Popularity: | 3.73 |
| First Submitted: | 2019-06-14 18:41 (UTC) |
| Last Updated: | 2025-01-26 21:06 (UTC) |
~~And now, for some reason I don't understand, what I said still works but it doesn't work inside of a chroot (with Paru) for some reason I can't understand~~
One would think the opposite would make it build but no, somehow
EDIT: Seems it was because python-pip is a dependency now
1) options+=(!lto) - this makes sure that any user's global lto pacman/makepkg flag is overriden to stay off; this will throw errors if not done and the global is on
2) add ac_add_options --enable-linker=lld before the "instrumental build"; this is what was preventing compilation for me in the first place
3) uncomment:
CFLAGS="${CFLAGS/-fno-plt/}"
CXXFLAGS="${CXXFLAGS/-fno-plt/}"
because the builds will throw errors if they're not uncommented
@Neko-san: could you sum up the changes you need in PKGBUILD again?
There are a few things you mentioned that wouldn't necessarily make sense to "globally" change in the PKGBUILD for everyone, but maybe I've missed something / maybe there's a way to conditionally add some of your requirements or something like that :)
Also, am I the only one who has Librewolf crashes when opening the settings menu?
@lsf not an issue with that but you didn't implement the other PKGBUILD things I mentioned that were necessary :/
For 94.0 a downgrade shouldn't be required anymore – do you still have that issue with the most recent release?
I temporary downgraded my clang, llvm, lld, compiler-rt to version 12.0.0, and my rust to 1.55 with the command
sudo pacman -U https://archive.archlinux.org/packages/r/rust/rust-1%3A1.55.0-1-x86_64.pkg.tar.zst https://archive.archlinux.org/packages/c/clang/clang-12.0.0-1-x86_64.pkg.tar.zst https://archive.archlinux.org/packages/c/compiler-rt/compiler-rt-12.0.0-1-x86_64.pkg.tar.zst https://archive.archlinux.org/packages/l/llvm/llvm-12.0.0-2-x86_64.pkg.tar.zst https://archive.archlinux.org/packages/l/lld/lld-12.0.0-1-x86_64.pkg.tar.zst
I was able to successfully compile librewolf with these packages temp downgraded. No need to deal with a chroot.
Ah, okay; I might just wait for the next release to start doing it in the chroot - I have the portable instance of rustup installed on my system (though I've not used it much) and managed to get the right toolchain and I managed to compile it with the PKGBUILD changes
Thanks for testing and telling me that the compiler flags were fine; I have no idea why it decided to assume what linker to use for the instrumented build for you guys without it being declared before then, or why one of the default makepkg.conf flags wasn't throwing LLVM errors for you guys, but that went over my head and I might have not thought of it if you hadn't told me
When directly using makechrootpkg, you can just install specific packages for a build by adding -I /path/to/some.pkg.tar.zst. I'm not sure if you can also do that with the paru chroot option (seems like you could install specific packages before running a build using --chrootctl and -i, but I've never tried it – maybe it will be thwarted by paru updating things?
…and if all else failed, that should be fixed with upcoming firefox/librewolf releases – those usually get configured for the newer/current rust versions ^^
How do I do that in the chroot?
Pinned Comments
lsf commented on 2025-01-01 21:28 (UTC)
Please refrain from abusing the flagging of a package as out of date for build issues. This is not what it is supposed to be used for.
I automatically get notified of comments to this package. I do not need to be notified of whatever build problems occur (whether they are an individual's problems or the actual package's problems) twice, and not via flagging it out of date.
Issues with this package can also be reported at https://codeberg.org/librewolf/issues/issues (as it is also maintained there, at https://codeberg.org/librewolf/arch, too).