spack build fails
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 236
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
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.
1. 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.
2. 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.
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 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.
Assessment
- Tech stack
- cpp
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100