I see that already in 2009 most of the references to "thread-safe" were
changed to talk about races instead. However the message output by
configure still says "checking for a thread-safe mkdir -p"; would it be
worth changing that too?
--
https://rrt.sc3d.org
I would like to test whether I can use C11.
I discover from git that this functionality was added in 2012 to
AC_PROG_CC, a few months after the 2.69 release.
I have a vague memory that there's a long-term plan for a major new version
of autoconf, but is there some reason why there can't be an int
On Fri, 3 Apr 2020 at 00:42, Paul Eggert wrote:
> On 4/2/20 4:14 PM, Reuben Thomas via Bug reports for autoconf wrote:
> > is there some reason why there can't be an interim release?
>
> We're working on it. I say "we" but it's mostly Zack.
>
Thank
Last night I had the baffling error "possibly undefined macro: AC_MSG_WARN".
Surely "impossibly undefined macro"!
Anyway, I was led to the following excellent analysis of the problem:
https://ae1020.github.io/undefined-macro-pkg-config/
In my case, I was briefly baffled even further, as I *had* i
On Sat, 6 Apr 2024 at 22:05, Paul Eggert wrote:
> Thanks for the suggestion. Although I didn't go to the trouble of
> writing code to generate the multiline diagnostic you suggested, it's
> easy to change "possibly undefined macro" (which doesn't cover the
> situation you mentioned) to the slight
