From: Matthias Klose <doko@ubuntu.com>
Date: Tue, 15 Nov 2016 11:08:33 +0000 (+0000)
Subject: install.texi: Move the 'Overriding configure test results' subsub section to the...
X-Git-Tag: releases/gcc-5.5.0~702
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=3c696aa89fe2b5da89e86a4549d65140b3f3d1dd;p=thirdparty%2Fgcc.git

install.texi: Move the 'Overriding configure test results' subsub section to the...

2016-11-15  Matthias Klose  <doko@ubuntu.com>

        * doc/install.texi: Move the 'Overriding configure test results'
        subsub section to the 'Cross-Compiler-Specific Options' sub section.

From-SVN: r242411
---

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 67622bf186c2..40ca4dcaab75 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+2016-11-15  Matthias Klose  <doko@ubuntu.com>
+
+	* doc/install.texi: Move the 'Overriding configure test results'
+	subsub section to the 'Cross-Compiler-Specific Options' sub section.
+
 2016-11-11  Uros Bizjak  <ubizjak@gmail.com>
 
 	PR target/78310
diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index 257dc49b89b0..bfedb136195d 100644
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -2081,6 +2081,36 @@ When you use this option, you should ensure that @var{dir} includes
 tools.
 @end table
 
+@subsubheading Overriding @command{configure} test results
+
+Sometimes, it might be necessary to override the result of some
+@command{configure} test, for example in order to ease porting to a new
+system or work around a bug in a test.  The toplevel @command{configure}
+script provides three variables for this:
+
+@table @code
+
+@item build_configargs
+@cindex @code{build_configargs}
+The contents of this variable is passed to all build @command{configure}
+scripts.
+
+@item host_configargs
+@cindex @code{host_configargs}
+The contents of this variable is passed to all host @command{configure}
+scripts.
+
+@item target_configargs
+@cindex @code{target_configargs}
+The contents of this variable is passed to all target @command{configure}
+scripts.
+
+@end table
+
+In order to avoid shell and @command{make} quoting issues for complex
+overrides, you can pass a setting for @env{CONFIG_SITE} and set
+variables in the site file.
+
 @subheading Java-Specific Options
 
 The following option applies to the build of the Java front end.
@@ -2315,35 +2345,6 @@ Do not try to compile and run a test libart program.
 
 @end table
 
-@subsubheading Overriding @command{configure} test results
-
-Sometimes, it might be necessary to override the result of some
-@command{configure} test, for example in order to ease porting to a new
-system or work around a bug in a test.  The toplevel @command{configure}
-script provides three variables for this:
-
-@table @code
-
-@item build_configargs
-@cindex @code{build_configargs}
-The contents of this variable is passed to all build @command{configure}
-scripts.
-
-@item host_configargs
-@cindex @code{host_configargs}
-The contents of this variable is passed to all host @command{configure}
-scripts.
-
-@item target_configargs
-@cindex @code{target_configargs}
-The contents of this variable is passed to all target @command{configure}
-scripts.
-
-@end table
-
-In order to avoid shell and @command{make} quoting issues for complex
-overrides, you can pass a setting for @env{CONFIG_SITE} and set
-variables in the site file.
 
 @html
 <hr />