Errors compiling PM from source

[access2godzilla]

@Artiom, did you see this: https://developer.mozilla.org/en-US/doc ... requisites (Note the arch linux section where it says about python).

You'll need 4.7

Actually, gcc 4.8 does work, just that it broke PNG decoding for me (http://forum.palemoon.org/viewtopic.php?f=37&t=4335).

[Artiom]

You'll need 4.7

Impossible on Arch. It is a rolling distro and it is already "rolled" on 4.9
I see on the Mozilla site that clang could be a better choice. Will try it later.

Anyway 24.5 was successfully compiled with 4.8. Is is something new in 24.6 that brakes gcc?
I would also try to split configure and make, any clues for it?

[Artiom]

@Artiom, did you see this: https://developer.mozilla.org/en-US/doc ... requisites (Note the arch linux section where it says about python).

Yes, I have read it and I used this guide to create my PKGBUILD

[access2godzilla]

Impossible on Arch.

It is possible, just that you have to use packages from another distro to get that done, if you're willing to put the effort. Debian wheezy packages should be a good choice for this.

[Artiom]

I was misunderstood. The AUR system is to share source packages with other users. I surely can find a way to compile it for me, but another user should have a possibility to compile it using standard Arch package system. So I need to create a special gcc package, which will install to an special fs tree (in order to coexist with distribution's package), than tweak palemoon tools to use it instead of Arch's gcc. This already sounds too much complicated... even without considering compilation time.
I will try clang first, at least it is in the repository.

[Moonchild]

I was misunderstood. The AUR system is to share source packages with other users. I surely can find a way to compile it for me, but another user should have a possibility to compile it using standard Arch package system. So I need to create a special gcc package, which will install to an special fs tree (in order to coexist with distribution's package), than tweak palemoon tools to use it instead of Arch's gcc. This already sounds too much complicated... even without considering compilation time.
I will try clang first, at least it is in the repository.

All I can say is: welcome to the wonderful world of Mozilla code.

[jumba]

Anyway 24.5 was successfully compiled with 4.8. Is is something new in 24.6 that brakes gcc?

Hi artiom! It compiled successfully for me too but it was unstable and crashed after opening few web pages.

maybe unrelated, but I noticed that you have commented out this line in your mozconfig:

Code: Select all

#ac_add_options --disable-webrtc

shouldn't webrtc be disabled on pm builds?

[jjacky]

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.

[Moonchild]

WebRTC should indeed be disabled on Pale Moon.
If you are building a package for official redistribution, please do not change the official feature set or included modules.

[jjacky]

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?

[Moonchild]

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

--disable-crashreporter
--disable-accessibility
--disable-parental-controls
--disable-maintenance-service
--disable-webrtc
--disable-websms-backend
--disable-windows-mobile-components
--disable-metro

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

--with-distribution-id=Palemoon
--enable-official-branding 
--enable-jemalloc
--enable-chrome-format=omni 
--enable-strip

[Artiom]

Ok, I will take into account all this for the next package. Will try to compile with 4.9 this week.

[Artiom]

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.

[jumba]

I found this:

[SOLVED] Makepkg option FORTIFY_SOURCE causes build fail (Page 1) / Creating & Modifying Packages / Arch Linux Forums

[Artiom]

Thank you a lot! I passed configure cap and if compilation is ok, I will update AUR this evening.