From: "Dan Wilder" <Dan.Wilder@eng.watchguard.com>
To: "peter" <peter@piments.com>, "Crossgcc list" <crossgcc@sourceware.org>
Subject: RE: how to get target ldd ?
Date: Sat, 06 Jun 2009 17:09:00 -0000 [thread overview]
Message-ID: <7C3D15DD6E8F464998CA1470D8A322F3386132@ES02CO.wgti.net> (raw)
In-Reply-To: <4A2A160E.7090400@piments.com>
Maybe nyou can, but LDD is a shell script, and you can grab almost any
old copy of it.
Very likely you can get the same effect on your command using the
command line
LD_TRACE_LOADED_OBJECTS=1 your-command-here
which is the heart of ldd. Don't set LD_TRACE_LOADED_OBJECTS on a
command line by itself!
--
Dan Wilder
-----Original Message-----
From: crossgcc-owner@sourceware.org
[mailto:crossgcc-owner@sourceware.org] On Behalf Of peter
Sent: Saturday, June 06, 2009 12:09 AM
To: Crossgcc list
Subject: how to get target ldd ?
Hi,
I am having problems with a busybox ARM target I have build using ct-ng.
None of the executables , including busybox, seem to work unless I
build them static.
Unfortunately the rather trimmed down error handling in BB is more of a
distraction than a help in finding where the real problem lies.
Is there a way to get ldd for the target system out of ct-ng?
TIA, Peter.
--
For unsubscribe information see http://sourceware.org/lists.html#faq
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2009-06-06 17:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-06 7:09 peter
2009-06-06 17:09 ` Dan Wilder [this message]
2009-06-07 16:56 ` Yann E. MORIN
2009-06-09 22:17 ` ng
2009-06-10 6:01 ` Yann E. MORIN
2009-06-10 7:08 ` ng
2009-06-10 21:29 ` ng
2009-06-11 20:39 ` Yann E. MORIN
2009-06-12 8:03 ` ng
2009-06-10 8:34 Nebojša Ćosić
2009-06-10 14:48 ` Dan Wilder
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=7C3D15DD6E8F464998CA1470D8A322F3386132@ES02CO.wgti.net \
--to=dan.wilder@eng.watchguard.com \
--cc=crossgcc@sourceware.org \
--cc=peter@piments.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).