This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: A completely different approach to EH runtime
- To: Joern Rennecke <amylaar at cambridge dot redhat dot com>
- Subject: Re: A completely different approach to EH runtime
- From: "H . J . Lu" <hjl at valinux dot com>
- Date: Wed, 21 Feb 2001 22:34:17 -0800
- Cc: Alexandre Oliva <aoliva at redhat dot com>,Zack Weinberg <zackw at Stanford dot EDU>, gcc at gcc dot gnu dot org
- References: <20010221164718.C25980@valinux.com> <200102220503.f1M53pt19655@phal.cambridge.redhat.com>
On Thu, Feb 22, 2001 at 05:03:51AM +0000, Joern Rennecke wrote:
> >
> > On Wed, Feb 21, 2001 at 07:56:00PM -0300, Alexandre Oliva wrote:
> > > On Feb 21, 2001, "H . J . Lu" <hjl@valinux.com> wrote:
> > >
> > > > Just think about you have more than libc.so.6 on your Linux machine in
> > > > different direcories and they are both visibible to ld-linux.so.2. Can
> > > > you tell me what may happen?
> > >
> > > I see a few possible scenarios:
> > >
> > > - it picks the first one it finds.
> >
> > That won't work since some binaries may need the newest one.
>
> This would indicate that either the old library was broken - than you
> should replace it - or that the new library has additional functionality -
> than its minor version should be incremented; then the dynamic linker
> will pick the newer library for programs that have been linked with the
The ELF dynamic linker doesn't work this way. It will use the first
DSO with the right soname. You just have to make sure the right DSO
is found by the dynamic linker. With libc.so, we only have one in
/lib.
--
H.J. Lu (hjl@valinux.com)