Found this bug on Autoconf 2.69
The AC_FUNC_MALLOC and AC_FUNC_REALLOC macros check for runtime
behaviors of `malloc` and `realloc` respectively. However, both checks
silently evaluate to "no" when cross-compiling.
This is a bug, because:
1. They do not emit a warning on cross-compiling mode.
Found this bug on Autoconf 2.69
The AC_FUNC_MALLOC and AC_FUNC_REALLOC macros check for runtime
behaviors of `malloc` and `realloc` respectively. However, both checks
silently evaluate to "no" when cross-compiling.
This is a bug, because:
1. They do not emit a warning on cross-compiling mode.
build_exeext to be empty, but not for $ac_build_objext.)
There's no easy workaround for users' side.
How to fix this problem other than avoiding BUILD_OBJEXT and BUILD_EXEEXT
altogether?
Thank you.
Kang-Che Sung
This bug is a funny one, I think.
In flex (lexer) configure.ac, I use "dnl" comments within
AC_CHECK_FUNCS for inline notes, like this:
#
AC_CHECK_FUNCS([dnl
pow dnl Used only by "examples/manual/expr"
setlocale dnl Needed only if NLS is enabled
Allow me to re-describe the bug in a clearer way:
In the configure.ac in Flex (lexer) project, I used a quoted argument with
"dnl" comments in within AC_CHECK_FUNCS like this:
AC_CHECK_FUNCS([dnl
pow dnl Used only by "examples/manual/expr"
setlocale dnl Needed only if NLS is enabled
On Fri, Feb 23, 2018 at 3:59 AM, Eric Blake <ebl...@redhat.com> wrote:
> On 02/21/2018 08:07 PM, Kang-Che Sung wrote:
>>
>> This bug is a funny one, I think.
>>
>> In flex (lexer) configure.ac, I use "dnl" comments with