configury: disable Fortran unless --enable-fortran - #1193
Merged
davidozog merged 1 commit intoMar 18, 2025
Merged
Conversation
bcmIntc
approved these changes
Mar 18, 2025
bcmIntc
left a comment
bcmIntc
left a comment
Collaborator
There was a problem hiding this comment.
Looks good, will you also change test-sos' usage?
Member
Author
We already disabled fortran by default in in commit openshmem-org/tests-sos@a46cb3a |
abrooks98
approved these changes
Mar 18, 2025
markbrown314
approved these changes
Mar 18, 2025
bcmIntc
pushed a commit
to bcmIntc/SOS
that referenced
this pull request
Jun 11, 2026
…rtran_by_default configury: disable Fortran unless --enable-fortran
This file contains hidden or 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
4 participants
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.
Configure such that the Fortran API is always disabled unless explicitly enabled.
Fortran was deprecated in OpenSHMEM v1.4 and removed in v1.5, and this seems to cause problems with updating the
sosSpack package, at least for me.Closes #1184