No, I don't have warnings.pm. It is only included in 5.6. We have no plans
on upgrading at this time. The code snippet from PerlRun is a workaround
for perl versions prior to the most recent release, but it appears to be
causing problems with StatInc.
perl -V reports:
Summary of my perl5 (5.0 patchlevel 4 subversion 5) configuration:
It may be that the combination of PerlRun/StatInc/perl<5.6 simply will not
work. If we were not using StatInc or were using perl 5.6, I do not believe
that we would be having these problems. Unfortunately, our development
environment would be rather painful without StatInc and, as I said, we have
no plans on upgrading from 5_00405.
For now, I've got the following hack in perl.conf:
PerlModule Apache::StatINC
#
# hack to keep $INC{'warnings.pm'} defined. PerlRun includes a
# workaround for perl<5.6 which defines $INC{'warnings.pm'} and
# ties the warnings::unimport function to an anonymous sub-routine.
#
PerlInitHandler "sub {delete $INC{'warnings.pm'};
$INC{'warnings.pm'='/usr/local/lib/perl/site_perl/Apache/PerlRun.pm';}"
PerlInitHandler Apache::StatINC
PerlSetVar StatINC_UndefOnReload On
PerlSetVar StatINC_Debug 1
PerlWarn On
PerlTaintCheck On
It's not the prettiest thing, but it does what's needed.
-----Original Message-----
From: G.W. Haywood [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 08, 2000 3:00 PM
To: Chris Strom
Cc: [EMAIL PROTECTED]
Subject: Re: PerlRun StatInc perl5_00405
Hi there,
On Wed, 8 Nov 2000, Chris Strom wrote:
> The offending item in %INC appears to be the 'warnings.pm' entry
> defined on line 308 of PerlRun:
>
> BEGIN {
> if ($] < 5.006) {
> $INC{'warnings.pm'} = __FILE__;
> *warnings::unimport = sub {};
> }
> }
Do you even have the file 'warnings.pm' if you're using 5.004_05?
I have it in a 5.6.0 inststallation, but not in 5.005_03. That's
why there's a test for Perl version less than 5.006 (== 5.6.0).
What does Perl -V say?
73,
Ged..
