I still occasionally get the ping error on dunfell autobuilder runs, so I suspect it needs something similar to this patch. I'm not conman literate, so if someone who is can create a patch

A fairly unique workflow (since no one else has seen this), but obviously supported! So all good on that front. I'd prefer to move towards simplification, and drop the hardcoded meta directory

<bruce.ashfield@...> wrote: Just trying to short-cut any further ping-ponging by providing an over abundance of detail. The build sub-directory still exists, but because

I'm aware of how the basics work :) I've run more builds than I'd like to admit in a very similar configuration, with many more kernel configuration issues than most .. and I've never triggered this

<bruce.ashfield@...> wrote: It's pretty straightforward. The default yocto steps create a directory tree that contains a directory called meta (along with meta-poky, meta-selftest, build,

It hasn't been used in quite some time, but the design intent is what I stated. So it would be better to make that later reference more flexible. You have described the problem, but not how you've

I thought so! ;-) Richard told me in IRC that the 3.3.6 build has happened and is in QA now so let's handle this glibc update in WR Linux/LTS21. ../Randy -- # Randy MacLeod # Wind River Linux

It's not working as intended though. While the check for the "meta" path is done in the cwd of the bitbake parent process, the actual usage of it is done in ${S}: if analysis: outfile =

That isn't actually a problem, and is the design intent of that check. It allows a temporary/local override of the meta data, simply by creating a 'meta' subdir. Bruce -- - Thou shalt not follow the

do_kernel_configcheck utilizes pathnames relative to the sourcedir but does not specify ${S} in [dirs]. tasks that do not specify [dirs] default to the cwd of the bitbake parent process. This can

From: Bruce Ashfield <bruce.ashfield@...> Updating linux-yocto/5.4 to the latest korg -stable release that comprises the following commits: dc213ac85601 Linux 5.4.190 a83a18c4c903

From: Bruce Ashfield <bruce.ashfield@...> Updating linux-yocto/5.4 to the latest korg -stable release that comprises the following commits: 2845ff3fd344 Linux 5.4.188 993c23880bce llc:

From: Bruce Ashfield <bruce.ashfield@...> Updating linux-yocto/5.4 to the latest korg -stable release that comprises the following commits: 8e24ff11b5d2 Linux 5.4.186 fcbdaa6a3c92

From: Bruce Ashfield <bruce.ashfield@...> Updating linux-yocto/5.4 to the latest korg -stable release that comprises the following commits: e7d1268f5671 Linux 5.4.183 5817c13cd6dc

From: Bruce Ashfield <bruce.ashfield@...> Updating linux-yocto/5.4 to the latest korg -stable release that comprises the following commits: 866ae42cf478 Linux 5.4.182 fb2bbb7d3021

Hi Randy, Sorry for the misunderstanding from my side. I am going through the list again and it seems like the required patch was not part of the Hardknott. It was rather a part of the Master

The files in /sysroot-only are intended to make it into the recipes sysroot output, but not into the package. However, if do_package is run before do_populate_sysroot, the files are removed. Use a

From: Andrei Gherzan <andrei.gherzan@...> Signed-off-by: Andrei Gherzan <andrei.gherzan@...> --- .../automake/0001-Drop-ar-u-argument.patch | 35 +++++++++++++++++++

Ah good. I'm not sue why my repo seemed to be behind. There are still 23 commits that could be picked up, several of which are marked as bug fixes but since we have the patch that was my

Agreed. I'll send v2. Andrei