Re: Problem on RedHat Enterprise 3.0

[prev] [thread] [next] [Date index for 2005/01/20]

Instead of mv'ing your Apache lib, couldn't you not include it  and 
just stipulate the libs you want to use in the startup.pl script?

Jay Scherrer

On Wednesday 19 January 2005 03:27 pm, Aaron Hawryluk wrote:
> I didn't get the full text of this message, but if the apache
> modules aren't loading right and this is a mod_perl 1.99 install on
> Apache2, I just had the exact same problem... mod_perl simply
> wouldn't load.  There were all kinds of complaints from perl about
> how various Apache:: and ModPerl:: modules couldn't be found...
> Turned out to be a conflict between the site_perl and vendor_perl
> libraries.  It was fixed by the following:
>
> mv /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/Apache
> /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/Apache.bak
>
> This causes the search for the Apache modules to default to
> vendor_perl instead of site.  Fixes it nicely.  May confuse CPAN,
> though I haven't checked yet.
>
> My problem?  My company is actually paying for a RHEL service
> contract, and they have neither detected nor patched this issue
> yet.  Ah, if only we could've gone with Fedora...
>
> -----Original Message-----
> From: Jay Scherrer [mailto:jay@xxxxxxxx.xxx]
> Sent: Wednesday, January 19, 2005 4:01 PM
> To: modperl@xxxx.xxxxxx.xxx
> Subject: Re: Problem on RedHat Enterprise 3.0
>
> Darren Young,
>
> Have you checked to see if Apache::RequestRec was installed?
> Try CPANing the installation of Bundle::Apache.  It looks like your
> mod_perl is looking for the Lib ok but it's not installed.
>
>
> Jay Scherrer
>
> On Wednesday 19 January 2005 12:58 pm, Young, Darren wrote:
> > Apache::RequestRec