httpd-apreq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Winstead <j...@trainedmonkey.com>
Subject Re: prepared 0.32 for release
Date Tue, 03 Apr 2001 19:27:13 GMT
On Tue, Apr 03, 2001 at 12:43:29PM -0500, Randy Kobes wrote:
> On Tue, 3 Apr 2001, Doug MacEachern wrote:
> > you mean not including the core dump it triggers? ;)
> > 
> > if PerlIO is defined, PerlIO_importFILE will be available as a function,
> > but it was being redefined.  this patch fixes for me..
> > 
> 
> I don't have access to my Win32 machine at the moment, but
> when I was looking at this before, without the
> 
>  #ifndef PerlIO_importFILE
>  #define PerlIO_importFILE(fp,flags) ((FILE *)fp)
>  #endif
> 
> I got an error about PerlIO_importFILE not being found - this 
> was with ActivePerl 623, which has the defines for multi-thread.
> On a self-compiled Win32 perl without multi-thread, it found
> PerlIO_importFILE OK, without the need for this check. 
> At the time I thought it related to PERL_IMPLICIT_SYS being defined 
> for ActivePerl - if instead of the above check I put at the top 
> of Request.xs
> 
> #undef PERL_IMPLICIT_SYS
> 
> then PerlIO_importFILE was found OK on ActivePerl.

so what's the verdict? my system is way too vanilla for this
problem. obviously the define of PerlIO_importFILE is wrong (and
i backed it out). is just undefining PERL_IMPLICIT_SYS going to be
safe, or will there need to be a more esoteric check for activeperl?

jim

Mime
View raw message