Fix runtime path setting when using clang++ and gfortran compilers#40
Merged
Fix runtime path setting when using clang++ and gfortran compilers#40
Conversation
nkoukpaizan
approved these changes
Jan 16, 2025
pelesh
added a commit
that referenced
this pull request
Apr 14, 2025
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
2 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.
If METIS and/or HSL libraries are built with gfortran and the Ipopt and GridKit with gcc/g++, the code will build but the runtime path may not be correctly set for gfortran library. It seems that linking mixed clang/gfortran code with gfortran rather than with clang fixes this issue.