@Ningen correct, compilation says this: (signal: 9, SIGKILL: kill)
I don't know if you can successfully build Firefox variants with less than 16 GB of RAM nowadays.
Maybe it's a common question and you can ask upstream.
Git Clone URL: | https://aur.archlinux.org/icecat.git (read-only, click to copy) |
---|---|
Package Base: | icecat |
Description: | GNU version of the Firefox ESR browser |
Upstream URL: | https://git.savannah.gnu.org/cgit/gnuzilla.git |
Keywords: | browser esr gnuzilla web |
Licenses: | MPL-2.0 |
Submitter: | None |
Maintainer: | figue (xiota) |
Last Packager: | xiota |
Votes: | 251 |
Popularity: | 0.87 |
First Submitted: | 2007-12-09 10:12 (UTC) |
Last Updated: | 2025-07-11 02:08 (UTC) |
« First ‹ Previous 1 .. 10 11 12 13 14 15 16 17 18 19 20 .. 88 Next › Last »
@Ningen correct, compilation says this: (signal: 9, SIGKILL: kill)
I don't know if you can successfully build Firefox variants with less than 16 GB of RAM nowadays.
Maybe it's a common question and you can ask upstream.
@figue I uploaded text output here https://files.catbox.moe/wdc58y.log
Sorry I have to upload the textfile since I can't copy to clipboard, don't want to recompile my vim with clipboard stuff... I truncated it to the area of the error, the rest of the log.
Additionally, yes I can see in journalctl the kernel ran out of memory so it killed a process... which was probably why compile failed.
Is there a way to make the compile process not take so much ram? How is it possible that 8GB + 4GiB ram is not enough?
@Ningen paste full output somewhere and I will review, but sometimes is by low memory.
Also you can use archlinuxcn repo, which has IceCat included.
@figue Same issue, it will fail compiling GKrust.
@figue 8GB ram + 4GiB swap space (swapfile), I will try -e anyway and let you know the outcome.
@Ningen how many RAM do you have? Try to relaunch the build with "makepkg -e" and see if the compilation success.
GKrust has a compilation error in the compiling process. Related: https://bugs.archlinux.org/task/72085
@figue Thank you for quick guidance! It's still bugged, but now I can see some error messages in the terminal: When I click at the noScript addon icon: JavaScript error: resource://gre/modules/ExtensionContent.jsm, line 567: TypeError: PrecompiledScript.executeInGlobal: Argument 1 is not an object.
@pepesafestemail try another GTK theme:
env GTK_THEME=Adwaita icecat
@figue I can't figure out what could be the problem. As I mentioned with the 60.7 binary version I don't have this problem. I feel like my knowledge is limited to solve this puzzle by myself, could you give me some tips what could cause such problems?
Pinned Comments
xiota commented on 2024-02-26 07:32 (UTC) (edited on 2025-07-11 02:14 (UTC) by xiota)
Description of build options and defaults. See PKGBUILD for current list.
_build_save_source
(true) – save tarball of patched sources_build_repatch
(false) – discard previously saved tarball_build_pgo
(true) – enable profile guided optimization; ~20% better benchmarks, 3× build time_build_pgo_reuse
(try) – reuse previously generated profile_build_pgo_xvfb
(true) – use Xvfb for profiling, otherwise, use xwayland-run_build_lto
(false) – whether to use LTO; disabling may prevent spurious crashes_build_system_libs
(true) – use system libraries_build_limit_cores
(false) – limit parallelization based on memory and core availabilityExamples of use:
_build_pgo=false makepkg -Csr
extra-x86_64-build -- -- _build_limit_cores=true
_build_pgo_xvfb=false yay icecat
(usage with AUR helpers may vary)