diff options
author | Todd Gamblin <tgamblin@llnl.gov> | 2017-04-21 15:45:12 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2017-04-21 15:45:12 -0700 |
commit | c67f8e4aa1d0d19c4c83d366d153d99428fcfb16 (patch) | |
tree | 37d93b8cb38f6eaabd0322c754e72f2a4bd73763 /pytest.ini | |
parent | 63c341037033f683221a7ede9d6b24e86ddf0951 (diff) | |
download | spack-c67f8e4aa1d0d19c4c83d366d153d99428fcfb16.tar.gz spack-c67f8e4aa1d0d19c4c83d366d153d99428fcfb16.tar.bz2 spack-c67f8e4aa1d0d19c4c83d366d153d99428fcfb16.tar.xz spack-c67f8e4aa1d0d19c4c83d366d153d99428fcfb16.zip |
Fix ABI detection issues with macOS gcc. (#3854)
- gcc on macOS says it's version 4.2.1, but it's really clang, and it's
actually the *same* clang as the system clang.
- It also doesn't respond with a full path when called with
--print-file-name=libstdc++.dylib, which is expected from gcc in abi.py.
Instead, it gives a relative path and _gcc_compiler_compare doesn't
understand what to do with it. This results in errors like:
```
lib/spack/spack/abi.py, line 71, in _gcc_get_libstdcxx_version
libpath = os.readlink(output.strip())
OSError: [Errno 2] No such file or directory: 'libstdc++.dylib'
```
- This commit does two things:
1. Ignore any gcc that's actually clang in abi.py. We can probably do
better than this, but it's not clear there is a need to, since we
should handle the compiler as clang, not gcc.
2. Don't auto-detect any "gcc" that is actually clang anymore. Ignore
it and expect people to use clang (which is the default macOS
compiler anyway).
Users can still add fake gccs to their compilers.yaml if they want, but
it's discouraged.
Diffstat (limited to 'pytest.ini')
0 files changed, 0 insertions, 0 deletions