Changqing Li (1): openssh: refresh patches to 8.5p1 Chen Qi (1): layer.conf: add hardknott to LAYERSERIES_COMPAT Yi Zhao (4): README.build: add "Known Issues" section openssh: refresh

Signed-off-by: Anuj Mittal <anuj.mittal@...> --- schedulers.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/schedulers.py b/schedulers.py index 920daab..9d81806

Keep meta-arm at master since there's no hardknott there yet. Signed-off-by: Anuj Mittal <anuj.mittal@...> --- schedulers.py | 12 +++++++++++- 1 file changed, 11 insertions(+), 1

Signed-off-by: Anuj Mittal <anuj.mittal@...> --- config.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config.json b/config.json index 5bfa240..3beb990 100644 ---

Hello, We are pleased to announce the Yocto Project 3.1.7 (dunfell-23.0.7) Release is now available for

Hi, Please join us for the upcoming OpenEmbedded Happy Hour on April 28 for Asia/Pacific timezones @ 2100/9pm UTC (5pm

I have created Rootfs with Rocko build for imx6. I am trying to use qt application with PostgreSQL database. Not able to access database. Showing log like : QSqlDatabase: QPSQL driver not

Khem: There are at least 4 zeus released tags, can you vouch for one of them to work properly with meta-clang ? Porting to dunfell might not be possible at this time... Would it be possible to build

No worries, thanks for the update!

Hi Ida My sincere apologies for the delay. I have now integrated this, but I did have to make a few changes: 1) Dropped the newline changes; these weren't related and also modified files that we

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