README.emx revision 50276 
1-- $Id: README.emx,v 1.1 1998/11/21 20:13:05 tom Exp $
2-- Author: Thomas Dickey <dickey@clark.net>
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.12).
15	GNU patch (version 2.5)
16
17Apply the autoconf patches from
18
19	http://www.clark.net/pub/dickey/autoconf
20	ftp://ftp.clark.net/pub/dickey/autoconf
21
22These are ordered by date:
23
24	autoconf-2.12-970309.patch
25	autoconf-2.12-970429.patch
26	autoconf-2.12-971222-emx.patch
27	autoconf-2.12-971222.patch
28	autoconf-2.12-971230.patch
29
30I built my development environment for ncurses using EMX 0.9c at the end of
311997.  Much of the EMX patch for autoconf was done originally by J.J.G.Ripoll,
32using a similar environment (he prefers using the 'ash' shell).  Newer versions
33may fix these problems:
34
35	+ The pdksh program distributed at Hobbes and Leo (with a 1996 date) is
36	  defective.  It does not process "here documents" correctly (which
37	  renders it useless for running the autoconf script).  I built my own
38	  copy of pdksh 5.2.13, which does have the bug corrected (documented
39	  in the change log for pdksh).
40
41	+ I also built from sources (because the distributed binaries did not
42	  work) the cmp, diff programs.
43	  
44	  Other required utilities such as ar, cat, chmod, cp, gawk, grep, mv,
45	  ls, rm, mkdir, sed, sort and tr worked.
46
47Once you have autoconf patched and installed, run 'autoconf' from the top-level
48directory of ncurses to generate the EMX-specific configure script.
49