version 1.12, 1995/11/13 18:37:09
|
version 1.18, 1996/01/07 17:22:06
|
Line 28 configure has the following useful param
|
Line 28 configure has the following useful param
|
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 |
hirarchy, say |
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.6.1"), type |
env "CC=gcc -b i486-linuxaout -V 2.7.0" ./configure |
|
|
make GCC=<whatever you call your gcc> |
After, configuration, type |
|
|
instead. |
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 |
|
|
Line 54 make bench
|
Line 56 make bench
|
|
|
and compare them with the results in Benchres and in the manual. |
and compare them with the results in Benchres and in the manual. |
|
|
If everything is allright, you may want to install gforth. Type |
If everything is all right, you may want to install gforth. Type |
|
|
make install |
make install |
|
|
Line 71 documentation in HTML format by typing
|
Line 73 documentation in HTML format by typing
|
|
|
make html |
make html |
|
|
|
If you prefer plain ASCII documentation, just concatenate the files |
|
gforth.info-* ('cat gforth.info-*' under Unix). |
|
|
|
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 |
Multiple Versions and Deinstallation |
|
|
Several versions of Gforth can be installed and used at the same |
Several versions of Gforth can be installed and used at the same |
Line 81 You can deinstall this version of Gforth
|
Line 108 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 |
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 |