Package Details: librewolf 133.0.3-1

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: 144
Popularity: 4.35
First Submitted: 2019-06-14 18:41 (UTC)
Last Updated: 2024-12-15 09:44 (UTC)

Sources (3)

Latest Comments

1 2 3 4 5 6 .. 28 Next › Last »

Blake_Smith commented on 2024-12-03 12:43 (UTC) (edited on 2024-12-03 12:43 (UTC) by Blake_Smith)

Hello all, I apologize for coming in with a completely unrelated issue. I have been trying to build Librewolf using the mold linker, I get these results:

3:11.52 = note: ld.lld: error: unknown argument '-fuse-ld=mold' 3:11.53 clang: error: linker command failed with exit code 1 (use -v to see invocation) 3:11.53 3:11.53 error: could not compileproc-macro2(build script) due to 1 previous error 3:12.31 make[4]: *** [/home/Blake/.cache/yay/librewolf/src/librewolf-133.0-1/config/makefiles/rust.mk:504: force-cargo-library-build] Error 101 3:12.63 make[3]: *** [/home/Blake/.cache/yay/librewolf/src/librewolf-133.0-1/config/recurse.mk:72: toolkit/library/rust/target-objects] Error 2 3:12.64 make[3]: *** Waiting for unfinished jobs.... 3:15.25 make[2]: *** [/home/Blake/.cache/yay/librewolf/src/librewolf-133.0-1/config/recurse.mk:34: compile] Error 2 3:15.25 make[1]: *** [/home/Blake/.cache/yay/librewolf/src/librewolf-133.0-1/config/rules.mk:359: default] Error 2 3:15.25 make: *** [client.mk:60: build] Error 2 3:15.45 W 0 compiler warnings present. ==> ERROR: A failure occurred in build(). Aborting... -> error making: librewolf-exit status 4 -> Failed to install the following packages. Manual intervention is required: librewolf - exit status 4

I then attempted to change the pkgbuild itself by changing the line: ac_add_options --enable-linker=mold However, it spits out this error:

2:50.12 = note: mold: fatal: -auxiliary may not be used without -shared 2:50.13 clang: error: linker command failed with exit code 1 (use -v to see invocation) 2:50.13 2:50.14 error: could not compileproc-macro2(build script) due to 1 previous error 2:50.85 make[4]: *** [/home/Blake/librewolf/src/librewolf-133.0-1/config/makefiles/rust.mk:504: force-cargo-library-build] Error 101 2:50.85 make[3]: *** [/home/Blake/librewolf/src/librewolf-133.0-1/config/recurse.mk:72: toolkit/library/rust/target-objects] Error 2 2:50.85 make[3]: *** Waiting for unfinished jobs.... 2:54.06 make[2]: *** [/home/Blake/librewolf/src/librewolf-133.0-1/config/recurse.mk:34: compile] Error 2 2:54.06 make[1]: *** [/home/Blake/librewolf/src/librewolf-133.0-1/config/rules.mk:359: default] Error 2 2:54.06 make: *** [client.mk:60: build] Error 2 2:54.26 W 0 compiler warnings present. ==> ERROR: A failure occurred in build(). Aborting... Perhaps this is merely a mold issue and not a librewolf issue? Other applications compiled just fine, however.

ducpai commented on 2024-11-26 00:17 (UTC)

importing mozillas pgp key might help people unable to install due to missing keys.

gpg --recv-key EBE41E90F6F12F6D

stormcloud19 commented on 2024-10-26 13:23 (UTC) (edited on 2024-10-26 13:24 (UTC) by stormcloud19)

Trying to build at the moment gives the following error:

0:04.34 ERROR: The libclang located at /usr/lib/libclang.so is too old (need at least 5.0). 0:04.34 Please make sure to update it or point to a newer libclang using 0:04.34 --with-libclang-path.

Installed clang:

$ clang --version clang version 18.1.8 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/bin

$ readelf -a /usr/lib/libclang.so | grep SONAME 0x000000000000000e (SONAME) Library soname: [libclang.so.18.1]

OdinVex commented on 2024-10-10 16:32 (UTC) (edited on 2024-10-11 15:38 (UTC) by OdinVex)

And we're right back to uncompilable again, just like before. Edit: Clean-building doesn't help, sometimes you have to flat out remove the entire librewolf folder from the yay cache. (~/.cache/yay/librewolf) Sometimes it'll compile, sometimes it won't.

OdinVex commented on 2024-09-13 01:57 (UTC) (edited on 2024-09-13 01:58 (UTC) by OdinVex)

@knuxyl, I was lucky enough to get 130.0-1 that worked but -2 and -3 failed, same error you have. Edit: I won't be disabling hwaccel either, so I'll wait until it's fixed. I wonder what's causing this. I noticed 130 changed the browser's DNS settings to Mozilla's Cloudflare crap instead of Off (system DNS). Mozilla's getting creepier and creepier.

knuxyl commented on 2024-09-03 16:52 (UTC) (edited on 2024-09-03 16:56 (UTC) by knuxyl) 

0:23.24 Created package: /home/knuxyl/.cache/yay/librewolf/src/librewolf-129.0.2-1/obj-x86_64-pc-linux-gnu/dist/librewolf-129.0.2-1.en-US.linux-x86_64.tar.bz2
>started SP3 server on port 8000
[Parent 241602, Main Thread] ###!!! ABORT: file resource://gre/modules/addons/XPIProvider.sys.mjs:2653
Exiting due to channel error.
Firefox exited with code -11 during profile initialization
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: librewolf-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
librewolf - exit status 4

It seems to have been built properly because librewolf-129.0.2-1.en-US.linux-x86_64.tar.bz2 is created and contains a working executable. Not sure what is going on. I'd rather wait for a fix than to force libgl to use software rendering, if that's what's even causing this error. This is on a Zen 4 desktop with 96gb ram.

account commented on 2024-08-24 18:49 (UTC) (edited on 2024-09-06 01:46 (UTC) by account) 

==> Verifying source file signatures with gpg...
    librewolf-129.0.1-1-linux-x86_64-package.tar.bz2 ... SIGNATURE NOT FOUND
FAILED
==> ERROR: One or more PGP signatures could not be verified!
aura :: Package failed to build, citing:

  makepkg failed.

aura :: Action cancelled.

To fix this, I had to use --skippgpcheck in my AUR update command.

AndyRTR commented on 2024-08-16 15:02 (UTC)

For me adding "export LIBGL_ALWAYS_SOFTWARE=true" fixed the build in a clean chroot using the official build server.

mabod commented on 2024-08-15 08:51 (UTC) (edited on 2024-08-15 08:52 (UTC) by mabod)

I had a successfull build with 

export LIBGL_ALWAYS_SOFTWARE=true
export GALLIUM_DRIVER=softpipe
makepkg

Thanks, @xiota, for mentioning GALLIUM_DRIVER!

xiota commented on 2024-08-14 21:53 (UTC) (edited on 2024-08-14 21:53 (UTC) by xiota)

I had a successful build. Those having problems can try setting MESA_LOADER_DRIVER_OVERRIDE and/or GALLIUM_DRIVER. (I don't know valid values.) Can look for other variables to try at Mesa Environment Variables.

1 2 3 4 5 6 .. 28 Next › Last »