From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Wed, 15 Jan 2003 04:48:23 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 14 ************************************************** Tuesday 14 January 2003 Number 14 ************************************************** Subjects for today 1 Building NCURSES apps : John Poltorak 2 Unloading EMXLOAD : John Poltorak 3 Re: Building NCURSES apps : Thomas Dickey 4 Re: Building NCURSES apps : Thomas Dickey 5 Re: Unloading EMXLOAD : Illya Vaes 6 Re: Building NCURSES apps : John Poltorak **= Email 1 ==========================** Date: Wed, 15 Jan 2003 10:03:59 +0000 From: John Poltorak Subject: Building NCURSES apps I've tried building several apps which require NCURSES headers and have found that they only build when those headers are found in /usr/include, but not in /usr/include/ncurses which is the default location for NCURSES. Looking at CONFIG.LOG for DIALOG, I see:- In file included from configure:4429: c:\usr\include\ncurses/curses.h:58: ncurses_dll.h: No such file or directory In file included from configure:4429: c:\usr\include\ncurses/curses.h:102: unctrl.h: No such file or directory configure: failed program was: The problem seems to be due to the use of different directory seperators. Have I forgotten to do something, and is there anything which I can do to get round this problem? -- John **= Email 2 ==========================** Date: Wed, 15 Jan 2003 14:17:18 +0000 From: John Poltorak Subject: Unloading EMXLOAD Is there any to unload EMXLOAD? Apart from killing the process... -- John **= Email 3 ==========================** Date: Wed, 15 Jan 2003 16:53:37 -0500 From: Thomas Dickey Subject: Re: Building NCURSES apps On Wed, Jan 15, 2003 at 10:03:59AM +0000, John Poltorak wrote: > > > I've tried building several apps which require NCURSES headers and have > found that they only build when those headers are found in /usr/include, > but not in /usr/include/ncurses which is the default location for NCURSES. > > Looking at CONFIG.LOG for DIALOG, I see:- > > In file included from configure:4429: > c:\usr\include\ncurses/curses.h:58: ncurses_dll.h: No such file or directory > In file included from configure:4429: > c:\usr\include\ncurses/curses.h:102: unctrl.h: No such file or directory > configure: failed program was: are $CFLAGS or $CPPFLAGS set in your environment? They might be the origin of the back-slashes. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 4 ==========================** Date: Wed, 15 Jan 2003 17:46:08 -0500 From: Thomas Dickey Subject: Re: Building NCURSES apps On Wed, Jan 15, 2003 at 09:56:03PM +0000, John Poltorak wrote: > On Wed, Jan 15, 2003 at 04:53:37PM -0500, Thomas Dickey wrote: > > On Wed, Jan 15, 2003 at 10:03:59AM +0000, John Poltorak wrote: > > > > > > > > > I've tried building several apps which require NCURSES headers and have > > > found that they only build when those headers are found in /usr/include, > > > but not in /usr/include/ncurses which is the default location for NCURSES. > > > > > > Looking at CONFIG.LOG for DIALOG, I see:- > > > > > > In file included from configure:4429: > > > c:\usr\include\ncurses/curses.h:58: ncurses_dll.h: No such file or directory > > > In file included from configure:4429: > > > c:\usr\include\ncurses/curses.h:102: unctrl.h: No such file or directory > > > configure: failed program was: > > > > are $CFLAGS or $CPPFLAGS set in your environment? > > They might be the origin of the back-slashes. > > If they are, they have crept in somewhere without my knowledge. > > Should I display the environment at some point to make sure? If so, where > should that be? did you do configure --with-ncurses If not, it doesn't look for ncurses-specific features, but only for generic curses stuff. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 5 ==========================** Date: Wed, 15 Jan 2003 20:11:31 CET From: Illya Vaes Subject: Re: Unloading EMXLOAD ** Reply to note from John Poltorak Wed, 15 Jan 2003 14:17:18 +0000 >Is there any to unload EMXLOAD? Apart from killing the process... RTFM ;-) The emx 0.9d Application Developer's Guide says: emxload -q to stop the emxload server process and don't wait for the server to unload all preloaded programs and emxload -qw to do the same but wait until the server is stopped. -- Illya Vaes (illya at vaeshiep.demon.nl) "Do...or do not, there is no 'try'" - Yoda **= Email 6 ==========================** Date: Wed, 15 Jan 2003 21:56:03 +0000 From: John Poltorak Subject: Re: Building NCURSES apps On Wed, Jan 15, 2003 at 04:53:37PM -0500, Thomas Dickey wrote: > On Wed, Jan 15, 2003 at 10:03:59AM +0000, John Poltorak wrote: > > > > > > I've tried building several apps which require NCURSES headers and have > > found that they only build when those headers are found in /usr/include, > > but not in /usr/include/ncurses which is the default location for NCURSES. > > > > Looking at CONFIG.LOG for DIALOG, I see:- > > > > In file included from configure:4429: > > c:\usr\include\ncurses/curses.h:58: ncurses_dll.h: No such file or directory > > In file included from configure:4429: > > c:\usr\include\ncurses/curses.h:102: unctrl.h: No such file or directory > > configure: failed program was: > > are $CFLAGS or $CPPFLAGS set in your environment? > They might be the origin of the back-slashes. If they are, they have crept in somewhere without my knowledge. Should I display the environment at some point to make sure? If so, where should that be? > -- > Thomas E. Dickey > http://invisible-island.net > ftp://invisible-island.net -- John