Mitchell, Neil wrote:
Hi
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 and simple.
Ah, now that seems a really good idea. I'll be getting a home computer
in the next month, so will prepare a set of instructions then, and test
them out on my new machine. I guess the way to keep a list such as this
up to date is to keep a Virtual Machine around, and reinstall from
scratch every so often.
I object (mildly) to having multiple sets of build instructions. It
doesn't seem possible to keep even one set up to date and working, let
alone two. Furthermore, we don't want to confuse someone who "just wants
to build GHC" with a decision between two subtly different sets of
instructions.
Cheers,
Simon
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
