Removing programes installed from source
- Inicie sesión o regístrese para enviar comentarios
Newbie question: how to remove programs you installed from source with "make install"?
make clean removes any intermediate or output files from your source / build
tree. However, it only affects the source / build tree; it does not touch the
rest of the filesystem and so will not remove previously installed software.
If you're lucky, running make uninstall will work. It's up to the library's
authors to provide that, however; some authors provide an uninstall target,
others don't.
If you're not lucky, you'll have to manually uninstall it. Running make -n
install can be helpful, since it will show the steps that the software would
take to install itself but won't actually do anything. You can then manually
reverse those steps.
--found on Stack Overflow, with my DuckDuckGo-fu
This problem gets adressed by a program called "checkinstall".
If present in the system, you can after "./configure" and "make"
run the command "make checkinstall" instead of "make install".
It creates a .deb package out of your compiled program.
Advantage: you can install it with dpkg -i and easily remove with "sudo apt-get remove packagename".
I have to mention that it's been a while ago since I last used this method.
I'm sure that it's called "checkinstall", but not garuantee about the syntax etc.
One also has to mention that the .deb package that you get is only suitable for your system.
You can't provide it only for others, i guess it won't work (that's what I've read, don't know any details).
"make install" isn't really needed as you can run the program that can
be found in the build directory.
I have been using "checkinstall make install". from the build directory,
note that Checkinstall seems to take the name of the currently working
directory as the package name, so if you normally make directories named
as "build" just to compile things, them you'll sooner or later end up
with package conflicts, and believe me, I have seen many compilation
instructions do so, probably they don't care because they don't instruct
the user to use "checkinstall make install" but just "make install".
I am a translator!
+ 1 Adfeno mate! That's the way I do it. I compile the source and just run the executable from the build directory.
If the archive you downloaded includes a README file or an INSTALL file (or any similarly named file), see if they contain the answer.
Thanks quantum! Checkinstall was just the sort of thing I was looking for.
- Inicie sesión o regístrese para enviar comentarios