[SOLVED] Slackware64 14, problems with compiling packages from slackbuilds.org
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.
Slackware64 14, problems with compiling packages from slackbuilds.org
Hi to all,
I've just reinstall my system to slackware64 14, before I used just x32 slackware. First of all I've installed compat32 packages from alien's site, and then start to build programs from slackbuilds.org. Some of them installed properly, but large amount of other didn't. The most often mistakes, is that some features are deprecated. Till there is no 14.0 branch on slackbuilds.org I'm using 13.37 branch. So I would like to know is this just my problem, or I should to wait for 14.0 slackbuilds?
I have problems with next packages: widelands, wethnoth, dirac, libffado, lirc, wiicd, graphhviz, physfs, libofa and others.
All this packages, were ok on slackware 13.37 x32.
My system is also running Slackware64-14.0 (Multi-Lib enabled). All the 13.37 packages that I have tried work perfectly. As Didier has said, best to wait for slackbuilds.org to catch up, or you can look and see the point at which the compilation failed and modify the slackbuild to compensate.
Anyone knows how long is it going to take for the 14.0 branch to appear in slackbuilds ?
If it is a couple of days I can wait, otherwise I will be tempted to access it from the git repository...
Except for HandBrake, all major issues had been fixed I believe. The admins are fixing only some remaining minor ones. Besides, branch 14.0 was already created in the git repo.
That said, it totally depends on the SBo admins when to officially announce the 14.0 branch.
GCC 4.7.x changed in a few significant ways, mostly in becoming more strict with compiling. Also glibc changed the way includes are handled. The latest ffmpeg has changed too, anything dependent upon that needs rebuilding. All of those types of build issues need to be resolved upstream or patched in the build scripts. Etc., etc.
So patience will be required with the slackbuilds scripts for 14.0.
So reading this thread, if I understand, one is better to wait for Slackbuild 14 before upgrading to Slackware 14 from say 13.37 if any packages from Slackbuild have been used?
I have upgraded from 13.37 to 14, I just finished actually, and I have some Slackbuilds. I had to recompile i3 due to libraries issues. I guess I was rather lucky.
EDIT:
Oups just found out Terminator is broken too. Recompiled and good to go.
Except for HandBrake, all major issues had been fixed I believe. The admins are fixing only some remaining minor ones. Besides, branch 14.0 was already created in the git repo.
That said, it totally depends on the SBo admins when to officially announce the 14.0 branch.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.