diff options
author | Guillem Jover <guillem@hadrons.org> | 2011-08-25 15:22:26 +0200 |
---|---|---|
committer | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2011-08-27 00:24:38 +0200 |
commit | 46ad4fdca1644288025a41e43cc2784c216861d2 (patch) | |
tree | 505f575ba4dc7e35af5e9b0b4cc0bfc1f9781a2c | |
parent | e89791ef14fd7944a7dd1dfd557f1e33a502ee17 (diff) |
Use AC_LANG_SOURCE inside AC_LANG_CONFTEST to fix autoconf warning
* configure.ac (AC_LANG_CONFTEST): Wrap the source into a AC_LANG_SOURCE
call.
-rw-r--r-- | configure.ac | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/configure.ac b/configure.ac index 50ec6b4..91bdea3 100644 --- a/configure.ac +++ b/configure.ac @@ -149,7 +149,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] |