Workarounds for building on a Raspberry Pi 5 host #217
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add an optional "hack" that replaces ischroot with /usr/bin/true for the duration of the build, because we can safely assume all commands run during the build are done in chroot. Select with `HACK_ISCHROOT_TRUE=y`. Debtools provides `ischroot` as an utility to chech if one is running in a chroot environment. This is used in various package installations to avoid behaviour that is invalid inside a chroot. The current version doesn't function properly in our build environment, returning 2 (= chroot detection is not possible), which breaks some package installs (e.g. raspi-bootloader, but not only). Signed-off-by: Ioan Dragomir <[email protected]>
Add an if clause to only activate the `qemu-arm` binfmt on non-arm hosts. On arm hosts, no emulation is needed. Attempting to activate the arm binfmt on native arm hosts leads to an error because the `qemu-user-binfmt` package doesn't contain binfmt configs for their respective host architecture (i.e. the amd64 package doesn't contain qemu-x86_64, the arm64 package doesn't contain qemu-arm, etc.). This makes it possible to build Kuiper images on an arm64 host, allowing for build speedups by removing the emulation layer. It should also allow building of 32 bit images on armv6/v7/v7l hosts. Building armhf images on an arm64 host -------------------------------------- Note that building armhf images requires the host run a kernel with 4k pages, such as `kernel8.img` instead of `kernel2712.img` on the Raspberry Pi 5. The kernel included in the image can be anything. On a 16k page kernel, many binaries will fail to load inside the chroot because of page alignment. The opposite is not an issue: binaries with 16k pages are compatible with a kernel with 4k pages. See: raspberrypi/bookworm-feedback#107 Signed-off-by: Ioan Dragomir <[email protected]>
trupples
force-pushed
the
add-rpi5-build-support
branch
from
a0eb091 to
44409d7
Compare
|
Force push rolls back dpkg unsafe-io hack. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Description
Building Kuiper images on a Debian bookworm Raspberry Pi 5 host would previously run into the following issues:
01.bootstrap/run.shfails atupdate-binfmts --enable qemu-armbecauseqemu-armis not provided on arm hosts ("why emulate arm if already natively on arm?")07.extra-tweaks/02.install-rpi-packagesfails because chroot detection with debtoolsischrootreturns incorrect results (2 instead of 0), which breaks the post-install script of theraspi-firmwarepackage.This PR adds:
update-binfmtsif emulation is actually needed (host arch != aarch64 && host arch != arm*)ischrootwith/usr/bin/trueduring the image build. This assumes all binaries executed from the built rootfs are ran inside a chroot environment.An optional "hack" to speed up dpkg by disabling filesystem syncs after each installed package. This helps a lot when the backing storage is slow, such as an SD card.Open questions:
The dpkg unsafe-io hack should be enabled as soon as possible to speed up as many package installs as possible (right after debootstrap would be ideal)PR Type
PR Checklist