Skip to content

Conversation

@MichaelBrim
Copy link
Collaborator

Motivation and Context

See Issue #663

How Has This Been Tested?

Using Rob's example from the issue, in Ubuntu Docker and on Summit using gcc

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Performance enhancement (non-breaking change which improves efficiency)
  • Code cleanup (non-breaking change which makes code smaller or more readable)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Testing (addition of new tests or update to current tests)
  • Documentation (a change to man pages or other documentation)

Checklist:

  • My code follows the UnifyFS code style requirements.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • All commit messages are properly formatted.

@roblatham00
Copy link
Contributor

thanks, yes, this does the trick for me on my build environment as well.

@adammoody adammoody merged commit 41455ad into llnl:dev Aug 16, 2021
@MichaelBrim MichaelBrim deleted the library-api-fix branch August 18, 2021 21:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants