Hello:
I'm sorry; I'm lost. I'm a newbie. All I understand is that the C++
header files and libraries were not installed during the GCC 4.3.0
installation process, but--and this seems contradictory to me--the g++
compiler *was* installed. That is, the g++ executable is in the bin
directory. Since the manual says that C, C++, and Fortran compilers are
installed by default, I went with the default options. And sure enough,
gcc, g++, and fortran executables are in the bin directory of the GCC
4.3.0 install.
Since I used GCC 4.1.0 to build GCC 4.3.0, I compared the directories
and contents of the 4.1.0 install with those from the 4.3.0 install, and
that's when I noticed that the libstdc++ libraries and the C++ header
files are *not* in the GCC 4.3.0 install path, but *are* in the 4.1.0
install path.
So, why would the g++ compiler be installed, but not the libraries or
the header files--that seems inconsistent to me?
Do I need to take additional steps? What am I doing wrong? How do I
get the C++ *environment* into the install directory?
I am most grateful for any tips, directions you can give me.
~chris
On Tue, May 13, 2008 at 3:52 PM, chris kuhlman <ckuhlman@xxxxxxxxxx> wrote:
I used GCC 4.1.0 to build GCC 4.3.0. So I looked under the install
directory for GCC 4.1.0, and under the include directory for GCC 4.1.0,
there is a c++ directory and a file called mf-runtime.h. Under the c++
directory is 4.1.0 and that directory appears to have all of the C++ header
files.
Do you know why I did not generate the directories and header files under
the include directory of GCC 4.3.0?
The *C compiler* has no business installing files that belong to the
*C library* (most likely GNU libc on a GNU/Linux host).
The reason you're seeing the C++ headers is that the GCC tarball
contains the C++ library. So really, when you install GCC, you're
really installing a C *compiler* and a complete C++ *environment*.
Hope that helps.
