On Sun, 24 Jun 2001, Todd Goldenbaum wrote:
> > actually yes, they appear to be in the right order:
> >
> > $ perl -V
> >
> > Characteristics of this binary (from libperl):
> > Compile-time options: USE_LARGE_FILES
> > Built under linux
> > Compiled at May 23 2001 08:18:14
> > @INC:
> > /usr/local/lib/perl5/5.6.1/i686-linux
> > /usr/local/lib/perl5/5.6.1
> > /usr/local/lib/perl5/site_perl/5.6.1/i686-linux
> > /usr/local/lib/perl5/site_perl/5.6.1
> > /usr/local/lib/perl5/site_perl
> >
> > and yet, mod perl is still showing that it's using 5.6.0...
>
> note- the results i get from a script running under mod_perl is slightly
> different, but 5.6.1 is indeed first. (this is the output of @INC)
>
> /usr/local/lib/perl5/5.6.1
> /usr/local/lib/perl5/site_perl/5.6.1
> /usr/lib/perl5/5.6.0/i386-linux
> /usr/lib/perl5/5.6.0
> /usr/lib/perl5/site_perl/5.6.0/i386-linux
> /usr/lib/perl5/site_perl/5.6.0
> /usr/lib/perl5/site_perl
>
> i may have misunderstood- were you recommending that i actually delete
> these 5.6.0 directories, and symlink them over to the 5.6.1 equivs?
It's me who wasn't clear. Of course perl -V is not what you want. I just
suggested it as an example to see what your @INC under mod_perl should be
like.
So grab the output of perl -V, and put it in
use lib qw(HERE);
in startup.pl
now make sure that 5.6.1's 4 directories are coming up first in @INC. As
you can see your output is missing i386-linux dirs for 5.6.1.
remove the symlinks.
ALso I repeat that this won't work if your 5.6.0 is binary incompatible
with 5.6.1 (which is the case if you've changed build args, like
enable/disable threads and similar).
Of course the best thing is to recompile :)
_____________________________________________________________________
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/
