PaleMoon from source SlackBuild
 

Hi,


I recently have been working on possible updating the script at SlackBuilds.org so that it will build a temporary gcc-4.9.4 and then build Pale Moon with that version of gcc. I think this will resolve issues for those who still have issues. I am wondering if anyone would be willing to test out the package I produce with gcc-4.9.4 and test to see if it works for them and or resolves issues if they had them. I am hosting the package on dropbox atm

https://www.dropbox.com/s/n8n2bu2tsh...6_64-1_SBo.tgz

What issues are you encountering with the package that is build with the Slackware gcc 5.x compiler?
What Slackware-specific issues exist that can be contributed to Slackware's compiler? When I asked the Pale Moon developer about this, he said that most issues are reported for Debian and its spinoffs and he was not aware of Slackware-specific issues.

I think it's based on user's report about remember password feature that was reported in IRC

That user was drunk, did not know what he was doing at the time, and did not answer to my questions to be more specific. Password manager works for me in Pale Moon (my own package, compiled with gcc5, not the SBo source-build).

Pale Moon is just an re-branded Firefox, because of the Debian's Zealots. Nothing more. :P

There is nothing magic into Pale Moon compared with Firefox, excluding the name change.

Same, we could stay in a old Firefox release, renamed/re-branded i.e. SlackFox... :hattip:

I just know that I was told that 4.7 series to 4.9 series is stable and gcc 5 and 6 are testing. I know some people report having issues. I know I've observed an issue with yahoo causing the browser to crash that I think is resolved with using 4.9.4. I am just trying to be helpful.

I am not bashing you, at all :-)
I think it is great that SBo has a script for a source build of Pale Moon. If possible, I always prefer programs that are compiled on Slackware instead of relying on "official binaries".
It's just that the Pale Moon developer is not a Linux guy, so he relies on some other people to tell him what's working and what not. Those people are all running some kind of Debian/Ubuntu/Mint variant, and when I told him I rely more on the stability of Slackware's un-patched compilers than on the stories about crashes on other distros, he answered that I should do what i think is best.

So, I use gcc5, and at the same time am using "-Os" as optimization flag, similar to "-O2" optimization but with better respect for code size.

What we used to have to do with Slackware's Firefox builds in the past, was to apply no optimizations at all by specifying CFLAGS="-O" and "--enable-optimization" without parameter. Perhaps I will try that in future builds of my own package.

I am at work now, so I can not test, but tonight I will test Pale Moon with Yahoo pages.

You're thinking of "iceweasel".

Please read up on Pale Moon. It is not a re-branded Firefox. It is based on an old firefox codebase and since then has been independently evolved.
In particular, Pale Moon has not followed Firefox when that made the switch to the Australis User Interface. Read https://www.palemoon.org/layout-differences.shtml

The PaleMoon built from source on SBo crashes pretty reliably for me on this site (using Slackware64 14.2):

http://hfboards.hockeysfuture.com/

It probably has to do with the ads, but PaleMoon's AdBlock Latitude didn't fix the problem. I haven't tried the repackaged official binary or Alien Bob's version, but this could be another one to check if you are looking for problematic sites.

I'm using the repackaged binary, and I just clicked around on that site a bunch with no problem. (I'm using Adblock Latitude as well)

I'm kind of wondering what kind of compile time it is taking Eric. Last time I compiled Pale Moon it took over 2 hours, but that was on an old C2D@2GHZ w/4GB RAM.

I just tried with the repackaged binary version, and I have no problems with that site either now, with or without AdBlock Latitude.

On my laptop with Core-i5 2.5 GHz, it only took about 30 minutes.

try having a look at the README and the SlackBuild for the OPTIMIZE build option (what Alien Bob was writing above).
if might be useful there's also an ENABLE_DEBUG option.

I read the README before building, but by the time I had tested it I mostly forgot about what it said. :tisk: I'm using the Oxygen icon theme, so that may be what's causing the problem. I will try testing some more when I get time.

There is a hack if you're using the Oxygen icon theme; just modify your launch command to point to a different theme.
It's on the forum here somewhere.