My rock pi 4 refused to boot with the latest changes because there are fa= lse entries written to fstab. Fix this by using uuid for all partitions --- wic/rockchip.wks | 16 ++++++++-------- 1 file

--- conf/machine/include/rockchip-wic.inc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/conf/machine/include/rockchip-wic.inc b/conf/machine/include= /rockchip-wic.inc index 15010a0..30b0d57

yes was seeing same. Can you turn this into a patch and send?

Hi, with this change my rock-pi-4 doesnt boot up and falls to emergency shell because wic includes wrong devices into fstab. For some reason it assumes /dev/sda1. I was able to fix this

A not so well-known feature of the WIC bootimg-partition plugin is that it can install files into different partitions. For that the variable IMAGE_BOOT_FILES has to be defined as one of the

Tried adding googletest to TOOLCHAIN_TARGET_TASK. The gtest .h files are still not showing up. Thanks,

The file is being created with python's tempfile function which will make it secure. Secure in this context means 00600... I suspect you're right that creating a file securely here with this

From: Alexander Kanavin <alex@...> In addition to the testresult json, testimage class now also provides task logs and qemu console output (splitted into folders by image name to avoid

its trying to create the file with 0600 mask. I wonder whats your global umask set to. and perhaps the user is not same when bitbake it running ?

Hi All, I have a server that's holding downloads and sstate-cache. I have a docker-compose file with nfs server that exposes the dowloads/sstate-cache volume. When I mount that in my PC and set the

The .h files will be in dev pkg in this case googletest-dev what happens if you add googletest to TOOLCHAIN_TARGET_TASK

From: Richard Purdie <richard.purdie@...> Signed-off-by: Richard Purdie <richard.purdie@...> (cherry picked from commit

Hi, Now I included googletest to the IMAGE_INSTALL in my image file, and built both board image and SDK image. I can see libgtest.so is available in both images. However, gtest/gtest.h is a not

Hi all, This is the full report for yocto-3.1.11.rc2: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults ======= Summary ======== No high

Hard to say without understanding how it failed. What was the error? You probably need to match python3 and python3-native versions but I don't know if you did. Cheers, Richard

The best way is to fix the app. Such major downgrades are firmly uncharted territory, and aren't supported. If you have errors, you need to figure out yourself how to fix them - but if you provide the

Hi, Currently we are building a Yocto image based on Hardknott release, which includes python 3.9.4. Due to a App constraint, we have to downgrade Python3 to 3.8. I tried copying over 3.8.5 bb file

Thanks Konrad. That worked.

Current Dev Position: YP 3.4 M4 Next Deadline: 4th Oct. 2021 YP 3.4 M4 build Next Team Meetings: Bug Triage meeting Thursday Sept. 23rd at 7:30am PDT

http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-graphics/spir/spirv-tools_2021.2.bb#n34 (and the next lines) might give you a hint what to do in this case. Although one could also