Thanks for the patch and the SoB line. I'm going to apply this patch, but I'm going to amend the commit message to capture some of the conversation we've had. There's a chance we'll want to know "why"

Ah, good catch. I'm using sysvinit.

Hello: I am running zeus 3.0.4… A vendor has supplied us with a generic license.txt file, which we were able to add to the acexpci recipe we use to build in their package. The license

Am 24.09.21 um 06:46 schrieb Khem Raj: I am using systemd

Yocto has built-in qemu targets for this purpose, and associated infrastructure to start qemu VMs and run tests in them. But to make it practical, these qemu images need to be started on a baremetal

CVE-2021-36086: The CIL compiler in SELinux 3.2 has a use-after-free in cil_reset_classpermission (called from cil_reset_classperms_set and

Hi, We are starting a new project using Yocto to build a custom Linux image which matches our needs. We are new to Yocto and still trying to figure out the best way to work with it. Especially, if it

Hello Enrico, an eSDK would be enough to do everything, however I would demand the entire development system if I were to start a project, but that is my opinion. I don't know well Node-RED but using

Hello Marco, In your opinion isn't enough to ask for eSDK? for instance if i want to add Node-RED, it would be difficult to build with devtool? because i've seen that it doesn't resolve dependencies

With the eSDK i've to use devtool right?

Hello Enrico, usually nowadays every honest hardware manufacturer provides all the sources of the BSP and the development system to their customers. Try asking your supplier for them. -- Marco

As OE-core explicitly have added depends for qemu-helper addto_recipe_sysroot task, which breaks zephyr-qemuboot implementation of adding build

It has GCC-11 fixes. https://github.com/zephyrproject-rtos/zephyr/issues/35707 Commits included: 2d6322d74a demand_paging: eviction/nru: fix incorrect dirty bit return val 25771e6928 drivers:

its hard to say what might be going on. Perhaps enable builds with V=1 so you can see if its always failing to compile at same file. or atleast you can get one file where it fails then you can

IMAGE_INSTALL += "gcov gcov-symlinks"

are you both using systemd or sysvinit

Hi, Regarding the INSANE_SKIP: as that files get packed in the "-dev" package, you should probably then accordingly have: INSANE_SKIP_${PN}-dev += "dev-elf" Cheers, Federico

No, it doesn't. Those entries are ignored except /boot.One interesting thing: i always had that bunch of malformed fstab entries.Before the change from static to uuid it looked like this in

Signed-off-by: MarkusVolk <f_l_k@...> --- conf/machine/include/rockchip-wic.inc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/conf/machine/include/rockchip-wic.inc

My rock pi 4 refused to boot with the latest changes because there are fa= lse entries written to fstab. Fix this by using uuid for all partitions Signed-off-by: MarkusVolk <f_l_k@...> ---