What It Actually Takes to Build Yocto Properly on Arch Linux
TL;DR: Building natively on a Yocto workspace on Arch Linux hits two separate failures. The host’s rolling toolchain is not pinned, so bitbake’s own host-side tooling drifts under you between builds. And uninative, the prebuilt glibc that keeps -native binaries loadable across hosts, disables itself silently once the glibc it sees outruns the ceiling baked into its own payload: one bb.warn line, and native sstate quietly stops being shareable. buildtools-extended, the Yocto Project’s own documented recommendation for unsupported hosts, fixes the first problem. Nothing off the shelf fixed the second, so I built yocto-uninative-tarball, an AUR (Arch User Repository) package that rebuilds the payload from the exact glibc commit Arch itself ships, so host and payload glibc are the same build by construction instead of racing each other. ...