From eca102fd503aed642cbb8d64fcc1a2e3a24422be Mon Sep 17 00:00:00 2001 From: Tommi Rantala Date: Fri, 31 Aug 2012 11:53:53 +0300 Subject: [PATCH] Remove AC_FUNC_MEMCMP check from configure.in As far as I can tell, AC_FUNC_MEMCMP is useless for us. It checks for some obscure `memcmp' bugs on some ancient systems, and gives us a chance to provide a working `memcmp'. Since we're not shipping with a local copy of a `memcmp', it makes no difference whether or not the test fails. And when cross-compiling, the test automatically fails, as it tries to compile and run a test program: checking for working memcmp... no Quoting autoconf docs: ``This macro is obsolescent, as current systems have a working memcmp. New programs need not use this macro.'' --- configure.in | 1 - 1 file changed, 1 deletion(-) diff --git a/configure.in b/configure.in index 0a7577b6..2caceffe 100644 --- a/configure.in +++ b/configure.in @@ -68,7 +68,6 @@ PT_STEP, PT_SYSCALL], [], [], ]) dnl Checks for library functions. -AC_FUNC_MEMCMP AC_CHECK_FUNCS(dl_iterate_phdr dl_phdr_removals_counter dlmodinfo getunwind \ ttrace mincore) is_gcc_m64() {