From: Ivan Kuten <ivan.kuten@promwad.com>
To: buildroot@busybox.net
Subject: [Buildroot] ldd disappearing from rootfs
Date: Tue, 17 Nov 2009 12:11:19 +0200 [thread overview]
Message-ID: <4B0276C7.8020309@promwad.com> (raw)
In-Reply-To: <4B01CC01.2000907@free.fr>
Hello Julien,
Actually I do not remember the reason why I commented out
#$(TARGET_DIR)/usr/bin/ldd
Or may be it was trying to install into my /usr/bin/ replacing my native
host ldd.
Regards,
Ivan
> Hi,
>
> While searching why ldd disappeared from the /usr/bin/ of my target
> since I updated my Buildroot, I found that the rule installing it was
> commented by this commit:
> http://git.buildroot.net/buildroot/commit/?id=cb815ae003d40cc971d6e214415c10e9a160ba82
> (last chunk of the commit)
>
> Yes, I know, it's quite old now, but the ldd disappearing is on my TODO
> list since ages :-)
> Do somebody recall why this line was commented out ? (I don't see the
> link with the commit title)
>
> I have put Ivan (the author of the commit) in copy.
>
> Regards,
> Julien
>
>
>
>
next prev parent reply other threads:[~2009-11-17 10:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 22:02 [Buildroot] ldd disappearing from rootfs Julien Boibessot
2009-11-17 1:20 ` Kelvin Cheung
2009-11-17 10:11 ` Ivan Kuten [this message]
2009-11-17 16:38 ` Peter Korsgaard
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=4B0276C7.8020309@promwad.com \
--to=ivan.kuten@promwad.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