Received: (qmail 93385 invoked by uid 501); 29 Apr 2001 09:25:30 -0000
Message-Id: <20010429092530.93384.qmail@apache.org>
Date: 29 Apr 2001 09:25:30 -0000
From: Tripp Lilley <tripp+apachebug@perspex.com>
Reply-To: tripp+apachebug@perspex.com
To: submit@bugz.apache.org
Subject: ./configure uses src/Configuration.tmpl, but docs refer to src/Configuration
X-Send-Pr-Version: 3.110

>Number:         7649
>Category:       build
>Synopsis:       ./configure uses src/Configuration.tmpl, but docs refer to src/Configuration
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   apache
>Arrival-Date:   Sun Apr 29 02:30:00 PDT 2001
>Closed-Date:    Sun Apr 29 13:31:07 PDT 2001
>Last-Modified:  Sun Apr 29 13:31:07 PDT 2001
>Originator:     tripp+apachebug@perspex.com
>Release:        1.3.19
>Organization:
>Environment:
Linux charmin.eheart.sg505.net 2.2.14-15mdk #2 Sat Feb 26 21:11:44 EST 2000 i686 unknown
>Description:
Wherever docs mention hardcoding configuration options, they say to copy
src/Configuration.tmpl to src/Configuration, then edit src/Configuration with
site customizations.

However, the top-level configure script (APACI?) subverts this, reading from
src/Configuration.tmpl. Furthermore, it -appears- to ignore AddModule and
SharedModule directives, preferring its --enable-module=... directives. My
enabling of mod_so through an AddModule directive actually seems to have worked,
but the other modules, all of which I marked with "SharedModule" are still
being statically linked into the core executable.
>How-To-Repeat:
tar -xvzf apache_1.3.19.tar.gz
cd apache_1.3.19
cp src/Configuration.tmpl src/Configuration
perl -pi -e 's|^AddModule|SharedModule|' src/Configuration
perl -pi -e 's|^\# (AddModule.*/mod_so.*)$|$1|' src/Configuration
./configure --with-layout=opt
make install
/opt/apache/sbin/httpd -l

Note that output lists lots of statically linked modules, and does not
list mod_so, which we specifically enabled.
>Fix:
Reading from Configuration instead of Configuration.tmpl is trivial :) The larger
issue of recognizing AddModule and SharedModule directives from Configuration is
another matter. No clue. Sorry :)
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open-closed
State-Changed-By: slive
State-Changed-When: Sun Apr 29 13:31:07 PDT 2001
State-Changed-Why:

This behavior is by design.  If you use the "configure" script in the root directory, then you must make all changes on the configure command line (see the ./INSTALL file), and you should not touch src/Configuration.  If you edit src/Configuration, then you must use src/Configure (see src/INSTALL).

I agree this is confusing, and perhaps not well documented, but you need to be sure not to mix the two systems.  This problem has gone away in Apache httpd 2.0 since autoconf is used.

Thanks for using Apache!

>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]