File:  [gforth] / gforth / INSTALL
Revision 1.17: download - view: text, annotated - select for diffs
Fri Dec 15 01:54:07 1995 UTC (23 years, 9 months ago) by anton
Branches: MAIN
CVS tags: gforth-0_1beta, HEAD
fixed many small things in Makefile.in and configure.in.
Direct threading is now the default on Alphas.

    1: You need gcc version 2.0 or later to compile gforth.
    2: 
    3: First, type
    4: 
    5: ./configure
    6: 
    7: configure has the following useful parameters:
    8:   --prefix=PREFIX         install architecture-independent files in PREFIX
    9:                           [default: /usr/local]
   10:   --exec-prefix=PREFIX    install architecture-dependent files in PREFIX
   11:                           [default: same as prefix]
   12:   --enable-force-reg      Use explicit register declarations if they appear in
   13:                           the machine.h file. This can cause a good speedup,
   14:                           but also incorrect code with some gcc versions on
   15:                           some processors (default disabled).
   16:   --enable-direct-threaded      Force direct threading. This may not work on
   17:                                 some machines and may cause slowdown on others.
   18:                                 (default processor-dependent)
   19:   --enable-indirect-threaded    Force indirect threading. This can cause a
   20:                                 slowdown on some machines.
   21:                                 (default processor-dependent)
   22:   --with-debug     specifies option -g to compile with debug info (default)
   23:    --without-debug  omits the -g switch and creates smaller images on
   24:                     machines where strip has problems with gcc style
   25:                     debugging informations.
   26:   --help: tells you about other parameters.
   27: 
   28: If you don't like the defaults for the installation directories, you
   29: should override them already during configure.  E.g., if you want to
   30: install in the /gnu hierarchy instead of in the default /usr/local
   31: hierarchy, say
   32: 
   33: ./configure --prefix=/gnu
   34: 
   35: Moreover, if your GCC is not called gcc (but, e.g., gcc-2.7.1), you
   36: should say so during configuration. E.g.:
   37: 
   38: env CC=gcc-2.7.1 ./configure
   39: 
   40: You can also pass additional options to gcc in this way, e.g., if you
   41: want to generate an a.out executable under Linux with gcc-2.7.0:
   42: 
   43: env "CC=gcc -b i486-linuxaout -V 2.7.0" ./configure
   44: 
   45: After, configuration, type
   46: 
   47: make
   48: 
   49: Now you can check whether your shiny new Forth system works. Say
   50: 
   51: make test
   52: 
   53: You can run some benchmarks with
   54: 
   55: make bench
   56: 
   57: and compare them with the results in Benchres and in the manual.
   58: 
   59: If everything is all right, you may want to install gforth. Type
   60: 
   61: make install
   62: 
   63: You have to make an entry in the info directory file manually.
   64: 
   65: For paper documentation, print gforth.ps (a Postscript file (300dpi
   66: fonts, i.e., it works, but does not produce best quality on better
   67: printers)), or say
   68: 
   69: make gforth.dvi
   70: 
   71: and print the resulting file gforth.dvi. You can also get the
   72: documentation in HTML format by typing
   73: 
   74: make html
   75: 
   76: 
   77: 		Preloading installation-specific code
   78: 
   79: If you want to have some installation-specific files loaded when
   80: Gforth starts (e.g., an assembler for your processor), put commands
   81: for loading them into /usr/local/share/gforth/site-forth/site-init.fs
   82: (if the commands work for all architectures) or
   83: /usr/local/lib/gforth/site-forth/site-init.fs (for
   84: architecture-specific commands);
   85: /usr/local/lib/gforth/site-forth/site-init.fs takes precedence if both
   86: files are present (unless you change the search path). The file names
   87: given above are the defaults; if you have changed the prefix, you have
   88: to replace "/usr/local" in these names with your prefix.
   89: 
   90: By default, the installation procedure creates an empty
   91: /usr/local/share/gforth/site-forth/site-init.fs if there is no such
   92: file.
   93: 
   94: If you change the site-init.fs file, you should run "make install"
   95: again for the changes to take effect (Actually, the part of "make
   96: install" starting with "rm gforth.fi" is sufficient).
   97: 
   98: 
   99: 		Multiple Versions and Deinstallation
  100: 
  101: Several versions of Gforth can be installed and used at the same
  102: time. Version `foo' can be invoked with `gforth-foo'. We recommend to
  103: keep the old version for some time after a new one has been installed.
  104: 
  105: You can deinstall this version of Gforth with 'make uninstall' and
  106: version foo with 'make uninstall VERSION=foo'. 'make uninstall' also
  107: tells you how to uninstall Gforth completely.
  108: 
  109: 
  110: 			A Possible Problem
  111: 
  112: You need to read this only if you see a message like
  113: 
  114: "gforth: Cannot load nonrelocatable image (compiled for address 0x1234) at address 0x5678
  115: The Gforth installer should look into the INSTALL file"
  116: 
  117: Gforth supports both relocatable and fixed-address images. If you load
  118: normal Forth code and save the image, you get a fixed-address
  119: image. Producing a relocatable image is more difficult.
  120: 
  121: Therefore, Gforth has only a relocatable image of the kernel
  122: (kernal.fi), which is powerful enough to load the rest of
  123: Gforth. However, loading the rest takes a noticable amount of time. To
  124: avoid this delay (which would occur on every startup), the
  125: installation procedure produces an image fixed at an address
  126: determined at the Gforth run that produced the image. This
  127: fixed-address image is loaded by default. On most OSs this works,
  128: because the first chunk of memory is always allocated at the same
  129: address. If the address changes, you get the message above.
  130: 
  131: An image address change can be caused by a change of the gforth
  132: executable, or by a change (upgrade) of the OS; in these cases you
  133: just have to rebuild and reinstall the fixed address image with
  134: 
  135: rm gforth.fi; make gforth.fi; make install
  136: 
  137: If you get such a message with a different address in place of the
  138: 0x5678 each time you try to start gforth, you cannot use fixed-address
  139: images on your OS. In this case, send us a message so that we start
  140: searching for a comfortable solution to this problem. In the
  141: meantime, start gforth with
  142: 
  143: gforth -i kernal.fi startup.fs
  144: 

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