FYI, the news section on https://savannah.gnu.org/projects/autoconf/
mentions the release of autoconf 2.70 as "Latest News"
Thats outdated since autoconf 2.71 was released...
--
Bye bye ... Detlef
Hi Team.
I saw yestereday late evening, that a new release is planed,
and i found, that my patch is still waiting.
As suggested by Sam today, i will send it to the autoconf-patches,
when i'm home in the evening
Thanks Sam for the ping.
:thumbsup:
--
bye bye Detlef
Hi autoconf team.
During testing of tcc 0.9.28rc,
I found a strange bug in autoconf 2.71 with `AC_CHECK_DEFINE` for `__unix__`.
For comparsion, i added checks for "__unix" and "__linux__":
Overview:
* [__unix__] always found, but the log text is crippled
* __unix__ never found and the log text
Thanks Nick and Peter for your analysis.
Yes, the "AC_" prefix fooled me, that AC_CHECK_DEFINE belongs to autoconf.
> On 2023-09-23, Nick Bowler wrote:
> > On 2023-09-23, Detlef Riekenberg wrote:
> >> AC_CHECK_DEFINE(__unix, CFLAGS="-DFOUND__unix $CFLAG
> > On 24/9/23 11:03, Nick Bowler wrote:
> >> The word AC_CHECK_DEFINE is not found anywhere in the Autoconf
> >> source code or documentation.
> >
> > My guess would be that the 3rd party is the autoconf archive because
> > they provide both AX_CHECK_DEFINE and AC_CHECK_DEFINE
> >
> > http://git.s
Hi Christoph.
Some hints about your draft application:
> > Where is your open source technology project being used (describe
> > all user bases)?
>
> GNU Autoconf and GNU Automake are part of the GNU Autotools, also known
> as the GNU Build System. The help making source code packages portable
