> > 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
> >
> >
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 $CFLAGS")
> >> AC_CHECK_DEFINE(__unix__,
On 24/09/2023, Peter Johansson wrote:
> Hi Detlef and Nick,
>
> 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
Hi,
On 2023-09-23, Detlef Riekenberg wrote:
> During testing of tcc 0.9.28rc,
> I found a strange bug in autoconf 2.71 with `AC_CHECK_DEFINE` for
> `__unix__`.
The word AC_CHECK_DEFINE is not found anywhere in the Autoconf
source code or documentation.
So I am afraid it is a bit difficult to
On 2023-09-23, Nick Bowler wrote:
> On 2023-09-23, Detlef Riekenberg wrote:
>> AC_CHECK_DEFINE(__unix, CFLAGS="-DFOUND__unix $CFLAGS")
>> AC_CHECK_DEFINE(__unix__, CFLAGS="-DFOUND__unix__ $CFLAGS")
>> AC_CHECK_DEFINE(__linux__, CFLAGS="-DFOUND__linux__ $CFLAGS")
[...]
> So it sounds like there
Hi Detlef and Nick,
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
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
