'spack compiler find' does not detect gfortran when using ccache
Open
Nobody has claimed this yet.
compilers
- Dominant language
- Python
- Stars
- 5.1k
- Forks
- 2.5k
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 82
Description
This is on fedora 27
I get:
$ cat compilers.yaml
compilers:
- compiler:
environment: {}
extra_rpaths: []
flags: {}
modules: []
operating_system: fedora27
paths:
cc: /usr/lib64/ccache/clang
cxx: /usr/lib64/ccache/clang++
f77: null
fc: null
spec: clang@4.0.1
target: x86_64
- compiler:
environment: {}
extra_rpaths: []
flags: {}
modules: []
operating_system: fedora27
paths:
cc: /usr/lib64/ccache/gcc
cxx: /usr/lib64/ccache/g++
f77: null
fc: null
spec: gcc@7
target: x86_64
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with spack compiler find on Fedora 27 using the ccache compiler paths shown in compilers.yaml. Check whether the generated compiler configuration detects gfortran; done means the Fortran compiler paths are populated when ccache-backed GCC is used.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fedora
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100