Preparing a Toolchain for Building ARM Binaries on x86 Hosts
  • 01 Oct 2021
  • 1 Minute to read
  • Dark
  • PDF

Preparing a Toolchain for Building ARM Binaries on x86 Hosts

  • Dark
  • PDF

Article Summary

Article Requires Update

This article requires an update to recent versions of software.


If you are building from source with Yocto, Yocto automatically builds a native toolchain from source. In many cases, you will also want to build binaries for 32-bit or 64-bit ARM targets without using Yocto to build a toolchain for you. The following steps will show you how to download and prepare your host with a Linaro toolchain.

Download the toolchain from Linaro

For 32-bit targets such as NXP i.MX6, i.MX6UL, and i.MX7, the toolchain you use depends on the version of kernel and bootloader, as well as the target processor architecture:

ToolchainU-bootLinux Kernel
GCC-4.6.2_201112U-boot 2013.10, U-boot 2014.103.0.35, 3.10.53
GCC-5.1_201508U-boot 2015.04, U-boot 2017.033.14.52, 4.1.15, 4.9.88

Currently, for 64-bit ARM targets such as PICO-IMX8M, we are using the following Linaro GCC toolchain, which can be downloaded from here:


Install the toolchain

We normally install the toolchain into the /opt directory on our Linux host:

tar xvf [toolchain-file.tar.xz] -C /opt/

Export the environment

When you are building a binary for target CPU architectures other than that of your host, you are cross-compiling. To do that with GCC, you should set up certain environment variables that are used by the other tools to ensure that you are calling the correct toolchain executables when building. For kernel and u-boot, you should also set the ARCH variable to the appropriate processor architecture.

export PATH=$PATH:/opt/[toolchain directory]/bin

For ARM64 (64-bit ARM) targets such as i.MX8M:

export ARCH=arm64
export CROSS_COMPILE=/opt/[toolchain directory]/bin/aarch64-linux-gnu-

For 32-bit ARM targets such as i.MX6 and i.MX7:

export ARCH=arm
export CROSS_COMPILE=/opt/[toolchain directory]/bin/arm-linux-gnueabihf-

You will need to do this in every Linux terminal in which you intend to build for your target.

Was this article helpful?