Diff for /gforth/INSTALL between versions 1.19 and 1.21

version 1.19, 1996/05/03 13:05:04 version 1.21, 1996/09/30 13:16:06
Line 4  First, type Line 4  First, type
   
 ./configure  ./configure
   
   (see Section Configuration Options below for details).
   
   After configuration, type
   
   make
   
   Now you can check whether your shiny new Forth system works. Say
   
   make test
   
   You can run some benchmarks with
   
   make bench
   
   and compare them with the results in Benchres and in the manual.
   
   If everything is all right, you may want to install gforth. Type
   
   make install
   
   You have to make an entry in the info directory file manually.
   
   For paper documentation, print gforth.ps (a Postscript file (300dpi
   fonts, i.e., it works, but does not produce best quality on better
   printers)), or say
   
   make gforth.dvi
   
   and print the resulting file gforth.dvi. You can also get the
   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).
   
   
                   Configuration Options
   
   You can build in a directory different from the source directory by
   changing to the build directory and invoking configure thus:
   
   $srcdir/configure
   
   where $srcdir is the source directory (Note that we tested this only
   for installation; i.e., if you want to hack the Gforth sources, you
   should probably build in the source directory).
   
 configure has the following useful parameters:  configure has the following useful parameters:
   --prefix=PREFIX         install architecture-independent files in PREFIX    --prefix=PREFIX         install architecture-independent files in PREFIX
                           [default: /usr/local]                            [default: /usr/local]
Line 25  configure has the following useful param Line 73  configure has the following useful param
                     debugging informations.                      debugging informations.
   --help: tells you about other parameters.    --help: tells you about other parameters.
   
   The file Benchres shows which combination of the -enable options we
   tried gave the best results for various machines.
   
 If you don't like the defaults for the installation directories, you  If you don't like the defaults for the installation directories, you
 should override them already during configure.  E.g., if you want to  should override them already during configure.  E.g., if you want to
 install in the /gnu hierarchy instead of in the default /usr/local  install in the /gnu hierarchy instead of in the default /usr/local
Line 42  want to generate an a.out executable und Line 93  want to generate an a.out executable und
   
 env "CC=gcc -b i486-linuxaout -V 2.7.0" ./configure  env "CC=gcc -b i486-linuxaout -V 2.7.0" ./configure
   
 After, configuration, type  
   
 make  
   
 Now you can check whether your shiny new Forth system works. Say  
   
 make test  
   
 You can run some benchmarks with  
   
 make bench  
   
 and compare them with the results in Benchres and in the manual.  
   
 If everything is all right, you may want to install gforth. Type  
   
 make install  
   
 You have to make an entry in the info directory file manually.  
   
 For paper documentation, print gforth.ps (a Postscript file (300dpi  
 fonts, i.e., it works, but does not produce best quality on better  
 printers)), or say  
   
 make gforth.dvi  
   
 and print the resulting file gforth.dvi. You can also get the  
 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                  Preloading installation-specific code
   
Line 124  normal Forth code and save the image, yo Line 142  normal Forth code and save the image, yo
 image. Producing a relocatable image is more difficult.  image. Producing a relocatable image is more difficult.
   
 Therefore, Gforth has only a relocatable image of the kernel  Therefore, Gforth has only a relocatable image of the kernel
 (kernal.fi), which is powerful enough to load the rest of  (kernel.fi), which is powerful enough to load the rest of
 Gforth. However, loading the rest takes a noticable amount of time. To  Gforth. However, loading the rest takes a noticable amount of time. To
 avoid this delay (which would occur on every startup), the  avoid this delay (which would occur on every startup), the
 installation procedure produces an image fixed at an address  installation procedure produces an image fixed at an address
Line 145  images on your OS. In this case, send us Line 163  images on your OS. In this case, send us
 searching for a comfortable solution to this problem. In the  searching for a comfortable solution to this problem. In the
 meantime, start gforth with  meantime, start gforth with
   
 gforth -i kernal.fi startup.fs  gforth -i kernel.fi startup.fs
   
   
 2) "%s: Checksum of image ($13579b) does not match the executable ($2468a)  2) "%s: Checksum of image ($13579b) does not match the executable ($2468a)
Line 162  trying to run an image produced for a di Line 180  trying to run an image produced for a di
 indirect threaded system.  indirect threaded system.
   
 Chances are that you unintentionally tried to execute an image from  Chances are that you unintentionally tried to execute an image from
 the wrong directory. As a remedy, you can determine Gforth's search  the wrong directory. As a remedy, you can specify Gforth's search
 path with the "-p" command line option and with the GFORTHPATH  path with the "-p" command line option and with the GFORTHPATH
 environment variable.  environment variable.
   

Removed from v.1.19  
changed lines
  Added in v.1.21


FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>