All of lore.kernel.org
 help / color / mirror / Atom feed
From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [meta][PATCH 05/06] kernel-devsrc: copy arch/x86 vdso2c sources for on-target prepare
Date: Fri, 21 Aug 2026 07:25:07 -0400	[thread overview]
Message-ID: <20260821112509.861559-6-bruce.ashfield@gmail.com> (raw)
In-Reply-To: <20260821112509.861559-1-bruce.ashfield@gmail.com>

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Since 7.2, arch/x86/tools/Makefile adds vdso2c to hostprogs with
"always-y := $(hostprogs)", so the archscripts target run by
"make scripts prepare" now always builds arch/x86/tools/vdso2c. Without
its sources in the devsrc tree the on-target prepare fails:

  make[2]: *** No rule to make target 'arch/x86/tools/vdso2c.c', needed
  by 'arch/x86/tools/vdso2c'.  Stop.

Copy vdso2c.c and its vdso2c.h alongside the relocs sources; the
<tools/le_byteshift.h> dependency is already shipped. 6.18 and earlier
still have the sources (just unused there), so the copy is safe across
versions.

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 meta/recipes-kernel/linux/kernel-devsrc.bb | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-kernel/linux/kernel-devsrc.bb b/meta/recipes-kernel/linux/kernel-devsrc.bb
index 47c0abfa38..2d80278830 100644
--- a/meta/recipes-kernel/linux/kernel-devsrc.bb
+++ b/meta/recipes-kernel/linux/kernel-devsrc.bb
@@ -326,6 +326,9 @@ do_install() {
             cp -a --parents arch/x86/tools/relocs.c $kerneldir/build/
             cp -a --parents arch/x86/tools/relocs_common.c $kerneldir/build/
             cp -a --parents arch/x86/tools/relocs.h $kerneldir/build/
+            # v7.2+ archscripts also builds the vdso2c host tool
+            cp -a --parents arch/x86/tools/vdso2c.c $kerneldir/build/ 2>/dev/null || :
+            cp -a --parents arch/x86/tools/vdso2c.h $kerneldir/build/ 2>/dev/null || :
             cp -a --parents arch/x86/tools/gen-insn-attr-x86.awk $kerneldir/build/ 2>/dev/null || :
             cp -a --parents arch/x86/tools/cpufeaturemasks.awk $kerneldir/build/ 2>/dev/null || :
             cp -a --parents arch/x86/purgatory/purgatory.c $kerneldir/build/
-- 
2.43.0



  parent reply	other threads:[~2026-08-21 11:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-21 11:25 [PATCH 0/6] kernel-yocto: 6.18 and 7.2 RFC/prep bruce.ashfield
2026-08-21 11:25 ` [meta][PATCH 01/06] linux-yocto/6.18: update to v6.18.44 bruce.ashfield
2026-08-21 11:25 ` [meta][PATCH 02/06] linux-libc-headers: update to 7.2 bruce.ashfield
2026-08-21 11:25 ` [meta][PATCH 03/06] linux-yocto/7.2: introduce reference kernel recipes bruce.ashfield
2026-08-21 11:25 ` [meta][PATCH 04/06] kernel-devsrc: strip riscv vdso-cfi-offsets .cmd file bruce.ashfield
2026-08-21 11:25 ` bruce.ashfield [this message]
2026-08-21 11:25 ` [meta-yocto-bsp][PATCH 06/06] linux-yocto/6.18: update to v6.18.44 bruce.ashfield
2026-08-21 11:33   ` Patchtest results for " patchtest
2026-08-21 15:43 ` [OE-core] [PATCH 0/6] kernel-yocto: 6.18 and 7.2 RFC/prep Khem Raj
2026-08-21 21:51   ` Khem Raj
2026-08-21 21:45 ` Richard Purdie

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=20260821112509.861559-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.