Attached are two files: a much abbreviated INSTALL and a revamp of install.html. Here is what my goals were:
INSTALL is a just a pointer to the real install docs with a very basic quickstart guide for people who have nothing but an xterm to work with. I removed most of the ./configure documentation because it was either obsolete or not functional because of bugs in httpd-2.0. I documented only the most basic things that people need to get things going, and that I could verify actually work. I do not think that this is at all complete, or even necessarily completely accurate, but I hope it is a good base for future work. In addition, I think that it is MUCH more useful than what is there for people actually trying to get 2.0 up and running. I will commit install.html unless I see major objections. By major objections I mean either 1. You think what is already there is better than this; or 2. You think this is heading in the wrong direction completely. I am also very interested in input on how to improve this, but I plan to commit it as is and then do improvements later. That way, others can take a crack at it too. I do not have the karma to commit INSTALL, so I would appreciate it if someone could take care of that for me. -- Joshua Slive [EMAIL PROTECTED] http://slive.ca/ Phone: (604) 822-1871
QUICK AND DIRTY APACHE INSTALLATION For full installation documentation, see docs/manual/install.html or http://httpd.apache.org/docs-2.0/install.html Overview for the impatient -------------------------- $ ./configure --prefix=PREFIX $ make $ make install $ PREFIX/bin/apachectl start NOTES: * 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. * If you are building on FreeBSD, you should add the argument --with-mpm=prefork to the configure line. The Apache Group has discovered that threads do not work well with Apache on FreeBSD. For that reason, we disable threads by default on FreeBSD, and you need to build the prefork MPM. If you wish to try to make threads work on FreeBSD, they can be re-enabled by using --enable-threads * If you are a developer using the CVS version of Apache, you will need to run ./buildconf before anything else. The easiest way to find all of the configuration flags for Apache 2.0 is to run ./configure --help. Thanks for using the Apache HTTP Server, Version 2.0. The Apache Software Foundation http://www.apache.org/Title: Compiling and Installing Apache
Compiling and InstallingThis document covers compilation and installation of Apache on Unix and Unix-like systems only. For compiling and installation on Windows, see Using Apache with Microsoft Windows. For other platforms, see the platform documentation. Apache 2.0's configuration and installation environment has changed completely from Apache 1.3. Apache 1.3 used a custom set of scripts to achieve easy installation. Apache 2.0 now uses libtool and autoconf to create an environment that looks like many other Open Source projects. Overview for the impatient
NN must be replaced with the current minor version number,
and PREFIX must be replaced with the filesystem path under
which the server should be installed. If PREFIX is not
specified, it defaults to Each section of the compilation and installation process is described in more detail below, beginning with the requirements for compiling and installing Apache HTTPD. RequirementsThe following requirements exist for building Apache:
DownloadApache can be downloaded from the Apache Software Foundation download site or from a nearby mirror. Version numbers that end in After downloading, especially if a mirror site is used, it is
important to verify that you have a complete and unmodified version
of the Apache HTTP Server. This can be accomplished by testing the
downloaded tarball against the PGP signature, which should always be
obtained from the main
Apache website. The signature file has a filename identical to
the source tarball with the addition of ExtractExtracting the source from the Apache HTTPD tarball is a simple matter of uncompressing, and then untarring: This will create a new directory under the current directory
containing the source code for the distribution. You should
Configuring the source treeThe next step is to configure the Apache source tree for your
particular platform and personal requirements. This is done using the
script To configure the source tree using all the default options, simply
type 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_speling for later loading through the DSO mechanism: When configure is run it will take several minutes to test for the availability of features on your system and build Makefiles which will later be used to compile the server. The easiest way to find all of the configuration flags for Apache is to run ./configure --help. What follows is a brief description of most of the arguments and environment variables. Environment VariablesThe autoconf build process uses several environment variables to
configure the build environment. In general, these variables change
the method used to build Apache, but not the eventual features of the
server. These variables can be placed in the environment before
invoking
autoconf Output Options
PathnamesThere are currently two ways to configure the pathnames under which Apache will install its files. First, you can specify a directory and have Apache install itself under that directory in its default locations.
It is possible to specify that architecture-dependent files should be placed under a different directory.
The second, and more flexible way to configure the install path
locations for Apache is using the
Presently it is not possible to mix the
ModulesApache 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 list of modules included in the documentation. Those modules with a status 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. There are two ways for a module to be compiled and used with
Apache. Modules may be statically compiled, which means that
they are permanently included in the Apache binary. Alternatively, if
your operating system supports Dynamic Shared Objects (DSOs) and
autoconf can detect that support, then modules may be dynamically
compiled. 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 mod_so. 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 actually compiling any dynamic modules, you can
explicitly
In addition to the standard set of modules, Apache 2.0 also
includes a choice of Multi-Processing Modules
(MPMs). One, and only one MPM must be included in the compilation
process. The default MPMs for each platform are listed on the MPM documentation page, but can be overridden
on the
SuexecApache includes a support program called suexec 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 suexec documentation before implementing this feature. Building the packageNow you can build the various parts which form the Apache package by simply running the command: 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. Installing the packageNow its time to install the package under the configured
installation PREFIX (see If you are upgrading, the installation will not overwrite your configuration files or documents. Customizing the packageNext, you can customize your Apache HTTP server by editing the configuration files under PREFIX/conf/. Have a look at the Apache manual under docs/manual/ or http://httpd.apache.org/docs/ for a complete reference of available configuration directives. Testing the packageNow you can start your Apache HTTP server by immediately running: and then you should be able to request your first document via URL
http://localhost/ (when you built and installed Apache as root) or
http://localhost:8080/ (when you built and installed Apache as a
regular user). The web page you see is located under the DocumentRoot which will usually
be |
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
