This is the mail archive of the
binutils@sourceware.cygnus.com
mailing list for the binutils project.
Re: Retreiving dynamic links through BFD
- To: jbailey@nisa.net
- Subject: Re: Retreiving dynamic links through BFD
- From: Ian Lance Taylor <ian@airs.com>
- Date: 24 May 1999 00:09:14 -0400
- CC: binutils@sourceware.cygnus.com
- References: <19990523203945.A8285@sparky.nisa.net>
Date: Sun, 23 May 1999 20:39:45 -0700
From: Jeff Bailey <jbailey@nisa.net>
I'm trying to find a way to list the library dependancies of an
executable. Unfortunetly this information seems to be only located in
the private-headers section (viewable through objdump -p). elf.c defines
the list of them through DT_NEEDED, and peicode.h shows the list of dll's
using bfd_get_32 calls. Is there any abstraction layer that will provide
this information?
Not in BFD.
BFD isn't a general ELF reading library. The dynamic information in
an ELF executable or shared library is ELF specific. I'm not aware of
any other object file format with anything comparable.
I suppose one could make a generic routine which somehow returned a
list of required shared libraries. I wouldn't be averse to such a
patch.
You could also use libelf.
Ian