Skip to content
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 says IPv6 enabled when it isn't #4555

MarcelRaad opened this issue Nov 3, 2019 · 1 comment

configure says IPv6 enabled when it isn't #4555

MarcelRaad opened this issue Nov 3, 2019 · 1 comment


Copy link

MarcelRaad commented Nov 3, 2019

I did this

./configure --enable-debug --with-winssl --enable-alt-svc

configure says:

IPv6:             enabled

because of


Line 1231 in 2839cfd


But curl_config.h says:

/* Define if you want to enable IPv6 support */
/* #undef ENABLE_IPV6 */

because of


Line 3968 in 2839cfd

if test "$curl_cv_func_getaddrinfo" = "yes"; then

I expected the following

The output of configure to match ENABLE_IPV6. And probably ENABLE_IPV6 being independent of HAVE_GETADDRINFO.

curl/libcurl version


curl 7.67.0-DEV (i686-pc-mingw32) libcurl/7.67.0-DEV Schannel zlib/1.2.11
Release-Date: [unreleased]
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp smtp smtps telnet tftp
Features: alt-svc AsynchDNS Debug Kerberos Largefile libz NTLM SPNEGO SSL SSPI TrackMemory

operating system

Classic MinGW with MSYS 1.0 on Windows 10

Copy link

bagder commented Nov 4, 2019

I don't think there's any point in making them independent of each other. We can only do IPv6 "proper" if getaddrinfo() exists.

bagder added a commit that referenced this issue Nov 4, 2019
Previously it could say "IPv6: enabled" at the end of the configure run
but the define wasn't set because of a missing getaddrinfo().

Reported-by: Marcel Raad
Fixes #4555
@bagder bagder closed this as completed in 07f8986 Nov 5, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Feb 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Successfully merging a pull request may close this issue.

2 participants