From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Tue, 25 Nov 2003 14:16:02 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 251 ************************************************** Monday 24 November 2003 Number 251 ************************************************** Subjects for today 1 New ZLIB : John Poltorak 2 sh alloc error : John Poltorak 3 Re: New ZLIB : John Poltorak 4 Re: New ZLIB : Stefan Neis 5 Re: New ZLIB : Stefan Neis 6 conflicting types for `_getcwd2' : John Poltorak 7 getopt problem : John Poltorak **= Email 1 ==========================** Date: Tue, 25 Nov 2003 09:14:11 +0000 From: John Poltorak Subject: New ZLIB ZLIB v1.2.1 has recently been released and is now available from:- http://www.zlib.org Does anyone know if this will build straight out of the box on OS/2? -- John **= Email 2 ==========================** Date: Tue, 25 Nov 2003 10:40:58 +0000 From: John Poltorak Subject: sh alloc error Does anyone have any idea what this error msg means:- ? ../devtools/bin/Build[796]: internal error: alloc: freeing memory outside of block (corrupted?) I'm using the most recent version of PDKSH which has worked well so far. Could it be a problem with stacksize or somesuch? The same error occurs on different machines, but disappears when using bash.exe renamed as sh.exe. -- John **= Email 3 ==========================** Date: Tue, 25 Nov 2003 11:14:34 +0000 From: John Poltorak Subject: Re: New ZLIB On Tue, Nov 25, 2003 at 11:34:31AM +0100, Stefan Neis wrote: > On Tue, 25 Nov 2003, John Poltorak wrote: > > > ZLIB v1.2.1 has recently been released and is now available from:- > > > > > > http://www.zlib.org > > > > > > Does anyone know if this will build straight out of the box on OS/2? > > According to old\README in that package, none of the OS/2 specific files > (i.e. Makefile.os2 and zlib.def) has been updated for zlib-1.2.1. :-( I wouldn't expect them to be updated. I don't think there is any OS/2 maintainer. There are quite a number of people who maintain their own versions of ZLIB independently. It would be useful if someone could submit their patches to the ZLIB team so that it could be built by everyone on OS/2 straight out of the box. > However, getting a suitable Makefile shouldn't be that difficult. Note, > however, that the configure script apparently is _not_ generated by > autoconf, so it might be easier to adapt the existing Makefile.os2 than > to generate one by configure. > > zlib-1.2.1 officially states that it want's export by name to > be used, so the def-File might require some changes as well ... I believe the def file was originally copied from NT and no one changed it properly. And I'm not sure that Makefile.OS2 is correct either... It would be nice to get them updated but I'm not sure what should be changed. > Regards, > Stefan > -- > Micro$oft is not an answer. It is a question. The answer is 'no'. > -- John **= Email 4 ==========================** Date: Tue, 25 Nov 2003 11:34:31 +0100 (CET) From: Stefan Neis Subject: Re: New ZLIB On Tue, 25 Nov 2003, John Poltorak wrote: > ZLIB v1.2.1 has recently been released and is now available from:- > > > http://www.zlib.org > > > Does anyone know if this will build straight out of the box on OS/2? According to old\README in that package, none of the OS/2 specific files (i.e. Makefile.os2 and zlib.def) has been updated for zlib-1.2.1. :-( However, getting a suitable Makefile shouldn't be that difficult. Note, however, that the configure script apparently is _not_ generated by autoconf, so it might be easier to adapt the existing Makefile.os2 than to generate one by configure. zlib-1.2.1 officially states that it want's export by name to be used, so the def-File might require some changes as well ... Regards, Stefan -- Micro$oft is not an answer. It is a question. The answer is 'no'. **= Email 5 ==========================** Date: Tue, 25 Nov 2003 11:34:31 +0100 (CET) From: Stefan Neis Subject: Re: New ZLIB On Tue, 25 Nov 2003, John Poltorak wrote: > ZLIB v1.2.1 has recently been released and is now available from:- > > > http://www.zlib.org > > > Does anyone know if this will build straight out of the box on OS/2? According to old\README in that package, none of the OS/2 specific files (i.e. Makefile.os2 and zlib.def) has been updated for zlib-1.2.1. :-( However, getting a suitable Makefile shouldn't be that difficult. Note, however, that the configure script apparently is _not_ generated by autoconf, so it might be easier to adapt the existing Makefile.os2 than to generate one by configure. zlib-1.2.1 officially states that it want's export by name to be used, so the def-File might require some changes as well ... Regards, Stefan -- Micro$oft is not an answer. It is a question. The answer is 'no'. **= Email 6 ==========================** Date: Tue, 25 Nov 2003 13:00:40 +0000 From: John Poltorak Subject: conflicting types for `_getcwd2' Why do I get this:- ? In file included from assert.c:20: c:\emx\include\stdlib.h:229: conflicting types for `_getcwd2' c:\emx\include\stdlib.h:163: previous declaration of `_getcwd2' In file included from assert.c:21: c:\emx\include\unistd.h:99: conflicting types for `_getcwd2' c:\emx\include\stdlib.h:229: previous declaration of `_getcwd2' make: *** [assert.o] Error 1 Lines 20 & 21 of assert.c contain:- #include #include -- John **= Email 7 ==========================** Date: Tue, 25 Nov 2003 22:07:35 +0000 From: John Poltorak Subject: getopt problem I have this problem with 'getopt':- conf.c: In function `getopt': conf.c:2992: argument `nargv' doesn't match prototype c:\emx\include\unistd.h:154: prototype declaration unistd.h defines it like this:- int getopt (int, char **, __const__ char *); conf.c has it like this:- int getopt(nargc,nargv,ostr) int nargc; char *const *nargv; const char *ostr; How do I rectify the conflict? -- John