Fix issue with installation of gfortran 11 #58
Merged
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 my repo I had issues running a program compiled with gfortran 11 in CI. The problem turned out to be that it was successfully compiled with gfortran 11, but it was linking against the wrong libgfortran-5.dll at runtime. It was linking to the one in /c/mingw64/bin, which is from gfortran 12 which is installed by default in the Windows 2022 image.
The simple solution is to move the entire mingw64 folder instead of just a few files.
For reference here is a minimal program that demonstrates the issue. If you compile this with gfortran 11 and then try to make sure that libgfortran-5.dll from gfortran 12 is on the search path ahead of the one from gfortran 11, you will get a segfault. I don't think it's necessary to make a regression test since the entire folder is now moved.