version 1.23, 1996/10/31 17:41:15
|
version 1.27, 1997/03/20 14:39:48
|
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 134 keep the old version for some time after
|
Line 154 keep the old version for some time after
|
You can deinstall this version of Gforth with 'make uninstall' and |
You can deinstall this version of Gforth with 'make uninstall' and |
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 |
|
|
|
You need to read this only if you see a message like |
|
|
|
... |
|
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" |
|
|
|
Gforth supports both relocatable and fixed-address images. If you load |
|
normal Forth code and save the image, you get a fixed-address |
|
image. Producing a relocatable image is more difficult. |
|
|
|
Therefore, Gforth has only a relocatable image of the kernel |
|
(kernel.fi), which is powerful enough to load the rest of |
|
Gforth. However, loading the rest takes a noticable amount of time. To |
|
avoid this delay (which would occur on every startup), the |
|
installation procedure produces an image fixed at an address |
|
determined at the Gforth run that produced the image. This |
|
fixed-address image is loaded by default. On most OSs this works, |
|
because the first chunk of memory is always allocated at the same |
|
address. If the address changes, you get the message above. |
|
|
|
An image address change can be caused by a change of the gforth |
|
executable, or by a change (upgrade) of the OS; in these cases you |
|
just have to rebuild and reinstall the fixed address image with |
|
|
|
rm gforth.fi; make gforth.fi; make install |
|
|
|
If you get such a message with a different address in place of the |
|
$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 |
|
searching for a comfortable solution to this problem. In the |
|
meantime, start gforth with |
|
|
|
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. |
|
|
|
|
|