On Wed, Jun 22, 2016 at 10:20 AM, William A Rowe Jr <wr...@rowe-clan.net>
wrote:

>
> Attached /was/ a patch, now attached again...
>

This patch solves the 80/20... but I'm seeing something disturbing
comparing the
original to the new logic in the new configure output from buildconf...
something
that does not occur with mod_ssl or mod_ldap, which follow the same pattern;

$ diff -u3 configure.orig configure | more
--- configure.orig 2016-06-22 13:36:58.719342545 -0500
+++ configure 2016-06-22 13:37:18.047758290 -0500
@@ -21588,10 +21588,6 @@
   proxy_mods_enable=most
 fi

-if test "$proxy_mods_enable" = "no"; then
-  enable_proxy_hcheck=no
-fi
-
 proxy_objs="mod_proxy.lo proxy_util.lo"

   { $as_echo "$as_me:${as_lineno-$LINENO}: checking whether to enable
mod_proxy
" >&5
@@ -23327,7 +23323,11 @@
 if test "${enable_proxy_hcheck+set}" = set; then :
   enableval=$enable_proxy_hcheck; force_proxy_hcheck=$enableval
 else
-  enable_proxy_hcheck=$enable_proxy_hcheck
+  enable_proxy_hcheck=$proxy_mods_enable
+      if test "$enable_watchdog" = "no"; then
+    enable_proxy_hcheck="";
+  fi
+
 fi

     _apmod_extra_msg=""
@@ -23374,7 +23374,15 @@
   if test "$enable_proxy_hcheck" != "no"; then
             { $as_echo "$as_me:${as_lineno-$LINENO}: result: checking
dependenc
ies" >&5
 $as_echo "checking dependencies" >&6; }
-            if test "$enable_watchdog" = "no" ; then
+            if test "$enable_proxy" = "no" ; then
+                              enable_proxy_hcheck=no
+                              { $as_echo "$as_me:${as_lineno-$LINENO}:
WARNING:
 \"mod_proxy is disabled but required for mod_proxy_hcheck\"" >&5
+$as_echo "$as_me: WARNING: \"mod_proxy is disabled but required for
mod_proxy_h
check\"" >&2;}
+                            elif test "$enable_proxy_hcheck" = "static" &&
test
 "$enable_proxy" != "static" ; then
+                              enable_proxy_hcheck=no
+                              { $as_echo "$as_me:${as_lineno-$LINENO}:
WARNING:
 \"cannot build mod_proxy_hcheck statically if mod_proxy is built shared\""
>&5
+$as_echo "$as_me: WARNING: \"cannot build mod_proxy_hcheck statically if
mod_pr
oxy is built shared\"" >&2;}
+                            elif test "$enable_watchdog" = "no" ; then
                               enable_proxy_hcheck=no
                               { $as_echo "$as_me:${as_lineno-$LINENO}:
WARNING:
 \"mod_watchdog is disabled but required for mod_proxy_hcheck\"" >&5
 $as_echo "$as_me: WARNING: \"mod_watchdog is disabled but required for
mod_prox
y_hcheck\"" >&2;}
@@ -23410,7 +23418,12 @@
       sharedobjs=yes
       shared=yes
       DSO_MODULES="$DSO_MODULES proxy_hcheck"
-      if test "$enable_proxy_hcheck" = "yes" ; then
+      if test "
+  $proxy_mods_enable
+      if test "$enable_watchdog" = "no"; then
+    enable_proxy_hcheck="";
+  fi
+" = "yes" ; then
         ENABLED_DSO_MODULES="${ENABLED_DSO_MODULES},proxy_hcheck"
       fi
       ;;

That last stanza is nonsense.

I'm coming to the conclusion that modules/proxy/config.m4 made a fatal error
in not providing the typical no|most|all schema defaults, and that this
resulted
in the obscure behavior in the last stanza.

Have a couple things to wrap up, but I'm coming back to this in about 2 hrs,
and can hopefully isolate why this unique behavior occurs in proxy, but not
in ssl or ldap APACHE_MODULE results.

Reply via email to