README.emx revision 66963 
1-- $Id: README.emx,v 1.4 2000/09/16 19:28:28 tom Exp $
2-- Author: Thomas Dickey
3-------------------------------------------------------------------------------
4
5You can build ncurses on OS/2 in the EMX environment.  But you must build and
6acquire tools.  Not all of the tools distributed with EMX work properly, and
7some additional ones are required.
8
9First, the configure script distributed with ncurses will not run as-is in EMX. 
10You can generate a new one if you have autoconf built for EMX.  You will need
11the EMX development tools, of course.  Get these programs to start:
12
13	GNU m4 program (version 1.4)
14	GNU autoconf (version 2.13).
15	GNU patch (version 2.5)
16
17Apply the autoconf patches from
18
19	http://dickey.his.com/autoconf
20	ftp://dickey.his.com/autoconf
21
22These are ordered by date:
23
24	autoconf-2.13-20000819.patch.gz
25	autoconf-2.13-20000819-emx.patch.gz
26
27I built my development environment for ncurses using EMX 0.9c at the end of
281997.  Much of the EMX patch for autoconf was done originally by J.J.G.Ripoll,
29using a similar environment (he prefers using the 'ash' shell).  Newer versions
30may fix these problems:
31
32	+ The pdksh program distributed at Hobbes and Leo (with a 1996 date) is
33	  defective.  It does not process "here documents" correctly (which
34	  renders it useless for running the autoconf script).  I built my own
35	  copy of pdksh 5.2.13, which does have the bug corrected (documented
36	  in the change log for pdksh).
37
38	+ I also built from sources (because the distributed binaries did not
39	  work) the cmp, diff programs.
40	  
41	  Other required utilities such as ar, cat, chmod, cp, gawk, grep, mv,
42	  ls, rm, mkdir, sed, sort and tr worked.
43
44Once you have autoconf patched and installed, run 'autoconf' from the top-level
45directory of ncurses to generate the EMX-specific configure script.
46