Package Details: icecat 115.17.0-1

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: 250
Popularity: 0.44
First Submitted: 2007-12-09 10:12 (UTC)
Last Updated: 2024-11-04 00:48 (UTC)

Dependencies (51)

Sources (10)

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:

  • Downloads Firefox ESR and localization using the source array. Files are saved for reuse.
  • Saves freshly patched IceCat sources in a tarball for reuse.
  • Saves the PGO profile for reuse.

Notes:

  • Currently requires clang/llvm 17, which has to be built from AUR.
  • Wayland users, consider setting _build_pgo_xvfb=false. This will use xwayland-run for profiling.
  • PGO should work now, but if it doesn't and you're willing to go without, try _build_pgo=false.
  • Running out of RAM? Try adding 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.
    • If a few people can confirm this is helpful, I will consider adding it as an additional option.
    • Main resource hog seems to be linking 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.

Latest Comments

« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 15 16 17 .. 85 Next › Last »

cysp74 commented on 2021-11-03 14:04 (UTC)

@figue:

My second attempt placed in absolutely clean directory, started by "git clone https://aur.archlinux.org/icecat.git", blabla and failed.

But I pulled through after nth try after installation of llvm stuffs + rust from testing repo: clang-13.0.0-2 compiler-rt-13.0.0-1 lib32-llvm-libs-13.0.0-1 llvm-13.0.0-2 llvm-libs-13.0.0-2 rust-1:1.56.1-1

Pretty weird, (ofcoz I forgot to include the most important line into my previous comment):

0:01.85 DEBUG: Executing: /usr/bin/clang -std=gnu99 -fuse-ld=lld -Wl,--version 0:01.85 ERROR: Could not use lld as linker

So, I'll be vigilant and make new test once those packages above will be pushed into regular repo.

figue commented on 2021-11-02 22:47 (UTC)

@cysp74 can you build in a clean chroot?

cysp74 commented on 2021-11-02 12:31 (UTC)

Heya,

Building attempt of 91.3.0-1 stopped with error below:

Exception: Process executed with non-0 exit code 1: ['/usr/bin/python3', '/xxx/yyy/icecat/src/gnuzilla-32631cac00953abbac61dc7ab1a0eafbdd59b53a/output/icecat-91.3.0/configure.py']

File "/xxx/yyy/icecat/src/gnuzilla-32631cac00953abbac61dc7ab1a0eafbdd59b53a/output/icecat-91.3.0/python/mozbuild/mozbuild/build_commands.py", line 159, in build return driver.build( File "/xxx/yyy/icecat/src/gnuzilla-32631cac00953abbac61dc7ab1a0eafbdd59b53a/output/icecat-91.3.0/python/mozbuild/mozbuild/controller/building.py", line 1144, in build config_rc = self.configure( File "/xxx/yyy/icecat/src/gnuzilla-32631cac00953abbac61dc7ab1a0eafbdd59b53a/output/icecat-91.3.0/python/mozbuild/mozbuild/controller/building.py", line 1528, in configure status = self._run_command_in_objdir( File "/xxx/yyy/icecat/src/gnuzilla-32631cac00953abbac61dc7ab1a0eafbdd59b53a/output/icecat-91.3.0/python/mozbuild/mozbuild/base.py", line 845, in _run_command_in_objdir return self.run_process(cwd=self.topobjdir, **args) File "/xxx/yyy/icecat/src/gnuzilla-32631cac00953abbac61dc7ab1a0eafbdd59b53a/output/icecat-91.3.0/python/mach/mach/mixin/process.py", line 176, in run_process raise Exception( ==> ERROR: A failure occurred in build(). Aborting... ==> Removing installed dependencies...

figue commented on 2021-10-20 21:24 (UTC)

@dale6998 something in your $PATH seems not "correct". Can you check it?

@Ningen yeah, I saw it. The orphan request only is accepted if a maintainer is not active or is doing something that is against Arch rules. In this case, as you said, the only way is some TU take care of it or become TU. Unfortunately I don't know any other TU who can sponsor me.

The right way I think is go to IRC or Arch's forums and request it. Feel free to promote it if you like.

dale6998 commented on 2021-10-20 18:58 (UTC)

this fails to build with this message:

find: The current directory is included in the PATH environment variable, which is insecure in combination with the -execdir action of find. Please remove the current directory from your $PATH (that is, remove ".", doubled colons, or leading or trailing colons) ==> ERROR: A failure occurred in prepare(). Aborting... :: Unable to build icecat - makepkg exited with code: 4

Ningen commented on 2021-10-20 00:27 (UTC)

@figue As per the email you got CC'd in, there are only two ways for the package to be put in the community repo, either a current TU adopts it (Do you know any?) or you become a TU yourself.

Would you be willing to become a TU?

figue commented on 2021-10-16 22:49 (UTC) (edited on 2021-10-16 22:49 (UTC) by figue)

@Ningen hahaha no, I didn't thought of becoming a TU for now. But you can request to TU community to move this package to community repo. It will be great indeed.

Ningen commented on 2021-10-16 22:26 (UTC)

@figue I actually have had the thought for a long time why this package is not in community repo..., have you thought of becoming a TU for ArchLinux? I think you will be great. This is a very important package that should be available to all without the hassle of compiling yourself every time. We should really get this in the community repo, then pacman can install the precompiled binary each time instead of doing this long 2 hours compile process!

figue commented on 2021-10-16 22:05 (UTC)

@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.

Ningen commented on 2021-10-16 21:56 (UTC) (edited on 2021-10-16 21:59 (UTC) by Ningen)

@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?

« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 15 16 17 .. 85 Next › Last »