adapting to phototypesetter

doc/install.doc

@@ -1,12 +1,11 @@
 .\" $Header$
-.nr LL 7.5i
 .nr PD 1v
 .TL
-Amsterdam Compiler Kit installation guide
+Amsterdam Compiler Kit Installation Guide
 .AU
 Ed Keizer
 .AI
-Wiskundig Seminarium
+Vakgroep Informatica
 Vrije Universiteit
 Amsterdam
 .NH
@@ -33,16 +32,16 @@ The process of installing Amsterdam Compiler Kit is quite simple.
 It is important that the original Amsterdam Compiler Kit
 distribution tree structure is restored.
 Proceed as follows
-.IP "  -" 10
+.IP "  \-" 10
 Create a directory, for example /usr/em, on a device
 with at least 15 Megabytes left.
-.IP "  -"
+.IP "  \-"
 Change to that directory (cd ...); it will be the working directory.
-.IP "  -"
+.IP "  \-"
 Extract all files from the distribution medium, for instance
 magtape:
 \fBtar x\fP.
-.IP "  -"
+.IP "  \-"
 Keep a copy of the original distribution to be able to repeat the process
 of installation in case of disasters.
 This copy is also useful as a reference point for diff-listings.
@@ -143,29 +142,31 @@ These directories have subdirectories named:
 .in +3n
 .TS
 l l.
-as	the assembler ( *.s + libraries => a.out )
 cg	the backend   ( *.m => *.s )
 ncg	the new backend   ( *.m => *.s )
+as	the assembler ( *.s + libraries => a.out )
+cv	Conversion programs for a.out files.
+dl	Down-load programs
+
+libem	Sources for EM runtime system, intended to depend only on CPU type
 libbc	Used to create Basic run-time system and libraries
 libcc	Used to create C run-time system and libraries
 libpc	Used to create Pascal run-time system and libraries
-libem	Sources for EM runtime system, intended to depend only on CPU type
 libsys	Sources for system-dependent EM library
 test	Various tests
-dl	Down-load programs
-cv	Conversion programs for a.out files.
+
 int	Source for an interpreter
 .TE
 .in -3n
-The directory proto contains files used by most machines
+The directory proto contains files used by most machines,
 like machine-independent sources and Makefiles.
 .in +3n
 .TS
 l l.
-mach/proto/libg	Makefile for compiling libraries.
-mach/proto/as	Assembler sources.
 mach/proto/cg	Current backend sources.
 mach/proto/ncg	New backend sources.
+mach/proto/as	Assembler sources.
+mach/proto/libg	Makefile for compiling libraries.
 .TE
 .IP "emtest"
 .br
@@ -277,14 +278,14 @@ first in a directory of the same name.
 .LP
 These actions are:
 .sp 1
-.IP -
+.IP \-
 Automatically checking whether you included the ACK bin directory in your
 shell PATH.
 See also the section on "commands".
-.IP -
+.IP \-
 Automatically setting the pathname of the parent directory in ../h/em_path.h.
 See also the section on "pathnames".
-.IP -
+.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
@@ -313,12 +314,12 @@ For ANY you can use any name you fancy,
 but the Kit will not be able to compile programs for your system.
 If you want to do that you have to read the section about "compilation
 on a different machine".
-.IP -
+.IP \-
 Automatically setting the default machine for which code is
 produced to your own type of system according to the table above.
 This in done in the file "h/local.h".
 See also the section 8.2.
-.IP -
+.IP \-
 Automatically editing a few description files that tell
 ACK to use your system's assembler.
 On both the PDP and the VAX the Kit uses the native assembler and linker.
@@ -326,14 +327,14 @@ The description files in lib/pdp/descr, lib/vax2/descr and
 lib/vax4/descr have to be altered to prevent
 attempts to assemble programs with unsuitable assemblers.
 The original descr files are copied to descr.orig.
-.IP -
+.IP \-
 Automatically installing the special include directory for vax2.
 This will only be done on VAX systems.
 The shell scripts needed by ACK for the vax2 backend differ slightly
 from the one issued by Berkeley.
 .br
 Note: this has only been tested under BSD4.1a.
-.IP -
+.IP \-
 Automatically editing the system.h file in mach/vax[24]/libem.
 Again, only on VAXen.
 These files reflect whether you have BSD4.1a, BSD4.1c or BSD4.2.
@@ -341,7 +342,7 @@ These files reflect whether you have BSD4.1a, BSD4.1c or BSD4.2.
 .sp 1
 Some actions still have to be done by hand.
 .sp 1
-.IP -
+.IP \-
 The VAX backends cannot be booted on systems
 with a 16-bit address space systems.
 The program lib/cgg needs more memory than available to transform
@@ -354,18 +355,18 @@ 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.
-.IP -
+.IP \-
 The installation of the PUBMAC macro package is not done
 automatically because you needs super-user privileges to do
 that on most systems.
 This macro package is used with several of the documents
 provided in the Kit.
-.IP -
+.IP \-
 UNIX V7 as originally distributed contains a few bugs that
 prevent correct execution of some of the larger programs.
 See the section named "Fixes for the UNIX V7 system"
 about what to do.
-.IP -
+.IP \-
 The manual files for the Kit can be copied to their
 appropriate place in the system by giving the command "make install"
 in the man directory.
@@ -788,7 +789,7 @@ Sometimes the system differs so much from V7 that certain manifest constants
 do not exist any more.
 At other times these include files were written for a compiler without
 a restriction on name length.
-In that case - I've seen it happen - people tend to use differing
+In that case \- I've seen it happen \- people tend to use differing
 identifiers that are identical in the first eight characters.
 All these problems you have to solve yourself,
 the libraries are only included as an extra and too much system