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.
Since curl 7.58.0 the TLS backend is configurable, and in 7.77.0 it appears to be a mandatory setting. This PR selects the openssl backend.
Note, this may cause problems if the user explicitly specifies an earlier version of curl - but I decided to apply the simple fix rather than testing the version number of curl against 7.58.0. I also didn't provide a means to use a different backend or disable TLS, mostly to keep things simple (and the current script already has hardcoded defaults of
--disable-shared
and--with-ca-fallback
).This is the failure when building curl 77.7.0 without this fix:
I assume openssl is a reasonable backend to use, although I'm no expert.
I added the
.gitignore
since the script produces thecurl*
files which shouldn't be checked into the repo.Thanks!