version 1.15, 1995/11/29 20:20:32
|
version 1.20, 1996/09/23 20:41:58
|
Line 33 hierarchy, say
|
Line 33 hierarchy, say
|
./configure --prefix=/gnu |
./configure --prefix=/gnu |
|
|
Moreover, if your GCC is not called gcc (but, e.g., gcc-2.7.1), you |
Moreover, if your GCC is not called gcc (but, e.g., gcc-2.7.1), you |
should say so during configuration: |
should say so during configuration. E.g.: |
|
|
env GCC=gcc-2.7.1 ./configure |
env CC=gcc-2.7.1 ./configure |
|
|
|
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: |
|
|
|
env "CC=gcc -b i486-linuxaout -V 2.7.0" ./configure |
|
|
After, configuration, type |
After, configuration, type |
|
|
Line 68 documentation in HTML format by typing
|
Line 73 documentation in HTML format by typing
|
|
|
make html |
make html |
|
|
|
If you prefer plain ASCII documentation, just concatenate the files |
|
gforth.info-* ('cat gforth.info-*' under Unix). |
|
|
Preloading installation-specific code |
Preloading installation-specific code |
|
|
Line 106 tells you how to uninstall Gforth comple
|
Line 113 tells you how to uninstall Gforth comple
|
|
|
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 114 normal Forth code and save the image, yo
|
Line 124 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 130 just have to rebuild and reinstall the f
|
Line 140 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 determine 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. |
|
|
|
|