On 10/22/22 11:52 PM, William A Rowe Jr wrote:
> There is an alternate solution for 2.4.x that is simpler for me to offer.
>
> it could be argued that an abandoned project, deprecated in 2015, and
> entirely abandoned effective June 2021, is only supported with an explicit
> path to the pcre-co
There is an alternate solution for 2.4.x that is simpler for me to offer.
it could be argued that an abandoned project, deprecated in 2015, and
entirely abandoned effective June 2021, is only supported with an explicit
path to the pcre-config file, and that only pcre2-config would ever be
searched
The error below is acknowledged, and I worked out how it escaped my radar
(when pcre2-config exists, the current logic tolerates a broken
--with-pcre=/path,
finds the system pcre2-config or pcre-config, and if another dependency picks
the same path, the "desired" pcre is used and httpd assumes it i
