[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[patch #9900] New AX_CHECK_PCRE2

From: anonymous
Subject: [patch #9900] New AX_CHECK_PCRE2
Date: Mon, 7 Jun 2021 15:14:30 -0400 (EDT)
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.1.1 Safari/605.1.15

Follow-up Comment #4, patch #9900 (project autoconf-archive):

[comment #3 comment #3:]
> Added to the archive in 1ce158d78a281e7be9bf495c0b5f1d193142a130. Thank you
very much for the submission.

Thank you! Today I ran into a very strange problem, which I do not understand.
This problem may not be necessarily related to the AX_CHECK_PCRE2 submission.
I just don't know why this happens even after years of using autoconf.

My has:

[echo "sorry, PCRE2 is not usable"]

Then running autoheader produces a with the PCRE2 entry. Nice.

But with this minor change:

[echo "using PCRE2"],
[echo "sorry, PCRE2 is not usable"]

running autoheader does NOT add a PCRE2 entry to This means that
all builds fail after autoconf and when the user executes ./configure.

I've looked into this, but can't figure out what is going on with autoheader.
Perhaps other users will run into this bug with autoheader or with

- Robert


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]