Support and discussions for the x86/x64 Linux version of Pale Moon and specific Linux distribution questions related to the browser.
If your question is about general use of the browser and not specific to Linux, then please use the General Support board.
- Pale Moon guru
- Posts: 29741
- Joined: 2011-08-28, 17:27
- Location: Tranås, SE
Moonchild wrote:If you are building a package for official redistribution, please do not change the official feature set or included modules.
Is there such a list (of options to use/not to use) to build PM somewhere?
You can get the list by looking at the official browser's about:buildconfig and I've also outlined them in the build instructions on this forum, but I'll re-iterate here, for sake of ease.
This is the current disabled feature
flags set for official mainline builds (24.6):
Code: Select all
Official builds also use the following additional flags (some are already defaults in the source code but still stated explicitly as a leftover from past changes by Mozilla):
Code: Select all
"Son, in life you do not fight battles because you expect to win, you fight them merely because they need to be fought." -- Snagglepuss
Ok, I will take into account all this for the next package. Will try to compile with 4.9 this week.
jjacky wrote:I was able to compile pale moon on Arch (x64) w/ gcc-4.9 just fine (well, almost, but unrelated), as along as I removed -D_FORTIFY_SOURCE=2 -- maybe try removing it from your CPPFLAGS.
I tried with clang, and with gcc 4.9. No difference, the same error about types. However clang works much faster!
How did you remove -D_FORTIFY_SOURCE=2 ?
I greped it in the sources and found nothing
The error is during configure step.
Thank you a lot! I passed configure cap and if compilation is ok, I will update AUR this evening.