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.
that's because you have downloaded the tarball using the browser instead of wget: I added an alternate tarball-extracting routine in my branch, will go in the next update
I think those with the segfault must have some hardware-specific problem. That's all I can think of, because lots of us have tried on a clean install with no problems. Of course, the debug output should be helpful, but other than that, maybe try it in a virtual machine? That would isolate it from the real hardware.
It's a puzzling situation for sure, but you can't expect upstream to fix the problem if they can't reproduce it.
Last edited by montagdude; 09-24-2016 at 07:20 AM.
--snip--
cat: /home/nitesky/Desktop/Slackware/SlackBuilds/PaleMoon.SlackBuild: No such file or directory
bash-4.3#
Looks like it compiled properly but couldn't find the SlackBuild afterwards (the SlackBuild copies itself into the package's doc directory). Do you have it named differently (case sensitive matters). Maybe you don't have the M on Moon capitalized. What's the output of:
Code:
ls -la ~nitesky/Desktop/Slackware/SlackBuilds/
Last edited by bassmadrigal; 09-24-2016 at 07:25 AM.
That looks like one problem. I never have had a problem like this happen with anything I have downloaded and have never had to correct names like with this one
That looks like one problem. I never have had a problem like this happen with anything I have downloaded and have never had to correct names like with this one
@Gordie, it looks like you just need to rename the SlackBuild into PaleMoon.SlackBuild (note that P M S and B are all capitalized). After that, you should be good
@kronosschoty, maybe it'd be worth changing the github download link to the following. It would make sure that it will be the same name whether you download it via wget or the browser (github is weird like that).
Either link would work, although with the second one, you'd obviously need to change the SlackBuild a bit to work with the new name, but then the source name is much more inline with most source names.
@Gordie, it looks like you just need to rename the SlackBuild into PaleMoon.SlackBuild (note that P M S and B are all capitalized). After that, you should be good
@kronosschoty, maybe it'd be worth changing the github download link to the following. It would make sure that it will be the same name whether you download it via wget or the browser (github is weird like that).
Either link would work, although with the second one, you'd obviously need to change the SlackBuild a bit to work with the new name, but then the source name is much more inline with most source names.
Distribution: Slackware 15.0 x64, Slackware Live 15.0 x64
Posts: 620
Original Poster
Rep:
Does that autoconf 'upgrade/substitute' the autoconf that comes with stock 32 bit Slackware 14.2 (autoconf 2.69)? It won't mess anything else up on the system will it?
No, it pretty much does what the stock slackware current firefox slackbuild does, builds an old autoconf and then uses that to build the browser without installing the new autoconf.
khronosschoty's slackbuild built fine for me and the RetroArch emscripten port even works in PaleMoon.
It's because you have it named PaleMoon.Slackbuild, not PaleMoon.SlackBuild. Did you rename it? I just checked the files from SBo and the name is right there.
Running Sbopkg now. Sick of this name game.
It is my own fault really but don't think it is in my power to change things. Have been having trouble seeing the obvious for at least 5 years now. Could be related to the meds I have to take. Not sure. Oh well, no sense getting upset with myself for MISSING THE "B".
Thanks for being patient with me. You guys are the greatest
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.