summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGeoffrey Oxberry <goxberry@gmail.com>2018-04-26 06:43:20 -0700
committerAdam J. Stewart <ajstewart426@gmail.com>2018-04-26 08:43:20 -0500
commitd54ceb6ce70ba8ff0cc729b0199ed9db1c953729 (patch)
tree2b4144dbeda5065bbaefcf9ca878985b91090951
parent2ec701d1dd35088e2aa264c55ad6de646d615329 (diff)
downloadspack-d54ceb6ce70ba8ff0cc729b0199ed9db1c953729.tar.gz
spack-d54ceb6ce70ba8ff0cc729b0199ed9db1c953729.tar.bz2
spack-d54ceb6ce70ba8ff0cc729b0199ed9db1c953729.tar.xz
spack-d54ceb6ce70ba8ff0cc729b0199ed9db1c953729.zip
mfem: add valid range of hypre version numbers (#7903)
This commit fixes #7900. In short: in the absence of constraints to the contrary, spack will download the preferred version of a package, which is usually the most recent non-develop version. On a clean spack installation without hypre installed, `spack install mfem` will download hypre 2.14.0, which is API-incompatible with mfem 3.3.2 (and earlier versions of mfem), so spack will throw compiler errors re: the API mismatch. This commit fixes that error by restricting mfem release versions 3.3.2 and earlier to hypre version 2.10.b to 2.13.999 (only 2.13.0 currently exists, but if it has a non-2.14.x maintenance release, these versions of hypre should also be permitted).
-rw-r--r--var/spack/repos/builtin/packages/mfem/package.py2
1 files changed, 2 insertions, 0 deletions
diff --git a/var/spack/repos/builtin/packages/mfem/package.py b/var/spack/repos/builtin/packages/mfem/package.py
index 2f25a7cc21..541f535353 100644
--- a/var/spack/repos/builtin/packages/mfem/package.py
+++ b/var/spack/repos/builtin/packages/mfem/package.py
@@ -164,6 +164,8 @@ class Mfem(Package):
depends_on('mpi', when='+mpi')
depends_on('hypre', when='+mpi')
+ depends_on('hypre@2.10.0:2.13.999', when='@:3.3.2')
+
depends_on('metis', when='+metis')
depends_on('blas', when='+lapack')
depends_on('lapack', when='+lapack')