[BACK]Return to INSTALL.DOS CVS log [TXT] [DIR] Up to [gforth] / gforth

Diff for /gforth/INSTALL.DOS between versions 1.1 and 1.3

version 1.1, 1995/12/11 13:15:18 version 1.3, 1996/10/06 22:24:13
Line 1 Line 1
 You need DJ Delorie's port of GCC to DOS (DJGPP) to compile Gforth. DJGPP  You need DJ Delorie's port of GCC to DOS (DJGPP 2.0) to compile
 provides a DOS extender (GO32) that allows to use the 32-bit features of  Gforth. DJGPP provides a DPMI client that allows to use the 32-bit
 the 80386, but on the other hand it requires at least an 386.  features of the 80386, but on the other hand it requires at least a
   386. A DPMI host is also part of the DJGPP 2.0 package, this is
   required if you don't have a DPMI host yourself (Windows/OS/2/Linux
   DOS-box, Quemm or others).
   
 Gforth hasn't been tested with EMX, using EMX will require some changes in  Gforth hasn't been tested with EMX, using EMX will require some changes in
 the console IO part. If you don't want to install this package (quite  the console IO part. If you don't want to install the DJGPP package (quite
 large), look for a binary distribution of Gforth for DOS. You must have a  large), look for a binary distribution of Gforth for DOS. You must have a
 version of GNU make, because DOS make programs are likely to have problems  version of GNU make, because DOS make programs are likely to have problems
 with the Makefile. If you want to change Gforth, you may need GNU m4, too.  with the Makefile. If you want to change Gforth, you may need GNU m4, too.
Line 12  If you don't bother and want to make it Line 15  If you don't bother and want to make it
   
 configure  configure
   
 There are no options for configure, because DOS can't execute a real  configure has the following useful parameters:
 configure script, all the configuring stuff is done on a real operating    --enable-force-reg      Use explicit register declarations if they appear in
 system. If you want to change something (e.g. use FORCE_REG or                            the machine.h file. This can cause a good speedup,
 DIRECT_THREADED), you have to change the makefile yourself. Be careful! DOS                            but also incorrect code with some gcc versions on
 command line arguments are limited to an overall size of 126 bytes, so                            some processors (default disabled).
 adding a new define in the makefile will make it too long. In this case add    --enable-direct-threaded      Force direct threading. This may not work on
 the define at the beginning of machine.h instead, or create a file                                  some machines and may cause slowdown on others.
 containing all extra options, and add @<filename> to the defines (move the                                  (default processor-dependent)
 -DDEFAULTPATH-define into this file, and it will fit into the command line).    --enable-indirect-threaded    Force indirect threading. This can cause a
                                   slowdown on some machines.
                                   (default processor-dependent)
   
 After covering all inconveniences, type  After covering all inconveniences, type
   
 make gforth  
   
 and after this finishes, type  
   
 make  make
   
 We apologize for the inconveniences, we did not invent the 640k limit  
 that prevents doing make straight forward. You may run out of memory  
 anyway, because GCC eats up lots of it while compiling engine.c. Keep  
 enough space free on your harddisk to allow GCC to swap.  
   
 If you want to add some defines like -DFORCE_REG, type  
   
 make gforth XDEFINES=-DFORCE_REG  
   
 instead.  
   
 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
Line 57  command lines. Line 47  command lines.
   
 Add the following entry to your Autoexec.bat:  Add the following entry to your Autoexec.bat:
   
 SET GFORTHPATH=<your gforth source directory>:.  SET GFORTHPATH=<your gforth source directory>;.
   
 Use / instead of \ in your gforth source directory.  Another problem  Use / instead of \ in your gforth source directory. Gforth now uses
 is, that Gforth uses : as path separator, and DOS pathes may look like  ';' as path separator, so you won't have problems DOS pathes that may
 D:/gforth.  Sorry, there is no workaround for this now.  contain ':', which is the default path separator in Unix.
   
 For paper documentation, print gforth.ps (a Postscript file (300dpi  For paper documentation, print gforth.ps (a Postscript file (300dpi
 fonts, i.e., it works, but does not produce best quality on better  fonts, i.e., it works, but does not produce best quality on better
Removed from v.1.1  
changed lines
  Added in v.1.3

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>