[sr #110530] Missing #include <string.h> in AC_FUNC_MEMCMP

[Zack Weinberg]

Follow-up Comment #8, sr #110530 (project autoconf):

This whole discussion has gotten way off into the weeds.

It's true that everything that uses the C version of AC_LANG_CALL or
AC_LANG_FUNC_LINK_TRY is broken by any compiler that defaults to [the
equivalent of] -Werror=implicit-function-declaration (or
-Werror=strict-prototypes, for that matter).  And fixing that "properly" (by
arranging for Autoconf to know which header to include for each library
function) is going to be enough work that it might make sense to use
-Wno-error=implicit-function-declaration -Wno-error=strict-prototypes as a
stopgap.

However, *none* of that should affect AC_FUNC_MEMCMP, because it *doesn't* use
either of those, and string.h is (or should be) automatically included via
AC_INCLUDES_DEFAULT.  Something else must be wrong.  Can we please keep this
bug report focused on the originally reported problem?

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/support/?110530>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/