This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
3.0 PATCH: More fixes to install.texi
- To: gcc-patches at gcc dot gnu dot org
- Subject: 3.0 PATCH: More fixes to install.texi
- From: Rainer Orth <ro at TechFak dot Uni-Bielefeld dot DE>
- Date: Fri, 15 Jun 2001 21:58:26 +0200 (MEST)
Here's another bunch of fixes to install.texi.
A few more issues have come up while proofreading install.texi, but I
haven't done anything about them:
* Unpacking binutils and gcc in the same directory may be dangerous: what
about different versions of shared files, especially when gcc and
binutils versions are not very close in time.
* Do we want to provide a list of possible targets, or a hint where to find
one?
* There seems to be no way to specify that no local prefix is desired.
* When does gcc use a different debug format than the host default?
* When is is still necessary to have/build texinfo, bison, and gperf when
building a native compiler? Which versions?
* URLs should be included in the printed manual (three-arg form of @uref?).
* Use make mail-report.log to create test summary?
As before, if this is ok, I won't be able to install it myself until
monday.
Rainer
-----------------------------------------------------------------------------
Rainer Orth, Faculty of Technology, Bielefeld University
Email: ro@TechFak.Uni-Bielefeld.DE
* doc/install.texi: Various spelling and markup fixes.
(Installing GCC): Component specific installation instructions are
gone.
Fix reference.
Warn about removing old install dir in the presence of shared libs.
(Configuration): Invoke with options target to match configure
--help.
Consistently refer to gas, gld pathnames.
Invert --enable-multilib documentation.
Remove references to old compiler versions.
Index: install.texi
===================================================================
RCS file: /cvs/gcc/egcs/gcc/doc/install.texi,v
retrieving revision 1.1.2.26
diff -u -p -r1.1.2.26 install.texi
--- install.texi 2001/06/15 17:31:53 1.1.2.26
+++ install.texi 2001/06/15 19:46:39
@@ -106,13 +106,11 @@ as detailing some target specific instal
GCC includes several components that previously were separate distributions
with their own installation instructions. This document supersedes all
-package specific installation instructions. We provide the component
-specific installation information in the source distribution for historical
-reference purposes only.
+package specific installation instructions.
@emph{Before} starting the build/install procedure please check the
@ifnothtml
-@xref{Specific, host/target specific installation notes}.
+@ref{Specific, host/target specific installation notes}.
@end ifnothtml
@ifnotinfo
@uref{specific.html,,host/target specific installation notes}.
@@ -150,7 +148,8 @@ Please note that GCC does not support @s
won't do so in the near future as this would open a can of worms. Instead,
we suggest that you install GCC into a directory of its own and simply
remove that directory when you do not need that specific version of GCC
-any longer.
+any longer, and, if shared libraries are installed there as well, no
+more binaries exist that use them.
@html
<hr>
@@ -176,7 +175,8 @@ any longer.
@cindex Downloading GCC
@cindex Downloading the Source
-GCC is distributed via CVS and FTP tarballs compressed with @command{gzip} or
+GCC is distributed via @uref{http://gcc.gnu.org/cvs.html,,CVS} and FTP
+tarballs compressed with @command{gzip} or
@command{bzip2}. It is possible to download a full distribution or specific
components.
@@ -184,14 +184,14 @@ Please refer to our @uref{http://gcc.gnu
for information on how to obtain GCC.
The full distribution includes the C, C++, Objective-C, Fortran, Java,
-and Chill compilers. The full distribution also includes runtime libraries
-for C++, Objective-C, Fortran, Java and Chill. (GCC 3.0 does not
-include Chill. Releases before 3.0 do not include the Java runtime
+and CHILL compilers. The full distribution also includes runtime libraries
+for C++, Objective-C, Fortran, Java and CHILL. (GCC 3.0 does not
+include CHILL. Releases before 3.0 do not include the Java runtime
library.) In GCC 3.0 and later versions, GNU compiler testsuites
are also included in the full distribution.
If you choose to download specific components, you must download the core
-gcc distribution plus any language specific distributions you wish to
+GCC distribution plus any language specific distributions you wish to
use. The core distribution includes the C language front-end as well as the
shared components. Each language has a tarball which includes the language
front-end as well as the language runtime (when appropriate).
@@ -249,7 +249,7 @@ where @var{srcdir} == @var{objdir} shoul
get extensive testing; building where @var{objdir} is a subdirectory
of @var{srcdir} is unsupported.
-If you have built GNU CC previously in the same directory for a
+If you have built GCC previously in the same directory for a
different target machine, do @samp{make distclean} to delete all files
that might be invalid. One of the files this deletes is
@file{Makefile}; if @samp{make distclean} complains that @file{Makefile}
@@ -263,12 +263,18 @@ Second, when configuring a native system
your environment before running configure. Otherwise the configuration
scripts may fail.
+Note that the bootstrap compiler and the resulting GCC must be link
+compatible, else the bootstrap will fail with linker errors about
+incompatible object file formats. Several multilibbed targets are
+affected by this requirement, see @ref{Specific, host/target specific
+installation notes} for details.
+
To configure GCC:
@example
% mkdir @var{objdir}
% cd @var{objdir}
- % @var{srcdir}/configure [@var{target}] [@var{options}]
+ % @var{srcdir}/configure [@var{options}] [@var{target}]
@end example
@@ -340,7 +346,7 @@ manual.)
@item --with-gxx-include-dir=@var{dirname}
Specify
-the installation directory for g++ header files. The default is
+the installation directory for G++ header files. The default is
@file{@var{prefix}/include/g++-v3}.
@end table
@@ -383,7 +389,9 @@ installing GCC creates the directory.
@item --enable-shared[=@var{package}[,@dots{}]]
Build shared versions of libraries, if shared libraries are supported on
the target platform. Unlike GCC 2.95.x and earlier, shared libraries
-are enabled by default on all platforms that support shared libraries.
+are enabled by default on all platforms that support shared libraries,
+except for @samp{libobjc} which is built as a static library only by
+default.
If a list of packages is given as an argument, build shared libraries
only for the listed packages. For other packages, only static libraries
@@ -392,7 +400,7 @@ will be built. Package names currently
@samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc} and
@samp{libjava}. Note that @samp{libobjc} does not recognize itself by
any name, so, if you list package names in @option{--enable-shared},
-you'll only get static Objective C libraries. @samp{libf2c} and
+you'll only get static Objective-C libraries. @samp{libf2c} and
@samp{libiberty} do not support shared libraries at all.
Use @option{--disable-shared} to build only static libraries. Note that
@@ -405,9 +413,9 @@ assembler it finds is the GNU assembler.
the rules to find an assembler and will result in confusion if found
assembler is not actually the GNU assembler. If you have more than one
assembler installed on your system, you may want to use this option in
-connection with @option{--with-as=@file{/path/to/gas}}.
+connection with @option{--with-as=@var{pathname}}.
-@item --with-as=@file{/path/to/as}
+@item --with-as=@var{pathname}
Specify that the
compiler should use the assembler pointed to by @var{pathname}, rather
than the one found by the standard rules to find an assembler, which
@@ -418,9 +426,9 @@ Check the
@file{@var{exec_prefix}/lib/gcc-lib/@var{target}/@var{version}}
directory, where @var{exec_prefix} defaults to @var{prefix} which
defaults to @file{/usr/local} unless overridden by the
-@option{--prefix=/pathname} switch described above. @var{target} is the
+@option{--prefix=@var{pathname}} switch described above. @var{target} is the
target system triple, such as @var{sparc-sun-solaris2.7}, and
-@var{version} denotes the GCC version, such as 2.95.2.
+@var{version} denotes the GCC version, such as 3.0.
@item
Check operating system specific directories (e.g. @file{/usr/ccs/bin} on
Sun Solaris).
@@ -435,7 +443,7 @@ Same as @uref{#with-gnu-as,,@option{--wi
but for linker.
-@item --with-ld=@file{/path/to/ld}
+@item --with-ld=@var{pathname}
Same as
@option{--with-as}, but for the linker.
@@ -444,10 +452,11 @@ Specify that stabs debugging
information should be used instead of whatever format the host normally
uses. Normally GCC uses the same debug format as the host system.
-@item --enable-multilib
+@item --disable-multilib
Specify that multiple target
-libraries should be built to support different target variants, calling
-conventions, etc. This is the default.
+libraries to support different target variants, calling
+conventions, etc should not be built. The default is to build a
+predefined set of them.
@item --enable-threads
Specify that the target
@@ -471,7 +480,7 @@ DEC OSF/1 thread support.
@item irix
SGI IRIX thread support.
@item mach
-Generic MACH thread support, known to work on NEXTSTEP.
+Generic MACH thread support, known to work on NeXTSTEP.
@item os2
IBM OS/2 thread support.
@item posix
@@ -481,7 +490,7 @@ Same as @samp{posix}.
@item single
Disable thread support, should work for all platforms.
@item solaris
-SUN Solaris thread support.
+Sun Solaris 2 thread support.
@item vxworks
VxWorks thread support.
@item win32
@@ -521,24 +530,26 @@ to do so.
Specify
that runtime libraries should be installed in the compiler specific
subdirectory (@file{@var{libsubdir}}) rather than the usual places. In
-addition, libstdc++'s include files will be installed in
+addition, @samp{libstdc++}'s include files will be installed in
@file{@var{libsubdir}/include/g++} unless you overruled it by using
@option{--with-gxx-include-dir=@var{dirname}}. Using this option is
particularly useful if you intend to use several versions of GCC in
parallel. This is currently supported by @samp{libf2c} and
-@samp{libstdc++}.
+@samp{libstdc++}, and is the default for @samp{libobjc} which cannot be
+changed in this case.
@item --enable-languages=@var{lang1},@var{lang2},@dots{}
Specify that only a particular subset of compilers and
their runtime libraries should be built. For a list of valid values for
@var{langN} you can issue the following command in the
-@file{gcc} directory of your GCC source tree:@* @samp{grep language=
-*/config-lang.in}@* Currently, you can use any of the following:
+@file{gcc} directory of your GCC source tree:@*
+@example
+grep language= */config-lang.in
+@end example
+Currently, you can use any of the following:
@code{c++}, @code{f77}, @code{java} and @code{objc}.
@code{CHILL} is not currently maintained, and will almost
-certainly fail to compile. Note that this switch does not work with
-EGCS 1.1.2 or older versions of egcs. It is supported in GCC 2.95
-and newer versions.@*
+certainly fail to compile.@*
If you do not pass this flag, all languages available in the @file{gcc}
sub-tree will be configured. Re-defining @code{LANGUAGES} when calling
@samp{make bootstrap} @strong{does not} work anymore, as those
@@ -551,27 +562,27 @@ to use GCJ with some other run-time, or
separately, or it just happens not to build on your particular
machine. In general, if the Java front-end is enabled, the GCJ
libraries will be enabled too, unless they're known to not work on
-the target platform. If GCJ is enabled but libgcj isn't built, you
+the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
may need to port it; in this case, before modifying the top-level
-@file{configure.in} so that libgcj is enabled by default on this platform,
+@file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
you may use @option{--enable-libgcj} to override the default.
@item --with-dwarf2
Specify that the compiler should
-use DWARF2 debugging information as the default.
+use DWARF 2 debugging information as the default.
@item --enable-win32-registry
-@itemx --enable-win32-registry=@var{KEY}
+@itemx --enable-win32-registry=@var{key}
@itemx --disable-win32-registry
The @option{--enable-win32-registry} option enables Windows-hosted GCC
to look up installations paths in the registry using the following key:
@smallexample
-@code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{KEY}}
+@code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}}
@end smallexample
-@var{KEY} defaults to GCC version number, and can be overridden by the
-@option{--enable-win32-registry=@var{KEY}} option. Vendors and distributors
+@var{key} defaults to GCC version number, and can be overridden by the
+@option{--enable-win32-registry=@var{key}} option. Vendors and distributors
who use custom installers are encouraged to provide a different key,
perhaps one comprised of vendor name and GCC version number, to
avoid conflict with existing installations. This feature is enabled
@@ -625,16 +636,16 @@ which has target include files.
compiler, if @file{@var{prefix}/@var{target}/sys-include} doesn't pre-exist.
These include files will be copied into the @file{gcc} install directory.
Fixincludes will be run on these files to make them compatible with
-@command{gcc}.
+GCC.
@item --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}''
Specifies a list of directories which contain the target runtime
libraries. These libraries will be copied into the @file{gcc} install
directory.
@item --with-newlib
-Specifies that ``newlib'' is
+Specifies that @samp{newlib} is
being used as the target C library. This causes @code{__eprintf} to be
-omitted from libgcc.a on the assumption that it will be provided by
-newlib.
+omitted from @file{libgcc.a} on the assumption that it will be provided by
+@samp{newlib}.
@end table
Note that each @option{--enable} option has a corresponding
@@ -724,7 +735,7 @@ gperf.
@item
Build target tools for use by the compiler such as binutils (bfd,
-binutils, gas, gprof, ld, and opcodes)@*
+binutils, gas, gprof, ld, and opcodes)
if they have been individually linked
or moved into the top level GCC source tree before configuring.
@@ -753,8 +764,8 @@ without debugging information with @samp
roughly 40% of disk space both for the bootstrap and the final installation.
(Libraries will still contain debugging information.)
-If you wish to use non-default flags when compiling the stage2 and
-stage3 compile, set @code{BOOT_CFLAGS} on the command line when doing
+If you wish to use non-default GCC flags when compiling the stage2 and
+stage3 compilers, set @code{BOOT_CFLAGS} on the command line when doing
@samp{make bootstrap}. Non-default optimization flags are less well
tested here than the default of @samp{-g -O2}, but should still work.
In a few cases, you may find that you need to specify special flags such
@@ -768,11 +779,11 @@ If you used the flag @option{--enable-la
the compilers to be built, only those you've actually enabled will be
built. This will of course only build those runtime libraries, for
which the particular compiler has been built. Please note,
-that re-defining LANGUAGES when calling @samp{make bootstrap}
+that re-defining @env{LANGUAGES} when calling @samp{make bootstrap}
@strong{does not} work anymore!
If the comparison of stage2 and stage3 fails, this normally indicates
-that the stage 2 compiler has compiled GCC incorrectly, and is therefore
+that the stage2 compiler has compiled GCC incorrectly, and is therefore
a potentially serious bug which you should investigate and report. (On
a few systems, meaningful comparison of object files is impossible; they
always appear ``different''. If you encounter this problem, you will
@@ -850,10 +861,6 @@ the number of processors in your machine
@cindex Installing GCC: Testing
@cindex Testsuite
-@strong{Please note that this is only applicable
-to current development versions of GCC and GCC 3.0 or later.
-GCC 2.95.x does not come with a testsuite.}
-
Before you install GCC, you might wish to run the testsuite. This
step is optional and may require you to download additional software.
@@ -867,11 +874,6 @@ dejagnu 1.3 is not sufficient.
Now you may need specific preparations:
@itemize @bullet
-@item
-In order to run the libio tests in GCC 2.95 and earlier versions of GCC
-on targets which do not fully
-support Unix/POSIX commands (e.g. Cygwin), the references to the @file{dbz}
-directory have to be deleted from @file{libio/configure.in}.
@item
The following environment variables may need to be set appropriately, as in
@@ -899,27 +901,27 @@ Finally, you can run the testsuite (whic
@end example
The testing process will try to test as many components in the GCC
-distribution as possible, including the C, C++, Objective C and Fortran
+distribution as possible, including the C, C++, Objective-C and Fortran
compilers as well as the C++ and Java runtime libraries.
@section How can I run the test suite on selected tests?
As a first possibility to cut down the number of tests that are run it is
possible to use @samp{make check-gcc} or @samp{make check-g++}
-in the gcc subdirectory of the object directory. To further cut down the
+in the @file{gcc} subdirectory of the object directory. To further cut down the
tests the following is possible:
@example
make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
@end example
-This will run all gcc execute tests in the testsuite.
+This will run all @command{gcc} execute tests in the testsuite.
@example
make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
@end example
-This will run the g++ ``old-deja'' tests in the testsuite where the filename
+This will run the @command{g++} ``old-deja'' tests in the testsuite where the filename
matches @samp{9805*}.
The @file{*.exp} files are located in the testsuite directories of the GCC
@@ -997,8 +999,10 @@ should look here first if you think your
@chapter Installing GCC: Final installation
@end ifnothtml
-Now that GCC has been built and tested, you can install it with
-@samp{cd @var{objdir}; make install}.
+Now that GCC has been built (and optionally tested), you can install it with
+@example
+cd @var{objdir}; make install
+@end example
That step completes the installation of GCC; user level binaries can
be found in @file{@var{prefix}/bin} where @var{prefix} is the value you
@@ -1014,11 +1018,11 @@ info format in @file{@var{infodir}} (nor
If you don't mind, please quickly review the
@uref{http://gcc.gnu.org/gcc-3.0/buildstat.html,,build status page}.
If your system is not listed, send a note to
-@uref{mailto:gcc@@gcc.gnu.org,,gcc@@gcc.gnu.org} indicating
+@email{gcc@@gcc.gnu.org} indicating
that you successfully built and installed GCC.
Include the output from running @file{@var{srcdir}/config.guess}. (Do
-not send us the config.guess file itself, just the one-line output from
+not send us the @file{config.guess} file itself, just the one-line output from
running it!)
If you find a bug, please report it following our
@@ -1369,7 +1375,7 @@ not yet implemented for the 1750A.)
The @code{as1750} assembler requires the file @file{ms1750.inc}, which is
found in the directory @file{config/1750a}.
-GNU CC produced the same sections as the Fairchild F9450 C Compiler,
+GCC produced the same sections as the Fairchild F9450 C Compiler,
namely:
@table @code
@@ -1389,7 +1395,7 @@ Initialization section (code to copy KRE
The smallest addressable unit is 16 bits (BITS_PER_UNIT is 16). This
means that type @code{char} is represented with a 16-bit word per character.
The 1750A's ``Load/Store Upper/Lower Byte'' instructions are not used by
-GNU CC.
+GCC.
@html
</p>
@@ -1461,16 +1467,16 @@ we need to use the old assembler, invoke
Compaq C Compiler:
@example
- % CC=cc @var{srcdir}/configure [@var{target}] [@var{options}]
+ % CC=cc @var{srcdir}/configure [@var{options}] [@var{target}]
@end example
or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
@example
- % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{target}] [@var{options}]
+ % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{options}] [@var{target}]
@end example
-GNU CC writes a @samp{.verstamp} directive to the assembler output file
+GCC writes a @samp{.verstamp} directive to the assembler output file
unless it is built as a cross-compiler. It gets the version to use from
the system header file @file{/usr/include/stamp.h}. If you install a
new version of DEC Unix, you should rebuild GCC to pick up the new version
@@ -1495,14 +1501,14 @@ unless the comparisons fail without that
@option{-save-temps}, you will have to manually delete the @samp{.i} and
@samp{.s} files after each series of compilations.
-GNU CC now supports both the native (ECOFF) debugging format used by DBX
+GCC now supports both the native (ECOFF) debugging format used by DBX
and GDB and an encapsulated STABS format for use only with GDB. See the
discussion of the @option{--with-stabs} option of @file{configure} above
for more information on these formats and how to select them.
There is a bug in DEC's assembler that produces incorrect line numbers
for ECOFF format when the @samp{.align} directive is used. To work
-around this problem, GNU CC will not emit such alignment directives
+around this problem, GCC will not emit such alignment directives
while writing ECOFF format debugging information even if optimization is
being performed. Unfortunately, this has the very undesirable
side-effect that code addresses when @option{-O} is specified are
@@ -2090,11 +2096,11 @@ These problems don't exist in operating
<hr>
@end html
@heading @anchor{*-lynx-lynxos}*-lynx-lynxos
-LynxOS 2.2 and earlier comes with GNU CC 1.x already installed as
+LynxOS 2.2 and earlier comes with GCC 1.x already installed as
@file{/bin/gcc}. You should compile with this instead of @file{/bin/cc}.
-You can tell GNU CC to use the GNU assembler and linker, by specifying
+You can tell GCC to use the GNU assembler and linker, by specifying
@samp{--with-gnu-as --with-gnu-ld} when configuring. These will produce
-COFF format object files and executables; otherwise GNU CC will use the
+COFF format object files and executables; otherwise GCC will use the
installed tools, which produce @file{a.out} format executables.
@html
@@ -2191,8 +2197,8 @@ This configuration is intended for embed
@end html
@heading @anchor{m68000-hp-bsd}m68000-hp-bsd
HP 9000 series 200 running BSD. Note that the C compiler that comes
-with this system cannot compile GNU CC; contact @email{law@@cygnus.com}
-to get binaries of GNU CC for bootstrapping.
+with this system cannot compile GCC; contact @email{law@@cygnus.com}
+to get binaries of GCC for bootstrapping.
@html
</p>
@@ -2231,7 +2237,7 @@ that configuration with + the @option{--
options to @code{configure}.
Note the C compiler that comes
-with this system cannot compile GNU CC. You can find binaries of GNU CC
+with this system cannot compile GCC. You can find binaries of GCC
for bootstrapping on @code{jagubox.gsfc.nasa.gov}.
You will also a patched version of @file{/bin/ld} there that
raises some of the arbitrary limits found in the original.
@@ -2241,7 +2247,7 @@ raises some of the arbitrary limits foun
<hr>
@end html
@heading @anchor{m68k-att-sysv}m68k-att-sysv
-AT&T 3b1, a.k.a. 7300 PC. This version of GNU CC cannot
+AT&T 3b1, a.k.a. 7300 PC. This version of GCC cannot
be compiled with the system C compiler, which is too buggy.
You will need to get a previous version of GCC and use it to
bootstrap. Binaries are available from the OSU-CIS archive, at
@@ -2252,7 +2258,7 @@ bootstrap. Binaries are available from
<hr>
@end html
@heading @anchor{m68k-bull-sysv}m68k-bull-sysv
-Bull DPX/2 series 200 and 300 with BOS-2.00.45 up to BOS-2.01. GNU CC works
+Bull DPX/2 series 200 and 300 with BOS-2.00.45 up to BOS-2.01. GCC works
either with native assembler or GNU assembler. You can use
GNU assembler with native coff generation by providing @option{--with-gnu-as} to
the configure script or use GNU assembler with dbx-in-coff encapsulation
@@ -2269,7 +2275,7 @@ Use @samp{configure unos} for building o
The Unos assembler is named @code{casm} instead of @code{as}. For some
strange reason linking @file{/bin/as} to @file{/bin/casm} changes the
-behavior, and does not work. So, when installing GNU CC, you should
+behavior, and does not work. So, when installing GCC, you should
install the following script as @file{as} in the subdirectory where
the passes of GCC are installed:
@@ -2279,12 +2285,12 @@ casm $*
@end example
The default Unos library is named @file{libunos.a} instead of
-@file{libc.a}. To allow GNU CC to function, either change all
+@file{libc.a}. To allow GCC to function, either change all
references to @option{-lc} in @file{gcc.c} to @option{-lunos} or link
@file{/lib/libc.a} to @file{/lib/libunos.a}.
@cindex @code{alloca}, for Unos
-When compiling GNU CC with the standard compiler, to overcome bugs in
+When compiling GCC with the standard compiler, to overcome bugs in
the support of @code{alloca}, do not use @option{-O} when making stage 2.
Then use the stage 2 compiler with @option{-O} to make the stage 3
compiler. This compiler will have the same characteristics as the usual
@@ -2306,7 +2312,7 @@ and linking from that library.
@end html
@heading @anchor{m68k-hp-hpux}m68k-hp-hpux
HP 9000 series 300 or 400 running HP-UX. HP-UX version 8.0 has a bug in
-the assembler that prevents compilation of GNU CC. This
+the assembler that prevents compilation of GCC. This
bug manifests itself during the first stage of compilation, while
building @file{libgcc2.a}:
@@ -2368,14 +2374,14 @@ to look like:
Current GCC versions probably do not work on version 2 of the NeXT
operating system.
-On NeXTStep 3.0, the Objective C compiler does not work, due,
+On NeXTSTEP 3.0, the Objective-C compiler does not work, due,
apparently, to a kernel bug that it happens to trigger. This problem
does not happen on 3.1.
You absolutely @strong{must} use GNU sed and GNU make on this platform.
-On NEXTSTEP 3.x where x < 3 the build of GCC will abort during
+On NeXTSTEP 3.x where x < 3 the build of GCC will abort during
stage1 with an error message like this:
@example
@@ -2458,7 +2464,7 @@ compiler. If the stage 3 and stage 4 ob
suggests you encountered a problem with the standard C compiler; the
stage 3 and 4 compilers may be usable.
-It is best, however, to use an older version of GNU CC for bootstrapping
+It is best, however, to use an older version of GCC for bootstrapping
if you have one.
@html
@@ -2872,8 +2888,8 @@ switch by using the configure option @op
@end html
@heading @anchor{romp-*-aos}romp-*-aos, romp-*-mach
The only operating systems supported for the IBM RT PC are AOS and
-MACH. GNU CC does not support AIX running on the RT. We recommend you
-compile GNU CC with an earlier version of itself; if you compile GNU CC
+MACH. GCC does not support AIX running on the RT. We recommend you
+compile GCC with an earlier version of itself; if you compile GCC
with @code{hc}, the Metaware compiler, it will work, but you will get
mismatches between the stage 2 and stage 3 compilers in various files.
These errors are minor differences in some floating-point constants and
@@ -3142,7 +3158,7 @@ system's linker seems to be unable to ha
debugging information.
The system's compiler runs out of capacity when compiling @file{stmt.c}
-in GNU CC. You can work around this by building @file{cpp} in GNU CC
+in GCC. You can work around this by building @file{cpp} in GCC
first, then use that instead of the system's preprocessor with the
system's C compiler to compile @file{stmt.c}. Here is how:
@@ -3153,7 +3169,7 @@ echo '/lib/cpp.gnu -traditional $@{1+"$@
chmod +x /lib/cpp
@end smallexample
-The system's compiler produces bad code for some of the GNU CC
+The system's compiler produces bad code for some of the GCC
optimization files. So you must build the stage 2 compiler without
optimization. Then build a stage 3 compiler with optimization.
That executable should work. Here are the necessary commands: