| 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.75 |
| First Submitted: | 2007-12-09 10:12 (UTC) |
| Last Updated: | 2024-11-30 19:41 (UTC) |
Tried to build on my laptop with ~30GB of ram and it just failed before compiling toolkit/library/build/libxul.so which were one of the last few components, very annoying. Retrying build with ~50GB ram on a more powerful computer.
@texer22 In the PKGBUILD on line 85 change if [ "${_only-compile}q" = q ]; then to if [ 1 ]; then. I would also not recommend building until someone figures out whether the PGO build really requires a lot of ram or there is an issue somewhere
Cannot build...
==> Starting build()...
/home/user/.cache/paru/clone/icecat/PKGBUILD: line 195: cd: gnuzilla-dbe6da400cf4f28e5e893d0acb5022e23cf3afcf/output/icecat-115.7.0: No such file or directory
==> ERROR: A failure occurred in build().
Aborting...
@figue You're right it seems to be much more resource intensive than before PGO, I can't compile natively with 8GB ram and 8GiB swap space. That said, perhaps the only option is to make a very large swap file and use that temporarily for compile time such as https://files.catbox.moe/56bafh.sh I included this as the first line under prepare() before cd gnuzilla-${_commit}, running it now and will let you know how it goes...
@xiota thank you for your PKGBUILD. I've merged a few things.
@Ningen 115.7.0 pushed
@figue Ohh I see. Would you mind pushing the PKGBUILD for 115.7.0 anyway and I will see if I can compile?
I have currently tried your PKGBUILD here https://gist.github.com/figue/4a407a15e0eedfc2e88eb5de431b69f7 but there are weird things going on outside of your mentioned issue, so I would like to just try to build the regular way if you can push the updates and investigate
@Ningen I have the PKGBUILD ready since last week but the PGO build is not working in my HP laptop, it always end in OOM kill. I was trying this week to use distcc between 3 nodes, but I was unable to build (it says something about target error), so I think I'll quit trying to maintain this package anymore.
If I can't build it properly, it doesn't have any sense to continue.
Please, contact to me by private to anyone interested for transferring this package.
Thank you for understanding.
@figue Upstream is 115.7.0 now, does the 'flag package out of date' option on this page not notify you? Is it better if we comment for you to be notified?
I was also getting stuck at the same place. The problem is the browser extensions disable javascript, which is needed for the profiling. Even if javascript wasn't needed, the extensions would still need to be disabled to profile the javascript engine.
Pinned Comments
xiota commented on 2024-02-26 07:32 (UTC) (edited on 2024-08-08 03:44 (UTC) by xiota)
PKGBUILD has been updated. Major changes:
Notes:
_build_pgo_xvfb=false. This will usexwayland-runfor profiling._build_pgo=false.mk_add_options MOZ_PARALLEL_BUILD=___around line 300. Pick a value less than number of cores and free RAM in GB. For example, on a system with 8 cores, 64GB total RAM, but only 6 GB free, the value should be set to 4 or 5.libxul.so. Leave a comment if you have a potential solution.Having problems? Please provide details: processor make and model, number of cores,
free -m, full log in pastebin, whether using AUR helper/makepkg/clean chroot, etc.