Diff for /gforth/INSTALL between versions 1.12 and 1.21

version 1.12, 1995/11/13 18:37:09 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
 hirarchy, say  hierarchy, say
   
 ./configure --prefix=/gnu  ./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  
   
 If your make has trouble with the Makefile, "make gforth" might work.  env CC=gcc-2.7.1 ./configure
   
 If your installed gcc isn't called "gcc" (e.g., called "gcc-2.6.1"), type  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:
 make GCC=<whatever you call your gcc>  
   
 instead.  
   
 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 allright, you may want to install gforth. Type  env "CC=gcc -b i486-linuxaout -V 2.7.0" ./configure
   
 make install  
   
 You have to make an entry in the info directory file manually.                  Preloading installation-specific code
   
 For paper documentation, print gforth.ps (a Postscript file (300dpi  If you want to have some installation-specific files loaded when
 fonts, i.e., it works, but does not produce best quality on better  Gforth starts (e.g., an assembler for your processor), put commands
 printers)), or say  for loading them into /usr/local/share/gforth/site-forth/site-init.fs
   (if the commands work for all architectures) or
   /usr/local/lib/gforth/site-forth/site-init.fs (for
   architecture-specific commands);
   /usr/local/lib/gforth/site-forth/site-init.fs takes precedence if both
   files are present (unless you change the search path). The file names
   given above are the defaults; if you have changed the prefix, you have
   to replace "/usr/local" in these names with your prefix.
   
 make gforth.dvi  By default, the installation procedure creates an empty
   /usr/local/share/gforth/site-forth/site-init.fs if there is no such
   file.
   
 and print the resulting file gforth.dvi. You can also get the  If you change the site-init.fs file, you should run "make install"
 documentation in HTML format by typing  again for the changes to take effect (Actually, the part of "make
   install" starting with "rm gforth.fi" is sufficient).
   
 make html  
   
                 Multiple Versions and Deinstallation                  Multiple Versions and Deinstallation
   
Line 81  You can deinstall this version of Gforth Line 126  You can deinstall this version of Gforth
 version foo with 'make uninstall VERSION=foo'. 'make uninstall' also  version foo with 'make uninstall VERSION=foo'. 'make uninstall' also
 tells you how to uninstall Gforth completely.  tells you how to uninstall Gforth completely.
   
   
                         A Possible Problem                          A Possible Problem
   
 You need to read this only if you see a message like  You need to read this only if you see a message like
   
 "gforth: Cannot load nonrelocatable image (compiled for address 0x1234) at address 0x5678  ...
   The Gforth installer should look into the INSTALL file
   
   1) "gforth: Cannot load nonrelocatable image (compiled for address $1234) at address $5678
 The Gforth installer should look into the INSTALL file"  The Gforth installer should look into the INSTALL file"
   
 Gforth supports both relocatable and fixed-address images. If you load  Gforth supports both relocatable and fixed-address images. If you load
Line 93  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 109  just have to rebuild and reinstall the f Line 158  just have to rebuild and reinstall the f
 rm gforth.fi; make gforth.fi; make install  rm gforth.fi; make gforth.fi; make install
   
 If you get such a message with a different address in place of the  If you get such a message with a different address in place of the
 0x5678 each time you try to start gforth, you cannot use fixed-address  $5678 each time you try to start gforth, you cannot use fixed-address
 images on your OS. In this case, send us a message so that we start  images on your OS. In this case, send us a message so that we start
 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)
   The Gforth installer should look into the INSTALL file"
   
   A fixed-address image is not only fixed with respect to its base
   address, but also with respect to certain addresses in the gforth
   executable and the threading method. These things are encoded in a
   checksum.
   
   If the checksum of the executable and the checksum of the image are
   not equal, you get the message above. This can be caused, e.g., by
   trying to run an image produced for a direct threading system on an
   indirect threaded system.
   
   Chances are that you unintentionally tried to execute an image from
   the wrong directory. As a remedy, you can specify Gforth's search
   path with the "-p" command line option and with the GFORTHPATH
   environment variable.
   
   On the other hand, if you need to solve the problem by creating a new
   fixed-address image, you can use the steps described above.
   
   

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


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