[BACK]Return to INSTALL CVS log [TXT] [DIR] Up to [gforth] / gforth

Diff for /gforth/INSTALL between versions 1.22 and 1.26

version 1.22, 1996/10/28 17:24:30 version 1.26, 1997/02/01 14:59:27
Line 43  gforth.info-* ('cat gforth.info-*' under Line 43  gforth.info-* ('cat gforth.info-*' under
   
                 Configuration Options                  Configuration Options
   
 You can build in a directory different from the source directory by  If you use GNU make, you can build in a directory different from the
 changing to the build directory and invoking configure thus:  source directory by changing to the build directory and invoking
   configure thus:
   
 $srcdir/configure  $srcdir/configure
   
 where $srcdir is the source directory. You need a VPATH-capable 'make'  where $srcdir is the source directory. (Note that we tested this only
 (e.g., GNU make) for this. (Note that we tested this only  
 for installation; i.e., if you want to hack the Gforth sources, you  for installation; i.e., if you want to hack the Gforth sources, you
 should probably build in the source directory).  should probably build in the source directory).
   
Line 98  You can change the sizes of the various Line 98  You can change the sizes of the various
 image `gforth.fi' by passing the appropriate Gforth command line  image `gforth.fi' by passing the appropriate Gforth command line
 options in the FORTHSIZES environment variable:  options in the FORTHSIZES environment variable:
   
 env "FORTHSIZES=--dictionary-size=256k --data-stack-size=16k --fp-stack-size=16k --return-stack-size=16k --locals-stack-size=16k" ./configure  env "FORTHSIZES=--dictionary-size=256k --data-stack-size=16k --fp-stack-size=15872b --return-stack-size=15k --locals-stack-size=14848b" ./configure
   
 The line above reaffirms the default sizes. Note that the locals  The line above reaffirms the default sizes. Note that the locals
 stack area is also used as input buffer stack.  stack area is also used as input buffer stack.
   
   If C's "long long" do not work properly on your machine (i.e., if the
   tests involving double-cell numbers fail), you can build Gforth such
   that it does not use "long long":
   
   env ac_cv_sizeof_long_long=0 ./configure
   
   
                           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
   
   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.
   
   
                 Preloading installation-specific code                  Preloading installation-specific code
   
 If you want to have some installation-specific files loaded when  If you want to have some installation-specific files loaded when
Line 174  meantime, start gforth with Line 194  meantime, start gforth with
   
 gforth -i kernel.fi startup.fs  gforth -i kernel.fi startup.fs
   
   If the addresses changes by only a small amount (e.g. by one or two
   pages), you can fix it by defining FUZZ (in config.h) to a number at
   least two times the changes you observe (0x4000 is a good idea, this
   is four 4k pages) and recompile. We do this for the DJGPP port for
   DOS, because the start address there changes by one or two pages, and
   it helps us to keep the DOS people happy without investing too much
   work in a braindead environment.
   
   
 2) "%s: Checksum of image ($13579b) does not match the executable ($2468a)  2) "%s: Checksum of image ($13579b) does not match the executable ($2468a)
 The Gforth installer should look into the INSTALL file"  The Gforth installer should look into the INSTALL file"
Removed from v.1.22  
changed lines
  Added in v.1.26

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