[OE-core] [PATCH] dtc: upgrade 1.6.0 -> 1.6.1

2021-06-09 Thread wangmy 
0001-fdtdump-Fix-gcc11-warning.patch
removed since it is included in 1.6.1

Signed-off-by: Wang Mingyu 
---
 .../dtc/0001-fdtdump-Fix-gcc11-warning.patch  | 35 ---
 .../dtc/{dtc_1.6.0.bb => dtc_1.6.1.bb}|  4 +--
 2 files changed, 1 insertion(+), 38 deletions(-)
 delete mode 100644 
meta/recipes-kernel/dtc/dtc/0001-fdtdump-Fix-gcc11-warning.patch
 rename meta/recipes-kernel/dtc/{dtc_1.6.0.bb => dtc_1.6.1.bb} (68%)

diff --git a/meta/recipes-kernel/dtc/dtc/0001-fdtdump-Fix-gcc11-warning.patch 
b/meta/recipes-kernel/dtc/dtc/0001-fdtdump-Fix-gcc11-warning.patch
deleted file mode 100644
index ec825cbf7b..00
--- a/meta/recipes-kernel/dtc/dtc/0001-fdtdump-Fix-gcc11-warning.patch
+++ /dev/null
@@ -1,35 +0,0 @@
-From 4827e0db6c4f7dea7f4094f49d3bb48ef6dfdc2d Mon Sep 17 00:00:00 2001
-From: David Gibson 
-Date: Wed, 6 Jan 2021 14:52:26 +1100
-Subject: [PATCH] fdtdump: Fix gcc11 warning
-
-In one place, fdtdump abuses fdt_set_magic(), passing it just a small char
-array instead of the full fdt header it expects.  That's relying on the
-fact that in fact fdt_set_magic() will only actually access the first 4
-bytes of the buffer.
-
-This trips a new warning in GCC 11 - and it's entirely possible it was
-always UB.  So, don't do that.
-
-Upstream-Status: Backport 
[https://git.kernel.org/pub/scm/utils/dtc/dtc.git/patch/?id=ca16a723fa9dde9c5da80dba567f48715000e77c]
-Signed-off-by: David Gibson 

- fdtdump.c | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/fdtdump.c b/fdtdump.c
-index 9613bef..d9fb374 100644
 a/fdtdump.c
-+++ b/fdtdump.c
-@@ -217,7 +217,7 @@ int main(int argc, char *argv[])
-   char *p = buf;
-   char *endp = buf + len;
- 
--  fdt_set_magic(smagic, FDT_MAGIC);
-+  fdt32_st(smagic, FDT_MAGIC);
- 
-   /* poor man's memmem */
-   while ((endp - p) >= FDT_MAGIC_SIZE) {
--- 
-2.30.1
-
diff --git a/meta/recipes-kernel/dtc/dtc_1.6.0.bb 
b/meta/recipes-kernel/dtc/dtc_1.6.1.bb
similarity index 68%
rename from meta/recipes-kernel/dtc/dtc_1.6.0.bb
rename to meta/recipes-kernel/dtc/dtc_1.6.1.bb
index a407137859..de9a46d3ef 100644
--- a/meta/recipes-kernel/dtc/dtc_1.6.0.bb
+++ b/meta/recipes-kernel/dtc/dtc_1.6.1.bb
@@ -3,9 +3,7 @@ require dtc.inc
 LIC_FILES_CHKSUM = "file://GPL;md5=b234ee4d69f5fce4486a80fdaf4a4263 \

file://libfdt/libfdt.h;beginline=4;endline=7;md5=05bb357cfb75cae7d2b01d2ee8d76407"
 
-SRCREV = "2525da3dba9beceb96651dc2986581871dbeca30"
-
-SRC_URI += "file://0001-fdtdump-Fix-gcc11-warning.patch"
+SRCREV = "b6910bec11614980a21e46fbccc35934b671bd81"
 
 S = "${WORKDIR}/git"
 
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#152821): 
https://lists.openembedded.org/g/openembedded-core/message/152821
Mute This Topic: https://lists.openembedded.org/mt/83438764/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] diffoscope: upgrade 175 -> 177

2021-06-09 Thread wangmy 
Signed-off-by: Wang Mingyu 
---
 .../diffoscope/{diffoscope_175.bb => diffoscope_177.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-support/diffoscope/{diffoscope_175.bb => 
diffoscope_177.bb} (92%)

diff --git a/meta/recipes-support/diffoscope/diffoscope_175.bb 
b/meta/recipes-support/diffoscope/diffoscope_177.bb
similarity index 92%
rename from meta/recipes-support/diffoscope/diffoscope_175.bb
rename to meta/recipes-support/diffoscope/diffoscope_177.bb
index 853f8dd3a0..0d9061dda0 100644
--- a/meta/recipes-support/diffoscope/diffoscope_175.bb
+++ b/meta/recipes-support/diffoscope/diffoscope_177.bb
@@ -12,7 +12,7 @@ PYPI_PACKAGE = "diffoscope"
 
 inherit pypi setuptools3
 
-SRC_URI[sha256sum] = 
"b87481752815140e35088647ccdea13297e41a2d72772e842590360b662f7533"
+SRC_URI[sha256sum] = 
"8ac0cad150914bab2a53caa3f21876a78b092f3d2a36b9134874cd5c04a26b2e"
 
 RDEPENDS_${PN} += "binutils vim squashfs-tools python3-libarchive-c 
python3-magic python3-rpm"
 
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#152820): 
https://lists.openembedded.org/g/openembedded-core/message/152820
Mute This Topic: https://lists.openembedded.org/mt/83438762/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [meta-oe][dunfell][PATCH] opencv: Add fix for CVE-2019-5063 and CVE-2019-5064

2021-06-09 Thread akash hadke 
Hi Armin,

Any update on this?

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#152819): 
https://lists.openembedded.org/g/openembedded-core/message/152819
Mute This Topic: https://lists.openembedded.org/mt/83071295/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] arch-armv4: Allow -march=armv4

2021-06-09 Thread Khem Raj 
Even though it is deprecated in GCC 6 [1] it has not yet been
removed from gcc upstream. We do have active machines in OE
ecosystem which use armv4 ( SA11xx ) e.g. collie in meta-handheld
so until upstream gcc takes next step to remove them
lets support armv4 again, we are still carrying the relevant gcc patch
to support v4 BX fix.

[1] https://gcc.gnu.org/gcc-6/changes.html#arm

Signed-off-by: Khem Raj 
Cc: Andrea Adami 
---
 meta/conf/machine/include/arm/arch-armv4.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/conf/machine/include/arm/arch-armv4.inc 
b/meta/conf/machine/include/arm/arch-armv4.inc
index fac2bdf952..b71739c20a 100644
--- a/meta/conf/machine/include/arm/arch-armv4.inc
+++ b/meta/conf/machine/include/arm/arch-armv4.inc
@@ -2,7 +2,7 @@ DEFAULTTUNE ?= "armv4"
 
 TUNEVALID[arm] = "Enable ARM instruction set"
 TUNEVALID[armv4] = "Enable instructions for ARMv4"
-TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'armv4', ' 
-march=armv4t', '', d)}"
+TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'armv4', ' 
-march=armv4${ARMPKGSFX_THUMB}', '', d)}"
 # enable --fix-v4bx when we have armv4 in TUNE_FEATURES, but then disable it 
when we have also armv5 or thumb
 # maybe we should extend bb.utils.contains to support check for any 
checkvalues in value, now it does 
 # checkvalues.issubset(val) which cannot be used for negative test of foo 
neither bar in value
-- 
2.32.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#152818): 
https://lists.openembedded.org/g/openembedded-core/message/152818
Mute This Topic: https://lists.openembedded.org/mt/83436409/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [V2][PATCH] libjpeg-turbo: fix do_compile error on armv5

2021-06-09 Thread Andrea Adami 
On Wed, Jun 9, 2021 at 7:30 PM Andre McCurdy  wrote:
>
> On Wed, Jun 9, 2021 at 12:32 AM Changqing Li  
> wrote:
> >
> > From: Changqing Li 
> >
> > fix below error:
> > /include/arm_neon.h:31:2: error: #error "NEON intrinsics not available with 
> > the soft-float ABI. Please use -mfloat-abi=softfp or -mfloat-abi=hard"
> > 31 | #error "NEON intrinsics not available with the soft-float ABI. Please 
> > use -mfloat-abi=softfp or -mfloat-abi=hard"
> >
> > Neon is not supported by armv5, disable the simd extension build.
>
> Drop this comment. Neon may be missing from other ISA levels too (i.e.
> this fix is not specific to armv5).
>
> > Signed-off-by: Changqing Li 
> > ---
> >  meta/recipes-graphics/jpeg/libjpeg-turbo_2.1.0.bb | 2 ++
> >  1 file changed, 2 insertions(+)
> >
> > diff --git a/meta/recipes-graphics/jpeg/libjpeg-turbo_2.1.0.bb 
> > b/meta/recipes-graphics/jpeg/libjpeg-turbo_2.1.0.bb
> > index 7f91cc02ac..da21971113 100644
> > --- a/meta/recipes-graphics/jpeg/libjpeg-turbo_2.1.0.bb
> > +++ b/meta/recipes-graphics/jpeg/libjpeg-turbo_2.1.0.bb
> > @@ -40,6 +40,8 @@ EXTRA_OECMAKE_append_class-target = " 
> > ${@bb.utils.contains("TUNE_FEATURES", "mx3
> >  # Work around missing non-floating point ABI support in MIPS
> >  EXTRA_OECMAKE_append_class-target = " 
> > ${@bb.utils.contains("MIPSPKGSFX_FPU", "-nf", "-DWITH_SIMD=False", "", d)}"
> >
> > +EXTRA_OECMAKE_append_class-target = " ${@ ('') if 
> > (d.getVar('TUNE_CCARGS_MFPU') != '') else '-DWITH_SIMD=False'}"
>
> Shouldn't this be checking for neon in TUNE_FEATURES rather than
> TUNE_CCARGS_MFPU? It should also probably be conditional on the _arm
> over-ride since neon will be missing from
> TUNE_CCARGS_MFPU/TUNE_FEATURES for other architectures. Since big
> endian ARM doesn't use the _arm over-ride you will also need a
> duplicate line with the same logic with the _armeb override too. See
> the lines below which do the equivalent for _powerpc / _powerpc64 as a
> reference.
>
> >  # Provide a workaround if Altivec unit is not present in PPC
> >  EXTRA_OECMAKE_append_class-target_powerpc = " 
> > ${@bb.utils.contains("TUNE_FEATURES", "altivec", "", "-DWITH_SIMD=False", 
> > d)}"
> >  EXTRA_OECMAKE_append_class-target_powerpc64 = " 
> > ${@bb.utils.contains("TUNE_FEATURES", "altivec", "", "-DWITH_SIMD=False", 
> > d)}"
> > --
> > 2.17.1
> >
> >
> >
> >
>
> 
>

Just to confirm it fails on armv4 as well.

CheckSymbolExists.c:8:19: error: 'vld1_s16_x3' undeclared (first use
in this function)
CheckSymbolExists.c:8:19: error: 'vld1_u16_x2' undeclared (first use
in this function)
CheckSymbolExists.c:8:19: error: 'vld1q_u8_x4' undeclared (first use
in this function)

...
#include 
...
3 | #error "float ABI = softfp"

A.A.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#152817): 
https://lists.openembedded.org/g/openembedded-core/message/152817
Mute This Topic: https://lists.openembedded.org/mt/83415559/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH 3/3] opkg: add QA check for openssl feed verification

2021-06-09 Thread Alex Stewart 
Feed signature checking with OpenSSL will be deprecated in the next
release of opkg.

Upstream ML Announcement:
https://groups.google.com/g/opkg-devel/c/drqw5_HuXuU

The opkg-0.4.5 configure.ac already throws a warning when
`--enable-openssl` is requested.

Add a temporary QA check to the opkg recipe, which will throw a warning
to the builder when they have `openssl` enabled in their opkg
PACKAGECONFIG. This will give builders some time to either change their
feed verification mechanism, or raise their use-case with upstream.

Signed-off-by: Alex Stewart 
---
 meta/recipes-devtools/opkg/opkg_0.4.5.bb | 13 +
 1 file changed, 13 insertions(+)

diff --git a/meta/recipes-devtools/opkg/opkg_0.4.5.bb 
b/meta/recipes-devtools/opkg/opkg_0.4.5.bb
index 
bc948647c804f3f24800275289ef3fd7dee9335f..56d6211a8a8112b4ae1afcd8987f950fcbcb
 100644
--- a/meta/recipes-devtools/opkg/opkg_0.4.5.bb
+++ b/meta/recipes-devtools/opkg/opkg_0.4.5.bb
@@ -60,6 +60,19 @@ do_install_ptest () {
sed -i -e '/@PYTHONPATH=. $(PYTHON) $^/a\\t@if [ "$$?" != "0" ];then 
echo "FAIL:"$^;else echo "PASS:"$^;fi' ${D}${PTEST_PATH}/tests/Makefile
 }
 
+WARN_QA_append += "openssl-deprecation"
+QAPKGTEST[openssl-deprecation] = "package_qa_check_openssl_deprecation"
+def package_qa_check_openssl_deprecation (package, d, messages):
+sane = True
+
+pkgconfig = (d.getVar("PACKAGECONFIG") or "").split()
+if pkgconfig and 'openssl' in pkgconfig:
+package_qa_add_message(messages, 'openssl-deprecation', '"openssl" in 
opkg.bb PACKAGECONFIG. Feed signature checking with OpenSSL will be deprecated 
in the next opkg release. Consider using GPG checking instead.')
+sane = False
+
+return sane
+
+
 RDEPENDS_${PN} = "${VIRTUAL-RUNTIME_update-alternatives} opkg-arch-config 
libarchive"
 RDEPENDS_${PN}_class-native = ""
 RDEPENDS_${PN}_class-nativesdk = ""
-- 
2.32.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#152816): 
https://lists.openembedded.org/g/openembedded-core/message/152816
Mute This Topic: https://lists.openembedded.org/mt/83431242/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH 2/3] opkg: upgrade to version 0.4.5

2021-06-09 Thread Alex Stewart 
Drop patches which have been accepted upstream.

Signed-off-by: Alex Stewart 
---
 ...e-OS-negotiate-relative-package-dirs.patch | 43 ---
 .../opkg/opkg/sourcedateepoch.patch   | 24 ---
 .../opkg/{opkg_0.4.4.bb => opkg_0.4.5.bb} |  6 +--
 3 files changed, 2 insertions(+), 71 deletions(-)
 delete mode 100644 
meta/recipes-devtools/opkg/opkg/0001-tests-let-the-OS-negotiate-relative-package-dirs.patch
 delete mode 100644 meta/recipes-devtools/opkg/opkg/sourcedateepoch.patch
 rename meta/recipes-devtools/opkg/{opkg_0.4.4.bb => opkg_0.4.5.bb} (91%)

diff --git 
a/meta/recipes-devtools/opkg/opkg/0001-tests-let-the-OS-negotiate-relative-package-dirs.patch
 
b/meta/recipes-devtools/opkg/opkg/0001-tests-let-the-OS-negotiate-relative-package-dirs.patch
deleted file mode 100644
index 
33b7280e5a1d171400e0765c7d66072e3a718d17..
--- 
a/meta/recipes-devtools/opkg/opkg/0001-tests-let-the-OS-negotiate-relative-package-dirs.patch
+++ /dev/null
@@ -1,43 +0,0 @@
-From 4acda6d01c5abd33f1a1a3275fd695363f59473f Mon Sep 17 00:00:00 2001
-From: Alex Stewart 
-Date: Tue, 15 Dec 2020 15:17:54 -0600
-Subject: [opkg][opkg-0.4.4 PATCH] tests: let the OS negotiate relative package
- dirs
-
-In cases where a regression test requires that a package be installed to
-a subdirectory in the test feed, the opk.py module will attempt to
-resolve the subdirectory and rebase it to the root of the test feed.
-
-This is unnecessary, since all operations which make use of the
-subdirectory path do so from the perspective of the test feed already.
-Further, the rebase implementation breaks in cases where the test feed
-is beyond a symlink.
-
-Remove the resolve-and-rebase logic, and allow the OS to negotiate the
-relative path.
-
-Upstream-Status: Submitted 
[https://groups.google.com/g/opkg-devel/c/dE1o7_OVQSY]
-
-Signed-off-by: Alex Stewart 

- tests/opk.py | 4 +---
- 1 file changed, 1 insertion(+), 3 deletions(-)
-
-diff --git a/tests/opk.py b/tests/opk.py
-index 
692339567f72441766c8e658edc5bdf6a339f77d..711abacaeb328283e31524f6a49305fc7d39696a
 100644
 a/tests/opk.py
-+++ b/tests/opk.py
-@@ -58,9 +58,7 @@ class Opk:
- if 'Version' not in control.keys():
- control['Version'] = '1.0'
- if subdirectory is not None:
--subdir = Path(subdirectory).resolve()
--opkdir = Path(cfg.opkdir)
--self._relative_dir = subdir.relative_to(opkdir)
-+self._relative_dir = Path(subdirectory)
- else:
- self._relative_dir = None
- self.control = control
--- 
-2.29.2
-
diff --git a/meta/recipes-devtools/opkg/opkg/sourcedateepoch.patch 
b/meta/recipes-devtools/opkg/opkg/sourcedateepoch.patch
deleted file mode 100644
index 
4578fa33be2cdb7de509796b43ffa96f6ab291dc..
--- a/meta/recipes-devtools/opkg/opkg/sourcedateepoch.patch
+++ /dev/null
@@ -1,24 +0,0 @@
-Having CLEAN_DATE come from the current date doesn't allow for build
-reproducibility. Add the option of using SOURCE_DATE_EPOCH if set
-which for OE, it will be.
-
-Upstream-Status: Pending
-RP 2021/2/2
-
-Index: opkg-0.4.4/configure.ac
-===
 opkg-0.4.4.orig/configure.ac
-+++ opkg-0.4.4/configure.ac
-@@ -281,7 +281,11 @@ AC_FUNC_UTIME_NULL
- AC_FUNC_VPRINTF
- AC_CHECK_FUNCS([memmove memset mkdir regcomp strchr strcspn strdup strerror 
strndup strrchr strstr strtol strtoul sysinfo utime])
- 
--CLEAN_DATE=`date +"%B %Y" | tr -d '\n'`
-+if ! test -z "$SOURCE_DATE_EPOCH" ; then
-+CLEAN_DATE=`LC_ALL=C date -d @$SOURCE_DATE_EPOCH +"%B %Y" | tr -d '\n'`
-+else
-+CLEAN_DATE=`date +"%B %Y" | tr -d '\n'`
-+fi
- 
- AC_SUBST([CLEAN_DATE])
- 
diff --git a/meta/recipes-devtools/opkg/opkg_0.4.4.bb 
b/meta/recipes-devtools/opkg/opkg_0.4.5.bb
similarity index 91%
rename from meta/recipes-devtools/opkg/opkg_0.4.4.bb
rename to meta/recipes-devtools/opkg/opkg_0.4.5.bb
index 
9eca61be2aa581ecdb1bb38a6af858899c31203e..bc948647c804f3f24800275289ef3fd7dee9335f
 100644
--- a/meta/recipes-devtools/opkg/opkg_0.4.4.bb
+++ b/meta/recipes-devtools/opkg/opkg_0.4.5.bb
@@ -15,13 +15,11 @@ PE = "1"
 SRC_URI = 
"http://downloads.yoctoproject.org/releases/${BPN}/${BPN}-${PV}.tar.gz \
file://opkg.conf \

file://0001-opkg_conf-create-opkg.lock-in-run-instead-of-var-run.patch \
-   file://0001-tests-let-the-OS-negotiate-relative-package-dirs.patch \
-   file://sourcedateepoch.patch \
file://run-ptest \
 "
 
-SRC_URI[md5sum] = "345900c1d4747d58455867f9fe88ca43"
-SRC_URI[sha256sum] = 
"2217acc58b8eb31300631ebae75e222ebc700c9c1cf6408088705d19a472c839"
+SRC_URI[md5sum] = "5dc41ad37d88803b5e0f456a9c5a0811"
+SRC_URI[sha256sum] = 
"a1214a75fa34fb9228db8da47308e0e711b1c93fd8938cf164c10fd28eb50f1e"
 
 # This needs to be before ptest inherit, otherwise all ptest files end packaged
 # in libopkg package if OPKGLIBDIR =

[OE-core] [PATCH 1/3] opkg-utils: upgrade to version 0.4.5

2021-06-09 Thread Alex Stewart 
Signed-off-by: Alex Stewart 
---
 .../opkg-utils/{opkg-utils_0.4.3.bb => opkg-utils_0.4.5.bb}   | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-devtools/opkg-utils/{opkg-utils_0.4.3.bb => 
opkg-utils_0.4.5.bb} (94%)

diff --git a/meta/recipes-devtools/opkg-utils/opkg-utils_0.4.3.bb 
b/meta/recipes-devtools/opkg-utils/opkg-utils_0.4.5.bb
similarity index 94%
rename from meta/recipes-devtools/opkg-utils/opkg-utils_0.4.3.bb
rename to meta/recipes-devtools/opkg-utils/opkg-utils_0.4.5.bb
index 
ce299d6b6358a037973cceabe2f343a0daec24f8..93d291110444211990c4c204fc23a84ec86b417e
 100644
--- a/meta/recipes-devtools/opkg-utils/opkg-utils_0.4.3.bb
+++ b/meta/recipes-devtools/opkg-utils/opkg-utils_0.4.5.bb
@@ -12,8 +12,8 @@ SRC_URI = 
"http://git.yoctoproject.org/cgit/cgit.cgi/${BPN}/snapshot/${BPN}-${PV
"
 UPSTREAM_CHECK_URI = 
"http://git.yoctoproject.org/cgit/cgit.cgi/opkg-utils/refs/";
 
-SRC_URI[md5sum] = "7bbadb3c381f3ea935b21d3bb8cc4671"
-SRC_URI[sha256sum] = 
"046517600fb0aed6c4645edefe02281f4fa2f1c02f71596152d93172452c0b01"
+SRC_URI[md5sum] = "025b19744e5c7fc1c8380e17df1fcc64"
+SRC_URI[sha256sum] = 
"528635e674addea5c2b3a3268404ad04a952c4f410d17c3d754f5dd5529770c9"
 
 TARGET_CC_ARCH += "${LDFLAGS}"
 
-- 
2.32.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#152814): 
https://lists.openembedded.org/g/openembedded-core/message/152814
Mute This Topic: https://lists.openembedded.org/mt/83431239/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] conf/machine-sdk: Add ppc64 SDK machine

2021-06-09 Thread Marcus Comstedt 
Signed-off-by: Marcus Comstedt 
---

I was able to work around the lack of this file by putting

SDKMACHINE = ""
SDK_ARCH = "${BUILD_ARCH}"

into local.conf, but it seems to me that should not be necessary.

Thanks

  // Marcus


 meta/conf/machine-sdk/ppc64.conf | 2 ++
 1 file changed, 2 insertions(+)
 create mode 100644 meta/conf/machine-sdk/ppc64.conf

diff --git a/meta/conf/machine-sdk/ppc64.conf b/meta/conf/machine-sdk/ppc64.conf
new file mode 100644
index 00..1eb064eef0
--- /dev/null
+++ b/meta/conf/machine-sdk/ppc64.conf
@@ -0,0 +1,2 @@
+SDK_ARCH = "ppc64"
+ABIEXTENSION_class-nativesdk = ""
-- 
2.31.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#152813): 
https://lists.openembedded.org/g/openembedded-core/message/152813
Mute This Topic: https://lists.openembedded.org/mt/83429347/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] systemd: install new sysext tool via systemd-extra-utils

2021-06-09 Thread Luca Bocassi 
From: Luca Boccassi 

New standalone (no new dependency) utility added in v248

Signed-off-by: Luca Boccassi 
---
 meta/recipes-core/systemd/systemd_248.3.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-core/systemd/systemd_248.3.bb 
b/meta/recipes-core/systemd/systemd_248.3.bb
index 4e65656494..37607708f7 100644
--- a/meta/recipes-core/systemd/systemd_248.3.bb
+++ b/meta/recipes-core/systemd/systemd_248.3.bb
@@ -507,6 +507,7 @@ FILES_${PN}-extra-utils = "\
 ${bindir}/systemd-cgls \
 ${bindir}/systemd-cgtop \
 ${bindir}/systemd-stdio-bridge \
+${bindir}/systemd-sysext \
 ${base_bindir}/systemd-ask-password \
 ${base_bindir}/systemd-tty-ask-password-agent \
 
${systemd_unitdir}/system/systemd-ask-password-console.path \
-- 
2.29.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#152812): 
https://lists.openembedded.org/g/openembedded-core/message/152812
Mute This Topic: https://lists.openembedded.org/mt/83429046/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] overlayfs.bbclass: generate overlayfs mount units

2021-06-09 Thread Vyacheslav Yurkov 

Hi Andrei,
Like you mentioned, it's application specific. The advantage of 
overlayfs here is that you preserve the data that was changed by user 
(in case of persistent storage), which of course would hide the data 
from rootfs, or your just see the defaults from rootfs if the data was 
not changed. With bind mounts you would need to copy default data first 
into your tmpfs/ext4 bind mount if you wanna have defaults.


Vyacheslav

I was looking into something like this lately. There are actually two kinds of 
write access - volatile (tmpfs) and persistent (to disk). So my approach would 
have been to use bind mounts from a tmpfs/ext4 based on configuration per 
recipe. Is there any advantage to working with overlayfs in this case? The main 
idea is to have state that doesn't come from the ro part of the OS because 
otherwise, updates will be shadowed by the overlayfs. So I fail to see the 
advantage of using a set of overlayfs mounts instead of bind mounts. At least 
with bind mounts, it will always shadow the rootfs bits so you can catch early 
this case.

Depending on your use case, most of the times, you'd want this "state" setup 
happening pre init (in initramfs, for example), especially if you want to handle 
persistent systemd logging or machine id, etc.




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#152811): 
https://lists.openembedded.org/g/openembedded-core/message/152811
Mute This Topic: https://lists.openembedded.org/mt/83284453/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [V2][PATCH] libjpeg-turbo: fix do_compile error on armv5

2021-06-09 Thread Andre McCurdy 
On Wed, Jun 9, 2021 at 12:32 AM Changqing Li  wrote:
>
> From: Changqing Li 
>
> fix below error:
> /include/arm_neon.h:31:2: error: #error "NEON intrinsics not available with 
> the soft-float ABI. Please use -mfloat-abi=softfp or -mfloat-abi=hard"
> 31 | #error "NEON intrinsics not available with the soft-float ABI. Please 
> use -mfloat-abi=softfp or -mfloat-abi=hard"
>
> Neon is not supported by armv5, disable the simd extension build.

Drop this comment. Neon may be missing from other ISA levels too (i.e.
this fix is not specific to armv5).

> Signed-off-by: Changqing Li 
> ---
>  meta/recipes-graphics/jpeg/libjpeg-turbo_2.1.0.bb | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/meta/recipes-graphics/jpeg/libjpeg-turbo_2.1.0.bb 
> b/meta/recipes-graphics/jpeg/libjpeg-turbo_2.1.0.bb
> index 7f91cc02ac..da21971113 100644
> --- a/meta/recipes-graphics/jpeg/libjpeg-turbo_2.1.0.bb
> +++ b/meta/recipes-graphics/jpeg/libjpeg-turbo_2.1.0.bb
> @@ -40,6 +40,8 @@ EXTRA_OECMAKE_append_class-target = " 
> ${@bb.utils.contains("TUNE_FEATURES", "mx3
>  # Work around missing non-floating point ABI support in MIPS
>  EXTRA_OECMAKE_append_class-target = " ${@bb.utils.contains("MIPSPKGSFX_FPU", 
> "-nf", "-DWITH_SIMD=False", "", d)}"
>
> +EXTRA_OECMAKE_append_class-target = " ${@ ('') if 
> (d.getVar('TUNE_CCARGS_MFPU') != '') else '-DWITH_SIMD=False'}"

Shouldn't this be checking for neon in TUNE_FEATURES rather than
TUNE_CCARGS_MFPU? It should also probably be conditional on the _arm
over-ride since neon will be missing from
TUNE_CCARGS_MFPU/TUNE_FEATURES for other architectures. Since big
endian ARM doesn't use the _arm over-ride you will also need a
duplicate line with the same logic with the _armeb override too. See
the lines below which do the equivalent for _powerpc / _powerpc64 as a
reference.

>  # Provide a workaround if Altivec unit is not present in PPC
>  EXTRA_OECMAKE_append_class-target_powerpc = " 
> ${@bb.utils.contains("TUNE_FEATURES", "altivec", "", "-DWITH_SIMD=False", d)}"
>  EXTRA_OECMAKE_append_class-target_powerpc64 = " 
> ${@bb.utils.contains("TUNE_FEATURES", "altivec", "", "-DWITH_SIMD=False", d)}"
> --
> 2.17.1
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#152810): 
https://lists.openembedded.org/g/openembedded-core/message/152810
Mute This Topic: https://lists.openembedded.org/mt/83415559/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [oe] Fedora 34, shadow-native/icedtea7-native, umask problems ?

2021-06-09 Thread Jacob Kroon 

On 6/2/21 6:01 PM, Jacob Kroon via lists.openembedded.org wrote:

On 6/2/21 8:32 AM, Jacob Kroon via lists.openembedded.org wrote:

Hi,

I'm using Fedora 34 and OE-Core/Bitbake/layers from git master as of 
today, with reproducible builds. Sometimes when rebuilding my image I 
see sudden changes in file permissions (jumping back and forth) in the 
buildhistory output for two native recipes:


shadow-native: (OE-Core)

-drwxr-xr-x -  -  40 ./var/spool/mail
+drwxrwxr-x -  -  40 ./var/spool/mail




I can reproduce it reliably with these commands:

After I do:
# bitbake -c cleansstate shadow-native && bitbake shadow-native
I get:
drwxrwxr-x - - 40 ./var/spool/mail

After I do:
# bitbake -c clean shadow-native && bitbake shadow-native
I get:
drwxr-xr-x - - 40 ./var/spool/mail

shadow.inc does:


do_install_append() {
     ...
     install -m 0775 -d ${D}${localstatedir}/spool/mail


So it looks to me like those permissions are either not recorded in the 
sstate cache, or they are not restored when extracting the cache.




I see this issue in master and hardknot builds, but not in dunfell builds.
/Jacob

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#152809): 
https://lists.openembedded.org/g/openembedded-core/message/152809
Mute This Topic: https://lists.openembedded.org/mt/83262243/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 04/10] cmake: update 3.20.2 -> 3.20.3

2021-06-09 Thread Alexander Kanavin 
On Wed, 9 Jun 2021 at 13:37, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:

> Thanks Michael and Alex. We can therefore pretty safely say that something
> was
> broken between the 240 and 305 of the centos8 kernel for the 32 bit syscall
> utimensat syscalls.
>
> I did poke around https://github.com/kernelim/linux/tree/centos8 which
> does
> have a kernel diff but it is huge and you have to clone the repo to get it.
>
> git show a3342908613ba72a84f652ca7a56c3e2113bda12 | grep sys_utimensat -C
> 40
>
> shows they did add the syscalls in that kernel.
>
> So this does look to be a RedHat issue. Not sure if we want to report it
> to them? Can we run the autobuilders on the older kernel for now until
> they hopefully fix it?
>

Centos 8 will be discontinued in just over 6 months  (
https://www.centos.org/centos-linux/)
so I think at least one of the centos 8 workers should be updated to centos
stream 8
(https://www.centos.org/centos-stream/ - includes instructions) and take it
from there.

Alex

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#152808): 
https://lists.openembedded.org/g/openembedded-core/message/152808
Mute This Topic: https://lists.openembedded.org/mt/83304703/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] overlayfs.bbclass: generate overlayfs mount units

2021-06-09 Thread Andrei Gherzan 
Hi,

On Thu, 3 Jun 2021, at 15:21, Vyacheslav Yurkov wrote:
> It's often desired in Embedded System design to have a read-only rootfs.
> But a lot of different applications might want to have a read-write access
> to some parts of a filesystem. It can be especially useful when your update
> mechanism overwrites the whole rootfs, but you want your application data
> to be preserved between updates. This class provides a way to achieve that
> by means of overlayfs and at the same time keeping the base rootfs read-only.

I was looking into something like this lately. There are actually two kinds of 
write access - volatile (tmpfs) and persistent (to disk). So my approach would 
have been to use bind mounts from a tmpfs/ext4 based on configuration per 
recipe. Is there any advantage to working with overlayfs in this case? The main 
idea is to have state that doesn't come from the ro part of the OS because 
otherwise, updates will be shadowed by the overlayfs. So I fail to see the 
advantage of using a set of overlayfs mounts instead of bind mounts. At least 
with bind mounts, it will always shadow the rootfs bits so you can catch early 
this case.

Depending on your use case, most of the times, you'd want this "state" setup 
happening pre init (in initramfs, for example), especially if you want to 
handle persistent systemd logging or machine id, etc.

-- 
Andrei Gherzan 
gpg: rsa4096/D4D94F67AD0E9640

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#152807): 
https://lists.openembedded.org/g/openembedded-core/message/152807
Mute This Topic: https://lists.openembedded.org/mt/83284453/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 04/10] cmake: update 3.20.2 -> 3.20.3

2021-06-09 Thread Richard Purdie 
On Tue, 2021-06-08 at 20:15 +0200, Alexander Kanavin wrote:
> I can confirm that the previous kernel behaves correctly:
> utimensat_time64(AT_FDCWD, 
> "../install/usr/local/lib/cmake/assimp-4.1/assimp-config.cmake",
> [{tv_sec=1623176017, tv_nsec=6290007298941124608}, {tv_sec=1622966579, 
> tv_nsec=17838646317425885184}], 0) = -1
> ENOSYS (Function not implemented)
> utimensat(AT_FDCWD, 
> "../install/usr/local/lib/cmake/assimp-4.1/assimp-config.cmake", 
> [{tv_sec=1623176017,
> tv_nsec=0} /* 2021-06-08T18:13:37+ */, {tv_sec=1622966579, tv_nsec=0} /* 
> 2021-06-06T08:02:59+ */], 0)
> = 0
> 
> Does look like a botched backport of time64 syscalls to me.
> 
> Alex
> 
> On Tue, 8 Jun 2021 at 17:40, Michael Halstead  
> wrote:
> > I've rebooted centos8-ty-1 using the previous 4.18.0-240.15.1.el8_3.x86_64 
> > kernel and kept it in the pool.
> > I've paused centos8-ty-2 so it won't interfere with builds and left it at 
> > the current 4.18.0-
> > 305.3.1.el8.x86_64 kernel for testing. 

Thanks Michael and Alex. We can therefore pretty safely say that something was 
broken between the 240 and 305 of the centos8 kernel for the 32 bit syscall
utimensat syscalls.

I did poke around https://github.com/kernelim/linux/tree/centos8 which does
have a kernel diff but it is huge and you have to clone the repo to get it.

git show a3342908613ba72a84f652ca7a56c3e2113bda12 | grep sys_utimensat -C 40

shows they did add the syscalls in that kernel.

So this does look to be a RedHat issue. Not sure if we want to report it
to them? Can we run the autobuilders on the older kernel for now until
they hopefully fix it?

Cheers,

Richard





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#152806): 
https://lists.openembedded.org/g/openembedded-core/message/152806
Mute This Topic: https://lists.openembedded.org/mt/83304703/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH][hardknott 2/2] bind: 9.16.12 -> 9.16.16

2021-06-09 Thread Lee Chee Yang 
From: Lee Chee Yang 

updates include fix for
CVE-2021-25214
CVE-2021-25215
CVE-2021-25216

release notes:
https://downloads.isc.org/isc/bind9/9.16.16/doc/arm/html/notes.html#notes-for-bind-9-16-16

Signed-off-by: Lee Chee Yang 
---
 .../0001-avoid-start-failure-with-bind-user.patch   | 0
 .../0001-named-lwresd-V-and-start-log-hide-build-options.patch  | 0
 .../bind-ensure-searching-for-json-headers-searches-sysr.patch  | 0
 .../bind/{bind-9.16.12 => bind-9.16.16}/bind9   | 0
 .../bind/{bind-9.16.12 => bind-9.16.16}/conf.patch  | 0
 .../bind/{bind-9.16.12 => bind-9.16.16}/generate-rndc-key.sh| 0
 .../init.d-add-support-for-read-only-rootfs.patch   | 0
 .../make-etc-initd-bind-stop-work.patch | 0
 .../bind/{bind-9.16.12 => bind-9.16.16}/named.service   | 0
 .../bind/{bind_9.16.12.bb => bind_9.16.16.bb}   | 2 +-
 10 files changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-connectivity/bind/{bind-9.16.12 => 
bind-9.16.16}/0001-avoid-start-failure-with-bind-user.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.16.12 => 
bind-9.16.16}/0001-named-lwresd-V-and-start-log-hide-build-options.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.16.12 => 
bind-9.16.16}/bind-ensure-searching-for-json-headers-searches-sysr.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.16.12 => bind-9.16.16}/bind9 
(100%)
 rename meta/recipes-connectivity/bind/{bind-9.16.12 => 
bind-9.16.16}/conf.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.16.12 => 
bind-9.16.16}/generate-rndc-key.sh (100%)
 rename meta/recipes-connectivity/bind/{bind-9.16.12 => 
bind-9.16.16}/init.d-add-support-for-read-only-rootfs.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.16.12 => 
bind-9.16.16}/make-etc-initd-bind-stop-work.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.16.12 => 
bind-9.16.16}/named.service (100%)
 rename meta/recipes-connectivity/bind/{bind_9.16.12.bb => bind_9.16.16.bb} 
(98%)

diff --git 
a/meta/recipes-connectivity/bind/bind-9.16.12/0001-avoid-start-failure-with-bind-user.patch
 
b/meta/recipes-connectivity/bind/bind-9.16.16/0001-avoid-start-failure-with-bind-user.patch
similarity index 100%
rename from 
meta/recipes-connectivity/bind/bind-9.16.12/0001-avoid-start-failure-with-bind-user.patch
rename to 
meta/recipes-connectivity/bind/bind-9.16.16/0001-avoid-start-failure-with-bind-user.patch
diff --git 
a/meta/recipes-connectivity/bind/bind-9.16.12/0001-named-lwresd-V-and-start-log-hide-build-options.patch
 
b/meta/recipes-connectivity/bind/bind-9.16.16/0001-named-lwresd-V-and-start-log-hide-build-options.patch
similarity index 100%
rename from 
meta/recipes-connectivity/bind/bind-9.16.12/0001-named-lwresd-V-and-start-log-hide-build-options.patch
rename to 
meta/recipes-connectivity/bind/bind-9.16.16/0001-named-lwresd-V-and-start-log-hide-build-options.patch
diff --git 
a/meta/recipes-connectivity/bind/bind-9.16.12/bind-ensure-searching-for-json-headers-searches-sysr.patch
 
b/meta/recipes-connectivity/bind/bind-9.16.16/bind-ensure-searching-for-json-headers-searches-sysr.patch
similarity index 100%
rename from 
meta/recipes-connectivity/bind/bind-9.16.12/bind-ensure-searching-for-json-headers-searches-sysr.patch
rename to 
meta/recipes-connectivity/bind/bind-9.16.16/bind-ensure-searching-for-json-headers-searches-sysr.patch
diff --git a/meta/recipes-connectivity/bind/bind-9.16.12/bind9 
b/meta/recipes-connectivity/bind/bind-9.16.16/bind9
similarity index 100%
rename from meta/recipes-connectivity/bind/bind-9.16.12/bind9
rename to meta/recipes-connectivity/bind/bind-9.16.16/bind9
diff --git a/meta/recipes-connectivity/bind/bind-9.16.12/conf.patch 
b/meta/recipes-connectivity/bind/bind-9.16.16/conf.patch
similarity index 100%
rename from meta/recipes-connectivity/bind/bind-9.16.12/conf.patch
rename to meta/recipes-connectivity/bind/bind-9.16.16/conf.patch
diff --git a/meta/recipes-connectivity/bind/bind-9.16.12/generate-rndc-key.sh 
b/meta/recipes-connectivity/bind/bind-9.16.16/generate-rndc-key.sh
similarity index 100%
rename from meta/recipes-connectivity/bind/bind-9.16.12/generate-rndc-key.sh
rename to meta/recipes-connectivity/bind/bind-9.16.16/generate-rndc-key.sh
diff --git 
a/meta/recipes-connectivity/bind/bind-9.16.12/init.d-add-support-for-read-only-rootfs.patch
 
b/meta/recipes-connectivity/bind/bind-9.16.16/init.d-add-support-for-read-only-rootfs.patch
similarity index 100%
rename from 
meta/recipes-connectivity/bind/bind-9.16.12/init.d-add-support-for-read-only-rootfs.patch
rename to 
meta/recipes-connectivity/bind/bind-9.16.16/init.d-add-support-for-read-only-rootfs.patch
diff --git 
a/meta/recipes-connectivity/bind/bind-9.16.12/make-etc-initd-bind-stop-work.patch
 
b/meta/recipes-connectivity/bind/bind-9.16.16/make-etc-initd-bind-stop-work.patch
similarity index 100%
rename from 
meta/recipes-connectivity/bind/bind-9.16.12/make-etc-initd-bind-sto

[OE-core] [PATCH][hardknott 1/2] python3: 3.9.4 -> 3.9.5

2021-06-09 Thread Lee Chee Yang 
From: Lee Chee Yang 

This fifth maintenance release of Python 3.9 include fix for CVE-2021-29921.

Signed-off-by: Lee Chee Yang 
---
 .../python/{python3_3.9.4.bb => python3_3.9.5.bb}   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/python/{python3_3.9.4.bb => python3_3.9.5.bb} 
(99%)

diff --git a/meta/recipes-devtools/python/python3_3.9.4.bb 
b/meta/recipes-devtools/python/python3_3.9.5.bb
similarity index 99%
rename from meta/recipes-devtools/python/python3_3.9.4.bb
rename to meta/recipes-devtools/python/python3_3.9.5.bb
index cb371ceed7..82177f4a18 100644
--- a/meta/recipes-devtools/python/python3_3.9.4.bb
+++ b/meta/recipes-devtools/python/python3_3.9.5.bb
@@ -38,7 +38,7 @@ SRC_URI_append_class-native = " \
file://12-distutils-prefix-is-inside-staging-area.patch \
file://0001-Don-t-search-system-for-headers-libraries.patch \
"
-SRC_URI[sha256sum] = 
"4b0e6644a76f8df864ae24ac500a51bbf68bd098f6a173e27d3b61cdca9aa134"
+SRC_URI[sha256sum] = 
"0c5a140665436ec3dbfbb79e2dfb6d192655f26ef4a29aeffcb6d1820d716d83"
 
 # exclude pre-releases for both python 2.x and 3.x
 UPSTREAM_CHECK_REGEX = "[Pp]ython-(?P\d+(\.\d+)+).tar"
-- 
2.17.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#152804): 
https://lists.openembedded.org/g/openembedded-core/message/152804
Mute This Topic: https://lists.openembedded.org/mt/83416840/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH][dunfell 1/3] gstreamer-plugins-good: fix CVE-2021-3497 CVE-2021-3498

2021-06-09 Thread Lee Chee Yang 
From: Lee Chee Yang 

Signed-off-by: Lee Chee Yang 
---
 .../CVE-2021-3497.patch   | 207 ++
 .../CVE-2021-3498.patch   |  44 
 .../gstreamer1.0-plugins-good_1.16.3.bb   |   2 +
 3 files changed, 253 insertions(+)
 create mode 100644 
meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good/CVE-2021-3497.patch
 create mode 100644 
meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good/CVE-2021-3498.patch

diff --git 
a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good/CVE-2021-3497.patch
 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good/CVE-2021-3497.patch
new file mode 100644
index 00..81f7c59a7b
--- /dev/null
+++ 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good/CVE-2021-3497.patch
@@ -0,0 +1,207 @@
+From 9181191511f9c0be6a89c98b311f49d66bd46dc3 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Sebastian=20Dr=C3=B6ge?= 
+Date: Thu, 4 Mar 2021 13:05:19 +0200
+Subject: [PATCH] matroskademux: Fix extraction of multichannel WavPack
+
+The old code had a couple of issues that all lead to potential memory
+safety bugs.
+
+  - Use a constant for the Wavpack4Header size instead of using sizeof.
+It's written out into the data and not from the struct and who knows
+what special alignment/padding requirements some C compilers have.
+  - gst_buffer_set_size() does not realloc the buffer when setting a
+bigger size than allocated, it only allows growing up to the maximum
+allocated size. Instead use a GstAdapter to collect all the blocks
+and take out everything at once in the end.
+  - Check that enough data is actually available in the input and
+otherwise handle it an error in all cases instead of silently
+ignoring it.
+
+Among other things this fixes out of bounds writes because the code
+assumed gst_buffer_set_size() can grow the buffer and simply wrote after
+the end of the buffer.
+
+Thanks to Natalie Silvanovich for reporting.
+
+Fixes https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/-/issues/859
+
+Part-of: 

+
+Upstream-Status: Backport
+https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/-/commit/9181191511f9c0be6a89c98b311f49d66bd46dc3?merge_request_iid=903
+CVE: CVE-2021-3497
+Signed-off-by: Chee Yang Lee 
+
+---
+ gst/matroska/matroska-demux.c | 99 +++
+ gst/matroska/matroska-ids.h   |  2 +
+ 2 files changed, 55 insertions(+), 46 deletions(-)
+
+diff --git a/gst/matroska/matroska-demux.c b/gst/matroska/matroska-demux.c
+index 467815986..0e47ee7b5 100644
+--- a/gst/matroska/matroska-demux.c
 b/gst/matroska/matroska-demux.c
+@@ -3851,6 +3851,12 @@ gst_matroska_demux_add_wvpk_header (GstElement * 
element,
+ guint32 block_samples, tmp;
+ gsize size = gst_buffer_get_size (*buf);
+ 
++if (size < 4) {
++  GST_ERROR_OBJECT (element, "Too small wavpack buffer");
++  gst_buffer_unmap (*buf, &map);
++  return GST_FLOW_ERROR;
++}
++
+ gst_buffer_extract (*buf, 0, &tmp, sizeof (guint32));
+ block_samples = GUINT32_FROM_LE (tmp);
+ /* we need to reconstruct the header of the wavpack block */
+@@ -3858,10 +3864,10 @@ gst_matroska_demux_add_wvpk_header (GstElement * 
element,
+ /* -20 because ck_size is the size of the wavpack block -8
+  * and lace_size is the size of the wavpack block + 12
+  * (the three guint32 of the header that already are in the buffer) */
+-wvh.ck_size = size + sizeof (Wavpack4Header) - 20;
++wvh.ck_size = size + WAVPACK4_HEADER_SIZE - 20;
+ 
+ /* block_samples, flags and crc are already in the buffer */
+-newbuf = gst_buffer_new_allocate (NULL, sizeof (Wavpack4Header) - 12, 
NULL);
++newbuf = gst_buffer_new_allocate (NULL, WAVPACK4_HEADER_SIZE - 12, NULL);
+ 
+ gst_buffer_map (newbuf, &outmap, GST_MAP_WRITE);
+ data = outmap.data;
+@@ -3886,9 +3892,11 @@ gst_matroska_demux_add_wvpk_header (GstElement * 
element,
+ audiocontext->wvpk_block_index += block_samples;
+   } else {
+ guint8 *outdata = NULL;
+-guint outpos = 0;
+-gsize buf_size, size, out_size = 0;
++gsize buf_size, size;
+ guint32 block_samples, flags, crc, blocksize;
++GstAdapter *adapter;
++
++adapter = gst_adapter_new ();
+ 
+ gst_buffer_map (*buf, &map, GST_MAP_READ);
+ buf_data = map.data;
+@@ -3897,6 +3905,7 @@ gst_matroska_demux_add_wvpk_header (GstElement * element,
+ if (buf_size < 4) {
+   GST_ERROR_OBJECT (element, "Too small wavpack buffer");
+   gst_buffer_unmap (*buf, &map);
++  g_object_unref (adapter);
+   return GST_FLOW_ERROR;
+ }
+ 
+@@ -3918,59 +3927,57 @@ gst_matroska_demux_add_wvpk_header (GstElement * 
element,
+   data += 4;
+   size -= 4;
+ 
+-  if (blocksize == 0 || size < blocksize)
+-break;
+-
+-  g_assert ((newbuf == NULL) == (outdata == NULL));
++  if (blocksize == 0 ||

[OE-core] [PATCH][dunfell 3/3] ruby: 2.7.1 -> 2.7.3

2021-06-09 Thread Lee Chee Yang 
From: Lee Chee Yang 

This release includes security fixes.

CVE-2021-28965: XML round-trip vulnerability in REXML
CVE-2021-28966: Path traversal in Tempfile on Windows

CVE-2020-25613 fixed in 2.7.2, do drop the patch

release notes for 2.7.2 and 2.7.3
https://www.ruby-lang.org/en/news/2020/10/02/ruby-2-7-2-released/
https://www.ruby-lang.org/en/news/2021/04/05/ruby-2-7-3-released/

Signed-off-by: Lee Chee Yang 
---
 .../ruby/ruby/CVE-2020-25613.patch| 40 ---
 .../ruby/{ruby_2.7.1.bb => ruby_2.7.3.bb} |  5 +--
 2 files changed, 2 insertions(+), 43 deletions(-)
 delete mode 100644 meta/recipes-devtools/ruby/ruby/CVE-2020-25613.patch
 rename meta/recipes-devtools/ruby/{ruby_2.7.1.bb => ruby_2.7.3.bb} (94%)

diff --git a/meta/recipes-devtools/ruby/ruby/CVE-2020-25613.patch 
b/meta/recipes-devtools/ruby/ruby/CVE-2020-25613.patch
deleted file mode 100644
index 1abcb7547e..00
--- a/meta/recipes-devtools/ruby/ruby/CVE-2020-25613.patch
+++ /dev/null
@@ -1,40 +0,0 @@
-From 8946bb38b4d87549f0d99ed73c62c41933f97cc7 Mon Sep 17 00:00:00 2001
-From: Yusuke Endoh 
-Date: Tue, 29 Sep 2020 13:15:58 +0900
-Subject: [PATCH] Make it more strict to interpret some headers
-
-Some regexps were too tolerant.
-
-Upstream-Status: Backport
-[https://github.com/ruby/webrick/commit/8946bb38b4d87549f0d99ed73c62c41933f97cc7]
-CVE: CVE-2020-25613
-Signed-off-by: Chee Yang Lee 

- lib/webrick/httprequest.rb | 6 +++---
- 1 file changed, 3 insertions(+), 3 deletions(-)
-
-diff --git a/lib/webrick/httprequest.rb b/lib/webrick/httprequest.rb
-index 294bd91..d34eac7 100644
 a/lib/webrick/httprequest.rb
-+++ b/lib/webrick/httprequest.rb
-@@ -227,9 +227,9 @@ def parse(socket=nil)
- raise HTTPStatus::BadRequest, "bad URI `#{@unparsed_uri}'."
-   end
- 
--  if /close/io =~ self["connection"]
-+  if /\Aclose\z/io =~ self["connection"]
- @keep_alive = false
--  elsif /keep-alive/io =~ self["connection"]
-+  elsif /\Akeep-alive\z/io =~ self["connection"]
- @keep_alive = true
-   elsif @http_version < "1.1"
- @keep_alive = false
-@@ -508,7 +508,7 @@ def read_body(socket, block)
-   return unless socket
-   if tc = self['transfer-encoding']
- case tc
--when /chunked/io then read_chunked(socket, block)
-+when /\Achunked\z/io then read_chunked(socket, block)
- else raise HTTPStatus::NotImplemented, "Transfer-Encoding: #{tc}."
- end
-   elsif self['content-length'] || @remaining_size
diff --git a/meta/recipes-devtools/ruby/ruby_2.7.1.bb 
b/meta/recipes-devtools/ruby/ruby_2.7.3.bb
similarity index 94%
rename from meta/recipes-devtools/ruby/ruby_2.7.1.bb
rename to meta/recipes-devtools/ruby/ruby_2.7.3.bb
index a6c65e887b..318b9acdae 100644
--- a/meta/recipes-devtools/ruby/ruby_2.7.1.bb
+++ b/meta/recipes-devtools/ruby/ruby_2.7.3.bb
@@ -6,12 +6,11 @@ SRC_URI += " \
file://remove_has_include_macros.patch \
file://run-ptest \

file://0001-Modify-shebang-of-libexec-y2racc-and-libexec-racc2y.patch \
-   file://CVE-2020-25613.patch \

file://0001-template-Makefile.in-do-not-write-host-cross-cc-item.patch \
"
 
-SRC_URI[md5sum] = "debb9c325bf65021214451660f46e909"
-SRC_URI[sha256sum] = 
"d418483bdd576c1370571121a6eb24582116db0b7bb2005e90e250eae418"
+SRC_URI[md5sum] = "72ef97685008981de3ddb748d0dab31f"
+SRC_URI[sha256sum] = 
"8925a95e31d8f2c81749025a52a544ea1d05dad18794e6828709268b92e55338"
 
 PACKAGECONFIG ??= ""
 PACKAGECONFIG += "${@bb.utils.filter('DISTRO_FEATURES', 'ipv6', d)}"
-- 
2.17.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#152803): 
https://lists.openembedded.org/g/openembedded-core/message/152803
Mute This Topic: https://lists.openembedded.org/mt/83416195/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH][dunfell 2/3] bind: 9.11.22 -> 9.11.32

2021-06-09 Thread Lee Chee Yang 
From: Lee Chee Yang 

updates include fixes for
CVE-2021-25214
CVE-2021-25215
CVE-2021-25216

CVE-2020-8625 fixed in 9.11.28, so drop that patch

Signed-off-by: Lee Chee Yang 

tmp

Signed-off-by: Lee Chee Yang 
---
 .../bind/bind/CVE-2020-8625.patch   | 17 -
 .../bind/{bind_9.11.22.bb => bind_9.11.32.bb}   |  5 ++---
 2 files changed, 2 insertions(+), 20 deletions(-)
 delete mode 100644 meta/recipes-connectivity/bind/bind/CVE-2020-8625.patch
 rename meta/recipes-connectivity/bind/{bind_9.11.22.bb => bind_9.11.32.bb} 
(96%)

diff --git a/meta/recipes-connectivity/bind/bind/CVE-2020-8625.patch 
b/meta/recipes-connectivity/bind/bind/CVE-2020-8625.patch
deleted file mode 100644
index 9078f2448e..00
--- a/meta/recipes-connectivity/bind/bind/CVE-2020-8625.patch
+++ /dev/null
@@ -1,17 +0,0 @@
-Upstream-Status: Backporting 
[https://downloads.isc.org/isc/bind9/9.16.12/patches/CVE-2020-8625.patch]
-CVE: CVE-2020-8625
-Signed-off-by: Minjae Kim 
-
-diff --git a/lib/dns/spnego.c b/lib/dns/spnego.c
-index e61d1c600f2..753dc8049fa 100644
 a/lib/dns/spnego.c
-+++ b/lib/dns/spnego.c
-@@ -848,7 +848,7 @@ der_get_oid(const unsigned char *p, size_t len, oid *data, 
size_t *size) {
-   return (ASN1_OVERRUN);
-   }
- 
--  data->components = malloc(len * sizeof(*data->components));
-+  data->components = malloc((len + 1) * sizeof(*data->components));
-   if (data->components == NULL) {
-   return (ENOMEM);
-   }
diff --git a/meta/recipes-connectivity/bind/bind_9.11.22.bb 
b/meta/recipes-connectivity/bind/bind_9.11.32.bb
similarity index 96%
rename from meta/recipes-connectivity/bind/bind_9.11.22.bb
rename to meta/recipes-connectivity/bind/bind_9.11.32.bb
index 5598ba976d..9feebe5ae2 100644
--- a/meta/recipes-connectivity/bind/bind_9.11.22.bb
+++ b/meta/recipes-connectivity/bind/bind_9.11.32.bb
@@ -4,7 +4,7 @@ DESCRIPTION = "BIND 9 provides a full-featured Domain Name 
Server system"
 SECTION = "console/network"
 
 LICENSE = "ISC & BSD"
-LIC_FILES_CHKSUM = "file://COPYRIGHT;md5=bf39058a7f64b2a934ce14dc9ec1dd45"
+LIC_FILES_CHKSUM = "file://COPYRIGHT;md5=b88e7ca5f21908e1b2720169f6807cf6"
 
 DEPENDS = "openssl libcap zlib"
 
@@ -19,10 +19,9 @@ SRC_URI = 
"https://ftp.isc.org/isc/bind9/${PV}/${BPN}-${PV}.tar.gz \
file://0001-configure.in-remove-useless-L-use_openssl-lib.patch \
file://0001-named-lwresd-V-and-start-log-hide-build-options.patch \
file://0001-avoid-start-failure-with-bind-user.patch \
-   file://CVE-2020-8625.patch \
"
 
-SRC_URI[sha256sum] = 
"afc6d8015006f1cabf699ff19f517bb8fd9c1811e5231f26baf51c3550262ac9"
+SRC_URI[sha256sum] = 
"cbf8cb4b74dd1452d97c3a2a8c625ea346df8516b4b3508ef07443121a591342"
 
 UPSTREAM_CHECK_URI = "https://ftp.isc.org/isc/bind9/";
 # stay at 9.11 until 9.16, from 9.16 follow the ESV versions divisible by 4
-- 
2.17.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#152802): 
https://lists.openembedded.org/g/openembedded-core/message/152802
Mute This Topic: https://lists.openembedded.org/mt/83416194/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [V2][PATCH] libjpeg-turbo: fix do_compile error on armv5

2021-06-09 Thread William A. Kennington III via lists.openembedded.org 
Btw, I'm hoping upstream will fix this for all arm
https://github.com/libjpeg-turbo/libjpeg-turbo/issues/523

On Wed, Jun 9, 2021 at 12:32 AM Changqing Li  wrote:
>
> From: Changqing Li 
>
> fix below error:
> /include/arm_neon.h:31:2: error: #error "NEON intrinsics not available with 
> the soft-float ABI. Please use -mfloat-abi=softfp or -mfloat-abi=hard"
> 31 | #error "NEON intrinsics not available with the soft-float ABI. Please 
> use -mfloat-abi=softfp or -mfloat-abi=hard"
>
> Neon is not supported by armv5, disable the simd extension build.
>
> Signed-off-by: Changqing Li 
> ---
>  meta/recipes-graphics/jpeg/libjpeg-turbo_2.1.0.bb | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/meta/recipes-graphics/jpeg/libjpeg-turbo_2.1.0.bb 
> b/meta/recipes-graphics/jpeg/libjpeg-turbo_2.1.0.bb
> index 7f91cc02ac..da21971113 100644
> --- a/meta/recipes-graphics/jpeg/libjpeg-turbo_2.1.0.bb
> +++ b/meta/recipes-graphics/jpeg/libjpeg-turbo_2.1.0.bb
> @@ -40,6 +40,8 @@ EXTRA_OECMAKE_append_class-target = " 
> ${@bb.utils.contains("TUNE_FEATURES", "mx3
>  # Work around missing non-floating point ABI support in MIPS
>  EXTRA_OECMAKE_append_class-target = " ${@bb.utils.contains("MIPSPKGSFX_FPU", 
> "-nf", "-DWITH_SIMD=False", "", d)}"
>
> +EXTRA_OECMAKE_append_class-target = " ${@ ('') if 
> (d.getVar('TUNE_CCARGS_MFPU') != '') else '-DWITH_SIMD=False'}"
> +
>  # Provide a workaround if Altivec unit is not present in PPC
>  EXTRA_OECMAKE_append_class-target_powerpc = " 
> ${@bb.utils.contains("TUNE_FEATURES", "altivec", "", "-DWITH_SIMD=False", d)}"
>  EXTRA_OECMAKE_append_class-target_powerpc64 = " 
> ${@bb.utils.contains("TUNE_FEATURES", "altivec", "", "-DWITH_SIMD=False", d)}"
> --
> 2.17.1
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#152800): 
https://lists.openembedded.org/g/openembedded-core/message/152800
Mute This Topic: https://lists.openembedded.org/mt/83415559/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [V2][PATCH] libjpeg-turbo: fix do_compile error on armv5

2021-06-09 Thread Changqing Li 
From: Changqing Li 

fix below error:
/include/arm_neon.h:31:2: error: #error "NEON intrinsics not available with the 
soft-float ABI. Please use -mfloat-abi=softfp or -mfloat-abi=hard"
31 | #error "NEON intrinsics not available with the soft-float ABI. Please use 
-mfloat-abi=softfp or -mfloat-abi=hard"

Neon is not supported by armv5, disable the simd extension build.

Signed-off-by: Changqing Li 
---
 meta/recipes-graphics/jpeg/libjpeg-turbo_2.1.0.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-graphics/jpeg/libjpeg-turbo_2.1.0.bb 
b/meta/recipes-graphics/jpeg/libjpeg-turbo_2.1.0.bb
index 7f91cc02ac..da21971113 100644
--- a/meta/recipes-graphics/jpeg/libjpeg-turbo_2.1.0.bb
+++ b/meta/recipes-graphics/jpeg/libjpeg-turbo_2.1.0.bb
@@ -40,6 +40,8 @@ EXTRA_OECMAKE_append_class-target = " 
${@bb.utils.contains("TUNE_FEATURES", "mx3
 # Work around missing non-floating point ABI support in MIPS
 EXTRA_OECMAKE_append_class-target = " ${@bb.utils.contains("MIPSPKGSFX_FPU", 
"-nf", "-DWITH_SIMD=False", "", d)}"
 
+EXTRA_OECMAKE_append_class-target = " ${@ ('') if 
(d.getVar('TUNE_CCARGS_MFPU') != '') else '-DWITH_SIMD=False'}"
+
 # Provide a workaround if Altivec unit is not present in PPC
 EXTRA_OECMAKE_append_class-target_powerpc = " 
${@bb.utils.contains("TUNE_FEATURES", "altivec", "", "-DWITH_SIMD=False", d)}"
 EXTRA_OECMAKE_append_class-target_powerpc64 = " 
${@bb.utils.contains("TUNE_FEATURES", "altivec", "", "-DWITH_SIMD=False", d)}"
-- 
2.17.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#152799): 
https://lists.openembedded.org/g/openembedded-core/message/152799
Mute This Topic: https://lists.openembedded.org/mt/83415559/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-