From: Mingli Yu <mingli.yu@...> * see oe-core base.bbclass changes from: https://lists.openembedded.org/g/openembedded-core/message/143159

Few kernel testcases have dependencies on gperf-native, so we should keep it in DEPENDS. Regards, Naveen

I can confirm that Ive also seen this trying to build in the Yocto build appliance I downloaded yesterday....

Hi team, I am not able compile a core-image-minimal also. same issue facing here. PFA (local.conf) .

Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-3.2.rc1 We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2.

I have absolutely no need for python2, I made this abundantly clear when I created the meta-python2 layer. If you depend upon continuing support of python2 via the meta-python2 layer, this is your

Apologies for the marginally related reply, but the provided example triggered a reminder of a best practice we started doing that had some significant maintainability benefits. Instead of this

I think this will also link the app with newlib now which previously was using baremetal.

Can we use markdown syntax and call it README.md ? this helps with other infras like gitlab and github where this might be cloned to

A build flagged for QA (yocto-3.2.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-3.2.rc1 Build hash information: bitbake:

Signed-off-by: Aníbal Limón <anibal.limon@...> --- conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/layer.conf b/conf/layer.conf index

Current Dev Position: YP 3.2 Final Build Next Deadline: YP 3.2 M4 Feature Freeze - Now Next Team Meetings: Bug Triage meeting Thursday Oct. 22nd at 7:30am PDT

Hi Nikhil, We encourage people to avoid top-posting so that discussions are easier to read: https://wiki.yoctoproject.org/wiki/Community_Guidelines#Mailing_List_Guidelines Your description doesn't

It is, you just answered the wrong mail so my answer isn't in the body of this mail. You don't need to change anything in the networkmanager recipe. You need to add networkmanager-nmcli to the

* I hope this is gona be public * I did a diff between your recommended file, and mine, there is no diff, since it's from the same source. I understand that I had to install network-manager-nmcli, but

I changed in local.conf (ostree related stuffs ), and put it for compilation , that time i got these error

Please do review this one carefully, it continues to build for me and solves a build failure when using meta-zephyr but not DISTRO=zephyr (instead, a custom DISTRO and a MACHINE that sets

Instead of setting TCLIBC=3Dbaremetal and then adding newlib in various p= laces, just set TCLIBC=3Dnewlib directly. This also means we can use the standard DEPENDS instead of reinventing

--- README.txt | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/README.txt b/README.txt index be1ea39..a02659a 100644 --- a/README.txt +++ b/README.txt @@ -69,4 +69,15 @@ or $

Please keep the mailing list in copy so everyone can benefit from your progress/the solution, thanks! This is an option at build time (i.e. for the **recipe**). It just configures the piece of SW