public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: isar-users <isar-users@googlegroups.com>
Cc: "Schmidt, Adriaan" <adriaan.schmidt@siemens.com>
Subject: [PATCH] linux-custom: Fix multiple provider warning when compat mode is active
Date: Mon, 12 Aug 2024 21:50:12 +0200	[thread overview]
Message-ID: <fbc783b6-a271-4bde-824a-f2c1bf38b19c@siemens.com> (raw)

From: Jan Kiszka <jan.kiszka@siemens.com>

As the comment explains: When ISAR_ENABLE_COMPAT_ARCH is enabled, we
get the -compat variant of the recipe, but that will also provide
${BPN}-pseudo-native because of it pre-existing ending. This leads to

NOTE: Multiple providers are available for linux-mainline-pseudo-native (linux-mainline, linux-mainline-compat)
Consider defining a PREFERRED_PROVIDER entry to match linux-mainline-pseudo-native

Resolve that by only providing this pseudo target via the base recipe.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---

And I thought we already covered all possible corner cases...

 meta/recipes-kernel/linux/linux-custom.inc | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/meta/recipes-kernel/linux/linux-custom.inc b/meta/recipes-kernel/linux/linux-custom.inc
index 6aa70fd3..f8f66cb3 100644
--- a/meta/recipes-kernel/linux/linux-custom.inc
+++ b/meta/recipes-kernel/linux/linux-custom.inc
@@ -156,6 +156,10 @@ RECIPE_PROVIDES:remove:cross-profile = " \
     linux-headers-${KERNEL_NAME_PROVIDED} \
     linux-kbuild-${KERNEL_NAME_PROVIDED}"
 
+# As the multiarch class will not append -compat to -pseudo-native, we end up
+# with two providers of it. Remove the wrong one.
+RECIPE_PROVIDES:remove:class-compat = "${BPN}-pseudo-native"
+
 # Append headers depends
 HEADERS_DEPENDS = ", linux-kbuild-${KERNEL_NAME_PROVIDED} | linux-kbuild-${KERNEL_NAME_PROVIDED}-${DISTRO_ARCH}-cross"
 KERNEL_HEADERS_DEBIAN_DEPENDS:append = "${HEADERS_DEPENDS}"
-- 
2.43.0

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/fbc783b6-a271-4bde-824a-f2c1bf38b19c%40siemens.com.

             reply	other threads:[~2024-08-12 19:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-12 19:50 'Jan Kiszka' via isar-users [this message]
2024-08-15  4:40 ` 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=fbc783b6-a271-4bde-824a-f2c1bf38b19c@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=adriaan.schmidt@siemens.com \
    --cc=jan.kiszka@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