public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Vered Zvi <veredz@elta.co.il>
To: "crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: ldd for busybox compiled for arm
Date: Tue, 03 Jan 2017 21:49:00 -0000	[thread overview]
Message-ID: <1EFFBDE6584C794F8A0ADF2CAC8D60E09F909C3C@eltidex2.elta.co.il> (raw)


Hello,

Using crosstool-ng 1.22.0 I created a toolchain for:  arm-cortex_a15-linux-gnueabi
The host is Centos 7.2.1511 (64)

Using this toolchain I compiled busybox.
make ARCH=arm CROSS_COMPILE=../../../../toolchain/crosstool/release/bin/arm-cortex_a15-linux-gnueabihf- defconfig
make ARCH=arm CROSS_COMPILE=../../../../toolchain/crosstool/release/bin/arm-cortex_a15-linux-gnueabihf-

Is it possible to use ldd from this toolchain to find out the dependencies for /bin/sh , /sbin/init ?

Strange: both /bin/sh, /sbin/init run under x86.
How it is possible ?
They were compiled for ARM.

Thank you,
Z.V
The information contained in this communication is proprietary to Israel Aerospace Industries Ltd. and/or third parties, may contain confidential or privileged information, and is intended only for the use of the intended addressee thereof. If you are not the intended addressee, please be aware that any use, disclosure, distribution and/or copying of this communication is strictly prohibited. If you receive this communication in error, please notify the sender immediately and delete it from your computer.

             reply	other threads:[~2017-01-03 21:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-03 21:49 Vered Zvi [this message]
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

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=1EFFBDE6584C794F8A0ADF2CAC8D60E09F909C3C@eltidex2.elta.co.il \
    --to=veredz@elta.co.il \
    --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).