diff options
| author | Barry Smith <bsmith@mcs.anl.gov> | 2016-10-30 19:13:16 -0500 |
|---|---|---|
| committer | Todd Gamblin <tgamblin@llnl.gov> | 2016-10-30 17:13:16 -0700 |
| commit | a714377123cf2aefb895badfbf9d4baf81b39654 (patch) | |
| tree | 91c9b55d3667b841c39c20a08c93ba637f545983 /.coveragerc | |
| parent | 9989f8e2675495763d35b26ccc9fcc07db7fd50f (diff) | |
| download | spack-a714377123cf2aefb895badfbf9d4baf81b39654.tar.gz spack-a714377123cf2aefb895badfbf9d4baf81b39654.tar.bz2 spack-a714377123cf2aefb895badfbf9d4baf81b39654.tar.xz spack-a714377123cf2aefb895badfbf9d4baf81b39654.zip | |
python: PYTHONHOME may not be the same as the prefix of the python executable (#2173)
On MacOS, brew installs /usr/local/bin/python but the Python prefix is not /usr/local/bin
Use the python command sys.exec to get the correct directory, instead of the ad hoc self.prefix
previously used
This was a bear to debug; been driving me nuts since I started using spack.
Since spack passes PYTHONHOME down to package builds in the environment
it was passing PYTHONHOME of /usr/local/bin to the PETSc build that uses Python so
the PETSc Python ./configure errored immediately with
ImportError: No module named site
since python could find no python modules. Todd Gamblin pointed out that my first try to fix
this was wrong since it assumed the spack python was the same python used to run spack. Elizabeth Fischer
suggested how to get it to work also with python3
Funded-by: IDEAS
Project: IDEAS/xSDK
Time: 7 hours
Thanks-to: Todd Gamblin, Elizabeth Fischer
Diffstat (limited to '.coveragerc')
0 files changed, 0 insertions, 0 deletions