Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 4 Jan 2012 23:58:15 +0100
From:      Luigi Rizzo <rizzo@iet.unipi.it>
To:        Garrett Cooper <yanegomi@gmail.com>
Cc:        current@freebsd.org
Subject:   Re: add 'ldd' to cross-tools ?
Message-ID:  <20120104225815.GA73964@onelab2.iet.unipi.it>
In-Reply-To: <CAGH67wR8WCimVp8tn4MY=7=BWUubjma1Cjcsj0%2BqEqo4StK_wg@mail.gmail.com>
References:  <20120104222315.GA73613@onelab2.iet.unipi.it> <CAGH67wR0jwr9vtJWNCB=-947TSAxciEf971m4keNNkwxvO9SeQ@mail.gmail.com> <20120104222955.GA73868@onelab2.iet.unipi.it> <CAGH67wR8WCimVp8tn4MY=7=BWUubjma1Cjcsj0%2BqEqo4StK_wg@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 04, 2012 at 02:30:27PM -0800, Garrett Cooper wrote:
> On Wed, Jan 4, 2012 at 2:29 PM, Luigi Rizzo <rizzo@iet.unipi.it> wrote:
...
> >> $ objdump -x `which tar` | awk '$1 == "NEEDED" { print $2 }'
> >> libarchive.so.5
> >> libbz2.so.4
> >> libz.so.6
> >> liblzma.so.5
> >> libbsdxml.so.4
> >> libcrypto.so.6
> >> libc.so.7
> >
> > wonderful, thanks!
> 
>     Np! The only gap with both of these tools is that you have to
> watch out for dl_open'ed binaries as they won't show up in ldd/objdump
> -x. If I could figure out how to detect these with a command line
> tool, I would be set for life :).

and the other thing, i just realized, is that once you locate
the libraries you should run objdump recursively to find
out further dependencies. Perhaps ldd sorts this out by itself ?

cheers
luigi



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120104225815.GA73964>