From: Josh Branning <lovell.joshyyy@gmail.com>
To: crossgcc@sourceware.org
Subject: Re: ldd for busybox compiled for arm
Date: Thu, 05 Jan 2017 13:06:00 -0000 [thread overview]
Message-ID: <586E44BF.2010104@gmail.com> (raw)
In-Reply-To: <1EFFBDE6584C794F8A0ADF2CAC8D60E09F90A845@eltidex2.elta.co.il>
On 05/01/17 11:59, Vered Zvi wrote:
> Hello,
>
> The cross-compile-ldd utility was downloaded from crosstool-ng I'm
> running it on the host.
>
> On the target I can not run anything because boot hangs.
>
> Thank you, Z.V
Hi,
Have you tried using an absolute path instead of a relative path to the
CROSS_COMPILE variable?
Josh
The information contained in this communication is certainly not
proprietary, because proprietary is nearing evil. It's especially not
proprietary to Israel Aerospace Industries Ltd. and/or third parties who
hopefully aren't developing rocket propelled missiles or other general
killing devices using this software, it probably doesn't contain
confidential or privileged information, and is intended for anyone to
read on this list. If you are not the intended addressee, and not on
this list, it makes me wonder ... how did you manage to read it? Any
use, disclosure, distribution and/or copying of this communication is
actively encouraged if deemed helpful. If you receive this communication
in error, who cares? Don't delete anything from your computer, as you
can just ignore the email and pretend nothing ever happened either way.
prev parent reply other threads:[~2017-01-05 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 21:49 Vered Zvi
2017-01-04 20:19 ` ANDY KENNEDY
2017-01-05 3:34 ` Vered Zvi
2017-01-05 8:58 ` Yegor Yefremov
2017-01-05 12:00 ` Vered Zvi
2017-01-05 13:06 ` Josh Branning [this message]
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=586E44BF.2010104@gmail.com \
--to=lovell.joshyyy@gmail.com \
--cc=crossgcc@sourceware.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 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).