RE: :ShareLite with 5.6
I tried it (on Solaris) and indeed IPC::ShareLite does
indeed pass on tests, however IPC::SharedCache (which is
a pure-Perl module that uses IPC::ShareList does not
pass its tests:
Running make test
PERL_DL_NONLAZY=1 /usrl1/home/pweiss/perl-56/bin/perl -Iblib/arch -Iblib/lib
-I/usrl1/home/pweiss/perl-56/lib/5.6.0/sun4-solaris
-I/usrl1/home/pweiss/perl-56/lib/5.6.0 test.pl
1..9
ok 1
ok 2
IPC::SharedCache: Unable to get shared cache block 9 : No such file or
directory at blib/lib/IPC/SharedCache.pm line 1040
IPC::SharedCache::_get_share_object('IPC::SharedCache=HASH(0xfea30)', 9)
called at blib/lib/IPC/SharedCache.pm line 517
IPC::SharedCache::FETCH('IPC::SharedCache=HASH(0xfea30)',
'some_key') called at test.pl line 35
*** Error code 255
make: Fatal error: Command failed for target `test_dynamic'
/usr/ccs/bin/make test -- NOT OK
-Original Message-
From: jason kirtland [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 28, 2000 1:59 PM
To: Paul G. Weiss; [EMAIL PROTECTED]
Subject: RE: :ShareLite with 5.6
The following has cleared up most module problems for me-
Build Perl 5.6 like so:
Configure -Dbincompat5005 -Accflags=-DPERL_POLLUTE
And then for modules:
perl Makefile.PL POLLUTE=1
On Linux, IPC::ShareLite passes all tests using the above.
-=j
> -Original Message-
> From: Paul G. Weiss [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, March 28, 2000 4:18 AM
> To: [EMAIL PROTECTED]
> Subject: IPC::ShareLite with 5.6
>
>
> I have been unsuccessful in building IPC::ShareLite,
> which is used by HTML::Template under 5.6. Two problems:
>
> (1) It won't build at all w/o adding
> #define PERL_POLLUTE
>
> before the
>
> #include "EXTERN.h"
> #include "perl.h"
> #include "XSUB.h"
>
> in ShareLite.xs.
>
> (2) After building it, test fails:
>
> 1..8
> ok 1
> ok 2
> ok 3
> Bad realloc() ignored at
> /usrl1/home/pweiss/perl-56/lib/site_perl/5.6.0/sun4-solari
s/IPC/ShareLite.pm
> line 111.
> Segmentation Fault (core dumped)
>
>
> This also occurs if I build the extension under 5.00503
> and run in under
> 5.6.
>
> Can anyone confirm this problem and suggest a workaround?
>
> -Paul
>
RE: :ShareLite with 5.6
The following has cleared up most module problems for me- Build Perl 5.6 like so: Configure -Dbincompat5005 -Accflags=-DPERL_POLLUTE And then for modules: perl Makefile.PL POLLUTE=1 On Linux, IPC::ShareLite passes all tests using the above. -=j > -Original Message- > From: Paul G. Weiss [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, March 28, 2000 4:18 AM > To: [EMAIL PROTECTED] > Subject: IPC::ShareLite with 5.6 > > > I have been unsuccessful in building IPC::ShareLite, > which is used by HTML::Template under 5.6. Two problems: > > (1) It won't build at all w/o adding > #define PERL_POLLUTE > > before the > > #include "EXTERN.h" > #include "perl.h" > #include "XSUB.h" > > in ShareLite.xs. > > (2) After building it, test fails: > > 1..8 > ok 1 > ok 2 > ok 3 > Bad realloc() ignored at > /usrl1/home/pweiss/perl-56/lib/site_perl/5.6.0/sun4-solari s/IPC/ShareLite.pm > line 111. > Segmentation Fault (core dumped) > > > This also occurs if I build the extension under 5.00503 > and run in under > 5.6. > > Can anyone confirm this problem and suggest a workaround? > > -Paul >
RE: :ShareLite with 5.6
By the way, this is under Solaris 2.6, with none of the threading options selected in the build. -Paul > -Original Message- > From: Paul G. Weiss > Sent: Tuesday, March 28, 2000 7:18 AM > To: [EMAIL PROTECTED] > Subject: IPC::ShareLite with 5.6 > > > I have been unsuccessful in building IPC::ShareLite, > which is used by HTML::Template under 5.6. Two problems: > > (1) It won't build at all w/o adding > #define PERL_POLLUTE > > before the > > #include "EXTERN.h" > #include "perl.h" > #include "XSUB.h" > > in ShareLite.xs. > > (2) After building it, test fails: > > 1..8 > ok 1 > ok 2 > ok 3 > Bad realloc() ignored at > /usrl1/home/pweiss/perl-56/lib/site_perl/5.6.0/sun4-solaris/IP > C/ShareLite.pm > line 111. > Segmentation Fault (core dumped) > > > This also occurs if I build the extension under 5.00503 and > run in under > 5.6. > > Can anyone confirm this problem and suggest a workaround? > > -Paul >
