Hi all, I'm having trouble figuring out how to fix my issues with the new intel NUC gen 11 (NUC11TNBi5). At the moment I'm testing with the following meta-layer poky (hardknott) meta-openembedded

Disables debuginfod when using MingGW. This feature brings in unbuildable dependencies and can't be used. Signed-off-by: Joshua Watt <JPEWhacker@...> ---

Hello All, I am tyro in yocto , I am having a strange issue where I am trying to build the recipe using devtool build <recipe> . It fails first time but builds second time. It flags an error

What I think happened is that glibc simply got better at linking, optimised the runtime bits to the fullest, and any benefits prelink may once have had aren't there anymore. Which is IMO fine - I am

The numbers certainly don't look convincing, thanks for running the tests. Mark and I did briefly talk yesterday and whilst Mark can/will speak up, the summary was "drop it". What makes me sad is

summarize_top_output.py is used to summarize the top output that is captured during autobuilder intermittent failures. Use the script to summarize the host top output and publish the summary that is

From: Kai Kang <kai.kang@...> The patch fix-ldblibdir.patch has been dropped when update sssd to 2.5.0. But it fails to start sssd without this patch. So add it back. Signed-off-by: Kai

Signed-off-by: Federico Pellegrin <fede@...> --- .../{aircrack-ng_1.3.bb => aircrack-ng_1.6.bb} | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) rename

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

I think the advantage is not on high end CPUs but more on less powerful ones, so perhaps trying it on something like rpi0 or lower would be good

I went ahead and ran some quick benchmarks myself. Specifically: 1. Running 'free' after things have settled down at boot: a) without prelink core-image-sato-sdk total used

Current Dev Position: YP 3.4 M2 Next Deadline: 12th July 2021 YP 3.4 M2 build Next Team Meetings: Bug Triage meeting Thursday June 17th at 7:30am PDT

From: Yann Dirson <yann@...> This is a RK3328 board from Pine64. Board details at https://wiki.pine64.org/wiki/ROCK64. Default image is built to boot from SD-card. Building an image

In fact we already have rock-pi-e.wks doing this. Let's do the minimum for now for this to get merged, and we'll improve incrementally. Eg. only now I realize, through the presence of

From: Kai Kang <kai.kang@...> /var/run is deprecated and set pid path with /run to store pid files for the SSSD. Signed-off-by: Kai Kang <kai.kang@...> ---

True. We could definitely use some cleanup in this area. If you want to propose something that's going to work, I'll add it. Also, when adding a new board, please update the top-level

Oh, right, copypaste rules around here, so Garmin does have a role but something may be missing :) Right that was something I wondered how to deal with and forgot (and note that for the nanopi-m4 I

Unfortunately I think you mirrored the wrong tarballs. The problematic ones are specifically the six tarballs coming from http://icedtea.classpath.org/hg/ and I am not seeing them mirrored. See the

This ensures that DISTRO_FEATURES can translates correctly for qtbate packageconfigs and we can get right platforms enabled Signed-off-by: Khem Raj <raj.khem@...> --- conf/layer.conf

All, YP M+ or high bugs which moved to a new milestone in WW24 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 3362 Improve dependency analysis