+2010-05-25 Stefano Lattarini <stefano.lattarini@gmail.com>
+ Eric Blake <eblake@redhat.com>
+
+ Don't expose AC_{COMPILE,LINK}_IFELSE internals in documentation.
+ * doc/autoconf.texi (Runtime) <AC_LINK_IFELSE>: Suggest to use
+ `conftest$EXEEXT' rather than `conftest$ac_exeext' to acces the
+ just-linked program file.
+ (Runtime) <AC_COMPILE_IFELSE>: Suggest to use `conftest.$OBJEXT'
+ rather than `conftest.$ac_object' to access the just-compiled
+ object file. Also, refer to the object file as "just-compiled"
+ rather than "just-linked".
+
2010-05-20 Eric Blake <eblake@redhat.com>
Mention another line-counting alternative.
@code{AC_MSG_FAILURE}. This macro does not try to link; use
@code{AC_LINK_IFELSE} if you need to do that (@pxref{Running the
Linker}). If needed, @var{action-if-true} can further access the
-just-linked object file @file{conftest.$ac_object}.
+just-compiled object file @file{conftest.$OBJEXT}.
This macro uses @code{AC_REQUIRE} for the compiler associated with the
current language, which means that if the compiler has not yet been
commands @var{action-if-true} on success, @var{action-if-false}
otherwise. The @var{input} can be made by @code{AC_LANG_PROGRAM} and
friends. If needed, @var{action-if-true} can further access the
-just-linked program file @file{conftest$ac_exeext}.
+just-linked program file @file{conftest$EXEEXT}.
@code{LDFLAGS} and @code{LIBS} are used for linking, in addition to the
current compilation flags.