But it turns out this answer is a bit different. I had forgotten about that when I wrote this answer. So I suggest that users installing Bugzilla on newer Ubuntu systems not run those cpan commands until they have actually observed the problem with make not being found even though it's installed.ġ I've posted about this before, apparently. This question is old and the problem may no longer be common. So if you did not already have make and the other necessary development tools, installing build-essential should be sufficient to provide them, though it doesn't substitute for configuring cpan if necessary. Note that the module being referred to here in the script name is a Perl module, and not any other kind of module such as a kernel module. Source: This answer, by 3h4x, to Bugzilla can't find “make” but it's installed and in my path To enter the cpan shell, and then running the CPAN commands: o conf make '/usr/bin/make' You can help cpan find make by running cpan The problem in this situation is that, behind the scenes, uses cpan (a Perl package manager) which doesn't find and use make even though it is installed.ģh4x has given a solution to this. There isn't enough information in the question to be entirely certain that Bugzilla is what's being installed-perhaps there is other software that ships with a script by that name-but the exact problem described here is one that people have had while installing Bugzilla. is an installation script that is part of Bugzilla. What reveals this is the "No targets specified and no makefile found" message, which is produced by make itself. The uninstall target is generated and running sudo make uninstall works to uninstall CMake.As tuxpiper says, make is already installed. To be sure, I tested this with CMake 3.9.0, and it does work. You can also search for uninstall support in its CMakeLists.txt file. $(MAKE) -f CMakeFiles/uninstall.dir/build.make CMakeFiles/uninstall.dir/build $(MAKE) -f CMakeFiles/Makefile2 uninstall # Target rules for targets named uninstall However, CMake itself is designed to be easily uninstalled, and its source code does define those uninstall targets for itself. It would have installed files in the various subdirectories of /usr/local, such as bin and lib (and others), so aside from the situation where you know nothing else was installed into /usr/local, this option requires a lot of work.ġ It's easy to become confused about whether or not you can uninstall CMake by running sudo make uninstall because, by default, when you use CMake to create build scripts for your own software, no uninstall target is generated unless you explicitly ask for one. bootstrap when you compiled CMake then it installed files in /usr/local, but it is not the only program that uses that directory. After running sudo make install again, which would (harmlessly) overwrite the files that were already installed with copies of themselves, you would then be able to use sudo make uninstall.Īnother possible approach, which I strongly discourage you from doing, would be to try to figure out exactly what files and directories were created in the installation, and to try to remove just those files and directories but no others. bootstrap with no arguments after it, do that again. tar.gz file and passing all the same options you used (if any) to. That is, you would follow the same installation steps, starting from the same. If you have deleted the folder in which you ran sudo make install, or otherwise changed it, then your best bet is to rebuild and reinstall it (be sure to use exactly the same version) to get back the ability to run sudo make uninstall. Not all software that can be installed by running make install has a corresponding uninstall target letting you run make uninstall to remove it. Use cd to go back to the directory where you ran that command. Since you installed cmake by compiling it and then running sudo make install, the solution is for you to: Because the version that you have installed now is not provided by Ubuntu's package manager, but instead the version you compiled and installed yourself, running sudo apt-get purge cmake again does not remove it. This is to say that you uninstalled the version provided by Ubuntu's package manager and manually downloaded, compiled, and installed it yourself from source code.Īssuming you were able to follow those instructions successfully, the version of CMake provided by Ubuntu's package manager (via the cmake package) is already uninstalled. You followed this method of installing a different version of CMake. TL DR: Run sudo make uninstall in the directory where you ran sudo make install before.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |