Skip to content
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

cached_cmake: mpifc is not always defined #46861

Merged
merged 2 commits into from
Nov 18, 2024

Conversation

rbberger
Copy link
Member

@rbberger rbberger commented Oct 8, 2024

Packages like caliper that have optional fortran support will still try to access mpifc via CachedCMakePackage even if the underlying MPI doesn't provide them (e.g. mpich~fortran). This PR makes that configuration optional.

It also makesmpich only depend on fortran when +fortran.

@spackbot-app spackbot-app bot added build-systems core PR affects Spack core functionality labels Oct 8, 2024
Copy link
Contributor

@raffenet raffenet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving change to MPICH package.py.

@tldahlgren tldahlgren self-assigned this Nov 18, 2024
@tldahlgren tldahlgren merged commit 73316c3 into spack:develop Nov 18, 2024
34 of 35 checks passed
@rbberger rbberger deleted the cached_cmake_mpifc_fix branch November 18, 2024 23:57
fryeguy52 pushed a commit to fryeguy52/spack that referenced this pull request Dec 17, 2024
* cached_cmake: mpifc is not always defined
* mpich: only depend on fortran when +fortran
kshea21 pushed a commit to kshea21/spack that referenced this pull request Dec 26, 2024
* cached_cmake: mpifc is not always defined
* mpich: only depend on fortran when +fortran
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants