All, The below were the owners of enhancements or bugs closed during the last week! Who Count mhalstead@... 1 akuster808@... 1 Grand Total 2 Thanks, Stephen K. Jolley Yocto Project

All, Below is the list as of top 48 bug owners as of the end of WW52 of who have open medium or higher bugs and enhancements against YP 3.3. There are 85 possible work days left until the final

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on

If you remove "wic" from the IMAGE_TYPES, it won't be built. https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-IMAGE_TYPES Bruce -- - Thou shalt not follow the NULL

<p32=tuta.io@...> wrote: Nope. There is no way to do this on the build host. Not without complex use of qemu-user to generate and package for the target architecture. We cannot

Hi: Was wondering if there was a way to exclude wic image from being built. Many thanks, and Happy New year. Howard

friend recently asked me for recommendations for entry-level, linux-based drones whose software is generated by yocto project, so it could be used as a learning experience. as in, the fun would be

Hello, The execution of "make scripts prepare" did actually solve the issue, thank you very much for your help! However, the need to manually execute this command on the target platform made me look

You might have better luck on the meta-xilinx mailing list. They should know the details for their BSP. More info on Xilnx layers and a pointer to subscribe info to the mailing list is

Hi, You need to run "make scripts prepare" in /usr/src/kernel before trying to compile kernel modules on target. Ovidiu

Hello everyone, I am using the Yocto-based build system provided by NXP (primarily via the meta-freescale layer) to create Linux images for an i.MX 8M board and would like to develop small kernel

Paul, Thanks for the reply. I am using Xilinx-SDK based : Linux version 4.19.0-rt1-xilinx-v2019.1 Can you please let me know how to verify the yocto version running on target. Thanks, Raghu

<raghu.icecraft@...> wrote: Yocto Project doesn't have a version "2019.1", see https://wiki.yoctoproject.org/wiki/Releases. I guess you're using a vendor supplied BSP or SDK with that

Hello, I have upgraded my kernel poky to 2019.1 version, here i am unable to find chpasswd utility because of which i am unable to set password to my root-user. Can you please let me know if the

Bisect points at the commit that introduced the hard pseudo abort: /MR

One more thing: I tried reverting the linux-libc-headers version change (57d5f4ad410d4e9d55bdd9734bf5ab8fa6667a53) and that fails in the same way, so it's not that. I also realized that the yocto-3.2

Hi, I hit the same issue, also while trying things out on WSL2 (not committed enough to build a dedicated workstation/VM). I found a few more things: This seems to be a pseudo abort with: I tried to

i'm not fluent enough in ruby to want to submit a patch for this, so i'll let someone higher up the food chain handle it. trying to build a number of "native" ruby recipes from meta-openstack, and

to prepare for trying to build a number of ruby gems for WR LTS19 (effectively zeus, as always), i thought i'd start simple and begin with building for qemux86-64 with gatesgarth so i could

We encountered a runtime error for auditctl on lib32 image for aarch64: root@qemuarm64:~# auditctl -a always,exit -F arch=b32 -S adjtimex -S settimeofday -k time_change arch elf mapping not