No description
Two install commands passed one --nodeps and looked like they were skipping dependencies. pacman documents the difference: -d skips dependency VERSION checks, -dd skips them entirely. So cython could not be installed -- warning: cannot resolve python-pygments, a dependency of cython :: unable to satisfy dependency python-numpy required by cython -- and the numbers matter. cython is wanted here only as a BUILD tool, for libseccomp Python binding, while its declared RUNTIME dependencies are numpy and pygments, and numpy brings BLAS and LAPACK. A single -d nearly bought a numerical stack to compile one .pyx file. The message named numpy and numpy was not the subject. The subject was a missing letter d. python-poetry-core joins the list: the fourth Python build backend needed here after flit_core, setuptools and hatchling. --- FR --- Deux commandes d installation passaient un seul --nodeps et semblaient sauter les dependances. pacman documente la difference : -d saute les controles de VERSION, -dd les saute entierement. cython ne pouvait donc pas etre installe -- warning: cannot resolve python-pygments, a dependency of cython :: unable to satisfy dependency python-numpy required by cython -- et les chiffres comptent. cython n est voulu ici que comme OUTIL de construction, pour la liaison Python de libseccomp, alors que ses dependances d EXECUTION declarees sont numpy et pygments, et numpy tire BLAS et LAPACK. Un seul -d a failli faire compiler une pile numerique pour un fichier .pyx. Le message nommait numpy, et numpy n etait pas le sujet. Le sujet etait un d manquant. python-poetry-core rejoint la liste : quatrieme moteur de construction Python necessaire ici, apres flit_core, setuptools et hatchling. Assisted-by: Claude Opus 5 |
||
|---|---|---|
| .github/workflows | ||
| arch-kernel | ||
| boot | ||
| patches | ||
| scripts | ||
| .env.example | ||
| .gitignore | ||
| CODEOWNERS | ||
| Containerfile | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| RELAIS.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.