Prevent oshmem related files inside install folder in case --disable-oshmem #879
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
|
Test FAILed. |
1 similar comment
|
Test FAILed. |
|
FWIW, I think the error is this: |
igor-ivanov
force-pushed
the
pr/disable-oshmem-issue
branch
from
ecea160 to
5f13270
Compare
This was referenced Sep 11, 2015
|
@miked-mellanox include/openshmem folder stores internal header-files. It is done to meet openmpi approach, |
|
thanks |
mike-dubman
added a commit
that referenced
this pull request
Sep 14, 2015
Prevent oshmem related files inside install folder in case --disable-oshmem
jsquyres
pushed a commit
to jsquyres/ompi
that referenced
this pull request
Aug 23, 2016
Fix vader resource leak.
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.
This PR should resolve issue #850
@jsquyres, @miked-mellanox could you review