-- $Id: README.emx,v 1.6 2002/09/07 17:03:19 tom Exp $-- Author: Thomas Dickey-------------------------------------------------------------------------------You can build ncurses on OS/2 in the EMX environment.  But you must build andacquire tools.  Not all of the tools distributed with EMX work properly, andsome additional ones are required.First, the configure script distributed with ncurses will not run as-is in EMX. You can generate a new one if you have autoconf built for EMX.  You will needthe EMX development tools, of course.  Get these programs to start:	GNU m4 program (version 1.4)	GNU autoconf (version 2.13).	GNU patch (version 2.5)Apply the autoconf patches from	http://invisible-island.net/autoconf	ftp://invisible-island.net/autoconfThese are ordered by date:	autoconf-2.13-20020210.patch.gz	autoconf-2.13-20020210-emx.patch.gzI built my development environment for ncurses using EMX 0.9c at the end of1997.  Much of the EMX patch for autoconf was done originally by J.J.G.Ripoll,using a similar environment (he prefers using the 'ash' shell).  Newer versionsmay fix these problems:	+ The pdksh program distributed at Hobbes and Leo (with a 1996 date) is	  defective.  It does not process "here documents" correctly (which	  renders it useless for running the autoconf script).  I built my own	  copy of pdksh 5.2.13, which does have the bug corrected (documented	  in the change log for pdksh).	+ I also built from sources (because the distributed binaries did not	  work) the cmp, diff programs.	  	  Other required utilities such as ar, cat, chmod, cp, gawk, grep, mv,	  ls, rm, mkdir, sed, sort and tr worked.Once you have autoconf patched and installed, run 'autoconf' from the top-leveldirectory of ncurses to generate the EMX-specific configure script.