Package Details: palemoon 27.5.1-1

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: 110
Popularity: 3.684962
First Submitted: 2014-06-05 10:54
Last Updated: 2017-10-10 19:23

Latest Comments

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.

kzoli429 commented on 2017-08-30 14:27

Although enough memory/disk space seem to be available, building failed with:
{standard input}: Assembler messages:
2:14.21 {standard input}: Fatal error: can't close Unified_cpp_js_src4.o: No space left on device
2:14.23 In the directory /tmp/makepkg/palemoon/src/pmbuild/js/src
2:14.23 The following command failed to execute properly:
2:14.23 g++-5 -o Unified_cpp_js_src4.o -c -I../../dist/system_wrappers -include /tmp/makepkg/palemoon/src/Pale-Moon/config/gcc_hidden.h -DFFI_BUILDING -DEXPORT_JS_API -DJS_HAS_CTYPES -DDLL_PREFIX="lib" -DDLL_SUFFIX=".so" -DMOZ_GLUE_IN_PROGRAM -DAB_CD= -DNO_NSPR_10_SUPPORT -I/tmp/makepkg/palemoon/src/Pale-Moon/js/src -I. -Ictypes/libffi/include -I/tmp/makepkg/palemoon/src/Pale-Moon/intl/icu/source/common -I/tmp/makepkg/palemoon/src/Pale-Moon/intl/icu/source/i18n -I../../dist/include -I/tmp/makepkg/palemoon/src/pmbuild/dist/include/nspr -fPIC -D_FORTIFY_SOURCE=2 -O2 -DMOZILLA_CLIENT -include ../../js/src/js-confdefs.h -MD -MP -MF .deps/Unified_cpp_js_src4.o.pp -D_FORTIFY_SOURCE=2 -O2 -Wall -Wsign-compare -Wtype-limits -Wno-invalid-offsetof -Wcast-align -march=native -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -fno-rtti -ffunction-sections -fdata-sections -fno-exceptions -fno-math-errno -std=gnu++0x -pthread -pipe -DNDEBUG -DTRIMMED -g -O2 -msse2 -mfpmath=sse -fomit-frame-pointer /tmp/makepkg/palemoon/src/pmbuild/js/src/Unified_cpp_js_src4.cpp
2:14.23 make[5]: *** [/tmp/makepkg/palemoon/src/Pale-Moon/config/ Unified_cpp_js_src4.o] Error 1
2:14.24 make[4]: *** [/tmp/makepkg/palemoon/src/Pale-Moon/config/ js/src/target] Error 2
2:14.24 make[3]: *** [/tmp/makepkg/palemoon/src/Pale-Moon/config/ compile] Error 2
2:14.24 make[2]: *** [/tmp/makepkg/palemoon/src/Pale-Moon/config/ default] Error 2
2:14.24 make[1]: *** [/tmp/makepkg/palemoon/src/Pale-Moon/ realbuild] Error 2
2:14.24 make: *** [ build] Error 2
2:14.27 262 compiler warnings present.
2:15.36 Failed to parse ccache stats output: cache hit rate 0.00 %
==> ERROR: A failure occurred in build().
==> ERROR: Makepkg was unable to build palemoon.
==> Restart building palemoon ? [y/N]

WorMzy commented on 2017-08-23 20:09

Thanks for the heads up. :)

The gcc5 drop shouldn't be too much of a problem. The current gcc5 package hasn't been touched in over a year, so there's probably not much risk in users installing it from the ALA once it disappears from the repos. Unfortunately I think it's unlikely that upstream will support/recommend a modern gcc any time soon.

It doesn't look like that fix for 2.26 causes any problems for 2.25, so I'll push out a pkgrel bump adding it and the job limit change shortly.

All comments