Match spack-ohpc dependencies to published system requirements #1365
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
From discussion with @adrianreber on Slack this morning, we noticed on a fresh install of OHPC with Spack, that we were unable to run some
spack install
commands out of the box, due to us not yet havingg++
installed, nor had we runspack compiler find
after installing OHPC-packaged compilers to fix root'scompilers.yaml
.This PR ensures all the system prerequisites are dependencies of the Spack package. It may not provide optimized compilations, but should work better out of the box.