Spack build #66
Merged
Spack build #66
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…l bring exodus along with suitesparse with no troubles.
…library is a real nightmare and not shipped properly.
tupek2
approved these changes
Oct 28, 2023
Removing 3.7 and adding 3.10
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adding a simple spack build after I went through a few headaches setting up suitesparse on different systems. I've tested this on RHEL7 and ubuntu 22.
Added some instructions to the README as well.
I was hoping to also get exodus.py in the loop but that thing is a nightmare to work with the exodusii spack build is pretty outdated.