glibc always external with spack v0.22.1
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.1k
- Forks
- 2.5k
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 82
Description
Steps to reproduce
spack install glibc
Error message
[+] /usr (external glibc-2.39-t546aqtsv6c2nzq4cdwpftejqb6htmtz)
Information on your system
Hello, I am trying to compile glibc in order to detach spack completely from the OS but glibc always appear to be set as an external package, even though I never set it as an external package.
Is it due to this?
lib/spack/spack/concretize.py:79: non_buildable_packages = {"glibc", "musl"}
Thank you and congrats for your great job.
General information
- I have run
spack debug reportand reported the version of Spack/Python/Platform - I have searched the issues of this repo and believe this is not a duplicate
- I have run the failing commands in debug mode and reported the output
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
Reproduce the behavior with spack install glibc, then inspect lib/spack/spack/concretize.py around line 79 and trace how the non-buildable package set affects glibc. Done means determining why glibc is selected as external and identifying the appropriate behavior or configuration change; no test file is mentioned in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100