Improve documentation on AC_{COMPILE,LINK}_IFELSE.

* doc/autoconf.texi (Running the Compiler): Mention that the
object file is available after a successful compile.
(Running the Linker): Likewise for the linker output.
Suggested by Paolo Bonzini.

Signed-off-by: Eric Blake <eblake@redhat.com>
This commit is contained in:
Eric Blake 2010-03-02 14:00:24 -07:00
parent dcd879464e
commit 026070fea8
2 changed files with 10 additions and 2 deletions

View File

@ -1,5 +1,11 @@
2010-03-02 Eric Blake <eblake@redhat.com>
Improve documentation on AC_{COMPILE,LINK}_IFELSE.
* doc/autoconf.texi (Running the Compiler): Mention that the
object file is available after a successful compile.
(Running the Linker): Likewise for the linker output.
Suggested by Paolo Bonzini.
Fix typo in docs.
* doc/autoconf.texi (Conditional constructs) <m4_ifblank>: Fix
typo.

View File

@ -8914,7 +8914,8 @@ Run the compiler and compilation flags of the current language
It is customary to report unexpected failures with
@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}).
Linker}). If needed, @var{action-if-true} can further access the
just-linked object file @file{conftest.$ac_object}.
This macro uses @code{AC_REQUIRE} for the compiler associated with the
current language, which means that if the compiler has not yet been
@ -8959,7 +8960,8 @@ Run the compiler (and compilation flags) and the linker of the current
language (@pxref{Language Choice}) on the @var{input}, run the shell
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.
friends. If needed, @var{action-if-true} can further access the
just-linked program file @file{conftest$ac_exeext}.
@code{LDFLAGS} and @code{LIBS} are used for linking, in addition to the
current compilation flags.