spack build fails
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- build-system
Research direction
Start by examining the Spack build configuration and how it obtains the libROM source. Check the repository's configure.ac and aclocal.m4 relationship, then compare the build behavior for a distribution tarball versus the git archive. Done means a Spack build no longer triggers the reported autotools version-mismatch failure.
Written by the indexing model from the issue text.
Description
A spack build fails on my machine when make determines that configure.ac is newer than aclocal.m4, and wants to rebuild aclocal.m4. This leads to problems with a version mismatch in the autotools on my local machine vs what was run to build what's in the repo.
I think there are two possible routes to solving this issue.
-
Have spack download a tarball instead of check out the git archive. The tarball will be a distribution tarball with a configure script and makefile, but no autotools stuff.
-
Remove all generated files from the repo, so automake rebuilds everything fresh, which should prevent problems with version mismatches.
I think solution 1. is preferable and will sidestep a lot of possible headaches with requiring autotools on the destination machine.
- Dominant language
- C++
- Stars
- 236
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
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.
More from llnl/libROM
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
bug
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 28/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·