From 59f0c22ed2b131cac16446d6bcc3d5da1d09e120 Mon Sep 17 00:00:00 2001
From: Joseph Myers <joseph@codesourcery.com>
Date: Mon, 21 May 2012 23:26:27 +0000
Subject: Filter out unknown symbols in stack-protector test.

---
 configure.in | 7 +++++++
 1 file changed, 7 insertions(+)

(limited to 'configure.in')

diff --git a/configure.in b/configure.in
index a9ee7334d6..38b55a6784 100644
--- a/configure.in
+++ b/configure.in
@@ -2072,6 +2072,13 @@ libc_undefs=`$NM -u conftest.o |
   AC_MSG_ERROR([confusing output from $NM -u])
 }
 echo >&AS_MESSAGE_LOG_FD "libc_undefs='$libc_undefs'"
+# On some architectures, there are architecture-specific undefined
+# symbols (resolved by the linker), so filter out unknown symbols.
+# This will fail to produce the correct result if the compiler
+# defaults to -fstack-protector but this produces an undefined symbol
+# other than __stack_chk_fail.  However, compilers like that have not
+# been encountered in practice.
+libc_undefs=`echo "$libc_undefs" | egrep '^(foobar|__stack_chk_fail)$'`
 case "$libc_undefs" in
 foobar) libc_cv_predef_stack_protector=no ;;
 '__stack_chk_fail
-- 
cgit 1.4.1