Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] toolchain/toolchain-external: install ldd on the target
Date: Fri, 24 Apr 2020 14:16:25 +0200	[thread overview]
Message-ID: <20200424141625.5cd80421@windsurf.home> (raw)
In-Reply-To: <20200424120246.GJ5035@scaer>

On Fri, 24 Apr 2020 14:02:46 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:

> What does ldd bring that can't be already achieved? For example on my
> host system:
> 
>     $ ldd /bin/bash
>         linux-vdso.so.1 (0x00007ffea5be0000)
>         libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 (0x00007f2ea6fa0000)
>         libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f2ea6f9a000)
>         libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f2ea6da9000)
>         /lib64/ld-linux-x86-64.so.2 (0x00007f2ea7114000)
> 
>     $ LD_TRACE_LOADED_OBJECTS=1 /bin/bash
>         linux-vdso.so.1 (0x00007ffd3d3a7000)
>         libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 (0x00007f46883cd000)
>         libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f46883c7000)
>         libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f46881d6000)
>         /lib64/ld-linux-x86-64.so.2 (0x00007f4688419000)

I guess the main thing that it brings is that people know about "ldd"
in general, while nobody knows about LD_TRACE_LOADED_OBJECTS :)

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-04-24 12:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-22 15:34 [Buildroot] [PATCH 1/1] toolchain/toolchain-external: install ldd on the target Sébastien Szymanski
2020-04-24 12:02 ` Yann E. MORIN
2020-04-24 12:16   ` Thomas Petazzoni [this message]
2020-04-27 20:55 ` Yann E. MORIN

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=20200424141625.5cd80421@windsurf.home \
    --to=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox