Here we spell out what files will be set up by
configure in the
gcc directory. Some other files are created as temporary files
in the configuration process, and are not used in the subsequent
build; these are not documented.
Makefileis constructed from
Makefile.in, together with the host and target fragments (see Makefile Fragments)
config, if any, and language Makefile fragments
auto-host.hcontains information about the host machine determined by
configure. If the host machine is different from the build machine, then
auto-build.his also created, containing such information about the build machine.
config.statusis a script that may be run to recreate the current configuration.
configargs.his a header containing details of the arguments passed to
configureto configure GCC, and of the thread model used.
cstamp-his used as a timestamp.
fixinc/Makefileis constructed from
gccbug, a script for reporting bugs in GCC, is constructed from
intl/Makefileis constructed from
mklibgcc, a shell script to create a Makefile to build libgcc, is constructed from
config-lang.infile (see The Front End
outputs, then the files listed in
outputsthere are also generated.
The following configuration headers are created from the Makefile,
mkconfig.sh, rather than directly by
tconfig.h all contain the
.h header, if any, appropriate to the host,
build and target machines respectively, the configuration headers for
the target, and some definitions; for the host and build machines,
these include the autoconfigured headers generated by
configure. The other configuration headers are determined by
config.gcc. They also contain the typedefs for
config.h, for use in programs that run on the host machine.
hconfig.h, for use in programs that run on the build machine.
tconfig.h, for use in programs and libraries for the target machine.
tm_p.h, which includes the header
-protos.hthat contains prototypes for functions in the target
.cfile. FIXME: why is such a separate header necessary?