From: Anton Mikanovich <amikan@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com
Subject: Re: [PATCH] fix systemd-boot for non x64 targets
Date: Wed, 26 Oct 2022 17:03:03 +0300 [thread overview]
Message-ID: <f713e322-626f-73de-aa67-4c937c0e06b0@ilbers.de> (raw)
In-Reply-To: <20221020025657.1458548-1-felix.moessbauer@siemens.com>
20.10.2022 05:56, Felix Moessbauer wrote:
> With the recently introduced cross-imaging, all imager dependencies are
> installed for the build architecture but not the target / distro
> architecture. This is correct for tools, but not for architecture
> specific files that are copied into the target rootfs.
> By that, arm64 targets got bootx64.efi loaders installed, making it
> impossible to boot the image.
>
> For grub, we already have architecture specific support based on package
> names. This patch introduces the same for systemd-boot. Here, the
> architecture is not encoded in the package name, but in the architecture
> field. To avoid conflicts with other packages in the buildchroot-host,
> from bookworm on, we only depend on systemd-boot-efi,
> as this package provides the efi stubs and is co-installable for
> multiple architectures. For older releases, this is not possible but
> depending on systemd works as well.
>
> In theory this could conflict with a build-arch systemd installed into
> the buildchroot-host, but as almost all dependencies are now installed
> using sbuilder and schroot, this case is very unlikely.
> In this case, a user still can disable cross for the imaging.
>
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
Applied to next, thanks.
prev parent reply other threads:[~2022-10-26 14:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 2:56 Felix Moessbauer
2022-10-26 14:03 ` Anton Mikanovich [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f713e322-626f-73de-aa67-4c937c0e06b0@ilbers.de \
--to=amikan@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox