Before solving the problem, GHC builds would proceed fine. The link problem occurred during runtime. What libraries on the Windows operating would the build have succeeded on? Win32 Api -- do those have the standard C functions. If these libraries are available, I wonder why the link failed during runtime. (There is a libmsvcrt.a under c:\ghc\ghc-6.6.1\gcc-lib, should this have played a role? ) Edward Ing
On unix the C compiler generally links to the standard C library without you having to ask for it explicitly.
I'm not sure that if we automatically linked to msvcrt that everyone would be happy. Many people seem to think msvcrt is to be avoided in preference of 'native' win32 calls.
Information for understanding this problem would be great.
This is a slightly tricky problem because the names of the libraries to link to are different on different operating systems.
We don't have a proper solution to this at the moment. I'm posting this to the cabal-devel list in case anyone has any good practical realistic suggestions.
Duncan