No description
Mathieu Benoit
62233fc747
The first package the host is too OLD for rather than missing something. libgcrypt 1.12.2 wants libgpg-error >= 1.56; Ubuntu ships 1.51. No -dev package fixes a version floor. We built 1.61 ourselves, so the material exists -- but using it crosses a line worth naming: consuming stage 1's own output is the property that defines stage 2. The alternative was deferring libgcrypt, which gnupg and systemd both declare, leaving the repository unresolvable. Using our own is also what a bootstrap does, and stage 2 erases the distinction anyway. --with-libgpg-error-prefix looks like the mechanism and is not: it sets GPG_ERROR_CONFIG to $prefix/bin/gpg-error-config, a program 1.61 no longer ships. It would have named an absent file, fallen back to PATH, found 1.51 again, and the error would not have moved. GPGRT_CONFIG is what configure consults. Verified on a copy: version >= 1.56 yes (1.61-unknown), rc=0. The artefact carries no RPATH and no reference to the scratch prefix; it links the bare soname, which the target resolves from its own /usr/lib. --- FR --- Le premier paquet pour lequel l'hôte est trop VIEUX plutôt qu'incomplet. libgcrypt 1.12.2 veut libgpg-error >= 1.56 ; Ubuntu livre la 1.51. Aucun paquet -dev ne corrige un plancher de version. Nous avons bâti la 1.61 nous-mêmes, le matériel existe donc — mais l'employer franchit une limite qu'il faut nommer : consommer la sortie de l'étage 1 est la propriété qui définit l'étage 2. L'alternative était de reporter libgcrypt, que gnupg et systemd déclarent tous deux, laissant le dépôt insoluble. Employer le nôtre est aussi ce que fait un amorçage, et l'étage 2 efface la distinction de toute façon. --with-libgpg-error-prefix a l'air d'être le mécanisme et ne l'est pas : il fixe GPG_ERROR_CONFIG à $prefix/bin/gpg-error-config, programme que la 1.61 ne livre plus. Il aurait nommé un fichier absent, on serait retombé sur le PATH, retrouvé la 1.51, et l'erreur n'aurait pas bougé. C'est GPGRT_CONFIG que configure consulte. Vérifié sur une copie : version >= 1.56 yes (1.61-unknown), rc=0. L'artefact ne porte ni RPATH ni référence au préfixe temporaire ; il lie le soname nu, que la cible résout depuis son propre /usr/lib. 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.