When configuring 'no-comp', zlib support should be disabled too [1.0.2] #6248
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
|
Wait...why? Isn't zlib support a libcrypto level thing, while no-comp is a libssl level thing? So it should be possible to have zlib whilst still compiled with no-comp |
|
Because the zlib support was designed to be a 'comp' component, nothing else. 'comp' itself may be designed with libssl in mind, but it is also designed for general use. |
|
Merged. fe4fe67 When configuring 'no-comp', zlib support should be disabled too |
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.
Fixes #6241