autoconf-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[SCM] GNU Autoconf source repository branch, master, updated. v2.68-42-g


From: Eric Blake
Subject: [SCM] GNU Autoconf source repository branch, master, updated. v2.68-42-gf9fb235
Date: Fri, 18 Feb 2011 18:11:02 +0000

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU Autoconf source repository".

http://git.sv.gnu.org/gitweb/?p=autoconf.git;a=commitdiff;h=f9fb23548804e962be8ce619e7fcec62299c100e

The branch, master has been updated
       via  f9fb23548804e962be8ce619e7fcec62299c100e (commit)
      from  5d1fd3630946d3ac2a98f87a8558e83b8e1588cb (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit f9fb23548804e962be8ce619e7fcec62299c100e
Author: Eric Blake <address@hidden>
Date:   Fri Feb 18 11:08:08 2011 -0700

    docs: document fourth argument of AC_RUN_IFELSE better
    
    * doc/autoconf.texi (Runtime) <AC_RUN_IFELSE>: Make synopsis show
    that the default is configure failure.  Rework the text about
    proper use of the fourth argument.
    
    Signed-off-by: Eric Blake <address@hidden>

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog         |    5 +++++
 doc/autoconf.texi |   39 +++++++++++++++++++++++----------------
 2 files changed, 28 insertions(+), 16 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index f46eb6f..0bd0b78 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,10 @@
 2011-02-18  Eric Blake  <address@hidden>
 
+       docs: document fourth argument of AC_RUN_IFELSE better
+       * doc/autoconf.texi (Runtime) <AC_RUN_IFELSE>: Make synopsis show
+       that the default is configure failure.  Rework the text about
+       proper use of the fourth argument.
+
        long long: don't abort configure when cross-compiling
        * lib/autoconf/types.m4 (AC_TYPE_LONG_LONG_INT): Provide no-op
        cross-compiling fallback; fixing regression from 2011-02-16.
diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index d62ec9b..a08208f 100644
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -9176,7 +9176,7 @@ cross-compiling.
 
 @anchor{AC_RUN_IFELSE}
 @defmac AC_RUN_IFELSE (@var{input}, @ovar{action-if-true}, @
-  @ovar{action-if-false}, @ovar{action-if-cross-compiling})
+  @ovar{action-if-false}, @dvar{action-if-cross-compiling, AC_MSG_FAILURE})
 @acindex{RUN_IFELSE}
 If @var{program} compiles and links successfully and returns an exit
 status of 0 when executed, run shell commands @var{action-if-true}.
@@ -9188,30 +9188,37 @@ compilation flags of the current language 
(@pxref{Language Choice}).
 Additionally, @var{action-if-true} can run @command{./conftest$EXEEXT}
 for further testing.
 
-If the compiler being used does not produce executables that run on the
-system where @command{configure} is being run, then the test program is
-not run.  If the optional shell commands @var{action-if-cross-compiling}
-are given, they are run instead.  Otherwise, @command{configure} prints
-an error message and exits.
-
 In the @var{action-if-false} section, the failing exit status is
 available in the shell variable @samp{$?}.  This exit status might be
 that of a failed compilation, or it might be that of a failed program
 execution.
 
+If the compiler being used does not produce executables that run on the
+system where @command{configure} is being run, then the test program is
+not run.  If the optional shell commands @var{action-if-cross-compiling}
+are given, those commands are run instead; typically these commands
+provide pessimistic defaults that allow cross-compilation to work even
+if the guess was wrong.  If the fourth argument is empty or omitted, but
+cross-compilation is detected, then @command{configure} prints an error
+message and exits.  If you want your package to be useful in a
+cross-compilation scenario, you @emph{should} provide a non-empty
address@hidden clause, as well as wrap the
address@hidden compilation inside an @code{AC_CACHE_CHECK}
+(@pxref{Caching Results}) which allows the user to override the
+pessimistic default if needed.
+
 It is customary to report unexpected failures with
 @code{AC_MSG_FAILURE}.
 @end defmac
 
-Try to provide a pessimistic default value to use when cross-compiling
-makes runtime tests impossible.  You do this by passing the optional
-last argument to @code{AC_RUN_IFELSE}.  @command{autoconf} prints a
-warning message when creating @command{configure} each time it
-encounters a call to @code{AC_RUN_IFELSE} with no
address@hidden argument given.  You may ignore the
-warning, though users cannot configure your package for
-cross-compiling.  A few of the macros distributed with Autoconf produce
-this warning message.
address@hidden prints a warning message when creating
address@hidden each time it encounters a call to
address@hidden with no @var{action-if-cross-compiling} argument
+given.  If you are not concerned about users configuring your package
+for cross-compilation, you may ignore the warning.  A few of the macros
+distributed with Autoconf produce this warning message; but if this is a
+problem for you, please report it as a bug, along with an appropriate
+pessimistic guess to use instead.
 
 To configure for cross-compiling you can also choose a value for those
 parameters based on the canonical system name (@pxref{Manual


hooks/post-receive
-- 
GNU Autoconf source repository



reply via email to

[Prev in Thread] Current Thread [Next in Thread]