diff options
| -rw-r--r-- | var/spack/repos/builtin/packages/dla-future/package.py | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/var/spack/repos/builtin/packages/dla-future/package.py b/var/spack/repos/builtin/packages/dla-future/package.py index c360aa3078..5e90ac112e 100644 --- a/var/spack/repos/builtin/packages/dla-future/package.py +++ b/var/spack/repos/builtin/packages/dla-future/package.py @@ -79,6 +79,22 @@ class DlaFuture(CMakePackage, CudaPackage, ROCmPackage): depends_on("rocsolver", when="+rocm") depends_on("rocthrust", when="+rocm") + # nvcc 11.2 and older is unable to detect fmt::formatter specializations. + # DLA-Future 0.3.1 includes a workaround to avoid including fmt in device + # code: + # https://github.com/pika-org/pika/issues/870 + # https://github.com/eth-cscs/DLA-Future/pull/1045 + conflicts("^fmt@10:", when="@:0.3.0 +cuda ^cuda@:11.2") + + # Compilation problem triggered by the bundled fmt in Umpire together with + # fmt 10, which only happens with GCC 9 and nvcc 11.2 and older: + # https://github.com/eth-cscs/DLA-Future/issues/1044 + conflicts("^fmt@10:", when="@:0.3.0 %gcc@9 +cuda ^cuda@:11.2 ^umpire@2022.10:") + + # Pedantic warnings, triggered by GCC 9 and 10, are always errors until 0.3.1: + # https://github.com/eth-cscs/DLA-Future/pull/1043 + conflicts("%gcc@9:10", when="@:0.3.0") + depends_on("hdf5 +cxx+mpi+threadsafe+shared", when="+hdf5") conflicts("+cuda", when="+rocm") |