| > We had all these version-skew problems between MSYS and our build
| > system, which we beautifully resolved by including a tar-ball of
| > guaranteed-compatible msys binaries in the GHC source repo (and GHC
| > distributions). The C compiler is there, the linker. Why not
| > autoreconf??
|
| All the build tools are installed separately, we only have the compiler
| tools in the repository.
What "build tools" do you have in mind? Apart from 'autoreconf'?
For example, the in-tree tarball (unpacked to inplace/mingw/bin) includes
gcc
ld
ar
as
cpp
nm
ranlib
strip
What build tools do you expect to use from the user's mingw installation? What
is the downside of including all stuff that suffers version skew (of which
autoreconf is an example), thus removing a road-block? For example, maybe
cygwin's autoreconf behaves slightly differently.
Simon
_______________________________________________
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/listinfo/cvs-ghc
