Description
This is a tracking issue for building aarch64 images, meaning they run natively on linux/arm64 instead of linux/amd64, and what's confirmed to work, what needs to be fixed, and what's currently untested, so we can ensure the maintainers don't duplicate work, new contributors know where to start, and looking at what to patch for future builds. We can also likely add builds for PPC64LE, since almost all of the maintained packages that have install candidates for ARM64 also support PPC64LE. Currently, most of the linux GNU packages are/will be failing.
Note that the PPC64LE images are currently untested, but assumed to work.
Currently Succeeding
Builds of these images for aarch64 can be found here for debugging and testing purposes (these are not official images, not are they guaranteed to be stable).
aarch64-unknown-linux-gnu(x86_64, i686, arm64, ppc64le, depends on Add concept of a native Dockerfile. #982)s390x-unknown-linux-gnu(x86_64, i686, arm64, pp64le)arm-unknown-linux-gnueabi(x86_64, i686, arm64, pp64le)armv5te-unknown-linux-gnueabi(x86_64, i686, arm64, pp64le)armv7-unknown-linux-gnueabi(x86_64, i686, arm64, pp64le)armv7-unknown-linux-gnueabihf(x86_64, i686, arm64, pp64le)i586-unknown-linux-gnu(x86_64, arm64, pp64le)i686-unknown-linux-gnu(x86_64, i686, arm64, pp64le)powerpc64le-unknown-linux-gnu(x86_64, i686, arm64)riscv64gc-unknown-linux-gnu(x86_64, i686, arm64, ppc64le)x86_64-unknown-linux-gnu(x86_64, i686, arm64, ppc64le, depends on Add concept of a native Dockerfile. #982)aarch64-unknown-linux-musl(likely all architectures)arm-unknown-linux-musleabi(likely all architectures)arm-unknown-linux-musleabihf(likely all architectures)armv5te-unknown-linux-musleabi(likely all architectures)armv7-unknown-linux-musleabi(likely all architectures)armv7-unknown-linux-musleabihf(likely all architectures)i586-unknown-linux-musl(likely all architectures)i686-unknown-freebsd(likely all architectures)mips-unknown-linux-musl(likely all architectures)mips64-unknown-linux-muslabi64(likely all architectures)mips64el-unknown-linux-muslabi64(likely all architectures)mipsel-unknown-linux-musl(likely all architectures)sparcv9-sun-solaris(likely all architectures)thumbv6m-none-eabi(x86_64, armhf, arm64, pp64le, s390x)thumbv7em-none-eabi(x86_64, armhf, arm64, pp64le, s390x)thumbv7em-none-eabihf(x86_64, armhf, arm64, pp64le, s390x)thumbv7m-none-eabi(x86_64, armhf, arm64, pp64le, s390x)thumbv7neon-unknown-linux-gnueabihf(x86_64, armhf, arm64, pp64le, s390x)x86_64-unknown-freebsd(likely all architectures)
Currently Failing
arm-unknown-linux-gnueabihf(Unknown error in crosstool-ng build process)sparc64-unknown-linux-gnu(Unable to locate packageg++-sparc64-linux-gnu, not available for ARM64, will need a full compile from source)mips-unknown-linux-gnu(Package for ARM64 and PPC64LE only in 22.04+, not in 20.04)mips64-unknown-linux-gnuabi64(Unable to locate packageg++-mips64-linux-gnuabi64, not available for ARM64, will need a full compile from source)mips64el-unknown-linux-gnuabi64(Unable to locate packageg++-mips64el-linux-gnuabi64, not available for ARM64, will need a full compile from source)mipsel-unknown-linux-gnu(Unable to locate packageg++-mipsel-linux-gnu, not available for ARM64, will need a full compile from source)powerpc-unknown-linux-gnu(Unable to locate packageg++-powerpc-linux-gnu, not available for ARM64, only x86_64 and PPC64LE, will need a full compile from source)powerpc64-unknown-linux-gnu(Unable to locate packageg++-powerpc64-linux-gnu, not available for ARM64, will need a full compile from source)i686-pc-windows-gnu(unlikely to work without building WINE from source)x86_64-pc-windows-gnu(unlikely to work without building WINE from source)wasm32-unknown-emscripten(nolinux/arm64image for emsdk)x86_64-sun-solaris(fails while building GCC).
Failing, Cannot Fix
aarch64-linux-androidarm-linux-androideabiarmv7-linux-androideabii686-linux-androidthumbv7neon-linux-androideabix86_64-linux-android
The Android images have the following requirements, which means it will be impossible to build a cross-compiler for them without significant effort from a non-x86 host:
- They require
gcc-multilibandg++-multilib, which are not available on aarch64 and any host other than i686, x86_64, and s390x. - They use prebuilts for
clang,gccandgothat assume an x86 host. - The NDKs assume an x86_64 host.
The only solution therefore would be to rebuild the entire NDK from source, get Android system, replace the prebuilts with native toolchains for a non-x86 host, update code so it uses the correct non-x86 prebuilts, etc. If this sounds like an issue, it is.
Currently Untested
x86_64-unknown-dragonflyx86_64-unknown-illumosx86_64-unknown-linux-gnu:centosx86_64-unknown-linux-muslx86_64-unknown-netbsd
Contributing
If you'd like to contribute your own tests, successes, etc., feel free to do so with the following examples. The runners, std, C++, and dynamic library support can be found in the Github actions ci.yml.
# change this for specific targets
$ export TARGET=s390x-unknown-linux-gnu
$ cargo build-docker-image --platform linux/arm64/v8=aarch64-unknown-linux-gnu $TARGET
$ export CROSS_TARGET_S390X_UNKNOWN_LINUX_GNU_IMAGE_TOOLCHAIN="aarch64-unknown-linux-gnu"
$ export CROSS_TARGET_S390X_UNKNOWN_LINUX_GNU_IMAGE="ghcr.io/cross-rs/$TARGET:local"
$ export STD=1
$ export CPP=1
$ export DYLIB=1
$ export RUN=1
$ export RUNNERS="qemu-user qemu-system"
$ ci/test.sh