> Something's up with your WinSock setup on that machine, > I suspect -- works fine on the Win98 box I tested it on.
That's a useful reference point, thanks! It also means that the program I want to use it for will work on win98 boxes, even if not yet on mine. I'm also hunting on the web, but while similar problems do not seem unknown, the few suggested "cures" are not very encouraging so far. And while I'm grasping at straws: which port number did you use? > You may want to investigate whether the 'identical' client > written in C (or some such) behaves as expected on that > box.. good idea (although I thought this library was pretty close to the foreign metal anyway?). the standard client/server-example from the perlipc man page appears to work (they use PF_INET as well as AF_INET, but one is defined in terms of the other). Hmm, that means it isn't my machine.. (unless perl is clever as usual; oh, and that was a cygwin perl, but still..) > The HEAD version of the 'network' package tidies up the > propagation of WinSock errors. It also drops the need for > the user to remember to use withSocketsDo. Thanks, that was quick. Have updated my libraries tree, but don't build ghc from source (no space left here..). How do I build libraries/network with my installed ghc-5.04 (?? have there been any socket-relevant fixes since then, checking with 5.04.2 [which resets my filetype settings for .hs].. no)? The building guide asks for a mingw-gcc to be specified for configure, so I simply tried specifying the one in the ghc-5.04 directory, which causes configure to fail (gcc can't create files or so). Well, we'll see.. Thanks for the help, Claus _______________________________________________ Glasgow-haskell-bugs mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
