On Wed, Dec 05, 2007 at 11:37:59PM -0500, Dennis Clarke wrote:
> I go hunting through src/modules/elf.c to find the calls that require libmd
> but it is not obvious. Either that .. or I simply don't know what to look
> for.
>
> It is quite frustrating.
If you build on a system with libmd, and enable direct binding at link
time:
cc -B direct -G -lelf -lmd elf.o liblist.o elfextract.o -o elf.so
then the .SUNW_syminfo section of elf.so will contain a list of symbols
that need binding, as well as what object the symbol can be resolved in.
Then elfdump -y will dump that section:
% elfdump -y elf.so | grep libmd
[16] DBL [3] libmd.so.1 SHA1Final
[42] DBL [3] libmd.so.1 SHA1Init
[45] DBL [3] libmd.so.1 SHA1Update
I've no idea how much of this is available on releases prior to Nevada.
> By the way, as an aside, I spent some time trying to figure out how to
> create an ELF binary that would return osabi of "none".
What do you get for osabi on your binaries? What does "od -x <file> | head
-1" give for a binary with osabi != none? They're certainly none for
everything here ...
Danek
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
