Package Details: palemoon

Git Clone URL: (read-only)
Package Base: palemoon
Description: Open source web browser based on Firefox focusing on efficiency.
Upstream URL:
Keywords: browser goanna web
Licenses: GPL, MPL, LGPL
Submitter: artiom
Maintainer: WorMzy
Last Packager: WorMzy
Votes: 121
Popularity: 1.783259
First Submitted: 2014-06-05 10:54
Last Updated: 2019-07-04 22:45

Latest Comments

« First ‹ Previous ... 3 4 5 6 7 8 9 10 11 12 13 ... Next › Last »

wolf commented on 2017-10-29 00:36

Cannot build with gcc5 from AUR, any help?

12:35.30 In file included from /build/palemoon/src/pmbuild/dom/canvas/Unified_cpp_dom_canvas0.cpp:11:0:
12:35.30 Warning: -Wunknown-pragmas in /build/palemoon/src/Pale-Moon/dom/canvas/CanvasRenderingContext2D.cpp: ignoring #pragma omp parallel
12:35.30 /build/palemoon/src/Pale-Moon/dom/canvas/CanvasRenderingContext2D.cpp:1635:0: warning: ignoring #pragma omp parallel [-Wunknown-pragmas]
12:35.30 #pragma omp parallel for
12:35.30 ^
12:36.46 libembedding_components_printingui_ipc.a.desc
12:36.55 nsAppRunner.o
12:36.58 nsEmbedFunctions.o
12:38.41 UnifiedProtocols9.o
12:42.29 /build/palemoon/src/Pale-Moon/dom/canvas/CanvasRenderingContext2D.cpp: In function ‘bool mozilla::dom::ValidateRect(double&, double&, double&, double&)’:
12:42.29 /build/palemoon/src/Pale-Moon/dom/canvas/CanvasRenderingContext2D.cpp:2420:8: error: ‘__builtin_isfinite’ is not a member of ‘std’
12:42.29 if (!std::isfinite((float)aX) | !std::isfinite((float)aY) |
12:42.29 ^

WorMzy commented on 2017-10-25 08:04

Alas, gcc5 has now been dropped from the official repos. However, you can still get the old package here:

Note that that package is out of date, and the final version of gcc5 (5.5) is available on the AUR here: 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.

WorMzy commented on 2017-10-03 08:24

Builds fine here. All I can recommend is that you ditch yaourt and build in a clean chroot.

simona commented on 2017-10-02 14:13

/tmp/yaourt-tmp-simona/aur-palemoon/src/pmbuild/dist/bin/ riferimento non definito a "icudt58_dat"
8:04.22 collect2: error: ld returned 1 exit status

WorMzy commented on 2017-09-27 15:00

m4 is part of base-devel, which you should have installed if you want to build AUR packages:

sekret commented on 2017-09-27 14:41

@fft, are you sure? I always build in a clean chroot and the package builds fine here, so there shouldn't be a missing dependency.

Could you post the error?

fft commented on 2017-09-27 14:38

WorMzy, thank you for packaging. It seems, that need to add m4 to makedepends.

ondoho commented on 2017-09-20 17:42

nope, it didn't fix the issue at all.

tried running palemoon from the terminal but there was no ouput at all.

can anyone at least confirm this?

btw, sorry forgot to mention, kernel is 4.9.50-1-lts x86_64, gpu is Intel HD Graphics 530

ondoho commented on 2017-09-18 06:15

after a system update, palemoon started glitching - when i opened another window on top of palemoon, sometimes even only when i switched desktops, palemoon's window would become blank, and palemoon unresponsive until i kill it.
something to do with gpu accel no doubt.
this went on for a couple of weeks and across at least one kernel upgrade - until i simply re-installed (recompiled) palemoon, now it's fine again.

has this happened before?
is there any way to deal with that through package management?

WorMzy commented on 2017-08-30 15:08

> enough memory/disk space seem to be available

Your output suggests otherwise. You mention disk space, but it looks like you're building in /tmp which, on Arch, is a tmpfs by default. When building on tmpfs, you need to have enough free memory to handle the git repository, the checked out source code, the actual build process (including temporary files and compiler/linker processes), and the packaging. When the build fails, the compiler/linker processes get reaped and the memory they were using gets freed, so checking the free space of /tmp or the memory usage of the system after the build fails is not actually indicitive of the situation during the build.

How big is your /tmp? Anything smaller than 5GB is unlikely to result in a successful build.