On Mon, 3 Oct 2022 19:11:34 +0200 "Michael Opdenacker via lists.yoctoproject.org" <michael.opdenacker=bootlin.com@...> wrote: The manpage for git 2.34.1 has this extra detail: --

Hi Quentin, "Quentin Schulz" <foss@...> wrote: Sure this is correct? 'git clean -ffdx' does not revert changes to tracked files, be them staged or not. Same here. -- Luca Ceresoli,

Hi Quentin, In both cases, why "-ffdx"? Isn't it the same as "-fdx" (just checking the manual page). Cheers Michael. -- Michael Opdenacker, Bootlin Embedded Linux and Kernel

Hi all, Forgot to say this was not tested. Let's run this on the autobuilder and see if it helps? Is there a way to try without merging? Cheers, Quentin

From: Quentin Schulz <quentin.schulz@...> It happened that the git repositories were dirty and resulted in incorrect files being used. Let's use git clean -ffdx to force

Merged.

Hello Alexander, Please find log.do_rootfs file for the image.

Signed-off-by: Yi Zhao <yi.zhao@...> --- meta-cgl-common/conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-cgl-common/conf/layer.conf

Fix buildpaths warning: WARNING: resource-agents-4.5.0-r0 do_package_qa: QA Issue: File /lib/systemd/system/ldirectord.service in package ldirectord contains reference to TMPDIR

It helps if you show log.do_rootfs for the image, so it's possible to inspect what actually got installed into it. Alex

Hello All, I have made a preempt-rt image with "core-image-rt" by including the following line in local.conf file. PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt" IMAGE_CLASSES += "testimage

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

Tried PACKAGECONFIG:append:aarch64:pn-mesa = ' gallium-llvm It goes pretty far, but then we get back to: ../mesa-22.2.0/meson.build:1782:2: Unhandled python exception Am 30. September 2022 22:53:22

Host is x86-64 ubuntu, guest is aarch64 yocto. Am 30. September 2022 22:53:22 MESZ schrieb Alexander Kanavin <alex.kanavin@...>: -- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail

I added your line to mesa.inc now it complains over llvm disabled again. Am 30. September 2022 22:39:44 MESZ schrieb Alexander Kanavin <alex.kanavin@...>: -- Diese Nachricht wurde von meinem

That depends on what is your target. If you're running qemu on a x86 host, it's better to not do software emulation and build for qemux86_64 as well, and then run qemu with kvm, so it

X86-64 is right or do you mean arm? Am 30. September 2022 22:39:44 MESZ schrieb Alexander Kanavin <alex.kanavin@...>: -- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

You might want to try enabling gallium-llvm only for the target mesa: PACKAGECONFIG:append:x86-64:pn-mesa = ' gallium-llvm' Alex

I deleted the whole build directory, recreated it, only added the arm switch in local conf and your changes for mesa.inc. After a few hours of building core-image-weston it again complains that it

Series verified in a batch CI job (on top of the other submitted patches). See https://gitlab.com/jonmason00/meta-zephyr/-/pipelines/655489776 Tested-by: Jon Mason <jon.mason@...>