| Is installing a newer version of msys/mingw an option? The version I | have here has autoreconf version 2.68, which I expect would just work.
Interesting. I had assumed that we used autoreconf from inplace/mingw/bin. But there is no autoreconf there. So in fact the build system is using it from c:/mys/1.0/bin. Is that right? 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?? I have been to the msys/mingw install page http://www.mingw.org/wiki/Getting_Started, downloaded mingw-get-inst, and run it. It lets you decide what to install. If you choose "MSYS basic system" you don't get autoreconf. If you choose "MSYS developer toolkit" you do get autoreconf, in c:/mingw/bin. But you get a lot of other developer-toolkit stuff too. To me the simple solution is to add autoreconf to our msys tar-ball, and make 'perl boot' refer to it by explicit path (to avoid accidentally getting the installed one if there is one). Does that make sense? Simon _______________________________________________ Cvs-ghc mailing list Cvs-ghc@haskell.org http://www.haskell.org/mailman/listinfo/cvs-ghc
