Re: What tool versions (MinGW, MSYS, automake, etc.) do I need to build GHC on Windows?

11 Sep 2006

      Sorry, My message got sent prematurely. I was saying that the whole suite of
tools needed to build GHC, Hugs, and Darcs on MSYS takes about 575MB; Cygwin
is about 115MB of that and GHC 6.4.2 is 300MB of it.

I have managed to get the binaries, HTML documentation (not DVI, PS, or
PDF), and tests to build/run for GHC HEAD and Hugs HEAD. I am still working
on Darcs HEAD.

The versions of the tools I am using are:

MinGW/MSYS Current:
    binutils 2.15.91-20040904
    bison 2.0
    gcc-core 3.4.2.20040916-1
    gcc-g++ 3.4.2.20040916-1
    mingw-runtime 3.9
    mingw-utils 0.3
    MSYS 1.0.10
    MSYS DTK 1.0.1
    libtool 1.5
    w32api-3.6
    automake 1.8.2
    autoconf 2.59
CVS 1.11.22
DocBook XML 4.2
DocBook XSL 1.71.0
iconv 1.9.2
libcurl 7.15.4
libxml2 2.6.26
libxslt 1.1.17
zlib 1.2.3
Darcs 1.0.7
OpenSSL 0.9.8c
Haddock 0.8 (HEAD as of today, the latest release, 0.7, will not build the
GHC HEAD unmodified)
Alex 2.0.1
Happy 1.15
GHC 6.4.2
Cygwin (latest as of today TODO: need version numbers)

Regards,
Brian

On 9/10/06, Brian Smith  wrote:
...
On 9/8/06, Simon Peyton-Jones  wrote:
...
I do recommend using MSYS as the environment, though.   I find that GHC
builds much, much faster using MSYS than using Cygwin.
I always use MSYS, not Cygwin, when building GHC and Hugs. (MSYS is pretty
slow too--I can build GHC faster in Ubuntu 6.06 in VMWare than I can when
building it using MinGW.) But, I still need Cygwin because the tests require
Cygwin python for some reason.
The tools needed to build GHC, Hugs, and Darcs take about 575MB of disk
space. Cygwin takes
Do you know what tool versions are used for the automated builds?
Re