@mhsmith, would you like to review this?

@corona10, feel free to take a look at this, if you have the time.

@mhsmith, thanks for the review; I addressed your remarks in 9c3596d. PTAL.

Found the culprit; typo on my end! ✅

Now, there's one more thing we should add before landing this: support configure cache.

Now, there's one more thing we should add before landing this: support configure cache.

I'm not sure we want to automatically generate the cache variable name in this macro. The first argument would need heavy string modifications to end up as a usable identifier. Perhaps it is best to introduce a new param for the cache variable name.

Alternatively, all but one usage of PY_CHECK_CPP could be replaced with AX_CHECK_DEFINE, which has caching already built in.

Alternatively, all but one usage of PY_CHECK_CPP could be replaced with AX_CHECK_DEFINE, which has caching already built in.

That's a good suggestion; I'll have a look in a day or two.

UPDATE: Created alternative PR gh-116016.

Alternatively, all but one usage of PY_CHECK_CPP could be replaced with AX_CHECK_DEFINE, which has caching already built in.

For the glibc check; do we really need to worry about glibc < 2.1?

I agree, so #116016 looks like the way to go.

Superseded by #116016