Amos Jeffries wrote:
> FAILING:
>
> AC_CACHE_CHECK(if working, foo_works,
>
> AC_RUN_IFELSE([AC_LANG_SOURCE([[int main(){return
> 1;}]])],[foo_works=yes],[foo_works=no],[])
I can't say if this is a genuine bug in autoconf, but the above
snippet is dangerously underquoted; I can't reproduce with proper m4
quotation:
cat > configure.ac <<'EOF'
AC_INIT
AC_CACHE_CHECK([if working], [my_cv_foo_works],
[AC_RUN_IFELSE([AC_LANG_SOURCE([[int main (){return 1;}]])],
[my_cv_foo_works=yes], [my_cv_foo_works=no], [])])
AC_OUTPUT
EOF
autoconf
./configure
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking if working... no
configure: creating ./config.status
Note also that the cache variable name must contain _cv_, otherwise it
won't be cached.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
