summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2012-04-23 10:30:05 -0700
committerPaul Eggert <eggert@cs.ucla.edu>2012-04-23 10:30:19 -0700
commited96f6541caacbc35cd8fca6444d04b40bba9b1a (patch)
tree600578401d53192ab5e87ad051d41de472b6ae8b
parenteaa96cb8bd6dca5317329b6682df91dfda286d06 (diff)
downloadautoconf-ed96f6541caacbc35cd8fca6444d04b40bba9b1a.tar.gz
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
-rw-r--r--doc/autoconf.texi4
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index 2ae8bb93..b1295ebe 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}