No description
mv: cannot stat 'usr/lib/libquadmath.a': No such file or directory libquadmath implements __float128, which exists on x86 and ia64. On s390x the directory is CONFIGURED -- it holds a Makefile, a config.log and a config.status -- but no library is ever built. The half-created directory is what makes this one confusing: it looks like a build that failed rather than a target that has nothing to build. Dropped from pkgname, from the _pick lines, and from the depends entry in another sub-package. That last one matters: with --nodeps it is harmless at build time and fatal at install time, which is exactly the kind of defect that surfaces long after the build that introduced it. package_libquadmath() is left in place. makepkg never calls a function whose name is absent from pkgname, so removing it would be churn. util-linux calls "python", which Ubuntu does not provide -- only python3. python-is-python3 supplies the name. --- FR --- mv: cannot stat 'usr/lib/libquadmath.a': No such file or directory libquadmath implemente __float128, qui existe sur x86 et ia64. Sur s390x le repertoire est CONFIGURE -- il contient un Makefile, un config.log et un config.status -- mais aucune bibliotheque n y est jamais batie. C est ce repertoire a moitie cree qui rend le cas trompeur : il a l air d une compilation ratee plutot que d une cible qui n a rien a construire. Retire de pkgname, des lignes _pick, et de la declaration depends d un autre sous-paquet. Ce dernier point compte : avec --nodeps il est inoffensif a la compilation et fatal a l installation, exactement le genre de defaut qui se revele longtemps apres la compilation qui l a introduit. package_libquadmath() reste en place. makepkg n appelle jamais une fonction dont le nom est absent de pkgname ; la retirer serait du bruit. util-linux appelle « python », qu Ubuntu ne fournit pas -- seulement python3. python-is-python3 fournit le nom. 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.