Fix assertion error with example make scripts #22
Conversation
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
Based on ifort 12 Windows compilation, the compiled executable has 'exe' extension even though the target was specified without this extension. This leads to assertion error despite the successful compilation.
Based on ifort 12 Windows compilation, the compiled executable has 'exe' extension even though the target was specified without this extension. This leads to assertion error despite the successful compilation.
Based on ifort 12 Windows compilation, the compiled executable has 'exe' extension even though the target was specified without this extension. This leads to assertion error despite the successful compilation.
Based on ifort 12 Windows compilation, the compiled executable has 'exe' extension even though the target was specified without this extension. This leads to assertion error despite the successful compilation.
Based on ifort 12 Windows compilation, the compiled executable has 'exe' extension even though the target was specified without this extension. This leads to assertion error despite the successful compilation.
Based on ifort 12 Windows compilation, the compiled executable has 'exe' extension even though the target was specified without this extension. This leads to assertion error despite the successful compilation.
Based on ifort 12 Windows compilation, the compiled executable has 'exe' extension even though the target was specified without this extension. This leads to assertion error despite the successful compilation.
Based on ifort 12 Windows compilation, the compiled executable has 'exe' extension even though the target was specified without this extension. This leads to assertion error despite the successful compilation.
Based on ifort 12 Windows compilation, the compiled executable has 'exe' extension even though the target was specified without this extension. This leads to assertion error despite the successful compilation.
Based on ifort 12 Windows compilation, the compiled executable has 'exe' extension even though the target was specified without this extension. This leads to assertion error despite the successful compilation.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
On Windows, the compiled executable contains 'exe' extension (tested with ifort 12 and gfortran) when the provided target name does not have extension part. Because of this, assertion error of type Target Does Not Exist occurs at the end of various make scripts in spite of successful compilation.