-
-
Notifications
You must be signed in to change notification settings - Fork 6.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
configure: use the threaded resolver backend by default if possible #1647
Conversation
Coverage increased (+0.2%) to 74.668% when pulling f95b01b7dad8f2458f53bd8324809f3ff84636f7 on bagder/configure-threaded-by-default into 9ee6cb1 on master. |
Coverage increased (+0.2%) to 74.608% when pulling 1c8f15b865d83919c7177947f164c4ae53240c82 on bagder/configure-threaded-by-default into 9ee6cb1 on master. |
Coverage decreased (-0.09%) to 74.339% when pulling 5ced944100f851132e3669b2e6318ebd779595c8 on bagder/configure-threaded-by-default into 9ee6cb1 on master. |
5ced944
to
9cf2a34
Compare
I cherry-picked over the irrelevant fixes to master and left only the actual configure fix here. |
cURL 7.55.1 use the threaded resolver (THREADED_RESOLVER) backend if c-ares (CARES) is not available. That means you must enable either CARES or THREADED_RESOLVER (default) option. Reference: curl/curl#1647 MFH: 2017Q3 git-svn-id: svn+ssh://svn.freebsd.org/ports/head@448108 35697150-7ecd-e111-bb59-0022644237b5
cURL 7.55.1 use the threaded resolver (THREADED_RESOLVER) backend if c-ares (CARES) is not available. That means you must enable either CARES or THREADED_RESOLVER (default) option. Reference: curl/curl#1647 MFH: 2017Q3
Change RESOLV from RADIO to SINGLE cURL 7.55.1 use the threaded resolver (THREADED_RESOLVER) backend if c-ares (CARES) is not available. That means you must enable either CARES or THREADED_RESOLVER (default) option. Reference: curl/curl#1647 Approved by: ports-secteam (feld)
No description provided.