Return-Path: Delivered-To: apmail-httpd-docs-archive@httpd.apache.org Received: (qmail 78731 invoked by uid 500); 4 Feb 2002 11:49:16 -0000 Mailing-List: contact docs-help@httpd.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: docs@httpd.apache.org Delivered-To: mailing list docs@httpd.apache.org Received: (qmail 78709 invoked by uid 500); 4 Feb 2002 11:49:16 -0000 Delivered-To: apmail-apache-docs@apache.org Delivered-To: apmail-httpd-docs-1.3-cvs@apache.org Date: 4 Feb 2002 11:49:16 -0000 Message-ID: <20020204114916.9113.qmail@icarus.apache.org> From: rbowen@apache.org To: httpd-docs-1.3-cvs@apache.org Subject: cvs commit: httpd-docs-1.3/htdocs/manual install.html.en X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N rbowen 02/02/04 03:49:16 Modified: htdocs/manual install.html.en Log: Cover both installation methods in this doc. Much of the stuff in INSTALL made it into this. This is for 1.3 only, as this got done for 2.0 some time ago. Reviewed by: Joshua Slive Revision Changes Path 1.35 +259 -41 httpd-docs-1.3/htdocs/manual/install.html.en Index: install.html.en =================================================================== RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/install.html.en,v retrieving revision 1.34 retrieving revision 1.35 diff -u -r1.34 -r1.35 --- install.html.en 2 Oct 2001 11:02:58 -0000 1.34 +++ install.html.en 4 Feb 2002 11:49:16 -0000 1.35 @@ -9,50 +9,249 @@ - +

Compiling and Installing Apache 1.3

-

This document covers compilation and installation of Apache - on Unix systems, using the manual build and install method. If - you wish to use the autoconf-style configure interface, you - should instead read the INSTALL file in the root directory of - the Apache source distribution. For compiling and installation - on specific platforms, see

- + +

This document covers compilation and installation of Apache on Unix + systems. For compiling and installation on other platforms, see

+ -
  • Using Apache with Novell Netware - 5
  • +

    Downloading Apache

    -
  • Using Apache with HP MPE/iX
  • +

    You may download the latest version of Apache either directly from the + Apache web site, at http://www.apache.org/dist/httpd/, + or from one of the many mirror sites, listed at http://www.apache.org/dyn/closer.cgi. + These sites will list the current release, and more recent beta releases, + and have links to older versions, and binary distributions for a variety + of platforms.

    + +

    Introduction

    + +

    Like all good things, there are two ways to configure, compile, and + install Apache. You can go for the 3-minute installation process using + the APACI process described below; or, you can opt for the same mechanism + used in previous versions of Apache, as described in the file + 'src/INSTALL'. Each mechanism has its benefits and drawbacks - APACI is + newer and a little more raw, but it gets you up and running the least + amount of time, whereas the "Configuration.tmpl" mechanism may be more + familiar and give you some more flexibility to the power user. We'd be + very interested in your comments and feedback regarding each + approach.

    -
  • Compiling Apache under - UnixWare
  • +

    Installing the Apache 1.3 HTTP server with + APACI

    -
  • Overview of the Apache TPF - Port
  • - +

    Overview for the impatient

    +
      +     $ ./configure --prefix=PREFIX
      +     $ make
      +     $ make install
      +     $ PREFIX/bin/apachectl start
      +
    + +

    NOTE: PREFIX is not the string "PREFIX". Instead + use the Unix filesystem path under which Apache should be installed. For + instance use "/usr/local/apache" for PREFIX above.

    + +

    Requirements

    + +

    The following requirements exist for building Apache:

    + +
    +
    Disk Space:
    + +
    Make sure you have approximately 12 MB of temporary free disk space + available. After installation Apache occupies approximately 3 MB of + disk space (the actual required disk space depends on the amount of + compiled in third party modules, etc).
    + +
    ANSI-C Compiler:
    + +
    Make sure you have an ANSI-C compiler installed. The GNU C compiler + (GCC) from the Free Software Foundation (FSF) is recommended (version + 2.7.2 is fine). If you don't have GCC then at least make sure your + vendors compiler is ANSI compliant. You can find the homepage of GNU at + http://www.gnu.org/ and the GCC distribution under + http://www.gnu.org/order/ftp.html .
    + +
    Perl 5 Interpreter [OPTIONAL]:
    + +
    For some of the support scripts like `apxs' or `dbmmanage' (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 APACI's + `configure' script this is no harm. Of course, you still can build and + install Apache 1.3. Only those support scripts cannot be used. If you + have multiple Perl interpreters 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 APACI.
    + +
    Dynamic Shared Object (DSO) support [OPTIONAL]:
    + +
    +

    To provide maximum flexibility Apache now is able to load modules + under runtime via the DSO mechanism by using the pragmatic + dlopen()/dlsym() system calls. These system calls are not available + under all operating systems therefore you cannot use the DSO + mechanism on all platforms. And Apache currently has only limited + built-in knowledge on how to compile shared objects because this is + heavily platform-dependent. The current state is this:

    + +
      +
    • + Out-of-the-box supported platforms are: + +

      + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
      LinuxSunOSUnixWareDarwin/Mac OS
      FreeBSDSolarisAIXOpenStep/Mach
      OpenBSDIRIXSCODYNIX/ptx
      NetBSDHPUXReliantUNIXBSDI
      Digital UnixDGUX
      +

      +
    • + +
    • + Entirely unsupported platforms are: + +

      Ultrix

      +
    • +
    + +

    If your system is not on these lists but has the dlopen-style + interface, you either have to provide the appropriate compiler and + linker flags (see CFLAGS_SHLIB, LDFLAGS_SHLIB and + LDFLAGS_SHLIB_EXPORT below) manually or at least make sure a Perl 5 + interpreter is installed from which Apache can guess the options.

    + +

    For more in-depth information about DSO support in Apache 1.3 + please read the document htdocs/manual/dso.html carefully. Especially + the section entitled "Advantages & Disadvantages" because using + the DSO mechanism can have strange side-effects if you are not + carefully. BE WARNED!

    +
    +
    + +

    Configuring the source tree

    + +

    The next step is to configure the Apache source tree for your + particular platform and personal requirements. The most important setup + here is the location prefix where Apache is to be installed later, + because Apache has to be configured for this location to work correctly. + But there are a lot of other options available for your pleasure.

    + +

    For a short impression of what possibilities you have, here is a + typical example which compiles Apache for the installation tree + /sw/pkg/apache with a particular compiler and flags plus the two + additional modules mod_rewrite and mod_proxy for later loading through + the DSO mechanism:

    +
      +     $ CC="pgcc" OPTIM="-O2" \
      +       ./configure --prefix=/usr/local/apache \
      +                   --enable-module=rewrite --enable-shared=rewrite \
      +                   --enable-module=proxy   --enable-shared=proxy
      +
    + +

    For a complete list of the available options, type the following + command:

    +

    ./configure --help

    + +

    See also the file README.configure for listings of + example configurations.

    + +

    Building the package

    + +

    Now you can build the various parts which form the Apache package by + simply running the command

    +
      +        $ make 
      +
    + +

    Please be patient here, this takes approximately 2 minutes to complete + under a Pentium-166/FreeBSD-2.2 system, dependent on the amount of + modules you have enabled.

    + +

    Installing the package

    + +

    Now its time to install the package under the configured installation + PREFIX (see the --prefix option above):

    +
      +        $ make install
      +
    -

    Downloading Apache

    - Information on the latest version of Apache can be found on the - Apache web server at http://www.apache.org/. This - will list the current release, any more recent beta-test - release, together with details of mirror web and anonymous ftp - sites. - -

    If you downloaded a binary distribution, skip to Installing Apache. Otherwise read the next - section for how to compile the server.

    +

    In the following examples, PREFIX is not the literal string + "PREFIX", but whatever argument you provided to + the--prefix option.

    + + + +

    Building and installing Apache in the traditional way

    + + Before the advent of APACI, there was just one way to build and + install Apache. While APACI gave a configuration interface which is + more familiar to some people, the older method gives a way to + configure the installation without typing a large number of + command-line options. + +

    Configuring the installation

    -

    Compiling Apache

    Compiling Apache consists of three steps: Firstly select which Apache modules you want to include into the server. Secondly create a configuration for your operating @@ -123,6 +322,8 @@ Configure -file Configuration.ai).

    +

    Compiling Apache

    +
  • Type make.
  • The modules we place in the Apache distribution are the ones we @@ -134,7 +335,7 @@ There are instructions on that page for linking these modules into the core Apache code. -

    Installing Apache

    +

    Installing Apache

    You will have a binary file called httpd in the src directory. A binary distribution of Apache will supply this file. @@ -180,14 +381,7 @@ .htaccess files in directories accessed by the server.

    -

    Set your system time properly!

    - Proper operation of a public web server requires accurate time - keeping, since elements of the HTTP protocol are expressed as - the time of day. So, it's time to investigate setting up NTP or - some other time synchronization system on your Unix box, or - whatever the equivalent on NT would be. - -

    Compiling Support Programs

    +

    Compiling Support Programs

    In addition to the main httpd server which is compiled and configured as above, Apache includes a number of support programs. These are not compiled by default. The @@ -197,7 +391,31 @@
           make
       
    - + +

    Testing the package

    + +

    Now you can fire up your Apache HTTP server by immediately running

    +
      +        $ PREFIX/bin/apachectl start
      +
    + +

    and then you should be able to request your first document via URL + http://localhost/ (when you built and installed Apache as root or at + least used the --without-confadjust option) or http://localhost:8080/ + (when you built and installed Apache as a regular user). Then stop the + server again by running:

    +
      +        $ PREFIX/bin/apachectl stop
      +
    + +

    Set your system time properly!

    + Proper operation of a public web server requires accurate time + keeping, since elements of the HTTP protocol are expressed as + the time of day. So, it's time to investigate setting up NTP or + some other time synchronization system on your Unix box, or + the net time command on NT. + + --------------------------------------------------------------------- To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org For additional commands, e-mail: docs-help@httpd.apache.org