X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=docs%2Fbuilding%2Fbuilding.sgml;h=1bb92d5e9636090f3a3711a34616275a117395e2;hb=c0c05bb3fbfdd1a82bccdcbc34c77a4927c99316;hp=df516880049cca89a5d633d13e1f17bab42380ae;hpb=9fb45abf5ad47f90746aa71cf0ec0ac83e8a6d83;p=ghc-hetmet.git
diff --git a/docs/building/building.sgml b/docs/building/building.sgml
index df51688..1bb92d5 100644
--- a/docs/building/building.sgml
+++ b/docs/building/building.sgml
@@ -137,6 +137,12 @@
Set your $CVSROOT environment variable to
:pserver:anoncvs@glass.cse.ogi.edu:/cvs
+ If you set $CVSROOT in a shell script, be sure not to
+ have any trailing spaces on that line, otherwise CVS will respond with
+ a perplexing message like
+
+ /cvs : no such repository
+
Run the command
@@ -1116,6 +1122,14 @@ $ cvs checkout nofib/spectral
+ mips64-sgi-irix6
+ mips-sgi-irix6
+
+ GHC currently works unregisterised.
+
+
+
+
powerpc-ibm-aix
powerpc-ibm-aix
@@ -4093,10 +4107,13 @@ Hello World!
To support GHCi, you need to port the dynamic linker
(fptools/ghc/rts/Linker.c). The linker
currently supports the ELF and PEi386 object file formats - if
- your platform uses one of these then you probably don't have
- to do anything except fiddle with the
- #ifdefs at the top of
- Linker.c to tell it about your OS.
+ your platform uses one of these then things will be
+ significantly easier. The majority of Unix platforms use the
+ ELF format these days. Even so, there are some
+ machine-specific parts of the ELF linker: for example, the
+ code for resolving particular relocation types is
+ machine-specific, so some porting of this code to your
+ architecture will probaly be necessary.
If your system uses a different object file format, then
you have to write a linker — good luck!
@@ -4428,14 +4445,37 @@ but you do need it to build GHC.
Install Cygwin from http://www.cygwin.com/.
The installation process is straightforward; we install it in c:/cygwin.
-During the installation dialogue, make sure that you select:
-cvs, openssh,
-autoconf,
-binutils (includes ld and (I think) ar),
-gcc,
-flex,
-make.
-
+During the installation dialogue, make sure that you select all of the following:
+
+
+ cvs,
+
+
+ openssh,
+
+
+ autoconf,
+
+
+ automake,
+
+
+ binutils (includes ld and (I think) ar),
+
+
+ gcc,
+
+
+ flex,
+
+
+ make.
+
+
+If you miss out any of these, strange things will happen to you. To see thse packages,
+click on the "View" button in the "Select Packages"
+stage of Cygwin's installation dialogue, until the view says "Full". The default view, which is
+"Category" isn't very helpful, and the "View" button is rather unobtrousive.
Now set the following user environment variables:
@@ -4455,7 +4495,7 @@ don't do this you get very weird messages when you type
Set SHELL to
-c:/cygwin/bin/sh. When you invoke a shell in Emacs, this
+c:/cygwin/bin/bash. When you invoke a shell in Emacs, this
SHELL is what you get.