1------------------------------------------------------------------------------- 2-- Copyright 2020 Thomas E. Dickey -- 3-- Copyright 1998-2006,2018 Free Software Foundation, Inc. -- 4-- -- 5-- Permission is hereby granted, free of charge, to any person obtaining a -- 6-- copy of this software and associated documentation files (the -- 7-- "Software"), to deal in the Software without restriction, including -- 8-- without limitation the rights to use, copy, modify, merge, publish, -- 9-- distribute, distribute with modifications, sublicense, and/or sell copies -- 10-- of the Software, and to permit persons to whom the Software is furnished -- 11-- to do so, subject to the following conditions: -- 12-- -- 13-- The above copyright notice and this permission notice shall be included -- 14-- in all copies or substantial portions of the Software. -- 15-- -- 16-- THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS -- 17-- OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF -- 18-- MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN -- 19-- NO EVENT SHALL THE ABOVE COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, -- 20-- DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR -- 21-- OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE -- 22-- USE OR OTHER DEALINGS IN THE SOFTWARE. -- 23-- -- 24-- Except as contained in this notice, the name(s) of the above copyright -- 25-- holders shall not be used in advertising or otherwise to promote the -- 26-- sale, use or other dealings in this Software without prior written -- 27-- authorization. -- 28------------------------------------------------------------------------------- 29-- $Id: README.emx,v 1.11 2020/02/02 23:34:34 tom Exp $ 30-- Author: Thomas Dickey 31------------------------------------------------------------------------------- 32 33You can build ncurses on OS/2 in the EMX environment. But you must build and 34acquire tools. Not all of the tools distributed with EMX work properly, and 35some additional ones are required. 36 37First, the configure script distributed with ncurses will not run as-is in EMX. 38You can generate a new one if you have autoconf built for EMX. You will need 39the EMX development tools, of course. Get these programs to start: 40 41 GNU m4 program (version 1.4) 42 GNU autoconf (version 2.13). 43 GNU patch (version 2.5) 44 45Apply the autoconf patches from 46 47 https://invisible-island.net/autoconf 48 ftp://ftp.invisible-island.net/autoconf 49 50These are ordered by date: 51 52 autoconf-2.13-20030927.patch.gz 53 autoconf-2.13-20030927-emx.patch.gz 54 55I built my development environment for ncurses using EMX 0.9c at the end of 561997. Much of the EMX patch for autoconf was done originally by J.J.G.Ripoll, 57using a similar environment (he prefers using the 'ash' shell). Newer versions 58may fix these problems: 59 60 + The pdksh program distributed at Hobbes and Leo (with a 1996 date) is 61 defective. It does not process "here documents" correctly (which 62 renders it useless for running the autoconf script). I built my own 63 copy of pdksh 5.2.13, which does have the bug corrected (documented 64 in the change log for pdksh). 65 66 + I also built from sources (because the distributed binaries did not 67 work) the cmp, diff programs. 68 69 Other required utilities such as ar, cat, chmod, cp, gawk, grep, mv, 70 ls, rm, mkdir, sed, sort and tr worked. 71 72Once you have autoconf patched and installed, run 'autoconf' from the top-level 73directory of ncurses to generate the EMX-specific configure script. 74