RE: [Haskell-cafe] Re: "getServiceEntry: does not exist" on Windows

Nope, actually it also happens for me with the updated installer. Sigbjorn - any ideas? It doesn't happen with my local STABLE build, but I'm still using gcc 3.2.x. Cheers, Simon On 21 October 2005 13:33, Simon Marlow wrote:
Please try the updated installer for 6.4.1. I believe this is caused by the same bug in the dynamic linker that was fixed in the update. At least, I can reproduce your bug with the 6.4.1 installation I have, but not with a fresh build.
Cheers, Simon
On 21 October 2005 13:20, Joel Reymont wrote:
Folks, ideas on this? It's a major showstopper for me since it prevents me from deploying the Haskell app for my customer :(.
Thanks, Joel
On Oct 19, 2005, at 5:06 PM, Joel Reymont wrote:
This fails also but the C call to getprotobyname succeeds.
Prelude> Network.BSD.getProtocolByName "tcp" *** Exception: getServiceEntry: does not exist (no such service entry)
On Oct 19, 2005, at 4:51 PM, Joel Reymont wrote:
I checked my Windows protocol file in system32/drivers/etc and it has
tcp 6 TCP # Transmission control protocol
Still, I get the following:
Prelude> Network.BSD.getProtocolNumber "tcp" *** Exception: getServiceEntry: does not exist (no such service entry)
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe

It stopped happening for me on WinXP but it's still happening for my customer on Win2K. On Oct 21, 2005, at 1:45 PM, Simon Marlow wrote:
Nope, actually it also happens for me with the updated installer.
Sigbjorn - any ideas? It doesn't happen with my local STABLE build, but I'm still using gcc 3.2.x.

I don't really have the time, but here's some debugging
code that'll maybe help diagnosing why/if WinSock is failing
to start up:
- compile the attached initws.c via ghc,
foo$ ghc -c initws.c
- run some tests
foo$ ghc -package net IWS.hs initws.o -e "initWS 1 1 >>= print"
foo$ ghc -package net IWS.hs initws.o -e "initWS 2 2 >>= print"
foo$ ghc -package net IWS.hs initws.o -e "initWS 1 1 >>
Network.BSD.getProtocolByName \"tcp\" >>= print"
foo$ ghc -package net IWS.hs initws.o -e "initWS 2 2 >>
Network.BSD.getProtocolByName \"tcp\" >>= print"
initWS returns 0 on success.
The GHC networking support is ultra-conservative wrt WinSock versioning,
sticking with 1.1 for max portability. Perhaps that's working against us
here?
Needless to say, this is working for me (on a pair of XP boxes.)
--sigbjorn
----- Original Message -----
From: "Joel Reymont"
It stopped happening for me on WinXP but it's still happening for my customer on Win2K.
On Oct 21, 2005, at 1:45 PM, Simon Marlow wrote:
Nope, actually it also happens for me with the updated installer.
Sigbjorn - any ideas? It doesn't happen with my local STABLE build, but I'm still using gcc 3.2.x.
participants (3)
-
Joel Reymont
-
Sigbjorn Finne
-
Simon Marlow