Date   

Re: unparsed line #yocto

Michael Ho
 

It looks like you have a dunfell yocto setup which doesn't support that new recipe syntax. Maybe you need to check out the dunfell branch of those meta layers to get them to be compatible.

Michael

On Tue, 28 Dec 2021, 7:12 pm Kevin Kettinger, <kkettinger@...> wrote:
Hello,

after including the meta-qt5 and meta-boot2qt layer from https://code.qt.io/cgit/yocto, and adding them to my bblayers.conf, bitbake breaks directly while parsing the recipes:
---------------------------------------------
ERROR: ParseError at /home/yocto/projects/faseroptik-dunfell/build/../layers/meta-qt5/classes/cmake_qt5.bbclass:4: unparsed line: 'DEPENDS:prepend = "${QTBASEDEPENDS} "'                                                                                                                                    | ETA:  --:--:--

Summary: There was 1 ERROR message shown, returning a non-zero exit code.
---------------------------------------------

If i restart bitbake, the offending file changes now and then, but just for completion, here is the file:
---------------------------------------------
inherit cmake
inherit qmake5_paths

DEPENDS:prepend = "${QTBASEDEPENDS} "
QTBASEDEPENDS = "qtbase qtbase-native"
QTBASEDEPENDS:class-native = "qtbase-native"
QTBASEDEPENDS:class-nativesdk = "nativesdk-qtbase qtbase-native"

EXTRA_OECMAKE:prepend = " \
    -DOE_QMAKE_PATH_PREFIX=${OE_QMAKE_PATH_PREFIX} \
    -DOE_QMAKE_PATH_HEADERS=${OE_QMAKE_PATH_HEADERS} \
    -DOE_QMAKE_PATH_LIBS=${OE_QMAKE_PATH_LIBS} \
    -DOE_QMAKE_PATH_ARCHDATA=${OE_QMAKE_PATH_ARCHDATA} \
    -DOE_QMAKE_PATH_DATA=${OE_QMAKE_PATH_DATA} \
    -DOE_QMAKE_PATH_BINS=${OE_QMAKE_PATH_BINS} \
    -DOE_QMAKE_PATH_LIBEXECS=${OE_QMAKE_PATH_LIBEXECS} \
    -DOE_QMAKE_PATH_PLUGINS=${OE_QMAKE_PATH_PLUGINS} \
    -DOE_QMAKE_PATH_QML=${OE_QMAKE_PATH_QML} \
    -DOE_QMAKE_PATH_TRANSLATIONS=${OE_QMAKE_PATH_TRANSLATIONS} \
    -DOE_QMAKE_PATH_DOCS=${OE_QMAKE_PATH_DOCS} \
    -DOE_QMAKE_PATH_SETTINGS=${OE_QMAKE_PATH_SETTINGS} \
    -DOE_QMAKE_PATH_EXAMPLES=${OE_QMAKE_PATH_EXAMPLES} \
    -DOE_QMAKE_PATH_TESTS=${OE_QMAKE_PATH_TESTS} \
    -DOE_QMAKE_PATH_HOST_PREFIX=${OE_QMAKE_PATH_HOST_PREFIX} \
    -DOE_QMAKE_PATH_HOST_BINS=${OE_QMAKE_PATH_HOST_BINS} \
    -DOE_QMAKE_PATH_HOST_DATA=${OE_QMAKE_PATH_HOST_DATA} \
    -DOE_QMAKE_PATH_HOST_LIBS=${OE_QMAKE_PATH_HOST_LIBS} \
    -DOE_QMAKE_PATH_EXTERNAL_HOST_BINS=${OE_QMAKE_PATH_EXTERNAL_HOST_BINS} \
    -DOE_QMAKE_PATH_QT_HEADERS=${OE_QMAKE_PATH_QT_HEADERS} \
    -DOE_QMAKE_PATH_QT_ARCHDATA=${OE_QMAKE_PATH_QT_ARCHDATA} \
    -DOE_QMAKE_PATH_QT_DATA=${OE_QMAKE_PATH_QT_DATA} \
    -DOE_QMAKE_PATH_QT_BINS=${OE_QMAKE_PATH_QT_BINS} \
    -DOE_QMAKE_PATH_QT_TRANSLATIONS=${OE_QMAKE_PATH_QT_TRANSLATIONS} \
    -DOE_QMAKE_PATH_QT_DOCS=${OE_QMAKE_PATH_QT_DOCS} \
    -DOE_QMAKE_PATH_QT_SETTINGS=${OE_QMAKE_PATH_QT_SETTINGS} \
    -DOE_QMAKE_PATH_QT_EXAMPLES=${OE_QMAKE_PATH_QT_EXAMPLES} \
    -DOE_QMAKE_PATH_QT_TESTS=${OE_QMAKE_PATH_QT_TESTS} \
"
---------------------------------------------

The exact same layer with the exact same commit & files is working fine on the original boot2qt environment, but not on my environment.

My bblayers.conf looks like this:
---------------------------------------------
LCONF_VERSION = "7"

BBPATH = "${TOPDIR}"
BBFILES ?= ""

BBLAYERS ?= " \
  ${TOPDIR}/../layers/meta-toradex-nxp \
  ${TOPDIR}/../layers/meta-freescale \
  ${TOPDIR}/../layers/meta-freescale-3rdparty \
  ${TOPDIR}/../layers/meta-toradex-tegra \
  ${TOPDIR}/../layers/meta-toradex-bsp-common \
  ${TOPDIR}/../layers/meta-openembedded/meta-oe \
  ${TOPDIR}/../layers/meta-openembedded/meta-filesystems \
  ${TOPDIR}/../layers/meta-openembedded/meta-gnome \
  ${TOPDIR}/../layers/meta-openembedded/meta-xfce \
  ${TOPDIR}/../layers/meta-openembedded/meta-initramfs \
  ${TOPDIR}/../layers/meta-openembedded/meta-networking \
  ${TOPDIR}/../layers/meta-openembedded/meta-multimedia \
  ${TOPDIR}/../layers/meta-openembedded/meta-python \
  ${TOPDIR}/../layers/meta-freescale-distro \
  ${TOPDIR}/../layers/meta-toradex-demos \
  ${TOPDIR}/../layers/meta-boot2qt/meta-boot2qt \
  ${TOPDIR}/../layers/meta-boot2qt/meta-boot2qt-distro \
  ${TOPDIR}/../layers/meta-qt5 \
  ${TOPDIR}/../layers/meta-toradex-distro \
  ${TOPDIR}/../layers/meta-yocto/meta-poky \
  ${TOPDIR}/../layers/openembedded-core/meta \
  ${TOPDIR}/../layers/meta-mender/meta-mender-core \
  ${TOPDIR}/../layers/meta-mender-community/meta-mender-toradex-nxp \
  ${TOPDIR}/../layers/meta-mender/meta-mender-demo \
  "
---------------------------------------------

On the working boot2qt environment poky 3.1.11 is used, i'm using poky 3.1.8.

Is there anything i can do to track this issue down? bitbake -v doesn't report more infos.

I appreciate any help here, thank you.

Best regards,
Kevin



Re: /bin/sh: 1: bison: not found while compiling own kernel module with poky-dunfell #bitbake

Markus Volk
 

hello,

try to add 'bison-native' to DEPENDS.

Am 29.12.21 um 07:16 schrieb prashantsingh@...:

hello team,
I'm trying to build my own kernel module with yocto for raspberry-pi kernel, but it's giving me error that "bison not found", as-

DEBUG: Executing shell function do_compile
NOTE: make -j 12 KERNEL_SRC=/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work-shared/raspberrypi3/kernel-source KSRC=/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work-shared/raspberrypi3/kernel-build-artifacts KERNEL_PATH=/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work-shared/raspberrypi3/kernel-source KERNEL_VERSION=5.4.72-v7 CC=arm-poky-linux-gnueabi-gcc  -mno-thumb-interwork -marm -fuse-ld=bfd -fmacro-prefix-map=/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work/raspberrypi3-poky-linux-gnueabi/ax88772/1.0-r0=/usr/src/debug/ax88772/1.0-r0                      -fdebug-prefix-map=/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work/raspberrypi3-poky-linux-gnueabi/ax88772/1.0-r0=/usr/src/debug/ax88772/1.0-r0                      -fdebug-prefix-map=/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work/raspberrypi3-poky-linux-gnueabi/ax88772/1.0-r0/recipe-sysroot=                      -fdebug-prefix-map=/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work/raspberrypi3-poky-linux-gnueabi/ax88772/1.0-r0/recipe-sysroot-native=  -fdebug-prefix-map=/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work-shared/raspberrypi3/kernel-source=/usr/src/kernel LD=arm-poky-linux-gnueabi-ld.bfd   AR=arm-poky-linux-gnueabi-ar  O=/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work-shared/raspberrypi3/kernel-build-artifacts KBUILD_EXTRA_SYMBOLS=
make -C /home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work-shared/raspberrypi3/kernel-build-artifacts SUBDIRS=/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work/raspberrypi3-poky-linux-gnueabi/ax88772/1.0-r0 modules
make[1]: warning: jobserver unavailable: using -j1.  Add '+' to parent make rule.
make[1]: Entering directory '/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work-shared/raspberrypi3/kernel-build-artifacts'
  GEN     Makefile
  YACC    scripts/kconfig/parser.tab.[ch]
/bin/sh: 1: bison: not found
make[4]: *** [scripts/Makefile.host:17: scripts/kconfig/parser.tab.h] Error 127
make[3]: *** [/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work-shared/raspberrypi3/kernel-source/Makefile:590: syncconfig] Error 2
make[2]: *** [/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work-shared/raspberrypi3/kernel-source/Makefile:696: include/config/auto.conf.cmd] Error 2
make[1]: *** [/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work-shared/raspberrypi3/kernel-source/Makefile:179: sub-make] Error 2
make[1]: Leaving directory '/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work-shared/raspberrypi3/kernel-build-artifacts'
make: *** [Makefile:19: default] Error 2
ERROR: oe_runmake failed
WARNING: exit code 1 from a shell command.


Here is my bb file for the same-

SUMMARY = "WAN IC asix kernel module"
LICENSE = "GPLv2"
LIC_FILES_CHKSUM = "file://LICENSE;md5=014e508ee78ef83e5007b9cb3834f0e9"

DEPENDS = "virtual/kernel bc bison"

inherit module

PR = "r0"
PV = "1.0"

SRC_URI = "file://Makefile \
          file://asix.c \
          file://asix.h \
          file://axusbnet.c \
          file://axusbnet.h \
          file://command.h \
          file://debug.txt \
          file://eeprom_data.tar.bz2 \
          file://ioctl.c \
          file://ioctl.h \
          file://ioctl_readme \
          file://readme \
          file://readme \
          file://LICENSE \
"

S = "${WORKDIR}"

export TARGET_SYS
EXTRA_OEMAKE += "KSRC=${STAGING_KERNEL_BUILDDIR}"

do_compile_append() {
        ${CC} ioctl.c -o ioctl
}

do_install_prepend() {
        export DESTDIR="${D}"
}




# The inherit of module.bbclass will automatically name module packages with
# "kernel-module-" prefix as required by the oe-core build environment.



Same kernel module with poky zeus and rpi kernel 4.19 got compiled successfully, but here I'm getting issue with poky dunfell with Rpi kernel 5.4

Please help me resolve this issue.

Thanks.



/bin/sh: 1: bison: not found while compiling own kernel module with poky-dunfell #bitbake

@prashant2314
 

hello team,
I'm trying to build my own kernel module with yocto for raspberry-pi kernel, but it's giving me error that "bison not found", as-

DEBUG: Executing shell function do_compile
NOTE: make -j 12 KERNEL_SRC=/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work-shared/raspberrypi3/kernel-source KSRC=/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work-shared/raspberrypi3/kernel-build-artifacts KERNEL_PATH=/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work-shared/raspberrypi3/kernel-source KERNEL_VERSION=5.4.72-v7 CC=arm-poky-linux-gnueabi-gcc  -mno-thumb-interwork -marm -fuse-ld=bfd -fmacro-prefix-map=/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work/raspberrypi3-poky-linux-gnueabi/ax88772/1.0-r0=/usr/src/debug/ax88772/1.0-r0                      -fdebug-prefix-map=/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work/raspberrypi3-poky-linux-gnueabi/ax88772/1.0-r0=/usr/src/debug/ax88772/1.0-r0                      -fdebug-prefix-map=/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work/raspberrypi3-poky-linux-gnueabi/ax88772/1.0-r0/recipe-sysroot=                      -fdebug-prefix-map=/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work/raspberrypi3-poky-linux-gnueabi/ax88772/1.0-r0/recipe-sysroot-native=  -fdebug-prefix-map=/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work-shared/raspberrypi3/kernel-source=/usr/src/kernel LD=arm-poky-linux-gnueabi-ld.bfd   AR=arm-poky-linux-gnueabi-ar  O=/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work-shared/raspberrypi3/kernel-build-artifacts KBUILD_EXTRA_SYMBOLS=
make -C /home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work-shared/raspberrypi3/kernel-build-artifacts SUBDIRS=/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work/raspberrypi3-poky-linux-gnueabi/ax88772/1.0-r0 modules
make[1]: warning: jobserver unavailable: using -j1.  Add '+' to parent make rule.
make[1]: Entering directory '/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work-shared/raspberrypi3/kernel-build-artifacts'
  GEN     Makefile
  YACC    scripts/kconfig/parser.tab.[ch]
/bin/sh: 1: bison: not found
make[4]: *** [scripts/Makefile.host:17: scripts/kconfig/parser.tab.h] Error 127
make[3]: *** [/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work-shared/raspberrypi3/kernel-source/Makefile:590: syncconfig] Error 2
make[2]: *** [/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work-shared/raspberrypi3/kernel-source/Makefile:696: include/config/auto.conf.cmd] Error 2
make[1]: *** [/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work-shared/raspberrypi3/kernel-source/Makefile:179: sub-make] Error 2
make[1]: Leaving directory '/home/dialtronics/DIALT_WORK/RPI_YOCTO/PS_RPI_BUILD/FXS_BSP/workspace/FXS/tmp/work-shared/raspberrypi3/kernel-build-artifacts'
make: *** [Makefile:19: default] Error 2
ERROR: oe_runmake failed
WARNING: exit code 1 from a shell command.


Here is my bb file for the same-

SUMMARY = "WAN IC asix kernel module"
LICENSE = "GPLv2"
LIC_FILES_CHKSUM = "file://LICENSE;md5=014e508ee78ef83e5007b9cb3834f0e9"

DEPENDS = "virtual/kernel bc bison"

inherit module

PR = "r0"
PV = "1.0"

SRC_URI = "file://Makefile \
          file://asix.c \
          file://asix.h \
          file://axusbnet.c \
          file://axusbnet.h \
          file://command.h \
          file://debug.txt \
          file://eeprom_data.tar.bz2 \
          file://ioctl.c \
          file://ioctl.h \
          file://ioctl_readme \
          file://readme \
          file://readme \
          file://LICENSE \
"

S = "${WORKDIR}"

export TARGET_SYS
EXTRA_OEMAKE += "KSRC=${STAGING_KERNEL_BUILDDIR}"

do_compile_append() {
        ${CC} ioctl.c -o ioctl
}

do_install_prepend() {
        export DESTDIR="${D}"
}




# The inherit of module.bbclass will automatically name module packages with
# "kernel-module-" prefix as required by the oe-core build environment.



Same kernel module with poky zeus and rpi kernel 4.19 got compiled successfully, but here I'm getting issue with poky dunfell with Rpi kernel 5.4

Please help me resolve this issue.

Thanks.


[meta-cgl-common][PATCH] pacemaker: use main branch

Yu, Mingli
 

From: Mingli Yu <mingli.yu@...>

Use the main branch to fix do_fetch error.

Signed-off-by: Mingli Yu <mingli.yu@...>
---
meta-cgl-common/recipes-cgl/pacemaker/pacemaker_2.0.5.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_2.0.5.bb b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_2.0.5.bb
index f9a0bf7..3bff2ba 100644
--- a/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_2.0.5.bb
+++ b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_2.0.5.bb
@@ -13,7 +13,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=000212f361a81b100d9d0f0435040663"

DEPENDS = "corosync libxslt libxml2 gnutls resource-agents libqb python3-native"

-SRC_URI = "git://github.com/ClusterLabs/${BPN}.git;branch=master;protocol=https \
+SRC_URI = "git://github.com/ClusterLabs/${BPN}.git;branch=main;protocol=https \
file://0001-Fix-python3-usage.patch \
file://0001-pacemaker-set-OCF_ROOT_DIR-to-libdir-ocf.patch \
file://volatiles \
--
2.17.1


Re: building image for Realtek RTS3916N mips SoC using vendor provided prebuilt external uClibc toolchain

Khem Raj
 

On 12/28/21 2:53 PM, davis roman wrote:
Hi all,
I'm working on a project utilizing a Realtek RTS3916N mips SoC and as
part of Realtek's bsp offering, they provide their own fork of
buildroot packaged with their prebuilt binary toolchain.
I would much rather use yocto instead however Realtek made it clear
that no yocto support is available from their end and they have no
plans to provide it in the future.
In theory, I have Realtek's u-boot and kernel source so it should be
possible to build an image so long as poky is instructed to use an
external toolchain. This is where I hit my first road block because
Realtek only supports uClibc and I know the yocto community moved way
from uClibc, in favor of musl, since the Morty release. As a result, I
decided to use Krogoth-15.0.0 (knowing it's EOL) only because it
supports uClibc.
Now that I had picked a specific version of poky, I continued forward
with the EXTERNAL_TOOLCHAIN feature. The documentation references the
meta-sourcery layer as the typical use case. Using a sourcery
toolchain tarball ( 2014.05) I was able to build qemuarm/glibc
therefore as far as I can tell the EXTERNAL_TOOLCHAIN feature works as
documented.
Unfortunately, the issue I have now arises when I use the Realtek
toolchain. meta-sourcery informs me that building against uClibc is
not allowed as it has been blacklisted. Only glibc appears to be
supported.
I have looked around to see what other projects are similar and the
closest I can find is the creator CI20 however due to the Realtek
toolchain being based on uClibc, I haven't been able to find anything
suitable for my usecase.
I would greatly appreciate any suggestions regarding how to proceed
forward with yocto integration, using a mips uClibc based toolchain.
We have dropped uclibc support long time ago so any effort to support uClibc based system will be a bit of work and we have also dropped stale patches from metadata so even if you are able to get external toolchain bolted in, you will unfurl next set of problems for yourself So I don't have a better answer for you here, other than drop the idea of using uclibc if you want to use modern yocto baseline. We did support it long time ago so if you like you can use thise EOLed releases but there wont be much support for it here on community mailing lists.

Is there any other course of action that I can try?
Since you have bootloader and kernel available to you, it might be less work to put together a BSP layer and machine definition for this SOC easily and it could be forward looking but there could be some portability issues w.r.t. toolchain etc. which are manageable
here you will use internal mips toolchain to build your system and you can use musl instead of uclibc to build the system or glibc is other supported option.

Thank you,
Davis


building image for Realtek RTS3916N mips SoC using vendor provided prebuilt external uClibc toolchain

davis roman <davis.roman84@...>
 

Hi all,

I'm working on a project utilizing a Realtek RTS3916N mips SoC and as
part of Realtek's bsp offering, they provide their own fork of
buildroot packaged with their prebuilt binary toolchain.
I would much rather use yocto instead however Realtek made it clear
that no yocto support is available from their end and they have no
plans to provide it in the future.

In theory, I have Realtek's u-boot and kernel source so it should be
possible to build an image so long as poky is instructed to use an
external toolchain. This is where I hit my first road block because
Realtek only supports uClibc and I know the yocto community moved way
from uClibc, in favor of musl, since the Morty release. As a result, I
decided to use Krogoth-15.0.0 (knowing it's EOL) only because it
supports uClibc.

Now that I had picked a specific version of poky, I continued forward
with the EXTERNAL_TOOLCHAIN feature. The documentation references the
meta-sourcery layer as the typical use case. Using a sourcery
toolchain tarball ( 2014.05) I was able to build qemuarm/glibc
therefore as far as I can tell the EXTERNAL_TOOLCHAIN feature works as
documented.

Unfortunately, the issue I have now arises when I use the Realtek
toolchain. meta-sourcery informs me that building against uClibc is
not allowed as it has been blacklisted. Only glibc appears to be
supported.

I have looked around to see what other projects are similar and the
closest I can find is the creator CI20 however due to the Realtek
toolchain being based on uClibc, I haven't been able to find anything
suitable for my usecase.

I would greatly appreciate any suggestions regarding how to proceed
forward with yocto integration, using a mips uClibc based toolchain.

Is there any other course of action that I can try?

Thank you,

Davis


[meta-security][PATCH 2/2] meta-tpm: drop strongswan bbappends

Armin Kuster
 

Signed-off-by: Armin Kuster <akuster808@...>
---
...rmi-Only-build-if-libcharon-is-built.patch | 38 -------------------
.../strongswan/strongswan-tpm.inc | 12 ------
.../strongswan/strongswan_5.%.bbappend | 1 -
3 files changed, 51 deletions(-)
delete mode 100644 meta-tpm/dynamic-layers/meta-networking/recipes-support/strongswan/files/0001-xfrmi-Only-build-if-libcharon-is-built.patch
delete mode 100644 meta-tpm/dynamic-layers/meta-networking/recipes-support/strongswan/strongswan-tpm.inc
delete mode 100644 meta-tpm/dynamic-layers/meta-networking/recipes-support/strongswan/strongswan_5.%.bbappend

diff --git a/meta-tpm/dynamic-layers/meta-networking/recipes-support/strongswan/files/0001-xfrmi-Only-build-if-libcharon-is-built.patch b/meta-tpm/dynamic-layers/meta-networking/recipes-support/strongswan/files/0001-xfrmi-Only-build-if-libcharon-is-built.patch
deleted file mode 100644
index 8250282..0000000
--- a/meta-tpm/dynamic-layers/meta-networking/recipes-support/strongswan/files/0001-xfrmi-Only-build-if-libcharon-is-built.patch
+++ /dev/null
@@ -1,38 +0,0 @@
-From db772305c6baa01f6c6750be74733e4bfc1d6106 Mon Sep 17 00:00:00 2001
-From: Tobias Brunner <tobias@...>
-Date: Tue, 14 Apr 2020 10:44:19 +0200
-Subject: [PATCH] xfrmi: Only build if libcharon is built
-
-The kernel-netlink plugin is only built if libcharon is.
-
-Closes strongswan/strongswan#167.
-
-Upstream-Status: Backport
-Signed-off-by: Armin Kuster <akuster808@...>
-
----
- src/Makefile.am | 7 +++----
- 1 file changed, 3 insertions(+), 4 deletions(-)
-
-Index: strongswan-5.8.4/src/Makefile.am
-===================================================================
---- strongswan-5.8.4.orig/src/Makefile.am
-+++ strongswan-5.8.4/src/Makefile.am
-@@ -42,6 +42,9 @@ endif
-
- if USE_LIBCHARON
- SUBDIRS += libcharon
-+if USE_KERNEL_NETLINK
-+ SUBDIRS += xfrmi
-+endif
- endif
-
- if USE_FILE_CONFIG
-@@ -143,7 +146,3 @@ endif
- if USE_TPM
- SUBDIRS += tpm_extendpcr
- endif
--
--if USE_KERNEL_NETLINK
-- SUBDIRS += xfrmi
--endif
diff --git a/meta-tpm/dynamic-layers/meta-networking/recipes-support/strongswan/strongswan-tpm.inc b/meta-tpm/dynamic-layers/meta-networking/recipes-support/strongswan/strongswan-tpm.inc
deleted file mode 100644
index 497474f..0000000
--- a/meta-tpm/dynamic-layers/meta-networking/recipes-support/strongswan/strongswan-tpm.inc
+++ /dev/null
@@ -1,12 +0,0 @@
-FILESEXTRAPATHS:prepend := "${THISDIR}/files:"
-
-DEPENDS = "libtspi"
-
-SRC_URI:append = " file://0001-xfrmi-Only-build-if-libcharon-is-built.patch"
-
-PACKAGECONFIG += "aikgen tpm"
-
-PACKAGECONFIG[tpm] = "--enable-tpm,--disable-tpm,,"
-PACKAGECONFIG[aikgen] = "--enable-aikgen,--disable-aikgen,,"
-
-EXTRA_OECONF += "--with-linux-headers=${STAGING_KERNEL_DIR}"
diff --git a/meta-tpm/dynamic-layers/meta-networking/recipes-support/strongswan/strongswan_5.%.bbappend b/meta-tpm/dynamic-layers/meta-networking/recipes-support/strongswan/strongswan_5.%.bbappend
deleted file mode 100644
index 34757bb..0000000
--- a/meta-tpm/dynamic-layers/meta-networking/recipes-support/strongswan/strongswan_5.%.bbappend
+++ /dev/null
@@ -1 +0,0 @@
-require ${@bb.utils.contains('DISTRO_FEATURES', 'tpm', 'strongswan-tpm.inc', '', d)}
--
2.25.1


[meta-security][PATCH 1/2] meta-integrity: drop strongswan bbappends

Armin Kuster
 

Signed-off-by: Armin Kuster <akuster808@...>
---
.../strongswan/strongswan-ima.inc | 61 -------------------
.../strongswan/strongswan_5.%.bbappend | 1 -
2 files changed, 62 deletions(-)
delete mode 100644 meta-integrity/dynamic-layers/meta-networking/recipes-support/strongswan/strongswan-ima.inc
delete mode 100644 meta-integrity/dynamic-layers/meta-networking/recipes-support/strongswan/strongswan_5.%.bbappend

diff --git a/meta-integrity/dynamic-layers/meta-networking/recipes-support/strongswan/strongswan-ima.inc b/meta-integrity/dynamic-layers/meta-networking/recipes-support/strongswan/strongswan-ima.inc
deleted file mode 100644
index 807075c..0000000
--- a/meta-integrity/dynamic-layers/meta-networking/recipes-support/strongswan/strongswan-ima.inc
+++ /dev/null
@@ -1,61 +0,0 @@
-FILESEXTRAPATHS:prepend := "${THISDIR}/files:"
-
-DEPENDS = "libtspi"
-
-SRC_URI:append = " file://0001-xfrmi-Only-build-if-libcharon-is-built.patch"
-
-PACKAGECONFIG += " \
- aikgen \
- tpm \
-"
-
-PACKAGECONFIG[tpm] = "--enable-tpm,--disable-tpm,,"
-PACKAGECONFIG[aikgen] = "--enable-aikgen,--disable-aikgen,,"
-
-PACKAGECONFIG_ima += "\
- imc-test \
- imv-test \
- imc-scanner \
- imv-scanner \
- imc-os \
- imv-os \
- imc-attestation \
- imv-attestation \
- tnc-ifmap \
- tnc-imc \
- tnc-imv \
- tnc-pdp \
- tnccs-11 \
- tnccs-20 \
- tnccs-dynamic \
- "
-
-EXTRA_OECONF += "--with-linux-headers=${STAGING_KERNEL_DIR}"
-
-PACKAGECONFIG[imc-test] = "--enable-imc-test,--disable-imc-test,,"
-PACKAGECONFIG[imc-scanner] = "--enable-imc-scanner,--disable-imc-scanner,,"
-PACKAGECONFIG[imc-os] = "--enable-imc-os,--disable-imc-os,,"
-PACKAGECONFIG[imc-attestation] = "--enable-imc-attestation,--disable-imc-attestation,,"
-PACKAGECONFIG[imc-swima] = "--enable-imc-swima, --disable-imc-swima,,"
-PACKAGECONFIG[imc-hcd] = "--enable-imc-hcd, --disable-imc-hcd,,"
-PACKAGECONFIG[tnc-imc] = "--enable-tnc-imc,--disable-tnc-imc,,"
-
-PACKAGECONFIG[imv-test] = "--enable-imv-test,--disable-imv-test,,"
-PACKAGECONFIG[imv-scanner] = "--enable-imv-scanner,--disable-imv-scanner,,"
-PACKAGECONFIG[imv-os] = "--enable-imv-os,--disable-imv-os,,"
-PACKAGECONFIG[imv-attestation] = "--enable-imv-attestation,--disable-imv-attestation,,"
-PACKAGECONFIG[imv-swima] = "--enable-imv-swima, --disable-imv-swima,,"
-PACKAGECONFIG[imv-hcd] = "--enable-imv-hcd, --disable-imv-hcd,,"
-PACKAGECONFIG[tnc-imv] = "--enable-tnc-imv,--disable-tnc-imv,,"
-
-PACKAGECONFIG[tnc-ifmap] = "--enable-tnc-ifmap,--disable-tnc-ifmap,libxml2,"
-PACKAGECONFIG[tnc-pdp] = "--enable-tnc-pdp,--disable-tnc-pdp,,"
-
-PACKAGECONFIG[tnccs-11] = "--enable-tnccs-11,--disable-tnccs-11,libxml2,"
-PACKAGECONFIG[tnccs-20] = "--enable-tnccs-20,--disable-tnccs-20,,"
-PACKAGECONFIG[tnccs-dynamic] = "--enable-tnccs-dynamic,--disable-tnccs-dynamic,,"
-
-#FILES_${PN} += "${libdir}/ipsec/imcvs/*.so ${datadir}/regid.2004-03.org.strongswan"
-#FILES_${PN}-dbg += "${libdir}/ipsec/imcvs/.debug"
-#FILES_${PN}-dev += "${libdir}/ipsec/imcvs/*.la"
-#FILES_${PN}-staticdev += "${libdir}/ipsec/imcvs/*.a"
diff --git a/meta-integrity/dynamic-layers/meta-networking/recipes-support/strongswan/strongswan_5.%.bbappend b/meta-integrity/dynamic-layers/meta-networking/recipes-support/strongswan/strongswan_5.%.bbappend
deleted file mode 100644
index 4669fd2..0000000
--- a/meta-integrity/dynamic-layers/meta-networking/recipes-support/strongswan/strongswan_5.%.bbappend
+++ /dev/null
@@ -1 +0,0 @@
-require ${@bb.utils.contains('DISTRO_FEATURES', 'imp', 'strongswan-ima.inc', '', d)}
--
2.25.1


Re: unparsed line #yocto

Kevin Kettinger
 

Thank you, after updating from 1.46.8 to 1.46.11 in the bitake repository (https://github.com/openembedded/bitbake) it is now parsing the recipes just fine.


Re: unparsed line #yocto

Martin Jansa
 

Upgrade bitbake to support new overrides syntax, see https://github.com/ros/meta-ros/pull/902


On Tue, Dec 28, 2021 at 7:12 PM Kevin Kettinger <kkettinger@...> wrote:
Hello,

after including the meta-qt5 and meta-boot2qt layer from https://code.qt.io/cgit/yocto, and adding them to my bblayers.conf, bitbake breaks directly while parsing the recipes:
---------------------------------------------
ERROR: ParseError at /home/yocto/projects/faseroptik-dunfell/build/../layers/meta-qt5/classes/cmake_qt5.bbclass:4: unparsed line: 'DEPENDS:prepend = "${QTBASEDEPENDS} "'                                                                                                                                    | ETA:  --:--:--

Summary: There was 1 ERROR message shown, returning a non-zero exit code.
---------------------------------------------

If i restart bitbake, the offending file changes now and then, but just for completion, here is the file:
---------------------------------------------
inherit cmake
inherit qmake5_paths

DEPENDS:prepend = "${QTBASEDEPENDS} "
QTBASEDEPENDS = "qtbase qtbase-native"
QTBASEDEPENDS:class-native = "qtbase-native"
QTBASEDEPENDS:class-nativesdk = "nativesdk-qtbase qtbase-native"

EXTRA_OECMAKE:prepend = " \
    -DOE_QMAKE_PATH_PREFIX=${OE_QMAKE_PATH_PREFIX} \
    -DOE_QMAKE_PATH_HEADERS=${OE_QMAKE_PATH_HEADERS} \
    -DOE_QMAKE_PATH_LIBS=${OE_QMAKE_PATH_LIBS} \
    -DOE_QMAKE_PATH_ARCHDATA=${OE_QMAKE_PATH_ARCHDATA} \
    -DOE_QMAKE_PATH_DATA=${OE_QMAKE_PATH_DATA} \
    -DOE_QMAKE_PATH_BINS=${OE_QMAKE_PATH_BINS} \
    -DOE_QMAKE_PATH_LIBEXECS=${OE_QMAKE_PATH_LIBEXECS} \
    -DOE_QMAKE_PATH_PLUGINS=${OE_QMAKE_PATH_PLUGINS} \
    -DOE_QMAKE_PATH_QML=${OE_QMAKE_PATH_QML} \
    -DOE_QMAKE_PATH_TRANSLATIONS=${OE_QMAKE_PATH_TRANSLATIONS} \
    -DOE_QMAKE_PATH_DOCS=${OE_QMAKE_PATH_DOCS} \
    -DOE_QMAKE_PATH_SETTINGS=${OE_QMAKE_PATH_SETTINGS} \
    -DOE_QMAKE_PATH_EXAMPLES=${OE_QMAKE_PATH_EXAMPLES} \
    -DOE_QMAKE_PATH_TESTS=${OE_QMAKE_PATH_TESTS} \
    -DOE_QMAKE_PATH_HOST_PREFIX=${OE_QMAKE_PATH_HOST_PREFIX} \
    -DOE_QMAKE_PATH_HOST_BINS=${OE_QMAKE_PATH_HOST_BINS} \
    -DOE_QMAKE_PATH_HOST_DATA=${OE_QMAKE_PATH_HOST_DATA} \
    -DOE_QMAKE_PATH_HOST_LIBS=${OE_QMAKE_PATH_HOST_LIBS} \
    -DOE_QMAKE_PATH_EXTERNAL_HOST_BINS=${OE_QMAKE_PATH_EXTERNAL_HOST_BINS} \
    -DOE_QMAKE_PATH_QT_HEADERS=${OE_QMAKE_PATH_QT_HEADERS} \
    -DOE_QMAKE_PATH_QT_ARCHDATA=${OE_QMAKE_PATH_QT_ARCHDATA} \
    -DOE_QMAKE_PATH_QT_DATA=${OE_QMAKE_PATH_QT_DATA} \
    -DOE_QMAKE_PATH_QT_BINS=${OE_QMAKE_PATH_QT_BINS} \
    -DOE_QMAKE_PATH_QT_TRANSLATIONS=${OE_QMAKE_PATH_QT_TRANSLATIONS} \
    -DOE_QMAKE_PATH_QT_DOCS=${OE_QMAKE_PATH_QT_DOCS} \
    -DOE_QMAKE_PATH_QT_SETTINGS=${OE_QMAKE_PATH_QT_SETTINGS} \
    -DOE_QMAKE_PATH_QT_EXAMPLES=${OE_QMAKE_PATH_QT_EXAMPLES} \
    -DOE_QMAKE_PATH_QT_TESTS=${OE_QMAKE_PATH_QT_TESTS} \
"
---------------------------------------------

The exact same layer with the exact same commit & files is working fine on the original boot2qt environment, but not on my environment.

My bblayers.conf looks like this:
---------------------------------------------
LCONF_VERSION = "7"

BBPATH = "${TOPDIR}"
BBFILES ?= ""

BBLAYERS ?= " \
  ${TOPDIR}/../layers/meta-toradex-nxp \
  ${TOPDIR}/../layers/meta-freescale \
  ${TOPDIR}/../layers/meta-freescale-3rdparty \
  ${TOPDIR}/../layers/meta-toradex-tegra \
  ${TOPDIR}/../layers/meta-toradex-bsp-common \
  ${TOPDIR}/../layers/meta-openembedded/meta-oe \
  ${TOPDIR}/../layers/meta-openembedded/meta-filesystems \
  ${TOPDIR}/../layers/meta-openembedded/meta-gnome \
  ${TOPDIR}/../layers/meta-openembedded/meta-xfce \
  ${TOPDIR}/../layers/meta-openembedded/meta-initramfs \
  ${TOPDIR}/../layers/meta-openembedded/meta-networking \
  ${TOPDIR}/../layers/meta-openembedded/meta-multimedia \
  ${TOPDIR}/../layers/meta-openembedded/meta-python \
  ${TOPDIR}/../layers/meta-freescale-distro \
  ${TOPDIR}/../layers/meta-toradex-demos \
  ${TOPDIR}/../layers/meta-boot2qt/meta-boot2qt \
  ${TOPDIR}/../layers/meta-boot2qt/meta-boot2qt-distro \
  ${TOPDIR}/../layers/meta-qt5 \
  ${TOPDIR}/../layers/meta-toradex-distro \
  ${TOPDIR}/../layers/meta-yocto/meta-poky \
  ${TOPDIR}/../layers/openembedded-core/meta \
  ${TOPDIR}/../layers/meta-mender/meta-mender-core \
  ${TOPDIR}/../layers/meta-mender-community/meta-mender-toradex-nxp \
  ${TOPDIR}/../layers/meta-mender/meta-mender-demo \
  "
---------------------------------------------

On the working boot2qt environment poky 3.1.11 is used, i'm using poky 3.1.8.

Is there anything i can do to track this issue down? bitbake -v doesn't report more infos.

I appreciate any help here, thank you.

Best regards,
Kevin



unparsed line #yocto

Kevin Kettinger
 

Hello,

after including the meta-qt5 and meta-boot2qt layer from https://code.qt.io/cgit/yocto, and adding them to my bblayers.conf, bitbake breaks directly while parsing the recipes:
---------------------------------------------
ERROR: ParseError at /home/yocto/projects/faseroptik-dunfell/build/../layers/meta-qt5/classes/cmake_qt5.bbclass:4: unparsed line: 'DEPENDS:prepend = "${QTBASEDEPENDS} "'                                                                                                                                    | ETA:  --:--:--

Summary: There was 1 ERROR message shown, returning a non-zero exit code.
---------------------------------------------

If i restart bitbake, the offending file changes now and then, but just for completion, here is the file:
---------------------------------------------
inherit cmake
inherit qmake5_paths

DEPENDS:prepend = "${QTBASEDEPENDS} "
QTBASEDEPENDS = "qtbase qtbase-native"
QTBASEDEPENDS:class-native = "qtbase-native"
QTBASEDEPENDS:class-nativesdk = "nativesdk-qtbase qtbase-native"

EXTRA_OECMAKE:prepend = " \
    -DOE_QMAKE_PATH_PREFIX=${OE_QMAKE_PATH_PREFIX} \
    -DOE_QMAKE_PATH_HEADERS=${OE_QMAKE_PATH_HEADERS} \
    -DOE_QMAKE_PATH_LIBS=${OE_QMAKE_PATH_LIBS} \
    -DOE_QMAKE_PATH_ARCHDATA=${OE_QMAKE_PATH_ARCHDATA} \
    -DOE_QMAKE_PATH_DATA=${OE_QMAKE_PATH_DATA} \
    -DOE_QMAKE_PATH_BINS=${OE_QMAKE_PATH_BINS} \
    -DOE_QMAKE_PATH_LIBEXECS=${OE_QMAKE_PATH_LIBEXECS} \
    -DOE_QMAKE_PATH_PLUGINS=${OE_QMAKE_PATH_PLUGINS} \
    -DOE_QMAKE_PATH_QML=${OE_QMAKE_PATH_QML} \
    -DOE_QMAKE_PATH_TRANSLATIONS=${OE_QMAKE_PATH_TRANSLATIONS} \
    -DOE_QMAKE_PATH_DOCS=${OE_QMAKE_PATH_DOCS} \
    -DOE_QMAKE_PATH_SETTINGS=${OE_QMAKE_PATH_SETTINGS} \
    -DOE_QMAKE_PATH_EXAMPLES=${OE_QMAKE_PATH_EXAMPLES} \
    -DOE_QMAKE_PATH_TESTS=${OE_QMAKE_PATH_TESTS} \
    -DOE_QMAKE_PATH_HOST_PREFIX=${OE_QMAKE_PATH_HOST_PREFIX} \
    -DOE_QMAKE_PATH_HOST_BINS=${OE_QMAKE_PATH_HOST_BINS} \
    -DOE_QMAKE_PATH_HOST_DATA=${OE_QMAKE_PATH_HOST_DATA} \
    -DOE_QMAKE_PATH_HOST_LIBS=${OE_QMAKE_PATH_HOST_LIBS} \
    -DOE_QMAKE_PATH_EXTERNAL_HOST_BINS=${OE_QMAKE_PATH_EXTERNAL_HOST_BINS} \
    -DOE_QMAKE_PATH_QT_HEADERS=${OE_QMAKE_PATH_QT_HEADERS} \
    -DOE_QMAKE_PATH_QT_ARCHDATA=${OE_QMAKE_PATH_QT_ARCHDATA} \
    -DOE_QMAKE_PATH_QT_DATA=${OE_QMAKE_PATH_QT_DATA} \
    -DOE_QMAKE_PATH_QT_BINS=${OE_QMAKE_PATH_QT_BINS} \
    -DOE_QMAKE_PATH_QT_TRANSLATIONS=${OE_QMAKE_PATH_QT_TRANSLATIONS} \
    -DOE_QMAKE_PATH_QT_DOCS=${OE_QMAKE_PATH_QT_DOCS} \
    -DOE_QMAKE_PATH_QT_SETTINGS=${OE_QMAKE_PATH_QT_SETTINGS} \
    -DOE_QMAKE_PATH_QT_EXAMPLES=${OE_QMAKE_PATH_QT_EXAMPLES} \
    -DOE_QMAKE_PATH_QT_TESTS=${OE_QMAKE_PATH_QT_TESTS} \
"
---------------------------------------------

The exact same layer with the exact same commit & files is working fine on the original boot2qt environment, but not on my environment.

My bblayers.conf looks like this:
---------------------------------------------
LCONF_VERSION = "7"

BBPATH = "${TOPDIR}"
BBFILES ?= ""

BBLAYERS ?= " \
  ${TOPDIR}/../layers/meta-toradex-nxp \
  ${TOPDIR}/../layers/meta-freescale \
  ${TOPDIR}/../layers/meta-freescale-3rdparty \
  ${TOPDIR}/../layers/meta-toradex-tegra \
  ${TOPDIR}/../layers/meta-toradex-bsp-common \
  ${TOPDIR}/../layers/meta-openembedded/meta-oe \
  ${TOPDIR}/../layers/meta-openembedded/meta-filesystems \
  ${TOPDIR}/../layers/meta-openembedded/meta-gnome \
  ${TOPDIR}/../layers/meta-openembedded/meta-xfce \
  ${TOPDIR}/../layers/meta-openembedded/meta-initramfs \
  ${TOPDIR}/../layers/meta-openembedded/meta-networking \
  ${TOPDIR}/../layers/meta-openembedded/meta-multimedia \
  ${TOPDIR}/../layers/meta-openembedded/meta-python \
  ${TOPDIR}/../layers/meta-freescale-distro \
  ${TOPDIR}/../layers/meta-toradex-demos \
  ${TOPDIR}/../layers/meta-boot2qt/meta-boot2qt \
  ${TOPDIR}/../layers/meta-boot2qt/meta-boot2qt-distro \
  ${TOPDIR}/../layers/meta-qt5 \
  ${TOPDIR}/../layers/meta-toradex-distro \
  ${TOPDIR}/../layers/meta-yocto/meta-poky \
  ${TOPDIR}/../layers/openembedded-core/meta \
  ${TOPDIR}/../layers/meta-mender/meta-mender-core \
  ${TOPDIR}/../layers/meta-mender-community/meta-mender-toradex-nxp \
  ${TOPDIR}/../layers/meta-mender/meta-mender-demo \
  "
---------------------------------------------

On the working boot2qt environment poky 3.1.11 is used, i'm using poky 3.1.8.

Is there anything i can do to track this issue down? bitbake -v doesn't report more infos.

I appreciate any help here, thank you.

Best regards,
Kevin


[ANNOUNCEMENT] Yocto Project 3.1.13 (dunfell-23.0.13) is Released

Lee Chee Yang
 

Hello,

 

We are pleased to announce the Yocto Project 3.1.13 (dunfell-23.0.13) Release is now available for download.

http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.13/poky-dunfell-23.0.13.tar.bz2

https://mirrors.kernel.org/yocto/yocto/yocto-3.1.13/poky-dunfell-23.0.13.tar.bz2

 

A gpg signed version of these release notes is available at:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.13/RELEASENOTES

 

Full Test Report:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.13/testreport.txt

 

Thank you for everyone's contributions to this release.

 

Chee Yang Lee <chee.yang.lee@...>

Yocto Project Build and Release

 

 

- --------------------------

yocto-3.1.13 Release Notes

- --------------------------

 

 

- --------------------------

Repositories/Downloads

- --------------------------

 

Repository Name: poky

Repository Location: https://git.yoctoproject.org/git/poky

Branch: dunfell

Tag: yocto-3.1.13

Git Revision: 795339092f87672e4f68e4d3bc4cfd0e252d1831

Release Artefact: poky-dunfell-23.0.13

sha: 9408163f281fb28e9fc5a7db6955e5c932f286aacb40f5ad7285066154cff76b

Download Locations:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.13/poky-dunfell-23.0.13.tar.bz2

http://mirrors.kernel.org/yocto/yocto/yocto-3.1.13/poky-dunfell-23.0.13.tar.bz2

 

Repository Name: openembedded-core

Repository Location: https://git.openembedded.org/openembedded-core

Branch: dunfell

Tag: yocto-3.1.13

Git Revision: 90a07178ea26be453d101c2e8b33d3a0f437635d

Release Artefact: oecore-dunfell-23.0.13

sha: 20f41dc45af76e140a6b49b6d71cc0ef61ea5fb5c6df6a210b52944c0d70c2f5

Download Locations:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.13/oecore-dunfell-23.0.13.tar.bz2

http://mirrors.kernel.org/yocto/yocto/yocto-3.1.13/oecore-dunfell-23.0.13.tar.bz2

 

Repository Name: meta-mingw

Repository Location: https://git.yoctoproject.org/git/meta-mingw

Branch: dunfell

Tag: yocto-3.1.13

Git Revision: 524de686205b5d6736661d4532f5f98fee8589b7

Release Artefact: meta-mingw-dunfell-23.0.13

sha: 2688d3cfadb7cdc7025d7e6f4b9300f4e29611d97b8329b1b033a251e7d354a2

Download Locations:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.13/meta-mingw-dunfell-23.0.13.tar.bz2

http://mirrors.kernel.org/yocto/yocto/yocto-3.1.13/meta-mingw-dunfell-23.0.13.tar.bz2

 

Repository Name: meta-gplv2

Repository Location: https://git.yoctoproject.org/git/meta-gplv2

Branch: dunfell

Tag: yocto-3.1.13

Git Revision: 60b251c25ba87e946a0ca4cdc8d17b1cb09292ac

Release Artefact: meta-gplv2-dunfell-23.0.13

sha: f937e7e051b19285e7d59033d7cb08c641c55860cd64d2c6d7b57b26338b5801

Download Locations:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.13/meta-gplv2-dunfell-23.0.13.tar.bz2

http://mirrors.kernel.org/yocto/yocto/yocto-3.1.13/meta-gplv2-dunfell-23.0.13.tar.bz2

 

Repository Name: bitbake

Repository Location: https://git.openembedded.org/bitbake

Branch: dunfell

Tag: yocto-3.1.13

Git Revision: f18b65d0b9a6b983d53bde491e1bf2ca56949444

Release Artefact: bitbake-dunfell-23.0.13

sha: 570b58952ddcf7262b8ff13bd06c8cfcdadecf80af2d9bc3868446ee07693676

Download Locations:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.13/bitbake-dunfell-23.0.13.tar.bz2

http://mirrors.kernel.org/yocto/yocto/yocto-3.1.13/bitbake-dunfell-23.0.13.tar.bz2

 

Repository Name: yocto-docs

Repository Location: https://git.yoctoproject.org/git/yocto-docs

Branch: dunfell

Tag: yocto-3.1.13

Git Revision: c00596374d2c6ddd1b81e536972aa8fc807e60b9

 

 

- ---------------

Known Issues

- ---------------

Bug 14669 - [QA 3.1.13 RC1] failure in ptest :gstreamer1.0.gstreamer-1.0/pipelines_seek.test

 

 

- ---------------

Security Fixes

- ---------------

libgcrypt: solve CVE-2021-33560 and CVE-2021-40528

ncurses: Fix for CVE-2021-39537

vim: fix CVE-2021-3968 and CVE-2021-3973

busybox: Fix for CVE-2021-42376

busybox: Fix for CVE-2021-42374

git: fix CVE-2021-40330

gmp: fix CVE-2021-43618

vim: fix CVE-2021-3927 and CVE-2021-3928

vim: fix CVE-2021-3796, CVE-2021-3872, and CVE-2021-3875

 

 

- ---------------

Fixes

- ---------------

README.OE-Core.md: update URLs

Revert "vim: fix 2021-3796"

available release updates

bind: update to 9.11.35

bitbake: bblayers/action: When adding layers, catch BBHandledException

bitbake: command: Ensure exceptions inheriting from BBHandledException are visible

bitbake: cooker: Ensure reparsing is handled correctly

bitbake: process/knotty: Improve early exception handling

bitbake: tinfoil: When sending commands we need to process events

build-appliance-image: Update to dunfell head revision

buildhistory: Fix srcrevs output

busybox: Fix multiple security issues in awk

cmake: FindGTest: Add target for gmock library

cups: Fix missing installation of cups sysv init scripts

cve-extra-exclusions: add db CVEs to exclusion list

dnf: Backport bugfix for upgrade

documentation: conf.py: explicit which version of bitbake objects.inv is used

gcc: Add CVE-2021-37322 to the list of CVEs to ignore

glib-2.0: Add security fixes

glibc-version.inc: remove branch= from GLIBC_GIT_URI

libdnf: Backport bugfix for upgrade calc

libpcre/libpcre2: correct SRC_URI

libsolv: update tag for missing CVEs

libunwind: Backport a fix for -fno-common option to compile

linux-firmware: upgrade 20210919 -> 20211027

linux-yocto/5.4: update to v5.4.158

lrzsz: Use Cross AR during compile

lttng-modules: do not search in non-existing folder during install

make-mod-scripts: pass CROSS_COMPILE to configure and build

oeqa/parselogs: Fix quoting

oeqa: fix warnings for append operators combined with +=

openssh: Improve LICENSE to show BSD license variants.

openssh: remove redundant BSD license

os-release: Add DISTRO_CODENAME as vardeps for do_compile

poky.conf: Bump version for 3.1.13 release

python3: upgrade 3.8.11 -> 3.8.12

recipetool: Set master branch only as fallback

remove reference to BB_SETSCENE_VERIFY_FUNCTION2

reproducible_build/package_XXX: Ensure SDE task is in dependency chain

runqemu: check the qemu PID has been set before kill()ing it

scripts/checklayer/common.py: Fixed a minor grammatical error

scripts/lib/wic/help.py: Update Fedora Kickstart URLs

scripts/oe-package-browser: Handle no packages being built

selftest/devtool: Check branch in git fetch

selftest: skip virgl test on centos 8 entirely

systemd: add packageconfig for wheel-group

vim: add patch number to CVE-2021-3778 patch

wic:direct.py: ignore invalid mountpoints during fstab update


[meta-cgl][PATCH] resource-agents: use branch main

Kai Kang
 

From: Kai Kang <kai.kang@...>

Branch master has been removed from resource-agents upstream git repo.
Use branch main instead.

Signed-off-by: Kai Kang <kai.kang@...>
---
.../cluster-resource-agents/resource-agents_4.5.0.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_4.5.0.bb b/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_4.5.0.bb
index 261681c..00ddd22 100644
--- a/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_4.5.0.bb
+++ b/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_4.5.0.bb
@@ -14,7 +14,7 @@ LICENSE:${PN}-extra = "GPLv3"
LICENSE:${PN}-extra-dbg = "GPLv3"
LICENSE:ldirectord = "GPLv2+"

-SRC_URI = "git://github.com/ClusterLabs/resource-agents;branch=master;protocol=https \
+SRC_URI = "git://github.com/ClusterLabs/resource-agents;branch=main;protocol=https \
file://01-disable-doc-build.patch \
file://02-set-OCF_ROOT_DIR-to-libdir-ocf.patch \
file://03-fix-header-defs-lookup.patch \
--
2.17.1


Re: Fetch of shared-mime-info and shared-mime-info-native never finishes.

Alexander Kanavin
 

I think it's just holiday season and freedesktop infra went down with no one to fix it. Give it a few days, it'll come back.

Alex


On Mon, 27 Dec 2021 at 23:04, Howard <howard.egan@...> wrote:

Ok so for some reason the repo for shared-mime-info is offline.  

I just ran a simple git clone of:


git clone git://gitlab.freedesktop.org/xdg/shared-mime-info.git;protocol=https

and it never completes or even starts near as I can tell.  

The src URI above is what is specified in the recipe.





M+ & H bugs with Milestone Movements WW52

Stephen Jolley
 

All,

YP M+ or high bugs which moved to a new milestone in WW52 are listed below:

Priority

Bug ID

Short Description

Changer

Owner

Was

Became

Medium+

5876

Add a test for the kernel -c menuconfig option

randy.macleod@...

unassigned@...

3.5 M1

3.5 M3

 

6428

Improve the ability to isolate changes that have caused a rebuild

randy.macleod@...

unassigned@...

3.5 M1

3.5 M3

 

10061

Ctrl+C during BB_HASHCHECK_FUNCTION execution does not interrupt processing nicely

randy.macleod@...

unassigned@...

3.5 M1

3.5 M2

 

10731

bitbake --observe-only doesn't work with memres

randy.macleod@...

unassigned@...

3.5 M1

3.5 M3

 

12760

CMake Toolchain File Has Wrong Module Path

randy.macleod@...

unassigned@...

3.5 M1

3.5 M2

 

13004

Automate yocto-check-layer -m option

randy.macleod@...

unassigned@...

3.5 M1

3.5 M3

 

13233

fetch2: try_premirror(): improve on updating repo from mirror

randy.macleod@...

unassigned@...

3.5 M1

3.5 M2

 

13285

YoctoProject Compatibility script improvements needed

randy.macleod@...

unassigned@...

3.5 M1

3.5 M3

 

13338

SDK  build fails if image contains bash

randy.macleod@...

unassigned@...

3.5 M1

3.5 M2

 

13419

recipes that add users to groups cannot rely on other recipes creating those groups (when population from sstate happens)

randy.macleod@...

unassigned@...

3.5 M1

3.5 M2

 

13425

Add bblock and bbunlock helper tools

randy.macleod@...

newcomer@...

3.5 M1

3.5 M2

 

13520

many valgrind tests fail for arm64

randy.macleod@...

randy.macleod@...

3.5 M1

3.5 M2

 

13705

master] bitbake and hashserve.sock left behind when ^C a build

randy.macleod@...

unassigned@...

3.5 M1

3.5 M2

 

13897

POSTINST_INTERCEPTS_DIR broken by undocumented POSTINST_INTERCEPTS_PATHS since thud

randy.macleod@...

unassigned@...

3.5 M1

3.5 M2

 

13910

Intermittent host UID contamination highlighted by devtool tests

randy.macleod@...

unassigned@...

3.5 M1

3.5 M2

 

13919

Multi License GPLv3 -lic cannot be installed into the image because it has incompatible license

randy.macleod@...

unassigned@...

3.5 M1

3.5 M2

 

13954

Invalid layerindex data causing backtrace in `bitbake-layers layerindex-fetch`

randy.macleod@...

unassigned@...

3.5 M1

3.5 M2

 

13975

cve-checker: save to alternate file format like JSON

randy.macleod@...

unassigned@...

3.5 M1

3.5 M3

 

13976

gdb8.3 do compile with musl is error

randy.macleod@...

unassigned@...

3.5 M1

3.5 M2

 

14020

environment-setup script in multilib eSDK doesn't work for multilib variant

randy.macleod@...

unassigned@...

3.5 M1

3.5 M2

 

14045

git fetcher deadlock with self-referencing sub-modules

randy.macleod@...

unassigned@...

3.5 M1

3.5 M2

 

14066

bitbake core-image-base -c populate_sdk fails when image contains bash, core-utils and package_deb is used

randy.macleod@...

unassigned@...

3.5 M1

3.5 M2

 

14081

Not possible to get src package in image when using PACKAGE_DEBUG_SPLIT_STYLE='debug-file-directory'

randy.macleod@...

jonathan.richardson@...

3.5 M1

3.5 M2

 

14157

git fetcher: consider using different git commands for repo packing, eliminating "git pack-redundant"

randy.macleod@...

newcomer@...

3.5 M1

3.5 M3

 

14163

AB-INT PTEST ARM: libevent arm ptest intermittent failure

randy.macleod@...

ross@...

3.5 M1

3.5 M2

 

14165

AB-INT PTEST: strace ptest intermittent failure in qual_fault-syscall.test

randy.macleod@...

randy.macleod@...

3.5 M1

3.5 M2

 

14196

Add integration to send data to KCIDB

randy.macleod@...

unassigned@...

3.5 M1

3.5 M2

 

14206

oe-selftest perl errors on rpm based distros

randy.macleod@...

unassigned@...

3.5 M1

3.5 M2

 

14218

Recipe rebuilds can contaminate builds

randy.macleod@...

unassigned@...

3.5 M1

3.5 M2

 

14236

npmsw does not support github URLs in the npm-shrinkwrap.json file

randy.macleod@...

unassigned@...

3.5 M1

3.5 M2

 

14270

go packages are not reproducible

randy.macleod@...

unassigned@...

3.5 M1

3.5 M2

 

14274

dnf parselogs failed on qemux86-64 due to networking error

randy.macleod@...

unassigned@...

3.5 M1

3.5 M2

 

14383

archiver.bbclass:do_ar_mirror copies entire contents of ${DL_DIR} to ${WORKDIR} when used with npm.bbclass

randy.macleod@...

unassigned@...

3.5 M1

3.5 M2

 

14434

[3.4 M1] dmesg: proc: Bad value for 'hidepid' with poky-altcfg distro

randy.macleod@...

unassigned@...

3.5 M1

3.5 M2

 

14464

AB-INT PTEST ARM: glib-2.0 glib/timeout.test failure

randy.macleod@...

unassigned@...

3.5 M1

3.5 M2

 

14467

curl timeout while dnf is downloading package

randy.macleod@...

sakib.sajal@...

3.5 M1

3.5 M3

 

14525

rust-llvm isn't reproducible

randy.macleod@...

pgowda.cve@...

3.5 M1

3.5 M2

 

14528

remove floppy controller from qemu

randy.macleod@...

unassigned@...

3.5 M1

3.5 M2

 

14560

AB-INT PTEST ARM: tcl timer.test failure

randy.macleod@...

ross@...

3.5 M1

3.5 M2

 

14556

Running dates tests in systemd images causes loss of networking

randy.macleod@...

ross@...

3.5 M1

3.5 M2

 

14570

debuginfod gdb: *** stack smashing detected ***: terminated

randy.macleod@...

pgowda.cve@...

3.5 M1

3.5 M2

 

14588

testimage: oe_syslog.SyslogTestConfig.test_syslog_startup_config failed

randy.macleod@...

unassigned@...

3.5 M1

3.5 M3

 

14596

AB-INT PTEST ARM: strace ptest intermittent failure in strace-T.test

randy.macleod@...

ross@...

3.5 M1

3.5 M2

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Enhancements/Bugs closed WW52!

Stephen Jolley
 

All,

The below were the owners of enhancements or bugs closed during the last week!

Who

Count

randy.macleod@...

3

richard.purdie@...

3

trevor.gamblin@...

2

Grand Total

8

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Current high bug count owners for Yocto Project 3.5

Stephen Jolley
 

All,

Below is the list as of top 45 bug owners as of the end of WW52 of who have open medium or higher bugs and enhancements against YP 3.5.   There are 85 possible work days left until the final release candidates for YP 3.5 needs to be released.

Who

Count

michael.opdenacker@...

37

ross@...

36

randy.macleod@...

22

david.reyna@...

22

bruce.ashfield@...

16

timothy.t.orling@...

15

trevor.gamblin@...

13

sakib.sajal@...

12

JPEWhacker@...

12

richard.purdie@...

8

mhalstead@...

8

saul.wold@...

7

kai.kang@...

7

bluelightning@...

6

chee.yang.lee@...

4

hongxu.jia@...

4

pgowda.cve@...

3

jon.mason@...

3

kiran.surendran@...

3

Qi.Chen@...

3

alexandre.belloni@...

2

mshah@...

2

raj.khem@...

2

alejandro@...

2

jay.shen.teoh@...

1

TicoTimo@...

1

shachar@...

1

open.source@...

1

yf3yu@...

1

pokylinux@...

1

akuster808@...

1

limon.anibal@...

1

john.kaldas.enpj@...

1

kexin.hao@...

1

elberger@...

1

aehs29@...

1

thomas.perrot@...

1

matthewzmd@...

1

Martin.Jansa@...

1

yi.zhao@...

1

nicolas.dechesne@...

1

mingli.yu@...

1

jonathan.richardson@...

1

mark.hatle@...

1

mostthingsweb@...

1

Grand Total

270

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Yocto Project Newcomer & Unassigned Bugs - Help Needed

Stephen Jolley
 

All,

 

The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please review: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and how to create a bugzilla account at: https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work on who doesn't have deep experience with the project.  If anyone can help, please take ownership of the bug and send patches!  If anyone needs help/advice there are people on irc who can likely do so, or some of the more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 393 unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out with these.  Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.  There are also roughly four different "priority" classes right now, “3.4”, “3.5, "3.99" and "Future", the more pressing/urgent issues being in "3.4" and then “3.5”.

 

Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (sjolley.yp.pm@...) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a Bugzilla account).  The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Re: Fetch of shared-mime-info and shared-mime-info-native never finishes.

Howard
 

Ok so for some reason the repo for shared-mime-info is offline.  

I just ran a simple git clone of:


git clone git://gitlab.freedesktop.org/xdg/shared-mime-info.git;protocol=https

and it never completes or even starts near as I can tell.  

The src URI above is what is specified in the recipe.


Re: Fetch of shared-mime-info and shared-mime-info-native never finishes.

Howard
 

I should point out that nothing changed on my end and this was all building fine Friday Dec 24, and now it does not build on Monday Dec 27.