X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=docs%2Fbuilding.sgml;h=b7c3fbba51677781543db64d96ffe004b69e38e7;hb=c39373f1371fd1e46ea91be262f00c277b31f8e5;hp=4e8c9e82833ef28c17c86f26a860a5ec3fd84408;hpb=4afec09558abd5b61846fd4f527ee2f9c0e0a052;p=ghc-hetmet.git diff --git a/docs/building.sgml b/docs/building.sgml index 4e8c9e8..b7c3fbb 100644 --- a/docs/building.sgml +++ b/docs/building.sgml @@ -650,7 +650,7 @@ URL="http://sourceware.cygnus.com/docbook-tools/">Cygnus DocBook tools, which is the most shrink-wrapped SGML suite that we could find. Unfortunately, it's only packaged as RPMs. You can use it to generate HTML, DVI (and hence PDF and Postscript) and RTF from any -DocBook source file (including this manual). +DocBook source file (including this manual). N.B. The Cygnus version of the tools is assumed. Others, such as the SuSE version, may not work. @@ -819,10 +819,11 @@ from the source is that the build tree can be placed in a non-backed-up partition, saving your systems support people from backing up untold megabytes of easily-regenerated, and rapidly-changing, gubbins. The golden rule is that (with a single -exception— absolutely everything in the build tree is either -a symbolic link to the source tree, or else is mechanically -generated. It should be perfectly OK for your build tree to vanish -overnight; an hour or two compiling and you're on the road again. +exception—) +absolutely everything in the build tree is either a symbolic +link to the source tree, or else is mechanically generated. +It should be perfectly OK for your build tree to vanish overnight; an +hour or two compiling and you're on the road again. @@ -919,12 +920,13 @@ Runs the newly-created configure script, thus: ./configure -configure's mission is to scurry round your computer working out -what architecture it has, what operating system, whether it has the -vfork system call, where yacc is kept, whether gcc is available, -where various obscure #include files are, whether it's a leap year, -and what the systems manager had for lunch. It communicates these -snippets of information in two ways: +configure's mission is to scurry round your +computer working out what architecture it has, what operating system, +whether it has the vfork system call, where +yacc is kept, whether gcc is +available, where various obscure #include files +are, whether it's a leap year, and what the systems manager had for +lunch. It communicates these snippets of information in two ways: @@ -1250,8 +1252,12 @@ file. Typing gmake alone is generally the same as typing installs the things built by all. Where does it -install them? That is specified by mk/config.mk.in; you can -override it in mk/build.mk. +install them? That is specified by +mk/config.mk.in; you can override it in +mk/build.mk, or by running +configure with command-line arguments like +--bindir=/home/simonpj/bin; see ./configure +--help for the full details. @@ -2477,11 +2483,14 @@ vagaries of different systems, it seems. The solution is simple: - If you're compiling with GHC 4.00 or above, then the -maximum heap size must have been reached. This is somewhat -unlikely, since the maximum is set to 64M by default. Anyway, you can -raise it with the flag (add this flag to -<module>_HC_OPTS make variable in the appropriate Makefile). + If you're compiling with GHC 4.00 or later, then the +maximum heap size must have been reached. This +is somewhat unlikely, since the maximum is set to 64M by default. +Anyway, you can raise it with the + flag (add this flag to +<module>_HC_OPTS +make variable in the appropriate +Makefile).