Date: Mon, 1 Dec 2003 14:17:26 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 257 ************************************************** Sunday 30 November 2003 Number 257 ************************************************** Subjects for today 1 Re: curses! this libncurses thing... : Lewis G Rosenthal 2 Re: curses! this libncurses thing... : Henry Sobotka 3 Re: curses! this libncurses thing... : John Poltorak 4 Re: curses! this libncurses thing... : John Poltorak 5 Python install : John Poltorak **= Email 1 ==========================** Date: Mon, 01 Dec 2003 02:11:29 -0500 From: Lewis G Rosenthal Subject: Re: curses! this libncurses thing... Hey, thanks, Henry. So, then, when I have ncurses installed (as I do), what's up with: | #define BUILD_CURSES 1 | /* end confdefs.h. */ | | /* Override any gcc2 internal prototype to avoid an error. */ | #ifdef __cplusplus | extern "C" | #endif | /* We use char because int might match the return type of a gcc2 | builtin and then its argument prototype would still apply. */ | char initscr (); | int | main () | { | initscr (); | ; | return 0; | } configure.:5088: result: no configure.:5103: error: Unable to find libncurses or libcurses From what I can tell, ncurses is installed where it should be (this happens under my own "homegrown" build environment as well as under UX2BS. On 11/30/2003 10:12 pm, Henry Sobotka thus wrote : >Lewis G Rosenthal wrote: > > >>It seems that all the distros of ncurses I've seen do not include >>libncurses. Could someone explain to me why and what the difference is >>between ncurses and libncurses, anyway? >> >> > >Normally nothing except for the name. On *nix systems, libraries usually >have a "lib" prefix that isn't specified when linking, e.g. "gcc foo.c >-lbar" will make the linker look for libbar.a. On OS/2, the same command >tells the linker to look for bar.a. So we have socket.a instead of >libsocket.a, ncurses.a instead of libncurses.a etc. > >h~ > > > > > > -- Lewis ------------------------------------------------------------ Lewis G Rosenthal, CNA Rosenthal & Rosenthal Accountants / Network Consultants New York / Northern Virginia www.2rosenthals.com Team OS/2 / NetWare Users International www.novell.com ------------------------------------------------------------ This OS/2 system (Apollo) uptime is 0 days 04:48 hours and 27 seconds **= Email 2 ==========================** Date: Mon, 01 Dec 2003 09:30:59 -0500 From: Henry Sobotka Subject: Re: curses! this libncurses thing... Lewis G Rosenthal wrote: > > Hey, thanks, Henry. So, then, when I have ncurses installed (as I do), > what's up with: > [SNIP] > configure.:5088: result: no > configure.:5103: error: Unable to find libncurses or libcurses > > From what I can tell, ncurses is installed where it should be (this > happens under my own "homegrown" build environment as well as under UX2BS. This shouldn't happen if wherever ncurses is installed is in LIBRARY_PATH. What happens if you create test.c consisting of: int main() { return 0; } and go "gcc test.c -lncurses"? If ncurses is in place, you should get no output. Otherwise ld will complain "No such file or directory for ncurses.a". If you do get no output, what's the command used to compile and link the failing conftest.c? It should appear in config.log. h~ **= Email 3 ==========================** Date: Mon, 1 Dec 2003 11:57:19 +0000 From: John Poltorak Subject: Re: curses! this libncurses thing... On Sun, Nov 30, 2003 at 07:53:51PM -0500, Lewis G Rosenthal wrote: > Does anybody have a complete ncurses build, including libncurses? If you have installed UX2BS successfully, it will have produced a full build of ncurses for you. > Naturally, in my frustration, I decided I'd build ncurses myself, but of > course, this brought along its own set of problems... There are lots of traps to fall into, but the distributed versions of ncurses builds on OS/2 without problems, and its developer has done everything to ensure it is sufficiently cross-platform to handle OS/2 seemlessly. The only problem is that you need to set the environment up correctly using a patched version of Autoconf v2.13 which can be a little tricky to set up, however everything you need to do is done automatically by UX2BS. > -- > Lewis > ------------------------------------------------------------ > Lewis G Rosenthal, CNA > Rosenthal & Rosenthal > Accountants / Network Consultants > New York / Northern Virginia www.2rosenthals.com > Team OS/2 / NetWare Users International www.novell.com > ------------------------------------------------------------ > This OS/2 system (Apollo) uptime is 0 days 04:42 hours and 54 seconds > -- John **= Email 4 ==========================** Date: Mon, 1 Dec 2003 14:02:09 +0000 From: John Poltorak Subject: Re: curses! this libncurses thing... On Mon, Dec 01, 2003 at 02:11:29AM -0500, Lewis G Rosenthal wrote: > Hey, thanks, Henry. So, then, when I have ncurses installed (as I do), > what's up with: What are you trying to build? > -- > Lewis > ------------------------------------------------------------ > Lewis G Rosenthal, CNA > Rosenthal & Rosenthal > Accountants / Network Consultants > New York / Northern Virginia www.2rosenthals.com > Team OS/2 / NetWare Users International www.novell.com > ------------------------------------------------------------ > This OS/2 system (Apollo) uptime is 0 days 04:48 hours and 27 seconds > > -- John **= Email 5 ==========================** Date: Mon, 1 Dec 2003 22:09:03 +0000 From: John Poltorak Subject: Python install When building Python from source, what is the correct installation procedure? It says in README.os2emx that 'make install' isn't yet complete, so in the meantime which directories are an absolute requirement to get a functioning Python installation? I take it that directories such as Demo are optional... -- John