Viktor Szakats edae6c66c7 lib: sync guard for Curl_getaddrinfo_ex() definition and use ... `Curl_getaddrinfo_ex()` gets _defined_ with `HAVE_GETADDRINFO` set. But, `hostip4.c` _used_ it with `HAVE_GETADDRINFO_THREADSAFE` set alone. It meant a build with the latter, but without the former flag could result in calling this function but not defining it, and failing to link. Patch this by adding an extra check for `HAVE_GETATTRINFO` around the call. Before this patch, build systems prevented this condition. Now they don't need to. While here, simplify the related CMake logic on Windows by setting `HAVE_GETADDRINFO_THREADSAFE` to the detection result of `HAVE_GETADDRINFO`. This expresses the following intent clearer than the previous patch and keeps the logic in a single block of code: When we have `getaddrinfo()` on Windows, it's always threadsafe. Follow-up to 67d88626d4 Reviewed-by: Jay Satiro Closes #9734		2022-11-01 22:40:36 +00:00
..
WindowsCache.cmake	lib: sync guard for Curl_getaddrinfo_ex() definition and use	2022-11-01 22:40:36 +00:00