From: "Ross Burton" <ross@burtonini.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2 6/7] systemd-boot: allow building for Arm targets
Date: Mon, 14 Dec 2020 18:31:47 +0000 [thread overview]
Message-ID: <20201214183148.2673069-6-ross.burton@arm.com> (raw)
In-Reply-To: <20201214183148.2673069-1-ross.burton@arm.com>
systemd-boot works on 32-bit and 64-bit Arm targets (assuming the
firmware does EFI, obviously), so allow it to be built.
Signed-off-by: Ross Burton <ross.burton@arm.com>
---
meta/recipes-core/systemd/systemd-boot_246.6.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-core/systemd/systemd-boot_246.6.bb b/meta/recipes-core/systemd/systemd-boot_246.6.bb
index 97093e4bb2..249e620f4e 100644
--- a/meta/recipes-core/systemd/systemd-boot_246.6.bb
+++ b/meta/recipes-core/systemd/systemd-boot_246.6.bb
@@ -48,7 +48,7 @@ RDEPENDS_${PN} += "virtual/systemd-bootconf"
# Imported from the old gummiboot recipe
TUNE_CCARGS_remove = "-mfpmath=sse"
-COMPATIBLE_HOST = "(x86_64.*|i.86.*)-linux"
+COMPATIBLE_HOST = "(aarch64.*|arm.*|x86_64.*|i.86.*)-linux"
COMPATIBLE_HOST_x86-x32 = "null"
do_compile() {
--
2.25.1
next prev parent reply other threads:[~2020-12-14 18:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 18:31 [PATCH v2 1/7] syslinux: rewrite recipe so only target code is x86-specific Ross Burton
2020-12-14 18:31 ` [PATCH v2 2/7] wic-image-minimal: only depend on syslinux on x86 targets Ross Burton
2020-12-14 18:31 ` [PATCH v2 3/7] wic-tools: don't build syslinux-native for targets without syslinux Ross Burton
2020-12-14 18:31 ` [PATCH v2 4/7] image-uefi.conf: add EFI arch variable Ross Burton
2020-12-14 18:31 ` [PATCH v2 5/7] systemd-boot: build the EFI stub Ross Burton
2020-12-14 18:31 ` Ross Burton [this message]
2020-12-14 18:31 ` [PATCH v2 7/7] wic-tools: add grub-efi and systemd-boot on arm64 Ross Burton
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=20201214183148.2673069-6-ross.burton@arm.com \
--to=ross@burtonini.com \
--cc=openembedded-core@lists.openembedded.org \
/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