From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>,
Helmut Grohne <helmut@subdivi.de>
Subject: Re: [PATCH 2/9] Add workaround for cross-building riscv64
Date: Mon, 8 Jan 2024 18:31:44 +0100 [thread overview]
Message-ID: <c27ec132-ab82-4e4f-a648-70a707918b7a@siemens.com> (raw)
In-Reply-To: <c1e5d483ee4fae79645d69ac95258a622c9b5a7d.1704190109.git.jan.kiszka@siemens.com>
On 02.01.24 11:08, 'Jan Kiszka' via isar-users wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> As Debian unstable does not care for riscv64 packages being in sync with
> other archs, cross-building is generally broken. However, we are at
> least currently just one package away from an essential crossbuild env,
> and that is libkeyutils1. By rebuilding that package from source for
> riscv64, non-cross, and then using it for sbuild-chroot-host, we can
> start building the kernel and firmware packages cross again.
>
> This patch should be removed again once riscv64 hits trixie, thus
> testing. But that may take some more moons, and we will benefit greatly
> from having a workaround until then to fix and improve other topics
> around that arch.
>
> See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059698 for
> more background.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> CC: Helmut Grohne <helmut@subdivi.de>
> ---
> meta/recipes-devtools/keyutils/keyutils.bb | 13 +++++++++++++
> .../sbuild-chroot/sbuild-chroot-host.bb | 2 ++
> 2 files changed, 15 insertions(+)
> create mode 100644 meta/recipes-devtools/keyutils/keyutils.bb
>
> diff --git a/meta/recipes-devtools/keyutils/keyutils.bb b/meta/recipes-devtools/keyutils/keyutils.bb
> new file mode 100644
> index 00000000..e3c8e909
> --- /dev/null
> +++ b/meta/recipes-devtools/keyutils/keyutils.bb
> @@ -0,0 +1,13 @@
> +# This software is a part of ISAR.
> +# Copyright (c) Siemens AG, 2023
> +#
> +# SPDX-License-Identifier: MIT
> +
> +inherit dpkg
> +
> +SRC_URI = "apt://${PN}"
> +
> +PROVIDES += "libkeyutils1 libkeyutils-dev"
> +
> +ISAR_CROSS_COMPILE = "0"
> +DEB_BUILD_OPTIONS += "nocheck"
> diff --git a/meta/recipes-devtools/sbuild-chroot/sbuild-chroot-host.bb b/meta/recipes-devtools/sbuild-chroot/sbuild-chroot-host.bb
> index 255d6937..b61e3634 100644
> --- a/meta/recipes-devtools/sbuild-chroot/sbuild-chroot-host.bb
> +++ b/meta/recipes-devtools/sbuild-chroot/sbuild-chroot-host.bb
> @@ -24,3 +24,5 @@ SBUILD_CHROOT_PREINSTALL:riscv64 ?= " \
> gcc-riscv64-linux-gnu \
> g++-riscv64-linux-gnu \
> dpkg-cross"
> +
> +DEPENDS:append:riscv64 = " keyutils"
We can drop this! Helmut just pointed out that Debian has fixed this
issue (and possibly more). There might be new ones in the future,
though, at least until riscv64 hits testing.
Jan
--
Siemens AG, Technology
Linux Expert Center
next prev parent reply other threads:[~2024-01-08 17:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 10:08 [PATCH 0/9] Restore cross-build for RISC-V, update VisionFive 2 Jan Kiszka
2024-01-02 10:08 ` [PATCH 1/9] crossvars: Account for PACKAGE_ARCH = "${BUILD_ARCH}" Jan Kiszka
2024-01-02 10:08 ` [PATCH 2/9] Add workaround for cross-building riscv64 Jan Kiszka
2024-01-08 17:31 ` Jan Kiszka [this message]
2024-01-02 10:08 ` [PATCH 3/9] meta-isar: jh7110-u-boot-spl-tool: Use BPN instead of PN Jan Kiszka
2024-01-02 10:08 ` [PATCH 4/9] meta-isar: starfive-visionfive2: Use kernel DTB Jan Kiszka
2024-01-02 10:08 ` [PATCH 5/9] meta-isar: jh7110-u-boot-spl-tool: Rework Jan Kiszka
2024-01-02 10:08 ` [PATCH 6/9] meta-isar: starfive-visionfive2: Switch to upstream U-Boot Jan Kiszka
2024-01-02 10:08 ` [PATCH 7/9] meta-isar: starfive-visionfive2: Drop obsolete recipes Jan Kiszka
2024-01-02 10:08 ` [PATCH 8/9] meta-isar: linux-mainline: Update to 6.6.9 Jan Kiszka
2024-01-02 10:08 ` [PATCH 9/9] meta-isar: Switch VisionFive 2 to mainline kernel Jan Kiszka
2024-01-03 16:39 ` [PATCH 0/9] Restore cross-build for RISC-V, update VisionFive 2 Jan Kiszka
2024-01-05 15:45 ` Anton Mikanovich
2024-01-05 21:19 ` Jan Kiszka
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=c27ec132-ab82-4e4f-a648-70a707918b7a@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=helmut@subdivi.de \
--cc=isar-users@googlegroups.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