Re: gcc 3.x test matrix

[Jakub Jelinek <jakub at redhat dot com>]

On Tue, Sep 04, 2001 at 02:15:12PM +0200, Jakub Jelinek wrote:
> Now the interesting point is how to make sure no < 3.0 newly compiled shared
> library/binary has __frame_state_for.
> Because if __frame_state_for is removed from libstdc++, it means
> the usual g++ linker line
> -lstdc++ -lm -lgcc -lc -lgcc
> will make sure __frame_state_for will be linked into output binary/library.
> Either pre-3.0 libgcc.a will have to include __frame_state_for and other
> stuff from glibc (thus it doesn't matter that __frame_state_for from glibc
> is not used), or will need 2 separate libstdc++'s
> (/usr/lib/gcc-lib/*/*/libstdc++.so which will have __register_*,
> __frame_state_for etc.) and /usr/lib/libstdc++-libc6*.so.3 which will not
> have it. libstdc++.so could be created with a script, which would rad
> libstdc++-libc6*.so.3's symbol table (and DT_ tags) and recreate smallest
> possible library with the same symbols (by using empty functions, etc.).
> Ideas?

Another option could be to have libgcc_d.a which would be libgcc.a minus
frame.o (or frame-dwarf2.o) and just modify specs so that if not -static,
-lgcc_d -lc -lgcc_d is used instead of -lgcc -lc -lgcc.

	Jakub