Daniel Stenberg wrote:
> On Sun, 6 Mar 2005, Adam D. Moss wrote:
>> I've got feedback now: the non-c-ares build behaved the same.
>
> I'm very puzzled by this and I don't really know how to proceeed from
> here... :-(

I'm not sure either. What I'll likely end up doing is
completely stuffing libcurl with trace printfs along the
paths that lead to CURLE_COULDNT_CONNECT and see where
a win2k run diverges from other windows versions... unless
I can think of something more direct.

I'll also try to find an official mingw32-linkable static
libcurl, to see if the problem is either in my build options
or build setup (though it'd be puzzling to have such effects
only manifest on win2k). I use my own libcurl build because
I only need vanilla HTTP support and distribution binary size
is very important.

Regards,
--Adam
Received on 2005-03-07