I also had this problem, but changing it to point to the pcre2-config file 
fixed it for me on RHEL 7, but...

On some operating systems this is still failing for me.  Solaris 10 is one 
example.  The configure script uses the "which" command.  On my Solaris 10 
system "which" is an actual csh script, and when run, it outputs "Processing 
<path to a .cshrc file>" in addition to the "normal" which output.

This extra output seems to be tripping up the configure script.

John
________________________________
From: Ash <[email protected]>
Sent: Monday, March 14, 2022 3:05 PM
To: [email protected] <[email protected]>
Subject: [External] : Re: [users@httpd] configure fails using --with-pcre with 
httpd-2.4.53

Thanks Yann, that was it (specifying the path to the pcre-config binary rather 
than the path to its installation directory). The build succeeds on both 
platforms now. We really appreciate the help.

> ------- Original Message -------
>
> On Monday, March 14th, 2022 at 2:06 PM, Yann Ylavic [email protected] 
> wrote:
>
> > On Mon, Mar 14, 2022 at 5:46 PM Ash [email protected] wrote:
> >
> > > Configure fails for us when building httpd-2.4.53 from source using the 
> > > --with-pcre option. The error occurs on both RHEL 8 and Solaris 11.3. A 
> > > prior release of httpd (httpd-2.4.51) builds successfully in these same 
> > > environments with the same commands.
> > >
> > > We're using apr 1.7.0, apr-util 1.6.1, PCRE 8.4.1 and OpenSSL 1.1.1l.
> > >
> > > Our configure command is:
> > >
> > > ./configure --prefix=/path/to/apache \
> > >
> > > --with-crypto --with-openssl=/path/to/ssl \
> > >
> > > --with-included-apr \
> > >
> > > --with-pcre=/path/to/pcre \
> > >
> > > --with-ssl=/path/to/ssl
> >
> > It should probably be "--with-pcre=/path/to/pcre-config", pointing to
> >
> > the pcre-config file rather than pcre the installation directory.
> >
> > Regards;
> >
> > Yann.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to