check https://layers.openembedded.org/layerindex/branch/master/recipes/ if its not there then perhaps no one published it yet.

#frr

try to see if /bin/ls exists. if its not there then maybe its deleted somehow. best is to flash a new rootfs > >

<maaloulsafouane@...> wrote: also add following to machine conf file. RPI_KERNEL_DEVICETREE = " \ broadcom/bcm2710-rpi-zero-2.dtb \ "

Signed-off-by: Khem Raj <raj.khem@...> --- README | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/README b/README index cec1b53..cc63d0a 100644 --- a/README +

<richard.purdie@...> wrote: From a different data point, we have clipped the parallelism for XZ and ZSTD internally to very low ( 2 and 4 ) and it has in fact reduced unexpected failur

to get more info, can you try adding IMAGE_LINGUAS = " " and see if this changes anything ?

#yocto #zeus

Look into chromium recipe

meta-rockchip does not have honister branch for now. So it expects master to keep working with honister for now. kernel upgrades are already committed into honister branch on meta-yocto-bsps so fix it

I am not yet convinced why should we have such version specific patch

<quentin.schulz@...> wrote: once dot release is out then thats whats maintained not the original release since they are incremental. the anon python to apply a patch. Can you explain

<quentin.schulz@...> wrote: Patching piece below looks quite a bit. lets just fix v5.14.14 and dont worry about 3.4

Signed-off-by: Khem Raj <raj.khem@...> --- recipes-devtools/flex/flex_%.bbappend | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 recipes-devtools/flex/flex_%.bbappend diff --git a/rec

do you have stack trace ? that might give some more info on whats going on

#golang

Whatever you are setting for LICENSE Variable inside recipe there should be a file with same name stored inside One of LICENSE_PATH directories.

at one point, I had ppc64le working as SDKMACHINE target as well.

It’s also good to post your build configuration that bitbake prints at the beginning of build this could also be other policies like default libc being musl vs glibc is in play etc

OK, I think it will be a while before I can get to tip if dunfell though.

it was dunfell primarily

We have seen a lot of hung builds when we used this option internally on builders, Additionally some packages like bison started to fail intermittently which seemed like a parallel build issue but nev

Hi Jared Please see [1] usually sending to the right mailing list and CCing the maintainers is the usual way to send patches [1] https://git.yoctoproject.org/cgit/cgit.cgi/meta-qt4/tree/README