version 1.27, 1997/03/20 14:39:48
|
version 1.34, 2003/03/09 17:16:38
|
Line 1
|
Line 1
|
|
Copyright (C) 2003 Free Software Foundation, Inc. |
|
This file is free documentation; the Free Software Foundation gives |
|
unlimited permission to copy, distribute and modify it. |
|
|
You need gcc version 2.0 or later to compile gforth. |
You need gcc version 2.0 or later to compile gforth. |
|
|
First, type |
First, type |
Line 12 make
|
Line 16 make
|
|
|
Now you can check whether your shiny new Forth system works. Say |
Now you can check whether your shiny new Forth system works. Say |
|
|
make test |
make check |
|
|
You can run some benchmarks with |
You can run some benchmarks with |
|
|
Line 24 If everything is all right, you may want
|
Line 28 If everything is all right, you may want
|
|
|
make install |
make install |
|
|
You have to make an entry in the info directory file manually. |
|
|
|
For paper documentation, print gforth.ps (a Postscript file (300dpi |
For paper documentation, print gforth.ps (a Postscript file (300dpi |
fonts, i.e., it works, but does not produce best quality on better |
fonts, i.e., it works, but does not produce best quality on better |
printers)), or say |
printers)), or say |
Line 37 documentation in HTML format by typing
|
Line 39 documentation in HTML format by typing
|
|
|
make html |
make html |
|
|
If you prefer plain ASCII documentation, just concatenate the files |
If you prefer plain ASCII documentation, you can |
gforth.info-* ('cat gforth.info-*' under Unix). |
|
|
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 |
Configuration Options |
Line 62 configure has the following useful param
|
Line 72 configure has the following useful param
|
the machine.h file. This can cause a good speedup, |
the machine.h file. This can cause a good speedup, |
but also incorrect code with some gcc versions on |
but also incorrect code with some gcc versions on |
some processors (default disabled). |
some processors (default disabled). |
--enable-direct-threaded Force direct threading. This may not work on |
|
some machines and may cause slowdown on others. |
|
(default processor-dependent) |
|
--enable-indirect-threaded Force indirect threading. This can cause a |
|
slowdown on some machines. |
|
(default processor-dependent) |
|
--with-debug specifies option -g to compile with debug info (default) |
|
--without-debug omits the -g switch and creates smaller images on |
|
machines where strip has problems with gcc style |
|
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 |
The file Benchres shows which combination of the -enable options we |
Line 110 that it does not use "long long":
|
Line 110 that it does not use "long long":
|
env ac_cv_sizeof_long_long=0 ./configure |
env ac_cv_sizeof_long_long=0 ./configure |
|
|
|
|
Cross-Configuration |
Cross-Installation |
|
|
|
You need a cross-compilation toolchain for your target including gcc |
|
(2.0 or later). |
|
|
A few tests made by the configure script do not work in a |
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 |
cross-compilation situation. You have to provide the results of these |
tests by hand. E.g., if you compile for a 386 architecture processor: |
tests by hand. E.g., if you compile for a 386 architecture processor: |
|
|
env ac_cv_sizeof_char_p=4 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 |
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_sizeof_intptr_t=4 ac_cv_sizeof_int128_t=0 ac_cv_c_bigendian=no ./configure |
|
|
The ac_cv_sizeof_... variables give the sizes of various C types; |
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_sizeof_char_p is the same as "sizeof(char*)" in C code. The |
ac_cv_c_bigendian variable gives the byte order. |
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 |
|
|
|
make check |
|
make bench |
|
|
|
or equivalent. Finally, perform |
|
|
|
make install |
|
|
|
or the equivalent commands on the target. |
|
|
|
|
Preloading installation-specific code |
Preloading installation-specific code |
|
|
If you want to have some installation-specific files loaded when |
If you want to have some installation-specific files loaded when |
Gforth starts (e.g., an assembler for your processor), put commands |
Gforth starts (e.g., an assembler for your processor), put commands |
for loading them into /usr/local/share/gforth/site-forth/site-init.fs |
for loading them into /usr/local/share/gforth/site-forth/siteinit.fs |
(if the commands work for all architectures) or |
(if the commands work for all architectures) or |
/usr/local/lib/gforth/site-forth/site-init.fs (for |
/usr/local/lib/gforth/site-forth/siteinit.fs (for |
architecture-specific commands); |
architecture-specific commands); |
/usr/local/lib/gforth/site-forth/site-init.fs takes precedence if both |
/usr/local/lib/gforth/site-forth/siteinit.fs takes precedence if both |
files are present (unless you change the search path). The file names |
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 |
given above are the defaults; if you have changed the prefix, you have |
to replace "/usr/local" in these names with your prefix. |
to replace "/usr/local" in these names with your prefix. |
|
|
By default, the installation procedure creates an empty |
By default, the installation procedure creates an empty |
/usr/local/share/gforth/site-forth/site-init.fs if there is no such |
/usr/local/share/gforth/site-forth/siteinit.fs if there is no such |
file. |
file. |
|
|
If you change the site-init.fs file, you should run "make install" |
If you change the siteinit.fs file, you should run "make install" |
again for the changes to take effect (Actually, the part of "make |
again for the changes to take effect (Actually, the part of "make |
install" starting with "rm gforth.fi" is sufficient). |
install" starting with "rm gforth.fi" is sufficient). |
|
|
Line 154 keep the old version for some time after
|
Line 188 keep the old version for some time after
|
You can deinstall this version of Gforth with 'make uninstall' and |
You can deinstall this version of Gforth with 'make uninstall' and |
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. |
|
|
|
|
|
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: |
|
|
|
1. Add an INFOPATH environment variable. The easiest place to do |
|
this is '/etc/profile', right next to PATH and MANPATH: |
|
|
|
INFOPATH=/usr/local/info:/usr/info |
|
|
|
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). |
|
|