Closed gjaeger closed 4 years ago
@bsteinb any idea?
For the first warnings the reason is that no OpenMP Module is loaded. We could think about suppressing this warning. But for the computation you should load a OpenMP module and recompile everything.
The Boost related warnings should be disabled... I have to check why boost is not marked as system includes...
There is no OpenMP module (as in $ module load OpenMP
), because OpenMP is included in the compiler. I think the issue here is that the OpenMP::OpenMP_CXX
target is not mentioned in the target_link_libraries(report ...)
statement in jpsreport/CMakeList.txt
(similar to target_link_libraries(core ...)
in libcore/CMakeList.txt
).
In addition, this was my workflow for building from source:
module load CMake
module load GCC
module load ParaStationMPI
module load Boost
mkdir build && cd build
../scripts/setup-deps.sh
cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_PREFIX_PATH=$(pwd)/deps ..
make
The Boost warning is due to a bug (not really a bug, more like a rough edge) in EasyBuild which we use to install the modules: https://github.com/easybuilders/easybuild-framework/issues/3331
To work around this, you can do this before building:
$ export CPLUS_INCLUDE_PATH="$CPATH"
$ unset CPATH
Although that does seem like overkill for getting rid of a few warnings.
BTW, the make log can be made much more useful by running make VERBOSE=1
.
When compiling on JURECA (cmake 3.14.0, Boost 1.69.0, Python 3.6.8) I get the following hints for jpsreport:
relating to OpenMP:
relating to Boost and Python:
The compilation of jpscore and jpsreport is completed without errors (cmake log - make log).