Re: MS-Windows build broken in Fmake_network_process

[Eli Zaretskii]

> From: Helmut Eller <address@hidden>
> Cc: address@hidden
> Date: Fri, 26 Mar 2010 19:17:41 +0100
> 
> >> >          /* getsockopt(,,SO_ERROR,,) is said to hang on some systems.
> >> >             So only use it on systems where it is known to work.  */
> >> 
> >> Have you test case to reproduce it?
> >
> > No.  And I don't know enough about this issue to work on the problem,
> > even if I did.
> 
> Then link in getsockopt.  That's the most direct solution.

Solution for what?  The previous code had no problems on Windows.  The
bug report that triggered the new code was deeply rooted in Posix
behavior; the solution is Posix-centric code, and was never tested on
Windows.  Why should it be run on Windows, and what ``problem'' will
that solve?