spack-reusable: investigate cmake and gcc usage #65
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
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.
In our
spack-cgcore-1.8container the dependencies were built using spack againstcmake-3.30.5.In our products CIs that use spack-reusable.yml it seems that
cmake-3.27.9(the preferred version in spack-0.22.2) is used for the packages to compile :https://github.com/LIHPC-Computational-Geometry/magix3d/actions/runs/11831454053/job/32966626392#step:5:43
Adding the call to
spack external find cmakeseems to address to anomaly and now we make use of thecmake-3.30.5declared as external; as an added bonus we gain 7min in the CIs execution time (see https://github.com/LIHPC-Computational-Geometry/magix3d/actions/runs/11864380050/job/33067703385)I am not sure why it is necessary to make this call to find cmake, as the spack user configuration files from the container should have stored this info, whereas we do not need to make a call to find the compiler.