All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] where is 'ldd'?
Date: Tue, 9 Jul 2013 12:40:30 +0200	[thread overview]
Message-ID: <20130709124030.530d3a3e@skate> (raw)
In-Reply-To: <CAAXf6LU3ShNk9JdG-eVv7Lt3OLopP5butkPK-8Mb4L+3gmRzxg@mail.gmail.com>

Dear Thomas De Schampheleire,

On Mon, 8 Jul 2013 18:49:40 +0200, Thomas De Schampheleire wrote:

> You really don't need a special ldd.
> ldd is just a script. In its most basic usage (ldd <executable>), it just runs:
> # LD_TRACE_LOADED_OBJECTS=1 <executable>
> 
> For example on busybox:
> # LD_TRACE_LOADED_OBJECTS=1 /bin/busybox
>         linux-vdso32.so.1 =>  (0x00100000)
>         libc.so.6 => /lib/libc.so.6 (0x0fe70000)
>         /lib/ld.so.1 (0x48000000
> 
> So for sporadic usage, an ldd script isn't even needed.

Right, but does this work with the uClibc dynamic loader? Anyway, if
those features don't exist with the uClibc dynamic loader, then
implementing ldd is simply impossible.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2013-07-09 10:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08 13:56 [Buildroot] where is 'ldd'? Woody Wu
2013-07-08 14:14 ` Zoltan Gyarmati
2013-07-08 14:27   ` Woody Wu
2013-07-08 16:49     ` Thomas De Schampheleire
2013-07-09  1:05       ` Woody Wu
2013-07-09 10:40       ` Thomas Petazzoni [this message]
2013-07-09 17:39         ` Thomas De Schampheleire
2013-07-09 17:43           ` Baruch Siach
2013-07-09 18:13             ` Thomas De Schampheleire
2013-07-10  7:18             ` Thomas Petazzoni

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=20130709124030.530d3a3e@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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.