# Config file for the Apache httpd.# Configuration.tmpl is the template for Configuration. Configuration should# be edited to select the modules to be included as well as various flags# for Makefile.# The template should only be changed when a new system or module is added,# or an existing one modified. This will also most likely require some minor# changes to Configure to recognize those changes.# There are 5 types of lines here:# '#' comments, distinguished by having a '#' as the first non-blank character## Makefile options, such as CC=gcc, etc...## Rules, distinguished by having "Rule" at the front. These are used to# control Configure's behavior as far as how to create Makefile.## Module selection lines, distinguished by having 'AddModule' at the front.# These list the configured modules, in priority order (highest priority# last).  They're down at the bottom.## Optional module selection lines, distinguished by having `%Module'# at the front.  These specify a module that is to be compiled in (but# not enabled).  The AddModule directive can be used to enable such a# module.  By default no such modules are defined.################################################################# Makefile configuration## These are added to the general flags determined by Configure.# Edit these to work around Configure if needed. The EXTRA_* family# will be added to the regular Makefile flags. For example, if you# want to compile with -Wall, then add that to EXTRA_CFLAGS. These# will be added to whatever flags Configure determines as appropriate# and needed for your platform.## You can also set the compiler (CC) and optimization (OPTIM) used here as# well.  Settings here have priority; If not set, Configure will attempt to# guess the C compiler, looking for gcc first, then cc.## Optimization note: # Be careful when adding optimization flags (like -O3 or -O6) on the OPTIM# entry, especially when using some GCC variants. Experience showed that using# these for compiling Apache is risky. If you don't want to see Apache dumping# core regularly then at most use -O or -O2.## The EXTRA_DEPS can be used to add extra Makefile dependencies to external# files (for instance third-party libraries) for the httpd target. The effect# is that httpd is relinked when those files are changed.#EXTRA_CFLAGS=-gEXTRA_LDFLAGS=EXTRA_LIBS=-lpthread -lg++ -ldlEXTRA_INCLUDES=-I/home/aberger/apache_gsoap.0.0.5EXTRA_DEPS=#CC=#CPP=#OPTIM=#RANLIB=################################################################# Name of the installed Apache HTTP webserver.##TARGET=################################################################# Dynamic Shared Object (DSO) support## There is experimental support for compiling the Apache core and# the Apache modules into dynamic shared object (DSO) files for# maximum runtime flexibility.## The Configure script currently has only limited built-in# knowledge on how to compile these DSO files because this is# heavily platform-dependent. The current state of supported and# explicitly unsupported platforms can be found in the file # "htdocs/manual/dso.html", under "Supported Platforms".## For other platforms where you want to use the DSO mechanism you# first have to make sure it supports the pragmatic dlopen()# system call and then you have to provide the appropriate# compiler and linker flags below to create the DSO files on your# particular platform.## The placement of the Apache core into a DSO file is triggered# by the SHARED_CORE rule below while support for building# individual Apache Modules as DSO files and loading them under# runtime without recompilation is triggered by `SharedModule'# commands. To be able to use the latter one first enable the# module mod_so (see corresponding `AddModule' command below).# Then enable the DSO feature for particular modules individually# by replacing their `AddModule' command with `SharedModule' and# change the filename extension from `.o' to `.so'. ## Sometimes the DSO files need to be linked against other shared# libraries to explicitly resolve symbols from them when the# httpd program not already contains references to them. For# instance when buidling mod_auth_db as a DSO you need to link# the DSO against the libdb explicity because the Apache kernel# has no references for this library. But the problem is that# this "chaining" is not supported on all platforms. Although one# usually can link a DSO against another DSO without linker# complains the linkage is not really done on these platforms.# So, when you receive "unresolved symbol" errors under runtime# when using the LoadModule directive for a particular module try# to enable the SHARED_CHAIN rule below.#CFLAGS_SHLIB=#LD_SHLIB=#LDFLAGS_SHLIB=#LDFLAGS_SHLIB_EXPORT=Rule SHARED_CORE=defaultRule SHARED_CHAIN=default################################################################# Rules configuration## These are used to let Configure know that we want certain# functions. The format is: Rule RULE=value## At present, only the following RULES are known: WANTHSREGEX, SOCKS4,# SOCKS5, IRIXNIS, IRIXN32, PARANOID, and DEV_RANDOM.## For all Rules except DEV_RANDOM, if set to "yes", then Configure knows# we want that capability and does what is required to add it in. If set# to "default" then Configure makes a "best guess"; if set to anything# else, or not present, then nothing is done.## SOCKS4:#  If SOCKS4 is set to 'yes', be sure that you add the socks library#  location to EXTRA_LIBS, otherwise Configure will assume#  "-L/usr/local/lib -lsocks"## SOCKS5:#  If SOCKS5 is set to 'yes', be sure that you add the socks5 library#  location to EXTRA_LIBS, otherwise Configure will assume#  "-L/usr/local/lib -lsocks5"## IRIXNIS:#  Only takes effect if Configure determines that you are running#  SGI IRIX.  If you are using a (ancient) 4.x version of IRIX, you#  need this if you are using NIS and Apache needs access to it for#  things like mod_userdir.  This is not required on 5.x and later#  and you should not enable it on such systems.## IRIXN32:#  If you are running a version of IRIX and Configure detects#  n32 libraries, it will use those instead of the o32 ones.## PARANOID:#  New with version 1.3, during Configure modules can run#  pre-programmed shell commands in the same environment that#  Configure runs in. This allows modules to control how Configure#  works. Normally, Configure will simply note that a module#  is performing this function. If PARANOID is set to yes, it will#  actually print-out the code that the modules execute## EXPAT:#  Include an Expat implementation into Apache for use by the#  modules. James Clark's Expat package (expat-lite) is bundled#  with Apache for the convenience of our users. The EXPAT rule#  determines which Expat implementation, if any, to use as follows:##  Rule EXPAT=yes       : Use system Expat if available; otherwise#                         use bundled Expat (lib/expat-lite). If#                         neither exists the build will fail#  Rule EXPAT=no        : Don't include Expat at all#  Rule EXPAT=default   : If Expat can be found at the system or#                         in lib/expat-lite, use it; otherwise#                         skip it# # CYGWIN_WINSOCK: #  Use Win32 API system calls for socket communication instead #  of Cygwin's POSIX.1 wrappers. This avoids the Cygwin specific#  implementation and uses the Win32 native calls. Should be faster#  and more reliable for high-load systems.  # Rule SOCKS4=noRule SOCKS5=noRule IRIXNIS=noRule IRIXN32=yesRule PARANOID=noRule EXPAT=defaultRule CYGWIN_WINSOCK=no # DEV_RANDOM:#  Note: this rule is only used when compiling mod_auth_digest.#  mod_auth_digest requires a cryptographically strong random seed for its#  random number generator. It knows two ways of getting this: 1) from#  a file or device (such as "/dev/random"), or 2) from the truerand#  library. If this rule is set to 'default' then Configure will choose#  to use /dev/random if it exists, else /dev/urandom if it exists,#  else the truerand library. To override this behaviour set DEV_RANDOM#  either to 'truerand' (to use the library) or to a device or file#  (e.g. '/dev/urandom'). If the truerand library is selected, Configure#  will assume "-L/usr/local/lib -lrand".Rule DEV_RANDOM=default# The following rules should be set automatically by Configure. However, if# they are not set by Configure (because we don't know the correct value for# your platform), or are set incorrectly, you may override them here.# If you have to do this, please let us know what you set and what your# platform is, by filling out a problem report form at the Apache web site:# <http://bugs.apache.org/>.  If your browser is forms-incapable, you# can get the information to us by sending mail to apache-bugs@apache.org.## WANTHSREGEX:#  Apache requires a POSIX regex implementation. Henry Spencer's#  excellent regex package is included with Apache and can be used#  if desired. If your OS has a decent regex, you can elect to#  not use this one by setting WANTHSREGEX to 'no' or commenting#  out the Rule. The "default" action is "yes" unless overruled#  by OS specificsRule WANTHSREGEX=default################################################################# Module configuration## Modules are listed in reverse priority order --- the ones that come# later can override the behavior of those that come earlier.  This# can have visible effects; for instance, if UserDir followed Alias,