You are not logged in.
Pages: 1
How would one uninstall a program that was compiled from source? (Eg: "./configure" then "make")
How's my programming? Call 1-800-DEV-NULL
Offline
/me wonders how many times this has come up....
Try make uninstall. If that doesn't work, use your time machine to go back to before you installed it, and read the README file and any other relevant docs. If you don't have a time machine, reading the README might still help.
Whether any of the above works or not, Write the following on a piece of paper and stick it on top of your monitor:
I WILL NOT INSTALL ANY APPS ON MY SYSTEM WITHOUT FINDING OUT HOW TO REMOVE THEM FIRST
Might be no harm to stick copies of this everywhere you go, just to reinforce the message.
When you are confident that you have learnt your lesson, you can then move on to the sane, common-sense approach i.e. creating Arch packages for the stuff you want to install and installing/removing them with pacman.
Offline
Ok thanks for the tip. I havn't installed stuff in that manner before I just wanted to know in case I do. Sorry for the dumb question, this should have belonged to the newbie corner.
How's my programming? Call 1-800-DEV-NULL
Offline
Also note that you can try to run some programs before running "make install". The compiled binary is in the 'src' folder, try starting it. This way you can test some programs before installing them.
There are two types of people in this world - those who can count to 10 by using their fingers, and those who can count to 1023.
Offline
the way to install something in arch, is to make a PKGBUILD, then makepkg, and then install it using pacman. That way, pacman can also remove it and everything is awesome.
Read this:
http://wiki.archlinux.org/index.php/The … guidelines
http://wiki.archlinux.org/index.php/ABS … _Explained
http://wiki.archlinux.org/index.php/Makepkg
And surprisingly, it's a lot less complicated than it looks! Seriously.
Last edited by Shapeshifter (2009-09-02 18:37:13)
Offline
Installing virtualbox as a test environment is a nice way to keep your system clean, An option besides the above mentioned
Offline
If you know approximately where the files were installed, you can use pacpal to list all unpackaged files in a given location (pacpal --list-unpkgd). You can get pacpal from my repo or from the AUR.
My Arch Linux Stuff • Forum Etiquette • Community Ethos - Arch is not for everyone
Offline
To sum up, make install is evil. Use your distro's method of making packages, or at the very least use checkinstall or similar.
Offline
To sum up, make install is evil. Use your distro's method of making packages, or at the very least use checkinstall or similar.
It's not evil, it's just less efficient.
Also we need it for our build function in pkgbuilds.
Last edited by Acecero (2009-09-03 06:29:44)
Offline
If you are saying "make install" is so bad then how do people live with source based distributions like CRUX?
How's my programming? Call 1-800-DEV-NULL
Offline
If you are saying "make install" is so bad then how do people live with source based distributions like CRUX?
I think you have a basic misunderstanding of what does a "source based distro" mean. It doesn't mean that people using them do 'make install' manually. It means that their package manager compiles the package everytime it's installed/updated, instead of just downloading precompiled binaries (as happens with e.g. pacman).
Offline
Another way is to use the --prefix option when you run the ./configure stage.
For example, I like to compile PostgreSQL from source, and install it using 'make install' so I'm in *total* control (eg, pacman doesn't even know it exists). To do this, I use the --prefix option to install *everything* to do with the package under /usr/local/pg-X.y where X = major and y = minor version (eg, /usr/local/pg-8.3)
This way, not only can I run 2 versions at the same time (eg, testing when a new major version is released), but once I upgrade, I can just rm -Rf /usr/local/pg-8.2 and the old version is gone.
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
Ranguvar wrote:To sum up, make install is evil. Use your distro's method of making packages, or at the very least use checkinstall or similar.
It's not evil, it's just less efficient.
Also we need it for our build function in pkgbuilds.
I have an aversion to things that spew files randomly all over my system We harness make install's power in PKGBUILDs by forcing it into a fakeroot.
Offline
Pages: 1