Any one seen this before… ? SDK appears to be working okay without the inclusion of native python3 components, not sure how the inclusion breaks devtool…

Obviously this is to the wrong list! It escaped before I could stop it :D I've already resent to oe-core. Bruce On Tue, Apr 20, 2021 at 8:31 AM Bruce Ashfield

Under ../poky/meta/recipes-devtools the is “llvm”… Devtool search <component> Devtool sdk-install <component> Will add this component to my EXT SDK… Is this a fully functional

Hello, It might be a bit heavy but I usually install a text editor and python-periphery (https://github.com/vsergeev/python-periphery) (It did not know c-periphery but this is the same author) Before

From: Bruce Ashfield <bruce.ashfield@...> A recent fix to the kern-tools promoted some previously unseen issues to warnings. This commit fixes them by tagging some BT options as non-hardware so

I tend to use a reasonably standard image, usually the one that will evolve into the product, and once the network (usb, ethernet or wifi) is up, use "opkg install" to grab whatever else I need from

Hi All, This is the full report for yocto-3.1.7.rc1: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults ======= Summary ======== No high milestone

Hi, Multiple ways to fix this. One is to switch to using dunfell branches for the BSP SW stack, if they are available. Alternatively you can use the old zeus based BSP SW stack but for that you need

Hello, I'm actually migrating a yocto project zeus version to dunfell LTS to build my imx6 Linux system on this LTS release. Almost all works fine except the following message I try to understand when

The default behavior is to look for a bitbake command, which fails and produces a confusing output of [-1:]. [YOCTO #14208] Signed-off-by: Yi Fan Yu <yifan.yu@...> --- scripts/utils.py |

This is the default oe-core MACHINE value. Prevent error-reporting tool to report simply False. It was seen in check-layer where the MACHINE wasn't specified. [YOCTO #14208] Signed-off-by: Yi Fan

All, YP M+ or high bugs which moved to a new milestone in WW16 are listed below: Priority Bug ID Short Description Changer Owner Was Became High 14334 open-vm-tools not present in layer

All, The below were the owners of enhancements or bugs closed during the last week! Who Count ross@... 2 akuster808@... 2 randy.macleod@... 2 richard.purdie@... 1 Grand Total 7 Thanks,

All, Below is the list as of top 50 bug owners as of the end of WW16 of who have open medium or higher bugs and enhancements against YP 3.4. There are 135 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

Just to clarify, btrfs-tools has always had an LGPL-3.0 library (libbtrfsutil), the recipe just never declared it before. Upstream is relicensing that library to LGPL-2.1+, which should be done for

Hello, We are pleased to announce the Yocto Project 3.3 (hardknott-25.0.0) Release is now available for

+1. Ross <richard.purdie@...> wrote:

btrfs-tools has changed to LGPL-3.1 so to allow util-linux to build, remove the dependency from its ptest package. This may regress some ptests but keeps the gplv2 layer working. Signed-off-by:

Hi Robert, Having the device tree compiler on the target has been useful for me in the past to check the actual content of the device tree using commands such as: * dtc -I fs -O dts