--- gforth/INSTALL 1997/03/20 14:39:48 1.27 +++ gforth/INSTALL 2003/01/22 18:05:19 1.32 @@ -12,7 +12,7 @@ make Now you can check whether your shiny new Forth system works. Say -make test +make check You can run some benchmarks with @@ -24,7 +24,8 @@ If everything is all right, you may want make install -You have to make an entry in the info directory file manually. +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 @@ -37,8 +38,16 @@ 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). +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 @@ -62,16 +71,6 @@ configure has the following useful param the machine.h file. This can cause a good speedup, but also incorrect code with some gcc versions on 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. The file Benchres shows which combination of the -enable options we @@ -110,37 +109,71 @@ that it does not use "long long": 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 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; 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 + +make check +make bench + +or equivalent. Finally, perform + +make install + +or the equivalent commands on the target. + 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 +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/site-init.fs (for +/usr/local/lib/gforth/site-forth/siteinit.fs (for 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 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 +/usr/local/share/gforth/site-forth/siteinit.fs if there is no such 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 install" starting with "rm gforth.fi" is sufficient). @@ -154,3 +187,28 @@ keep the old version for some time after 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. + + + 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). +