PaleMoon on Slackware 14.2 update...

Skaendo · 09-18-2016, 07:17 PM

Quote:

Originally Posted by khronosschoty

Here is the SlackBuild I wrote for palemoon, to compile palemoon from source.

https://notabug.org/khronosschoty/Sl...aster/palemoon

I tested it in a pure untouched install of slackware64-14.2 and it appears to run flawlessly.

Thanks! I'll give this a run tonight.

Skaendo · 09-18-2016, 10:53 PM

Quote:

Originally Posted by khronosschoty

Here is the SlackBuild I wrote for palemoon, to compile palemoon from source.

https://notabug.org/khronosschoty/Sl...aster/palemoon

I tested it in a pure untouched install of slackware64-14.2 and it appears to run flawlessly.

I did a clean install of 14.2, removed autoconf and installed the one from ponce and tried to compile palemoon.

Code:

Pale-Moon-26.4.1_Release/xulrunner/tools/redit/Makefile.in
Pale-Moon-26.4.1_Release/xulrunner/tools/redit/moz.build
Pale-Moon-26.4.1_Release/xulrunner/tools/redit/redit.cpp
Creating global state directory from environment variable: /home/endo/Pale-Moon-26.4.1_Release/moz.build
Please re-run mach.
Next =>
make: *** No rule to make target 'package'.  Stop.

It's not going into the correct folder, the files are being extracted to /tmp/SBo/Pale-Moon-26.4.1_Release when your SlackBuild is going into /tmp/pmbuild.

Ztcoracat · 09-18-2016, 10:56 PM

Quote:

Originally Posted by khronosschoty

Here is the SlackBuild I wrote for palemoon, to compile palemoon from source.

https://notabug.org/khronosschoty/Sl...aster/palemoon

I tested it in a pure untouched install of slackware64-14.2 and it appears to run flawlessly.

That was really nice of you Thanks khronosschoty!-

khronosschoty · 09-19-2016, 12:08 AM

Whoops wow sorry about that, and thanks for caching that. That is not supposed to work that way and your changes even may still prove problematic... let me fix that.

Quote:

Originally Posted by Skaendo

I did a clean install of 14.2, removed autoconf and installed the one from ponce and tried to compile palemoon.

Code:

Pale-Moon-26.4.1_Release/xulrunner/tools/redit/Makefile.in
Pale-Moon-26.4.1_Release/xulrunner/tools/redit/moz.build
Pale-Moon-26.4.1_Release/xulrunner/tools/redit/redit.cpp
Creating global state directory from environment variable: /home/endo/Pale-Moon-26.4.1_Release/moz.build
Please re-run mach.
Next =>
make: *** No rule to make target 'package'.  Stop.

It's not going into the correct folder, the files are being extracted to /tmp/SBo/Pale-Moon-26.4.1_Release when your SlackBuild is going into /tmp/pmbuild.

I do believe that I have it working correctly with these edits:

Code:

-rm -rf /tmp/pmbuild
-mkdir /tmp/pmbuild

python2 mach build || echo "Next =>"

-cd /tmp/pmbuild
+cd /tmp/SBo/Pale-Moon-26.4.1_Release
make package
-cd dist
+cd /tmp/pmbuild/dist

I have not confirmed totally, but it is compiling for me right now.

Skaendo · 09-19-2016, 12:11 AM

I did get a successful compile, but there is something goofy going on.

*Edit, you got there before I did

(Removed my edits from post)

khronosschoty · 09-19-2016, 12:53 AM

I changed the SlackBuild slightly to address that issue that crept in, I've not had a chance to compile all the way through but I suspect the issue is fixed now. It will take a bit for the compile to run all the way through. The issue was mainly with "export MOZBUILD_STATE_PATH" pointing to the wrong place but also there was some issue with the location of where the program was being extracted.

I pushed the changes to notabug in case you want to give it anther go.

Skaendo · 09-19-2016, 01:07 AM

Quote:

Originally Posted by khronosschoty

I changed the SlackBuild slightly to address that issue that crept in, I've not had a chance to compile all the way through but I suspect the issue is fixed now. It will take a bit for the compile to run all the way through. The issue was mainly with "export MOZBUILD_STATE_PATH" pointing to the wrong place but also there was some issue with the location of where the program was being extracted.

I pushed the changes to notabug in case you want to give it anther go.

Gotcha, gonna set it up and let it run as I go to bed. It only took 2 hours (almost exactly) for me to compile. That's about what they say it takes over at PM forum.

Nice work!

khronosschoty · 09-19-2016, 08:43 AM

Over the course of the night I really polished the Slackbuild. So I would really encourage people to give it a try and please feel free to comment and share tips.

montagdude · 09-19-2016, 09:35 AM

I plan to give it a try tonight. I mainly want to see if Vimperator will work with it, because that's the only real reason I'm using Firefox right now. Thanks for putting this together!

Skaendo · 09-19-2016, 04:24 PM

Quote:

Originally Posted by khronosschoty

I changed the SlackBuild slightly to address that issue that crept in, I've not had a chance to compile all the way through but I suspect the issue is fixed now. It will take a bit for the compile to run all the way through. The issue was mainly with "export MOZBUILD_STATE_PATH" pointing to the wrong place but also there was some issue with the location of where the program was being extracted.

I pushed the changes to notabug in case you want to give it anther go.

Unfortunately, on a clean install of 14.2 with a replaced autoconf, Pale Moon is still segfaulting here.

I'm not using VM's here, I do full clean installs on metal.

This last compile that I did took a little over an hour, probably 1:15 and it seemed to go well although I didn't log it.

I don't know if I used the latest commit that you made, so I'm going to give it another go.

montagdude · 09-19-2016, 06:07 PM

It's working for me here on Slackware64 14.2. Skaendo, when does the segfault occur? Right away, or when browsing a certain site? (Sorry, I haven't kept up on this saga enough to remember the details.)

khronosschoty, everything is working well so far here, though I've only started testing. Also, Vimperator works, so this may be able to replace Firefox for me. My one nitpick is that after running the SlackBuild, palemoon.desktop came in with 600 permissions. It should be 644.

Skaendo · 09-19-2016, 06:37 PM

Quote:

Originally Posted by montagdude

It's working for me here on Slackware64 14.2. Skaendo, when does the segfault occur? Right away, or when browsing a certain site? (Sorry, I haven't kept up on this saga enough to remember the details.)

khronosschoty, everything is working well so far here, though I've only started testing. Also, Vimperator works, so this may be able to replace Firefox for me. My one nitpick is that after running the SlackBuild, palemoon.desktop came in with 600 permissions. It should be 644.

Segfault was happening instantly. I wouldn't even see Pale Moon launch.

But with the last commit that I downloaded, (390b62e8b1dbe6510d0a0f0233742a67a854b2ef) it is giving me "Illegal Instruction" when I try to launch from terminal.

I swear that all I'm doing is install Slackware, remove autoconf, install ponce's autoconf, build and install Pale Moon.

I will try again later, I have some yard work to get to before it gets dark here.

Maybe it's this crappy HP/AMD/nVidia PC that I'm using.

khronosschoty · 09-19-2016, 07:56 PM

I updated the Slackbuld now because I borrowed a trick from Pat on how he uses autoconf to compile Firefox without installing autoconf in the normal fashion.

Quote:

Originally Posted by montagdude

It's working for me here on Slackware64 14.2. Skaendo, when does the segfault occur? Right away, or when browsing a certain site? (Sorry, I haven't kept up on this saga enough to remember the details.)

khronosschoty, everything is working well so far here, though I've only started testing. Also, Vimperator works, so this may be able to replace Firefox for me. My one nitpick is that after running the SlackBuild, palemoon.desktop came in with 600 permissions. It should be 644.

Great! and thanks for letting me know I'll fix that.

khronosschoty · 09-20-2016, 07:28 AM

Did you ever get it working? Give it one more go? If you do I'd be interested in knowing the results. I was thinking I hope you get it compiled and it works for you because its just been an amazingly stable fast experience here.

Quote:

Originally Posted by Skaendo

Segfault was happening instantly. I wouldn't even see Pale Moon launch.

But with the last commit that I downloaded, (390b62e8b1dbe6510d0a0f0233742a67a854b2ef) it is giving me "Illegal Instruction" when I try to launch from terminal.

I swear that all I'm doing is install Slackware, remove autoconf, install ponce's autoconf, build and install Pale Moon.

I will try again later, I have some yard work to get to before it gets dark here.

Maybe it's this crappy HP/AMD/nVidia PC that I'm using.

Skaendo · 09-20-2016, 01:23 PM

Quote:

Originally Posted by khronosschoty

Did you ever get it working? Give it one more go? If you do I'd be interested in knowing the results. I was thinking I hope you get it compiled and it works for you because its just been an amazingly stable fast experience here.

I have not gotten it to work yet. I also have not tried your latest commit yet.

It is still segfaulting for me. I have tried it on 2 different PC so far, 1 HP & 1 Dell both full clean installs of Slackware 14.2 and then trying to compile. No settings changed, no customizations, etc...

Also just a side note, I keep a local mirror of Slackware and it is kept up to date.

I don't know what I am doing different, maybe someone could be so kind and upload a compiled package for me to try out.

I was really hoping that this would work, I really like Pale Moon and was hoping to be able to continue to use it.