"make -j4" is failing for me. My best guess is that my compiler is not being used in c++17 mode.
The first failure is reported at Building CXX object cobs/CMakeFiles/cobs_static.dir/construction/compact_index.cpp.o The reported error is
...cobs/kmer.hpp:47:55: error: expected ',' before ')' token for a call to static_assert() with only one argument. The single argument static_assert() was introduced in c++17, before that two arguments were required. This is why I believe the problem is that the compiler is being run in pre-17 mode.
I note that the output from the top level cmake command included this line: TLX CMAKE_CXX_FLAGS: ... -std=c++17 .... Does that suggest that cmake was smart eough to know it needed to add -std=c++17 to get my compiler into c++17?
I've tried to dig through the build process to see what gcc command line was used for that first failure. That information is (effectively) hidden in the definitions of $(CXX_FLAGS) (or perhaps $(CXX_DEFINES)) in effect in cobs/CMakeFiles/cobs_static.dir/build.make, but I'm not familiar enough with the cmake process to know where to find where those are defined.
Is there any way to get make -j4 to show me all the commands it performs, i.e. the command lines instead of the usually more informative summaries it is currently showing me?
"make -j4" is failing for me. My best guess is that my compiler is not being used in c++17 mode.
The first failure is reported at
Building CXX object cobs/CMakeFiles/cobs_static.dir/construction/compact_index.cpp.oThe reported error is...cobs/kmer.hpp:47:55: error: expected ',' before ')' tokenfor a call to static_assert() with only one argument. The single argument static_assert() was introduced in c++17, before that two arguments were required. This is why I believe the problem is that the compiler is being run in pre-17 mode.I note that the output from the top level cmake command included this line:
TLX CMAKE_CXX_FLAGS: ... -std=c++17 .... Does that suggest that cmake was smart eough to know it needed to add-std=c++17to get my compiler into c++17?I've tried to dig through the build process to see what gcc command line was used for that first failure. That information is (effectively) hidden in the definitions of
$(CXX_FLAGS)(or perhaps$(CXX_DEFINES)) in effect incobs/CMakeFiles/cobs_static.dir/build.make, but I'm not familiar enough with the cmake process to know where to find where those are defined.Is there any way to get
make -j4to show me all the commands it performs, i.e. the command lines instead of the usually more informative summaries it is currently showing me?