diff options
| author | Geoffrey Oxberry <goxberry@gmail.com> | 2018-04-26 06:43:20 -0700 |
|---|---|---|
| committer | Adam J. Stewart <ajstewart426@gmail.com> | 2018-04-26 08:43:20 -0500 |
| commit | d54ceb6ce70ba8ff0cc729b0199ed9db1c953729 (patch) | |
| tree | 2b4144dbeda5065bbaefcf9ca878985b91090951 /.mailmap | |
| parent | 2ec701d1dd35088e2aa264c55ad6de646d615329 (diff) | |
| download | spack-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).
Diffstat (limited to '.mailmap')
0 files changed, 0 insertions, 0 deletions