summaryrefslogtreecommitdiff
path: root/share
diff options
context:
space:
mode:
authorBen Cowan <benc@txcorp.com>2020-12-11 16:54:11 -0700
committerGitHub <noreply@github.com>2020-12-11 15:54:11 -0800
commitcf37e9276d826a4607afcc307f765c0708e83311 (patch)
tree466c3adf897eda06a04487d0a690e6272b842545 /share
parent0924b209847e2d7284ff0ff2b234f8afd47e0921 (diff)
downloadspack-cf37e9276d826a4607afcc307f765c0708e83311.tar.gz
spack-cf37e9276d826a4607afcc307f765c0708e83311.tar.bz2
spack-cf37e9276d826a4607afcc307f765c0708e83311.tar.xz
spack-cf37e9276d826a4607afcc307f765c0708e83311.zip
Debugging support: fix compiler wrapper log on Mac OS (#20333)
This fixes a logging error observed on macOS 11.0.1 (Big Sur). When performing a Spack install in debugging mode (e.g. `spack -d install py-scipy`) Spack is supposed to write a log of compiler wrapper command line invocations to the current working directory. Due to a regression error introduced by #18205, these files were no-longer generated, and Spack was printing errors such as "No such file or directory: None/." This is because the log file directory gets set from `spack.main.spack_working_dir`, but that variable is not set in the spawned process. This PR ensures that the working directory (at the time of the "spack install" invocation) is persisted to the subprocess.
Diffstat (limited to 'share')
0 files changed, 0 insertions, 0 deletions