This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[patch] [5/6] fix installation documentation
- From: Matthias Klose <doko at ubuntu dot com>
- To: GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Tue, 15 Nov 2016 12:07:37 +0100
- Subject: [patch] [5/6] fix installation documentation
- Authentication-results: sourceware.org; auth=none
Seen while cleaning up the GCJ references. The last section of the gcj install
docs doesn't belong there, but into the cross install section. The change is
not necessary on the trunk once the gcj docs are removed. Fixed this on the 5
and 6 branches by moving the section.
Committed as obvious.
Matthias
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.
Index: gcc/doc/install.texi
===================================================================
--- gcc/doc/install.texi (revision 242386)
+++ gcc/doc/install.texi (working copy)
@@ -2081,6 +2081,36 @@
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,36 +2345,7 @@
@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 />
<p>