Windows build issues
claus.reinke at talk21.com
Wed Sep 17 09:07:45 EDT 2008
>Before I fix the documentation the GHC team needs to make a decision -
>do you want to support the latest mingw/cygwin, or advise people to use
>specific old versions?
>The old versions work exactly as per the descriptions Claus gave
>(although there are a few tweaks required for bootstrapping with GHC
Thanks, that is good to know. Please add any tweaks needed.
>The new version has a number of issues that need fixing:
>1) Windres doesn't work.
>2) cc1 is in the wrong place, and can't be found.
>3) one line needed commenting out in the mingw headers.
>My preference is to use the latest versions, otherwise we'll run into
>some other bug and the mingw people will (legitimately) tell us to use a
>newer version, requiring us to upgrade everything anyway. I think Claus
>disagrees with me on this.
Actually, I don't disagree. A bit of background: before that log, the
wiki pages simply said get the latest versions of everything, and every
single time I had to do that on a new machine, something else would
go wrong (autoconf, mingw, cygwin, ..). So that log was an attempt
to give one single known-to-work reference path. The generic "try
the newest versions, but watch out for .." instructions are still there,
the log was just added at the end, for users who prefer concrete
If it can be made to work with newer versions, that is preferred (eg,
6.8.3 should replace 6.4.1, darcs2.0.2(+76patches) should replace
darcs1, etc.). Just make sure that the log still gives _specific working
versions_, in a form that is *known* (not hoped;-) to work when
starting from a new machine. That's all I ask:-)
More information about the Cvs-ghc