From 0f951f4b471567c1c2e7bd55b4b833129fe57455 Mon Sep 17 00:00:00 2001 From: "Mark J. Cox" Date: Thu, 21 Nov 1996 15:00:09 +0000 Subject: [PATCH] Change installation documentation to 1.2's way of doing it but keep link to the old stuff for people not using the beta git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@77027 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/install.html | 92 ++++++++++++++++++++++--------------- docs/manual/install.html.en | 92 ++++++++++++++++++++++--------------- 2 files changed, 108 insertions(+), 76 deletions(-) diff --git a/docs/manual/install.html b/docs/manual/install.html index 86f1429d33..fd4c7eb1b3 100644 --- a/docs/manual/install.html +++ b/docs/manual/install.html @@ -6,10 +6,15 @@ -

Compiling and Installing Apache

+

Compiling and Installing Apache 1.2

+If you wish to download and install an earlier version of Apache please +read Compiling and Installing Apache 1.1. +

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, +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. @@ -19,52 +24,63 @@ However, the server has to know which modules are compiled into it, in order for those modules to be effective; this requires generation of a short bit of code (`modules.c') which simply has a list of them.

-If you are satisfied with our standard module set, and expect to -continue to be satisfied with it, then you can just edit the stock -Makefile and compile as you have been doing previously. If you -would -like to select optional modules, however, you need to run the -configuration script. -

+It is also necessary to choose the correct options for your platform. + To do this:

    -
  1. Edit the file `Configuration'. This contains the per-machine -config settings of the Makefile, and also an additional section at -the bottom which lists the modules which have been compiled in, and -also names the files containing them. You will need to: -
      -
    1. Select a compiler and compilation options as appropriate to -your machine. -
    2. Uncomment lines corresponding to those optional modules you wish -to include (among the Module lines at the bottom of the file) -or add new lines corresponding to custom modules you have written. -

      -Note that DBM auth has to be explicitly configured in, if you want -it; just uncomment the corresponding line. -

    -
  2. Run the `Configure' script: -
    -% Configure
    -Using 'Configuration' as config file
    -%
    +
  3. +Copy the file "Configuration.tmpl" to +"Configuration" and then edit +"Configuration". This contains the list and settings of various +"Rules" and an additional section at the bottom which +lists the modules which have been compiled in, and also names the +files containing them. You will need to: +
      +

    • Adjust the Rules and EXTRA_CFLAGS|LIBS|LFLAGS|INCLUDES if + you feel so inclined. + +

    • Uncomment lines corresponding to those optional modules you wish + to include (among the Module lines at the bottom of the file), + or add new lines corresponding to custom modules you have written. + (See API.html for preliminary docs on how to do that). +

    + Note that DBM auth has to be explicitly configured in, if you want + it --- just uncomment the corresponding line. -This generates new versions of the Makefile and of modules.c. If -you want to maintain multiple configurations, you can say, e.g., -

    -% Configure -file Configuration.ai
    -Using alternate config file Configuration.ai
    -%
    -
  4. Type `make'. +

  5. Run the "Configure" script: +
    +      % Configure
    +      Using 'Configuration' as config file
    +       + configured for  platform
    +       + setting C compiler to  *
    +       + setting C compiler optimization-level to  *
    +      %
    +
    + This generates new versions of the Makefile and of modules.c. (If + you want to maintain multiple configurations, you can say, e.g., +
    +      % Configure -file Configuration.ai
    +      Using alternate config file Configuration.ai
    +       + configured for  platform
    +       + setting C compiler to  *
    +       + setting C compiler optimization-level to  *
    +      % 
    +

    +*: Depending on Configuration and your system, Configure + make not print these lines. That's OK + +

  6. Type "make".

    The modules we place in the Apache distribution are the ones we have tested and are used regularly by various members of the Apache development group. Additional modules contributed by members or third parties with specific needs or functions are available at -<URL:http://www.apache.org/dist/contrib/modules/>. There are instructions on that page for -linking these modules into the core Apache code. +. +There are +instructions on that page for linking these modules into the +core Apache code.

-

Installing Apache

After compilation, you will have a binary called `httpd' in the src/ directory. A binary distribution of Apache will supply this diff --git a/docs/manual/install.html.en b/docs/manual/install.html.en index 86f1429d33..fd4c7eb1b3 100644 --- a/docs/manual/install.html.en +++ b/docs/manual/install.html.en @@ -6,10 +6,15 @@ -

Compiling and Installing Apache

+

Compiling and Installing Apache 1.2

+If you wish to download and install an earlier version of Apache please +read Compiling and Installing Apache 1.1. +

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, +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. @@ -19,52 +24,63 @@ However, the server has to know which modules are compiled into it, in order for those modules to be effective; this requires generation of a short bit of code (`modules.c') which simply has a list of them.

-If you are satisfied with our standard module set, and expect to -continue to be satisfied with it, then you can just edit the stock -Makefile and compile as you have been doing previously. If you -would -like to select optional modules, however, you need to run the -configuration script. -

+It is also necessary to choose the correct options for your platform. + To do this:

    -
  1. Edit the file `Configuration'. This contains the per-machine -config settings of the Makefile, and also an additional section at -the bottom which lists the modules which have been compiled in, and -also names the files containing them. You will need to: -
      -
    1. Select a compiler and compilation options as appropriate to -your machine. -
    2. Uncomment lines corresponding to those optional modules you wish -to include (among the Module lines at the bottom of the file) -or add new lines corresponding to custom modules you have written. -

      -Note that DBM auth has to be explicitly configured in, if you want -it; just uncomment the corresponding line. -

    -
  2. Run the `Configure' script: -
    -% Configure
    -Using 'Configuration' as config file
    -%
    +
  3. +Copy the file "Configuration.tmpl" to +"Configuration" and then edit +"Configuration". This contains the list and settings of various +"Rules" and an additional section at the bottom which +lists the modules which have been compiled in, and also names the +files containing them. You will need to: +
      +

    • Adjust the Rules and EXTRA_CFLAGS|LIBS|LFLAGS|INCLUDES if + you feel so inclined. + +

    • Uncomment lines corresponding to those optional modules you wish + to include (among the Module lines at the bottom of the file), + or add new lines corresponding to custom modules you have written. + (See API.html for preliminary docs on how to do that). +

    + Note that DBM auth has to be explicitly configured in, if you want + it --- just uncomment the corresponding line. -This generates new versions of the Makefile and of modules.c. If -you want to maintain multiple configurations, you can say, e.g., -

    -% Configure -file Configuration.ai
    -Using alternate config file Configuration.ai
    -%
    -
  4. Type `make'. +

  5. Run the "Configure" script: +
    +      % Configure
    +      Using 'Configuration' as config file
    +       + configured for  platform
    +       + setting C compiler to  *
    +       + setting C compiler optimization-level to  *
    +      %
    +
    + This generates new versions of the Makefile and of modules.c. (If + you want to maintain multiple configurations, you can say, e.g., +
    +      % Configure -file Configuration.ai
    +      Using alternate config file Configuration.ai
    +       + configured for  platform
    +       + setting C compiler to  *
    +       + setting C compiler optimization-level to  *
    +      % 
    +

    +*: Depending on Configuration and your system, Configure + make not print these lines. That's OK + +

  6. Type "make".

    The modules we place in the Apache distribution are the ones we have tested and are used regularly by various members of the Apache development group. Additional modules contributed by members or third parties with specific needs or functions are available at -<URL:http://www.apache.org/dist/contrib/modules/>. There are instructions on that page for -linking these modules into the core Apache code. +. +There are +instructions on that page for linking these modules into the +core Apache code.

-

Installing Apache

After compilation, you will have a binary called `httpd' in the src/ directory. A binary distribution of Apache will supply this -- 2.50.1