meta-toolchain, gdb-cross-canadian_9.2 fails due to "no usable python" #toolchain
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:
while in the filesystem it existed at
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:
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!
On Fri, Mar 5, 2021 at 4:01 AM <firstname.lastname@example.org> wrote:
there will be a file called config.log created in gdb build dir which
will have further information as to why it thing python interpreter is
My host is Ubuntu 20.04, and I'm using yocto/poky gatesgarth as base. Target core-image-minimal builds without issue, only meta-toolchain fails.
I have been trying to build meta-toolchain however it fails to compile during gdb-cross-canadian. Follows the relevant output:
| checking for libmpfr... no
| configure: WARNING: MPFR is missing or unusable; some features may be unavailable.
| checking whether to use python... /home/.../workspace/gatesgarth/build/tmp/work/x86_64-nativesdk-pokysdk-linux/gdb-cross-canadian-arm/9.2-r0/python
| checking for python... no
| configure: error: no usable python found at /home/.../workspace/gatesgarth/build/tmp/work/x86_64-nativesdk-pokysdk-linux/gdb-cross-canadian-arm/9.2-r0/python
| make: *** [Makefile:8866: configure-gdb] Error 1My host is Ubuntu 20.04, and I'm using yocto/poky gatesgarth as base. Target core-image-minimal builds without issue, only meta-toolchain fails.
Normally I can get a good idea why something is failing from the logs, but this time I'm really left clueless. Any help would be appreciated.