OpenEmbedded

openembedded@lists.linaro.org

106 discussions

/var/volatile not mounted as tmpfs on read-only rootfs when migrating to Warrior

by Ryan Harkin

Hi, I have a working system based on Sumo. The system boots with a read-only rootfs, then applies are read-write overlay for /etc. When I migrate to Warrior, systemd-resolved fails to start. If I mount the same rootfs via NFS, it starts and works fine. systemd-timesyncd is also failing, but I haven't looked into that yet. It also works fine on the NFS mounted system. The resolve problem seems to be caused by two things: - /var/volatile is read-only - /run/systemd/resolve has the wrong ownership drwxr-xr-x 2 systemd-network systemd-journal 80 Jul 12 16:23 resolve/ I think this permissions problem may be a result of the /var/volatile mounting problems; it looks fine on the NFS mounted system. If I manually mount /var/volatile (it's in fstab) and change the ownership on /run/systemd/resolve, the service starts just fine. I also notice that /tmp is not mounted at all, which may be related. Here are the various tmp mount points on my read-only rootfs: $ mount | grep tmp devtmpfs on /dev type devtmpfs (rw,nosuid,size=112036k,nr_inodes=28009,mode=755) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) overlay on /etc type overlay (rw,relatime,lowerdir=/tmp/lower/etc,upperdir=/tmp/upper/etc,workdir=/tmp/upper/work/etc) tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=23840k,mode=700) On the NFS mounted system, I see these: $ mount | grep tmp devtmpfs on /dev type devtmpfs (rw,relatime,size=118180k,nr_inodes=29545,mode=755) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) tmpfs on /tmp type tmpfs (rw,nosuid,nodev) tmpfs on /var/volatile type tmpfs (rw,relatime) tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=23840k,mode=700) As you can see, NFS has these extra mounts: tmpfs on /tmp type tmpfs (rw,nosuid,nodev) tmpfs on /var/volatile type tmpfs (rw,relatime) I've tried reverting a few commits that may be related, but I haven't had any luck working out things have changed, eg: c4acf1b531 2018-10-19 volatile-binds: use overlayfs if available [Matt Hoosier] Advice would be appreciated. Are there any particular areas I should be looking to work out what's going wrong? Kind regards, Ryan.

5 years, 11 months

widevine support

by tarani.nomula＠yahoo.com

Hi Team, I have downloaded the lhg-oe-manifest source and builded it successfully for Dragonboard-410c.After flashing it on device i am only able to play the clearkey encrypted video but when i am trying to play the widevine encrypted content,it is showing like there is no supported key system.Is there any support of playing widevine encrypted content in this code.If not can you help me how to play widevine encrypted video.I have downloaded the code from below manifest $repo init -u https://github.com/linaro-mmwg/lhg-oe-manifests.git -b morty It would be a great help for me if you provide me any way to get out of it. Thanks and RegardsN.Tarani

5 years, 11 months

RPB builds broken

by Anibal Limon

Hi, I noticed that the RPB builds for warrior and thud are failing due to Hikey (graphics stack), it has been some months happening if someone can take care of it will be good if not may be we need to make the decision and remove it. Regards, Anibal [1] https://ci.linaro.org/job/rpb-openembedded-warrior/ [2] https://ci.linaro.org/job/rpb-openembedded-thud/

5 years, 12 months

meta-rpb and yocto-check-layer

by Nicolas Dechesne

Daniel, as discussed, I've experimented with meta-rpb and the Yocto Compatible check scripts.. see : https://www.yoctoproject.org/docs/2.6/mega-manual/mega-manual.html#making-s… There are many obvious reasons why it's a good idea to make sure that layers can pass this script.. I was able to get meta-rpb to pass the compatibility check with the following patches: https://github.com/ndechesne/meta-rpb/tree/check-layer The simplest way to run the script is to use a copy of Poky git: $ git clone http://git.yoctoproject.org/git/poky $ cd poky $ source oe-init-build-env $ yocto-check-layer <oe-rpb folder>/layers/meta-rpb/ --dependency <oe-rpb folder>/layers/ The main things that the script will test are: 1. Adding your layer in bblayers.conf will not change any recipe content/checksum 2. All dependencies are properly tracked For meta-rpb, we depend on meta-virtualization (docker) and that layer breaks compatibility in many ways.. so I had to remove references to docker and meta-virt to run the script.. I will be doing a bit more testing/review, and submit the PR. cheers nico

6 years, 1 month

Linaro OE RPB warrior updates

by Nicolas Dechesne

hi, i've started to push some updates about OE warrior for our Linaro builds. The branch warrior was added to meta-rpb, meta-96boards, meta-qcom, meta-linaro, meta-backports. I have added a 'warrior' branch to the oe-rpb-manifest as well, see: https://github.com/96boards/oe-rpb-manifest/commit/dd60a2322845adb9cfe7e82e… Some layers still don't have a warrior branch, in which case we use master. I have submitted a change to start build based on warrior.. Let's see how things go with this new branch! cheers nico

6 years, 1 month

external-linaro-toolchain fails to build on thud branch

by Paul Barker

Hi all, I'm trying to use the thud branch of Yocto Project with the Arago distro and the Linaro toolchain. The external-linaro-toolchain.bb recipe includes glibc-package.inc from oe-core which has been modified in 2018 to install a makedbs.sh script [1] and to handle the floatn.h header introduced in glibc 2.26 [2]. The first change definitely breaks the external-linaro-toolchain recipe as no makedbs.sh script is present - in the oe-core glibc recipe this is included as a file and referenced in SRC_URI. The second change breaks if the Linaro toolchain includes a version of glibc prior to 2.26. I see that an attempt to fix the above issues has been posted to this mailing list [3] but this wasn't merged and no other fix has gone into the meta-linaro repository. The was also a report of this issue posted to the Yocto mailing list in January [4]. So it looks like this has been broken for a few months but obviously hasn't been noticed more widely. Is the external-linaro-toolchain recipe expected to work on the thud branch? If not, what should I be using instead? [1]: https://git.openembedded.org/openembedded-core/commit/?h=thud&id=13cf502fce… [2]: https://git.openembedded.org/openembedded-core/commit/?h=thud&id=650c59c8b6… [3]: https://lists.linaro.org/pipermail/openembedded/2019-January/000159.html [4]: https://lists.yoctoproject.org/pipermail/yocto/2019-January/043747.html -- Paul Barker Managing Director & Principal Engineer Beta Five Ltd

6 years, 2 months

[meta-linaro][PATCH] layer.conf: Update to warrior release name series

by Martin Jansa

Signed-off-by: Martin Jansa <Martin.Jansa(a)gmail.com> --- meta-aarch64/conf/layer.conf | 2 +- meta-bigendian/conf/layer.conf | 2 +- meta-ilp32/conf/layer.conf | 2 +- meta-linaro-integration/conf/layer.conf | 2 +- meta-linaro-toolchain/conf/layer.conf | 2 +- meta-linaro/conf/layer.conf | 2 +- meta-optee/conf/layer.conf | 2 +- 7 files changed, 7 insertions(+), 7 deletions(-) diff --git a/meta-aarch64/conf/layer.conf b/meta-aarch64/conf/layer.conf index b48cdc1..ffa0b19 100644 --- a/meta-aarch64/conf/layer.conf +++ b/meta-aarch64/conf/layer.conf @@ -13,4 +13,4 @@ BB_DANGLINGAPPENDS_WARNONLY = "true" LAYERDEPENDS_aarch64 = "linaro linaro-toolchain" -LAYERSERIES_COMPAT_aarch64 = "thud" +LAYERSERIES_COMPAT_aarch64 = "warrior" diff --git a/meta-bigendian/conf/layer.conf b/meta-bigendian/conf/layer.conf index afc3f6a..a1f3687 100644 --- a/meta-bigendian/conf/layer.conf +++ b/meta-bigendian/conf/layer.conf @@ -8,4 +8,4 @@ BBFILE_COLLECTIONS += "bigendian" BBFILE_PATTERN_bigendian := "^${LAYERDIR}/" BBFILE_PRIORITY_bigendian = "20" -LAYERSERIES_COMPAT_bigendian = "thud" +LAYERSERIES_COMPAT_bigendian = "warrior" diff --git a/meta-ilp32/conf/layer.conf b/meta-ilp32/conf/layer.conf index cd6dcaf..39e60f5 100644 --- a/meta-ilp32/conf/layer.conf +++ b/meta-ilp32/conf/layer.conf @@ -13,4 +13,4 @@ BB_DANGLINGAPPENDS_WARNONLY = "true" LAYERDEPENDS_ilp32 = "linaro linaro-toolchain" -LAYERSERIES_COMPAT_ilp32 = "thud" +LAYERSERIES_COMPAT_ilp32 = "warrior" diff --git a/meta-linaro-integration/conf/layer.conf b/meta-linaro-integration/conf/layer.conf index 0cdb87b..323f467 100644 --- a/meta-linaro-integration/conf/layer.conf +++ b/meta-linaro-integration/conf/layer.conf @@ -8,7 +8,7 @@ BBFILE_COLLECTIONS += "linaro-integration" BBFILE_PATTERN_linaro-integration := "^${LAYERDIR}/" BBFILE_PRIORITY_linaro-integration = "30" -LAYERSERIES_COMPAT_linaro-integration = "thud" +LAYERSERIES_COMPAT_linaro-integration = "warrior" # do not error out on bbappends for missing recipes BB_DANGLINGAPPENDS_WARNONLY = "true" diff --git a/meta-linaro-toolchain/conf/layer.conf b/meta-linaro-toolchain/conf/layer.conf index 9e31117..995f81e 100644 --- a/meta-linaro-toolchain/conf/layer.conf +++ b/meta-linaro-toolchain/conf/layer.conf @@ -8,7 +8,7 @@ BBFILE_COLLECTIONS += "linaro-toolchain" BBFILE_PATTERN_linaro-toolchain := "^${LAYERDIR}/" BBFILE_PRIORITY_linaro-toolchain = "30" -LAYERSERIES_COMPAT_linaro-toolchain = "thud" +LAYERSERIES_COMPAT_linaro-toolchain = "warrior" # do not error out on bbappends for missing recipes BB_DANGLINGAPPENDS_WARNONLY = "true" diff --git a/meta-linaro/conf/layer.conf b/meta-linaro/conf/layer.conf index 450a4b1..5b1f29e 100644 --- a/meta-linaro/conf/layer.conf +++ b/meta-linaro/conf/layer.conf @@ -8,7 +8,7 @@ BBFILE_COLLECTIONS += "linaro" BBFILE_PATTERN_linaro := "^${LAYERDIR}/" BBFILE_PRIORITY_linaro = "25" -LAYERSERIES_COMPAT_linaro = "thud" +LAYERSERIES_COMPAT_linaro = "warrior" # do not error out on bbappends for missing recipes (mysql5) BB_DANGLINGAPPENDS_WARNONLY = "true" diff --git a/meta-optee/conf/layer.conf b/meta-optee/conf/layer.conf index baf01d0..e5b3320 100644 --- a/meta-optee/conf/layer.conf +++ b/meta-optee/conf/layer.conf @@ -8,4 +8,4 @@ BBFILE_COLLECTIONS += "meta-optee" BBFILE_PATTERN_meta-optee := "^${LAYERDIR}/" BBFILE_PRIORITY_meta-optee = "8" -LAYERSERIES_COMPAT_meta-optee = "thud" +LAYERSERIES_COMPAT_meta-optee = "warrior" -- 2.17.1

6 years, 2 months

[PATCH] gcc-arm-8.2: switch from upstream svn to linaro/arm git sources

by Denys Dmytriyenko

From: Denys Dmytriyenko <denys(a)ti.com> This is to sync up with thud, which already uses git sources of linaro/arm gcc instead of upstream svn base. Signed-off-by: Denys Dmytriyenko <denys(a)ti.com> --- meta-linaro-toolchain/recipes-devtools/gcc/gcc-arm-8.2.inc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/meta-linaro-toolchain/recipes-devtools/gcc/gcc-arm-8.2.inc b/meta-linaro-toolchain/recipes-devtools/gcc/gcc-arm-8.2.inc index bf803cf..c47c320 100644 --- a/meta-linaro-toolchain/recipes-devtools/gcc/gcc-arm-8.2.inc +++ b/meta-linaro-toolchain/recipes-devtools/gcc/gcc-arm-8.2.inc @@ -24,7 +24,8 @@ LIC_FILES_CHKSUM = "\ " #BASEURI ?= "${GNU_MIRROR}/gcc/gcc-${PV}/gcc-${PV}.tar.bz2" -BASEURI ?= "svn://gcc.gnu.org/svn/gcc/branches/ARM;rev=263559;module=arm-8-branch" +SRCREV = "1a721bce9532193e63acdcdb56fc16e8ac70b20a" +BASEURI ?= "git://git.linaro.org/toolchain/gcc.git;protocol=https;branch=linaro-local/A…" SRC_URI = "\ ${BASEURI} \ @@ -74,7 +75,7 @@ SRC_URI = "\ BACKPORTS = "\ " -S = "${TMPDIR}/work-shared/gcc-${PV}-${PR}/arm-8-branch" +S = "${TMPDIR}/work-shared/gcc-${PV}-${PR}/git" #S = "${TMPDIR}/work-shared/gcc-${PV}-${PR}/gcc-${PV}" #S = "${TMPDIR}/work-shared/gcc-${PV}-${PR}/git" #S = "${TMPDIR}/work-shared/gcc-${PV}-${PR}/gcc-${RELEASE}" -- 2.7.4

6 years, 3 months

[thud/master][PATCH] external-arm-toolchain: libc.so linker script should use relative path

by Denys Dmytriyenko

From: Denys Dmytriyenko <denys(a)ti.com> libc.so linker script should use relative paths to not clash with host libs. Using absolute paths in libc.so is fine with standalone toolchain or when used inside a rootfs. But when used inside OE SDK for cross-compilation, the absolute path confuses compiler with libs from host environment. In the past, Linaro prebuilt toolchains always had relative paths inside libc.so linker script. Adjust it the same for the Arm prebuilt toolchain. Signed-off-by: Denys Dmytriyenko <denys(a)ti.com> --- .../recipes-devtools/external-arm-toolchain/external-arm-toolchain.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/meta-linaro-toolchain/recipes-devtools/external-arm-toolchain/external-arm-toolchain.bb b/meta-linaro-toolchain/recipes-devtools/external-arm-toolchain/external-arm-toolchain.bb index 6fb5a4d..a4067d8 100644 --- a/meta-linaro-toolchain/recipes-devtools/external-arm-toolchain/external-arm-toolchain.bb +++ b/meta-linaro-toolchain/recipes-devtools/external-arm-toolchain/external-arm-toolchain.bb @@ -233,6 +233,7 @@ do_install() { if [ -f ${D}${libdir}/libc.so ];then sed -i -e "s# /${EAT_LIBDIR}/${EAT_TARGET_SYS}# ../../${EAT_LIBDIR}#g" -e "s# /usr/${EAT_LIBDIR}/# /usr/lib/#g" -e "s# /usr/${EAT_LIBDIR}/${EAT_TARGET_SYS}# .#g" -e "s# /${EAT_LIBDIR}/ld-linux# ../../${EAT_LIBDIR}/ld-linux#g" ${D}${libdir}/libc.so sed -i -e "s# /${EAT_LIBDIR}/libc.so.6# /lib/libc.so.6#g" ${D}${libdir}/libc.so + sed -i -e "s# /lib# ../../lib#g" -e "s# /usr/lib# .#g" ${D}${libdir}/libc.so fi if [ -f ${D}${base_libdir}/libc.so ];then -- 2.7.4

6 years, 3 months

[PATCH 0/3] external-arm-toolchain fixes and enhancements

by Denys Dmytriyenko

From: Denys Dmytriyenko <denys(a)ti.com> This set cleans up and adds additional features to external-arm-toolchain recipe. It packages up libc binaries like ldconfig, locale, tzselect, ldd and so on. That results in a proper non-empty glibc-utils package, which gets pulled by LIBC_DEPENDENCIES variable defined in tclibc-glibc.inc in OE-Core It also packages up necessary static libs, stubs and headers for -dev variants of libgcc, libgfortran, etc., satisfying packagegroup-core-standalone-sdk-target recipe from OE-Core. Please merge this set to master and backport it to thud as well. Thanks. Denys Dmytriyenko (3): external-arm-toolchain: basic cleanup external-arm-toolchain: package up toolchain binaries external-arm-toolchain: also package up extra libs, stubs and headers .../external-arm-toolchain.bb | 45 ++++++++++++++++------ 1 file changed, 33 insertions(+), 12 deletions(-) -- 2.7.4

6 years, 3 months

← Newer
1
2
3
4
5
6
7
...
11
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

OpenEmbedded