Don't enable TLS when --without-* flags are used #7994
Closed
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.
Previously specifying
--without-gnutls
would unexpectedly attempt to compile with GnuTLS, effectively interpeting this as--with-gnutls
. This caused a significant amount of confusion whenlibcurl
was built with SSL disabled since GnuTLS wasn't present.68d89f2 dropped the
--without-*
options from the configure help, butAC_ARG_WITH
still defines these flags automatically. As https://www.gnu.org/software/autoconf/manual/autoconf-2.60/html_node/External-Software.htmldescribes, the
action-if-given
is called when the user specifies--with-*
or--without-*
options:The scripts didn't check whether "yes" or "no" was specified, so "yes" was the default.
To prevent this confusion, we make the
--without
flag do the right thing by ignoring the value if it set to "no".