Problematic linking between glibc and shared libgcc

[H . J . Lu]

On Mon, Feb 19, 2001 at 11:58:33AM -0800, Ulrich Drepper wrote:
> ebiederm@xmission.com (Eric W. Biederman) writes:
> 
> > You as the system administrator should know that by not putting
> > libgcc_s.so in /lib that you are deliberately installing a half broken
> > gcc.  And for your uses it probably isn't a problem.
> 
> And note, it's not libgcc_s.so.  This DSO is versioned, via file names
> or internally.  Every time it changes on any supported platform the
> version number must be changed (unless you keep track of the version
> numbers for each platform individually which is a maintainer's
> nightmare).  This means you /lib directory (or whatever) will be
> filled up with different libgcc versions.  I've said all this before

Unless the shared libgcc is done in the glibc way. In that case, we
need only have one shared libgcc for all versions of gcc.

-- 
H.J. Lu (hjl@valinux.com)