On 04/23/2012 04:16 AM, Bruno Haible wrote: > 2012-04-23 Bruno Haible <[email protected]> > > doc: Mention an effect of --build on AC_RUN_IFELSE. > * doc/autoconf.texi (Specifying Target Triplets): Mention another > effect of --build.
Thanks, I pushed the following slightly-different (and I hope clearer) patch. I don't understand the disagreement about what --host and --build should do (I try not to do cross-builds myself...) but at least this helps document what autoconf currently does, and it can be changed if the behavior needs to be changed. >From 71d2c125cb3ad167a59776a3bab0e95169805af0 Mon Sep 17 00:00:00 2001 From: Paul Eggert <[email protected]> Date: Mon, 23 Apr 2012 10:30:05 -0700 Subject: [PATCH] doc: document --build and cross-compilation better * doc/autoconf.texi (Specifying Target Triplets): Mention that specifying a build-type that differs from host-type enables cross-compilation. Problem reported by Bruno Haible in: http://lists.gnu.org/archive/html/autoconf-patches/2012-04/msg00009.html --- doc/autoconf.texi | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/doc/autoconf.texi b/doc/autoconf.texi index 2ae8bb9..b1295eb 100644 --- a/doc/autoconf.texi +++ b/doc/autoconf.texi @@ -21747,10 +21747,12 @@ system types are involved. The options to specify them are: @item --build=@var{build-type} the type of system on which the package is being configured and compiled. It defaults to the result of running @command{config.guess}. +Specifying a @var{build-type} that differs from @var{host-type} enables +cross-compilation mode. @item --host=@var{host-type} the type of system on which the package runs. By default it is the -same as the build machine. Specifying it enables the cross-compilation +same as the build machine. Specifying it enables cross-compilation mode. @item --target=@var{target-type} -- 1.7.6.5
