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

Hi Nicolas, I guess part of your problem is that DISTRO does not end up in any package grouping, unlike MACHINE and ARCH and so. So if OE/Yocto does The Right Thing, this means that it will have to

This works as intended. So the problem is that when qemu runs from testimage it tries to open a graphical window using X and that for some reason fails. You can perhaps force a no-graphical execution

Reviewed-by: Michael Opdenacker <michael.opdenacker@...> Indeed, it should be applied right after the latest pull request from master-next is applied. Cheers Michael. -- Michael Opdenacker,

Build and test core-image-full-cmdline with the linux-yocto-rt kernel, adding the new rt test to verify that the kernel is actually the PREEMPT_RT version expected. Signed-off-by: Ross Burton

Hello Alexander I am putting some of lines of qemu output of nographic here . [ 0.053290] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level) [ 0.053300] ACPI: INT_SRC_OVR (bus 0

Can I also see the output of 'runqemu nographic' please? Alex

Hi Poornesh This is not supported in Zeus, but otherwise you may be interested in the "overlay-etc"

Hi, This seems like a good use for overlayfs-etc IMAGE_FEATURES? c.f. https://docs.yoctoproject.org/ref-manual/features.html#image-features See