LinuxQuestions.org - [SOLVED] Slackware64 14, problems with compiling packages from slackbuilds.org

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Slackware64 14, problems with compiling packages from slackbuilds.org (https://www.linuxquestions.org/questions/slackware-14/slackware64-14-problems-with-compiling-packages-from-slackbuilds-org-4175429712/)

Did you use version 2.32.1 in git? I remember successfully building it when 14.0 was still in -current state.

Quote:

Originally Posted by Woodsman (Post 4793364)

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. :)

I thought I'd piggy-back onto this comment some more specifics about gcc 4.7.x. One of the issues is actually well documented (if you know where to look) on the gnu/gcc site:

Quote:

Many of the standard C++ library include files have been edited to no longer include <unistd.h> to remove namespace pollution.

As such, C++ programs that used functions including truncate, sleep or pipe without first including <unistd.h> will no longer compile. The diagnostic produced is similar to:

error: ‘truncate’ was not declared in this scope
error: ‘sleep’ was not declared in this scope
error: ‘pipe’ was not declared in this scope
error: there are no arguments to 'offsetof' that depend on a template
parameter, so a declaration of 'offsetof' must be available
Fixing this issue is easy: just include <unistd.h>.

Unfortunately, this isn't something you're going to work around with a configure option or environment variable. You'll need to find the particular file in the source and add the include line. Fortunately, this has actually fixed the few instances I've found where this was a problem.

Now I see a new branch 14.0 on slackbuilds.org but I can't chose one in sbopkg util. Am I should to wait for update of sbopkg?

you can add yourself this line on top of /etc/sbopkg/repos.d/40-sbo.repo

Code:

SBo 14.0 "SBo repository for Slackware 14.0" _SBo rsync slackbuilds.org::slackbuilds/14.0 GPG

then edit /etc/sbopkg/sbopkg.conf and set the variables REPO_BRANCH and REPO_NAME like this

Code:

REPO_BRANCH=${REPO_BRANCH:-14.0}

REPO_NAME=${REPO_NAME:-SBo}

sync

Code:

sbopkg -r

and you're ready to go :)

Thanks, I was something confused by the warning in "/etc/sbopkg/repos.d/40-sbo.repo". But it's alright.

I am currently using sbopkg with the SBo-git/current repository. Is it safe to keep it that way on 14 or should I change that to the 14 repo?

I'll usually rebase SBo-git/current on slackbuilds.org's git master (the delay is some hours at max) so you will have that stuff plus the needed updates for -current for the stuff I use, so it's safe to use that if you use -current.

If you stay on 14.0, you are better off with the settings above (or with the ones to follow slackbuilds.org's git master branch).

Thanks, I will make the change, these machines will stay at 14, at least for a while.

Quote:

Originally Posted by ponce (Post 4795307)

you can add yourself this line on top of /etc/sbopkg/repos.d/40-sbo.repo

Code:

SBo 14.0 "SBo repository for Slackware 14.0" _SBo rsync slackbuilds.org::slackbuilds/14.0 GPG

then edit /etc/sbopkg/sbopkg.conf and set the variables REPO_BRANCH and REPO_NAME like this

Code:

REPO_BRANCH=${REPO_BRANCH:-14.0}

REPO_NAME=${REPO_NAME:-SBo}

sync

Code:

sbopkg -r

and you're ready to go :)

Thanks!

Quote:

Originally Posted by ponce (Post 4795307)

you can add yourself this line on top of /etc/sbopkg/repos.d/40-sbo.repo

Code:

SBo 14.0 "SBo repository for Slackware 14.0" _SBo rsync slackbuilds.org::slackbuilds/14.0 GPG

then edit /etc/sbopkg/sbopkg.conf and set the variables REPO_BRANCH and REPO_NAME like this

Code:

REPO_BRANCH=${REPO_BRANCH:-14.0}

REPO_NAME=${REPO_NAME:-SBo}

sync

Code:

sbopkg -r

and you're ready to go :)

As an alternate to editing /etc/sbopkg/sbopkg.conf, you can change the version sbopkg uses with

Code:

# sbopkg -V SBo/14.0

This will prompt you to create the repository directory in /var/lib/sbopkg/SBo/14.0 and take you to the ncurses dialog, where you can start to sync the archive to your local repository and check/build and install updates.

Yes, but using like this (with the -V option) it's only for temporary use: if you don't specify the "-V SBo/14.0" also the next time you launch it, it will default to the repository set in /etc/sbopkg/sbopkg.conf (or ~/.sbopkg.conf, if you save your options from the dialog interface).

Is sbopkg still being maintained? It's very feature rich as it is already, but was wondering about the development since I haven't seen much lately.

I would think that sbopkg is feature complete, so a slow development cycle has to be expected. It works fine here, the only thing that bother me a bit is that the queue files are not adapted yet. I have to look into how to maintain them and then maybe volunteer for that. Well, and I have to learn how to work with git, in the first place.

I can't think of any new features to add. Pretty complete.

And as we speak of it slakmagik released a new version: http://www.linuxquestions.org/questi...ed-4175430399/