issue with finding MPI when building with spack
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 100
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
I'm getting a very strange issue when building with spack. It appears that configure finds MPI correctly, but then fails.
77 checking for stdlib.h... (cached) yes
78 checking for GNU libc compatible malloc... yes
79 checking for /usr/local/bin/mpicc... /usr/local/bin/mpicc
80 Checking whether /usr/local/bin/mpicc responds to '-showme:compile'.
.. no
81 Checking whether /usr/local/bin/mpicc responds to '-showme'... no
82 Checking whether /usr/local/bin/mpicc responds to '-compile-info'...
yes
>> 83 configure: error: You should check to see if MPI is setup properly.
This does not happen when manually building libcircle. Does the build system properly detect the MPI that spack passes, or does it rely on hard coded paths?
Contributor guide
No contributing guide indexed for this repository
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 with the configure step that checks /usr/local/bin/mpicc, then compare the Spack build invocation with a manual libcircle build. Done means configure accepts the MPI compiler and the Spack build proceeds without the MPI setup error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100