--- gforth/INSTALL	1995/11/27 18:37:06	1.14
+++ gforth/INSTALL	1996/01/07 17:22:06	1.18
@@ -4,14 +4,6 @@ First, type
 
 ./configure
 
-or better
-
-CC=gcc ./configure
-
-or however your gcc is called; because configure needs cc to find out some
-parameters, and there may be differences in what is obtained from gcc and
-from ghe default cc.
-
 configure has the following useful parameters:
   --prefix=PREFIX         install architecture-independent files in PREFIX
                           [default: /usr/local]
@@ -36,21 +28,23 @@ configure has the following useful param
 If you don't like the defaults for the installation directories, you
 should override them already during configure.  E.g., if you want to
 install in the /gnu hierarchy instead of in the default /usr/local
-hirarchy, say
+hierarchy, say
 
 ./configure --prefix=/gnu
 
-After, configuration, type
+Moreover, if your GCC is not called gcc (but, e.g., gcc-2.7.1), you
+should say so during configuration. E.g.:
 
-make
+env CC=gcc-2.7.1 ./configure
 
-If your make has trouble with the Makefile, "make gforth" might work.
+You can also pass additional options to gcc in this way, e.g., if you
+want to generate an a.out executable under Linux with gcc-2.7.0:
 
-If your installed gcc isn't called "gcc" (e.g., called "gcc-2.6.1"), type
+env "CC=gcc -b i486-linuxaout -V 2.7.0" ./configure
 
-make GCC=<whatever you call your gcc>
+After, configuration, type
 
-instead.
+make
 
 Now you can check whether your shiny new Forth system works. Say
 
@@ -79,6 +73,8 @@ documentation in HTML format by typing
 
 make html
 
+If you prefer plain ASCII documentation, just concatenate the files
+gforth.info-* ('cat gforth.info-*' under Unix).
 
 		Preloading installation-specific code