httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralf S. Engelschall" <...@engelschall.com>
Subject Re: [patch] ./configure --activate-module bugfix
Date Sat, 28 Aug 1999 14:49:54 GMT

In article <000401bef0f2$4ac79be0$0500a8c0@delf> you wrote:
 
> I just ran into an interesting bug in the configure script.
> The --activate-module option does not work correctly with the --enable-shared
> option.
> 
> In my configuration I had:
> 
> ./configure \
> --activate-module=src/modules/extra/mod_frontpage.c \
> --enable-shared=frontpage

Errr... actually it was never intended that you specify the _source_, David.
It was intended that you specify the path as it would be on the AddModule
line, i.e. with mod_foo.o or libfoo.o. We can accept .c, of course.  But
whether it makes the situation better, I don't know. Perhaps it would be
better to document it more carefully in INSTALL?

So, +0 for the patch and +1 for only or additionally the following patch:

Index: INSTALL
===================================================================
RCS file: /e/apache/REPOS/apache-1.3/INSTALL,v
retrieving revision 1.59
diff -u -r1.59 INSTALL
--- INSTALL	1999/08/09 07:38:32	1.59
+++ INSTALL	1999/08/28 14:49:11
@@ -240,14 +240,14 @@
      process.
  
      Use the --activate-module=FILE option to add an entry for an existing
-     module source file into the configuration file on-the-fly. FILE has to be
-     a valid path beginning with "src/modules/", and the file has to have been
-     copied to this location in the Apache source tree before running
-     configure.  The module is automatically enabled. Use this option to
-     automatically include a complex third-party module to the Apache build
-     process where, for instance a module like mod_perl or mod_php3 consisting
-     of more than one file which are created by a third-party configuration
-     scheme.
+     module object or library file into the configuration file on-the-fly.
+     FILE has to be a valid path beginning with "src/modules/", and the
+     corresponding file has to have been copied to this location in the Apache
+     source tree before running configure.  The module is automatically
+     enabled. Use this option to automatically include a complex third-party
+     module to the Apache build process where, for instance a module like
+     mod_perl or mod_php3 consisting of more than one file which are created
+     by a third-party configuration scheme.
  
      Use the --enable-module=NAME and --disable-module=NAME options to enable
      or disable a particular already distributed module from the Apache

                                       Ralf S. Engelschall
                                       rse@engelschall.com
                                       www.engelschall.com

Mime
View raw message