No description
Mathieu Benoit
e137999f8b
39 of 39 packages failed on the same line: bsdtar: error while loading shared libraries: libicuuc.so.76 libarchive is in STAGE2_SKIP_HOOKS, so stage 2 rebuilt it as Arch does -- with xar, linking whatever libxml2 was installed at that moment: the stage-1 one, which wants the host's ICU 76 while ours ships 78. bsdtar is what makepkg uses to extract sources and write packages, so nothing could come out, including libxml2 itself. The stage-1 fix does not reach in here. No new mechanism was needed. libarchive is dropped from stage2.state, so the restore falls back to the stage-1 build that has no xar and therefore no libxml2 at all; libxml2 is hoisted and rebuilt against our icu; libarchive is rebuilt later with xar, against a libxml2 whose ICU now agrees. Verified: bsdtar 3.8.9 runs, and libxml2 is the first OK of the pass. The libgpgme.so.11 errors in five logs were noise -- makepkg carries on past a failed .BUILDINFO. Reading the FIRST error in a log had attributed five failures to the wrong cause; the last error before the abort is the one that matters. --- FR --- 39 paquets sur 39 ont échoué sur la même ligne : bsdtar: error while loading shared libraries: libicuuc.so.76 libarchive figure dans STAGE2_SKIP_HOOKS : l'étage 2 l'a donc rebâti comme le fait Arch — avec xar, contre le libxml2 installé à cet instant, celui de l'étage 1, qui veut l'ICU 76 de l'hôte quand le nôtre livre la 78. bsdtar est ce dont makepkg se sert pour extraire et pour écrire les paquets : plus rien ne sortait, libxml2 compris. Le correctif d'étage 1 n'atteint pas l'intérieur. Aucun mécanisme nouveau. libarchive quitte stage2.state, donc la restauration retombe sur la construction d'étage 1, sans xar et donc sans libxml2 ; libxml2 est hissé et rebâti contre notre icu ; libarchive est rebâti plus tard avec xar, contre un libxml2 dont l'ICU concorde. Vérifié : bsdtar 3.8.9 démarre, et libxml2 est le premier OK de la passe. Les erreurs libgpgme.so.11 de cinq journaux étaient du bruit — makepkg poursuit après un .BUILDINFO manqué. Lire la PREMIÈRE erreur d'un journal avait attribué cinq échecs à la mauvaise cause ; c'est la dernière avant l'abandon qui compte. 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.