> It's got to be built in. My mod_perl conf keeps looking in 5.6.0 in the @INC
> array even after the 5.6.1 upgrade
Rebuild mod_perl or add the 5.6.1 paths to @INC in startup.pl via use lib:
http://perl.apache.org/guide/install.html#Should_I_Rebuild_mod_perl_if_I_h
> which was more or less forced on me
> by cpan.
Yeah, it's a known bug, has been fixed lately.
> It kind of ticks me off those guys who install modules on CPAN which
> upgrade by damn perl.
Configure CPAN.pm to 'ask' rather than 'follow'.
I was aborting the fetch of 5.6.1 manually by punching Ctrl-C a few times.
> NET::FTP of libnet is a big culprit of this.
>
> Ruben
>
>
> > gotcha. so it's 5.6.0... however i'm still really curious about whether
> > mod_perl 'builds in' the interpreter when you build apache, or is it when
> > you >run< apache?
> >
> > what i'm actually trying to do is get mod_perl to use a different version
> > of perl also installed on my system, 5.6.1, so as to settle some problems
> > within mason causing the httpd child processes to segfault.
> >
> >
> >
>
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:[EMAIL PROTECTED] http://apachetoday.com http://eXtropia.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
