* configure.ac (AC_LANG_CONFTEST): Wrap the source into a AC_LANG_SOURCE
call.
---
configure.ac | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/configure.ac b/configure.ac
index 9afa81b..7d64d71 100644
--- a/configure.ac
+++ b/configure.ac
@@ -152,7 +152,8 @@ m4_include([linux/configfrag.ac])
[ssp_possible=yes]
AC_MSG_CHECKING([whether the compiler accepts `-fstack-protector'])
# Is this a reliable test case?
-AC_LANG_CONFTEST([[void foo (void) { volatile char a[8]; a[3]; }]])
+AC_LANG_CONFTEST(
+ [AC_LANG_SOURCE([[void foo (void) { volatile char a[8]; a[3]; }]])])
[# `$CC -c -o ...' might not be portable. But, oh, well... Is calling
# `ac_compile' like this correct, after all?
if eval "$ac_compile -S -fstack-protector -o conftest.s" 2> /dev/null; then]
--
1.7.5.4
