Cannot build both gcc and new snapshot on i686-pc-linux-gnu

Benjamin Kosnik bkoz@cygnus.com
Sat Apr 1 00:00:00 GMT 2000


>I had this one myself -- forgot that the rebuilt libgcc.a doesn't get
>installed with 'make install'.  This should be highlighted.

Hmm. This is what I did, and everything is working correctly:

libstdc++2.90.8 + gcc-2.95.2. Re/move libstdc++/libio from
gcc-2.95.2. Link libstdc++-2.90.8 to libstdc++ as per install/build
instructions.

configure all of gcc.

After this is done do this in the build directory:

make all-target-libstdc++
make install-gcc
make install-target-libstdc++
make install-target-libiberty

Then set PATHs to the newly installed g++ and libstdc++. The correct
includes and libraries will be picked up automatically, including the
rebuilt libgcc.a 

(this can easily be verified by a "nm libgcc.a |grep exception" -- you
should see std as part of the mangled name, like this:

<bkoz@haight>
/mnt/hd/bliss/H-x86-libstdc++-namespaces/lib/gcc-lib/i586-pc-linux-gnu/2.95.2

%nm --demangle libgcc.a | grep "std::exception"
000004b4 T std::exception::~exception(void)
000004a4 T std::exception::exception(void)
00000000 W std::exception type_info function
00000008 C std::exception type_info node
00000000 W std::exception virtual table
00000480 T std::exception::what(void) const
         U std::exception type_info function
         U std::exception type_info node
         U std::exception virtual table
         U std::exception virtual table
         U std::exception type_info function
         U std::exception type_info node
         U std::exception virtual table
         U std::exception::what(void) const
)

The the testsuite files work as expected:

<bkoz@haight> /mnt/hd/bliss/src.libstdc++/testsuite                             %g++ -fhonor-std 17_intro/header_fstream.cc
<bkoz@haight> /mnt/hd/bliss/src.libstdc++/testsuite                             %

Anyway. I hope this is useful. 

Phil, the last bits from the install/build page should be removed
(Building and Installing the library (without GCC sources)), the build
instructions are already too complicated without that bit of
disinformation. . . . it's going to drive both of us nuts.

-benjamin


More information about the Libstdc++ mailing list