Repair breaks after boost python 1.65 changes #1753
Merged
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
Alas, the new Boost 1.65 moves some boost python material from one namespace to another in a way that breaks compatibility related to support for numpy arrays. This breaks the build, including all of our MacOS-based TravisCI tests, which of course pick up the latest Boost via Homebrew.
lgritz
added a commit
to lgritz/OpenImageIO
that referenced
this pull request
Aug 26, 2017
…ion#1753) Alas, the new Boost 1.65 moves some boost python material from one namespace to another in a way that breaks compatibility related to support for numpy arrays. This breaks the build, including all of our MacOS-based TravisCI tests, which of course pick up the latest Boost via Homebrew.
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.
Alas, the new Boost 1.65 moves some boost python material from one namespace to another in a way that breaks compatibility related to support for numpy arrays. This broke the build with using the new Boost, including all of our MacOS-based TravisCI tests, which of course pick up the latest Boost via Homebrew.