Can you post some details as to where / how it aborts?
Search Criteria
Package Details: librewolf 1:139.0.1_1-1
Package Actions
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: | MPL-2.0 |
Submitter: | lsf |
Maintainer: | lsf |
Last Packager: | lsf |
Votes: | 175 |
Popularity: | 8.41 |
First Submitted: | 2019-06-14 18:41 (UTC) |
Last Updated: | 2025-05-30 11:41 (UTC) |
Dependencies (62)
- alsa-lib
- at-spi2-core (at-spi2-core-gitAUR)
- bash (bash-devel-gitAUR, bash-gitAUR)
- cairo (cairo-gitAUR)
- dbus (dbus-gitAUR, dbus-selinuxAUR)
- ffmpeg (ffmpeg-nvcodec-11-1-gitAUR, ffmpeg-cudaAUR, ffmpeg-ffplayoutAUR, ffmpeg-decklinkAUR, ffmpeg-amd-fullAUR, ffmpeg-fullAUR, ffmpeg-headlessAUR, ffmpeg-libfdk_aacAUR, ffmpeg-amd-full-gitAUR, ffmpeg-full-gitAUR, ffmpeg-gitAUR, ffmpeg-obsAUR)
- fontconfig (fontconfig-gitAUR, fontconfig-ubuntuAUR)
- freetype2 (freetype2-macosAUR, freetype2-qdoledAUR, freetype2-gitAUR, freetype2-qdoled-aw3225qfAUR)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc-libs-snapshotAUR)
- gdk-pixbuf2 (gdk-pixbuf2-gitAUR)
- glib2 (glib2-gitAUR, glib2-selinuxAUR, glib2-patched-thumbnailerAUR)
- glibc (glibc-gitAUR, glibc-linux4AUR, glibc-eacAUR)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-classicAUR, gtk3-classic-xfceAUR)
- hicolor-icon-theme (hicolor-icon-theme-gitAUR)
- libpulse (pulseaudio-dummyAUR, libpulse-gitAUR)
- libx11 (libx11-gitAUR)
- libxcb (libxcb-gitAUR)
- libxcomposite
- libxdamage
- libxext (libxext-gitAUR)
- Show 42 more dependencies...
Required by (32)
- edge-frfox (optional)
- ff2mpv-go-git (optional)
- ff2mpv-rust (optional)
- firefox-gnome-theme (optional)
- librewolf-comment-out-cfg-hook
- librewolf-extension-bitwarden-bin
- librewolf-extension-bitwarden-git (optional)
- librewolf-extension-darkreader
- librewolf-extension-darkreader-bin
- librewolf-extension-foxyproxy
- librewolf-extension-gnome-shell-integration
- librewolf-extension-greasemonkey
- librewolf-extension-kagisearch-bin
- librewolf-extension-localcdn-bin
- librewolf-extension-plasma-integration
- librewolf-extension-return-youtube-dislike-bin
- librewolf-extension-reverse-image-search
- librewolf-extension-synclair-bin
- librewolf-extension-tridactyl-bin
- librewolf-extension-ublock-origin-bin
- librewolf-extension-uget-integration-bin
- librewolf-extension-user-agent-switcher
- librewolf-extension-vimiumc-bin
- librewolf-extension-xdman8-browser-monitor-bin
- librewolf-firefox-shim
- librewolf-gnome-search-provider
- librewolf-noscript
- librewolf-vencord
- librewolf-vencord-bin
- librewolf-vencord-git
- profile-sync-daemon-librewolf (optional)
- uget-integrator-libreworlf (optional)
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 27 28 29 30 31 32 33 34 Next › Last »
lsf commented on 2021-01-31 10:24 (UTC)
therealOri commented on 2021-01-31 03:48 (UTC)
So far it never manages to download from the AUR. It always takes forever to build then aborts.. :\
Note, I am on Manjaro Linux. Arch Based so idk why it wouldn't work.
lsf commented on 2021-01-27 12:36 (UTC)
Yeah, sounds like a memory issue. I have 16GB and this happens sometimes when compiling locally as well.
You could try running it on fewer cores by uncommenting # mk_add_options MOZ_MAKE_FLAGS="-j4"
in the PKGBUILD and setting it to something like half the amount of your physical cores or lower. This will obviously make things take quite a bit longer but might also use less RAM.
Another things worth trying might be to add export LDFLAGS+=" -Wl,--no-keep-memory"
to the PKGBUILD (at somewhere around line 81). This is currently only used for the aarch64 builds, but should also lead to the linking process using less memory.
lahwaacz commented on 2021-01-27 11:38 (UTC)
@saloniamatteo: that can happen e.g. if you don't have enough RAM.
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).