Arch Linux User Repository

Alas, gcc5 has now been dropped from the official repos. However, you can still get the old package here: https://archive.archlinux.org/packages/g/gcc5/

Note that that package is out of date, and the final version of gcc5 (5.5) is available on the AUR here: https://aur.archlinux.org/packages/gcc5/ it is unlikely that you will need to build this package more than once, since it's no longer receiving updates.

Also worth noting is that palemoon upstream /still/ reccomend the long defunct gcc49 over any modern compiler, if you want to use that you will need to modify the mozconfig file's CC and CXX flags as well as the PKGBUILD's makedepends array and md5sums.

I was able to compile palemoon 27.8.1 with gcc4.9 (built using the AUR PKGBUILD) and this patch:

http://dpaste.com/3V76NDX

@WorMzy I'm not running anything else and I'm not compiling in a tmpfs either nor do I have a swap parition. But it worked a few weeks before.

Upstream recommends having more than 4GB of RAM, so you should have more than enough. Are you running any other memory-intensive programs while you're compiling? Are you compiling on a tmpfs? Do you have a swap file/partition? What is your swappiness set to? These are the sorts of things that you should answer in a forum support thread if you need help with this.

https://developer.palemoon.org/Developer_Guide:Build_Instructions/Pale_Moon/Linux

This uses all my 8gb of RAM resulting in a systemfreeze. Is this normal?

@ray731: If you're happy with untracked software floating around your system, sure. The advantage of an AUR package is that, once built, you can install/remove the package with pacman. If that isn't of interest to you, then by all means use upstream's tarballs.

@WorMzy: yes, but palemoon-bin should be also installed. While the tarball should be just extracted to run palemoon. Isn't it simpler?

@ray731: yes, see the palemoon-bin package.

As indicated on https://www.palemoon.org , you can also download Pale Moon for Linux as a bzipped tarball that can be extracted and run from any location on your system.

@jerome2016: I've had another look at the strace output, and I noticed this line: openat(AT_FDCWD, "/usr/lib/libicuuc.so.59", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

I don't get that message when I run strace palemoon, so I have to assume something on your system is trying to pull it in. The icu package was updated in mid-November, so is your system completely up-to-date? (including any AUR packages which may need a rebuild due to the icu version bump).

Use lddd or findbrokenpkgs to identify any packages that might need a rebuild. Note that you will get false positives with either tool, so I prefer to run the former, then run

for pkg in $(pacman -Qqm); do
grep $pkg /tmp/lddd-script.*/possible-rebuilds.txt
done

to get a list of foreign packages which may need rebuilding.

@jerome2016: I haven't been able to reproduce this so far, but assuming you are the same user who created this topic, I recommend rebuilding with gcc5, instead of using gcc6. Aside from the glibc/C99_MATH bug below, I have never had any problems with the former.