This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: Problematic linking between glibc and shared libgcc

To: Thorsten Kukuk <kukuk at suse dot de>
Subject: Re: Problematic linking between glibc and shared libgcc
From: "H . J . Lu" <hjl at valinux dot com>
Date: Sat, 17 Feb 2001 00:15:11 -0800
Cc: Richard Henderson <rth at redhat dot com>,Ulrich Drepper <drepper at cygnus dot com>,Franz Sirl <Franz dot Sirl-kernel at lauterbach dot com>, gcc at gcc dot gnu dot org,libc-alpha at sources dot redhat dot com
References: <01021523111501.01075@enzo.bigblue.local> <m3bss38r2r.fsf@otr.mynet.cygnus.com> <20010216234821.D19905@redhat.com> <20010217090500.A21499@suse.de>

On Sat, Feb 17, 2001 at 09:05:00AM +0100, Thorsten Kukuk wrote:
> > 
> > > The best solution is to override the decision and not compile libgcc
> > > as a DSO.
> > 
> > You can do this on your own system of course: --disable-shared.
> > Don't expect that to ever be the default though.  I for one do
> > not think this is the best solution.
> 
> As far as I can see it is the only real solution :-(
> 

One solution is a published, well-defined and stable ABI for libgcc
so that gcc can use any implementation of the libgcc ABI. This
implementation can come from glibc :-). But I don't know if it will
ever happen.

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

References:
- Problematic linking between glibc and shared libgcc
  - From: Franz Sirl
- Re: Problematic linking between glibc and shared libgcc
  - From: Ulrich Drepper
- Re: Problematic linking between glibc and shared libgcc
  - From: Richard Henderson
- Re: Problematic linking between glibc and shared libgcc
  - From: Thorsten Kukuk

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]