All of lore.kernel.org
 help / color / mirror / Atom feed
From: mmiguelhorta@gmail.com
To: yocto@lists.yoctoproject.org
Subject: Re: meta-toolchain, gdb-cross-canadian_9.2 fails due to "no usable python" #toolchain
Date: Fri, 05 Mar 2021 12:58:22 -0800	[thread overview]
Message-ID: <3015.1614977902706588765@lists.yoctoproject.org> (raw)
In-Reply-To: <CAMKF1sqsMX1-TAX_m7HvPotwQs98yDE-HXfYe1upeCMNSMbT7g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]

Thanks for the tip Raj, it got me into the right track. The error was that "Python.h" missing, but the interesting bit was the path where it was looking for it.
It was searching for it within:
(...)./recipe-sysroot/opt/my-image/my-distro-version/sysroots/(...)
while in the filesystem it existed at
(...)./recipe-sysroot/opt/my-image/3.2.1/sysroots/(...)

From that I deduced that somehow it was picking conflicting values for DISTRO_VERSION, executing the follow commands confirmed my suspicion
bitbake -e gdb-cross-canadian-arm | grep "^DISTRO"; -> DISTRO_VERSION="my-distro-version"
bitbake -e nativesdk-python3| grep "^DISTRO"; -> DISTRO_VERSION="3.2.1"

After digging a bit more I figured why it was happening, "my-distro-version" was defined through an override:
MACHINEOVERRIDES="machine"
DISTRO_VERSION_machine="my-distro-version"

However for nativesdk recipes MACHINEOVERRIDES is empty so it picked up DISTRO_VERSION as defined in poky.conf file, "3.2.1".

Dropping the override and having both DISTRO_VERSION equal solved the issue. Thanks!

[-- Attachment #2: Type: text/html, Size: 1139 bytes --]

      reply	other threads:[~2021-03-05 20:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05 12:00 meta-toolchain, gdb-cross-canadian_9.2 fails due to "no usable python" #toolchain mmiguelhorta
2021-03-05 15:51 ` [yocto] " Khem Raj
2021-03-05 20:58   ` mmiguelhorta [this message]

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=3015.1614977902706588765@lists.yoctoproject.org \
    --to=mmiguelhorta@gmail.com \
    --cc=yocto@lists.yoctoproject.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.