diff options
| author | Erik Schnetter <schnetter@gmail.com> | 2016-01-08 22:24:42 -0500 |
|---|---|---|
| committer | Erik Schnetter <schnetter@gmail.com> | 2016-01-08 22:24:42 -0500 |
| commit | 2ac2985cf20f385e062227fc8f5bf7e4f330409a (patch) | |
| tree | 42daaecf7412c0e654a971191c53c7af064c2a35 | |
| parent | 7ad3e2b56bca4aca3a1ed5a157380070ea17514f (diff) | |
| download | spack-2ac2985cf20f385e062227fc8f5bf7e4f330409a.tar.gz spack-2ac2985cf20f385e062227fc8f5bf7e4f330409a.tar.bz2 spack-2ac2985cf20f385e062227fc8f5bf7e4f330409a.tar.xz spack-2ac2985cf20f385e062227fc8f5bf7e4f330409a.zip | |
Require Python for PETSc
PETSc requires Python for building.
I have a case where an HPC system has a very old default Python version, too old for Spack. So I load a module for Python, which makes Spack work. This module relies on LD_LIBRARY_PATH.
When building PETSc, Spack unsets LD_LIBRARY_PATH, breaking the Python that PETSc finds.
Explicitly requiring Python for PETSc makes building PETSc work.
| -rw-r--r-- | var/spack/packages/petsc/package.py | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/var/spack/packages/petsc/package.py b/var/spack/packages/petsc/package.py index f3ed3d72ec..50533dbe54 100644 --- a/var/spack/packages/petsc/package.py +++ b/var/spack/packages/petsc/package.py @@ -12,6 +12,8 @@ class Petsc(Package): version('3.5.2', 'ad170802b3b058b5deb9cd1f968e7e13') version('3.5.1', 'a557e029711ebf425544e117ffa44d8f') + depends_on("python @2.6:@2.9") # requires Python for building + depends_on("boost") depends_on("blas") depends_on("lapack") |