Actually that was a problem with broken gcc package . It resolved when i cleaned the gcc and rebuilt the image. Another Problem iam facing is we have actually 2 machine configurations , Same kernel

Thanks for your reply. I am aware that recipe-sysroot has to be populated before and that's fine with anonymous functions not working, but even if I make sure that recipe-sysroot and

Hi Marek, Anonymous functions are run during parsing before anything is built. Therefore, I don't think it'll be possible to use a python module from a recipe in an anonymous function. In order to

Hello everyone, I am working on creating a custom class (basically own image signing) that will be using a client's python module, but to simplify I'll use as an example a python3 module Magic as it

Add LAYERPATH_meta-openssl-one-zero-two-fips to vardepsexclude for do_check_fips to improve sstate reuse This variable notifies the user of a machine specific path. Signed-off-by: Jate Sujjavanich

Signed-off-by: Jate Sujjavanich <jatedev@...> --- MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index 66a924c..e248803 100644 ---

From: John Edward Broadbent <jebr@...> Libhoth is usb protocol implementation which is required for hoth class devices Signed-off-by: John Edward Broadbent <jebr@...> ---

done

I see, that should be ok. I do see a few issues with the patch see below. This should be HOMEPAGE = "https://github.com/google/libhoth" This revision does not build with musl/clang atleast since

The examples are not separately buildable, and not installed. So there is currently no way to make a sperate ${PN}-examples. We don't need the examples now, but we are interested to know what you

<jebr=google.com@...> wrote: Dont we want to package the examples too ? perhaps in a ${PN}-examples or something ?

From: John Edward Broadbent <jebr@...> Libhoth is usb protocol implementation which is required for hoth class devices Signed-off-by: John Edward Broadbent <jebr@...> ---

Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage Attendees: Steve Sakoman, Joshua Watt, Saul Wold, Randy Macleod, Richard Purdie, Aryaman, Ross Burton, Alexandre Belloni, Tim

there seems to be something in the interaction between core layer with your custom layers, Usually issues of this nature are solved in the custom layers. Since its not a community layer, its not easy

First, Zeus is *very* old: https://wiki.yoctoproject.org/wiki/Releases says that it was end-of-life in August 2020. Please upgrade to something newer. Anyway, it looks like the opentelemetry

Greetings ! I am having requirement of integrating Opentelemetry in Yocto Zeus . Requesting your suggestions/procedure for integrating Opentelemetry in Yocto Zeus . Thanks in advance

We are making a Custom BSP Package for our Board using the YOCTO. I encountered with a problem during the build of Yocto image in Ubuntu 18.04. But the Same image successfully got built in the Ubuntu

This is unfortunately a known issue and is one reason I'd like to stop recipes downloading files to WORKDIR. Sadly changing that to fix this bug is very invasive and painful but I think we do need to

There's actually already a patch for that :) https://lists.yoctoproject.org/g/yocto/message/56880 Alex

I don't know if there are any Yocto users of it who might notice. Instead of dropping the testing completely, may be we should switch to building/testing just the core-image-minimal image on