RE: :ShareLite with 5.6

2000-03-28 Thread Paul G. Weiss 

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

RE: :ShareLite with 5.6

2000-03-28 Thread jason kirtland 

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