Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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.
When I do slackpkg searches, they almost always return nothing. How much compatibility is there for the installation of non-slackware software in tarball format?
Example: I like grsync. It makes rsync much simpler to set up and manage.
slackpkg search grsync - "No package name matches.."
I downloaded the grsync tarball and attempted to compile, but found the following dependencies:
dee-1.0
dbusmenu-glib-0.4
unity
These packages are not available through slackpkg. Is there any point trying to source them elsewhere? Or, am I doomed in my attempt to add some user-level simplicity?
Part of the problem was the Unity dependency. I think this refers to the awful new GUI in some "cool", "user-friendly" distributions. I was able to add --enable-unity=no to the ./config line and lose all of the earlier dependencies.
I'm still not out of the woods, though.
The result of make:
/usr/lib64/gcc/x86_64-slackware-linux/4.7.1/../../../../x86_64-slackware-linux/bin/ld: callbacks.o: undefined reference to symbol 'round@@GLIBC_2.2.5'
/usr/lib64/gcc/x86_64-slackware-linux/4.7.1/../../../../x86_64-slackware-linux/bin/ld: note: 'round@@GLIBC_2.2.5' is defined in DSO /lib64/libm.so.6 so try adding it to the linker command line
I have used "make" many times, sometimes successfully. While I know that linking happens, at this point I have no idea how to access the "linker command line" or precisely what I would add to it. (I just want to install a little app! Shouldn't that be simple?)
I keep hoping that the learning curve for Slackware is worthwhile. I've had better decoding with the Dream Radio application under Slackware than I got under another distro.
Which package did you use: the source or the SlackBuild?
I downloaded the SlackBuild, grsync.tar.gz, expanded it and ran doinst.sh. Nothing happened. Did I do something wrong?
I used the Slackbuild. You need to download the file
Quote:
grsync.tar.gz
and the file
Quote:
grsync-1.2.1.tar.gz
.
I put them in a dir called /home/cliff/src. Any directory in your /home/user will do. The first file has to be unpacked, I do it with ark. If you have a full install, you will have it.
The second file comes from different sources, do not worry about that.
When I untar the first file, I allow it to maintain the same dir structure. Then I move the file with the version number into that dir. ( everything is in one place. )
On my system it looks like this:
Quote:
ls
total 228
drwxr-xr-x 2 cliff users 4096 Apr 24 2011 ./
drwxr-xr-x 93 cliff users 4096 Oct 12 09:51 ../
-rw-r--r-- 1 cliff users 273 May 24 2010 README
-rw-r--r-- 1 cliff users 130 May 24 2010 doinst.sh
-rw-r--r-- 1 cliff users 204566 Apr 24 2011 grsync-0.6.tar.gz
-rwxr-xr-x 1 cliff users 2730 Jun 4 2010 grsync.SlackBuild*
-rw-r--r-- 1 cliff users 276 May 24 2010 grsync.info
-rw-r--r-- 1 cliff users 881 May 24 2010 slack-desc
Now su to root. Type ./grsync.SlackBuild and press enter. The compiler will take off and build your package.
The result will end up in /tmp. After the compile finishes, go to tmp. If you want you can list the file there. One will be the package you install. It is a binary package at this point. You can, if you wish, copy it to the dir you put the other files in. You do not have to. Just type in /tmp dir installpkg nameofthe package and press enter. It will install.
That is it. The reasopn to copy the package back to the dir you create, is if you might want to install it again, later, on the same system, or on another system of the same release and arch; 32 bit or 64 bit. Of course you can always just build it again.
I do recommend you clear /tmp of the files you create with slackbuilds. You can fill up /tmp and cause system problems if you put too much stuff there.
Looking at the timestamps, it seems I figured it out about as fast as you could compose your instructions. But thanks. You mentioned a few things I didn't know.
No problem, now if you want to make your life with Slack slacker.... then take the time to install sbopkg; from here -->http://www.sbopkg.org/
Read the doc on the site. Once you have sbopkg installed, to install packages on slackbuild, you run as root, sbopkg. It takes a little use, easy to use, and it does all the work for you. Now you're slackin...
BTW, you still have to check the pre-req's. With sbopkg you can create install list in the correct order of packages, and install a bunch of packages in the correct order. Makes life much easier.
Last edited by camorri; 12-16-2012 at 03:12 PM.
Reason: fixed spelling.
For deps, you might want to use queuefiles w/sbopkg too.
Then it would be:
Code:
# sbopkg -i <package_name>.queue -k
and all the deps will be installed, and in the proper order.
I'll let you ponder that for a bit, so you look into how to correctly clone the queuefiles from the git repo and prepare sbopkg for use with them. There's gotta be some RTFM'ing or it just ain't like it should be, right?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.