From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Sat, 14 Dec 2002 04:43:44 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 398 ************************************************** Friday 13 December 2002 Number 398 ************************************************** Subjects for today 1 HTML Tidy : Christian Hennecke" 2 Mailman: update : Ted Sikora 3 Re: mkinstalldirs : Thomas Dickey 4 Re: Mailman: update : Ted Sikora 5 Perl - op/stat.t error : John Poltorak 6 Re: terminfo : Thomas Dickey 7 Re: mkinstalldirs : John Poltorak 8 Re: Building Autoconf from original source : Andreas Buening 9 Re: mkinstalldirs : Andreas Buening 10 Re: libunixos2 (was: sysexits.h) : Andreas Buening 11 Re: Building Autoconf from original source : John Poltorak 12 terminfo : John Poltorak 13 Building PDKSH 5.2.14 : John Poltorak 14 Re: Building Autoconf from original source : Thomas Dickey 15 Re: Building Autoconf from original source : John Poltorak 16 Re: Building Autoconf from original source : John Poltorak **= Email 1 ==========================** Date: Sat, 14 Dec 2002 02:31:17 +0100 (CET) From: "Christian Hennecke" Subject: HTML Tidy A while ago I started to build OS/2 binaries of HTML Tidy, a nice tool for pretty-printing and checking/correcting HTML and XML code which can also read and do some conversions between several codepages. Lately, I have added support for codepage 850 to Tidy and switched over to the code that is based on TidyLib. This seems to be working well. However, Tidy also can support Asian character encodings (Big5, shiftjs) and UTF-16. I have turned on these options for compilation, but I don't know if it's going to work on OS/2 and I cannot test it here (or at least I don't know how to do it). It would be nice if someone with suitable files and system could try this and tell me if it works. For documentation see: http://tidy.sourceforge.net/ For OS/2 test binaries see: http://www.os2world.com/os2files/files/tidy-os2-bin-20021213.zip Please don't upload this test package anywhere yet. Christian Hennecke **= Email 2 ==========================** Date: Sat, 14 Dec 2002 10:30:07 -0500 From: Ted Sikora Subject: Mailman: update Administrative tools and cgi web interface work flawlessly. MailLists can be added, removed or edited just fine. We have (2) problems: Mail cannot be sent: 1) Hit enter to continue with announce owner notification... Traceback (most recent call last): File "./newlist", line 220, in ? main() File "./newlist", line 214, in main HandlerAPI.DeliverToUser(mlist, msg) File "/unixos2/home/mailman/Mailman/Handlers/HandlerAPI.py", line 182, in Deli verToUser return DeliverToList(mlist, msg, msgdata) File "/unixos2/home/mailman/Mailman/Handlers/HandlerAPI.py", line 149, in Deli verToList pipeline = do_pipeline(mlist, msg, msgdata, pipeline) File "/unixos2/home/mailman/Mailman/Handlers/HandlerAPI.py", line 82, in do_pi peline func(mlist, msg, msgdata) 2) Lifetime locks: You have to manually remove the locks in the /locks dir to continue after each administrative task otherwise it fails or hangs. Once the locks are removed it's fine. -- Ted **= Email 3 ==========================** Date: Sat, 14 Dec 2002 10:38:26 -0500 From: Thomas Dickey Subject: Re: mkinstalldirs On Sat, Dec 14, 2002 at 02:21:52PM +0000, John Poltorak wrote: > On Sat, Dec 14, 2002 at 02:43:05PM +0100, Andreas Buening wrote: > > John Poltorak wrote: > > > On Thu, Dec 12, 2002 at 10:20:19PM +0100, Andreas Buening wrote: > > > > Thomas Dickey wrote: > > > > > On Wed, Dec 11, 2002 at 03:14:29PM +0000, John Poltorak wrote: > > > > > > Is the mkinstalldirs shell script included in Autoconf v2.57 suitable for > > > > > > use on OS/2 or not? > > > > > it doesn't know about drive letters, if that's what you mean. > > > > Not exactly. At least if they haven't changed it recently. > > > > It uses "mkdir -p" which knows about drive letters. > > > Can we get an OS/2 compliant version included with Autoconf? > > > If not what should we use as the definitive version on OS/2? > > The current mkinstalldirs _is_ OS/2 compliant. > Thomas said it didn't support drive letters... ...and the response to that said it uses "mkdir -p" (which doesn't work on some older platforms - not an issue for you), and that "mkdir -p" in your environment works adequately. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 4 ==========================** Date: Sat, 14 Dec 2002 10:39:54 -0500 From: Ted Sikora Subject: Re: Mailman: update Ted Sikora wrote: > > Administrative tools and cgi web interface work flawlessly. MailLists > can be added, removed or edited > just fine. > > We have (2) problems: > > 1) > > Mail cannot be sent: > > > Hit enter to continue with announce owner notification... > > Traceback (most recent call last): > File "./newlist", line 220, in ? > main() > File "./newlist", line 214, in main > HandlerAPI.DeliverToUser(mlist, msg) > File "/unixos2/home/mailman/Mailman/Handlers/HandlerAPI.py", line 182, > in Deli > verToUser > return DeliverToList(mlist, msg, msgdata) > File "/unixos2/home/mailman/Mailman/Handlers/HandlerAPI.py", line 149, > in Deli > verToList > pipeline = do_pipeline(mlist, msg, msgdata, pipeline) > File "/unixos2/home/mailman/Mailman/Handlers/HandlerAPI.py", line 82, > in do_pi > peline > func(mlist, msg, msgdata) > > 2) Lifetime locks: > > You have to manually remove the locks in the /locks dir > to continue after each administrative task otherwise it fails or > hangs. Once the locks are removed it's fine. Make that 3 problem areas: 3) Logging into the admin interface via the web produces: at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at admin(3206): [----- Mailman Version: 2.0.13 -----] admin(3206): [----- Traceback ------] admin(3206): Traceback (most recent call last): admin(3206): File "/unixos2/home/mailman/scripts/driver", line 96, in run_main admin(3206): main() admin(3206): File "/unixos2/home/mailman/Mailman/Cgi/admin.py", line 175, in main admin(3206): mlist.Save() admin(3206): File "/unixos2/home/mailman/Mailman/MailList.py", line 864, in Save admin(3206): self.__save(dict) admin(3206): File "/unixos2/home/mailman/Mailman/MailList.py", line 843, in __save admin(3206): os.rename(fname_tmp, fname) admin(3206): OSError: [Errno 13] Permission denied -- Ted **= Email 5 ==========================** Date: Sat, 14 Dec 2002 11:24:51 +0000 From: John Poltorak Subject: Perl - op/stat.t error When building Perl 5.8.0 I often get an error in the op/stat.t test, but not always, even though I'm trying to use the same environment. Does anyone know what this test is about and why the result can be inconsistant? -- John **= Email 6 ==========================** Date: Sat, 14 Dec 2002 12:00:11 -0500 From: Thomas Dickey Subject: Re: terminfo On Sat, Dec 14, 2002 at 04:33:46PM +0000, John Poltorak wrote: > > Is TERMINFO usually supplied with NCURSES? yes. > It's something which has just been installed when I built NCURSES, but it > doesn't apear in the recent NCURSES port on Hobbes. Wondered if this > would be likely to cause anyone a problem... perhaps (I didn't look at the port). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 7 ==========================** Date: Sat, 14 Dec 2002 14:21:52 +0000 From: John Poltorak Subject: Re: mkinstalldirs On Sat, Dec 14, 2002 at 02:43:05PM +0100, Andreas Buening wrote: > John Poltorak wrote: > > > > On Thu, Dec 12, 2002 at 10:20:19PM +0100, Andreas Buening wrote: > > > Thomas Dickey wrote: > > > > > > > > On Wed, Dec 11, 2002 at 03:14:29PM +0000, John Poltorak wrote: > > > > > > > > > > Is the mkinstalldirs shell script included in Autoconf v2.57 suitable for > > > > > use on OS/2 or not? > > > > > > > > it doesn't know about drive letters, if that's what you mean. > > > > > > Not exactly. At least if they haven't changed it recently. > > > It uses "mkdir -p" which knows about drive letters. > > > > Can we get an OS/2 compliant version included with Autoconf? > > > > If not what should we use as the definitive version on OS/2? > > The current mkinstalldirs _is_ OS/2 compliant. Thomas said it didn't support drive letters... > 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 Mordor where the Shadows lie. -- John **= Email 8 ==========================** Date: Sat, 14 Dec 2002 14:42:57 +0100 From: Andreas Buening Subject: Re: Building Autoconf from original source John Poltorak wrote: > > On Thu, Dec 12, 2002 at 10:20:53PM +0100, Andreas Buening wrote: [autoconf] > > Sorry, I haven't followed the discussion completely. What > > exactly are your problems? > > I'm not sure which source to use for your 2.53br2. > > Also, is it necessary to use Make v3.79.1 when building GNU Autoconf 2.57? If you're in doubt use the latest version which is 3.79.2a1. > My system gets into a loop when running Make, and it may be related to the > version of Make I'm using. > > When using Make v3.79.1 I get:- > > AUTOCONF-2.57/Makefile.maint:344: *** multiple target patterns. Stop. Hmm, I wonder how you get this. Makefile.maint should never be used. I've just downloaded autoconf 2.57, set CONFIG_SITE to x:/etc/unixos2/config.site and run ./configure --prefix=x:/test and I installed it out of the box. What exactly did you do? 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 Mordor where the Shadows lie. **= Email 9 ==========================** Date: Sat, 14 Dec 2002 14:43:05 +0100 From: Andreas Buening Subject: Re: mkinstalldirs John Poltorak wrote: > > On Thu, Dec 12, 2002 at 10:20:19PM +0100, Andreas Buening wrote: > > Thomas Dickey wrote: > > > > > > On Wed, Dec 11, 2002 at 03:14:29PM +0000, John Poltorak wrote: > > > > > > > > Is the mkinstalldirs shell script included in Autoconf v2.57 suitable for > > > > use on OS/2 or not? > > > > > > it doesn't know about drive letters, if that's what you mean. > > > > Not exactly. At least if they haven't changed it recently. > > It uses "mkdir -p" which knows about drive letters. > > Can we get an OS/2 compliant version included with Autoconf? > > If not what should we use as the definitive version on OS/2? The current mkinstalldirs _is_ OS/2 compliant. 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 Mordor where the Shadows lie. **= Email 10 ==========================** Date: Sat, 14 Dec 2002 14:43:13 +0100 From: Andreas Buening Subject: Re: libunixos2 (was: sysexits.h) John Poltorak wrote: > > On Fri, Dec 13, 2002 at 08:52:40PM +1100, Nicholas Sheppard wrote: > > I've got a programme that wants sysexits.h to compile. It exists on > > my Linux installation but doesn't seem to exist in EMX; is it part of some > > package? > > Having looked further, it appears to be part of GLIBC. > > We really ought to have some equivalent of this. I'm not sure if this is > what is intended for libunixos2. Maybe sysexits.h ought to be included > in that... Yes, that's exactly what libunixos2 is intended to be. For the next release I plan to add two static dummy libs. Both contain functions that are not supported by emx and can't be implemented like symlink() or chown(). The functions contained in the first library (os2dummy.a) will ever return an error ENOTSUP (function not supported) while the second library (os2links.a? - name suggestions are still accepted :-) ) will try to emulate this behaviour, e.g. chown() returns success, symlink() copies the file. The goal of these small dummy libraries is that you don't have to reinvent the wheel (i.e. write a symlink() or chown() implementation) ever and ever and ever and ever and ever again for every simple tool. Check out whether you need emulation of working links or whether your program can deal with not working links. Then add the according -los2dummy or -los2links to your LIBS and just compile your program. Of course, this is just to simplify the developer's life, a normal user wouldn't know what he should do if you don't tell him. If you have written any implementation of functions like chown(), fchown(), link(), symlink(), for any unix-like package please submit them so that I can build them into the next libunixos2 release. Thanks! 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 Mordor where the Shadows lie. **= Email 11 ==========================** Date: Sat, 14 Dec 2002 15:04:05 +0000 From: John Poltorak Subject: Re: Building Autoconf from original source On Sat, Dec 14, 2002 at 02:42:57PM +0100, Andreas Buening wrote: > John Poltorak wrote: > > > > On Thu, Dec 12, 2002 at 10:20:53PM +0100, Andreas Buening wrote: > > [autoconf] > > > > Sorry, I haven't followed the discussion completely. What > > > exactly are your problems? > > > > I'm not sure which source to use for your 2.53br2. > > > > Also, is it necessary to use Make v3.79.1 when building GNU Autoconf 2.57? > > If you're in doubt use the latest version which is 3.79.2a1. I came across a problem with it when building a particular app so I reverted to 3.79.1. Unfortunately I don't recall which app... > > My system gets into a loop when running Make, and it may be related to the > > version of Make I'm using. > > > > When using Make v3.79.1 I get:- > > > > AUTOCONF-2.57/Makefile.maint:344: *** multiple target patterns. Stop. > > Hmm, I wonder how you get this. Makefile.maint should never > be used. I've just downloaded autoconf 2.57, set CONFIG_SITE > to x:/etc/unixos2/config.site and run ./configure --prefix=x:/test > and I installed it out of the box. What exactly did you do? I'm developing a standard Build System which is meant as a universal wrapper for all UnixOS/2 builds. It works fine for Perl and NCURSES, but Autoconf fails every time. It is a very controlled and reproducible environment. I can let you have a copy if you like - it only takes up 500kB. > 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 Mordor where the Shadows lie. -- John **= Email 12 ==========================** Date: Sat, 14 Dec 2002 16:33:46 +0000 From: John Poltorak Subject: terminfo Is TERMINFO usually supplied with NCURSES? It's something which has just been installed when I built NCURSES, but it doesn't apear in the recent NCURSES port on Hobbes. Wondered if this would be likely to cause anyone a problem... -- John **= Email 13 ==========================** Date: Sat, 14 Dec 2002 17:18:20 +0000 From: John Poltorak Subject: Building PDKSH 5.2.14 Has anyone tried building PDKSH 5.2.14? Is it fairly straightfoward? -- John **= Email 14 ==========================** Date: Sat, 14 Dec 2002 18:52:27 -0500 From: Thomas Dickey Subject: Re: Building Autoconf from original source On Sun, Dec 15, 2002 at 12:17:57AM +0100, Stefan Neis wrote: > On Fri, 13 Dec 2002, John Poltorak wrote: > > > I nearly always need to rebuild configure to have a chance of building the > > app correctly on OS/2. It doesn't take long to run autoconf in any case. > > That's certainly true for all scripts generated by old autoconf versions > (e.g. 2.13), i.e. currently for the vast majority, but shouldn't be the > case for those generated by current autoconf versions... (at least in > theory...). The problem is that not every software package will include > it's configure.in... are any of those useful? (my policy is to not send bug reports to people who do that) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 15 ==========================** Date: Sat, 14 Dec 2002 21:51:29 +0000 From: John Poltorak Subject: Re: Building Autoconf from original source On Sat, Dec 14, 2002 at 02:42:57PM +0100, Andreas Buening wrote: > John Poltorak wrote: > > When using Make v3.79.1 I get:- > > > > AUTOCONF-2.57/Makefile.maint:344: *** multiple target patterns. Stop. > > Hmm, I wonder how you get this. Makefile.maint should never > be used. I've just downloaded autoconf 2.57, set CONFIG_SITE > to x:/etc/unixos2/config.site and run ./configure --prefix=x:/test > and I installed it out of the box. What exactly did you do? After getting it to work in another environment, I compared the two Makefiles and they were very similar but I couldn't explain three differences. The one which didn't work included the variable VPATH and the variables srcdir and topsrcdir had paths set. The one which did work had those two variables set to '.'. When I changed the srcdir on the former Makefile, the error above disppeared. I have no explanation for any of this but can easily reproduce the error above. > > 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 Mordor where the Shadows lie. -- John **= Email 16 ==========================** Date: Sat, 14 Dec 2002 23:09:57 +0000 From: John Poltorak Subject: Re: Building Autoconf from original source On Sat, Dec 14, 2002 at 09:51:29PM +0000, John Poltorak wrote: > On Sat, Dec 14, 2002 at 02:42:57PM +0100, Andreas Buening wrote: > > John Poltorak wrote: > > > > When using Make v3.79.1 I get:- > > > > > > AUTOCONF-2.57/Makefile.maint:344: *** multiple target patterns. Stop. > > > > Hmm, I wonder how you get this. Makefile.maint should never > > be used. I've just downloaded autoconf 2.57, set CONFIG_SITE > > to x:/etc/unixos2/config.site and run ./configure --prefix=x:/test > > and I installed it out of the box. What exactly did you do? > > After getting it to work in another environment, I compared the two > Makefiles and they were very similar but I couldn't explain three > differences. The one which didn't work included the variable VPATH and the > variables srcdir and topsrcdir had paths set. The one which did work had > those two variables set to '.'. When I changed the srcdir on the former > Makefile, the error above disppeared. > > > I have no explanation for any of this but can easily reproduce the error > above. The problem seems to occur when a drive letter is include in srcdir... If anyone has tried installing Autoconf recently, could you try editing the Makefile created by run configure, and just before running Make, change srcdir in the Makefile so that has a full path including drive letter, and see if you get the 'multiple target patterns' error when running make. > > > > 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 Mordor where the Shadows lie. -- John