procyberian/gcc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

install-old.texi: Don't mention enquire.

Browse source 
* doc/install-old.texi: Don't mention enquire.
        * doc/sourcebuild.texi: Update float.h description.

From-SVN: r56796
This commit is contained in:
Richard Henderson 2002-09-04 09:09:31 -07:00 • committed by Richard Henderson
parent 7fd6c930e5
commit cd42d3df16
3 changed files with 13 additions and 19 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
gcc/ChangeLog
View file

@ -1,3 +1,8 @@
2002-09-04 Richard Henderson <rth@redhat.com>
* doc/install-old.texi: Don't mention enquire.
* doc/sourcebuild.texi: Update float.h description.
Wed Sep 4 11:22:14 2002 J"orn Rennecke <joern.rennecke@superh.com>
* sh.md (mperm_w_little, mperm_w_big): Supply mode for zero_extract.

14
gcc/doc/install-old.texi
View file

@ -34,9 +34,7 @@ See @ref{VMS Install}, for VMS systems.
If you have chosen a configuration for GNU CC which requires other GNU
tools (such as GAS or the GNU linker) instead of the standard system
tools, install the required tools in the build directory under the names
@file{as}, @file{ld} or whatever is appropriate. This will enable the
compiler to find the proper tools for compilation of the program
@file{enquire}.
@file{as}, @file{ld} or whatever is appropriate.
Alternatively, you can do subsequent compilation using a value of the
@code{PATH} environment variable such that the necessary GNU tools come
@ -458,16 +456,6 @@ tar xf tarfile
Now you can proceed just as for compiling a single-machine compiler
through the step of building stage 1.
If your target is exotic, you may need to provide the header file
@file{float.h}.One way to do this is to compile @file{enquire} and run
it on your target machine. The job of @file{enquire} is to run on the
target machine and figure out by experiment the nature of its floating
point representation. @file{enquire} records its findings in the header
file @file{float.h}. If you can't produce this file by running
@file{enquire} on the target machine, then you will need to come up with
a suitable @file{float.h} in some other way (or else, avoid using it in
your programs).
Do not try to build stage 2 for a cross-compiler. It doesn't work to
rebuild GNU CC as a cross-compiler using the cross-compiler, because
that would produce a program that runs on the target machine, not on the

13
gcc/doc/sourcebuild.texi
View file

@ -255,12 +255,13 @@ In addition to these headers and those generated by fixing system
headers to work with GCC, some other headers may also be installed in
@file{@var{libsubdir}/include}. @file{config.gcc} may set
@code{extra_headers}; this specifies additional headers under
@file{config} to be installed on some systems. GCC normally installs
a @code{<float.h>} file; these are kept as
@file{config/float-@var{format}.h}, where @var{format} is specified by
a @code{float_format} setting in @file{config.gcc}, and a setting
@samp{float_format=none} disables installation of this header. GCC
also installs its own version of @code{<limits.h>}; this is generated
@file{config} to be installed on some systems.
GCC installs its own version of @code{<float.h>}, from @file{ginclude/float.h}.
This is done to cope with command-line options that change the
representation of floating point numbers.
GCC also installs its own version of @code{<limits.h>}; this is generated
from @file{glimits.h}, together with @file{limitx.h} and
@file{limity.h} if the system also has its own version of
@code{<limits.h>}. (GCC provides its own header because it is