#!/bin/sh set -e TARGET_ARCH="$1" SUDO_APK=abuild-apk # optional cross build packages : ${KERNEL_PKG=linux-firmware linux-lts} if [ -z "$TARGET_ARCH" ]; then program=$(basename $0) cat <&2 } if [ ! -d "$CBUILDROOT" ]; then msg "Creating sysroot in $CBUILDROOT" mkdir -p "$CBUILDROOT/etc/apk/keys" # /etc/apk/keys and ~/.abuild/ can contain files with the same names. # if that is the case, cp will abort copying and fail. Then on the next # run of the bootstrap script, 1) the keys are not in the sysroot and # 2) the apk database is not initialized the sysroot # Thus it's unusable at that point and needs to be deleted manually. cp -a /etc/apk/keys/* "$CBUILDROOT/etc/apk/keys" cp -a ~/.abuild/*.pub "$CBUILDROOT/etc/apk/keys" ${SUDO_APK} add --quiet --initdb --arch $TARGET_ARCH --root $CBUILDROOT fi msg "Building cross-compiler" # Build and install cross binutils (--with-sysroot) CTARGET=$TARGET_ARCH BOOTSTRAP=nobase APKBUILD=$(apkbuildname binutils) abuild -r if ! CHOST=$TARGET_ARCH BOOTSTRAP=nolibc APKBUILD=$(apkbuildname musl) abuild up2date 2>/dev/null; then # C-library headers for target CHOST=$TARGET_ARCH BOOTSTRAP=nocc APKBUILD=$(apkbuildname musl) abuild -r # Minimal cross GCC EXTRADEPENDS_HOST="musl-dev" \ CTARGET=$TARGET_ARCH BOOTSTRAP=nolibc APKBUILD=$(apkbuildname gcc) abuild -r # Cross build bootstrap C-library for the target EXTRADEPENDS_BUILD="gcc-pass2-$TARGET_ARCH" \ CHOST=$TARGET_ARCH BOOTSTRAP=nolibc APKBUILD=$(apkbuildname musl) abuild -r fi # Full cross GCC EXTRADEPENDS_TARGET="musl musl-dev" \ CTARGET=$TARGET_ARCH BOOTSTRAP=nobase APKBUILD=$(apkbuildname gcc) abuild -r # Cross build-base CTARGET=$TARGET_ARCH BOOTSTRAP=nobase APKBUILD=$(apkbuildname build-base) abuild -r msg "Cross building base system" # Implicit dependencies for early targets EXTRADEPENDS_TARGET="libgcc libstdc++ musl-dev" # On a few architectures like riscv64 we need to account for # gcc requiring -ltomic to be set explicitly if a C[++]11 program # uses atomics (e.g. #include ): # https://github.com/riscv/riscv-gnu-toolchain/issues/183#issuecomment-253721765 # The reason gcc itself is needed is because .so is in that package, # not in libatomic. if [ "$TARGET_ARCH" = "riscv64" ]; then NEEDS_LIBATOMIC="yes" fi for PKG in fortify-headers linux-headers musl libc-dev pkgconf zlib \ openssl ca-certificates libmd \ gmp mpfr4 mpc1 isl26 libucontext zstd binutils gcc \ libbsd busybox make \ apk-tools file \ libcap openrc alpine-conf alpine-baselayout alpine-keys alpine-base patch build-base \ attr acl fakeroot tar \ lzip abuild ncurses libedit openssh \ libcap-ng util-linux libaio lvm2 popt xz \ json-c argon2 cryptsetup kmod lddtree mkinitfs \ libffi \ brotli libev c-ares cunit nghttp2 curl \ libssh2 \ libxml2 pax-utils llvm14 community/ghc llvm16 rust \ $KERNEL_PKG ; do if [ "$NEEDS_LIBATOMIC" = "yes" ]; then EXTRADEPENDS_BUILD="libatomic gcc-$TARGET_ARCH g++-$TARGET_ARCH" fi EXTRADEPENDS_TARGET="$EXTRADEPENDS_TARGET" EXTRADEPENDS_BUILD="$EXTRADEPENDS_BUILD" \ CHOST=$TARGET_ARCH BOOTSTRAP=bootimage APKBUILD=$(apkbuildname $PKG) abuild -r case "$PKG" in fortify-headers | libc-dev) # Additional implicit dependencies once built EXTRADEPENDS_TARGET="$EXTRADEPENDS_TARGET $PKG" ;; gcc) if [ "$NEEDS_LIBATOMIC" = "yes" ]; then EXTRADEPENDS_TARGET="libatomic gcc $EXTRADEPENDS_TARGET" fi ;; build-base) # After build-base, that alone is sufficient dependency in the target EXTRADEPENDS_TARGET="busybox $PKG" ;; esac done