No description
The PKGBUILD composes its target as "linux-$CARCH", giving linux-s390x. That IS a valid OpenSSL target -- it is the 31-bit one. The 64-bit target is linux64-s390x. This one hid well. The log ends on Configuring OpenSSL version 3.6.3 for target linux-s390x and then fails, with the failure appearing to come from nowhere: the target name is right there, it looks correct, and nothing says the build is 31-bit on a 64-bit system. Four rounds of keyword grepping found nothing, because the answer was not in the log at all -- it was in the PKGBUILD, one line above the command that printed it. The PKGBUILD already special-cases exactly this for riscv64, so s390x joins that case rather than getting a mechanism of its own. filesystem now builds: the gid 11 the host was missing was the whole of it. --- FR --- Le PKGBUILD compose sa cible en « linux-$CARCH », ce qui donne linux-s390x. C EST une cible OpenSSL valide -- celle du 31 bits. La cible 64 bits s appelle linux64-s390x. Celle-la se cachait bien. Le journal s acheve sur Configuring OpenSSL version 3.6.3 for target linux-s390x puis echoue, et l echec semble venir de nulle part : le nom de la cible est la, il a l air juste, et rien ne dit qu on batit du 31 bits sur un systeme 64 bits. Quatre tours de recherche par mots-cles n ont rien trouve, parce que la reponse n etait pas dans le journal -- elle etait dans le PKGBUILD, une ligne au-dessus de la commande qui l imprimait. Le PKGBUILD traite deja exactement ce cas pour riscv64 ; s390x rejoint donc cette branche plutot que d obtenir un mecanisme a lui. filesystem se construit desormais : le gid 11 absent de l hote etait tout le probleme. Assisted-by: Claude Opus 5 |
||
|---|---|---|
| .github/workflows | ||
| arch-kernel | ||
| boot | ||
| patches | ||
| scripts | ||
| .env.example | ||
| .gitignore | ||
| CODEOWNERS | ||
| Containerfile | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| TODO.md | ||
Arch Linux s390x
A port of Arch Linux to IBM s390x mainframe architecture with systemd support.
Boots a full Arch Linux system on IBM mainframes (or QEMU s390x emulation) using a hybrid build: cross-compilation for the kernel, native s390x compilation on z/VM for userspace.
Quick Start
make container # build dev container (first time)
cp .env.example .env # configure z/VM access
make all # build kernel + initramfs + systemd
make test-systemd # boot it
What Works
- Arch Linux kernel 6.18.6-arch1 with Arch patches, cross-compiled
- Initramfs via modified mkinitcpio
- Static busybox built natively on z/VM, 2.3MB
- Root filesystem with ext4, switch_root to real rootfs
- Systemd as PID 1
Pacman, bash, and GNU coreutils are not yet ported.
Build System
The build uses two tiers:
Cross-compilation (x86_64 host): Kernel is built in a Fedora 43 container with s390x-linux-gnu-gcc. Initramfs is generated with a patched mkinitcpio that handles cross-architecture binary injection.
Native compilation (s390x z/VM): Busybox and systemd must be built on real s390x hardware. The z/VM system runs RHEL 9.6 with GCC 11.5.0. Scripts handle SSH deployment and retrieval automatically via .env configuration.