[SOLVED] Using packages built for 13.0 with slackware 13.1
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.
The SBo 13.1 repo is open now. If you're unable to find your package in that repo, you can certainly try a 13.0 SlackBuild. The most common problems are bash 4 subshell failures, libpng issues, and gcc issues, but some (many?) still work and many others are easily fixable.
Oh, hey, first post - and welcome to LQ!
-- Oh, oh. You're asking about 3rd party binary packages. Such a strange notion didn't even cross my brain at first. I wouldn't recommend installing 3rd party binary packages at all but definitely not ones built for 13.0. I was recommending http://slackbuilds.org/repository/13.1/
System binaries are linked with the GNU C Library, version 2.11.1. This version of glibc also has excellent compatibility with existing binaries.
So give your packages a try. If they don't work, then it won't take much to recompile them. You can, of course, ask for help here. A lot of people will be working on the same software with the new version of Slackware.
The SBo 13.1 repo is open now. If you're unable to find your package in that repo, you can certainly try a 13.0 SlackBuild. The most common problems are bash 4 subshell failures, libpng issues, and gcc issues, but some (many?) still work and many others are easily fixable.
Oh, hey, first post - and welcome to LQ!
-- Oh, oh. You're asking about 3rd party binary packages. Such a strange notion didn't even cross my brain at first. I wouldn't recommend installing 3rd party binary packages at all but definitely not ones built for 13.0. I was recommending http://slackbuilds.org/repository/13.1/
FWIW, the packages at Slackbuilds.org aretechnically 3rd party. But they are also the best 3rd party packages avaiable, except for some outstanding personal repositories maintained by Slackware developers.
I was advising against the combination of "third party binary" packages, not against third party stuff alone or meaning to imply SBo wasn't third party.
I was advising against the combination of "third party binary" packages, not against third party stuff alone or meaning to imply SBo wasn't third party.
it's not because of sbopkg that your builds fail on 13.1: you have to set it up tracking a repository for 13.1 (or the ex-current) that has usable slackbuilds on that version, then it works like a charm.
with the correct repository sbopkg let me build 267 packages on -current/13.1 in one shot.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.