Note that whilst the python headers and library will be in recipe- sysroot, the python3 binaries will not. This is because they're designed to run on the target, not the host you're building on so

Hi Paul, I didnt get u exactly . so for these what i can do can u please suggest .

We're missing important output here which would show the layers, versions and key config values. -- Paul Barker Konsulko Group

Hi, when i am compiling package using -> bitbake ostree-initrd ERROR: ostree-initrd-3-r0 do_install: Function failed: do_install (log file is located at

DEPEND on python3 and python3-native then. Ross

None of that output looks like an error to me. Could you share some more context? E.g. the bitbake command you ran, the initial output showing the layers, versions and key config values, what

This target builds and tests core-image-sato and associated SDKs, as otherwise the AB targets have been moved to core-image-weston. Signed-off-by: Alexander Kanavin <alex.kanavin@...> ---

Signed-off-by: Alexander Kanavin <alex.kanavin@...> --- config.json | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/config.json b/config.json index 51a540c..5ad3017 100644 ---

I believe the time has come for YP to be defaulting to Wayland and not X11. X11 is effectively deprecated technology at this point with only minimal maintenance; standalone X server will not

Signed-off-by: Alexander Kanavin <alex.kanavin@...> --- config.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/config.json b/config.json index def8d5a..51a540c

Signed-off-by: Alexander Kanavin <alex.kanavin@...> --- config.json | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/config.json b/config.json index

core-image-sato-sdk is a superset, and a much more useful one. Signed-off-by: Alexander Kanavin <alex.kanavin@...> --- config.json | 20 ++++++++++---------- 1 file changed, 10 insertions(+),

Hi team , while compiling a package i am getting following error :- Log data follows: | DEBUG: Executing python function extend_recipe_sysroot | NOTE: Direct dependencies are

I've been thinking about this and the reason I've not done this is release builds. I'm wondering if we we can somehow make the trigger release build specific. I think is is possible to do this, I've

Sure, I sent a patch for that. Alex

Those are run on a separate schedule, and in context of a-full only cause delays due to queues forming for single available workers. Signed-off-by: Alexander Kanavin <alex.kanavin@...> ---

I've been wondering about this but I suspect we should drop them from a-full instead... Cheers, Richard

The same builds are included in a-full, so they tend to get queued up and cause delays in builds completion, as there's only a single worker allocated to them. Let's run them less frequently to

bitbake mc:target1:target mc = qualifier keyword used to identify a multiconfig build by bitbake target1 = name of multiconfig ( e.g. first machine ) target = Firmware image name to be built for

<vaijayanthi.muralidharan@...> wrote: what is your failing recipe called (exact name )