SBo scripts not building on current (read 1st post, pls)
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.
If you ever see that, it is almost always due to multilib (or you just managed to install the wrong package). It means it is expecting one format (64bit), but found another (32bit).
Check out the FAQ on SBo for details on how to fix it.
If you ever see that, it is almost always due to multilib (or you just managed to install the wrong package). It means it is expecting one format (64bit), but found another (32bit).
Check out the FAQ on SBo for details on how to fix it.
Ah, that makes sense. Thanks, I will look into it.
Edit: Adding LDFLAGS="-L/usr/lib64" to the SlackBuild as the FAQ recommends worked.
Last edited by montagdude; 05-16-2016 at 10:01 PM.
Okay, I don't think this one was my fault, but of course I'm probably wrong. I had this issue with mlt:
Code:
make[2]: Entering directory '/tmp/SBo/mlt-6.0.0/src/modules/lumas'
install -d /tmp/SBo/package-mlt/usr/share/mlt/lumas/PAL
install -d /tmp/SBo/package-mlt/usr/share/mlt/lumas/NTSC
install -m 644 PAL/* /tmp/SBo/package-mlt/usr/share/mlt/lumas/PAL
install: cannot stat 'PAL/*': No such file or directory
Makefile:26: recipe for target 'install' failed
make[2]: *** [install] Error 1
The problem is that /tmp/SBo/mlt-6.0.0/src/modules/lumas/PAL (and also /tmp/SBo/mlt-6.0.0/src/modules/lumas/NTSC) is empty. I removed the two lines that attempt to install PAL/* and NTSC/* from the Makefile in /tmp/SBo/mlt-6.0.0/src/modules/lumas, and then the build finished and I was able to install the package. Whether this actually fixed the problem or merely let me ignore it for now and install the package, I'm not sure.
Last edited by montagdude; 05-16-2016 at 10:23 PM.
Okay, thanks for checking. It probably has to do with something that I either installed or removed, then. Sorry about burdening you with a something that was apparently my fault. I'll set up a clean VM like you did and test that myself first next time before reporting a problem.
Last edited by montagdude; 05-16-2016 at 11:41 PM.
I've modified the SlackBuild to `git` the source ; run `autoreconf --install` ; run `configure` and then `grep VERSION=` from the resulting MakeFile for the SBo.txz file.
However, I am not sure about the conventions for github source and the DOWNLOAD= link in the .info file.
Do Y'All want a copy of my modified arp-scan.SlackBuild file ( attached ) ?
I can't find an example SlackBuild that invokes `git` but if there's a convention, I can fix the .info file as well.
Minor documentation issue in libraries/backports-ssl-match-hostname:
VERSION variable in backports-ssl-match-hostname.info is listed as 3.5.1.0, but in the SlackBuild and the filename for the source download it is 3.5.0.1. This caused me to reinstall it, thinking my version was out of date, but really it wasn't.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.