-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
spack setup
: Fix Bugs + Multi-setup (2)
#5043
Conversation
…ere happening with `spack setup`. Avoid concretizing more than once (slow and was probably also causing bugs).
…fault versions of development packages can then all be put into `packages.yaml`, freeing the user the need to type (and remember) them when running `spack setup`.
Also add -j to the common arguments
# Conflicts: # lib/spack/spack/build_systems/cmake.py # lib/spack/spack/cmd/common/arguments.py # lib/spack/spack/cmd/install.py # lib/spack/spack/cmd/setup.py
Add everytrace to Mock repo; will be used for spack setup tests. Added unit test: setup
…FixSetup # Conflicts: # lib/spack/spack/build_systems/cmake.py # lib/spack/spack/cmd/install.py # lib/spack/spack/cmd/setup.py # lib/spack/spack/package.py # lib/spack/spack/test/cmd/install.py
@citibeth : I am trying this PR and getting below error: trying to build
Error / Relevant traceback is:
|
@citibeth : temporarily I disabled that In some of the (old) packages I have :
And then
So if I understood correctly :
|
Something is broken:
EDIT: just formatting as code section for readability |
Just for the record: In mean time there are two additional bugs:
With these two bugs |
Superceded by #7830 |
Continued from #2664. The branch for this PR was moved from a fork to the main LLNL Spack repo. I have done my best to merge/rebase in a sensible way, but I have not tried this out.