| Git Clone URL: | https://aur.archlinux.org/palemoon.git (read-only, click to copy) |
|---|---|
| Package Base: | palemoon |
| Description: | Open source web browser based on Firefox focusing on efficiency. |
| Upstream URL: | https://www.palemoon.org/ |
| Keywords: | browser goanna web |
| Licenses: | MPL-2.0 |
| Submitter: | artiom |
| Maintainer: | WorMzy |
| Last Packager: | WorMzy |
| Votes: | 141 |
| Popularity: | 0.063030 |
| First Submitted: | 2014-06-05 10:54 (UTC) |
| Last Updated: | 2024-12-05 10:09 (UTC) |
Since last update unable to compile palemoon 28.0.0-2 anymore even with empty CFLAGS.
27:12.97 make[3]: [/tmp/yaourt-tmp-root/aur-palemoon/src/UXP/config/recurse.mk:33: compile] Error 2 27:12.97 make[2]: [/tmp/yaourt-tmp-root/aur-palemoon/src/UXP/config/rules.mk:503: default] Error 2 27:12.97 make[1]: [/tmp/yaourt-tmp-root/aur-palemoon/src/UXP/client.mk:414: realbuild] Error 2 27:12.97 make: [client.mk:170: build] Error 2
Thanks for the heads up. Checking the palemoon "building for source" dev page [1] simply says that gcc 4.9 is the minimum required version, so I guess they've actually brought their code up-to-snuff for the latest compilers. I've tested that it builds, launches, and seems to work fine, but I don't use palemoon these days, so there may be stability issues when building with gcc 8 that I'm not hitting in my testing. Please let me know if you have stability issues (preferably before you inform upstream and they chuck all their toys out of their pram because someone dared to use a modern compiler...)
[1] http://developer.palemoon.org/Developer_Guide:Build_Instructions/Pale_Moon/Linux
Have successfully built palemoon 28.0.0-1 with core/gcc 8.2.0-2 (base-devel) [installed] CFLAGS="-march=native -mtune=native -O3 -pipe -fstack-protector-strong -fno-plt" LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now" MAKEFLAGS="-j1" banned from Arch Forum, can't report there. Pls, consider to remove GCC5 dependency and may be report to upstream.
Hah, it's been in community/ before. I'm surprised to see it back now that it's EOL though. Looks like it's needed by cuda for now..
Grats gentlemen! gcc5 has now been pushed to community repo, so no need to have sexual relations with build trying to get it into your system, just install.
<hr>Мои поздравления! gcc5 теперь собирается в репозитории community, поэтому можно не ипаццо с его сборкой, а просто установить оттуда.
I was able to compile palemoon 27.8.1 with gcc4.9 (built using the AUR PKGBUILD) and this patch:
@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?
Pinned Comments
WorMzy commented on 2021-03-02 16:19 (UTC) (edited on 2022-08-03 21:12 (UTC) by WorMzy)
The following key is used to sign release commits:
40481E7B8FCF9CEC
Import it into your keyring however you want.
https://wiki.archlinux.org/index.php/GnuPG#Import_a_public_key