SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Has anyone had success in building this new version on Slackware? After modifying the SlackBuild script slightly to account for changes to the directory structure in the latest versions, and after accounting for some sloppy regex in the mach script (as mentioned here,) the build is still failing--and throwing a rather confusing error. To wit:
Code:
0:20.12 Creating config.status
0:20.29 Feeding the hatchlings...
0:31.01 Finished reading 851 moz.build files in 2.62s
0:31.01 Processed into 6038 build config descriptors in 3.03s
0:31.01 RecursiveMake backend executed in 4.48s
0:31.01 1572 total backend files; 1572 created; 0 updated; 0 unchanged; 0 deleted; 41 -> 654 Makefile
0:31.02 FasterMake backend executed in 0.31s
0:31.02 7 total backend files; 7 created; 0 updated; 0 unchanged; 0 deleted
0:31.02 Total wall time: 10.77s; CPU time: 10.47s; Efficiency: 97%; Untracked: 0.32s
Configure complete!
Be sure to run |mach build| to pick up any changes
0:31.41 /usr/bin/gmake -f client.mk -s
0:32.02 gmake: *** No rule to make target 'There', needed by 'Error'. Stop.
0:32.03 0 compiler warnings present.
I can't imagine a make target called "There"!!! Any ideas on how to proceed would be greatly appreciated.
(For the record, I'm on Slackware64 14.2.)
I've been working to update the SlackBuild; as of right now on current the build fails for me as well. I haven't checked on 14.2 yet.
Has anyone had success in building this new version on Slackware? After modifying the SlackBuild script slightly to account for changes to the directory structure in the latest versions, and after accounting for some sloppy regex in the mach script (as mentioned here,) the build is still failing--and throwing a rather confusing error. To wit:
Code:
0:20.12 Creating config.status
0:20.29 Feeding the hatchlings...
0:31.01 Finished reading 851 moz.build files in 2.62s
0:31.01 Processed into 6038 build config descriptors in 3.03s
0:31.01 RecursiveMake backend executed in 4.48s
0:31.01 1572 total backend files; 1572 created; 0 updated; 0 unchanged; 0 deleted; 41 -> 654 Makefile
0:31.02 FasterMake backend executed in 0.31s
0:31.02 7 total backend files; 7 created; 0 updated; 0 unchanged; 0 deleted
0:31.02 Total wall time: 10.77s; CPU time: 10.47s; Efficiency: 97%; Untracked: 0.32s
Configure complete!
Be sure to run |mach build| to pick up any changes
0:31.41 /usr/bin/gmake -f client.mk -s
0:32.02 gmake: *** No rule to make target 'There', needed by 'Error'. Stop.
0:32.03 0 compiler warnings present.
I can't imagine a make target called "There"!!! Any ideas on how to proceed would be greatly appreciated.
(For the record, I'm on Slackware64 14.2.)
Try the modifications found in this script here (see attachments); and see if it builds on 14.2. I suspect it should build on 14.2.
Last edited by khronosschoty; 11-14-2021 at 01:39 PM.
Thank a lot for the revised SlackBuild script. After upgrading ffmpeg to 3.2.4.and installing Yasm 1.3.0 PaleMoon 29.4.2.1 built without problems on a single core 32bit Slackware 14.2 (10 hours) using the script.
B.t.w., is the UXP-RELBASE, as adviced on Slackbuilds.org, a necessity for building?
...B.t.w., is the UXP-RELBASE, as adviced on Slackbuilds.org, a necessity for building?
Not since Palemoon 29.4.1 was released. (September, I think.)
Since Moonchild removed Palemoon from github, and now provides only snapshots of the source tarballs, the UXP-RELBASE is included in the Palemoon source. (It used to be a separate tarball of its own.)
We can recycle the revised palemoon slackbuild script provided by Khronosschoty (see above) and use it to build also Basilisk on 32bit Slackware 14.2 if we modify the script a little and repack the basilisk 2021.11.14 source tarball so it's tree will be in accordance with the palemoon source structure.
Example of repack of basilisk source:
Code:
mkdir basilisk-source
cp basilisk-2021.11.14.source.tar.xz ./basilisk-source
cd basilisk-source
tar -xvf basilisk-2021.11.14.source.tar.xz
rm basilisk-2021.11.14.source.tar.xz
cd ..
tar -cjf repack.tar.xz basilisk-source
rm basilisk-2021.11.14.source.tar.xz
mv repack.tar.xz basilisk-2021.11.14.source.tar.xz
The script will build Basilisk against GTK3.Thanks to UXP developers Toby and Moonchild and to Khronosschoty/Ponce for the script.
decided to put a few things here: updated SlackBuild, and a build for gcc9, for those who want to build on current. Couldn't get binaries uploaded. However, after Xmas I should be back into the swing of things. The other thing I aim to do is get Pale Moon building on gcc 11 but until, I do gcc9 will have to do.
Its funny I started adding the necessary elements to certain extensions, to get them working again, and then this release came out. However, I decided I might keep my own list of extensions just because.
I never realized how handy video_downloadhelper is. I was going over the new webextension version of many extensions, to see what kind of updates were done, and was surprised to that these old unmaintained extensions are really holding up.
Last edited by khronosschoty; 12-20-2021 at 12:39 AM.
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,069
Rep:
Full (or at least as close as possible) extension support seems to be a matter of time:
Quote:
On the slightly longer term, Pale Moon will return to carrying the Firefox GUID (like Basilisk has done) instead of its own, to further improve extension compatibility. Of course this won't make "legacy" Firefox extensions suddenly/magically compatible if there are discrepancies with our core code and APIs as opposed to the state of Firefox when Mozilla abandoned them, but it will take away any barriers aside from user effort when it comes to extensions, and will reduce pressure on the core development people putting extension responsibility squarely and solely in the hands of the community.
Of course this will require some changes to extensions and the add-ons site, but that shouldn't be too terribly much of an issue and might actually simplify the site's code (to what extent will have to be answered by Tobin who wrote that code from the ground up).
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,095
Rep:
Quote:
Originally Posted by cwizardone
Good to know.
Thx.
OTOH, Click&Clean, HTTPS Always, and Adblock Latitude are all working here.
Something odd happen just happened.
Click&Clean has worked since installing Pale Moon yesterday and it worked this morning. After installing today's multilib updates and rebooting, Click&Clean no longer works. The message in the add-on setup panel is Click&Clean is not compatible. Installing the multilib updates is all I did. Nothing else.
Pale Moon has been removed and Basilisk re-installed.
Last edited by cwizardone; 12-22-2021 at 03:50 AM.
Reason: Typo.
Not fully, as it seems. Palemoon-29.4.3 won't install the EPUBReader-1.5.0.12 add-on, claiming it's not compatible despite running fine in Basilisk.
Not all of the old extensions worked on Pale Moon, that worked on Basilisk. However, that said, it does seem that Pale Moon is less compatible than it was in the past; however, I did a poor job of tracking that and can't be 100% sure (meaning it might only be a few rare edge cases).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
