| |
|
| ./configure |
./configure |
| |
|
| |
or |
| |
|
| |
CC=<whatever you call your gcc> ./configure |
| |
|
| |
if your local gcc installation uses a different name (e.g. gcc-2.7.2), |
| |
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 |
| |
which you may give your friends who don't have ELF libraries). |
| |
|
| 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] |
| 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 |
| |
|
| |
|
| If your make has trouble with the Makefile, "make gforth" might work. |
If your make has trouble with the Makefile, "make gforth" might work. |
| |
|
| If your installed gcc isn't called "gcc" (e.g., called "gcc-2.6.1"), type |
If your installed gcc isn't called "gcc" (e.g., called "gcc-2.7.2"), type |
| |
|
| make GCC=<whatever you call your gcc> |
make GCC=<whatever you call your gcc> |
| |
|
| instead. |
instead. The more appropriate place to select your compiler is when |
| |
running configure. |
| |
|
| 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 test |
| |
|
| To make the documentation, type |
You can run some benchmarks with |
| |
|
| make -k gforth.info gforth.ps html |
make bench |
| |
|
| |
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 allright, you may want to install gforth. Type |
| |
|
| make install |
make install |
| |
|
| You have to make an entry in the info directory file manually. Also, |
You have to make an entry in the info directory file manually. |
| you have to install gforth.ps and html yourself. |
|
| |
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 |
| |
|
| |
Multiple Versions and Deinstallation |
| |
|
| |
Several versions of Gforth can be installed and used at the same |
| |
time. Version `foo' can be invoked with `gforth-foo'. We recommend to |
| |
keep the old version for some time after a new one has been installed. |
| |
|
| |
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. |
| |
|
| 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 |
| |
|
