public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Paul Barker <paul@pbarker.dev>
To: openembedded-core@lists.openembedded.org
Cc: Paul Barker <paul@pbarker.dev>
Subject: [PATCH 09/12] linux-yocto: Avoid arch dependent vardeps for SRC_URI
Date: Wed, 18 Mar 2026 17:14:52 +0000	[thread overview]
Message-ID: <20260318-fix-checklayer-2-v1-9-388ba6ce47cd@pbarker.dev> (raw)
In-Reply-To: <20260318-fix-checklayer-2-v1-0-388ba6ce47cd@pbarker.dev>

yocto-check-layer will fail if SRC_URI is dependent on the target
architecture. Usually we would try to remove the dependency, but for the
linux-yocto recipe it's necessary in order to select the appropriate
branch from the source repository.

As none of the checks performed by yocto-check-layer actually depend on
the selected branch, we can discard this depedency by specifying a
generic vardepvalue for the branch name.

Signed-off-by: Paul Barker <paul@pbarker.dev>
---
 meta/recipes-kernel/linux/linux-yocto.inc | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/meta/recipes-kernel/linux/linux-yocto.inc b/meta/recipes-kernel/linux/linux-yocto.inc
index f47873348a9a..18f910f34e56 100644
--- a/meta/recipes-kernel/linux/linux-yocto.inc
+++ b/meta/recipes-kernel/linux/linux-yocto.inc
@@ -93,3 +93,8 @@ do_devshell:prepend() {
     d.setVar("HOSTPKG_CONFIG", "pkg-config-native")
     d.appendVar("OE_TERMINAL_EXPORTS", " HOSTPKG_CONFIG")
 }
+
+# Avoid potentially architecture dependent value when evaluating vardeps of
+# SRC_URI. This does mean do_recipe_qa may not re-run when KBRANCH changes, but
+# that should not invalidate the QA test.
+KBRANCH[vardepvalue] = "master"

-- 
2.43.0



  parent reply	other threads:[~2026-03-18 17:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-18 17:14 [PATCH 00/12] Further check-layer fixes Paul Barker
2026-03-18 17:14 ` [PATCH 01/12] checklayer: Fix regex in get_signatures Paul Barker
2026-03-18 17:14 ` [PATCH 02/12] curl: Drop arch dependent search paths Paul Barker
2026-03-18 17:14 ` [PATCH 03/12] ghostscript: " Paul Barker
2026-03-18 17:14 ` [PATCH 04/12] libssh2: " Paul Barker
2026-03-18 17:14 ` [PATCH 05/12] flac: Use arch independent search path Paul Barker
2026-03-18 17:14 ` [PATCH 06/12] gettext: Use arch independent search paths Paul Barker
2026-03-18 17:14 ` [PATCH 07/12] gnutls: " Paul Barker
2026-03-18 17:14 ` [PATCH 08/12] initscripts: Make SRC_URI arch independent Paul Barker
2026-03-18 17:22   ` [OE-core] " Richard Purdie
2026-03-18 17:14 ` Paul Barker [this message]
2026-03-18 17:14 ` [PATCH 10/12] libsdl2: Explicitly set PACKAGECONFIG vardeps Paul Barker
2026-03-18 17:29   ` [OE-core] " Richard Purdie
2026-03-18 17:14 ` [PATCH 11/12] graphene: " Paul Barker
2026-03-18 17:14 ` [PATCH 12/12] gstreamer1.0-plugins-good: " Paul Barker

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=20260318-fix-checklayer-2-v1-9-388ba6ce47cd@pbarker.dev \
    --to=paul@pbarker.dev \
    --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