version 1.16, 1995/12/11 13:15:18
|
version 1.31, 2002/03/13 16:59:12
|
Line 4 First, type
|
Line 4 First, type
|
|
|
./configure |
./configure |
|
|
or |
(see Section Configuration Options below for details). |
|
|
CC=<whatever you call your gcc> ./configure |
After configuration, type |
|
|
if your local gcc installation uses a different name (e.g. gcc-2.7.2), |
make |
or you want to generate for a different binary format (e.g. "gcc -b |
|
i486-linuxaout -V 2.7.0" to generate an a.out executable under Linux |
Now you can check whether your shiny new Forth system works. Say |
which you may give your friends who don't have ELF libraries). |
|
|
make check |
|
|
|
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 (see |
|
Installing Info Files, below). |
|
|
|
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, you can |
|
|
|
make doc/gforth.txt |
|
|
|
or just concatenate the files gforth.info-* ('cat gforth.info-*' under |
|
Unix); the result of the latter option is a little worse. |
|
|
|
You can find binary distributions, documentation in HTML and plain |
|
text format and information on known installation problems at |
|
http://www.complang.tuwien.ac.at/forth/gforth/. |
|
|
|
|
|
Configuration Options |
|
|
|
If you use GNU make, 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. (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 |
Line 29 configure has the following useful param
|
Line 78 configure has the following useful param
|
slowdown on some machines. |
slowdown on some machines. |
(default processor-dependent) |
(default processor-dependent) |
--with-debug specifies option -g to compile with debug info (default) |
--with-debug specifies option -g to compile with debug info (default) |
--without-debug omits the -g switch and creates smaller images on |
--without-debug omits the -g switch and creates smaller images on |
machines where strip has problems with gcc style |
machines where strip has problems with gcc style |
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 |
Line 41 hierarchy, say
|
Line 93 hierarchy, say
|
|
|
./configure --prefix=/gnu |
./configure --prefix=/gnu |
|
|
After, configuration, type |
Moreover, if your GCC is not called gcc (but, e.g., gcc-2.7.1), you |
|
should say so during configuration. E.g.: |
|
|
make |
env CC=gcc-2.7.1 ./configure |
|
|
If your make has trouble with the Makefile, "make gforth" might work. |
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: |
|
|
If your installed gcc isn't called "gcc" (e.g., called "gcc-2.7.2"), type |
env "CC=gcc -b i486-linuxaout -V 2.7.0" ./configure |
|
|
make GCC=<whatever you call your gcc> |
You can change the sizes of the various areas used in the default |
|
image `gforth.fi' by passing the appropriate Gforth command line |
|
options in the FORTHSIZES environment variable: |
|
|
instead. The more appropriate place to select your compiler is when |
env "FORTHSIZES=--dictionary-size=256k --data-stack-size=16k --fp-stack-size=15872b --return-stack-size=15k --locals-stack-size=14848b" ./configure |
running configure. |
|
|
|
Now you can check whether your shiny new Forth system works. Say |
The line above reaffirms the default sizes. Note that the locals |
|
stack area is also used as input buffer stack. |
|
|
make test |
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": |
|
|
You can run some benchmarks with |
env ac_cv_sizeof_long_long=0 ./configure |
|
|
make bench |
|
|
|
and compare them with the results in Benchres and in the manual. |
Cross-Installation |
|
|
|
You need a cross-compilation toolchain for your target including gcc |
|
(2.0 or later). |
|
|
|
The first step in cross-installation is the 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_char=1 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. |
|
|
|
After the cross-configuration you type |
|
|
|
make gforths |
|
|
|
This produces the gforth engines for the target. |
|
|
|
The next step is to transfer everything to the target; on the target, |
|
you do |
|
|
|
make |
|
|
|
to complete building gforth. If you do not have a make on the target, |
|
run |
|
|
|
make -n |
|
|
|
on the host; manually execute on the target the last command output by |
|
"make -n" (GFORTHD=...); the other commands output by "make -n" are |
|
not necessary unless you have changed the Gforth sources. You can |
|
then check and benchmark Gforth with |
|
|
If everything is allright, you may want to install gforth. Type |
make check |
|
make bench |
|
|
|
or equivalent. Finally, perform |
|
|
make install |
make install |
|
|
You have to make an entry in the info directory file manually. |
or the equivalent commands on the target. |
|
|
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 |
Preloading installation-specific code |
|
|
and print the resulting file gforth.dvi. You can also get the |
If you want to have some installation-specific files loaded when |
documentation in HTML format by typing |
Gforth starts (e.g., an assembler for your processor), put commands |
|
for loading them into /usr/local/share/gforth/site-forth/siteinit.fs |
|
(if the commands work for all architectures) or |
|
/usr/local/lib/gforth/site-forth/siteinit.fs (for |
|
architecture-specific commands); |
|
/usr/local/lib/gforth/site-forth/siteinit.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/siteinit.fs if there is no such |
|
file. |
|
|
|
If you change the siteinit.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). |
|
|
make html |
|
|
|
Multiple Versions and Deinstallation |
Multiple Versions and Deinstallation |
|
|
Line 91 You can deinstall this version of Gforth
|
Line 198 You can deinstall this version of Gforth
|
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 |
Installing Info Files |
|
|
|
Info is the GNU project on-line documentation format. You can read |
|
info files either from within Emacs (Ctrl-h i) or using the |
|
stand-alone Info reader, 'info'. |
|
|
|
If you use the default install root of '/usr/local' then the info |
|
files will be installed in '/usr/local/info'. |
|
|
|
Many GNU/Linux distributions are set up to put all of their |
|
documentation in '/usr/info', in which case you might have to do a |
|
couple of things to get your environment set up to accommodate files |
|
in both areas: |
|
|
"gforth: Cannot load nonrelocatable image (compiled for address 0x1234) at address 0x5678 |
1. Add an INFOPATH environment variable. The easiest place to do |
The Gforth installer should look into the INSTALL file" |
this is '/etc/profile', right next to PATH and MANPATH: |
|
|
Gforth supports both relocatable and fixed-address images. If you load |
INFOPATH=/usr/local/info:/usr/info |
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 |
|
(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 (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 |
|
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 |
2. Create a file called 'dir' in 'usr/local/info'. Use the file |
|
'/usr/info/dir' as a template. You can add the line for gforth |
|
manually, or use '/sbin/install-info' (man install-info for details). |
|
|