> > better to document external variables like $EXEEXT than to expose > > internal details like $ac_exeext; so it seems like AC_LINK_IFELSE > > should be the subject of the patch. > > And AC_COMPILE_IFELSE too, since its documentation mentions > $ac_object. > Done in the attached patch.
Regards, Stefano
From cc08b0b2776a0c7594cd3d83b719374fbd12ecbc Mon Sep 17 00:00:00 2001 From: Stefano Lattarini <stefano.lattar...@gmail.com> Date: Tue, 25 May 2010 18:58:24 +0200 Subject: [PATCH] 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". --- ChangeLog | 12 ++++++++++++ doc/autoconf.texi | 4 ++-- 2 files changed, 14 insertions(+), 2 deletions(-) diff --git a/ChangeLog b/ChangeLog index f9b7d04..1452eb3 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,15 @@ +2010-05-25 Stefano Lattarini <stefano.lattar...@gmail.com> + Eric Blake <ebl...@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 <ebl...@redhat.com> Mention another line-counting alternative. diff --git a/doc/autoconf.texi b/doc/autoconf.texi index cbdb56b..3df0d3f 100644 --- a/doc/autoconf.texi +++ b/doc/autoconf.texi @@ -8915,7 +8915,7 @@ 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}). 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 @@ -8961,7 +8961,7 @@ 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. 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. -- 1.6.5