Compiling busybox for ARM-V7

[Vered Zvi]

Hello,

I compiled busybox 1.25.1 for ARM-V7 using crosstool-ng toolchain.

I used the commands:

TOOLCHAIN=/home/zvivered/module/CARD/linux4.1.13/toolchain
make clean
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-
make CONFIG_PREFIX=../../../rootfs install

Then I ran:  file busybox
and got:
./busybox: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=4789168febe33cdab87b3d932c0fdbf8d5c73e30, stripped

Does it make sense ?

The output of ldd is:

arm-cortex_a15-linux-gnueabihf-ldd busybox
        libm.so.6 => /lib/libm.so.6 (0xdeadbeef)
        libc.so.6 => /lib/libc.so.6 (0xdeadbeef)
        ld-linux-armhf.so.3 => /lib/ld-linux-armhf.so.3 (0xdeadbeef)

Also, the busybox utils are running on my centos (64) machine.
How is it possible that a utility compiled for ARM is running on an x86 machine ?

The reason I'm asking:
I created a ramdisk image from all busybox tree. Upon boot, linux display a fatal error:
/sbin/init exists but couldn't execute it (error -8)
/bin/sh exists but couldn't execute it (error -8)

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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/busybox/attachments/20170106/fc3600c3/attachment.html>