[opensuse] uninstall source
Hello everyone, and welcome to Newbie Question Sunday. I often install packages from source with ./configure, make, make install. Sometimes I'm not happy with the software for whatever reason and I want to get rid of it. I don't actually know how to do this, till now I've always done make clean or make distclean if available, and then deleted the sources. But I installed something the other day that messed up something else, and uninstalling in this manner did not fix the problem. So how does one really fully undo what is done by ./configure, make, make install? To give an example, to solve a claimed dependency by some other software I went and installed iconv ( http://www.gnu.org/software/libiconv/ ). Then when I tried to run man from the command line I got:
man man Reformatting man(1), please wait... iconv: conversion from utf8 unsupported iconv: try 'iconv -l' to get the list of supported encodings
So I "uninstalled" iconv as mentioned above, but the problem didn't go away. to my surprise I found that /usr/local/bin/iconv was still there. If I delete it the problem is solved, so that's ok. The question is that I thought make clean would have got rid of it, and now I wonder what other junk is left lying around from other source packages I've installed and "removed". How does one really uninstall? How do you know if everything's been removed? Sorry if this is embarrassingly basic. Cheers. g -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I often install packages from source with ./configure, make, make install. Sometimes I'm not happy with the software for whatever reason and I want to get rid of it. I don't actually know how to do this, till now I've always done make clean or make distclean if available, and then deleted the sources. But I installed something the other day that messed up something else, and uninstalling in this manner did not fix the problem. So how does one really fully undo what is done by ./configure, make, make install?
As far as I know there's no way to undo the installation. If you delete the sources afterwards the location of the files is totally unknown. You could look for them manually. I'm not an expert to but my way is checkinstall (which is available as rpm). As non-priviliged user you do the ./configure & make install. Then you su to root and checkinstall. This will ask you for the name of your installation and produces a rpm. As root you can install it from /usr/src/RPMS. And if it wasn't the right you just hace to do a rpm -e. Someone mentioned that checkinstall made rpms have disadvantages compared to "real" rpms. Just wanted you to know. As I said I'm not an expert but for me it works fine... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2007-04-29 at 12:28 +0200, Johannes Nohl wrote:
Someone mentioned that checkinstall made rpms have disadvantages compared to "real" rpms. Just wanted you to know. As I said I'm not an expert but for me it works fine...
The way you use it is perfect, no problem. You only see those disadvanges if you plan to distribute those rpms. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGNNnKtTMYHG2NR9URAl0sAKCCy61MNCL/M5CJEgLY5gm4UWvzwACdGGcQ 2nnhWTt2xG19zXHm8BWw1HY= =BF3R -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Johannes Nohl wrote:
I'm not an expert to but my way is checkinstall (which is available as rpm). As non-priviliged user you do the ./configure & make install. Then you su to root and checkinstall. This will ask you for the name of your installation and produces a rpm. As root you can install it from /usr/src/RPMS. And if it wasn't the right you just hace to do a rpm -e. after i tar xzf fuse-2.6.5.tar.gz && cd fuse-2.6.5 && ./configure --enable-kernel-module && make && make install ....(work well => in root mode off course)
then i do your instruction above dwarf:/home/chika/ALPHA/fuse-2.6.5 # checkinstall checkinstall 1.6.0, Copyright 2002 Felipe Eduardo Sanchez Diaz Duran This software is released under the GNU GPL. ************************************** **** RPM package creation selected *** ************************************** This package will be built according to these values: 1 - Summary: [ fuse-2.6.5 ] 2 - Name: [ fuse ] 3 - Version: [ 2.6.5 ] 4 - Release: [ 1 ] 5 - License: [ GPL ] 6 - Group: [ Applications/System ] 7 - Architecture: [ i386 ] 8 - Source location: [ fuse-2.6.5 ] 9 - Alternate source location: [ ] 10 - Requires: [ ] 11 - Provides: [ fuse ] Enter a number to change any of them or press ENTER to continue: Installing with make install... ========================= Installation results =========================== Making install in kernel make[1]: Entering directory `/home/chika/ALPHA/fuse-2.6.5/kernel' make -C /usr/src/linux-2.6.18.8-362 SUBDIRS=`pwd` O=/usr/src/linux-2.6.18.8-362-obj/i386/default modules shell-init: error retrieving current directory: getcwd: cannot access parent directories: Invalid argument chdir: error retrieving current directory: getcwd: cannot access parent directories: Invalid argument /bin/pwd: couldn't find directory entry in `../../../../../..' with matching i-node make[2]: Entering directory `/usr/src/linux-2.6.18.8-362' Makefile:107: *** output directory "/usr/src/linux-2.6.18.8-362-obj/i386/default" does not exist. Stop. make[2]: Leaving directory `/usr/src/linux-2.6.18.8-362' make[1]: *** [all-spec] Error 2 make[1]: Leaving directory `/home/chika/ALPHA/fuse-2.6.5/kernel' make: *** [install-recursive] Error 1 **** Installation failed. Aborting package creation. Cleaning up...OK Bye. am i wrong in doing your clues? is checkinstall always success in all tar.gz? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2007-05-08 at 15:39 +0700, chikaTambun wrote:
after i tar xzf fuse-2.6.5.tar.gz && cd fuse-2.6.5 && ./configure --enable-kernel-module && make && make install ....(work well => in root mode off course)
fuse is suplied in the distro ready to install in rpm form. Why compile it?
am i wrong in doing your clues? is checkinstall always success in all tar.gz?
There are some (few) exceptions. And then, there are errors in those things you try to install or your options or who knows. Anyway, I have never tried checkinstall with the kernel or kernel modules. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGQEZwtTMYHG2NR9URAkuiAJ9xivuxyvSfglm3/6J6SvggGNv/LQCdEuiV RLJczbLQKfmhuM9Fe/Dt6xQ= =VcRf -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
fuse is suplied in the distro ready to install in rpm form. Why compile it?
There are some (few) exceptions. And then, there are errors in those things you try to install or your options or who knows.
Anyway, I have never tried checkinstall with the kernel or kernel modules. don't worry abt that if u want get update for fuse or ntfs-3g u can visit
for update reason(coz there are some new features added), AFAIK there is no problem to compile from source even the developers+community of ntfs-3g developers suggest that way you can google this keyword "Re: [ntfs-3g-devel] Bug report: folders with non-ASCII letters aren't displayed" from: "Udrescu Gabriel sau G@By" <gabi.udr.lin@gmail.com> this is the message: You should consider using the latest ntfs-3g rather than a precompiled rpm pack. it's much better, because openSUSE developers can't keep up with ntfs-3g (or other) developers. even if you prefer Yast or other packmangager, compiling the fuse kernel-module & ntfs-3g is a much better than installing a precompiled pack. I've had a similar problem with PCLinuxOS repos & rpm packs. this http://software.opensuse.org/download/filesystems/openSUSE_10.2/i586/ btw i succeded to checkinstall the latest stable ntfs-3g-1.417 (so i can uninstall it easily if there are problem, but as far i know there isn't major problem) cheers, chikaTambun nb: tell me if u have objection for receiving private message to your account, i do this reason. to give u quick response. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
chika wrote:
fuse is suplied in the distro ready to install in rpm form. Why compile it?
for update reason(coz there are some new features added), AFAIK there is no problem to compile from source even the developers+community of ntfs-3g developers suggest that way
then get the updated RPM. SHEESH! Your problems are self-inflicted, and are getting boring.... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
lists Guillot wrote:
[...] I often install packages from source with ./configure, make, make install. Sometimes I'm not happy with the software for whatever reason and I want to get rid of it. I don't actually know how to do this, till now I've always done make clean or make distclean if available, and then deleted the sources.
This procedure does *not* uninstall the software.
But I installed something the other day that messed up something else, and uninstalling in this manner did not fix the problem. So how does one really fully undo what is done by ./configure, make, make install?
Unless the Makefile provides an "uninstall" target, there is no way to uninstall software that has been installed with "make install". On a system based on RPM package format, you should only install RPM packages and nothing else. Otherwise, the consistency of your RPM database is no longer guaranteed.
[...] So I "uninstalled" iconv as mentioned above, but the problem didn't go away. to my surprise I found that /usr/local/bin/iconv was still there. If I delete it the problem is solved, so that's ok. The question is that I thought make clean would have got rid of it, and now I wonder what other junk is left lying around from other source packages I've installed and "removed".
"make clean" or "make distclean" cleans up the source/build directory. These Makefile targets do not remove anything that has already been installed.
How does one really uninstall? How do you know if everything's been removed?
You should only use RPM packages - these packages can be installed and uninstalled without problems. Either get a ready-to-use RPM package from a repository, or build an RPM package on your system, or (at least) use checkinstall to build an RPM package (instead of using "make install"). Anything else will sooner or later screw up your system. Cheers, Th. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
if u try to ./configure ...."make"..... "make install" (then don't happy with this installation) how abt this... don't delete your configured source (after your ./configure ... make... make install) then do this "make uninstall" the good packages should provide 2 way, how to make it installed n how to make it uninstalled......(am i right??) cheers, chikatambun am i right???
lists Guillot wrote:
[...] I often install packages from source with ./configure, make, make install. Sometimes I'm not happy with the software for whatever reason and I want to get rid of it. I don't actually know how to do this, till now I've always done make clean or make distclean if available, and then deleted the sources.
This procedure does *not* uninstall the software.
But I installed something the other day that messed up something else, and uninstalling in this manner did not fix the problem. So how does one really fully undo what is done by ./configure, make, make install?
Unless the Makefile provides an "uninstall" target, there is no way to uninstall software that has been installed with "make install". On a system based on RPM package format, you should only install RPM packages and nothing else. Otherwise, the consistency of your RPM database is no longer guaranteed.
[...] So I "uninstalled" iconv as mentioned above, but the problem didn't go away. to my surprise I found that /usr/local/bin/iconv was still there. If I delete it the problem is solved, so that's ok. The question is that I thought make clean would have got rid of it, and now I wonder what other junk is left lying around from other source packages I've installed and "removed".
"make clean" or "make distclean" cleans up the source/build directory. These Makefile targets do not remove anything that has already been installed.
How does one really uninstall? How do you know if everything's been removed?
You should only use RPM packages - these packages can be installed and uninstalled without problems. Either get a ready-to-use RPM package from a repository, or build an RPM package on your system, or (at least) use checkinstall to build an RPM package (instead of using "make install"). Anything else will sooner or later screw up your system.
Cheers, Th. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
chika@cs.its.ac.id, please stop sending private emails and reply to the list only. Furthermore, please avoid top-posting. chika@cs.its.ac.id wrote:
if u try to ./configure ...."make"..... "make install" (then don't happy with this installation) how abt this... don't delete your configured source (after your ./configure ... make... make install) then do this "make uninstall"
the good packages should provide 2 way, how to make it installed n how to make it uninstalled......(am i right??)
1.) Most packages do not provide an "uninstall" Makefile target. 2.) Even if a Makefile provides an "uninstall" target, it does not solve the inconsistent RPM database problem. On an RPM-based system, you have to use RPM packages in order to keep your system in a clean state. Anything else should only be used by experts who really know what they are doing... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 29 April 2007, lists Guillot wrote:
Hello everyone, and welcome to Newbie Question Sunday.
I often install packages from source with ./configure, make, make install. Sometimes I'm not happy with the software for whatever reason and I want to get rid of it. I don't actually know how to do this, till now I've always done make clean or make distclean if available, and then deleted the sources. But I installed something the other day that messed up something else, and uninstalling in this manner did not fix the problem. So how does one really fully undo what is done by ./configure, make, make install?
To give an example, to solve a claimed dependency by some other software I went and installed iconv ( http://www.gnu.org/software/libiconv/ ). Then when I tried to run man
from the command line I got:
man man
Reformatting man(1), please wait... iconv: conversion from utf8 unsupported iconv: try 'iconv -l' to get the list of supported encodings
So I "uninstalled" iconv as mentioned above, but the problem didn't go away. to my surprise I found that /usr/local/bin/iconv was still there. If I delete it the problem is solved, so that's ok. The question is that I thought make clean would have got rid of it, and now I wonder what other junk is left lying around from other source packages I've installed and "removed". How does one really uninstall? How do you know if everything's been removed?
Sorry if this is embarrassingly basic. Cheers.
g
============= If you haven't deleted your source directory of the program you installed, I believe you can use "make uninstall" to remove as easily as you installed it. As Thomas pointed out, it would be better to use a rpm file either by using "checkinstall", krpmbuilder or writing your own spec to compile as a rpm. All procedures would make your life and system infinitely easier to maintain. regards, Lee -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2007-04-29 at 12:12 +0200, lists Guillot wrote:
I often install packages from source with ./configure, make, make install.
Use "checkinstall" instead of "make install", and problem solved.
So I "uninstalled" iconv as mentioned above, but the problem didn't go away. to my surprise I found that /usr/local/bin/iconv was still there.
Of course. :-P
If I delete it the problem is solved, so that's ok. The question is that I thought make clean would have got rid of it,
Never.
and now I wonder what other junk is left lying around from other source packages I've installed and "removed".
All of them will be there :-P
How does one really uninstall? How do you know if everything's been removed?
You would have to use "make uninstall", if available. Better still, if you used checkinstall, then just remove the rpm as usual - even using Yast. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGNNqgtTMYHG2NR9URAikqAJ98FwtZoUq30kJ9gnPdDgD4J9R2+wCdFEE/ FX9GRHVrAc7ua4ixTqXlLLY= =nvzC -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (9)
-
Aaron Kulkis -
BandiPat -
Carlos E. R. -
chika -
chika＠cs.its.ac.id
-
chikaTambun
-
Johannes Nohl -
lists Guillot -
Thomas Hertweck