Fix build with openssl-1.1 #28
Merged
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
|
We could absolutely update the secp256k1 library from BTCs repo if that would be a better route. Please advise (as I'd just do that instead of merging this commit then and update the whole library). @g1itch |
|
I'll merge it anyway, will update SECP library as well |
CryptoCoderz
approved these changes
Dec 11, 2019
CryptoCoderz
added a commit
that referenced
this pull request
Sep 14, 2020
Update openssl and boost libs versions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Hello.
This patch is taken from bitcoin-core/secp256k1#433. Without it digitalnoted won't build with openssl-1.1 or newer.
Or alternatively maybe you can take fresh secp256k1 from Mar 31 2019 which is used in the recent bitcoin release?