On Mon, 25 Jun 2001, Stas Bekman wrote:
> 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!
>
> also notice that this will work only if your libs are binary compatible.
>
> did you make 4 symlinks? I've numbered these below as 1-4
>
> mine is:
>
> $ perl -V
>
> Characteristics of this binary (from libperl):
> Compile-time options: DEBUGGING USE_LARGE_FILES
> Built under linux
> Compiled at Apr 20 2001 22:58:59
> @INC:
> 1 /usr/lib/perl5/5.6.1/i686-linux
> 2 /usr/lib/perl5/5.6.1
> 3 /usr/lib/perl5/site_perl/5.6.1/i686-linux
> 4 /usr/lib/perl5/site_perl/5.6.1
> /usr/lib/perl5/site_perl/5.6.0
> /usr/lib/perl5/site_perl/5.005
> /usr/lib/perl5/site_perl
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...
