compile libstdc++ 2.7.2?

compile libstdc++ 2.7.2?

[Frederick V. Heitkamp]

netscape: error in loading shared libraries: /lib/libstdc++.so.2.7.2: i
undefined symbol: __register_exceptions

Is is possible to make libstdc++ 2.7.2 run on a system that's been
converted to glibc 2.1?  I get the above error when trying to run 
netscape.

I remember reading somewhere that it's not possible to compile
the 2.7.2 libs with newer gcc/egcs.  Has there been a patch?

This are the libraries that netscape is linked against.

        libBrokenLocale.so.1 => /lib/libBrokenLocale.so.1 (0x40017000)
        libXt.so.6 => /usr/X11R6/lib/libXt.so.6 (0x4001a000)
        libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x40063000)
        libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x4006c000)
        libXmu.so.6 => /usr/X11R6/lib/libXmu.so.6 (0x40083000)
        libXpm.so.4 => /usr/X11R6/lib/libXpm.so.4 (0x40095000)
        libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x400a4000)
        libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x400af000)
        libdl.so.2 => /lib/libdl.so.2 (0x40154000)
        libc.so.6 => /lib/libc.so.6 (0x40157000)
        libg++.so.2.7.2 => /usr/local/lib/libg++.so.2.7.2 (0x4023c000)
        libstdc++.so.2.7.2 => /lib/libstdc++.so.2.7.2 (0x40274000)
        libm.so.6 => /lib/libm.so.6 (0x402a5000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
        libm.so.5 => /lib/libm.so.5 (0x402c1000)

Fred

Re: compile libstdc++ 2.7.2?

[Andreas Schwab]

"Frederick V. Heitkamp" <heitkamp@ibm.net> writes:

|> I remember reading somewhere that it's not possible to compile
|> the 2.7.2 libs with newer gcc/egcs.  Has there been a patch?

No.  What's wrong with using the supplied libstdc++ 2.8?

-- 
Andreas Schwab                                      "And now for something
schwab@issan.cs.uni-dortmund.de                      completely different"
schwab@gnu.org

Re: compile libstdc++ 2.7.2?

[Matthias Urlichs]

Hi,

Andreas Schwab:
> "Frederick V. Heitkamp" <heitkamp@ibm.net> writes:
> 
> |> I remember reading somewhere that it's not possible to compile
> |> the 2.7.2 libs with newer gcc/egcs.  Has there been a patch?
> 
> No.  What's wrong with using the supplied libstdc++ 2.8?

Netscape (and others) are explicitly linked against libstdc++ 2.7.
libstdc++ 2.7 contains old parts of libio which conflict with glibc 2.1.

We therefore need a way to recompile libstdc++ 2.7 so that old programs
continue to work. The only other alternative, as far as I can tell, is to
force everybody to recompile their program with libstdc++ 2.8 before we can
upgrade glibc to 2.1. This is a Bad Thing.

-- 
Matthias Urlichs  |  noris network GmbH   |   smurf@noris.de  |  ICQ: 20193661
The quote was selected randomly. Really.    |      http://www.noris.de/~smurf/
-- 
All's well that ends well.
                                        -- E. A. Poe

Re: compile libstdc++ 2.7.2?

[H.J. Lu]

> 
> Hi,
> 
> Andreas Schwab:
> > "Frederick V. Heitkamp" <heitkamp@ibm.net> writes:
> > 
> > |> I remember reading somewhere that it's not possible to compile
> > |> the 2.7.2 libs with newer gcc/egcs.  Has there been a patch?
> > 
> > No.  What's wrong with using the supplied libstdc++ 2.8?
> 
> Netscape (and others) are explicitly linked against libstdc++ 2.7.
> libstdc++ 2.7 contains old parts of libio which conflict with glibc 2.1.
> 
> We therefore need a way to recompile libstdc++ 2.7 so that old programs
> continue to work. The only other alternative, as far as I can tell, is to
> force everybody to recompile their program with libstdc++ 2.8 before we can
> upgrade glibc to 2.1. This is a Bad Thing.
> 

My netscape binary works just fine with glibc 2.1. Don't recompile
libg++ 2.7. Leave it alone. You should remove libg++.a and libg++.so
though.

-- 
H.J. Lu (hjl@gnu.org)

Re: compile libstdc++ 2.7.2?

[Joe Buck]

> > |> I remember reading somewhere that it's not possible to compile
> > |> the 2.7.2 libs with newer gcc/egcs.  Has there been a patch?
> > 
> > No.  What's wrong with using the supplied libstdc++ 2.8?
> 
> Netscape (and others) are explicitly linked against libstdc++ 2.7.
> libstdc++ 2.7 contains old parts of libio which conflict with glibc 2.1.

To fix that problem, "recompiling" (e.g. fixing just enough C++ syntax
bugs to get libstdc++ 2.7.x to build with egcs) would not suffice.  The
conflicts would still be present.

> We therefore need a way to recompile libstdc++ 2.7 so that old programs
> continue to work. 

Rather, you'd need to rip out all of the old libio stuff from 2.7,
replace it with new glibc 2.1-compatible stuff, and do this in a way
that programs that dynamically link with libstdc++ 2.7 will still work.
Not an easy task.

> The only other alternative, as far as I can tell, is to
> force everybody to recompile their program with libstdc++ 2.8 before we can
> upgrade glibc to 2.1. This is a Bad Thing.

Either that or they need some compatibility setup to run old binaries.

But then, the measures taken to make libstdc++ 2.7.x and Linux libc
happy with each other were hideous.