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
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
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
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
Todd,
Perl and mod_perl are separate entities altogether. Perl is the scripting
language. mod_perl is an extension to Apache, which builds a Perl
interpreter into the Apache webserver.
The binary components are mostly separate, e.g. you could theoretically
run Perl and mod_perl at different
I recommend whatever stas is saying.
Ruben
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:
Hello,
RReally
R
RI asked this question and didn't get much of an answer from folks other
Rthan they THOUGHT it was built in the perl binary.
RI recommend whatever stas is saying.
Stop being an ass, and maybe people will help you out.
Humbly,
Andrew
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:
Thanks Andrew- good stuff. You've convinced me, I'm just going to bite the
bullet and rebuild :)
todd
On Sun, 24 Jun 2001, Andrew Ho wrote:
Todd,
Perl and mod_perl are separate entities altogether. Perl is the scripting
language. mod_perl is an extension to Apache, which builds a Perl
Hi,
I am running Apache/1.3.14 (Unix) mod_perl/1.25 on a redhat 7 system. Since
the perl binary that came with the redhat distribution was version 5.6.0, I
assumed that is the version that got built into mod perl (statically linked).
But I just discovered using perl's $] variable, that it's
I am running Apache/1.3.14 (Unix) mod_perl/1.25 on a redhat 7 system.
Since the perl binary that came with the redhat distribution was version
5.6.0, I assumed that is the version that got built into mod perl
(statically linked). But I just discovered using perl's $] variable,
that it's
On Sat, 23 Jun 2001, Steven Lembark wrote:
I am running Apache/1.3.14 (Unix) mod_perl/1.25 on a redhat 7 system.
Since the perl binary that came with the redhat distribution was version
5.6.0, I assumed that is the version that got built into mod perl
(statically linked). But I just
On Sat, 23 Jun 2001, Todd Goldenbaum wrote:
Hi,
I am running Apache/1.3.14 (Unix) mod_perl/1.25 on a redhat 7 system.
Since the perl binary that came with the redhat distribution was
version 5.6.0, I assumed that is the version that got built into mod
perl (statically linked). But I just
On Sat, 23 Jun 2001, Chris Reinhardt wrote:
On Sat, 23 Jun 2001, Todd Goldenbaum wrote:
Hi,
I am running Apache/1.3.14 (Unix) mod_perl/1.25 on a redhat 7 system.
Since the perl binary that came with the redhat distribution was
version 5.6.0, I assumed that is the version that got
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 which was more or less forced on me
by cpan.
It kind of ticks me off those guys who install modules on CPAN which
upgrade by damn perl.
NET::FTP of libnet is a big culprit of this.
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
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
Ruben
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
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.
Really
I asked this question and didn't get much of an answer from folks other than
they THOUGHT it was built in the
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.
Really
I asked this question and didn't get much of an answer from folks other than
they THOUGHT it was built in the
20 matches
Mail list logo
