From 330532ab094f0f61e869eef0a04bf41269ff062b Mon Sep 17 00:00:00 2001 From: Nathanael Nerode Date: Mon, 1 Sep 2003 17:47:21 +0000 Subject: [PATCH] fragments.texi: Mention config.host. * doc/fragments.texi: Mention config.host. * doc/sourcebuild.texi: Mention config.host. Give brief descriptions of config.build, config.host, and config.gcc. From-SVN: r70977 --- gcc/ChangeLog | 6 ++++++ gcc/doc/fragments.texi | 3 ++- gcc/doc/sourcebuild.texi | 30 +++++++++++++++++++++++------- 3 files changed, 31 insertions(+), 8 deletions(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 493e4b425c9..aa903e06401 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,9 @@ +2003-09-01 Nathanael Nerode + + * doc/fragments.texi: Mention config.host. + * doc/sourcebuild.texi: Mention config.host. Give brief descriptions + of config.build, config.host, and config.gcc. + 2003-09-01 Zack Weinberg * c-decl.c (pushdecl): Don't put variables on diff --git a/gcc/doc/fragments.texi b/gcc/doc/fragments.texi index 379703cf618..160ffed15b9 100644 --- a/gcc/doc/fragments.texi +++ b/gcc/doc/fragments.texi @@ -13,7 +13,8 @@ construct the file @file{Makefile} from the template file fragments from the @file{config} directory. These are used to set Makefile parameters that are not amenable to being calculated by autoconf. The list of fragments to incorporate is set by -@file{config.gcc} (and occasionally @file{config.build}); @xref{System Config}. +@file{config.gcc} (and occasionally @file{config.build} +and @file{config.host}); @xref{System Config}. Fragments are named either @file{t-@var{target}} or @file{x-@var{host}}, depending on whether they are relevant to configuring GCC to produce diff --git a/gcc/doc/sourcebuild.texi b/gcc/doc/sourcebuild.texi index b5a11a94a3e..73ad706bc74 100644 --- a/gcc/doc/sourcebuild.texi +++ b/gcc/doc/sourcebuild.texi @@ -175,7 +175,8 @@ timestamp. @menu * Config Fragments:: Scripts used by @file{configure}. -* System Config:: The @file{config.build} and @file{config.gcc} files. +* System Config:: The @file{config.build}, @file{config.host}, and + @file{config.gcc} files. * Configuration Files:: Files created by running @file{configure}. @end menu @@ -191,12 +192,14 @@ files, kept in the top level directory, are used. FIXME: when is the the top level one) used? @item The file @file{config.gcc} is used to handle configuration -specific to the particular host or target machine. The file +specific to the particular target machine. The file @file{config.build} is used to handle configuration specific to the -particular build machine. (In general, these should only be used for -features that cannot reasonably be tested in Autoconf feature tests.) -@xref{System Config, , The @file{config.build} and @file{config.gcc} Files}, -for details of the contents of these files. +particular build machine. The file @file{config.host} is used to handle +configuration specific to the particular host machine. (In general, +these should only be used for features that cannot reasonably be tested in +Autoconf feature tests.) +@xref{System Config, , The @file{config.build}, @file{config.host}, +and @file{config.gcc} Files}, for details of the contents of these files. @item Each language subdirectory has a file @file{@var{language}/config-lang.in} that is used for @@ -208,7 +211,20 @@ creating the output of @file{configure}. @end itemize @node System Config -@subsubsection The @file{config.build} and @file{config.gcc} Files +@subsubsection The @file{config.build}, @file{config.host}, and @file{config.gcc} Files + +The @file{config.build} file contains specific rules for particular systems +which GCC is built on. This should be used as rarely as possible, as the +behavior of the build system can always be detected by autoconf. + +The @file{config.host} file contains specific rules for particular systems +which GCC will run on. This is rarely needed. + +The @file{config.gcc} file contains specific rules for particular systems +which GCC will generate code for. This is usually needed. + +Each file has a list of the shell variables it sets, with descriptions, at the +top of the file. FIXME: document the contents of these files, and what variables should be set to control build, host and target configuration. -- 2.30.2