This is the mail archive of the
mailing list for the binutils project.
Re: Resolving symbols in dependent libraries
- From: Andrew Bell <andrew dot bell dot ia at gmail dot com>
- Cc: Binutils <binutils at sourceware dot org>
- Date: Tue, 1 Sep 2015 14:40:28 -0500
- Subject: Re: Resolving symbols in dependent libraries
- Authentication-results: sourceware.org; auth=none
- References: <CACJ51z04gF4sujV7OfFRXh7ZuVK+FGTnwwUYAXTiQDTzR+Q3_A at mail dot gmail dot com> <CAJimCsE3S4hAzs5kcaFMMN10TECCCMMTbiavZALJX4dQgBycFQ at mail dot gmail dot com> <mvmio8abfaz dot fsf at hawking dot suse dot de>
On Thu, Aug 20, 2015 at 2:16 AM, Andreas Schwab <email@example.com> wrote:
> Cary Coutant <firstname.lastname@example.org> writes:
> > In Solaris, you could do this by making a.so a filter library,
> > re-exporting the symbol B from b.so.
> Is that the same as ld --filter?
Alan suggested --copy-dt-needed-entries, and that works when specified
when linking the executable, but I'd like to stick something in the
library a.so so that things just work without forcing the library user
to resort to linker magic. On OSX I can use -reexport-l b. Is there
an equivalent on LInux or something that might get me there another
way? Is there some way I can reexport the symbols in b.so in a.so?
Not sure how Linux --filter helps. Maybe I'm just not sure how to use it.