Added config to use the external zlib for the orion Intel build. #9
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
|
I suggest we make this change across the board on Orion (for all compilers)? That would be in the Orion site config packages.yaml file. |
so that both gcc and intel builds will use the external zlib package.
|
@climbfuji I have done as you suggested - moved the external zlib config from packages_intel.yaml to packages.yaml. I verified that I get the exact same concretization as before for intel and now get an external zlib in the gcc concretization. |
climbfuji
merged commit 831677d
into
climbfuji:feature/libirc_parallel_netcdf_and_scipy
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.
This PR adds configuration for building spack-stack on Orion using Intel compiler/mpi that forces spack-stack to use the external zlib instead of the spack built zlib-ng package. This is part of the solution for the issue with the Intel build on Orion breaking the system tar command.
The final part of the solution is to use the cmake builtin tar feature instead of the system tar command to unpack the CRTM test data (which is where the system tar command crashes).
Partially addresses JCSDA/issues/1355