From: rrt Date: Wed, 21 Feb 2001 17:23:59 +0000 (+0000) Subject: [project @ 2001-02-21 17:23:59 by rrt] X-Git-Tag: Approximately_9120_patches~2569 X-Git-Url: http://git.megacz.com/?a=commitdiff_plain;h=7ca251d72f69c2873b55dfcd364490be23d7d196;p=ghc-hetmet.git [project @ 2001-02-21 17:23:59 by rrt] Tidied up and removed discussion of solved mingw package problem. --- diff --git a/ghc/docs/users_guide/installing.sgml b/ghc/docs/users_guide/installing.sgml index 1c13c69..3ba9520 100644 --- a/ghc/docs/users_guide/installing.sgml +++ b/ghc/docs/users_guide/installing.sgml @@ -528,7 +528,14 @@ your machine to run GHC. System requirements -An installation of GHC requires about 50M of disk space (which can be lowered by choosing a “compact” installation). The Cygwin support tools take another 200M or so (though if you really need to this can be halved by installing only the following packages: bash, binutils, cygwin, diff, fileutils, findutils, gcc, grep, make, perl, mingw, sed, textutils, w32api; however, it's fiddly and not recommended). To run GHC +An installation of GHC requires about 50M of disk space (which can be +lowered by choosing a “compact” installation). The Cygwin +support tools take another 200M or so (though if you really need to this can +be halved by installing only the following packages: bash, binutils, cygwin, +diff, fileutils, findutils, gcc, grep, make, perl, mingw, sed, textutils, +w32api; however, it's fiddly and not recommended, and if you're trying to +build rather than just use GHC, you need many more, so you might as well +install the lot). To run GHC comfortably, your machine should have at least 64M of memory. @@ -881,22 +888,6 @@ unfortunately. Anyway, better to install 4.08 binaries and use those. - - - - -My programs compile fine but do nothing when run. - - - - Some recent versions of the mingw package in Cygwin seem to -cause this. mingwin version 20001111-1 works fine; you should be able to -select it by clicking on the version number of the mingw package in the list -presented by the Cygwin setup program. - - - - @@ -908,7 +899,10 @@ presented by the Cygwin setup program. Building the documentation -We use the DocBook DTD, which is widely used. Most shrink-wrapped distributions seem to be broken in one way or another; thanks to heroic efforts by Sven Panne and Manuel Chakravarty, we now support most of them, plus properly installed versions. +We use the DocBook DTD, which is widely used. Most shrink-wrapped +distributions seem to be broken in one way or another; thanks to +heroic efforts by Sven Panne and Manuel Chakravarty, we now support +most of them, plus properly installed versions. @@ -918,20 +912,20 @@ Instructions on installing and configuring the DocBook tools follow. Installing the DocBook tools from RPMs - If you're using a system that can handle RedHat RPM packages, you can -probably use the If you're using a system that can handle RedHat RPM packages, +you can probably use the Cygnus DocBook -tools, which is the most shrink-wrapped SGML suite that we could -find. You need all the RPMs except for psgml (i.e. +tools, which is the most shrink-wrapped SGML suite that we +could find. You need all the RPMs except for psgml (i.e. docbook, jade, jadetex, sgmlcommon and stylesheets). Note that most of these RPMs are architecture neutral, so are likely to be found in a -noarch directory. The SuSE RPMs also work; the RedHat -ones don't as of version 6.2, but they are easy to fix: -just make a symlink from -/usr/lib/sgml/stylesheets/nwalsh-modular/lib/dblib.dsl to -/usr/lib/sgml/lib/dblib.dsl. +noarch directory. The SuSE RPMs also work; the +RedHat ones don't in RedHat 6.2 (7.0 and later +should be OK), but they are easy to fix: just make a symlink from +/usr/lib/sgml/stylesheets/nwalsh-modular/lib/dblib.dsl +to /usr/lib/sgml/lib/dblib.dsl.