Summary: Build: 20210420-1 had 23 triggers and isn't really worth analyzing. Stay tuned for what is hopefully better data with a higher timeout threshold. There is a nice looking pair of graph

<steven.monsees@...> wrote: I think for future development you should look into dunfell or newer since those are supported releases. clang toolchain has evolved rapidly in past few years

There appears to be an issue with build zeus based meta-clang under zeus platform... I followed steps off meta-clang page, and from the work I did with meta-clang under "Rocko" about a year ago, a

Yocto Technical Team Minutes, Engineering Sync, for April 20, 2021 archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit == announcements == The upcoming Yocto

this should be mips64el

this is intentional, when you use meta-clang, then llvm is preferred from LLVM since them we have consistent version of llvm for clang and others.

Current Dev Position: YP 3.4 M1 Next Deadline: 7th June 2021 YP 3.4 M1 build Next Team Meetings: Bug Triage meeting Thursday Apr. 22nd at 7:30am PDT

Signed-off-by: Armin Kuster <akuster808@...> --- recipes-core/packagegroup/packagegroup-core-security.bb | 3 +++ 1 file changed, 3 insertions(+) diff --git

So, does anyone know proper usage here? Is this a fully functional llvm drop under ../poky/meta/recipes-devtools ? Is it compatible with meta-clang?, and can they be used together to build 3rd

I noticed similar behavior… I am running zeus 3.0.4, “devtool sdk-install llvm” will get llvm 8.0.1… When I build meta-clang, and I set TOOLCHAIN?=”clang” in local.conf it appears

Hi Steven, I used meta-clang in my recipes and I noticed that: 1. The current release of poky uses LLVM v11.1.0 by default (poky/meta/recipes-devtools/llvm/llvm_git.bb) 2. Meta-clang requires LLVM

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