mirror/gcc
2
0
Fork 0
mirror of git://gcc.gnu.org/git/gcc.git synced 2024-12-19 03:38:59 +08:00
Code Issues Packages Projects Releases Wiki Activity

fragments.texi: Mention config.host.

Browse Source 
* 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
This commit is contained in:
Nathanael Nerode 2003-09-01 17:47:21 +00:00
parent 130a1080ce
commit 330532ab09
3 changed files with 31 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
gcc/ChangeLog
View File

@ -1,3 +1,9 @@
2003-09-01 Nathanael Nerode <neroden@gcc.gnu.org>
* 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 <zack@codesourcery.com>
* c-decl.c (pushdecl): Don't put variables on

3
gcc/doc/fragments.texi
View File

@ -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

30
gcc/doc/sourcebuild.texi
View File

@ -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.