Giuseppe Scrivano wrote: >> As for msys fixes I see you fixed the linking issue in the last revision, >> bravo :) ipv6 and ssl config tests are still broken. In windows >> if you are going do a static link test for openssl you should link with >> winsock2 (openssl now uses winsock2) and gdi as well. So this will >> work: >> >> gcc a.c -lssl -lcrypto -lws2_32 -lgdi32 >> >> regardless when wget is compiled with-ssl using mingw one would expect that >> instead of ssl crypto gdi it not be linked to any of those, >> just to eay32 and ssl32 (openssl dlls). >> >> also the config ac shows lwsock32 -lws2_32 and indeed on compile both are >> linked. is there any reason for this, like maybe a trick for a >> universal binary or something? it doesn't seem logical. >> >> > AFAIK, -lws2_32 is needed to build successfully, is there a way to don't > use it? > If you use ws2_32 you don't need to link with wsock32. In fact wsock32 is mostly forwarded functions. Linking to wsock32 and not ws2_32 has the advantage that it works in old windows versions* but if you are linking with ws2_32, I think it would break on them with ws2_32.dll not found, that you would need to dynamically load it to produce a -more or less- universal binary.
*And by old it is very old. Winsock 2 came with Windows 98 and Windows NT4. It can be installed into Windows 95. http://www.sockets.com/winsock2.htm#Status
