All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: andrej.v@skyrain.eu,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] perf: nativesdk
Date: Thu, 19 Jun 2025 12:21:08 +0100	[thread overview]
Message-ID: <dcf64e281e9fd6a81d3e3ec9fc7088c1cd09d06c.camel@linuxfoundation.org> (raw)
In-Reply-To: <7dee70c7-d0a8-44ea-94a1-2c4be581208e@skyrain.eu>

On Thu, 2025-06-19 at 09:53 +0200, Andrej Valek via lists.openembedded.org wrote:
> I know, that what I'm doing is not fully supported way, but... . I 
> wanted to build the perf for target device (aarch64), record the data
> and analyze them on the host. So I extended the recipe by adding 
> BBCLASSEXTEND = "native nativesdk".
> 
> After that I have compilation failure do to missing manifest.
> 
> ERROR: nativesdk-perf-1.0-r0 do_configure: The sstate manifest for task 
> 'linux-libc-headers:populate_sysroot' (multilib variant '') could not be 
> found.
> The pkgarchs considered were: machineA, cortexa53, cortexa53, cortexa53, 
> armv8a-crc, armv8a, aarch64, allarch, x86_64_x86_64-nativesdk.
> But none of these manifests exists:
> /home/build/tmp/sstate-control/manifest-machineA-linux-libc-headers.populate_sysroot
> /home/build/tmp/sstate-control/manifest-cortexa53-linux-libc-headers.populate_sysroot
> /home/build/tmp/sstate-control/manifest-cortexa53-linux-libc-headers.populate_sysroot
> /home/build/tmp/sstate-control/manifest-cortexa53-linux-libc-headers.populate_sysroot
> /home/build/tmp/sstate-control/manifest-armv8a-crc-linux-libc-headers.populate_sysroot
> /home/build/tmp/sstate-control/manifest-armv8a-linux-libc-headers.populate_sysroot
> /home/build/tmp/sstate-control/manifest-aarch64-linux-libc-headers.populate_sysroot
> /home/build/tmp/sstate-control/manifest-allarch-linux-libc-headers.populate_sysroot
> /home/build/tmp/sstate-control/manifest-x86_64_x86_64-nativesdk-linux-libc-headers.populate_sysroot
> 
> The "linux-libc-headers" dependency is coming from "gcc-cross-aarch64".
> 
> EXTRADEPENDS = ""
> DEPENDS = "virtual/${TARGET_PREFIX}binutils ${EXTRADEPENDS} ${NATIVEDEPS}"
> PROVIDES = "virtual/${TARGET_PREFIX}gcc virtual/${TARGET_PREFIX}g++"
> python () {
>      if d.getVar("TARGET_OS").startswith("linux"):
>          d.setVar("EXTRADEPENDS", "linux-libc-headers")
> }
> 
> This function adds the dependency without respecting any 
> native/nativesdk variant.
> 
> I know touching the "PACKAGE_EXTRA_ARCHS" or removing this function 
> above it's not right way to fix it.
> 
> How to deal with something like that?

Ignoring this is all a bad idea, something which is nativesdk should be
using gcc-crosssdk, not gcc-cross. gcc-cross quite correctly depends on
linux-libc-headers, gcc-crosssdk will depend on nativesdk-linux-libc-
headers.

Cheers,

Richard


  parent reply	other threads:[~2025-06-19 11:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19  7:53 perf: nativesdk Andrej Valek
2025-06-19  7:56 ` [OE-core] " Alexander Kanavin
2025-06-19  8:07   ` Andrej Valek
2025-06-19  8:13     ` Alexander Kanavin
2025-06-19  8:59       ` Marko, Peter
2025-06-19 10:57         ` Andrej Valek
2025-06-19 11:21 ` Richard Purdie [this message]
2025-06-19 11:44   ` Andrej Valek
2025-06-19 12:45     ` Richard Purdie
2025-06-19 12:55       ` Andrej Valek

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=dcf64e281e9fd6a81d3e3ec9fc7088c1cd09d06c.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=andrej.v@skyrain.eu \
    --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 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.