Hi,
I've been happily building images for the Renesas R-Car platform using the
Yocto project until recently. After clearing the sstate-cache and
rebuilding, I'm now suddenly encountering an issue where the version of
OpenCV being installed into the host SDK and the one being installed into
the tar
Signed-off-by: Adrian Bunk
---
documentation/ref-manual/ref-variables.xml | 12 +++-
1 file changed, 3 insertions(+), 9 deletions(-)
diff --git a/documentation/ref-manual/ref-variables.xml
b/documentation/ref-manual/ref-variables.xml
index 0080364e4f..33afaa5f45 100644
--- a/documentati
Is this a solved problem? If so, what is the correct solution?
Here are some more details of the problem statement...
I want to verify that my read-only rootfs has not been modified when I
boot. So I bundle the checksum of the the rootfs in /etc/rootfs.hash
in my initramfs using something a lot
use wildcards
Signed-off-by: Armin Kuster
---
recipes-kernel/linux/{linux-stable_5.2.bbappend => linux-%_5.%.bbappend} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename recipes-kernel/linux/{linux-stable_5.2.bbappend =>
linux-%_5.%.bbappend} (100%)
diff --git a/recipes-kernel/linux/
apparmor-2.13.2-r0 do_package_qa: QA Issue: /usr/bin/aa-easyprof contained in
package apparmor requires /usr/bin/python3, but no providers found in
RDEPENDS_apparmor? [file-rdeps]
Signed-off-by: Armin Kuster
---
recipes-mac/AppArmor/apparmor_2.13.2.bb | 2 +-
1 file changed, 1 insertion(+), 1
Boot loops were being seen when booting with selinux enabled, when the
init system in use is systemd. Once logs were retrieved from the
failing system the error was found to be
selinux-init.sh[284]: /sbin/restorecon: Could not set context for
/sys/fs/cgroup/cpuacct: Read-only file system
selinux
Adrian,
Thanks for the update to the KERNEL_DEVICETREE variable. I have applied
this patch to the 2.8 version of the reference manual:
https://yoctoproject.org/docs/2.8/ref-manual/ref-manual.html#var-KERNEL_DEVICETREE
.
Scott
On Fri, Aug 23, 2019 at 8:06 AM Adrian Bunk wrote:
> Signed-off-by:
On 8/22/19 11:23 AM, Behnke, Jochen wrote:
Hello Randy,
thanks for your reponse and sorry for my late reaction.
In order to test, if the problem can be reproduced reliably, I
performed a clean rebuild as follows
$ source oe-init-build-env build-tca5-32
$ rm -rf tmp
$ rm -rf sstate-cache
$ bi
