--- gforth/INSTALL	1998/12/26 15:41:24	1.28
+++ gforth/INSTALL	2002/03/13 16:59:12	1.31
@@ -12,7 +12,7 @@ make
 
 Now you can check whether your shiny new Forth system works. Say
 
-make test
+make check
 
 You can run some benchmarks with
 
@@ -24,7 +24,8 @@ If everything is all right, you may want
 
 make install
 
-You have to make an entry in the info directory file manually.
+You have to make an entry in the info directory file manually (see
+Installing Info Files, below).
 
 For paper documentation, print gforth.ps (a Postscript file (300dpi
 fonts, i.e., it works, but does not produce best quality on better
@@ -118,18 +119,52 @@ that it does not use "long long":
 env ac_cv_sizeof_long_long=0 ./configure
 
 
-			Cross-Configuration
+			Cross-Installation
 
-A few tests made by the configure script do not work in a
+You need a cross-compilation toolchain for your target including gcc
+(2.0 or later).
+
+The first step in cross-installation is the cross-configuration.  A
+few tests made by the configure script do not work in a
 cross-compilation situation. You have to provide the results of these
 tests by hand. E.g., if you compile for a 386 architecture processor:
 
-env ac_cv_sizeof_char_p=4 ac_cv_sizeof_short=2 ac_cv_sizeof_int=4 ac_cv_sizeof_long=4 ac_cv_sizeof_long_long=8 ac_cv_c_bigendian=no ./configure
+env ac_cv_sizeof_char_p=4 ac_cv_sizeof_char=1 ac_cv_sizeof_short=2 ac_cv_sizeof_int=4 ac_cv_sizeof_long=4 ac_cv_sizeof_long_long=8 ac_cv_c_bigendian=no ./configure
 
 The ac_cv_sizeof_... variables give the sizes of various C types;
 ac_cv_sizeof_char_p is the same as "sizeof(char*)" in C code. The
 ac_cv_c_bigendian variable gives the byte order.
 
+After the cross-configuration you type
+
+make gforths
+
+This produces the gforth engines for the target.
+
+The next step is to transfer everything to the target; on the target,
+you do
+
+make
+
+to complete building gforth.  If you do not have a make on the target,
+run
+
+make -n
+
+on the host; manually execute on the target the last command output by
+"make -n" (GFORTHD=...); the other commands output by "make -n" are
+not necessary unless you have changed the Gforth sources.  You can
+then check and benchmark Gforth with
+
+make check
+make bench
+
+or equivalent.  Finally, perform
+
+make install
+
+or the equivalent commands on the target.
+
 
 		Preloading installation-specific code
 
@@ -162,3 +197,28 @@ keep the old version for some time after
 You can deinstall this version of Gforth with 'make uninstall' and
 version foo with 'make uninstall VERSION=foo'. 'make uninstall' also
 tells you how to uninstall Gforth completely.
+
+
+		Installing Info Files
+
+Info is the GNU project on-line documentation format. You can read
+info files either from within Emacs (Ctrl-h i) or using the
+stand-alone Info reader, 'info'.
+
+If you use the default install root of '/usr/local' then the info
+files will be installed in '/usr/local/info'.
+
+Many GNU/Linux distributions are set up to put all of their
+documentation in '/usr/info', in which case you might have to do a
+couple of things to get your environment set up to accommodate files
+in both areas:
+
+1. Add an INFOPATH environment variable. The easiest place to do
+this is '/etc/profile', right next to PATH and MANPATH:
+
+INFOPATH=/usr/local/info:/usr/info
+
+2. Create a file called 'dir' in 'usr/local/info'. Use the file
+'/usr/info/dir' as a template. You can add the line for gforth
+manually, or use '/sbin/install-info' (man install-info for details).
+