Commit 7d4f6041 by Nathanael Nerode

collect2.texi: GNU CC -> GCC.

	* doc/collect2.texi: GNU CC -> GCC.
	* doc/headerdirs.texi: GNU CC -> GCC.

From-SVN: r66933
parent 8b87bb96
2003-05-18 Nathanael Nerode <neroden@gcc.gnu.org>
* doc/collect2.texi: GNU CC -> GCC.
* doc/headerdirs.texi: GNU CC -> GCC.
2003-05-18 Gabriel Dos Reis <gdr@integrable-solutions.net> 2003-05-18 Gabriel Dos Reis <gdr@integrable-solutions.net>
* hashtable.h (struct ht_identifier): Add data member "hash_value". * hashtable.h (struct ht_identifier): Add data member "hash_value".
......
...@@ -5,7 +5,7 @@ ...@@ -5,7 +5,7 @@
@node Collect2 @node Collect2
@chapter @code{collect2} @chapter @code{collect2}
GNU CC uses a utility called @code{collect2} on nearly all systems to arrange GCC uses a utility called @code{collect2} on nearly all systems to arrange
to call various initialization functions at start time. to call various initialization functions at start time.
The program @code{collect2} works by linking the program once and The program @code{collect2} works by linking the program once and
......
...@@ -6,28 +6,27 @@ ...@@ -6,28 +6,27 @@
@chapter Standard Header File Directories @chapter Standard Header File Directories
@code{GCC_INCLUDE_DIR} means the same thing for native and cross. It is @code{GCC_INCLUDE_DIR} means the same thing for native and cross. It is
where GNU CC stores its private include files, and also where GNU CC where GCC stores its private include files, and also where GCC
stores the fixed include files. A cross compiled GNU CC runs stores the fixed include files. A cross compiled GCC runs
@code{fixincludes} on the header files in @file{$(tooldir)/include}. @code{fixincludes} on the header files in @file{$(tooldir)/include}.
(If the cross compilation header files need to be fixed, they must be (If the cross compilation header files need to be fixed, they must be
installed before GNU CC is built. If the cross compilation header files installed before GCC is built. If the cross compilation header files
are already suitable for ISO C and GNU CC, nothing special need be are already suitable for GCC, nothing special need be done).
done).
@code{GPLUSPLUS_INCLUDE_DIR} means the same thing for native and cross. It @code{GPLUSPLUS_INCLUDE_DIR} means the same thing for native and cross. It
is where @command{g++} looks first for header files. The C++ library is where @command{g++} looks first for header files. The C++ library
installs only target independent header files in that directory. installs only target independent header files in that directory.
@code{LOCAL_INCLUDE_DIR} is used only by native compilers. GNU CC @code{LOCAL_INCLUDE_DIR} is used only by native compilers. GCC
doesn't install anything there. It is normally doesn't install anything there. It is normally
@file{/usr/local/include}. This is where local additions to a packaged @file{/usr/local/include}. This is where local additions to a packaged
system should place header files. system should place header files.
@code{CROSS_INCLUDE_DIR} is used only by cross compilers. GNU CC @code{CROSS_INCLUDE_DIR} is used only by cross compilers. GCC
doesn't install anything there. doesn't install anything there.
@code{TOOL_INCLUDE_DIR} is used for both native and cross compilers. It @code{TOOL_INCLUDE_DIR} is used for both native and cross compilers. It
is the place for other packages to install header files that GNU CC will is the place for other packages to install header files that GCC will
use. For a cross-compiler, this is the equivalent of use. For a cross-compiler, this is the equivalent of
@file{/usr/include}. When you build a cross-compiler, @file{/usr/include}. When you build a cross-compiler,
@code{fixincludes} processes any header files in this directory. @code{fixincludes} processes any header files in this directory.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment