Allow merging dotnetcore bins with openssl-compat in order to support LibreSSL #479
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
Remove direct dependency on dev-libs/openssl by allowing dev-libs/openssl-compat. This can be used as a workaround for merging dotnetcore on a system that uses dev-libs/libressl.
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.
I poked around with trying to run binaries on a machine with
dev-libs/libressl, turns out that ABI is not that compatible for a proper .NET Core support.The issue could be resolved by removing a direct dependency on OpenSSL by allowing building with
dev-libs/openssl-compat, as @zigford already suggested. This could also fix #427.I also noticed that
repomancomplains about headers being wrong but decided to leave it as is.