This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Linking against shared library linked to another shared one, please help

From: Ian Lance Taylor <ian at airs dot com>
To: matteo dot pampolini at seleniacomms dot com
Cc: binutils at sources dot redhat dot com
Date: 10 Mar 2005 17:39:42 -0500
Subject: Re: Linking against shared library linked to another shared one, please help
References: <OF19FFB83D.1814CE2A-ONC1256FC0.00598423-C1256FC0.0059EF86@SeleniaComms.com>

matteo.pampolini@seleniacomms.com writes:

> But my problem is not the linker warning, is the fact that the app doesn't
> link at all
> because of unresolved symbols (the ones implemented inside lb).

Does liba have a DT_NEEDED entry for libb?  You can find out using
objdump -p.

If you force the program to link using --allow-shlib-undefined, is it
possible to run the resulting program?  That is, does the dynamic
linker succeed and does the program run?  In particular, try it with
the LD_BIND_NOW environment variable set.

Ian

References:
- Re: Linking against shared library linked to another shared one, pleasehelp
  - From: matteo . pampolini

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