VPATH buils fail with v3.5
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- c
- Domain
- build-system
Research direction
Reproduce the out-of-tree build from a separate mybuild directory using ../configure followed by make. Start with arch/arch.h and the configure-generated build include paths, checking why arch/arch_x86_64.h is not found without CPATH. Done means the documented VPATH build succeeds without the CPATH workaround.
Written by the indexing model from the issue text.
Description
Building mpiP in-tree works fine. But out-of-tree / VPATH builds fail.
To reproduce:
$> # extract tarball and cd into mpiP directory
$> mkdir mybuild
$> cd mybuild
$> ../configure
$> make
../arch/arch.h:17:10: fatal error: arch/arch_x86_64.h: No such file or directory
It looks like the include path does not contain $(srcdir).
In fact, calling make as
$> make CPATH=$CPATH:../
serves as a workaround.
- Dominant language
- C
- Stars
- 112
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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.
More from llnl/mpiP
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
MPI 4.0 SupportOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Communication matrixOpen
Difficulty 4/5 3-5 days Newbie friendliness 30/100
-
ARM supportOpen
Difficulty 4/5 3-5 days Newbie friendliness 30/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
BasedHardware/omi#19711 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
microsoft/ebpf-for-windows#5604 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
trezor/trezor-firmware#7985 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day