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.
When compiling from source, I do not recommend issuing "make install". There is not always option to remove the program afterwards. You'd better make Slackware packages. You can use Slackbuild scripts ( from slackbuilds.og or slacky.eu for instance), gnashley's src2pkg (trackinstall) or checkinstall. After you create a slckware package in this way, you install it via installpkg and then you can remove it by removepkg.
That's why it's best to create a tgz package and install that. Then you can easily remove it with standard tools. Many options exist to create packages. A recent thread discussing this is at http://www.linuxquestions.org/questi...d.php?t=567104.
I tested src2pkg on a random source.tar.gz and got this error:
Quote:
bash-3.1# src2pkg -C razertool_0.0.7.orig.tar.gz
Found source archive: razertool_0.0.7.orig.tar.gz
Deleting old build files - Done
Creating working directories:
PKG_DIR=/tmp/razertool-0.0.7-pkg-1
SRC_DIR=/tmp/razertool-0.0.7-src-1
Unpacking source archive - Done
Correcting source permissions - Done
Checking for patches - None found
Found configure script - Configuring sources using:
CFLAGS=-O2 -march=i486 -mtune=i686 ./configure --prefix=/usr
Configuration has been - Successful!
Compiling sources - Using: 'make'
Compiling has been - Successful!
Tracking Installation - Using: 'make install'
/usr/libexec/src2pkg/FUNCTIONS: line 1463: /usr/libexec/src2pkg/static/cat: No such file or directory
FATAL! Running 'make install' with installwatch produced no files list.
This may be the result of an empty or faulty install rule. Exiting...
/usr/libexec/src2pkg/FUNCTIONS: line 1470: /usr/libexec/src2pkg/static/rm: No such file or directory
/usr/libexec/src2pkg/FUNCTIONS: line 1471: /usr/libexec/src2pkg/static/rm: No such file or directory
src2pkg FAILURE in make_install NO FILES
maybe the package is installed via a command, different from "make install". The installation command is supplied to src2pkg or trackinstall via -i="installation-command". See the INSTALL file of the package and the src2pkg documentation. I usually unpack and configure the package manually, then I compile it and just after that login as root and run trackinstall.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.