Arch Linux User Repository

diff --git a/PKGBUILD b/PKGBUILD
index 39a928a..05d50a2 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -17,7 +17,7 @@ url="https://www.palemoon.org/"
 license=('MPL-2.0')
 depends=('gtk2' 'dbus-glib' 'desktop-file-utils' 'libxt' 'mime-types' 'alsa-lib'
          'startup-notification')
-makedepends=('python2' 'autoconf2.13' 'unzip' 'zip' 'yasm'
+makedepends=('python2' 'unzip' 'zip' 'yasm'
              'libpulse' 'git')
 optdepends=('libpulse: PulseAudio audio driver'
             'ffmpeg: various video and audio support')
@@ -38,6 +38,10 @@ prepare() {
   git submodule init
   git config submodule.platform.url "${srcdir}/UXP"
   git -c protocol.file.allow=always submodule update
+  cd platform
+  git cherry-pick -n 6cbb2c372b208902e765aa577539c018d76ba1b8
+  git cherry-pick -n e484c9d31136fc7e197bb0d686463a6555897784
+  git cherry-pick -n acb34c35dbc3452101318cbb3cccf50b1a1c90b2
 }

 build() {
@@ -49,9 +53,6 @@ build() {
   export MOZCONFIG="${srcdir}/mozconfig"
   export CPPFLAGS="${CPPFLAGS} -O2 -Wno-format-overflow"

-  # Fix build failures with GCC>=14
-  export CFLAGS="${CFLAGS} -Wno-implicit-int -Wno-incompatible-pointer-types -Wno-int-conversion"
-
   ./mach build
 }

To drop autoconf2.13, alternatively just wait next month until 33.2.0, I cherry picked these patches for gtk3 version.

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

I had some time to read and try some stuff. So, GCC 9's -Werror=format-overflow warning is being treated as an error and aborting the build. From gcc's online documentation (available at https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html) :

"Warn about calls to formatted input/output functions such as snprintf and vsnprintf that might result in output truncation. When the exact number of bytes written by a format directive cannot be determined at compile-time it is estimated based on heuristics that depend on the level argument and on optimization. While enabling optimization will in most cases improve the accuracy of the warning, it may also result in false positives. Except as noted otherwise, the option uses the same logic -Wformat-overflow."

Therefore, by enabling lto by using -flto=2(cpu thread number), gcc9 analyzed the code better, didn't give the warning nor need the fix and produced a space net change savings of about 10MiB in comparison with the same version without lto, performance benefits are not known (it feels faster but it may be just placebo, I have to see how to quantify and display the performance gains) and a negligible amount less of time to build, but used more ram to build. Without lto it's a warning and the warning can be disabled with -Wno-format-overflow in the CPPFLAGS variable in: PKGBUILD

like this: export CPPFLAGS="$CPPFLAGS -O2 -Wno-format-overflow"

and in the mozconfig.in like this: ac_add_options --enable-optimize="-O2 -Wno-format-overflow"

The build progresses smoothly with gcc9 by just adding that and by commenting the gcc8 CC and CXX export lines at the beginning of mozconfig and removing gcc8 dependency from the PKGBUILD. Please, feel free to reproduce the fix provided and hopefully instate the needed changes so others can build with gcc9 smoothly as well. Enjoy. Edit1: fixed formatting Edit2: fixed space savings wording Edit3:fixes

Please use markdown to format your post, syrenity. Three backticks before and after the output should make it into a readable code block.

[  7931.122] (EE) Backtrace:
[  7931.122] (EE) 0: /usr/lib/Xorg (xorg_backtrace+0x4d) [0x55c7efcc30cd]
[  7931.122] (EE) 1: /usr/lib/Xorg (0x55c7efc12000+0xb1209) [0x55c7efcc3209]
[  7931.122] (EE) 2: /usr/lib/libc.so.6 (0x7f1fe5f85000+0x3a7e0) [0x7f1fe5fbf7e0]
[  7931.122] (EE) 3: /usr/lib/libc.so.6 (gsignal+0x145) [0x7f1fe5fbf755]
[  7931.122] (EE) 4: /usr/lib/libc.so.6 (abort+0x125) [0x7f1fe5faa851]
[  7931.122] (EE) 5: /usr/lib/libc.so.6 (0x7f1fe5f85000+0x7ca38) [0x7f1fe6001a38]
[  7931.122] (EE) 6: /usr/lib/libc.so.6 (0x7f1fe5f85000+0x8325a) [0x7f1fe600825a]
[  7931.122] (EE) 7: /usr/lib/libc.so.6 (0x7f1fe5f85000+0x84c5c) [0x7f1fe6009c5c]
[  7931.122] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f1fe44df000+0x5992f) [0x7f1fe453892f]
[  7931.122] (EE) 9: /usr/lib/Xorg (0x55c7efc12000+0x12d3ae) [0x55c7efd3f3ae]
[  7931.122] (EE) 10: /usr/lib/Xorg (0x55c7efc12000+0xfd945) [0x55c7efd0f945]
[  7931.122] (EE) 11: /usr/lib/Xorg (0x55c7efc12000+0x10e275) [0x55c7efd20275]
[  7931.122] (EE) 12: /usr/lib/Xorg (0x55c7efc12000+0x15ceee) [0x55c7efd6eeee]
[  7931.122] (EE) 13: /usr/lib/Xorg (FreeResource+0xcd) [0x55c7efd6f18d]
[  7931.122] (EE) 14: /usr/lib/Xorg (0x55c7efc12000+0x17ab6e) [0x55c7efd8cb6e]
[  7931.122] (EE) 15: /usr/lib/Xorg (0x55c7efc12000+0x37fe8) [0x55c7efc49fe8]
[  7931.122] (EE) 16: /usr/lib/libc.so.6 (__libc_start_main+0xf3) [0x7f1fe5fabee3]
[  7931.122] (EE) 17: /usr/lib/Xorg (_start+0x2e) [0x55c7efc4a30e]
[  7931.122] (EE) 
[  7931.122] (EE) 
Fatal server error:
[  7931.122] (EE) Caught signal 6 (Aborted). Server aborting
[  7931.122] (EE) 
[  7931.122] (EE) 
Please consult the The X.Org Foundation support 
         at http://wiki.x.org
 for help. 
[  7931.122] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[  7931.122] (EE) 
[  7931.122] (II) AIGLX: Suspending AIGLX clients for VT switch
[  7932.335] (EE) Server terminated with error (1). Closing log file.

Latest version randomly crashes X server on Dell XPS 15 (9570).

Had to stop using it for the meanwhile.

huh, I built them without any patches or weird flags, and I read that thread a while back too. What I did was remove ggc8 from the PKGBUILD and the mozconfig and voilà. That gentleman on the thread is the one which is building pale moon with gcc9 right now for fedora which I mentioned before. I'm gonna try on some boxes without -flto to see if I can succeed building it.

I got a build failure with gcc9 (the same build failure that upstream was aware of in March) which is why I've switched to gcc8 in the mozconfig.

I'd rather not include patches to make the package build with gcc9, as upstream get really arsey about that sort of thing, and it's not worth dealing with their antics. The best thing you can do is make noise on their bug tracker about it (but don't expect anything to change).

For the record, gcc9 is building Pale Moon nicely since version 28.5, although apparently is not endorsed (or supported) by the devs yet. PM is built with gcc9 for fedora (copr repo) with an official third-party build endorsed by Moonchild Productions. The patch to build it with gcc8 seems unnecessary, I wonder what happened... I have to warn that building PM with gcc9 uses a tad bit of RAM more... Well, I built with -flto enabled so that takes more RAM, disk space and additional time to build. At linking stages, it will place files in /tmp, which in arch is tmpfs. So if you don't have much ram to spare, I think it's best not to compile with flto because of the added ram usage. Maybe you could mount tmpfs in disk and slash part of ram usage. Make sure to have at least 12G of RAM on the build PC so it's not needed to change /tmp to disk.

Looks like you found the culprit, but if you still get build failures after fixing your space issue, post the new logs.

@WorMzy

https://pastebin.com/V9A1xR18

https://pastebin.com/ex9gCdhn

Thanks

DEBUG: | /var/tmp/conftest.wrS_a1.c:8:1: fatal error: error closing /tmp/ccPfgeq6.s: No space left on device <- oops

Cannot reproduce. Please post the full build output and also upload /home/ljohnson/AUR/palemoon/src/pmbuild/config.log to a pastebin and link here.