summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorHarmen Stoppels <harmenstoppels@gmail.com>2023-10-04 09:59:59 +0200
committerGitHub <noreply@github.com>2023-10-04 09:59:59 +0200
commitd9cacf664c3da8e0dfa3af6b75f256cc03ffd17f (patch)
tree69edbccd924d19b10cca573867acc08432954d39
parent7bf6780de2b279629dece88f7ae054305f2693b8 (diff)
downloadspack-d9cacf664c3da8e0dfa3af6b75f256cc03ffd17f.tar.gz
spack-d9cacf664c3da8e0dfa3af6b75f256cc03ffd17f.tar.bz2
spack-d9cacf664c3da8e0dfa3af6b75f256cc03ffd17f.tar.xz
spack-d9cacf664c3da8e0dfa3af6b75f256cc03ffd17f.zip
petsc: add conflict on rocm 5.6: for now (#40300)
hipsparse@5.6.0 changed hipsparseSpSV_solve() API, but reverted in 5.6.1
-rw-r--r--var/spack/repos/builtin/packages/petsc/package.py4
1 files changed, 4 insertions, 0 deletions
diff --git a/var/spack/repos/builtin/packages/petsc/package.py b/var/spack/repos/builtin/packages/petsc/package.py
index 4a8ac8657b..9d0d3a9016 100644
--- a/var/spack/repos/builtin/packages/petsc/package.py
+++ b/var/spack/repos/builtin/packages/petsc/package.py
@@ -159,6 +159,10 @@ class Petsc(Package, CudaPackage, ROCmPackage):
# https://github.com/spack/spack/issues/37416
conflicts("^rocprim@5.3.0:5.3.2", when="+rocm")
+ # petsc 3.20 has workaround for breaking change in hipsparseSpSV_solve api,
+ # but it seems to misdetect hipsparse@5.6.1 as 5.6.0, so the workaround
+ # only makes things worse
+ conflicts("^hipsparse@5.6", when="+rocm @3.20.0")
# 3.8.0 has a build issue with MKL - so list this conflict explicitly
conflicts("^intel-mkl", when="@3.8.0")