Version 11.2.1-1.2 is a maintenance release; it brings back support for parsing XML files in GDB, allowing it to auto-configure on target capabilities when connecting to J-Link GDB server and fixes libgcov.a, which resulted empty in the previous release.

The xPack GNU AArch64 Embedded GCC is a standalone cross-platform binary distribution of GNU AArch64 Embedded Toolchain.

There are separate binaries for Windows (Intel 64-bit), macOS (Intel 64-bit, Apple Silicon 64-bit) and GNU/Linux (Intel 64-bit, Arm 32/64-bit).


The binary files are available from GitHub Releases.


  • GNU/Linux Intel 64-bit: any system with GLIBC 2.27 or higher (like Ubuntu 18 or later, Debian 10 or later, RedHat 8 later, Fedora 29 or later, etc)
  • GNU/Linux Arm 32/64-bit: any system with GLIBC 2.27 or higher (like Raspberry Pi OS, Ubuntu 18 or later, Debian 10 or later, RedHat 8 later, Fedora 29 or later, etc)
  • Intel Windows 64-bit: Windows 7 with the Universal C Runtime (UCRT), Windows 8, Windows 10
  • Intel macOS 64-bit: 10.13 or later
  • Apple Silicon macOS 64-bit: 11.6 or later


The full details of installing the xPack GNU AArch64 Embedded GCC on various platforms are presented in the separate Install page.

Easy install

The easiest way to install Arm Embedded GCC is with xpm by using the binary xPack, available as @xpack-dev-tools/aarch64-none-elf-gcc from the registry.

With the xpm tool available, installing the latest version of the package and adding it as a dependency for a project is quite easy:

cd my-project
xpm init # Only at first use.

xpm install @xpack-dev-tools/aarch64-none-elf-gcc@latest

ls -l xpacks/.bin

To install this specific version, use:

xpm install @xpack-dev-tools/aarch64-none-elf-gcc@11.2.1-1.2.1

For xPacks aware tools, like the Eclipse Embedded C/C++ plug-ins, it is also possible to install Arm Embedded GCC globally, in the user home folder.

xpm install --global @xpack-dev-tools/aarch64-none-elf-gcc@latest --verbose

Eclipse will automatically identify binaries installed with xpm and provide a convenient method to manage paths.


To remove the links from the current project:

cd my-project

xpm uninstall @xpack-dev-tools/aarch64-none-elf-gcc

To completely remove the package from the central xPacks store:

xpm uninstall --global @xpack-dev-tools/aarch64-none-elf-gcc


The xPack GNU AArch64 Embedded GCC generally follows the official Arm Embedded GCC releases.

The current version is based on:

  • GNU AArch64 Embedded Toolchain release 11.2-2022.02 from February 15, 2022 and uses the same sources. It includes:
    • GCC 11.2.1
    • binutils 2.37
    • newlib 4.1.0
    • GDB 11.2

Supported libraries

The supported libraries are:

$ aarch64-none-elf-gcc -print-multi-lib


Compared to the Arm version, there should be no functional changes.

XML parsing in GDB

Some advanced GDB servers, like the one provided with SEGGER J-Link, are capable of passing an XML with the target capabilities to the GDB client. For unknown reasons, the Arm toolchain distribution came without XML parsing support. The xPack distribution brings back support for XML parsing and full integration with the SEGGER J-Link GDB server.


Support for Python scripting was added to GDB. This distribution provides a separate binary, aarch64-none-elf-gdb-py3 with support for Python 3.10.

The Python 3 run-time is included, so GDB does not need any version of Python to be installed, and is insensitive to the presence of other versions.

Text User Interface (TUI)

Support for TUI was added to GDB. The ncurses library was added to the distribution.

No Guile

Due to the difficulties of building standalone Guile libraries on all platforms, support for Guile scripting in GDB is currently not available.

Bug fixes

  • none


  • none

Known problems

  • none

Shared libraries

On all platforms the packages are standalone, and expect only the standard runtime to be present on the host.

All dependencies that are build as shared libraries are copied locally in the libexec folder (or in the same folder as the executable for Windows).


On GNU/Linux the binaries are adjusted to use a relative path:

$ readelf -d | grep runpath
 0x000000000000001d (RPATH)            Library rpath: [$ORIGIN]

In the GNU search strategy, the DT_RPATH has the highest priority, higher than LD_LIBRARY_PATH, so if this later one is set in the environment, it should not interfere with the xPack binaries.

Please note that previous versions, up to mid-2020, used DT_RUNPATH, which has a priority lower than LD_LIBRARY_PATH, and does not tolerate setting it in the environment.

@rpath and @loader_path

Similarly, on macOS, the binaries are adjusted with install_name_tool to use a relative path.


The original GNU GCC documentation is available online.


The binaries for all supported platforms (Windows, macOS and GNU/Linux) were built using the xPack Build Box (XBB), a set of build environments based on slightly older distributions, that should be compatible with most recent systems.

The scripts used to build this distribution are in:

  • distro-info/scripts

For the prerequisites and more details on the build procedure, please see the README-MAINTAINER page.

CI tests

Before publishing, a set of simple tests were performed on an exhaustive set of platforms. The results are available from:


The binaries were tested on a variety of platforms, but mainly to check the integrity of the build, not the compiler functionality.


The SHA-256 hashes for the files are:







Deprecation notices

32-bit support

Support for 32-bit Intel Linux and Intel Windows was dropped in 2022. Support for 32-bit Arm Linux (armv7l) will be preserved for a while, due to the large user base of 32-bit Raspberry Pi systems.

Linux minimum requirements

Support for RedHat 7 was dropped in 2022 and the minimum requirement was raised to GLIBC 2.27, available starting with Ubuntu 18, Debian 10 and RedHat 8.

Download analytics

Credit to Shields IO for the badges and to Somsubhra/github-release-stats for the individual file counters.