Annotation of gforth/INSTALL.DOS, revision 1.4
1.2 pazsan 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).
1.1 pazsan 7:
1.4 ! pazsan 8: Gforth hasn't been tested with EMX, using EMX will require some
! 9: changes in the console IO part. For OS/2 EMX supports POSIX-style tty,
! 10: so it might just compile out of the box. If you don't want to install
! 11: the DJGPP package (quite large), look for a binary distribution of
! 12: Gforth for DOS. You also must have a version of GNU make, because DOS
! 13: make programs are likely to have problems with the Makefile. If you
! 14: want to change Gforth, you may need GNU m4, too. Because DJGPP
! 15: provides use of long filenames under Windows 95, you should unpack the
! 16: gforth package with a Windows-95-aware archiver (those from DJGPP come
! 17: in mind), because otherwise gforth will not find the necessary
! 18: files. There is no such problem when using MS-DOS prior 7.x.
1.1 pazsan 19:
20: If you don't bother and want to make it yourself, type
1.2 pazsan 24: configure has the following useful parameters:
25: --enable-force-reg Use explicit register declarations if they appear in
26: the machine.h file. This can cause a good speedup,
27: but also incorrect code with some gcc versions on
28: some processors (default disabled).
29: --enable-direct-threaded Force direct threading. This may not work on
30: some machines and may cause slowdown on others.
1.4 ! pazsan 31: (default disabled)
1.2 pazsan 32: --enable-indirect-threaded Force indirect threading. This can cause a
33: slowdown on some machines.
1.4 ! pazsan 34: (default enabled)
1.1 pazsan 35:
36: After covering all inconveniences, type
40: Now you can check whether your shiny new Forth system works. Say
42: make test
44: You can run some benchmarks with
46: make bench
48: and compare them with the results in Benchres and in the manual.
50: Don't try to do "make install", it won't work, either. It is not possible to
51: "make dist" or "make bindist", too, because of the limitations of DOS
52: command lines.
54: Add the following entry to your Autoexec.bat:
1.3 pazsan 56: SET GFORTHPATH=<your gforth source directory>;.
1.1 pazsan 57:
1.3 pazsan 58: Use / instead of \ in your gforth source directory. Gforth now uses
1.4 ! pazsan 59: ';' as path separator, so you won't have problems with DOS pathes that
! 60: may contain ':', which is the default path separator in Unix.
1.1 pazsan 61:
62: For paper documentation, print gforth.ps (a Postscript file (300dpi
63: fonts, i.e., it works, but does not produce best quality on better
64: printers)), or say
66: make gforth.dvi
68: and print the resulting file gforth.dvi (you need TeX for that! But
69: with TeX you can print it even if you don't have a Postscript printer
70: nor Ghostscript). You could be able to make a html version of the
71: document, but AFAIK there is no texi2html for DOS available, as there
72: is no perl available.