* use it in-place, i.e., don't go ahead with a
full install, but just set it up to use the unpacked
- distribution from where it was unpacked.
+ distribution in-situ.
* get it over with, and do the full install (details of how are ahead).
This will figure out what platform you're running on, and a couple of other
interesting pieces of trivia, which it will then fill in the Makefile.in
-template to give you a real Makefile.
+template to give you a real Makefile.
+
+[Win32 users: don't be alarmed if you should encounter the following
+ message from the configure script:
+
+ not updating unwritable cache ./config.cache
+
+This is a known problem of generated autoconf configure scripts running
+on cygwin, but harmless (it only means you get to re-do all the configure
+tests should you decide to re-run the script.)
+]
Have a look at the Makefile to see if you agree with the information
therein. If you want to use the bundle in-place, now run `make in-place'.
-- possibly helpful).
For more information, please consult the installation guide in
-{html,dvi,info}/ghc-2.02/installing{.dvi,.info,_toc.html}.
+{html,dvi,info}/ghc-<version>/installing{.dvi,.info,_toc.html}.
Bug reports/suggestions for improvement to the installation procedure/setup
(as well as other GHC related troubles you're experiencing, of course),
-------Win32 users only----------------------------------------
NOTE to Win32 users: to enjoy any sort of happiness with the GHC
-tools, you will have to install the cygwin32 toolchain, which dresses
+tools, you will have to install the cygwin toolchain, which dresses
up the Win32 environment into something more UNIX-like (which
-this initial port of ghc relies on being the case). The cygwin32 tools
+this initial port of ghc relies on being the case). The cygwin tools
are available from
- ftp://ftp.cygnus.com/pub/gnu-win32/gnu-win32-b17.1/
- (Cygnus Solutions; Mt. View, CA.)
- ftp://sunsite.doc.ic.ac.uk/pub/gnu/cygnus/gnu-win32/
- (Sunsite Northern Europe; Imperial College, London)
- ftp://ftp.crl.go.jp/pub/GNU/cygnus/gnu-win32/
- (CRL, Ministry of Posts and Telecom., Japan)
-
-GHC was built with beta17 - you *might* get away with beta16 if you've already got it
-installed...not tested this though.
+ http://sourceware.cygnus.com/cygwin/
-The GHC tools are also quite picky about Perl, the commonly-used
-Hip/ActiveWare Win32 port of perl5 just ain't Cool Enough (main reason:
-GHC scripts assume they are talking to an underlying UNIX command
-shell). A port of perl5.003 done on top of cygwin32-b17 is just
-the ticket though, it is available from
+GHC was built with beta20.1 of the cygwin tools and depends on it
+to work.
- http://www.edv.agrar.tu-muenchen.de/~syring/gnu-win32/
+Install cygwin before continuing. Couple of things to remember
+doing while installing these two:
-this port is not complete - but the binaries available from there
-are sufficiently wonderful.
+ - Create a toplevel /bin directory, and copy bash.exe into it
+ as sh.exe (we'll need this for running the configure script.)
+ Add /bin to your PATH.
+ - Create a toplevel /tmp directory.
-Install both cygwin32&perl5 before continuing.
+Additionally, ghc requires perl to operate, so included in the
+binary distribution is a perl binary, (perl.exe in the toplevel
+directory.) Install (as in copy :-) this somewhere along your
+PATH too (/bin is a good choice.)
-Future releases of GHC for Win32 may very well avoid relying on
-cygwin32 to operate, for various reasons..
+This is hardly beatiful, but it avoids having to download and install
+yet another package, including piles of (useful) perl libraries that the
+ghc perl code does not require to operate. Besides which, there's a
+dearth of readily useable perl distributions 'out there' that contain
+cygwin-compiled binaries, something we really do depend on.
-------Win32 users only----------------------------------------
projects / ghc-hetmet.git / blobdiff