From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Sun, 26 Jan 2003 04:49:07 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 25 ************************************************** Saturday 25 January 2003 Number 25 ************************************************** Subjects for today 1 Re: SLANG : Thomas E. Dickey" 2 SLANG : John Poltorak 3 Re: RSYNC : Maynard" 4 Re: Terminfo database : Thomas Dickey 5 RSYNC : John Poltorak 6 Mailing lists : Jeff Robinson 7 Terminfo database : John Poltorak 8 wxWindows & varying build environments : Stefan Neis **= Email 1 ==========================** Date: Sun, 26 Jan 2003 09:30:45 -0500 (EST) From: "Thomas E. Dickey" Subject: Re: SLANG On Sun, 26 Jan 2003, John Poltorak wrote: > If we have anyone familiar with building and using SLANG, I'd like to > compare a few notes... > > What is the preferred method of building the library? it depends - the last time I looked, slang was missing some pieces to build on OS/2 EMX - as a "Unix" platform. I built it as a native OS/2 application, but that means it won't work on the telnet connection that I usually test-build on OS/2. > > What files need to be installed into a development environment from the > supplied SLANG archive? > > > -- T.E.Dickey http://invisible-island.net ftp://invisible-island.net **= Email 2 ==========================** Date: Sun, 26 Jan 2003 09:46:57 +0000 From: John Poltorak Subject: SLANG If we have anyone familiar with building and using SLANG, I'd like to compare a few notes... What is the preferred method of building the library? What files need to be installed into a development environment from the supplied SLANG archive? -- John **= Email 3 ==========================** Date: Sun, 26 Jan 2003 10:31:47 -0600 (CST) From: "Maynard" Subject: Re: RSYNC On Sun, 26 Jan 2003 14:53:05 +0000, John Poltorak wrote: >I nearly alwats get an error msg from the client >relating to something not found in main.c for example. The error msg makes >it appear to be more serious than it actually is. It seems that I *_always_* see this error; and I've never been able to agree that there was an actual problem. -- Maynard **= Email 4 ==========================** Date: Sun, 26 Jan 2003 13:13:15 -0500 From: Thomas Dickey Subject: Re: Terminfo database On Sun, Jan 26, 2003 at 04:49:47PM +0000, John Poltorak wrote: > Ncurses (v5.3) includes the file terminfo.src. > > Version 10.2.1 > $Date: 2002/10/05 18:40:53 $ > terminfo syntax > > GNU Termcap (v1.3.1) includes the file termcap.src. > > Version 11.0.1 > $Date: 2000/03/02 15:51:11 $ > termcap syntax I did point out to termcap's maintainers last year that it should be based on ncurses' version. They promised to look into it, but I haven't seen any result. (Oddly this morning I was working on an install of SuSE, whose termcap file has no comments ;-) > Both are described as TERMINAL TYPE DESCRIPTIONS SOURCE FILE, and I > understand they are derived from a common source. What I don't understand > is the version numbering. Does it refer to the common source, or is it the > version of that particular file. long story (will spare details unless someone says he's a masochist). ncurses's "10.2.1" is a later version than esr's "11.0.1". The esr version is actually based on ncurses changes in 1999. It's a little awkward to diff, because esr's version reordered the file - in iirc 1998 - without changing more than a couple hundred lines of comments. otoh, I've made a few thousand lines of corrections to the terminfo entries. > It seems a bit mixed up to me... politics... -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 5 ==========================** Date: Sun, 26 Jan 2003 14:53:05 +0000 From: John Poltorak Subject: RSYNC I've been very pleased to be able to able to run an RSYNC server for a number of weeks and it does seem to run pretty well. One thing I have noticed, though is that I nearly alwats get an error msg from the client relating to something not found in main.c for example. The error msg makes it appear to be more serious than it actually is. Is it worth reporting these problems? Also, I just found my rsync server had not servicing any requests for a while. Netstat -s showed:- 0 STREAM 50378 rsync..873 209.54.72.109 CLOSE_WAIT 0 STREAM 50379 rsync..873 209.54.72.109 CLOSE_WAIT 0 STREAM 51009 rsync..873 192.168.0.13 CLOSE_WAIT 0 STREAM 50598 rsync..873 209.54.72.109 CLOSE_WAIT 0 STREAM 50599 rsync..873 209.54.72.109 CLOSE_WAIT 0 STREAM 59657 rsync..873 213.152.37.91 ESTABLISH 0 STREAM 50352 rsync..873 209.54.72.109 CLOSE_WAIT 0 STREAM 50356 rsync..873 209.54.72.109 CLOSE_WAIT Does this indicate any sort of problem? -- John **= Email 6 ==========================** Date: Sun, 26 Jan 2003 15:55:15 -0600 From: Jeff Robinson Subject: Mailing lists Does anyone have a link for either joining the UnixOS2 mailing list or viewing the archives? At one time I had a link for it, but now the link leads to the OS2Ports mailing list and not the UnixOS2 list... and I can't seem to come up with a definitive site. Jeff **= Email 7 ==========================** Date: Sun, 26 Jan 2003 16:49:47 +0000 From: John Poltorak Subject: Terminfo database Ncurses (v5.3) includes the file terminfo.src. Version 10.2.1 $Date: 2002/10/05 18:40:53 $ terminfo syntax GNU Termcap (v1.3.1) includes the file termcap.src. Version 11.0.1 $Date: 2000/03/02 15:51:11 $ termcap syntax Both are described as TERMINAL TYPE DESCRIPTIONS SOURCE FILE, and I understand they are derived from a common source. What I don't understand is the version numbering. Does it refer to the common source, or is it the version of that particular file. It seems a bit mixed up to me... -- John **= Email 8 ==========================** Date: Sun, 26 Jan 2003 19:49:19 +0100 (CET) From: Stefan Neis Subject: wxWindows & varying build environments Hi, I thought I was cross-posting a couple of questions that did arise when compiling wxWindows-2.4.0 on a different box with a set of newer tools to the list, but apparently I didn't. So, I'll give a short summary to spare others the same kind of problems: - The newest bison still relies on the environment variable BISON_SIMPLE to locate its parser skeleton file "bison.simple", I was hoping for an automated look into $(UNIXROOT)/usr/share/lib (or whatever its location), so I failed to set that variable. - If you want to build wxBase (the toolkit restricted to non-GUI-related stuff), you need to pass "--disable-snglinst" to the configure script. - setting "INSTALL" to anything containing a drive letter (or have configure autodetect anything with a drive letter like f:/usr/bin/install.exe) makes the make process fail at the very end. set INSTALL to something which uses a relative path, at worst to the included "install-sh". - older versions of GNUmake supported "MAKE_SHELL", in the current version, that variable is named "MAKESHELL" (no more underscore!). - langinfo.h was/is missing an extern "C", so the one function it offers cannot be succesfully used from C++. Instead, it breaks the code at linking stage. Any idea what package on unixos2.com contains that broken "langinfo.h" and is there a chance to fix it? - If langinfo.h exists (in a fixed form), you still need to manually add "-lintl" to the linker flags, currently. I'll try to make an updated configure script available ASAP to avoid most of those problems... Regards, Stefan -- Micro$oft is not an answer. It is a question. The answer is 'no'.