On 06/02/11 18:13, Ian Lance Taylor wrote:
Works for me, but please add an @xref{Spec Files} (you might need a
document in there too, not sure) as a pointer to where the spec format
is documented.
ok, this is what I committed, cribbing from the rs6000 xref in the same file.
nathan
--
Nathan Sidwell
2011-06-03 Nathan Sidwell <nat...@codesourcery.com>
* doc/install.texi (Options specification): Document --with-specs.
Index: doc/install.texi
===================================================================
--- doc/install.texi (revision 174597)
+++ doc/install.texi (working copy)
@@ -771,6 +771,19 @@
on other configuration options, and differs between cross and native
configurations.
+@item --with-specs=@var{specs}
+Specify additional command line driver SPECS.
+This can be useful if you need to turn on a non-standard feature by
+default without modifying the compiler's source code, for instance
+@option{--with-specs=%@{!fcommon:%@{!fno-common:-fno-common@}@}}.
+@ifnothtml
+@xref{Spec Files,, Specifying subprocesses and the switches to pass to them,
+gcc, Using the GNU Compiler Collection (GCC)},
+@end ifnothtml
+@ifhtml
+See ``Spec Files'' in the main manual
+@end ifhtml
+
@end table
@item --program-prefix=@var{prefix}
