diff options
author | Joshua Slive <slive@apache.org> | 2002-08-15 14:49:54 +0000 |
---|---|---|
committer | Joshua Slive <slive@apache.org> | 2002-08-15 14:49:54 +0000 |
commit | 7f0145baa659a41669b2d0a4a75eedddc2f8f216 (patch) | |
tree | d13082ca4af0239a6c8b8aa732e80a49762f6845 /docs/manual/install.html.en | |
parent | f6e9bd544573cbe0b3abe6d87c374bfbba08d180 (diff) | |
download | httpd-7f0145baa659a41669b2d0a4a75eedddc2f8f216.tar.gz |
New XML.
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@96379 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'docs/manual/install.html.en')
-rw-r--r-- | docs/manual/install.html.en | 283 |
1 files changed, 94 insertions, 189 deletions
diff --git a/docs/manual/install.html.en b/docs/manual/install.html.en index be9eaaf4ae..050e8706fc 100644 --- a/docs/manual/install.html.en +++ b/docs/manual/install.html.en @@ -1,26 +1,13 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" - "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> - -<html xmlns="http://www.w3.org/1999/xhtml"> - <head> - <meta name="generator" content="HTML Tidy, see www.w3.org" /> - - <title>Compiling and Installing Apache</title> - </head> - <!-- Background white, links blue (unvisited), navy (visited), red (active) --> - - <body bgcolor="#FFFFFF" text="#000000" link="#0000FF" - vlink="#000080" alink="#FF0000"> - <!--#include virtual="header.html" --> - - <h1 align="center">Compiling and Installing</h1> +<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --><title>Compiling and Installing - Apache HTTP Server</title><link href="./style/manual.css" type="text/css" rel="stylesheet"></head><body><blockquote><div align="center"><img src="./images/sub.gif" alt="[APACHE DOCUMENTATION]"><h3>Apache HTTP Server Version 2.0</h3></div><h1 align="center">Compiling and Installing</h1> <p>This document covers compilation and installation of Apache on Unix and Unix-like systems only. For compiling and - installation on Windows, see <a - href="platform/windows.html">Using Apache with Microsoft - Windows</a>. For other platforms, see the <a - href="platform/">platform</a> documentation.</p> + installation on Windows, see <a href="platform/windows.html">Using Apache with Microsoft + Windows</a>. For other platforms, see the <a href="platform/">platform</a> documentation.</p> <p>Apache 2.0's configuration and installation environment has changed completely from Apache 1.3. Apache 1.3 used a custom @@ -28,43 +15,9 @@ uses libtool and autoconf to create an environment that looks like many other Open Source projects.</p> - <ul> - <li><a href="#overview">Overview for the impatient</a></li> - - <li><a href="#requirements">Requirements</a></li> - - <li><a href="#download">Download</a></li> - - <li><a href="#extract">Extract</a></li> - - <li> - <a href="#configure">Configuring the source tree</a> - - <ul> - <li><a href="#environment">Environment Variables</a></li> - - <li><a href="#output">autoconf Output Options</a></li> - - <li><a href="#pathnames">Pathnames</a></li> - - <li><a href="#modules">Modules</a></li> - - <li><a href="#suexec">Suexec</a></li> - </ul> - </li> - - <li><a href="#compile">Build</a></li> - - <li><a href="#install">Install</a></li> - - <li><a href="#customize">Customize</a></li> - - <li><a href="#test">Test</a></li> - </ul> - <hr /> - - <h3><a id="overview" name="overview">Overview for the - impatient</a></h3> +<ul><li><a href="#overview">Overview for the + impatient</a></li><li><a href="#requirements">Requirements</a></li><li><a href="#download">Download</a></li><li><a href="#extract">Extract</a></li><li><a href="#configure">Configuring the source tree</a><ul><li><a href="#environment">Environment Variables</a></li><li><a href="#output">autoconf Output Options</a></li><li><a href="#pathnames">Pathnames</a></li><li><a href="#modules">Modules</a></li><li><a href="#suexec">Suexec</a></li></ul></li><li><a href="#compile">Build</a></li><li><a href="#install">Install</a></li><li><a href="#customize">Customize</a></li><li><a href="#test">Test</a></li></ul><hr><h2><a name="overview">Overview for the + impatient</a></h2> <table> <tr> @@ -78,7 +31,7 @@ <tr> <td><a href="#extract">Extract</a></td> - <td><code>$ gzip -d httpd-2_0_<em>NN</em>.tar.gz<br /> + <td><code>$ gzip -d httpd-2_0_<em>NN</em>.tar.gz<br> $ tar xvf httpd-2_0_<em>NN</em>.tar</code> </td> </tr> @@ -124,57 +77,50 @@ <p>Each section of the compilation and installation process is described in more detail below, beginning with the requirements for compiling and installing Apache HTTPD.</p> - - <h3><a id="requirements" - name="requirements">Requirements</a></h3> +<h2><a name="requirements">Requirements</a></h2> <p>The following requirements exist for building Apache:</p> <ul> - <li>Disk Space<br /> - <br /> + <li>Disk Space<br> + <br> Make sure you have at least 50 MB of temporary free disk space available. After installation Apache occupies approximately 10 MB of disk space. The actual disk space requirements will vary considerably based on your chosen - configuration options and any third-party modules.<br /> - <br /> + configuration options and any third-party modules.<br> + <br> </li> - <li>ANSI-C Compiler and Build System<br /> - <br /> - Make sure you have an ANSI-C compiler installed. The <a - href="http://www.gnu.org/software/gcc/gcc.html">GNU C - compiler (GCC)</a> from the <a - href="http://www.gnu.org/">Free Software Foundation (FSF)</a> + <li>ANSI-C Compiler and Build System<br> + <br> + Make sure you have an ANSI-C compiler installed. The <a href="http://www.gnu.org/software/gcc/gcc.html">GNU C + compiler (GCC)</a> from the <a href="http://www.gnu.org/">Free Software Foundation (FSF)</a> is recommended (version 2.7.2 is fine). If you don't have GCC then at least make sure your vendor's compiler is ANSI compliant. In addition, your <code>PATH</code> must contain - basic build tools such as <code>make</code>.<br /> - <br /> + basic build tools such as <code>make</code>.<br> + <br> </li> - <li>Accurate time keeping<br /> - <br /> + <li>Accurate time keeping<br> + <br> Elements of the HTTP protocol are expressed as the time of day. So, it's time to investigate setting some time synchronization facility on your system. Usually the ntpdate or xntpd programs are used for this purpose which are based on the Network Time Protocol (NTP). See the Usenet newsgroup - <a - href="news:comp.protocols.time.ntp">comp.protocols.time.ntp</a> + <a href="news:comp.protocols.time.ntp">comp.protocols.time.ntp</a> and the <a href="http://www.eecis.udel.edu/~ntp/">NTP homepage</a> for more details about NTP software and public - time servers.<br /> - <br /> + time servers.<br> + <br> </li> <li><a href="http://www.perl.org/">Perl 5</a> - [OPTIONAL]<br /> - <br /> - For some of the support scripts like <a - href="programs/apxs.html">apxs</a> or <a - href="programs/dbmmanage.html">dbmmanage</a> (which are + [OPTIONAL]<br> + <br> + For some of the support scripts like <a href="programs/apxs.html">apxs</a> or <a href="programs/dbmmanage.html">dbmmanage</a> (which are written in Perl) the Perl 5 interpreter is required (versions 5.003 and 5.004 are fine). If no such interpreter is found by the `configure' script there is no harm. Of course, you still @@ -183,17 +129,14 @@ installed (perhaps a Perl 4 from the vendor and a Perl 5 from your own), then it is recommended to use the --with-perl option (see below) to make sure the correct one is selected - by ./configure.<br /> - <br /> + by ./configure.<br> + <br> </li> </ul> +<h2><a name="download">Download</a></h2> - <h3><a id="download" name="download">Download</a></h3> - - <p>Apache can be downloaded from the <a - href="http://www.apache.org/dist/httpd/">Apache Software - Foundation download site</a> or from a <a - href="http://www.apache.org/dyn/closer.cgi/httpd/">nearby + <p>Apache can be downloaded from the <a href="http://www.apache.org/dist/httpd/">Apache Software + Foundation download site</a> or from a <a href="http://www.apache.org/dyn/closer.cgi/httpd/">nearby mirror</a>.</p> <p>Version numbers that end in <code>alpha</code> indicate @@ -210,8 +153,7 @@ version of the Apache HTTP Server. This can be accomplished by testing the downloaded tarball against the PGP signature. This, in turn, is a two step procedure. First, you must obtain the - <code>KEYS</code> file from the <a - href="http://www.apache.org/dist/httpd/">Apache distribution + <code>KEYS</code> file from the <a href="http://www.apache.org/dist/httpd/">Apache distribution site</a>. (To assure that the <code>KEYS</code> file itself has not been modified, it may be a good idea to use a file from a previous distribution of Apache or import the keys from a @@ -219,39 +161,29 @@ key ring using one of the following commands (depending on your pgp version):</p> - <blockquote> - <code>$ pgp < KEYS</code> - </blockquote> - or +<blockquote><table cellpadding="10"><tr><td bgcolor="#eeeeee"><code>$ pgp < KEYS</code></td></tr></table></blockquote> - <blockquote> - <code>$ gpg --import KEYS</code> - </blockquote> + <p>or </p> + +<blockquote><table cellpadding="10"><tr><td bgcolor="#eeeeee"><code>$ gpg --import KEYS</code></td></tr></table></blockquote> <p>The next step is to test the tarball against the PGP - signature, which should always be obtained from the <a - href="http://www.apache.org/dist/httpd/">main Apache + signature, which should always be obtained from the <a href="http://www.apache.org/dist/httpd/">main Apache website</a>. The signature file has a filename identical to the source tarball with the addition of <code>.asc</code>. Then you can check the distribution with one of the following commands (again, depending on your pgp version):</p> - <blockquote> - <code>$ pgp httpd-2_0_<em>NN</em>.tar.gz.asc</code> - </blockquote> - or +<blockquote><table cellpadding="10"><tr><td bgcolor="#eeeeee"><code>$ pgp httpd-2_0_<em>NN</em>.tar.gz.asc</code></td></tr></table></blockquote> + + <p>or</p> - <blockquote> - <code>$ gpg --verify httpd-2_0_<em>NN</em>.tar.gz.asc</code> - </blockquote> - You should receive a message like<br /> - <br /> - +<blockquote><table cellpadding="10"><tr><td bgcolor="#eeeeee"><code>$ gpg --verify httpd-2_0_<em>NN</em>.tar.gz.asc</code></td></tr></table></blockquote> + + <p>You should receive a message like</p> - <blockquote> - <code>Good signature from user "Martin Kraemer - <martin@apache.org>".</code> - </blockquote> +<blockquote><table cellpadding="10"><tr><td bgcolor="#eeeeee"><code>Good signature from user "Martin Kraemer + <martin@apache.org>".</code></td></tr></table></blockquote> <p>Depending on the trust relationships contained in your key ring, you may also receive a message saying that the @@ -259,23 +191,21 @@ be verified. This is not a problem if you trust the authenticity of the <code>KEYS</code> file.</p> - <h3><a id="extract" name="extract">Extract</a></h3> +<h2><a name="extract">Extract</a></h2> <p>Extracting the source from the Apache HTTPD tarball is a simple matter of uncompressing, and then untarring:</p> - <blockquote> - <code>$ gzip -d httpd-2_0_<em>NN</em>.tar.gz<br /> - $ tar xvf httpd-2_0_<em>NN</em>.tar</code> - </blockquote> +<blockquote><table cellpadding="10"><tr><td bgcolor="#eeeeee"><code> + $ gzip -d httpd-2_0_<em>NN</em>.tar.gz<br> + $ tar xvf httpd-2_0_<em>NN</em>.tar +</code></td></tr></table></blockquote> <p>This will create a new directory under the current directory containing the source code for the distribution. You should <code>cd</code> into that directory before proceeding with compiling the server.</p> - - <h3><a id="configure" name="configure">Configuring the source - tree</a></h3> +<h2><a name="configure">Configuring the source tree</a></h2> <p>The next step is to configure the Apache source tree for your particular platform and personal requirements. This is @@ -304,12 +234,12 @@ the two additional modules mod_rewrite and mod_speling for later loading through the DSO mechanism:</p> - <blockquote> - <code>$ CC="pgcc" CFLAGS="-O2" \<br /> - ./configure --prefix=/sw/pkg/apache \<br /> - --enable-rewrite=shared \<br /> - --enable-speling=shared</code> - </blockquote> +<blockquote><table cellpadding="10"><tr><td bgcolor="#eeeeee"><code> + $ CC="pgcc" CFLAGS="-O2" \<br> + ./configure --prefix=/sw/pkg/apache \<br> + --enable-rewrite=shared \<br> + --enable-speling=shared +</code></td></tr></table></blockquote> <p>When configure is run it will take several minutes to test for the availability of features on your system and build @@ -320,8 +250,7 @@ description of most of the arguments and environment variables.</p> - <h4><a id="environment" name="environment">Environment - Variables</a></h4> +<h3><a name="environment">Environment Variables</a></h3> <p>The autoconf build process uses several environment variables to configure the build environment. In general, these @@ -384,8 +313,8 @@ compiler and linker.</dd> </dl> - <h4><a id="output" name="output">autoconf Output - Options</a></h4> + +<h3><a name="output">autoconf Output Options</a></h3> <dl> <dt><code>--help</code></dt> @@ -404,7 +333,8 @@ process, including the names of all the files examined.</dd> </dl> - <h4><a id="pathnames" name="pathnames">Pathnames</a></h4> + +<h3><a name="pathnames">Pathnames</a></h3> <p>There are currently two ways to configure the pathnames under which Apache will install its files. First, you can @@ -458,16 +388,15 @@ should edit the <code>config.layout</code> file and use the <code>--enable-layout</code> option.</p> - <h4><a id="modules" name="modules">Modules</a></h4> + +<h3><a name="modules">Modules</a></h3> <p>Apache is a modular server. Only the most basic functionality is included in the core server. Extended features are available in various modules. During the configuration process, you must select which modules to compile for use with - your server. You can view a <a - href="mod/index.html">list of modules</a> included in - the documentation. Those modules with a <a - href="mod/module-dict.html#Status">status</a> of "Base" are + your server. You can view a <a href="mod/index.html">list of modules</a> included in + the documentation. Those modules with a <a href="mod/module-dict.html#Status">status</a> of "Base" are included by default and must be specifically disabled if you do not want them. Modules with any other status must be specifically enabled if you wish to use them.</p> @@ -480,7 +409,7 @@ modules may be <em>dynamically compiled</em>. DSO modules are stored separately from the Apache binary, and may be included or excluded from the server using the run-time configuration - directives provided by <a href="mod/mod_so.html">mod_so</a>. + directives provided by <code><a href="./mod/mod_so.html">mod_so</a></code>. The mod_so is automatically included in the server if any dynamic modules are included in the compilation. If you would like to make your server capable of loading DSOs without @@ -491,8 +420,7 @@ <dt><code>--enable-<em>MODULE</em>[=shared]</code></dt> <dd>Compile and include the module <em>MODULE</em>. The - identifier <em>MODULE</em> is the <a - href="mod/module-dict.html#ModuleIdentifier">Module + identifier <em>MODULE</em> is the <a href="mod/module-dict.html#ModuleIdentifier">Module Identifier</a> from the module documentation without the "_module" string. To compile the module as a DSO, add the option <code>=shared</code>.</dd> @@ -521,15 +449,11 @@ space-separated list of module identifiers. For example, to enable mod_dav and mod_info, you can either use</p> - <blockquote> - <code>./configure --enable-dav --enable-info</code> - </blockquote> +<blockquote><table cellpadding="10"><tr><td bgcolor="#eeeeee"><code>./configure --enable-dav --enable-info</code></td></tr></table></blockquote> <p>or, equivalently,</p> - <blockquote> - <code>./configure --enable-modules="dav info"</code> - </blockquote> +<blockquote><table cellpadding="10"><tr><td bgcolor="#eeeeee"><code>./configure --enable-modules="dav info"</code></td></tr></table></blockquote> <p>In addition, the special keywords <code>all</code> or <code>most</code> can be used to add all or most of the modules @@ -538,10 +462,10 @@ For example, to include all modules as DSOs with the exception of mod_info, you can use</p> - <blockquote> - <code>./configure --enable-mods-shared=all - --disable-info</code> - </blockquote> +<blockquote><table cellpadding="10"><tr><td bgcolor="#eeeeee"><code> + ./configure --enable-mods-shared=all + --disable-info +</code></td></tr></table></blockquote> <p>In addition to the standard set of modules, Apache 2.0 also includes a choice of <a href="mpm.html">Multi-Processing @@ -557,78 +481,59 @@ <dd>Choose the mpm <em>NAME</em>.</dd> </dl> - <h4><a id="suexec" name="suexec">Suexec</a></h4> - <p>Apache includes a support program called <a - href="suexec.html">suexec</a> which can be used to isolate user +<h3><a name="suexec">Suexec</a></h3> + + <p>Apache includes a support program called <a href="suexec.html">suexec</a> which can be used to isolate user CGI programs. However, if suexec is improperly configured, it can cause serious security problems. Therefore, you should carefully read and consider the <a href="suexec.html">suexec documentation</a> before implementing this feature.</p> - <h3><a id="compile" name="compile">Build</a></h3> +<h2><a name="compile">Build</a></h2> <p>Now you can build the various parts which form the Apache package by simply running the command:</p> - <blockquote> - <code>$ make</code> - </blockquote> +<blockquote><table cellpadding="10"><tr><td bgcolor="#eeeeee"><code>$ make</code></td></tr></table></blockquote> <p>Please be patient here, since a base configuration takes approximately 3 minutes to compile under a Pentium III/Linux 2.2 system, but this will vary widely depending on your hardware and the number of modules which you have enabled.</p> - - <h3><a id="install" name="install">Install</a></h3> +<h2><a name="install">Install</a></h2> <p>Now its time to install the package under the configured installation <em>PREFIX</em> (see <code>--prefix</code> option above) by running:</p> - <blockquote> - <code>$ make install</code> - </blockquote> +<blockquote><table cellpadding="10"><tr><td bgcolor="#eeeeee"><code>$ make install</code></td></tr></table></blockquote> <p>If you are upgrading, the installation will not overwrite your configuration files or documents.</p> - - <h3><a id="customize" name="customize">Customize</a></h3> +<h2><a name="customize">Customize</a></h2> <p>Next, you can customize your Apache HTTP server by editing the <a href="configuring.html">configuration files</a> under <em>PREFIX</em>/conf/.</p> - <blockquote> - <code>$ vi <em>PREFIX</em>/conf/httpd.conf</code> - </blockquote> +<blockquote><table cellpadding="10"><tr><td bgcolor="#eeeeee"><code>$ vi <em>PREFIX</em>/conf/httpd.conf</code></td></tr></table></blockquote> - <p>Have a look at the Apache manual under <a - href="./">docs/manual/</a> or <a - href="http://httpd.apache.org/docs/">http://httpd.apache.org/docs/</a> - for a complete reference of available <a - href="mod/directives.html">configuration directives</a>.</p> - - <h3><a id="test" name="test">Test</a></h3> + <p>Have a look at the Apache manual under <a href="./">docs/manual/</a> or <a href="http://httpd.apache.org/docs/">http://httpd.apache.org/docs-2.0/</a> + for a complete reference of available <a href="mod/directives.html">configuration directives</a>.</p> +<h2><a name="test">Test</a></h2> <p>Now you can <a href="invoking.html">start</a> your Apache HTTP server by immediately running:</p> - <blockquote> - <code>$ <em>PREFIX</em>/bin/apachectl start</code> - </blockquote> +<blockquote><table cellpadding="10"><tr><td bgcolor="#eeeeee"><code>$ <em>PREFIX</em>/bin/apachectl start</code></td></tr></table></blockquote> <p>and then you should be able to request your first document via URL http://localhost/. The web page you see is located - under the <a href="mod/core.html#documentroot">DocumentRoot</a> + under the <a href="./mod/core.html#documentroot" class="directive"><code class="directive">DocumentRoot</code></a> which will usually be <code><em>PREFIX</em>/htdocs/</code>. Then <a href="stopping.html">stop</a> the server again by running:</p> - <blockquote> - <code>$ <em>PREFIX</em>/bin/apachectl stop</code> - </blockquote> - <!--#include virtual="footer.html" --> - </body> -</html> - +<blockquote><table cellpadding="10"><tr><td bgcolor="#eeeeee"><code>$ <em>PREFIX</em>/bin/apachectl stop</code></td></tr></table></blockquote> +<hr></blockquote><h3 align="center">Apache HTTP Server Version 2.0</h3><a href="./"><img src="./images/index.gif" alt="Index"></a><a href="./"><img src="./images/home.gif" alt="Home"></a></body></html>
\ No newline at end of file |