SlackwareThis Forum is for the discussion of Slackware Linux.
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.
I've released src2pkg-2.1 today after fixing a few issues which prevented compilation of the src2pkg-helpers on Slackware-current.
This release includes a very few other changes which have been incorporated over the last 3 weeks since the last release. Anyone running a system with glibc>=2.10 and/or gcc-4.4.x will want to upgrade to this latest release.
New version installed fine and even successfully created a partitionmanager package(how come?!) for me, but after reading Laodiceans post i did 'cat /var/log/packages/src2pkg-helpers-0.9-x86_64-1' and it only listed these files:
I did a reinstall, end keeped an eye better on whole process, it really failed to compile 'tar' here too, on a updated slackware64-current box (without multilib and with old 22.214.171.124 kernel - if it matters:
bash-3.1# src2pkg --setup
Notice - Updating src2pkg-helpers:
Your installed version of src2pkg-helpers needs to
be updated. src2pkg will now compile, package
and install the new version of src2pkg-helpers.
Starting build in 5 seconds
Creating libsentry - OK
Creating tar-1.13 - Failed!
Creating coreutils - chmod: cannot access `/usr/src/src2pkg/builds/src2pkg-helpers/PKG/usr/libexec/src2pkg/bin/cat': Not a directory
chmod: cannot access `/usr/src/src2pkg/builds/src2pkg-helpers/PKG/usr/libexec/src2pkg/bin/chmod': Not a directory
chmod: cannot access `/usr/src/src2pkg/builds/src2pkg-helpers/PKG/usr/libexec/src2pkg/bin/chown': Not a directory
chmod: cannot access `/usr/src/src2pkg/builds/src2pkg-helpers/PKG/usr/libexec/src2pkg/bin/cp': Not a directory
chmod: cannot access `/usr/src/src2pkg/builds/src2pkg-helpers/PKG/usr/libexec/src2pkg/bin/ginstall': Not a directory
chmod: cannot access `/usr/src/src2pkg/builds/src2pkg-helpers/PKG/usr/libexec/src2pkg/bin/groups': Not a directory
chmod: cannot access `/usr/src/src2pkg/builds/src2pkg-helpers/PKG/usr/libexec/src2pkg/bin/link': Not a directory
chmod: cannot access `/usr/src/src2pkg/builds/src2pkg-helpers/PKG/usr/libexec/src2pkg/bin/ln': Not a directory
chmod: cannot access `/usr/src/src2pkg/builds/src2pkg-helpers/PKG/usr/libexec/src2pkg/bin/mkdir': Not a directory
chmod: cannot access `/usr/src/src2pkg/builds/src2pkg-helpers/PKG/usr/libexec/src2pkg/bin/mknod': Not a directory
chmod: cannot access `/usr/src/src2pkg/builds/src2pkg-helpers/PKG/usr/libexec/src2pkg/bin/mv': Not a directory
chmod: cannot access `/usr/src/src2pkg/builds/src2pkg-helpers/PKG/usr/libexec/src2pkg/bin/readlink': Not a directory
chmod: cannot access `/usr/src/src2pkg/builds/src2pkg-helpers/PKG/usr/libexec/src2pkg/bin/rm': Not a directory
chmod: cannot access `/usr/src/src2pkg/builds/src2pkg-helpers/PKG/usr/libexec/src2pkg/bin/rmdir': Not a directory
chmod: cannot access `/usr/src/src2pkg/builds/src2pkg-helpers/PKG/usr/libexec/src2pkg/bin/stat': Not a directory
chmod: cannot access `/usr/src/src2pkg/builds/src2pkg-helpers/PKG/usr/libexec/src2pkg/bin/touch': Not a directory
chmod: cannot access `/usr/src/src2pkg/builds/src2pkg-helpers/PKG/usr/libexec/src2pkg/bin/unlink': Not a directory
/usr/src/src2pkg/src2pkg-helpers/src2pkg.setup: line 167: cd: /usr/src/src2pkg/builds/src2pkg-helpers/PKG/usr/libexec/src2pkg/bin: Not a directory
- Creating Slackware-type tgz package -
Slackware package maker, version 3.14159.
Searching for symbolic links:
No symbolic links were found, so we won't make an installation script.
You can make your own later in ./install/doinst.sh and rebuild the
package if you like.
This next step is optional - you can set the directories in your package
to some sane permissions. If any of the directories in your package have
special permissions, then DO NOT reset them here!
Would you like to reset all directory permissions to 755 (drwxr-xr-x) and
directory ownerships to root.root ([y]es, [n]o)? n
Creating Slackware package: /usr/src/src2pkg/src2pkg-helpers/src2pkg-helpers-0.9-x86_64-1.tgz
Slackware package /usr/src/src2pkg/src2pkg-helpers/src2pkg-helpers-0.9-x86_64-1.tgz created.
Done src2pkg is now ready to use.
Thanks for reporting fellows - ponce has been helping out by running some tests and I think we have found the problem with tar-1.13.
I would like to mention, though, that even if the build fails for src2pkg's 'private' copy of tar-1.13, it will just use the copy already installed with teh Slackware tar package. This is why the src2pkg-helpers build doesn' fail and exit if the build of tar-1.13 fails. And, in fact, the same is true for the build of coreutils-5.2.1 -scr2pkg will just use the normal copies on your system. libsentry is the only thing that is cosidered essential. Even it could be done without, but it would limit the INSTALL_TYPE options of src2pkg. And, src2pkg is set up to not run if libsentry is not found.
I'll send out the latest changes to a couple of those have been testing to make sure we have gotten all the problems resolved before updating and announcing here.
In case you are wondering, the default kernel in Slackware "Current" is the very latest - version 126.96.36.199.
the "get slack" web site lists the latest edition as 13.0, which dates, I don't recall exactly, from last summer, or early Autumn.
It may be worth a minute of time to update the version, once the bugs are worked out, else, to put a one liner at the "get slack" web site, reminding folks who visit the site, that the "current" version, is actually NOT the version described in the most recent issue of distrowatch.
Still working on some errors -this has to work for a wide variety of systems, so it is not so easy and takes some testing. The worst is that I have no 64-bit hardware to test with. I really should break down and buy some 64-bit hardware or setup a qemu installation for the purpose.