From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [meta][PATCH 05/07] kernel-devsrc: ship tools/include for archscripts host tools
Date: Wed, 2 Sep 2026 09:23:02 -0400 [thread overview]
Message-ID: <20260902132305.3685228-6-bruce.ashfield@gmail.com> (raw)
In-Reply-To: <20260902132305.3685228-1-bruce.ashfield@gmail.com>
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Since 7.2, "make scripts prepare" builds arch/x86/tools/vdso2c as part of
the archscripts target. vdso2c is compiled with -I$(srctree)/tools/include
and resolves <linux/types.h> to tools/include/linux/types.h, which pulls
in <stdbool.h>. On target that header was only shipped inside the objtool
block, but objtool is built on x86-64 only (arch/x86/Kconfig: select
HAVE_OBJTOOL if X86_64). A 32-bit x86 kernel-devsrc build therefore lacked
tools/include, fell back to include/uapi/linux/types.h (which does not
define bool), and failed:
arch/x86/tools/vdso2c.c:74:9: error: unknown type name 'bool'
Copy tools/include unconditionally so the archscripts host tools build
regardless of whether objtool is present.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
meta/recipes-kernel/linux/kernel-devsrc.bb | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-kernel/linux/kernel-devsrc.bb b/meta/recipes-kernel/linux/kernel-devsrc.bb
index a38e4fed44..90bdbfc534 100644
--- a/meta/recipes-kernel/linux/kernel-devsrc.bb
+++ b/meta/recipes-kernel/linux/kernel-devsrc.bb
@@ -158,6 +158,11 @@ do_install() {
# Remove as we else would ned to RDEPEND on make
rm $kerneldir/build/scripts/package/debian/rules 2>/dev/null || :
+ # tools/include is needed by the archscripts host tools that
+ # 'make scripts prepare' rebuilds on target (e.g. x86 vdso2c) and
+ # not checked against objtool as it previously was.
+ cp -a --parents tools/include/* $kerneldir/build/
+
# if our build dir had objtool, it will also be rebuilt on target, so
# we copy what is required for that build
if [ -f ${B}/tools/objtool/objtool ]; then
@@ -173,8 +178,6 @@ do_install() {
cp -a --parents tools/lib/* $kerneldir/build/
cp -a --parents tools/lib/subcmd/* $kerneldir/build/
- cp -a --parents tools/include/* $kerneldir/build/
-
cp -a --parents $(find tools/arch/${ARCH}/ -type f) $kerneldir/build/
fi
--
2.43.0
next prev parent reply other threads:[~2026-09-02 13:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 13:22 [PATCH 0/7 v2] linux-yocto: consolidated pull request bruce.ashfield
2026-09-02 13:22 ` [meta][PATCH 01/07] linux-yocto/7.2: introduce reference kernel recipes bruce.ashfield
2026-09-02 13:22 ` [meta][PATCH 02/07] linux-yocto/7.2: BSPs: fix configuration warnings bruce.ashfield
2026-09-02 13:23 ` [meta][PATCH 03/07] linux-yocto/7.2: update to v7.2.2 bruce.ashfield
2026-09-02 13:23 ` [meta][PATCH 04/07] linux-yocto/7.2: remap rust debug info paths bruce.ashfield
2026-09-02 13:23 ` bruce.ashfield [this message]
2026-09-02 13:23 ` [meta][PATCH 06/07] linux-yocto/6.18: update to v6.18.48 bruce.ashfield
2026-09-02 13:23 ` [meta-yocto-bsp][PATCH 07/07] " bruce.ashfield
2026-09-02 13:35 ` Patchtest results for " patchtest
2026-09-02 13:52 ` [OE-core] [PATCH 0/7 v2] linux-yocto: consolidated pull request Mikko Rapeli
2026-09-02 14:18 ` Bruce Ashfield
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=20260902132305.3685228-6-bruce.ashfield@gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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