Guten Tag Daniel Stenberg, am Mittwoch, 30. September 2015 um 12:18 schrieben Sie:
> Hm. I don't see how this happens in the code. Which code tries to use that > function? The unresolved external is mentioned for "asyn-thread", which seems to use Curl_ipv4_resolve_r depending on HAVE_GETADDRINFO NOT defined, which is the case for me. config-win32.h is not recognizing my compiler again, if I manually define e.g. _WIN32_WINNT = 0x0501 compiling and linking works with defining either ENABLE_IPV6 or USE_IPV6=1. So, what's the best thing to do now? _WIN32_WINNT is not defined automatically as well, should I define it manually? Should it be included in config-win32.h for my compiler like it is with _MSC_VER? Where does _WIN32_WINNT_VISTA come from? I couldn't find it, would I need to define it as well? Or should the check for HAVE_GETADDRINFO and its stuff in config-win32.h should be enhanced by recognizing my compiler, like it recognizes _MSC_VER? I would suspect my compiler being compatible with the case for _MSC_VER. I mean the following part: > /* Availability of freeaddrinfo, getaddrinfo and getnameinfo functions is > quite convoluted, compiler dependent and even build target dependent. */ Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail: [email protected] AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...........05151- 9468- 55 Fax...............05151- 9468- 88 Mobil..............0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
