Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
It might not have any uninstallation scripts. You could run the installation again and see where it places the files and delete them manually and also check the $PATH variable, if it's added anything there.
Are you in the same directory where you were when you installed it? (the kit)
Which assumes that there is a configuration for that in the sources. And probably a less remember-able method with debpkg (part of the devscripts package). But it makes it easier since you install / uninstall packages with the package manager. And you don't need root until you do that. And you have some sense of "trust" in the package manager. Alternatively never make install and instead use it from the path you compiled it in. It's more tedious but can be made to work for most things.
Otherwise you'll need to manually remove the installed files.
$ make install 2>&1 | tee thelogofoutputtedtext.txt
You'd really need to dissect the makefile to "know" what changed. Or have a filesystem with snapshots or a backup BEFORE you did the install. And compare it to the changes AFTER. Beyond that a fresh and clean install is a way to know it's gone. And standard practice if you have things or situations you don't "trust" affect your machine.
It might not have any uninstallation scripts. You could run the installation again and see where it places the files and delete them manually and also check the $PATH variable, if it's added anything there.
Are you in the same directory where you were when you installed it? (the kit)
the one that did that source make file did not include a rule to make a means to un-install it via make uninstall. you're screwed in that being the way you can now actually remove everything it installed. you will have to manually remove everything yourself.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.