Date: Sat, 3 Jan 2004 00:04:05 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 281 ************************************************** Friday 02 January 2004 Number 281 ************************************************** Subjects for today 1 libreal : John Poltorak 2 perl question : Dave Saville" 3 Re: New ZLIB : Yuri Dario" 4 Re: perl question : Henry Sobotka 5 Re: perl question : Lyn St George" 6 Re: perl question : Dave Saville" 7 Re: perl question : Dave Saville" 8 Re: perl question : John Poltorak **= Email 1 ==========================** Date: Thu, 1 Jan 2004 15:09:19 +0000 From: John Poltorak Subject: libreal I've just been looking through XINE which has recently been ported to OS/2 and it contains some source for LIBREAL. Does anyone know if this library has been developed for being able to access RealPlayer files? -- John **= Email 2 ==========================** Date: Thu, 01 Jan 2004 18:16:52 +0000 (GMT) From: "Dave Saville" Subject: perl question Months back when I used the build system to build perl it of course did not find chown - rather pointless on OS/2 :-) Recently, installing a package from CPAN, LWP to be exact, needed some sub package that uses chown in its tests - says it's not supported, craps out the test and the whole lot comes crashing down. I knocked up a quick chown in C that does nothing and hacked the os2/config.pm that has a load of switches set at build time but I still get a "this perl was built without chown" or words to that effect. Am I going to have to rebuild perl just to fix this? Yes I could just ignore the test, but the point is I am using "install Bundle::" as it knows about dependencies and some packages are just too complicated to try and manually do one bit and hope you get it right. TIA -- Regards Dave Saville **= Email 3 ==========================** Date: Thu, 01 Jan 2004 19:23:24 +0100 (CET) From: "Yuri Dario" Subject: Re: New ZLIB Hi, >>2. Even when switching to import by name, the OS/2 port must maintain >> the old ordinals, which means no fully automated build is possible. >How exactly do you move over to import by name and keep the old ordinals? I had the same problem creating the MySQL 4.0 client dll: when I did the 3.x version, VAC++ automatically exported all function by name and by ordinal; since ordinal gets first, all available client programs linked to mysql.dll are using ordinals to load the dll. Now I moved to a 'name only' export method using the following trick: in the EXPORTS section v3_mysql_connect = mysql_connect at 38 adds export for ordinal 38 as mysql_connect (as in 3.x code) but the exported name is renamed to v3_mysql_connect, so newer programs will not link with it. Below compatibility list, I added mysql_connect that is the name export for mysql_connect. So all future links to mysql_connect will go to the export by name entry rather than to ordinal 38. The ordinal list will be removed sometimes in the future, when no 3.x code will be allowed to run. Bye, Yuri Dario /* * member of TeamOS/2 - Italy * http://www.os2power.com/yuri * http://www.teamos2.it */ **= Email 4 ==========================** Date: Thu, 01 Jan 2004 15:18:59 -0500 From: Henry Sobotka Subject: Re: perl question Dave Saville wrote: > > Recently, installing a package from CPAN, LWP to be exact, needed > some sub package that uses chown in its tests - says it's not > supported, craps out the test and the whole lot comes crashing down. > > I knocked up a quick chown in C that does nothing and hacked the > os2/config.pm that has a load of switches set at build time but I > still get a "this perl was built without chown" or words to that > effect. > > Am I going to have to rebuild perl just to fix this? Yes, because the error message seems to indicate the test is trying to use Perl's built-in chown, which is normally unimplemented on OS/2. Or you could wrap the failing test in "unless ($^O eq 'os2')". What's the subpackage? There was no such problem with LWP 5.69 last winter. h~ **= Email 5 ==========================** Date: Fri, 02 Jan 2004 05:45:52 +0000 From: "Lyn St George" Subject: Re: perl question On Thu, 01 Jan 2004 18:16:52 +0000 (GMT), Dave Saville wrote: >Months back when I used the build system to build perl it of course >did not find chown - rather pointless on OS/2 :-) > >Recently, installing a package from CPAN, LWP to be exact, needed >some sub package that uses chown in its tests - says it's not >supported, craps out the test and the whole lot comes crashing down. > >I knocked up a quick chown in C that does nothing and hacked the >os2/config.pm that has a load of switches set at build time but I >still get a "this perl was built without chown" or words to that >effect. > >Am I going to have to rebuild perl just to fix this? Yes, but my perls are built with chown for a similar reason. Add into os2ish.h #define HAS_GETPWENT /* fake */ #define HAS_CRYPT #define HAS_CHOWN /* fake */ extern int chown(const char *p, uid_t o, gid_t g); (the last is poached from the wind tree). Ilya Z does not agree with this as it may clash with any multi-user method in future, but it does me for now. >Yes I could just ignore the test, but the point is I am using >"install Bundle::" as it knows about dependencies and some >packages are just too complicated to try and manually do one bit and >hope you get it right. > >TIA > >-- >Regards > >Dave Saville > > > - Cheers Lyn St George +--------------------------------------------------------------------------------- + http://www.zolotek.net .. eCommerce hosting, consulting +---------------------------------------------------------------------------------- **= Email 6 ==========================** Date: Fri, 02 Jan 2004 08:43:12 +0000 (GMT) From: "Dave Saville" Subject: Re: perl question On Thu, 01 Jan 2004 15:18:59 -0500, Henry Sobotka wrote: >What's the subpackage? There was no such problem with LWP 5.69 last >winter. Well as usual I was trying to do three things at once! I wanted to see if DBI would install so I started with that. perl immediately said there was a later version of CPAN. So I started that in case it made any difference to the errors I was getting with DBI. It took a long time to get everything right in the environment etc. but finally the build from CPAN over the net started working which I had never managed before. At some point in the past I had tried LWP and given up, so I tried it again. Now I can't recall which in that lot needed chown. Thinking back through the haze of Christmas it was most likely CPAN as the package was Archive-Tar-1.07 which is part of the CPAN bundle IIRC. -- Regards Dave Saville **= Email 7 ==========================** Date: Fri, 02 Jan 2004 08:44:55 +0000 (GMT) From: "Dave Saville" Subject: Re: perl question On Fri, 02 Jan 2004 05:45:52 +0000, Lyn St George wrote: >On Thu, 01 Jan 2004 18:16:52 +0000 (GMT), Dave Saville wrote: > >>Months back when I used the build system to build perl it of course >>did not find chown - rather pointless on OS/2 :-) >> >>Recently, installing a package from CPAN, LWP to be exact, needed >>some sub package that uses chown in its tests - says it's not >>supported, craps out the test and the whole lot comes crashing down. >> >>I knocked up a quick chown in C that does nothing and hacked the >>os2/config.pm that has a load of switches set at build time but I >>still get a "this perl was built without chown" or words to that >>effect. >> >>Am I going to have to rebuild perl just to fix this? > >Yes, but my perls are built with chown for a similar reason. Add into os2ish.h >#define HAS_GETPWENT /* fake */ >#define HAS_CRYPT >#define HAS_CHOWN /* fake */ >extern int chown(const char *p, uid_t o, gid_t g); > >(the last is poached from the wind tree). Ilya Z does not agree with this as >it may clash with any multi-user method in future, but it does me for now. Thanks - I will try this. Do I actually need real exe's to back up those two fake entries? -- Regards Dave Saville **= Email 8 ==========================** Date: Fri, 2 Jan 2004 11:14:43 +0000 From: John Poltorak Subject: Re: perl question On Fri, Jan 02, 2004 at 05:45:52AM +0000, Lyn St George wrote: > > >Months back when I used the build system to build perl it of course > >did not find chown - rather pointless on OS/2 :-) > > > >Recently, installing a package from CPAN, LWP to be exact, needed > >some sub package that uses chown in its tests - says it's not > >supported, craps out the test and the whole lot comes crashing down. > > > >I knocked up a quick chown in C that does nothing and hacked the > >os2/config.pm that has a load of switches set at build time but I > >still get a "this perl was built without chown" or words to that > >effect. > > > >Am I going to have to rebuild perl just to fix this? > > Yes, but my perls are built with chown for a similar reason. Add into os2ish.h > #define HAS_GETPWENT /* fake */ > #define HAS_CRYPT > #define HAS_CHOWN /* fake */ > extern int chown(const char *p, uid_t o, gid_t g); How do tell if an existing Perl was built with chown? > (the last is poached from the wind tree). Ilya Z does not agree with this as > it may clash with any multi-user method in future, but it does me for now. At this point in time would it be preferable to use chown? I could put the required changes into UX2BS so that it could default to HAS_CHOWN. > - > Cheers > Lyn St George > +--------------------------------------------------------------------------------- > + http://www.zolotek.net .. eCommerce hosting, consulting > +---------------------------------------------------------------------------------- > -- John