On 2012-03-30 11:06, hcvv wrote:
>
> When you realy did all the commands as -root-, it is not very important
> what user did the -sudo- commands. You will have polluted -roo-t’s
> environment regardless of what user you were first.
Well, in this case, he did the “make install”, and that can only be done as
root; it is irrelevant how he did run the previous phases.
> And one should of course first find out how to deinstall something
> before one installs.
Unfortunately, most Linux build instructions miss this phase. At least it
was so some years ago when I looked.
> And I would never trust a product where the documentation says that I
> should do the -configure- and -make all -as -root.-
They usually don’t say anything about that. But if they were bad guys, they
would delay any bad action till the make install phase, that has to be run
as root in any case. Install as plain user is normally not even contemplated.
I would run “sudo make uninstall” in any case, even if not documented. Many
programs have it.
A trick to uninstall a program is to create an rpm, using checkinstall. The
sequence is this:
make install
checkinstall
rpm --install whatever
rpm --erase whatever
The first install phase is needed to force creation of directories that
checkinstall fails to create, but needs. It is a reported bug and
corresponding hack.
It is possible that the checkinstall phase fails, something about wrong
spec syntax re requires. The hack is to configure change “REVIEW_SPEC=1” in
/etc/checkinstallrc
Another course of action is to look in /usr/local directory, because most
manuals installs go there. If the OP hasn’t done more installs, it is easy
to find the files. Then, the checkinstall phase above creates a listing of
all files installed.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)