Greetings,
I have a set of custom modules that I statically compile into the httpd
binary. In the past (2.2.11), I've used something like:
./configure --with-module=custom:mod_foo.c,custom:mod_bar.c,custom:mod_baz.c
I've recently tried to port my modules to 2.2.22 but the modules.mk file
generated by configure doesn't seem to work. I tracked the the problem
down to the modules/config5.m4 line that changed from 2.2.14 to 2.2.15:
@@ -18,7 +18,7 @@ AC_ARG_WITH(module,
fi
cp $pkg $modpath_current/$modfilec
fi
- module=`echo $pkg | sed -e 's;\(.*/\)*mod_\(.*\).c;\2;'`
+ module=`echo $pkg | sed -e 's;\(.*/\).*mod_\(.*\).c;\2;'`
objects="mod_$module.lo"
# The filename of a convenience library must have a "lib" prefix:
libname="libmod_$module.la"
The associated line in CHANGES is shown here:
*) Build: fix --with-module to work as documented
PR 43881. [Gez Saunders <email removed>]
I believe the original line was to take my configure line and generate
makefile targets of the following:
libmod_foo.la: mod_foo.lo
$(MOD_LINK) mod_foo.lo
But instead I get:
libmod_mod_foo.la: mod_mod_foo.lo
$(MOD_LINK) mod_mod_foo.lo
The new sed line seems to be not matching the leading "mod_". If this
is the intended behavior, is there something I'm doing wrong here?
And as an aside, is it bad form to try and contact directly the person
who made the change?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|