1: You need DJ Delorie's port of GCC to DOS (DJGPP 2.0) to compile
2: Gforth. DJGPP provides a DPMI client that allows to use the 32-bit
3: features of the 80386, but on the other hand it requires at least a
4: 386. A DPMI host is also part of the DJGPP 2.0 package, this is
5: required if you don't have a DPMI host yourself (Windows/OS/2/Linux
6: DOS-box, Quemm or others).
8: Gforth hasn't been tested with EMX, using EMX will require some changes in
9: the console IO part. If you don't want to install the DJGPP package (quite
10: large), look for a binary distribution of Gforth for DOS. You must have a
11: version of GNU make, because DOS make programs are likely to have problems
12: with the Makefile. If you want to change Gforth, you may need GNU m4, too.
14: If you don't bother and want to make it yourself, type
18: configure has the following useful parameters:
19: --enable-force-reg Use explicit register declarations if they appear in
20: the machine.h file. This can cause a good speedup,
21: but also incorrect code with some gcc versions on
22: some processors (default disabled).
23: --enable-direct-threaded Force direct threading. This may not work on
24: some machines and may cause slowdown on others.
25: (default processor-dependent)
26: --enable-indirect-threaded Force indirect threading. This can cause a
27: slowdown on some machines.
28: (default processor-dependent)
30: After covering all inconveniences, type
34: Now you can check whether your shiny new Forth system works. Say
36: make test
38: You can run some benchmarks with
40: make bench
42: and compare them with the results in Benchres and in the manual.
44: Don't try to do "make install", it won't work, either. It is not possible to
45: "make dist" or "make bindist", too, because of the limitations of DOS
46: command lines.
48: Add the following entry to your Autoexec.bat:
50: SET GFORTHPATH=<your gforth source directory>:.
52: Use / instead of \ in your gforth source directory. Another problem
53: is, that Gforth uses : as path separator, and DOS pathes may look like
54: D:/gforth. Sorry, there is no workaround for this now.
56: For paper documentation, print gforth.ps (a Postscript file (300dpi
57: fonts, i.e., it works, but does not produce best quality on better
58: printers)), or say
60: make gforth.dvi
62: and print the resulting file gforth.dvi (you need TeX for that! But
63: with TeX you can print it even if you don't have a Postscript printer
64: nor Ghostscript). You could be able to make a html version of the
65: document, but AFAIK there is no texi2html for DOS available, as there
66: is no perl available.