From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>,
stefan-koch@siemens.com,
Adriaan Schmidt <adriaan.schmidt@siemens.com>,
Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH v3 3/5] linux-custom: Resolve native source package differences
Date: Fri, 17 May 2024 18:35:40 +0200 [thread overview]
Message-ID: <99b4e97b01b683fa3bf6490475e3c8a125ab824b.1715963742.git.jan.kiszka@siemens.com> (raw)
In-Reply-To: <cover.1715963742.git.jan.kiszka@siemens.com>
From: Jan Kiszka <jan.kiszka@siemens.com>
When building the native package, KERNEL_FILE as defined in bitbake.conf
is wrong as it uses the package arch. Avoid that by redefining
KERNEL_FILE in the kernel recipe using KERNEL_ARCH.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
meta/recipes-kernel/linux/linux-custom.inc | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/recipes-kernel/linux/linux-custom.inc b/meta/recipes-kernel/linux/linux-custom.inc
index c54c287f..b53d136c 100644
--- a/meta/recipes-kernel/linux/linux-custom.inc
+++ b/meta/recipes-kernel/linux/linux-custom.inc
@@ -175,6 +175,9 @@ def get_kernel_arch(d):
KERNEL_ARCH ??= "${@get_kernel_arch(d)}"
+# set KERNEL_FILE without depending on package arch used in bitbake.conf
+KERNEL_FILE:forcevariable = "${@ 'vmlinux' if d.getVar('KERNEL_ARCH') in ['mipsel', 'riscv', 'arm64'] else 'vmlinuz'}"
+
def config_fragments(d):
fragments = []
sources = d.getVar("SRC_URI").split()
--
2.35.3
next prev parent reply other threads:[~2024-05-17 16:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 16:35 [PATCH v3 0/5] More kbuild improvements, single-build source packages, cross profile fix Jan Kiszka
2024-05-17 16:35 ` [PATCH v3 1/5] dpkg-base: Fix enabling of cross build profile Jan Kiszka
2024-05-17 16:35 ` [PATCH v3 2/5] linux-custom: Model cross-built kbuild package separately Jan Kiszka
2024-05-17 16:35 ` Jan Kiszka [this message]
2024-05-17 16:35 ` [PATCH v3 4/5] dpkg: Retrieve Debian source name from variable Jan Kiszka
2024-05-17 16:35 ` [PATCH v3 5/5] dpkg-source: Build source package only once Jan Kiszka
2024-05-17 16:57 ` [PATCH v3 6/5] testsuite: Build linux-headers for the hikey target Jan Kiszka
2024-05-21 10:29 ` [PATCH v3 0/5] More kbuild improvements, single-build source packages, cross profile fix Koch, Stefan
2024-05-21 10:35 ` Anton Mikanovich
2024-05-21 10:41 ` Jan Kiszka
2024-05-27 9:16 ` Jan Kiszka
2024-05-27 11:05 ` Uladzimir Bely
2024-05-28 5:30 ` Jan Kiszka
2024-05-28 5:38 ` Uladzimir Bely
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=99b4e97b01b683fa3bf6490475e3c8a125ab824b.1715963742.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=adriaan.schmidt@siemens.com \
--cc=amikan@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=stefan-koch@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