Workaround: gfortran compile with SHiELDFULL #376
Closed
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
…compiler was getting stuck when a line is continued in the middle of a calculation where the openening parenthesis is on one line and the losing parenthesis on another line. Workaround is to keep the line longer.
|
Better fix coming. |
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.
Description
When compiling the SHiELDFULL configuration with GNU fortran compiler, the build fails due to expecting a closing parenthesis where there is a line continuing character "&". This seems to be a bug with gfortran. The workaround here is to exceed the typically preferred max line length in these cases.
Fixes # (issue)
How Has This Been Tested?
Testing now
Checklist:
Please check all whether they apply or not