![]() But I've made it community-wiki so other people can edit it more easily and so I don't generate reputation from it. For now I'll keep this answer, which addresses the broader issues like what software this applies to, what kind of modules are being referred to, and how readers shouldn't assume they'll have this problem today. 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. When your installation is completed, you can verify your CMake. Then, you can use the command below to install CMake: sudo apt install cmake. First, update your local package index with the following command: sudo apt update -y. The first way to install CMake is to use the APT repository. This question is old and the problem may no longer be common. Install CMake on Ubuntu 20.04 from APT Repository. 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. See also "/projects/perceptualdiff/perceptualdiff/build/CMakeFiles/CMakeError.log".As tuxpiper says, make is already installed. See also "/projects/perceptualdiff/perceptualdiff/build/CMakeFiles/CMakeOutput.log". Configuring incomplete, errors occurred! To the compiler, or to the compiler name if it is in the PATH. Variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path Tell CMake where to find the compiler by setting either the environment ![]() The CXX compiler identification is unknownĬMake Error at CMakeLists.txt:1 (project): rw-r-r- 1 root root 2889 May 26 21:22 perceptualdiff.cpp rw-r-r- 1 root root 248 May 26 21:22 memcheck.supp rwxr-xr-x 1 root root 450 May 26 21:22 memcheck.bash rwxr-xr-x 1 root root 308 May 26 21:22 coverity.bash rwxr-xr-x 1 root root 535 May 26 21:22 coveralls.bash rwxr-xr-x 1 root root 206 May 26 21:22 coverage.bash rw-r-r- 1 root root 2540 May 26 21:22 FindFreeImage.cmake syntastic_cpp_configĭrwxr-xr-x 8 root root 4096 May 26 21:22. When I enter the directory and type make I get some weird build errors which i'm guessing are related to an incorrectly installed cmake app. The install/build instructions are listed there, which includes cmake. I'm trying to experiment with this image similarity git repo in an Ubuntu docker image instance. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |