Pale Moon 27.3.0 and GCC-7.1

3rensho · 05-23-2017, 06:10 AM

Am running Slack64-current and alienBob's build of Pale Moon 27.3.0. Moon seems to run OK except that I can't get the FireFTP (2.0.19.1-signed) extension to allow input of ftp sites so I thought I would build it on my system to see it that helped (have been using FF but the latest Slack release of 52.1.2esr has a lot of problems on my machine). Tried building PM using alienBob's script but it fails with errors -

./checkpkg -l build.log
++ Checking logfile 'build.log' (no news is good news):
122495: 0:55.70 ../../dist/include/mozilla/mozalloc.h:207:33: error: 'bad_alloc' in namespace 'std' does not name a type
122498: 0:55.70 ../../dist/include/mozilla/mozalloc.h:213:44: error: 'nothrow_t' in namespace 'std' does not name a type
122501: 0:55.70 ../../dist/include/mozilla/mozalloc.h:219:35: error: 'bad_alloc' in namespace 'std' does not name a type
122504: 0:55.70 ../../dist/include/mozilla/mozalloc.h:225:46: error: 'nothrow_t' in namespace 'std' does not name a type
122507: 0:55.70 ../../dist/include/mozilla/mozalloc.h:237:44: error: 'nothrow_t' in namespace 'std' does not name a type
122510: 0:55.70 ../../dist/include/mozilla/mozalloc.h:249:46: error: 'nothrow_t' in namespace 'std' does not name a type
122628: 0:57.52 gmake[5]: *** [/tmp/build/tmp-palemoon/Pale-Moon-27.3.0_Release/config/rules.mk:938: BatteryManager.o] Error 1
122629: 0:57.52 gmake[4]: *** [/tmp/build/tmp-palemoon/Pale-Moon-27.3.0_Release/config/recurse.mk:74: dom/battery/target] Error 2
122941: 1:23.30 gmake[3]: *** [/tmp/build/tmp-palemoon/Pale-Moon-27.3.0_Release/config/recurse.mk:37: compile] Error 2
122942: 1:23.30 gmake[2]: *** [/tmp/build/tmp-palemoon/Pale-Moon-27.3.0_Release/config/rules.mk:541: default] Error 2
122943: 1:23.30 gmake[1]: *** [/tmp/build/tmp-palemoon/Pale-Moon-27.3.0_Release/client.mk:398: realbuild] Error 2
122944: 1:23.30 gmake: *** [client.mk:171: build] Error 2
122946: ./palemoon.SlackBuild FAILED at line 282
|install mawk). For LFS: we put mktemp in /usr/bin not /bin, remove

A lot of searching shows that these mozalloc.h related errors are common when gcc is upgraded. Have found some proposed patches for these errors but they don't help in my hands. Not being a programmer I am at a loss as how to fix the errors. Has anyone found a way around? BTW am running the latest gcc-7.1 build from the updates of 22.5.17.

Didier Spaier · 05-29-2017, 10:04 AM

To get an answer, I suggest that you request a moderator to move your post in the Slackware forum (just click Report on the bottom of your post). Alternatively post in this thread or comment this blog post.

3rensho · 05-30-2017, 02:08 AM

OK, asked mods to move it although the problem has nothing to do with Slackware per se. It's just that Blue Moon needs a patch to build with gcc-7.1. Always happens with large gcc version jumps. Takes a while for software to catch up.

bassmadrigal · 05-31-2017, 12:36 PM

On SBo, they actually provide an option to use gcc 4.9.4 if it exists on your system. In the PaleMoon README, they state the following:

Quote:

If you experience crashes when visiting some sites, notable yahoo.com,
using a different compiler will likely resolve these issues. Gcc-4.9.4
is most likely the "best" compiler to use. Some users report that compiling
with clang also resolves crashes. Both, clang and the default GCC Slackware
ships with, however, are unsupported; but may work. If gcc-4.9.4 is installed
and detected, the script will compile PaleMoon with it; however, if you pass
the script the variable CC=clang and CXX=clang++ (for example) the script will
atempt to compile PaleMoon using clang (replace clang and clang++ with
whatever compiler is desired, and present in the system). If you desire to
install and use gcc-4.9.4 (and need help), visit the wiki help link above.

They have a gcclegacy494 package available on SBo.

3rensho · 06-01-2017, 02:40 AM

Thanks for that bassmadrigal. Will have a look. Goal is to build it with 7.1 though.

Alien Bob · 06-01-2017, 03:14 AM

Quote:

Originally Posted by 3rensho

Thanks for that bassmadrigal. Will have a look. Goal is to build it with 7.1 though.

You could start by adding " -std=gnu++98" to the CXXFLAGS, sometimes that is enough to make older code compile with the new stricter g++.