Jim Meyering <[EMAIL PROTECTED]> writes:
> Simon Josefsson <[EMAIL PROTECTED]> wrote:
> MinGW apparently needs gnulib's memcmp module
That was rather surprising to me, so I started investigating why that is
the case.
>>>
>>> The reason was that Autoconf's AC_FUNC_MEMCMP uses AC_
Simon Josefsson <[EMAIL PROTECTED]> wrote:
MinGW apparently needs gnulib's memcmp module
>>>
>>> That was rather surprising to me, so I started investigating why that is
>>> the case.
>>
>> The reason was that Autoconf's AC_FUNC_MEMCMP uses AC_RUN_IFELSE with a
>> cross-compile default of no.
Simon Josefsson wrote:
> The patch below works in the sense that, for cross-compilations only, it
> will assume that memcmp works when it is declared. This works better
> for MinGW.
This is good. It's the usual approach we take for cross-compiles in gnulib:
Put in the known cases into the autocon
Simon Josefsson <[EMAIL PROTECTED]> writes:
> Simon Josefsson <[EMAIL PROTECTED]> writes:
>
>> Simon Josefsson <[EMAIL PROTECTED]> writes:
>>
>>> MinGW apparently needs gnulib's memcmp module
>>
>> That was rather surprising to me, so I started investigating why that is
>> the case.
>
> The reason
Simon Josefsson <[EMAIL PROTECTED]> writes:
> Simon Josefsson <[EMAIL PROTECTED]> writes:
>
>> MinGW apparently needs gnulib's memcmp module
>
> That was rather surprising to me, so I started investigating why that is
> the case.
The reason was that Autoconf's AC_FUNC_MEMCMP uses AC_RUN_IFELSE wi
