From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Fri, 15 Feb 2002 04:15:22 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 136 ************************************************** Thursday 14 February 2002 Number 136 ************************************************** Subjects for today 1 Re: Autoconf 2.52h : Andreas Buening 2 Fetchmail 5.9.8 : John Poltorak 3 Re: Autoconf 2.52h : John Poltorak 4 Re: Clearing BISON temporary files : Holger Veit 5 IFS=\t ? : John Poltorak 6 Building libregex from BSD libc : John Poltorak 7 Re: Building libregex from BSD libc : Holger Veit 8 Re: TIN build error : Thomas Dickey 9 Re: TIN build error : Thomas Dickey 10 Re: curses.h : Thomas Dickey 11 Checking for BSD compatible install... : John Poltorak 12 TIN build error : John Poltorak 13 Re: TIN build error : John Poltorak **= Email 1 ==========================** Date: Fri, 15 Feb 2002 00:28:48 +0100 From: Andreas Buening Subject: Re: Autoconf 2.52h John Poltorak wrote: > > On Thu, Feb 14, 2002 at 11:02:32PM +0100, Andreas Buening wrote: > > John Poltorak wrote: > > > > > > There's a new beta of Autoconf here:- > > > > > > ftp://alpha.gnu.org/gnu/autoconf/autoconf-2.52h.tar.gz > > > > > > I can't get this on to install. There's some msgs about 'Command not > > > found' which are reminiscent of some Make bugs I've seen. They didn't > > > occur with the previous beta though. > > > > Yes, that's a make bug. > > Hopefully that will be fixed before too long ;-)... > > > However, there is also another bug, > > so you cannot recreate autoconf's configure script. > > Is there a fix available for this? You can apply the following if you want: --- old/autoconf-2.52h/lib/autom4te.in Tue Feb 5 08:11:24 2002 +++ new/autoconf-2.52h/lib/autom4te.in Thu Feb 14 22:48:36 2002 at at -129,7 +129,7 at at # patterns: "*.ac" # patterns: "configure.in" args: --include at datadir at -args: autoconf/autoconf.m4f +args: lib/autoconf/autoconf.m4f args: acsite.m4? args: aclocal.m4? args: --mode 777 at at -149,7 +149,7 at at begin-language: "Autotest" # patterns: *.at args: --include at datadir at -args: autotest/autotest.m4f +args: lib/autotest/autotest.m4f args: package.m4? args: --mode 777 args: --warning syntax at at -164,7 +164,7 at at begin-language: "M4sh" # patterns: *.as args: --include at datadir at -args: m4sugar/m4sh.m4f +args: lib/m4sugar/m4sh.m4f args: --mode 777 args: --warning syntax args: --language M4sugar at at -178,6 +178,6 at at begin-language: "M4sugar" # patterns: *.msh args: --include at datadir at -args: m4sugar/m4sugar.m4f +args: lib/m4sugar/m4sugar.m4f args: --warning syntax end-language: "M4sugar" bye, Andreas -- One OS to rule them all, One OS to find them, One OS to bring them all and in the darkness bind them In the Land of Redmond where the Shadows lie. **= Email 2 ==========================** Date: Fri, 15 Feb 2002 09:25:14 +0000 From: John Poltorak Subject: Fetchmail 5.9.8 The 5.9.8 release of fetchmail is now available at the usual locations, including . The source archive is available at: I don't know if this will build under OS/2, but there was a port of 5.9.6 recently. Maybe the patches from that would work with this... Wonder if the OS/2 patches have been submitted for inclusion in the base version... ISTR that they were at one time a few years ago. -- John **= Email 3 ==========================** Date: Fri, 15 Feb 2002 10:16:36 +0000 From: John Poltorak Subject: Re: Autoconf 2.52h On Fri, Feb 15, 2002 at 12:28:48AM +0100, Andreas Buening wrote: > John Poltorak wrote: > > > > On Thu, Feb 14, 2002 at 11:02:32PM +0100, Andreas Buening wrote: > > > John Poltorak wrote: > > > > > > > > There's a new beta of Autoconf here:- > > > > > > > > ftp://alpha.gnu.org/gnu/autoconf/autoconf-2.52h.tar.gz > > > > > > > > I can't get this on to install. There's some msgs about 'Command not > > > > found' which are reminiscent of some Make bugs I've seen. They didn't > > > > occur with the previous beta though. > > > > > > Yes, that's a make bug. > > > > Hopefully that will be fixed before too long ;-)... > > > > > However, there is also another bug, > > > so you cannot recreate autoconf's configure script. > > > > Is there a fix available for this? > > You can apply the following if you want: > > --- old/autoconf-2.52h/lib/autom4te.in Tue Feb 5 08:11:24 2002 > +++ new/autoconf-2.52h/lib/autom4te.in Thu Feb 14 22:48:36 2002 Thanks. I applied that but still get an error in 'make install' :- make[2]: ../../tests/autom4te: Command not found I tried using Make v3.75 which seemed to get into a loop and finally quit with recursive install errors. > bye, > Andreas > > -- > One OS to rule them all, One OS to find them, > One OS to bring them all and in the darkness bind them > In the Land of Redmond where the Shadows lie. -- John **= Email 4 ==========================** Date: Fri, 15 Feb 2002 11:04:17 +0100 From: Holger Veit Subject: Re: Clearing BISON temporary files On Thu, Feb 14, 2002 at 03:41:45PM +0000, John Poltorak wrote: > > I've noticed a whole load of files in %TMP% which have been created by > BISON; b.act.*, b.attrs.*, b.defs.*, b.tab.*. Do they normally get left > around or is there an option for deleting them? These are intermediate file which should not remain there at all. Unix Bison discards them. It looks to me like a bug in the logic to get rid of them after usage. > Also, is there anyway to identify the originator of various temp files? > I often have files dumped by some process and would like to be able to > identify them in case for the purpose of doing a general tidy up > periodically. There seem to be quite a few p[o,p,r]a* files around. Compiler intermediate files, e.g. by gcc. You have to know the PID (which is the number in the filenames) to identify the process. Holger -- Please update your tables to my new e-mail address: holger.veit$ais.fhg.de (replace the '$' with ' at ' -- spam-protection) **= Email 5 ==========================** Date: Fri, 15 Feb 2002 12:45:25 +0000 From: John Poltorak Subject: IFS=\t ? I came across a neat routine for parsing a line of text yesterday, something which I'd been struggling to do with AWK. Here it is:- grep ^KEY FILENAME | while read p1 p2 p3 ; do echo $p3 $p2 $p1 ; done Unfortunately the default delimiter is " " and I want to use TAB. I think I can do this by setting the envvar IFS, which sounds simple enough, but I haven't got it working. Can someone give me an exammple? -- John **= Email 6 ==========================** Date: Fri, 15 Feb 2002 13:18:00 +0000 From: John Poltorak Subject: Building libregex from BSD libc I've seen some code for building libregex and managed to compile a REGEX.DLL which is one of the standard DLLs in the OS2LIBS package of UnixOS/2. Unfortuantely this is derived from GLIBC and it appears that we don't want to go down that road, so I'd like to be able to build the same thing using BSD libc, but have no idea how. I guess I can use something from Posix/2 but I don't know my way round that package, so I'd be very grateful if someone could supply a Makefile which does the BSD equivalent of:- all: at echo Note: ignore the warning about "implicit declaration of function `free'"! gcc -c regex.c -Wall -I. -O3 -s -Zmt at echo LIBRARY REGEX INITINSTANCE TERMINSTANCE > regex.def at echo DESCRIPTION ' at #UX2:0.12.0.0# at REGEX - POSIX regular expression library 0.12' >> regex.def at echo STACKSIZE 32768 >> regex.def at echo EXPORTS >> regex.def emxexp regex.o >> regex.def ar rc regex.a regex.o emxomf regex.o emximp -o regex.lib regex.def gcc -o regex.dll regex.def regex.obj -Zdll -Zomf -Zcrtdll -Zlinker /exepack:2 -s -Zmt touch -r regex.c regex.dll clean: if exist regex.o del regex.o if exist regex.obj del regex.obj if exist regex.def del regex.def distclean: clean if exist regex.a del regex.a if exist regex.lib del regex.lib if exist regex.dll del regex.dll -- John **= Email 7 ==========================** Date: Fri, 15 Feb 2002 14:53:54 +0100 From: Holger Veit Subject: Re: Building libregex from BSD libc On Fri, Feb 15, 2002 at 01:18:00PM +0000, John Poltorak wrote: > > I've seen some code for building libregex and managed to compile a > REGEX.DLL which is one of the standard DLLs in the OS2LIBS package of > UnixOS/2. Unfortuantely this is derived from GLIBC and it appears that we > don't want to go down that road, so I'd like to be able to build the same > thing using BSD libc, but have no idea how. I guess I can use something > from Posix/2 but I don't know my way round that package, so I'd be very > grateful if someone could supply a Makefile which does the BSD equivalent LIBEMU will provide one as a sideeffect of compiling BSD libc. If my little offspring permits, I might finish a nonworking dummy of BSD libc RSN, for reference, not really for compile and test, because the man(2) functions are currently mostly empty. No need to worry about REGEX it now. You won't be able to plug in the LIBEMU version into the current code anyway; there is no direct replacement between REGEX.DLL(now) and REGEX support (LIEBEMU) anyway. Just assume that there will be a libc which will export the functions that are in the BSD regex/regexp headers somehow (whether they are in a libc.dll or in a libregex.dll or elsewhere is not clear now). What is fundamentally wrong with such a makefile fragment? Nothing, you just need matching headers and source code. Not the way I'd write it, as the below code does not take advantage of make's dependency handling; it is rather a build.cmd script, but it should work for most simple DLLs. > all: > at echo Note: ignore the warning about "implicit declaration of function `free'"! > gcc -c regex.c -Wall -I. -O3 -s -Zmt > at echo LIBRARY REGEX INITINSTANCE TERMINSTANCE > regex.def > at echo DESCRIPTION ' at #UX2:0.12.0.0# at REGEX - POSIX regular expression library 0.12' >> regex.def > at echo STACKSIZE 32768 >> regex.def STACKSIZE is irrelevant for a DLL. > at echo EXPORTS >> regex.def > emxexp regex.o >> regex.def This raises the ordinal vs. name question again. System DLLs should use ordinals, as long as their versions can't be distinugished by the loader. > ar rc regex.a regex.o > emxomf regex.o > emximp -o regex.lib regex.def > gcc -o regex.dll regex.def regex.obj -Zdll -Zomf -Zcrtdll -Zlinker /exepack:2 -s -Zmt > touch -r regex.c regex.dll Holger -- Please update your tables to my new e-mail address: holger.veit$ais.fhg.de (replace the '$' with ' at ' -- spam-protection) **= Email 8 ==========================** Date: Fri, 15 Feb 2002 17:13:13 -0500 From: Thomas Dickey Subject: Re: TIN build error On Fri, Feb 15, 2002 at 09:35:38PM +0000, John Poltorak wrote: > The following error occurred while building TIN 1.5.11:- > > > > [C:\workdir\tin-1.5.11]make build > make[1]: Entering directory `/workdir/tin-1.5.11/src' > gcc -DHAVE_CONFIG_H -I. -I../include -I../pcre -I../pcre -DLOCALEDIR=\"c:/usr/share/locale\" -I../ > nclude -D__ST_MT_ERRNO__ -g -O -Zmt -c ./active.c > In file included from c:\emx\include\curses.h:1, > from ..\include\tcurses.h:112, > from ./active.c:45: > c:\emx\include\bsd/curses.h:50: warning: `TRUE' redefined that isn't ncurses, btw. you won't be able to build tin with the bsd curses. (you can build a termcap or terminfo version, but the curses version assumes the sysv curses). > Configure seemed to run OK. Is this error due to having the wrong curses.h > on the INCLUDE_PATH? yes. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 9 ==========================** Date: Fri, 15 Feb 2002 19:20:06 -0500 From: Thomas Dickey Subject: Re: TIN build error On Fri, Feb 15, 2002 at 11:59:38PM +0000, John Poltorak wrote: > OK, I swapped curses.h and than managed to get it built successfully. Now > I have to work out how to test it... It's probably over six years since I > last tried using TIN, so it may well be a while before I get it to read > any news, but it's good to know I managed to build it. iirc, what I did for testing - copied a .newsrc file from my shell account (so I wouldn't have to wait for tin to read ~30,000 entries from the active newsgroups list), set $NNTPSERVER to another host where I can connect for news, and ran tin -ralQ -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 10 ==========================** Date: Fri, 15 Feb 2002 19:21:33 -0500 From: Thomas Dickey Subject: Re: curses.h On Sat, Feb 16, 2002 at 12:04:01AM +0000, John Poltorak wrote: > > I would like to replace curses.h in EMX with the one from NCURSES for > UnixOS/2. as long as you replace the corresponding library, of course. I doubt that it would break anything since I doubt there are any useful apps that use that bsd library. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 11 ==========================** Date: Fri, 15 Feb 2002 21:21:49 +0000 From: John Poltorak Subject: Checking for BSD compatible install... Sometimes when configure is running:- checking for a BSD compatible install... it finds ./install.sh -c and sometimes it finds c:/usr/bin/install.exe -c. Can someone provide a standalone test for this? I can't figure out why I get differring results. -- John **= Email 12 ==========================** Date: Fri, 15 Feb 2002 21:35:38 +0000 From: John Poltorak Subject: TIN build error The following error occurred while building TIN 1.5.11:- [C:\workdir\tin-1.5.11]make build make[1]: Entering directory `/workdir/tin-1.5.11/src' gcc -DHAVE_CONFIG_H -I. -I../include -I../pcre -I../pcre -DLOCALEDIR=\"c:/usr/share/locale\" -I../ nclude -D__ST_MT_ERRNO__ -g -O -Zmt -c ./active.c In file included from c:\emx\include\curses.h:1, from ..\include\tcurses.h:112, from ./active.c:45: c:\emx\include\bsd/curses.h:50: warning: `TRUE' redefined ..\include\bool.h:46: warning: this is the location of the previous definition c:\emx\include\bsd/curses.h:51: warning: `FALSE' redefined ..\include\bool.h:42: warning: this is the location of the previous definition In file included from c:\emx\include\curses.h:1, from ..\include\tcurses.h:112, from ./active.c:45: c:\emx\include\bsd/curses.h:70: parse error before `100' make[1]: *** [active.o] Error 1 make[1]: Leaving directory `/workdir/tin-1.5.11/src' make: [build] Error 2 (ignored) Configure seemed to run OK. Is this error due to having the wrong curses.h on the INCLUDE_PATH? -- John **= Email 13 ==========================** Date: Fri, 15 Feb 2002 23:59:38 +0000 From: John Poltorak Subject: Re: TIN build error On Fri, Feb 15, 2002 at 05:13:13PM -0500, Thomas Dickey wrote: > On Fri, Feb 15, 2002 at 09:35:38PM +0000, John Poltorak wrote: > > The following error occurred while building TIN 1.5.11:- > > > > > > > > [C:\workdir\tin-1.5.11]make build > > make[1]: Entering directory `/workdir/tin-1.5.11/src' > > gcc -DHAVE_CONFIG_H -I. -I../include -I../pcre -I../pcre -DLOCALEDIR=\"c:/usr/share/locale\" -I../ > > nclude -D__ST_MT_ERRNO__ -g -O -Zmt -c ./active.c > > In file included from c:\emx\include\curses.h:1, > > from ..\include\tcurses.h:112, > > from ./active.c:45: > > c:\emx\include\bsd/curses.h:50: warning: `TRUE' redefined > > that isn't ncurses, btw. Yes, I realised that. > you won't be able to build tin with the bsd curses. (you can build a termcap > or terminfo version, but the curses version assumes the sysv curses). > > > Configure seemed to run OK. Is this error due to having the wrong curses.h > > on the INCLUDE_PATH? > > yes. > OK, I swapped curses.h and than managed to get it built successfully. Now I have to work out how to test it... It's probably over six years since I last tried using TIN, so it may well be a while before I get it to read any news, but it's good to know I managed to build it. Is anyone else interested in testing it? > -- > Thomas E. Dickey > http://invisible-island.net > ftp://invisible-island.net -- John