set CMAKE_CUDA_HOST_COMPILER, CMAKE_CUDA_COMPILER, and CMAKE_CUDA_ARCHITECTURES when using CUDA in CMakeMake easyblock#3523
Conversation
|
@boegelbot please test @ jsc-zen3-a100 |
|
@bedroge: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 2509135920 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot Overview of tested easyconfigs (in order)
Build succeeded for 6 out of 7 (6 easyconfigs in total) edit: not sure why AMGX failed, but it looks like a runtime issue with the test suite, so I guess it's not related to this PR (unfortunately the original easyconfig PR for AMGX was not tested on jsc-zen3-a100). |
Co-authored-by: ocaisa <alan.ocais@cecam.org>
|
@boegelbot please test @ jsc-zen3-a100 |
|
@bedroge: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 2511671250 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot Overview of tested easyconfigs (in order)
Build succeeded for 5 out of 5 (5 easyconfigs in total) |
CMAKE_CUDA_HOST_COMPILER, CMAKE_CUDA_COMPILER, and CMAKE_CUDA_ARCHITECTURES when using CUDA in CMakeMake easyblock
When compiling a CUDA version of GROMACS in EESSI we noticed that
nvccwould pick up theg++from the compat layer sysroot as host compiler (instead of the GCC from the EB stack), leading to weird issues/errors:The right host compiler can be set using the
$CUDAHOSTCXXenvironment variable, which is preferred overCMAKE_CUDA_HOST_COMPILERaccording to https://cmake.org/cmake/help/latest/envvar/CUDAHOSTCXX.html (though that may change in the future, see https://gitlab.kitware.com/cmake/cmake/-/issues/23160).edit: for consistency reasons, I did switch to the
CMAKE_CUDA_HOST_COMPILER, see #3523 (comment).