perl-docs-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From s...@apache.org
Subject cvs commit: modperl-docs/src/docs/2.0/user/intro start_fast.pod
Date Fri, 05 Sep 2003 01:54:15 GMT
stas        2003/09/04 18:54:15

  Modified:    src/docs/2.0/user/install install.pod
               src/docs/2.0/user/intro start_fast.pod
  Log:
  most people want to use the MP_APXS when building mod_perl, so mention
  that option first
  
  Revision  Changes    Path
  1.47      +37 -28    modperl-docs/src/docs/2.0/user/install/install.pod
  
  Index: install.pod
  ===================================================================
  RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/install/install.pod,v
  retrieving revision 1.46
  retrieving revision 1.47
  diff -u -u -r1.46 -r1.47
  --- install.pod	3 Sep 2003 18:05:19 -0000	1.46
  +++ install.pod	5 Sep 2003 01:54:14 -0000	1.47
  @@ -271,39 +271,48 @@
   Like any other Perl module, mod_perl is configured via the
   I<Makefile.PL> file, but requires one or more configuration options:
   
  +  % cd modperl-1.99_xx
     % perl Makefile.PL <options>
   
  -where I<options> is an optional list of (key,value) pairs.  Usually
  -you need to use only the C<L<MP_AP_PREFIX|/MP_AP_PREFIX>> option to
  -complete the build. This and other options are discussed in the
  -following sections.
  -
  -If all Apache 2.0 files were installed under the same directory,
  -mod_perl 2.0's build only needs to know the path to that directory,
  -passed via the C<L<MP_AP_PREFIX|/MP_AP_PREFIX>> option:
  -
  -  % cd modperl-2.0
  -  % perl Makefile.PL MP_AP_PREFIX=$HOME/httpd/prefork \
  -    MP_INST_APACHE2=1
  -
  -XXX: MP_INST_APACHE2=1 should become the default, but for now add it
  -too.
  -
  -However if the Apache 2.0 files are spread under different locations,
  -which is the case on many distributions that provide the binary Apache
  -2.0 package, other options may need to be provided. For example RedHat
  -Linux system installs the httpd binary, the apxs and apr-config
  -scripts all in different locations, therefore they configure mod_perl
  -2.0 as:
  +where I<options> is an optional list of (key,value) pairs.
   
  -  % perl Makefile.PL MP_APXS=/path/to/apxs \
  +The following sections give the details about all the available
  +options, but let's mention first the most important ones.
  +
  +If you want to have mod_perl 1.0 and 2.0 installed under the same perl
  +tree you need to enable C<L<MP_INST_APACHE2|/MP_INST_APACHE2>>:
  +
  +  % perl Makefile.PL MP_INST_APACHE2=1 <other options>
  +
  +It seems that most users use pre-packaged Apache installation, most of
  +which tend to spread the Apache files across many directories
  +(i.e. not using --enable-layout=Apache, which puts all the files under
  +the same directory). If Apache 2.0 files are spread under different
  +directories, you need to use at least the C<L<MP_APXS|/MP_APXS>>
  +option, which should be set to a full path to the C<apxs>
  +executable. For example:
  +
  +  % perl Makefile.PL MP_INST_APACHE2=1 MP_APXS=/path/to/apxs
  +
  +For example RedHat Linux system installs the C<httpd> binary, the
  +C<apxs> and C<apr-config> scripts (the latter two are needed to build
  +mod_perl) all in different locations, therefore they configure
  +mod_perl 2.0 as:
  +
  +  % perl Makefile.PL MP_INST_APACHE2=1 MP_APXS=/path/to/apxs \
       MP_APR_CONFIG=/another/path/to/apr-config <other options>
   
  -In this case there is no need to specify the
  -C<L<MP_AP_PREFIX|/MP_AP_PREFIX>> option, since paths to the scripts
  -specified by C<L<MP_APXS|/MP_APXS>> and
  -C<L<MP_APR_CONFIG|/MP_APR_CONFIG>> can be used to retrieve the rest of
  -the information.
  +However a correctly built Apache shouldn't require the
  +C<L<MP_APR_CONFIG|/MP_APR_CONFIG>> option, since
  +C<L<MP_APXS|/MP_APXS>> should provide the location of this script.
  +
  +If however all Apache 2.0 files were installed under the same
  +directory, mod_perl 2.0's build only needs to know the path to that
  +directory, passed via the C<L<MP_AP_PREFIX|/MP_AP_PREFIX>> option:
  +
  +  % perl Makefile.PL MP_INST_APACHE2=1 MP_AP_PREFIX=$HOME/httpd/prefork
  +
  +These and other options are discussed in the following sections.
   
   =head3 Boolean Build Options
   
  
  
  
  1.16      +1 -2      modperl-docs/src/docs/2.0/user/intro/start_fast.pod
  
  Index: start_fast.pod
  ===================================================================
  RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/intro/start_fast.pod,v
  retrieving revision 1.15
  retrieving revision 1.16
  diff -u -u -r1.15 -r1.16
  --- start_fast.pod	18 Aug 2003 19:16:34 -0000	1.15
  +++ start_fast.pod	5 Sep 2003 01:54:15 -0000	1.16
  @@ -30,8 +30,7 @@
   
     % tar -xvzf mod_perl-2.x.xx.tar.gz
     % cd modperl-2.0
  -  % perl Makefile.PL MP_AP_PREFIX=$HOME/httpd/prefork \
  -    MP_INST_APACHE2=1
  +  % perl Makefile.PL MP_APXS=$HOME/httpd/prefork/bin/apxs MP_INST_APACHE2=1
   
   where C<MP_AP_PREFIX> is an Apache installation prefix, under which
   the I<include/> directory with Apache C header files can be found.
  
  
  

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


Mime
View raw message