Compiling busybox for ARM-V7

[Vered Zvi]

Hello Bob, Kang-Che,

Your tip did the work !
Once compiled with:
export ARCH=arm
export CROSS_COMPILE=path to compiler

I got a root file system that the kernel managed to run.

Your help is highly appreciated,
Best regards,
Z.V
________________________________________
From: Bob Dunlop [bob.dunlop at xyzzy.org.uk]
Sent: Friday, January 06, 2017 1:54 PM
To: Vered Zvi
Cc: busybox at busybox.net
Subject: Re: Compiling busybox for ARM-V7

On Fri, Jan 06 at 04:07, Vered Zvi wrote:
> 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

I'm not sure passing the parameters to make like this works,
they don't get passed to sub processes ?  I've always set them
in the environment so all children are guaranteed to see them.

I'd stick the commands in a scripts for easy repetition and tweaking.
Something like this:

  #!/bin/bash

  # Export cross build parameters to environment
  export ARCH=arm
  export CROSS_COMPILE=arm-cortex_a15-linux-gnueabihf-

  # Put compiler bin in the front of my PATH (automatically exported)
  TOOLCHAIN=/home/zvivered/module/CARD/linux4.1.13/toolchain
  PATH=$TOOLCHAIN/crosstool/release/bin:$PATH

  # Build
  make clean
  make defconfig
  make

  # Use absolute path for install directory
  make CONFIG_PREFIX=$(pwd)/../../../rootfs install

Hope this helps
--
        Bob Dunlop
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.