Getting Linux Distros to New Architectures
summary
Automated process for the OpenMandriva RISC‑V port that produces working binary packages by building synchronized cross toolchains, creating a runnable zroot (chroot-like target OS) and using adjusted RPM macros to force correct compilers and detect cross-builds. Packages are bootstrapped in a recorded order that breaks circular deps with RPM --with/--without variants, builds resume from the last succeeded package with logs, and device-specific images use an OS Image Builder that supports per-board kernels, bootloader configs and inheritance.
AI-written summary · about
chapters (15)
- 0:00Porting Linux distros to new arches
- 1:26Why non-x86 architectures matter
- 2:28Building toolchains for new arches
- 4:55Minimal bootable OS for compilation
- 6:44Configuring RPM for cross-compilation
- 8:53Resolving package circular dependencies
- 11:24Bootstrapping core packages
- 12:31Supporting musl ABI
- 14:18Booting challenges on new hardware
- 16:03Hardware-specific images with OS Image Builder
- 19:38Customizing images for use cases
- 21:03Q&A on RISC-V and vendor support
- 22:53Encouraging upstream vendor contributions
- 24:48Debugging build failures
- 29:50Closing remarks
related talks
19mLinux on RISC V Fedora and Firmware Status Update
52mBuildroot: What's New
45mLinux on RISC-V--Fedora and Firmware in practice
31mPanel – Enterprise Linux Enablement on RISC-V
08mDemo: Super-optimized Ubuntu and Open Source on RISC-V
13mA Linux Distribution’s View on RISC-V
28mUbuntu on RISC-V - state of things
29mBehind the Curtains of Making Real Consumer Devices using Debian