Part of the problem when attempting to use MS tools to build GHC is
the difference between Mingw32 library names (lib*.a, .so), which CL,
LIB, etc. do not recognise. The other part of the problem is the
Mingw toolset, notably AutoConf, AutoMake and Make, which do not
understand CL.
I discovered a possible replacement for these (all running under
DOS), in the GnuWin32 toolset, at http://gnuwin32.sourceforge.net .
The GnuWin32 tools are all Windows-native packaged as DLLs and also
include some more pervasive tools we were going to replace, such as
Readline (v5.0) and build tools, including Sed. With Windows-native
versions of Perl and Python, we may be able to build without relying
on any Mingw/Cygwin tools at all.
I am going to test a GnuWin32 build but wondered if you, or anyone
else on this list, has worked with GnuWin32 before and might know if
there are any problems with these packages?
Cheers,
Pete
_______________________________________________
Cvs-ghc mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/cvs-ghc
