This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


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

Re: A completely different approach to EH runtime


On Wed, Feb 21, 2001 at 11:18:15PM -0800, Zack Weinberg wrote:
> On Thu, Feb 22, 2001 at 06:59:48AM +0000, Joern Rennecke wrote:
> > > If we add symbols to libgcc_s.so, they will have a different symbol
> > > version (GCC_3.1 or something).  The dynamic linker will be faced with
> > > 
> > >   binary uses: GCC_3.0 GCC_3.1
> > >   /lib/libgcc_s.so: GCC_3.0
> > >   /path/to/other/lib/libgcc_s.so: GCC_3.0 GCC_3.1
> > > 
> > > I don't know if it is intelligent enough, in this context, to link
> > > only the libgcc_s.so in /path/to/other/lib.  However, it will pick one
> > 
> > Couldn't you make the binary use only GCC_3.1 ?
> > Would that make it unambigous what to link?
> 
> It's not necessary.  If your binary needs only things like __muldi3,
> you'd like it to work with the old libgcc_s.so.
> 
> It is unambiguous which library to load, IMO; I just don't know if
> ld.so gets it right.
> 

The ld.so in glibc will check GCC_3.0 and GCC_3.1 AFTER libgcc_s.so
is loaded, not before. The directory search order is defined by the
gABI and we also added /etc/ld.so.conf, which is similar to a
system wide rpath.

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


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