This is the mail archive of the
binutils@sourceware.cygnus.com
mailing list for the binutils project.
Re: Relocs left in shared objects
- To: ibm-ppc-binutils at swox dot com
- Subject: Re: Relocs left in shared objects
- From: Geoff Keating <geoffk at cygnus dot com>
- Date: Wed, 15 Dec 1999 07:03:54 -0800
- CC: binutils at sourceware dot cygnus dot com, ibm-ppc-binutils at swox dot com
- References: <yszg0x4qosb.fsf@king.swox.se>
> Reply-To: ibm-ppc-binutils@swox.com
> Date: 15 Dec 1999 15:09:08 +0100
> One thing I don't understand is that when creating a shared library
> from two (or more) object files that have function calls crossing the
> object file boundaries, there are dynamic relocations for the
> branch/call in the resulting shared object that seem unnecessary to
> me. This is true for at least elf32-x86 and elf32-ppc.
>
> Shouldn't the link editor be able to resolve these references itself?
No. Those routines appear to be in the shared library, but the
application can override them. So ld.so must be able to see all the
calls.
--
- Geoffrey Keating <geoffk@cygnus.com>