You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@perl.apache.org by barries <ba...@slaysys.com> on 2001/04/24 20:14:40 UTC

Minor patch to modperl_dev.pod

Well, I got mod_perl installed & tested as recommended in
modperl_dev.pod, and I thought I'd try to make it a little easier for
others. I'm not sure if I've overlooked something that would have made
it easier for me, however, and I presonally can't say why I think 5.6.1
won't cut it, I'm passing on a remark by Stas.

- Barrie

--- modperl_dev.pod.orig	Tue Apr 24 13:45:13 2001
+++ modperl_dev.pod	Tue Apr 24 14:01:16 2001
@@ -22,13 +22,25 @@
    --with-mpm=threaded --enable-so
  % make && make install
 
-For bleeding edge Perl:
+For bleeding edge Perl (5.6.1 won't cut it, sorry):
 
  % rsync -auvz rsync://ftp.linux.activestate.com/perl-current/ perl-current
  % cd perl-current
  % ./Configure -des -Dprefix=$HOME/bleedperl \
    -Dusethreads -Doptimize='-g' -Dusedevel
  % make && make test && make install
+ % ln $HOME/bleedperl/bin/perl5.x.x $HOME/bleedperl/bin/perl
+ % PATH=$HOME/bleedperl/bin:$PATH
+
+You'll also want to install (at least) LWP into the bleedperl/lib
+directory if you want to fully test mod_perl.  To do this,
+make sure bleedperl/bin/perl exists and can be found in your PATH,
+then do:
+ 
+ % perl -MCPAN -e 'install("LWP")'
+
+Note that a privately installed bleedperl won't find libraries installed in
+the normal places; it only looks in it's own lib tree.
 
 =head1 Compiling
 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org


Re: Minor patch to modperl_dev.pod

Posted by Stas Bekman <st...@stason.org>.
On Tue, 24 Apr 2001, barries wrote:

> Well, I got mod_perl installed & tested as recommended in
> modperl_dev.pod, and I thought I'd try to make it a little easier for
> others. I'm not sure if I've overlooked something that would have made
> it easier for me, however, and I presonally can't say why I think 5.6.1
> won't cut it, I'm passing on a remark by Stas.

Thanks, Barrie

> --- modperl_dev.pod.orig	Tue Apr 24 13:45:13 2001
> +++ modperl_dev.pod	Tue Apr 24 14:01:16 2001
> @@ -22,13 +22,25 @@
>     --with-mpm=threaded --enable-so
>   % make && make install
>
> -For bleeding edge Perl:
> +For bleeding edge Perl (5.6.1 won't cut it, sorry):

It works now.

>   % rsync -auvz rsync://ftp.linux.activestate.com/perl-current/ perl-current
>   % cd perl-current
>   % ./Configure -des -Dprefix=$HOME/bleedperl \
>     -Dusethreads -Doptimize='-g' -Dusedevel
>   % make && make test && make install
> + % ln $HOME/bleedperl/bin/perl5.x.x $HOME/bleedperl/bin/perl
> + % PATH=$HOME/bleedperl/bin:$PATH

you don't want to do that. This is bleed perl, you want to explicitly use
a full path, when you want it.

> +You'll also want to install (at least) LWP into the bleedperl/lib
> +directory if you want to fully test mod_perl.  To do this,
> +make sure bleedperl/bin/perl exists and can be found in your PATH,
> +then do:
> +
> + % perl -MCPAN -e 'install("LWP")'
> +
> +Note that a privately installed bleedperl won't find libraries installed in
> +the normal places; it only looks in it's own lib tree.
>
>  =head1 Compiling
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
> For additional commands, e-mail: dev-help@perl.apache.org
>



_____________________________________________________________________
Stas Bekman              JAm_pH     --   Just Another mod_perl Hacker
http://stason.org/       mod_perl Guide  http://perl.apache.org/guide
mailto:stas@stason.org   http://apachetoday.com http://eXtropia.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org