If I build a package from source how can I uninstall or remove completely?How to uninstall a program in...
Why avoid shared user accounts?
Python Pandas - difference between 'loc' and 'where'?
Can we harness potential energy?
How do I draw the dashed lines as shown in this figure
Why is it that Bernie Sanders is always called a "socialist"?
What is a good reason for every spaceship to carry a weapon on board?
Why would space fleets be aligned?
Variable is not visible
Is Krishna the only avatar among dashavatara who had more than one wife?
Is there a lava-breathing lizard creature (that could be worshipped by a cult) in 5e?
Dilemma of explaining to interviewer that he is the reason for declining second interview
Why does magnet wire need to be insulated?
Has Britain negotiated with any other countries outside the EU in preparation for the exit?
What sets the resolution of an analog resistive sensor?
Workflow Comment popup does not show up
How does Leonard in "Memento" remember reading and writing?
How can a large fleets maintain formation in interstellar space?
Do authors have to be politically correct in article-writing?
Why exactly do action photographers need high fps burst cameras?
Potential client has a problematic employee I can't work with
Is it possible to grant users sftp access without shell access? If yes, how is it implemented?
Why is working on the same position for more than 15 years not a red flag?
Square Root Distance from Integers
What is the difference between rolling more dice versus fewer dice?
If I build a package from source how can I uninstall or remove completely?
How to uninstall a program in linux?How to remove application installed from source codeHow to uninstall software that was installed by “make install”How do I Uninstall a Program and Dependencies from a tar.bz2?How to uninstall self compiled binaries?Uninstalling application built from sourceMultiple Python Versions on Ubuntu 15.10 Causing Problemscan't uninstall octaveHow to uninstall redundant python instance?Uninstall a manually installed programSynaptic remove “gedit” wants to remove “ubuntu-desktop”. How can I reinstall “gedit”?./configure error when compiling xgrafix on ubuntu 12.04C compiler cannot create excecutablesCannot build MonoDevelop from sourcemixed installation - how to remove older version of openscenegraphTrying to compile from source newest apache with newest opensslPackage requirements openglucoseHow can I remove a package?How to Remove varicad2013-en (A Virus or PIA)Boost version chaos, how to remove all traces from source build?
I used source code to build one package such as below:
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libexecdir=/usr/lib --with-package-name="Myplugin" --with-package-origin="http://www.ubuntu.org/" --enable-gtk-doc --disable-static
make
make install
But unfortunately, i discovered that its the latest version, and has lot of bugs, so i need to remove it/uninstall it. But how can i do so? I tried make clean; make uninstall
but still i see it exist:
# pkg-config --list-all | grep Myplugin
myplugin-....
$ ls /usr/lib/myplugin/libXYZ.so
exist....
How do you remove this now?
package-management uninstall compiling
add a comment |
I used source code to build one package such as below:
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libexecdir=/usr/lib --with-package-name="Myplugin" --with-package-origin="http://www.ubuntu.org/" --enable-gtk-doc --disable-static
make
make install
But unfortunately, i discovered that its the latest version, and has lot of bugs, so i need to remove it/uninstall it. But how can i do so? I tried make clean; make uninstall
but still i see it exist:
# pkg-config --list-all | grep Myplugin
myplugin-....
$ ls /usr/lib/myplugin/libXYZ.so
exist....
How do you remove this now?
package-management uninstall compiling
add a comment |
I used source code to build one package such as below:
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libexecdir=/usr/lib --with-package-name="Myplugin" --with-package-origin="http://www.ubuntu.org/" --enable-gtk-doc --disable-static
make
make install
But unfortunately, i discovered that its the latest version, and has lot of bugs, so i need to remove it/uninstall it. But how can i do so? I tried make clean; make uninstall
but still i see it exist:
# pkg-config --list-all | grep Myplugin
myplugin-....
$ ls /usr/lib/myplugin/libXYZ.so
exist....
How do you remove this now?
package-management uninstall compiling
I used source code to build one package such as below:
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libexecdir=/usr/lib --with-package-name="Myplugin" --with-package-origin="http://www.ubuntu.org/" --enable-gtk-doc --disable-static
make
make install
But unfortunately, i discovered that its the latest version, and has lot of bugs, so i need to remove it/uninstall it. But how can i do so? I tried make clean; make uninstall
but still i see it exist:
# pkg-config --list-all | grep Myplugin
myplugin-....
$ ls /usr/lib/myplugin/libXYZ.so
exist....
How do you remove this now?
package-management uninstall compiling
package-management uninstall compiling
edited Dec 31 '11 at 17:49
Jorge Castro
36.7k106422617
36.7k106422617
asked Dec 12 '11 at 11:42
YumYumYumYumYumYum
4,5373286133
4,5373286133
add a comment |
add a comment |
7 Answers
7
active
oldest
votes
Usually you can just use:
make uninstall
or
sudo make uninstall
if the app was installed as root.
But this will work only if the developer of the package has taken care of making a good uninstall rule.
You can also try to get a look at the steps used to install the software by running:
make -n install
And then try to reverse those steps manually.
In the future to avoid that kind of problems try to use checkinstall
instead of make install
whenever possible (AFAIK always unless you want to keep both the compiled and a packaged version at the same time). It will create and install a deb file that you can then uninstall using your favorite package manager.
make clean
usually cleans the building directories, it doesn't uninstall the package. It's used when you want to be sure that the whole thing is compiled, not just the changed files.
I did that too. But still it exist, as shown pkg-config and ls /usr/lib/myplugin/libXYZ.so
– YumYumYum
Dec 12 '11 at 11:54
30
+1 for usingcheckinstall
- it makes this whole problem evaporate.
– Oli♦
Dec 12 '11 at 12:00
6
@Google: If make uninstall doesn't work, you'll need to track what make install did and undo it manually.
– Javier Rivera
Dec 12 '11 at 12:42
4
Another thing to keep in mind is that ifmake install
was run as root (e.g.,sudo make install
), which is typically the case, it's virtual always necessary to runsudo make uninstall
to remove the software.
– Eliah Kagan
Jul 9 '13 at 1:46
3
If you have already runmake install
, you can still usecheckinstall
. Normallycheckinstall
will overwrite everything thatmake install
created. After that just usedpkg -r <package.deb>
, and everything should be removed.
– user502144
Oct 15 '17 at 18:00
|
show 3 more comments
I do not think this is a bug, it would be a good idea to read about and learn to use checkinstall when installing from source.
you can install checkinstall from the repositories, a short description of the package;
CheckInstall keeps track of all the files created or
modified by your installation script ("make install"
"make install_modules", "setup", etc), builds a
standard binary package and installs it in your
system giving you the ability to uninstall it with your
distribution's standard package management utilities.
These links below may be helpful to get a better understanding.
http://en.wikipedia.org/wiki/CheckInstall
http://checkinstall.izto.org/
add a comment |
This is not a bug - compiling from source is an unsupported method of installing software that bypasses the package management system (which is used by the Software Centre) completely.
There is no standard way that software compiled from source is installed or uninstalled so no way Ubuntu can know what to do. The software is not even listed as an installed program.
You should follow the distributor's instructions for installation and removal of such custom software. You could also contact the developer to ask for them to create a Debian package so that the package management system can be used.
add a comment |
It is not a bug, it is what happens when developers resort to distribution via source and not via the native packaging methods.
You can get your source files to become debian packages by using checkinstall or dhbuild.
Honestly, in my opinion - new users should avoid installing from source, and developers should avoid distributing by source only.
I know but sometimes it is unavoidable...In this case it was just a small game which is not really necessary but sometime back I had to install MATLAB a computational tool used in my university and had to install it by the source since they did not have a deb file for ubuntu...But I will definitely go through the methods checkinstall and dhbuild...thanks
– nik90
Jan 20 '11 at 22:44
add a comment |
We need to negotiate the fact that make uninstall would not always work, so below
is more of a proactive solution.
This involves the use of the paco program
which is available in the Ubuntu Software Center. Once we have installed paco,
we can use it the log mode when we "make install" a program. Paco acts like a wrapper for your "make install" and creates a log in the /var/log/paco directory with the list of files copied to various directories. Moreover, you could see the the files in the Paco Front end.
For example when I compiled php from source I did the following :
paco -lp php5 "make install"
The parameter l makes the paco run in the log mode.This created a log file in /var/log/paco named php5 (the name I have given in the command). It contained all the files which are copied to various standard locations during the install. You could use a command line editor or paco gui to view the files.
Below is the example of getting
the file list using sed command line editor
(Replace php5 with your filename).
cat /var/log/paco/php5 | sed -n 's/|(.*)//;/^#(.*)/d;p'
Once you got the list of the files, you know how to delete them don't you? Indeed, you could pass the results of the above command to rm using backticks like shown below:
sudo rm `cat /var/log/paco/php5 | sed -n 's/|(.*)//;/^#(.*)/d;p'`
Job done!
Note : Due to LD_PRELOAD limitations, paco can't follow the trace of suid programs. See man page.
add a comment |
I had compiled php-5.6.30 from source without configuring it with openssl, so I had to go back and install it from scratch.Using make uninstall did not work as the Makefile for php doesn't support it.
However, this step worked for me, - I listed all the files related to php and removed them manually, it took me about 5 minutes without breaking a sweat. You can similarly use these steps to uninstall your compiled software.
Replace php with the software you need to uninstall
whereis php
The above command lists directories where the binaries are installed ex: /usr/local/bin/php, /usr/bin/php .. remove each file/directory listed in your output.
sudo rm -f /usr/local/bin/php
Do this with all the files listed in the above output and you are all set to install the newer version from scratch.
add a comment |
I know of few packages that support "make uninstall" but many more that support make install DESTDIR=xxx" for staged installs.
You can use this to create a package which you install instead of installing directly from the source. I had no luck with checkinstall but fpm works very well.
This can also help you remove a package previously installed using make install. You simply force install your built package over the make installed one and then uninstall it.
For example, I used this recently to deal with protobuf-3.3.0.
On RHEL7:
make install DESTDIR=dest
cd dest
fpm -f -s dir -t rpm -n protobuf -v 3.3.0
--vendor "You Not RedHat"
--license "Google?"
--description "protocol buffers"
--rpm-dist el7
-m you@youraddress.com
--url "http:/somewhere/where/you/get/the/package/oritssource"
--rpm-autoreqprov
usr
sudo rpm -i -f protobuf-3.3.0-1.el7.x86_64.rpm
sudo rpm -e protobuf-3.3.0
Prefer yum to rpm if you can.
On Debian9:
make install DESTDIR=dest
cd dest
fpm -f -s dir -t deb -n protobuf -v 3.3.0
-C `pwd`
--prefix /
--vendor "You Not Debian"
--license "$(grep Copyright ../../LICENSE)"
--description "$(cat README.adoc)"
--deb-upstream-changelog ../../CHANGES.txt
--url "http:/somewhere/where/you/get/the/package/oritssource"
usr/local/bin
usr/local/lib
usr/local/include
sudo apt install -f *.deb
sudo apt-get remove protobuf
Prefer apt to dpkg where you can.
I've also posted this answer on stackoverflow
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f87111%2fif-i-build-a-package-from-source-how-can-i-uninstall-or-remove-completely%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
7 Answers
7
active
oldest
votes
7 Answers
7
active
oldest
votes
active
oldest
votes
active
oldest
votes
Usually you can just use:
make uninstall
or
sudo make uninstall
if the app was installed as root.
But this will work only if the developer of the package has taken care of making a good uninstall rule.
You can also try to get a look at the steps used to install the software by running:
make -n install
And then try to reverse those steps manually.
In the future to avoid that kind of problems try to use checkinstall
instead of make install
whenever possible (AFAIK always unless you want to keep both the compiled and a packaged version at the same time). It will create and install a deb file that you can then uninstall using your favorite package manager.
make clean
usually cleans the building directories, it doesn't uninstall the package. It's used when you want to be sure that the whole thing is compiled, not just the changed files.
I did that too. But still it exist, as shown pkg-config and ls /usr/lib/myplugin/libXYZ.so
– YumYumYum
Dec 12 '11 at 11:54
30
+1 for usingcheckinstall
- it makes this whole problem evaporate.
– Oli♦
Dec 12 '11 at 12:00
6
@Google: If make uninstall doesn't work, you'll need to track what make install did and undo it manually.
– Javier Rivera
Dec 12 '11 at 12:42
4
Another thing to keep in mind is that ifmake install
was run as root (e.g.,sudo make install
), which is typically the case, it's virtual always necessary to runsudo make uninstall
to remove the software.
– Eliah Kagan
Jul 9 '13 at 1:46
3
If you have already runmake install
, you can still usecheckinstall
. Normallycheckinstall
will overwrite everything thatmake install
created. After that just usedpkg -r <package.deb>
, and everything should be removed.
– user502144
Oct 15 '17 at 18:00
|
show 3 more comments
Usually you can just use:
make uninstall
or
sudo make uninstall
if the app was installed as root.
But this will work only if the developer of the package has taken care of making a good uninstall rule.
You can also try to get a look at the steps used to install the software by running:
make -n install
And then try to reverse those steps manually.
In the future to avoid that kind of problems try to use checkinstall
instead of make install
whenever possible (AFAIK always unless you want to keep both the compiled and a packaged version at the same time). It will create and install a deb file that you can then uninstall using your favorite package manager.
make clean
usually cleans the building directories, it doesn't uninstall the package. It's used when you want to be sure that the whole thing is compiled, not just the changed files.
I did that too. But still it exist, as shown pkg-config and ls /usr/lib/myplugin/libXYZ.so
– YumYumYum
Dec 12 '11 at 11:54
30
+1 for usingcheckinstall
- it makes this whole problem evaporate.
– Oli♦
Dec 12 '11 at 12:00
6
@Google: If make uninstall doesn't work, you'll need to track what make install did and undo it manually.
– Javier Rivera
Dec 12 '11 at 12:42
4
Another thing to keep in mind is that ifmake install
was run as root (e.g.,sudo make install
), which is typically the case, it's virtual always necessary to runsudo make uninstall
to remove the software.
– Eliah Kagan
Jul 9 '13 at 1:46
3
If you have already runmake install
, you can still usecheckinstall
. Normallycheckinstall
will overwrite everything thatmake install
created. After that just usedpkg -r <package.deb>
, and everything should be removed.
– user502144
Oct 15 '17 at 18:00
|
show 3 more comments
Usually you can just use:
make uninstall
or
sudo make uninstall
if the app was installed as root.
But this will work only if the developer of the package has taken care of making a good uninstall rule.
You can also try to get a look at the steps used to install the software by running:
make -n install
And then try to reverse those steps manually.
In the future to avoid that kind of problems try to use checkinstall
instead of make install
whenever possible (AFAIK always unless you want to keep both the compiled and a packaged version at the same time). It will create and install a deb file that you can then uninstall using your favorite package manager.
make clean
usually cleans the building directories, it doesn't uninstall the package. It's used when you want to be sure that the whole thing is compiled, not just the changed files.
Usually you can just use:
make uninstall
or
sudo make uninstall
if the app was installed as root.
But this will work only if the developer of the package has taken care of making a good uninstall rule.
You can also try to get a look at the steps used to install the software by running:
make -n install
And then try to reverse those steps manually.
In the future to avoid that kind of problems try to use checkinstall
instead of make install
whenever possible (AFAIK always unless you want to keep both the compiled and a packaged version at the same time). It will create and install a deb file that you can then uninstall using your favorite package manager.
make clean
usually cleans the building directories, it doesn't uninstall the package. It's used when you want to be sure that the whole thing is compiled, not just the changed files.
edited May 29 '17 at 0:51
Ashhar Hasan
494725
494725
answered Dec 12 '11 at 11:49
Javier RiveraJavier Rivera
30k978101
30k978101
I did that too. But still it exist, as shown pkg-config and ls /usr/lib/myplugin/libXYZ.so
– YumYumYum
Dec 12 '11 at 11:54
30
+1 for usingcheckinstall
- it makes this whole problem evaporate.
– Oli♦
Dec 12 '11 at 12:00
6
@Google: If make uninstall doesn't work, you'll need to track what make install did and undo it manually.
– Javier Rivera
Dec 12 '11 at 12:42
4
Another thing to keep in mind is that ifmake install
was run as root (e.g.,sudo make install
), which is typically the case, it's virtual always necessary to runsudo make uninstall
to remove the software.
– Eliah Kagan
Jul 9 '13 at 1:46
3
If you have already runmake install
, you can still usecheckinstall
. Normallycheckinstall
will overwrite everything thatmake install
created. After that just usedpkg -r <package.deb>
, and everything should be removed.
– user502144
Oct 15 '17 at 18:00
|
show 3 more comments
I did that too. But still it exist, as shown pkg-config and ls /usr/lib/myplugin/libXYZ.so
– YumYumYum
Dec 12 '11 at 11:54
30
+1 for usingcheckinstall
- it makes this whole problem evaporate.
– Oli♦
Dec 12 '11 at 12:00
6
@Google: If make uninstall doesn't work, you'll need to track what make install did and undo it manually.
– Javier Rivera
Dec 12 '11 at 12:42
4
Another thing to keep in mind is that ifmake install
was run as root (e.g.,sudo make install
), which is typically the case, it's virtual always necessary to runsudo make uninstall
to remove the software.
– Eliah Kagan
Jul 9 '13 at 1:46
3
If you have already runmake install
, you can still usecheckinstall
. Normallycheckinstall
will overwrite everything thatmake install
created. After that just usedpkg -r <package.deb>
, and everything should be removed.
– user502144
Oct 15 '17 at 18:00
I did that too. But still it exist, as shown pkg-config and ls /usr/lib/myplugin/libXYZ.so
– YumYumYum
Dec 12 '11 at 11:54
I did that too. But still it exist, as shown pkg-config and ls /usr/lib/myplugin/libXYZ.so
– YumYumYum
Dec 12 '11 at 11:54
30
30
+1 for using
checkinstall
- it makes this whole problem evaporate.– Oli♦
Dec 12 '11 at 12:00
+1 for using
checkinstall
- it makes this whole problem evaporate.– Oli♦
Dec 12 '11 at 12:00
6
6
@Google: If make uninstall doesn't work, you'll need to track what make install did and undo it manually.
– Javier Rivera
Dec 12 '11 at 12:42
@Google: If make uninstall doesn't work, you'll need to track what make install did and undo it manually.
– Javier Rivera
Dec 12 '11 at 12:42
4
4
Another thing to keep in mind is that if
make install
was run as root (e.g., sudo make install
), which is typically the case, it's virtual always necessary to run sudo make uninstall
to remove the software.– Eliah Kagan
Jul 9 '13 at 1:46
Another thing to keep in mind is that if
make install
was run as root (e.g., sudo make install
), which is typically the case, it's virtual always necessary to run sudo make uninstall
to remove the software.– Eliah Kagan
Jul 9 '13 at 1:46
3
3
If you have already run
make install
, you can still use checkinstall
. Normally checkinstall
will overwrite everything that make install
created. After that just use dpkg -r <package.deb>
, and everything should be removed.– user502144
Oct 15 '17 at 18:00
If you have already run
make install
, you can still use checkinstall
. Normally checkinstall
will overwrite everything that make install
created. After that just use dpkg -r <package.deb>
, and everything should be removed.– user502144
Oct 15 '17 at 18:00
|
show 3 more comments
I do not think this is a bug, it would be a good idea to read about and learn to use checkinstall when installing from source.
you can install checkinstall from the repositories, a short description of the package;
CheckInstall keeps track of all the files created or
modified by your installation script ("make install"
"make install_modules", "setup", etc), builds a
standard binary package and installs it in your
system giving you the ability to uninstall it with your
distribution's standard package management utilities.
These links below may be helpful to get a better understanding.
http://en.wikipedia.org/wiki/CheckInstall
http://checkinstall.izto.org/
add a comment |
I do not think this is a bug, it would be a good idea to read about and learn to use checkinstall when installing from source.
you can install checkinstall from the repositories, a short description of the package;
CheckInstall keeps track of all the files created or
modified by your installation script ("make install"
"make install_modules", "setup", etc), builds a
standard binary package and installs it in your
system giving you the ability to uninstall it with your
distribution's standard package management utilities.
These links below may be helpful to get a better understanding.
http://en.wikipedia.org/wiki/CheckInstall
http://checkinstall.izto.org/
add a comment |
I do not think this is a bug, it would be a good idea to read about and learn to use checkinstall when installing from source.
you can install checkinstall from the repositories, a short description of the package;
CheckInstall keeps track of all the files created or
modified by your installation script ("make install"
"make install_modules", "setup", etc), builds a
standard binary package and installs it in your
system giving you the ability to uninstall it with your
distribution's standard package management utilities.
These links below may be helpful to get a better understanding.
http://en.wikipedia.org/wiki/CheckInstall
http://checkinstall.izto.org/
I do not think this is a bug, it would be a good idea to read about and learn to use checkinstall when installing from source.
you can install checkinstall from the repositories, a short description of the package;
CheckInstall keeps track of all the files created or
modified by your installation script ("make install"
"make install_modules", "setup", etc), builds a
standard binary package and installs it in your
system giving you the ability to uninstall it with your
distribution's standard package management utilities.
These links below may be helpful to get a better understanding.
http://en.wikipedia.org/wiki/CheckInstall
http://checkinstall.izto.org/
answered Jan 20 '11 at 22:36
SabaconSabacon
26.1k42839
26.1k42839
add a comment |
add a comment |
This is not a bug - compiling from source is an unsupported method of installing software that bypasses the package management system (which is used by the Software Centre) completely.
There is no standard way that software compiled from source is installed or uninstalled so no way Ubuntu can know what to do. The software is not even listed as an installed program.
You should follow the distributor's instructions for installation and removal of such custom software. You could also contact the developer to ask for them to create a Debian package so that the package management system can be used.
add a comment |
This is not a bug - compiling from source is an unsupported method of installing software that bypasses the package management system (which is used by the Software Centre) completely.
There is no standard way that software compiled from source is installed or uninstalled so no way Ubuntu can know what to do. The software is not even listed as an installed program.
You should follow the distributor's instructions for installation and removal of such custom software. You could also contact the developer to ask for them to create a Debian package so that the package management system can be used.
add a comment |
This is not a bug - compiling from source is an unsupported method of installing software that bypasses the package management system (which is used by the Software Centre) completely.
There is no standard way that software compiled from source is installed or uninstalled so no way Ubuntu can know what to do. The software is not even listed as an installed program.
You should follow the distributor's instructions for installation and removal of such custom software. You could also contact the developer to ask for them to create a Debian package so that the package management system can be used.
This is not a bug - compiling from source is an unsupported method of installing software that bypasses the package management system (which is used by the Software Centre) completely.
There is no standard way that software compiled from source is installed or uninstalled so no way Ubuntu can know what to do. The software is not even listed as an installed program.
You should follow the distributor's instructions for installation and removal of such custom software. You could also contact the developer to ask for them to create a Debian package so that the package management system can be used.
answered Jan 20 '11 at 22:38
dv3500eadv3500ea
28.9k1289143
28.9k1289143
add a comment |
add a comment |
It is not a bug, it is what happens when developers resort to distribution via source and not via the native packaging methods.
You can get your source files to become debian packages by using checkinstall or dhbuild.
Honestly, in my opinion - new users should avoid installing from source, and developers should avoid distributing by source only.
I know but sometimes it is unavoidable...In this case it was just a small game which is not really necessary but sometime back I had to install MATLAB a computational tool used in my university and had to install it by the source since they did not have a deb file for ubuntu...But I will definitely go through the methods checkinstall and dhbuild...thanks
– nik90
Jan 20 '11 at 22:44
add a comment |
It is not a bug, it is what happens when developers resort to distribution via source and not via the native packaging methods.
You can get your source files to become debian packages by using checkinstall or dhbuild.
Honestly, in my opinion - new users should avoid installing from source, and developers should avoid distributing by source only.
I know but sometimes it is unavoidable...In this case it was just a small game which is not really necessary but sometime back I had to install MATLAB a computational tool used in my university and had to install it by the source since they did not have a deb file for ubuntu...But I will definitely go through the methods checkinstall and dhbuild...thanks
– nik90
Jan 20 '11 at 22:44
add a comment |
It is not a bug, it is what happens when developers resort to distribution via source and not via the native packaging methods.
You can get your source files to become debian packages by using checkinstall or dhbuild.
Honestly, in my opinion - new users should avoid installing from source, and developers should avoid distributing by source only.
It is not a bug, it is what happens when developers resort to distribution via source and not via the native packaging methods.
You can get your source files to become debian packages by using checkinstall or dhbuild.
Honestly, in my opinion - new users should avoid installing from source, and developers should avoid distributing by source only.
answered Jan 20 '11 at 22:36
RolandiXor♦RolandiXor
44.6k25140231
44.6k25140231
I know but sometimes it is unavoidable...In this case it was just a small game which is not really necessary but sometime back I had to install MATLAB a computational tool used in my university and had to install it by the source since they did not have a deb file for ubuntu...But I will definitely go through the methods checkinstall and dhbuild...thanks
– nik90
Jan 20 '11 at 22:44
add a comment |
I know but sometimes it is unavoidable...In this case it was just a small game which is not really necessary but sometime back I had to install MATLAB a computational tool used in my university and had to install it by the source since they did not have a deb file for ubuntu...But I will definitely go through the methods checkinstall and dhbuild...thanks
– nik90
Jan 20 '11 at 22:44
I know but sometimes it is unavoidable...In this case it was just a small game which is not really necessary but sometime back I had to install MATLAB a computational tool used in my university and had to install it by the source since they did not have a deb file for ubuntu...But I will definitely go through the methods checkinstall and dhbuild...thanks
– nik90
Jan 20 '11 at 22:44
I know but sometimes it is unavoidable...In this case it was just a small game which is not really necessary but sometime back I had to install MATLAB a computational tool used in my university and had to install it by the source since they did not have a deb file for ubuntu...But I will definitely go through the methods checkinstall and dhbuild...thanks
– nik90
Jan 20 '11 at 22:44
add a comment |
We need to negotiate the fact that make uninstall would not always work, so below
is more of a proactive solution.
This involves the use of the paco program
which is available in the Ubuntu Software Center. Once we have installed paco,
we can use it the log mode when we "make install" a program. Paco acts like a wrapper for your "make install" and creates a log in the /var/log/paco directory with the list of files copied to various directories. Moreover, you could see the the files in the Paco Front end.
For example when I compiled php from source I did the following :
paco -lp php5 "make install"
The parameter l makes the paco run in the log mode.This created a log file in /var/log/paco named php5 (the name I have given in the command). It contained all the files which are copied to various standard locations during the install. You could use a command line editor or paco gui to view the files.
Below is the example of getting
the file list using sed command line editor
(Replace php5 with your filename).
cat /var/log/paco/php5 | sed -n 's/|(.*)//;/^#(.*)/d;p'
Once you got the list of the files, you know how to delete them don't you? Indeed, you could pass the results of the above command to rm using backticks like shown below:
sudo rm `cat /var/log/paco/php5 | sed -n 's/|(.*)//;/^#(.*)/d;p'`
Job done!
Note : Due to LD_PRELOAD limitations, paco can't follow the trace of suid programs. See man page.
add a comment |
We need to negotiate the fact that make uninstall would not always work, so below
is more of a proactive solution.
This involves the use of the paco program
which is available in the Ubuntu Software Center. Once we have installed paco,
we can use it the log mode when we "make install" a program. Paco acts like a wrapper for your "make install" and creates a log in the /var/log/paco directory with the list of files copied to various directories. Moreover, you could see the the files in the Paco Front end.
For example when I compiled php from source I did the following :
paco -lp php5 "make install"
The parameter l makes the paco run in the log mode.This created a log file in /var/log/paco named php5 (the name I have given in the command). It contained all the files which are copied to various standard locations during the install. You could use a command line editor or paco gui to view the files.
Below is the example of getting
the file list using sed command line editor
(Replace php5 with your filename).
cat /var/log/paco/php5 | sed -n 's/|(.*)//;/^#(.*)/d;p'
Once you got the list of the files, you know how to delete them don't you? Indeed, you could pass the results of the above command to rm using backticks like shown below:
sudo rm `cat /var/log/paco/php5 | sed -n 's/|(.*)//;/^#(.*)/d;p'`
Job done!
Note : Due to LD_PRELOAD limitations, paco can't follow the trace of suid programs. See man page.
add a comment |
We need to negotiate the fact that make uninstall would not always work, so below
is more of a proactive solution.
This involves the use of the paco program
which is available in the Ubuntu Software Center. Once we have installed paco,
we can use it the log mode when we "make install" a program. Paco acts like a wrapper for your "make install" and creates a log in the /var/log/paco directory with the list of files copied to various directories. Moreover, you could see the the files in the Paco Front end.
For example when I compiled php from source I did the following :
paco -lp php5 "make install"
The parameter l makes the paco run in the log mode.This created a log file in /var/log/paco named php5 (the name I have given in the command). It contained all the files which are copied to various standard locations during the install. You could use a command line editor or paco gui to view the files.
Below is the example of getting
the file list using sed command line editor
(Replace php5 with your filename).
cat /var/log/paco/php5 | sed -n 's/|(.*)//;/^#(.*)/d;p'
Once you got the list of the files, you know how to delete them don't you? Indeed, you could pass the results of the above command to rm using backticks like shown below:
sudo rm `cat /var/log/paco/php5 | sed -n 's/|(.*)//;/^#(.*)/d;p'`
Job done!
Note : Due to LD_PRELOAD limitations, paco can't follow the trace of suid programs. See man page.
We need to negotiate the fact that make uninstall would not always work, so below
is more of a proactive solution.
This involves the use of the paco program
which is available in the Ubuntu Software Center. Once we have installed paco,
we can use it the log mode when we "make install" a program. Paco acts like a wrapper for your "make install" and creates a log in the /var/log/paco directory with the list of files copied to various directories. Moreover, you could see the the files in the Paco Front end.
For example when I compiled php from source I did the following :
paco -lp php5 "make install"
The parameter l makes the paco run in the log mode.This created a log file in /var/log/paco named php5 (the name I have given in the command). It contained all the files which are copied to various standard locations during the install. You could use a command line editor or paco gui to view the files.
Below is the example of getting
the file list using sed command line editor
(Replace php5 with your filename).
cat /var/log/paco/php5 | sed -n 's/|(.*)//;/^#(.*)/d;p'
Once you got the list of the files, you know how to delete them don't you? Indeed, you could pass the results of the above command to rm using backticks like shown below:
sudo rm `cat /var/log/paco/php5 | sed -n 's/|(.*)//;/^#(.*)/d;p'`
Job done!
Note : Due to LD_PRELOAD limitations, paco can't follow the trace of suid programs. See man page.
edited Mar 9 '15 at 19:13
answered Mar 9 '15 at 12:56
sjsamsjsam
1035
1035
add a comment |
add a comment |
I had compiled php-5.6.30 from source without configuring it with openssl, so I had to go back and install it from scratch.Using make uninstall did not work as the Makefile for php doesn't support it.
However, this step worked for me, - I listed all the files related to php and removed them manually, it took me about 5 minutes without breaking a sweat. You can similarly use these steps to uninstall your compiled software.
Replace php with the software you need to uninstall
whereis php
The above command lists directories where the binaries are installed ex: /usr/local/bin/php, /usr/bin/php .. remove each file/directory listed in your output.
sudo rm -f /usr/local/bin/php
Do this with all the files listed in the above output and you are all set to install the newer version from scratch.
add a comment |
I had compiled php-5.6.30 from source without configuring it with openssl, so I had to go back and install it from scratch.Using make uninstall did not work as the Makefile for php doesn't support it.
However, this step worked for me, - I listed all the files related to php and removed them manually, it took me about 5 minutes without breaking a sweat. You can similarly use these steps to uninstall your compiled software.
Replace php with the software you need to uninstall
whereis php
The above command lists directories where the binaries are installed ex: /usr/local/bin/php, /usr/bin/php .. remove each file/directory listed in your output.
sudo rm -f /usr/local/bin/php
Do this with all the files listed in the above output and you are all set to install the newer version from scratch.
add a comment |
I had compiled php-5.6.30 from source without configuring it with openssl, so I had to go back and install it from scratch.Using make uninstall did not work as the Makefile for php doesn't support it.
However, this step worked for me, - I listed all the files related to php and removed them manually, it took me about 5 minutes without breaking a sweat. You can similarly use these steps to uninstall your compiled software.
Replace php with the software you need to uninstall
whereis php
The above command lists directories where the binaries are installed ex: /usr/local/bin/php, /usr/bin/php .. remove each file/directory listed in your output.
sudo rm -f /usr/local/bin/php
Do this with all the files listed in the above output and you are all set to install the newer version from scratch.
I had compiled php-5.6.30 from source without configuring it with openssl, so I had to go back and install it from scratch.Using make uninstall did not work as the Makefile for php doesn't support it.
However, this step worked for me, - I listed all the files related to php and removed them manually, it took me about 5 minutes without breaking a sweat. You can similarly use these steps to uninstall your compiled software.
Replace php with the software you need to uninstall
whereis php
The above command lists directories where the binaries are installed ex: /usr/local/bin/php, /usr/bin/php .. remove each file/directory listed in your output.
sudo rm -f /usr/local/bin/php
Do this with all the files listed in the above output and you are all set to install the newer version from scratch.
answered Apr 3 '18 at 19:25
AbhinayAbhinay
1
1
add a comment |
add a comment |
I know of few packages that support "make uninstall" but many more that support make install DESTDIR=xxx" for staged installs.
You can use this to create a package which you install instead of installing directly from the source. I had no luck with checkinstall but fpm works very well.
This can also help you remove a package previously installed using make install. You simply force install your built package over the make installed one and then uninstall it.
For example, I used this recently to deal with protobuf-3.3.0.
On RHEL7:
make install DESTDIR=dest
cd dest
fpm -f -s dir -t rpm -n protobuf -v 3.3.0
--vendor "You Not RedHat"
--license "Google?"
--description "protocol buffers"
--rpm-dist el7
-m you@youraddress.com
--url "http:/somewhere/where/you/get/the/package/oritssource"
--rpm-autoreqprov
usr
sudo rpm -i -f protobuf-3.3.0-1.el7.x86_64.rpm
sudo rpm -e protobuf-3.3.0
Prefer yum to rpm if you can.
On Debian9:
make install DESTDIR=dest
cd dest
fpm -f -s dir -t deb -n protobuf -v 3.3.0
-C `pwd`
--prefix /
--vendor "You Not Debian"
--license "$(grep Copyright ../../LICENSE)"
--description "$(cat README.adoc)"
--deb-upstream-changelog ../../CHANGES.txt
--url "http:/somewhere/where/you/get/the/package/oritssource"
usr/local/bin
usr/local/lib
usr/local/include
sudo apt install -f *.deb
sudo apt-get remove protobuf
Prefer apt to dpkg where you can.
I've also posted this answer on stackoverflow
add a comment |
I know of few packages that support "make uninstall" but many more that support make install DESTDIR=xxx" for staged installs.
You can use this to create a package which you install instead of installing directly from the source. I had no luck with checkinstall but fpm works very well.
This can also help you remove a package previously installed using make install. You simply force install your built package over the make installed one and then uninstall it.
For example, I used this recently to deal with protobuf-3.3.0.
On RHEL7:
make install DESTDIR=dest
cd dest
fpm -f -s dir -t rpm -n protobuf -v 3.3.0
--vendor "You Not RedHat"
--license "Google?"
--description "protocol buffers"
--rpm-dist el7
-m you@youraddress.com
--url "http:/somewhere/where/you/get/the/package/oritssource"
--rpm-autoreqprov
usr
sudo rpm -i -f protobuf-3.3.0-1.el7.x86_64.rpm
sudo rpm -e protobuf-3.3.0
Prefer yum to rpm if you can.
On Debian9:
make install DESTDIR=dest
cd dest
fpm -f -s dir -t deb -n protobuf -v 3.3.0
-C `pwd`
--prefix /
--vendor "You Not Debian"
--license "$(grep Copyright ../../LICENSE)"
--description "$(cat README.adoc)"
--deb-upstream-changelog ../../CHANGES.txt
--url "http:/somewhere/where/you/get/the/package/oritssource"
usr/local/bin
usr/local/lib
usr/local/include
sudo apt install -f *.deb
sudo apt-get remove protobuf
Prefer apt to dpkg where you can.
I've also posted this answer on stackoverflow
add a comment |
I know of few packages that support "make uninstall" but many more that support make install DESTDIR=xxx" for staged installs.
You can use this to create a package which you install instead of installing directly from the source. I had no luck with checkinstall but fpm works very well.
This can also help you remove a package previously installed using make install. You simply force install your built package over the make installed one and then uninstall it.
For example, I used this recently to deal with protobuf-3.3.0.
On RHEL7:
make install DESTDIR=dest
cd dest
fpm -f -s dir -t rpm -n protobuf -v 3.3.0
--vendor "You Not RedHat"
--license "Google?"
--description "protocol buffers"
--rpm-dist el7
-m you@youraddress.com
--url "http:/somewhere/where/you/get/the/package/oritssource"
--rpm-autoreqprov
usr
sudo rpm -i -f protobuf-3.3.0-1.el7.x86_64.rpm
sudo rpm -e protobuf-3.3.0
Prefer yum to rpm if you can.
On Debian9:
make install DESTDIR=dest
cd dest
fpm -f -s dir -t deb -n protobuf -v 3.3.0
-C `pwd`
--prefix /
--vendor "You Not Debian"
--license "$(grep Copyright ../../LICENSE)"
--description "$(cat README.adoc)"
--deb-upstream-changelog ../../CHANGES.txt
--url "http:/somewhere/where/you/get/the/package/oritssource"
usr/local/bin
usr/local/lib
usr/local/include
sudo apt install -f *.deb
sudo apt-get remove protobuf
Prefer apt to dpkg where you can.
I've also posted this answer on stackoverflow
I know of few packages that support "make uninstall" but many more that support make install DESTDIR=xxx" for staged installs.
You can use this to create a package which you install instead of installing directly from the source. I had no luck with checkinstall but fpm works very well.
This can also help you remove a package previously installed using make install. You simply force install your built package over the make installed one and then uninstall it.
For example, I used this recently to deal with protobuf-3.3.0.
On RHEL7:
make install DESTDIR=dest
cd dest
fpm -f -s dir -t rpm -n protobuf -v 3.3.0
--vendor "You Not RedHat"
--license "Google?"
--description "protocol buffers"
--rpm-dist el7
-m you@youraddress.com
--url "http:/somewhere/where/you/get/the/package/oritssource"
--rpm-autoreqprov
usr
sudo rpm -i -f protobuf-3.3.0-1.el7.x86_64.rpm
sudo rpm -e protobuf-3.3.0
Prefer yum to rpm if you can.
On Debian9:
make install DESTDIR=dest
cd dest
fpm -f -s dir -t deb -n protobuf -v 3.3.0
-C `pwd`
--prefix /
--vendor "You Not Debian"
--license "$(grep Copyright ../../LICENSE)"
--description "$(cat README.adoc)"
--deb-upstream-changelog ../../CHANGES.txt
--url "http:/somewhere/where/you/get/the/package/oritssource"
usr/local/bin
usr/local/lib
usr/local/include
sudo apt install -f *.deb
sudo apt-get remove protobuf
Prefer apt to dpkg where you can.
I've also posted this answer on stackoverflow
answered 23 mins ago
Bruce AdamsBruce Adams
1063
1063
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f87111%2fif-i-build-a-package-from-source-how-can-i-uninstall-or-remove-completely%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown