From: Uwe Geuder <jrswdnan22@snkmail.com>
To: yocto@yoctoproject.org
Subject: Re: ldd
Date: Tue, 22 May 2018 10:45:12 +0300 [thread overview]
Message-ID: <87lgcckubb.fsf@linux.suse> (raw)
Hi!
When searching for "yocto ldd" Google brings up this old posting
On Mon Nov 11 05:25:08 PST 2013 Chris Hallinan challinan at gmail.com wrote:
> On Sat, Nov 9, 2013 at 9:57 AM, Gary Thomas <gary at mlbassoc.com> wrote:
>
>> On 2013-11-09 06:42, Seth Bollinger wrote:
>>
>>> Hello All,
>>>
>>> I don't see that ldd is part of the cross toolchain build anywhere. Am I
>>> missing something?
>>>
>>
>> It's built with the eglibc recipe and is packaged separately.
>>
>>
Right, and the command to locate it is
$ oe-pkgdata-util find-path /usr/bin/ldd
ldd: /usr/bin/ldd
So the package name is indeed ldd.
>Gosh, I though ldd, originally a hard-to-maintain script, was obsoleted a
>long time ago. This command:
>
>$ readelf --dynamic <binary>
>
>provides the same information, and readelf can be found in every cross
>toolchain.
>
>-Chris
>
I don't think that is correct. readelf only shows static information
embedded into the binary. ldd does runtime lookup obeying e.g. the
LD_LIBRARY_PATH environment variable. It also has options -r and -u for
actually doing the relocations and it will report errors if they don't
succeed. So ldd is more useful than readelf for some use cases.
Regards,
Uwe Geuder
Neuro Event Labs Oy
Tampere, Finland
uwe.gexder@neuroeventlabs.com (Bot check: fix one obvious typo)
next reply other threads:[~2018-05-22 7:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 7:45 Uwe Geuder [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-11-09 13:42 ldd Seth Bollinger
2013-11-09 14:57 ` ldd Gary Thomas
2013-11-11 13:25 ` ldd Chris Hallinan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lgcckubb.fsf@linux.suse \
--to=jrswdnan22@snkmail.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.