| |
|
| ./configure |
./configure |
| |
|
| |
(see Section Configuration Options below for details). |
| |
|
| |
After configuration, type |
| |
|
| |
make |
| |
|
| |
Now you can check whether your shiny new Forth system works. Say |
| |
|
| |
make test |
| |
|
| |
You can run some benchmarks with |
| |
|
| |
make bench |
| |
|
| |
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 |
| |
|
| |
You have to make an entry in the info directory file manually. |
| |
|
| |
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 |
| |
|
| |
If you prefer plain ASCII documentation, just concatenate the files |
| |
gforth.info-* ('cat gforth.info-*' under Unix). |
| |
|
| |
|
| |
Configuration Options |
| |
|
| |
You can build in a directory different from the source directory by |
| |
changing to the build directory and invoking configure thus: |
| |
|
| |
$srcdir/configure |
| |
|
| |
where $srcdir is the source directory. You need a VPATH-capable 'make' |
| |
(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 |
| |
should probably build in the source directory). |
| |
|
| configure has the following useful parameters: |
configure has the following useful parameters: |
| --prefix=PREFIX install architecture-independent files in PREFIX |
--prefix=PREFIX install architecture-independent files in PREFIX |
| [default: /usr/local] |
[default: /usr/local] |
| debugging informations. |
debugging informations. |
| --help: tells you about other parameters. |
--help: tells you about other parameters. |
| |
|
| |
The file Benchres shows which combination of the -enable options we |
| |
tried gave the best results for various machines. |
| |
|
| If you don't like the defaults for the installation directories, you |
If you don't like the defaults for the installation directories, you |
| should override them already during configure. E.g., if you want to |
should override them already during configure. E.g., if you want to |
| install in the /gnu hierarchy instead of in the default /usr/local |
install in the /gnu hierarchy instead of in the default /usr/local |
| |
|
| env "CC=gcc -b i486-linuxaout -V 2.7.0" ./configure |
env "CC=gcc -b i486-linuxaout -V 2.7.0" ./configure |
| |
|
| After, configuration, type |
You can change the sizes of the various areas used in the default |
| |
image `gforth.fi' by passing the appropriate Gforth command line |
| make |
options in the FORTHSIZES environment variable: |
| |
|
| Now you can check whether your shiny new Forth system works. Say |
|
| |
|
| make test |
|
| |
|
| You can run some benchmarks with |
|
| |
|
| make bench |
|
| |
|
| 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 |
|
| |
|
| You have to make an entry in the info directory file manually. |
|
| |
|
| 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 |
env "FORTHSIZES=--dictionary-size=256k --data-stack-size=16k --fp-stack-size=16k --return-stack-size=16k --locals-stack-size=16k" ./configure |
| documentation in HTML format by typing |
|
| |
|
| make html |
The line above reaffirms the default sizes. Note that the locals |
| |
stack area is also used as input buffer stack. |
| 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 |
| |
|
| |
|
| 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 |
| 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 |
| 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 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. |
| |
|
| |
|
