As noted, from how I understand it, currently we allow it to build BUT the behavior is not as expected or designed, since the expected behavior *requires* PCRE_DUPNAMES. If we require PCRE_DUPNAMES then we require it, right?
On Mar 19, 2014, at 12:26 PM, Plüm, Rüdiger, Vodafone Group <[email protected]> wrote: > > >> -----Original Message----- >> From: Jim Jagielski > Sent: Mittwoch, 19. März 2014 16:37 >> To: httpd >> Subject: Re: svn commit: r1554300 - in /httpd/httpd/trunk: CHANGES >> include/ap_mmn.h include/ap_regex.h include/http_core.h >> modules/proxy/mod_proxy.c modules/proxy/mod_proxy.h server/core.c >> server/request.c server/util_pcre.c >> >> As I understand it, we require PCRE_DUPNAMES functionality, right? >> So I think we need to check for it at configure/build time >> and bail if it isn't available. >> >> The configure part is done in >> >> http://svn.apache.org/r1579259 >> > > Keep in mind that this causes trunk to fail building on RHEL 5 with the > system provided PCRE >
