| 1 : |
pazsan
|
1.5
|
MS-DOS: |
| 2 : |
|
|
|
| 3 : |
pazsan
|
1.2
|
You need DJ Delorie's port of GCC to DOS (DJGPP 2.0) to compile |
| 4 : |
|
|
Gforth. DJGPP provides a DPMI client that allows to use the 32-bit |
| 5 : |
|
|
features of the 80386, but on the other hand it requires at least a |
| 6 : |
|
|
386. A DPMI host is also part of the DJGPP 2.0 package, this is |
| 7 : |
|
|
required if you don't have a DPMI host yourself (Windows/OS/2/Linux |
| 8 : |
|
|
DOS-box, Quemm or others). |
| 9 : |
pazsan
|
1.1
|
|
| 10 : |
pazsan
|
1.5
|
OS/2: |
| 11 : |
|
|
|
| 12 : |
|
|
You need EMX 0.9c to compile Gforth. The EMX package provides all |
| 13 : |
|
|
necessary Unix-like tools, tty and signal handling. |
| 14 : |
|
|
|
| 15 : |
|
|
If you don't want to install the DJGPP or EMX package (quite large), |
| 16 : |
|
|
look for a binary distribution of Gforth for DOS or OS/2. You also |
| 17 : |
|
|
must have a version of GNU make, because DOS/OS/2 make programs are |
| 18 : |
|
|
likely to have problems with the Makefile. If you want to change |
| 19 : |
|
|
Gforth, you may need GNU m4, too. Because DJGPP provides use of long |
| 20 : |
|
|
filenames under Windows 95, you should unpack the gforth package with |
| 21 : |
|
|
a Windows-95-aware archiver (those from DJGPP or the Cygnus |
| 22 : |
|
|
Win32-package come in mind), because otherwise gforth will not find |
| 23 : |
|
|
the necessary files. With MS-DOS versions prior 7.0 or DR-DOS, these |
| 24 : |
|
|
names are cut due to the 8.3 rule. This might confuse DJGPP 2.0's |
| 25 : |
|
|
make, you could use DJGPP 1.x's make instead. Gforth 0.2.0 hasn't been |
| 26 : |
|
|
compiled with a MS-DOS prior 7.0. |
| 27 : |
|
|
|
| 28 : |
|
|
Compiling under DOS or OS/2 has a number of quirks, and if it doesn't |
| 29 : |
|
|
compile out of the box, you should know what you do. I therefore |
| 30 : |
|
|
discourage unexperienced users to compile gforth themselfes. There's a |
| 31 : |
|
|
binary package for it anyway. |
| 32 : |
pazsan
|
1.1
|
|
| 33 : |
|
|
If you don't bother and want to make it yourself, type |
| 34 : |
|
|
|
| 35 : |
|
|
configure |
| 36 : |
|
|
|
| 37 : |
pazsan
|
1.2
|
configure has the following useful parameters: |
| 38 : |
|
|
--enable-force-reg Use explicit register declarations if they appear in |
| 39 : |
|
|
the machine.h file. This can cause a good speedup, |
| 40 : |
|
|
but also incorrect code with some gcc versions on |
| 41 : |
|
|
some processors (default disabled). |
| 42 : |
|
|
--enable-direct-threaded Force direct threading. This may not work on |
| 43 : |
|
|
some machines and may cause slowdown on others. |
| 44 : |
pazsan
|
1.4
|
(default disabled) |
| 45 : |
pazsan
|
1.2
|
--enable-indirect-threaded Force indirect threading. This can cause a |
| 46 : |
|
|
slowdown on some machines. |
| 47 : |
pazsan
|
1.4
|
(default enabled) |
| 48 : |
pazsan
|
1.1
|
|
| 49 : |
|
|
After covering all inconveniences, type |
| 50 : |
|
|
|
| 51 : |
|
|
make |
| 52 : |
|
|
|
| 53 : |
|
|
Now you can check whether your shiny new Forth system works. Say |
| 54 : |
|
|
|
| 55 : |
|
|
make test |
| 56 : |
|
|
|
| 57 : |
|
|
You can run some benchmarks with |
| 58 : |
|
|
|
| 59 : |
|
|
make bench |
| 60 : |
|
|
|
| 61 : |
|
|
and compare them with the results in Benchres and in the manual. |
| 62 : |
|
|
|
| 63 : |
|
|
Don't try to do "make install", it won't work, either. It is not possible to |
| 64 : |
|
|
"make dist" or "make bindist", too, because of the limitations of DOS |
| 65 : |
|
|
command lines. |
| 66 : |
|
|
|
| 67 : |
|
|
Add the following entry to your Autoexec.bat: |
| 68 : |
|
|
|
| 69 : |
pazsan
|
1.3
|
SET GFORTHPATH=<your gforth source directory>;. |
| 70 : |
pazsan
|
1.1
|
|
| 71 : |
pazsan
|
1.3
|
Use / instead of \ in your gforth source directory. Gforth now uses |
| 72 : |
pazsan
|
1.4
|
';' as path separator, so you won't have problems with DOS pathes that |
| 73 : |
|
|
may contain ':', which is the default path separator in Unix. |
| 74 : |
pazsan
|
1.1
|
|
| 75 : |
|
|
For paper documentation, print gforth.ps (a Postscript file (300dpi |
| 76 : |
|
|
fonts, i.e., it works, but does not produce best quality on better |
| 77 : |
|
|
printers)), or say |
| 78 : |
|
|
|
| 79 : |
|
|
make gforth.dvi |
| 80 : |
|
|
|
| 81 : |
|
|
and print the resulting file gforth.dvi (you need TeX for that! But |
| 82 : |
|
|
with TeX you can print it even if you don't have a Postscript printer |
| 83 : |
pazsan
|
1.5
|
nor Ghostscript). You could be able to make a HTML version of the |
| 84 : |
pazsan
|
1.1
|
document, but AFAIK there is no texi2html for DOS available, as there |
| 85 : |
|
|
is no perl available. |