> -----Original Message----- > From: Jim Jagielski [mailto:j...@jagunet.com] > Sent: Dienstag, 21. Juni 2016 13:46 > To: dev@httpd.apache.org > Subject: Re: svn commit: r1748888 - > /httpd/httpd/trunk/modules/proxy/config.m4 > > 2.4.21 was pulled for a very specific reason and was fixed to > address that specific reason... The below will be in 2.4.23 for > sure. > > The question is whether or not to pull/stop 2.4.22... since this > isn't a regression per-se, I am leaning towards not unless > this issue is larger than it appears... Considering that > both trunk and 2.4 have this same build issue and that > up until now, no one has brought it up, my thoughts is > that it is not common as well.
I think as well that it is not common, but it has been brought up by a user (this was the trigger for me to investigate) and it is a regression in 2.4.x as in 2.4.20 we do not have mod_proxy_hcheck and the same configure that runs there without issue fails with 2.4.22. I guess it wasn't noticed by us prior to the user since I guess most of us build at least --enable-mods-shared=most if not more and it only pops up if you build less. Regards Rüdiger > > > On Jun 20, 2016, at 2:46 PM, Ruediger Pluem <rpl...@apache.org> wrote: > > > > > > > > On 06/20/2016 07:04 PM, William A Rowe Jr wrote: > >> Did we miss this build breakage fix in 2.4.22? > > > > I guess so, but it only should happen with --enable-mods-shared=few > which I guess is not that common. > > > > Regards > > > > Rüdiger > >
