The following bug was reported against the Debian package for
autoconf 2.13. I was able to reproduce it with autoconf 2.52,
using this configure.in fragment:
AC_TRY_RUN([int main(void){return 5;}], [echo success],
[echo fail: "$?"], [echo cross-compile])
which reports `fail: "0"' in my test run, whereas I expected to
see `fail: "5"' if everything were correct.
Thanks,
Ben.
----------------------------------------------------------------------
Subject: Bug#113484: AC_TRY_RUN doesn't set $? as documented
From: Richard Kettlewell <[EMAIL PROTECTED]>
Package: autoconf
Version: 2.13
The manual says:
- Macro: AC_TRY_RUN (PROGRAM, [ACTION-IF-TRUE [, ACTION-IF-FALSE [,
ACTION-IF-CROSS-COMPILING]]])
PROGRAM is the text of a C program, on which shell variable and
backquote substitutions are performed. If it compiles and links
successfully and returns an exit status of 0 when executed, run
shell commands ACTION-IF-TRUE. Otherwise run shell commands
ACTION-IF-FALSE; the exit status of the program is available in
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
the shell variable `$?'. This macro uses `CFLAGS' or `CXXFLAGS',
^^^^^^^^^^^^^^^^^^^^^^^
`CPPFLAGS', `LDFLAGS', and `LIBS' when compiling.
However this is not actually true, as trying to take advantage of this
feature, or just looking at acgeneral.m4, reveals.
Sorry if this bug has already been reported, my net connection is
currently down.
ttfn/rjk
----------------------------------------------------------------------
