[SCM] GNU Autoconf source repository branch, master, updated. v2.68b-22-g280f330

[Eric Blake]

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=280f3309927f87d8483d092425cdc2d2f7842ba1

The branch, master has been updated
       via  280f3309927f87d8483d092425cdc2d2f7842ba1 (commit)
       via  303e507c2783bb6c43c7c5be2467eaa8a57dadd9 (commit)
      from  ed96f6541caacbc35cd8fca6444d04b40bba9b1a (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 280f3309927f87d8483d092425cdc2d2f7842ba1
Author: Bruno Haible <address@hidden>
Date:   Sun Apr 22 19:42:24 2012 +0200

    AC_INIT: remove a transitional warning
    
    On bi-arch systems (such as x86 / x86_64) it is often necessary to pass
    the --host option together with an appropriate value for CC. But this
    triggers a warning:
    
    $ ./configure --host=i686-pc-linux-gnu CC="gcc -m32 -march=i586"
    configure: WARNING: if you wanted to set the --build type, don't use --host.
        If a cross compiler is detected then cross compile mode will be used
    ..
    
    This warning was introduced on 2000-06-30, in commit
    
<http://git.savannah.gnu.org/gitweb/?p=autoconf.git;a=commitdiff;h=cb2e761b8e1181f97e8e09d85526bd22078433db>
    with the remark "Re-enable the old behavior of --host and --build."
    
    This warning was meant to warn users about a changed semantics of
    --build and --host. This change is now 12 years in the past; users
    have had enough time to learn it. I therefore suggest to remove the
    warning.
    
    I've done lots of cross and bi-arch compilations in the last 10 years,
    all with --host and without --build, and have never observed a problem
    with it, except for the warning. Simply relying on config.guess is 
sufficient.
    
    * lib/autoconf/general.m4 (_AC_INIT_PARSE_ARGS): Don't warn if --host
    given without --build.
    
    Signed-off-by: Eric Blake <address@hidden>

commit 303e507c2783bb6c43c7c5be2467eaa8a57dadd9
Author: Bruno Haible <address@hidden>
Date:   Mon Apr 23 21:43:04 2012 +0200

    doc: fix incorrect and incomplete doc about cross-compilation mode
    
    * doc/autoconf.texi (Runtime): Mention the effect of the cross-
    compilation mode on AC_RUN_IFELSE.
    (Specifying Target Triplets): Fix description of --host's effects.
    (Hosts and Cross-Compilation): Remove incorrect statement about
    --host's effects.
    
    Signed-off-by: Eric Blake <address@hidden>

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

Summary of changes:
 doc/autoconf.texi       |   17 +++++++++--------
 lib/autoconf/general.m4 |    2 --
 2 files changed, 9 insertions(+), 10 deletions(-)

diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index b1295eb..a629668 100644
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -9491,8 +9491,11 @@ 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
+If cross-compilation mode is enabled (this is the case if either the
+compiler being used does not produce executables that run on the system
+where @command{configure} is being run, or if the options @code{--build}
+and @code{--host} were both specified and their values are different),
+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
@@ -21752,8 +21755,9 @@ cross-compilation mode.
 
 @item address@hidden
 the type of system on which the package runs.  By default it is the
-same as the build machine.  Specifying it enables cross-compilation
-mode.
+same as the build machine.  Specifying a @var{host-type} that differs
+from @var{build-type}, when @var{build-type} was also explicitly
+specified, enables cross-compilation mode.
 
 @item address@hidden
 the type of system for which any compiler tools in the package
@@ -24459,10 +24463,7 @@ and they're different, @command{configure} enters 
cross compilation
 mode, so it doesn't run any tests that require execution.
 
 Hint: if you mean to override the result of @command{config.guess},
-prefer @option{--build} over @option{--host}.  In the future,
address@hidden will not override the name of the build system type.
-Whenever you specify @option{--host}, be sure to specify @option{--build}
-too.
+prefer @option{--build} over @option{--host}.
 
 @sp 1
 
diff --git a/lib/autoconf/general.m4 b/lib/autoconf/general.m4
index dfa687f..adfae1d 100644
--- a/lib/autoconf/general.m4
+++ b/lib/autoconf/general.m4
@@ -949,8 +949,6 @@ target=$target_alias
 if test "x$host_alias" != x; then
   if test "x$build_alias" = x; then
     cross_compiling=maybe
-    AC_MSG_WARN([if you wanted to set the --build type, don't use --host.
-    If a cross compiler is detected then cross compile mode will be used])
   elif test "x$build_alias" != "x$host_alias"; then
     cross_compiling=yes
   fi


hooks/post-receive
-- 
GNU Autoconf source repository