Fix compiler detection when using --without-{crypt,crypto,ssl} #28
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
|
At least that'll do no harm ;-) Thanks! |
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.
As the author of #13 honestly admitted, moving around parts of
configure.acto fix its horrors is not the best solution. Specifically, the change introduced by #13 causes compilation to fail when--without-cryptoand/or--without-sslis used.The root problem with
configure.acis that if the combination ofconfigureswitches used does not cause at least one branch withAC_CHECK_LIBto be evaluated then the C compiler is never detected.The simplest way to fix this appears to be to explicitly look for a working C compiler before doing anything else and this is what this pull request attempts.
DISCLAIMER: I am no Autotools expert. This just happened to work for me.