On 21/09/2009 22:14, Dominic Steinitz wrote:
Simon Marlow wrote:
I couldn't find anything - happy to look into it if someone points me to
the ticket.
I think this is it:
http://hackage.haskell.org/trac/ghc/ticket/3513
The problem there seems to be that the network library is calling
functions that do not exist on older versions of Windows. I don't think
there's anything that GHC can do about that.
Also this looks relevant:
http://permalink.gmane.org/gmane.comp.lang.haskell.glasgow.user/17456
Something C++ specific, by the looks of it.
Are you sure the problem you had isn't just that the C erfc function is
not available on Windows?
Oh, perhaps the problem that Lennart is referring to is that when GHCi
loads up a package it requires that all the symbols in the package can
be resolved, whereas when you statically link a .a library we only have
to resolve the symbols required by the library modules that the program
actually refers to.
So one workaround would be to link in a dummy erfc() function, or
alternatively hack the erf pacakge so that it omits the offending parts
on Windows.
Cheers,
Simon
_______________________________________________
cabal-devel mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cabal-devel