Next:Memory Management and Type Information, Previous:collect2, Up:Introduction [Contents][Index]
GCC_INCLUDE_DIR means the same thing for native and cross. It iswhere GCC stores its private include files, and also where GCCstores the fixed include files. A cross compiled GCC runsfixincludes on the header files in$(tooldir)/include.(If the cross compilation header files need to be fixed, they must beinstalled before GCC is built. If the cross compilation header filesare already suitable for GCC, nothing special need be done).
GPLUSPLUS_INCLUDE_DIR means the same thing for native and cross. Itis whereg++ looks first for header files. The C++ libraryinstalls only target independent header files in that directory.
LOCAL_INCLUDE_DIR is used only by native compilers. GCCdoesn’t install anything there. It is normally/usr/local/include. This is where local additions to a packagedsystem should place header files.
CROSS_INCLUDE_DIR is used only by cross compilers. GCCdoesn’t install anything there.
TOOL_INCLUDE_DIR is used for both native and cross compilers. Itis the place for other packages to install header files that GCC willuse. For a cross-compiler, this is the equivalent of/usr/include. When you build a cross-compiler,fixincludes processes any header files in this directory.