From: rrt Date: Tue, 22 May 2001 12:00:05 +0000 (+0000) Subject: [project @ 2001-05-22 12:00:05 by rrt] X-Git-Tag: Approximately_9120_patches~1903 X-Git-Url: http://git.megacz.com/?a=commitdiff_plain;h=e48d54da203c969faae1bf2524e848ca6e3e69a4;p=ghc-hetmet.git [project @ 2001-05-22 12:00:05 by rrt] Add changes for latest 4.08.2 InstallShield; merge into 4.08 branch, especially as the HEAD story will soon change with the New Improved Windows System for GHC 5. --- diff --git a/docs/building/building.sgml b/docs/building/building.sgml index 89e60e0..cf116dc 100644 --- a/docs/building/building.sgml +++ b/docs/building/building.sgml @@ -1180,11 +1180,12 @@ emacs mk/build.mk -You can make subsequent changes to mk/build.mk as often -as you like. You do not have to run any further configuration -programs to make these changes take effect. -In theory you should, however, say gmake clean, gmake all, -because configuration option changes could affect anything—but in practice you are likely to know what's affected. +You can make subsequent changes to mk/build.mk as often +as you like. You do not have to run any further configuration programs to +make these changes take effect. In theory you should, however, say +gmake clean, gmake all, because +configuration option changes could affect anything—but in practice you +are likely to know what's affected. @@ -2650,11 +2651,23 @@ guide) before continuing to read these notes. -Before you start, make sure you've installed Cygwin (from cygwin.org). You also need to make -sure that the user environment variable MAKE_MODE -is set to UNIX. If you don't do this you get very -weird messages when you type make, such as: +Because of various hard-wired infelicities, you need to copy +bash.exe (from GHC's extra-bin +directory) and perl.exe (from GHC's +bin directory) to /bin (discover +where your Cygwin root directory is by typign mount). If +you want to use bash as the shell in Emacs, you need to set the +SHELL environment variable to point to +bash.exe; similarly, if you want to use CVS, then +CVS_RSH must point to ssh.exe, +which is also in GHC's extra-bin directory. + + + +Before you start, you need to make sure that the user environment variable +MAKE_MODE is set to UNIX. If you +don't do this you get very weird messages when you type +make, such as: /c: /c: No such file or directory @@ -2788,7 +2801,8 @@ optional. Try doing cvs co fpconfig. All being well, bytes should start to trickle through, leaving a directory fptools -in your current directory. (You can rm it if you don't want to keep it.) The following messages appear to be harmless: +in your current directory. (You can rm it if you don't +want to keep it.) The following messages appear to be harmless: @@ -2798,10 +2812,10 @@ setsockopt IPTOS_THROUGHPUT: Invalid argument At this point I found that CVS tried to invoke a little dialogue with -me (along the lines of `do you want to talk to this host'), but -somehow bombed out. This was from a bash shell running in emacs. +me (along the lines of `do you want to talk to this host?'), but +for some reason bombed out. This was from a bash shell running in Emacs. I solved this by invoking a Cygnus shell, and running CVS from there. -Once things are dialogue free, it seems to work OK from within emacs. +Once things are dialogue free, it seems to work OK from within Emacs.