How comes? When some of the macros or tests in the configure phase fails, CMake "helpfully" dumps these files to the output. What you are looking at is the CMakeCache.txt, the CMakeOutput.log or the CMakeError.log. However, this (often useful) strategy in such cases leads astray. Typically you'd look for the last error message. Hint: search for the actual error message I've done a minimal version of the cmakelists.txt and started testing it line by line until I found which package was causing it to stop: finally I found it was a version mismatch. Though, in this case cmake was not the problem the error was silent and the -lpthreads related error/warning was the only thing being written to the cmake error log file, although that was not causing any issue. The problem was happening when running cmake. Looking for pthread_create in pthread - found Looking for pthread_create in pthreads - not found Looking for pthread_create - not found. Looking for include file pthread.h - found Which produced the following output: - Looking for include file pthread.h Used a minimal Cmakelists.txt as follows: cmake_minimum_required (VERSION 2.4) The cmakelists.txt lines that include the compiler flags are as follows: set(CMAKE_C_FLAGS "$\n\n") I've installed all the dependencies and I'am using cmake to build the project, although it stops with the following error:ĭetermining if the function pthread_create exists in the pthreads failed with the following output: I have c project that was smoothly running on a given machine, and now I am trying to compile it on another one with the same operating system (Xubuntu 14.04).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |