- view: text
- select for diffs
Wed Oct 11 19:39:31 1995 UTC
(25 years ago) by anton
CVS tags: HEAD
Now gforth.fi is a nonrelocatable image containing all of startup.fs etc.
savesystem now saves `included-files', too (so require does not start from
added/fixed stack effect and wordset documentation for many words in kernal.fs
some reformatting in kernal.fs
fixed some wordset info in primitives
1: You need gcc version 2.0 or later to compile gforth.
3: First, type
7: configure has the following useful parameters:
8: --prefix=PREFIX install architecture-independent files in PREFIX
9: [default: /usr/local]
10: --exec-prefix=PREFIX install architecture-dependent files in PREFIX
11: [default: same as prefix]
12: --enable-force-reg Use explicit register declarations if they appear in
13: the machine.h file. This can cause a good speedup,
14: but also incorrect code with some gcc versions on
15: some processors (default disabled).
16: --enable-direct-threaded Force direct threading. This may not work on
17: some machines and may cause slowdown on others.
18: (default processor-dependent)
19: --enable-indirect-threaded Force indirect threading. This can cause a
20: slowdown on some machines.
21: (default processor-dependent)
22: --with-debug specifies option -g to compile with debug info (default)
23: --without-debug omits the -g switch and creates smaller images on
24: machines where strip has problems with gcc style
25: debugging informations.
26: --help: tells you about other parameters.
28: If you don't like the defaults for the installation directories, you
29: should override them already during configure. E.g., if you want to
30: install in the /gnu hierarchy instead of in the default /usr/local
31: hirarchy, say
33: ./configure --prefix=/gnu
35: After, configuration, type
39: If your make has trouble with the Makefile, "make gforth" might work.
41: If your installed gcc isn't called "gcc" (e.g., called "gcc-2.6.1"), type
43: make GCC=<whatever you call your gcc>
47: Now you can check whether your shiny new Forth system works. Say
49: make test
51: To make the documentation, type
53: make -k gforth.info gforth.ps html
55: If everything is allright, you may want to install gforth. Type
57: make install
59: You have to make an entry in the info directory file manually. Also,
60: you have to install gforth.ps and html yourself.
63: A possible problem:
65: You need to read this only if you see a message like
67: "gforth: Cannot load nonrelocatable image (compiled for address 0x1234) at address 0x5678
68: The Gforth installer should look into the INSTALL file"
70: Gforth supports relocatable and fixed-address images. If you load
71: normal Forth code and save the image, you get a fixed-address
72: image. Producing a relocatable image is more difficult.
74: Consequently, Gforth has only a relocatable image of the kernel
75: (kernal.fi), which is powerful enough to load the rest of
76: Gforth. However, loading the rest takes a noticable amount of time. To
77: avoid this delay on every startup,the installation procedure produces
78: an image fixed at an address determined at the Gforth run that
79: produced the image. This fixed-address image is loaded by default. On
80: most OSs this works, because the first chunk of memory is always
81: allocated at the same address. If the address changes, you get the
82: message above.
84: An image address change can be caused by a change of the gforth
85: executable, or by a change (upgrade) of the OS; in these cases you
86: just have to rebuild and reinstall the fixed address image with
88: rm gforth.fi; make gforth.fi; make install
90: If you get such a message with a different address in place of the
91: 0x5678 each time you try to start gforth, you cannot use fixed-address
92: images on your OS. In this case, send us a message so that we start
93: searching for a comfortable solution to this problem. In the
94: meantime, start gforth with
96: gforth -i kernal.fi startup.fs