version 1.10, 1995/10/11 19:39:31
|
version 1.13, 1995/11/24 18:05:31
|
Line 48 Now you can check whether your shiny new
|
Line 48 Now you can check whether your shiny new
|
|
|
make test |
make test |
|
|
To make the documentation, type |
You can run some benchmarks with |
|
|
make -k gforth.info gforth.ps html |
make bench |
|
|
If everything is allright, you may want to install gforth. Type |
and compare them with the results in Benchres and in the manual. |
|
|
|
If everything is all right, you may want to install gforth. Type |
|
|
make install |
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. |
you have to install gforth.ps and html yourself. |
|
|
For paper documentation, print gforth.ps (a Postscript file (300dpi |
|
fonts, i.e., it works, but does not produce best quality on better |
|
printers)), or say |
|
|
|
make gforth.dvi |
|
|
|
and print the resulting file gforth.dvi. You can also get the |
|
documentation in HTML format by typing |
|
|
|
make html |
|
|
|
|
|
Preloading installation-specific code |
|
|
|
If you want to have some installation-specific files loaded when |
|
Gforth starts (e.g., an assembler for your processor), put commands |
|
for loading them into /usr/local/share/gforth/site-forth/site-init.fs |
|
(if the commands work for all architectures) or |
|
/usr/local/lib/gforth/site-forth/site-init.fs (for |
|
architecture-specific commands); |
|
/usr/local/lib/gforth/site-forth/site-init.fs takes precedence if both |
|
files are present (unless you change the search path). The file names |
|
given above are the defaults; if you have changed the prefix, you have |
|
to replace "/usr/local" in these names with your prefix. |
|
|
|
By default, the installation procedure creates an empty |
|
/usr/local/share/gforth/site-forth/site-init.fs if there is no such |
|
file. |
|
|
|
If you change the site-init.fs file, you should run "make install" |
|
again for the changes to take effect (Actually, the part of "make |
|
install" starting with "rm gforth.fi" is sufficient). |
|
|
|
|
|
Multiple Versions and Deinstallation |
|
|
|
Several versions of Gforth can be installed and used at the same |
|
time. Version `foo' can be invoked with `gforth-foo'. We recommend to |
|
keep the old version for some time after a new one has been installed. |
|
|
|
You can deinstall this version of Gforth with 'make uninstall' and |
|
version foo with 'make uninstall VERSION=foo'. 'make uninstall' also |
|
tells you how to uninstall Gforth completely. |
|
|
|
|
A possible problem: |
A Possible Problem |
|
|
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 |
"gforth: Cannot load nonrelocatable image (compiled for address 0x1234) at address 0x5678 |
The Gforth installer should look into the INSTALL file" |
The Gforth installer should look into the INSTALL file" |
|
|
Gforth supports relocatable and fixed-address images. If you load |
Gforth supports both relocatable and fixed-address images. If you load |
normal Forth code and save the image, you get a fixed-address |
normal Forth code and save the image, you get a fixed-address |
image. Producing a relocatable image is more difficult. |
image. Producing a relocatable image is more difficult. |
|
|
Consequently, 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 |
(kernal.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 on every startup,the installation procedure produces |
avoid this delay (which would occur on every startup), the |
an image fixed at an address determined at the Gforth run that |
installation procedure produces an image fixed at an address |
produced the image. This fixed-address image is loaded by default. On |
determined at the Gforth run that produced the image. This |
most OSs this works, because the first chunk of memory is always |
fixed-address image is loaded by default. On most OSs this works, |
allocated at the same address. If the address changes, you get the |
because the first chunk of memory is always allocated at the same |
message above. |
address. If the address changes, you get the message above. |
|
|
An image address change can be caused by a change of the gforth |
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 |
executable, or by a change (upgrade) of the OS; in these cases you |