On Sun, 24 Jun 2001, Todd Goldenbaum wrote:
> On Sun, 24 Jun 2001, Stas Bekman wrote:
>
> > On Sun, 24 Jun 2001, Brooklyn Linux Solutions CEO wrote:
> >
> > > > > 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
> > > >
> > > I got sick of the problem and linked 5.6.1 into 5.6.0
> >
> > You could achieve the same with:
> >
> > startup.pl:
> > -----------
> > use lib qw(/usr/lib/perl5/5.6.1 /usr/lib/perl5/site_perl/5.6.1);
> >
> > note that lib.pm takes care of adding the arch lib paths (i686-linux on my
> > machine) and removing dups.
>
> interesting. I created a symlink to my 5.6.1 binary, and I am pointing to
> the 5.6.1 libraries within my PerlRequire script (in my case it's mason's
> handler.pl)... and yet, modperl is still using 5.6.0!
>
> I am really at a loss... I'm really hoping i won't have to rebuild mod_perl
> as this particular server is using a pre-built SSL version we don't want to
> break ;) but would that even help? Is sounds like it shouldn't be necessary.
check the order of paths in @INC. If 5.6.0 is coming first, that explains
your problem. try:
perl -le 'print join "\n", @INC' but this is your perl with no @INC
adjustments.
do the same from some simple CGI script
/server-status via Apache::Status is another way to check (See the guide
or the manpage)
_____________________________________________________________________
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/
