dng: Work around non-backwards compatible change to libtiff #81
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
Versions of libtiff from 4.2.0 onwards have made a non-backwards compatible API change. Unfortunately code that was correct previously still compiles but crashes the application at runtime. Signed-off-by: David Plowman <[email protected]>
|
@naushir @XECDesign |
|
LGTM |
|
You should be albe to use the old image and upgrade normally ( |
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.
Versions of libtiff from 4.2.0 onwards have made a non-backwards
compatible API change. Unfortunately code that was correct previously
still compiles but crashes the application at runtime.
Signed-off-by: David Plowman [email protected]