www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tripp Lilley <tripp+apache...@perspex.com>
Subject build/7649: ./configure uses src/Configuration.tmpl, but docs refer to src/Configuration
Date Sun, 29 Apr 2001 09:25:30 GMT

>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:          open
>Class:          doc-bug
>Submitter-Id:   apache
>Arrival-Date:   Sun Apr 29 02:30:00 PDT 2001
>Originator:     tripp+apachebug@perspex.com
>Release:        1.3.19
Linux charmin.eheart.sg505.net 2.2.14-15mdk #2 Sat Feb 26 21:11:44 EST 2000 i686 unknown
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.
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.
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 :)
 [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!     ]

View raw message