updated

doc/install.doc

@@ -67,7 +67,7 @@ root of a tree containing almost all binaries and libraries used by
 commands.
 All files specific to a certain machine are collected in one subtree
 per machine. E.g. "lib/pdp", "lib/z8000".
-The names used here are the same names as used for subdirectories
+The names used here are the same names as used for subtrees
 of "mach".
 .IP "lib/descr"
 .br
@@ -76,6 +76,10 @@ Command descriptor files used by the program ack.
 .br
 Files used by the LL(1) Parser-generator.
 .br
+.IP "lib/ego"
+.br
+Files used by the global optimizer.
+.br
 .IP "etc"
 .br
 The main description of EM sits here.
@@ -152,10 +156,10 @@ This directory contains the unformatted documents for the Kit.
 A list of the available documents can be found in the last section.
 .IP "doc/em"
 .br
-The EM-manual IR-81
+The EM-manual IR-81.
 .IP "doc/em/int"
 .br
-The EM interpreter written in Pascal
+The EM interpreter written in Pascal.
 .IP "mkun"
 .br
 The PUBMAC macro package for nroff/troff from the Katholieke Universiteit at
@@ -352,6 +356,12 @@ See also the section on "commands".
 Automatically setting the pathname of the parent directory in ../h/em_path.h.
 See also the section on "pathnames".
 .IP \-
+Discovering how to call
+.I cc
+to get it to include the
+.I lex
+library.
+.IP \-
 Asking you for the type of system you have
 and creating the shell script "ack_sys" in the Kit's bin directory.
 Several utilities make use of "ack_sys" to determine the type of
@@ -409,9 +419,23 @@ You will hardly be able to use these, because the
 code generated by these programs cannot be
 assembled and loaded without a native VAX assembler,
 but its nice to be able to look at the code produced.
+The same problem occurs for the m68k2 backend and the m68020 backend,
+and the same solution is chosen.
 .IP \-
-For the m68k2 backend, the same problem occurs, and the same
+On machines with a 16-bit address space, the C-compiler has no 
-solution is chosen.
+builtin preprocessor. Arangements are made to this effect.
+.IP \-
+On the PDP, 
+.I ranlib
+is not used, because it does not work properly,
+at least, on our 2.9 BSD system it does'nt. 
+This is done by creating a dummy shell script
+.I ranlib
+in the ACK bin directory.
+If you are sure that your
+.I ranlib
+does work properly, you can just remove the shell script before
+installing the Kit.
 .LP
 .sp 1
 Some actions still have to be done by hand.
@@ -1002,6 +1026,18 @@ Floating point registers are not copied to child in fork().
 .LP
 Use the test programs to see if the errors are present in your system
 and to check if the modifications are effective.
+.PP
+You may also have to change /usr/src/cmd/cc.c (/bin/cc) to pass the
+.B -i
+flag to
+.I ld.
+Also, /usr/src/cmd/ld.c (/bin/ld) may have to be changed to increase the
+number of library positions it can hold.
+On our (2.9 BSD) version, this is the constant
+.I NROUT.
+It must be at least 400.
+This may require separate I&D.
+Also, our version does not check that the table does not overflow.
 .NH
 Testing
 .PP