version 1.9, 1995/06/07 10:05:01
|
version 1.10, 1995/10/11 19:39:31
|
Line 58 make install
|
Line 58 make install
|
|
|
You have to make an entry in the info directory file manually. Also, |
You have to make an entry in the info directory file manually. Also, |
you have to install gforth.ps and html yourself. |
you have to install gforth.ps and html yourself. |
|
|
|
|
|
A possible problem: |
|
|
|
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" |
|
|
|
Gforth supports 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. |
|
|
|
Consequently, Gforth has only a relocatable image of the kernel |
|
(kernal.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 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 |
|
0x5678 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 kernal.fi startup.fs |
|
|