[OE-core] [meta-oe][PATCH] bitwise: Upgrade 0.43 -> 0.50

[Ramon Fried]

Signed-off-by: Ramon Fried 
---
 .../bitwise/{bitwise_0.43.bb => bitwise_0.50.bb}| 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta-oe/recipes-extended/bitwise/{bitwise_0.43.bb => bitwise_0.50.bb} 
(91%)

diff --git a/meta-oe/recipes-extended/bitwise/bitwise_0.43.bb 
b/meta-oe/recipes-extended/bitwise/bitwise_0.50.bb
similarity index 91%
rename from meta-oe/recipes-extended/bitwise/bitwise_0.43.bb
rename to meta-oe/recipes-extended/bitwise/bitwise_0.50.bb
index 3a9943916..5cd20c5b1 100644
--- a/meta-oe/recipes-extended/bitwise/bitwise_0.43.bb
+++ b/meta-oe/recipes-extended/bitwise/bitwise_0.50.bb
@@ -15,7 +15,7 @@ SRC_URI = 
"https://github.com/mellowcandle/bitwise/releases/download/v${PV}/bitw
file://run-ptest \
file://ptest.out.expected \
"
-SRC_URI[sha256sum] = 
"f524f794188a10defc4df673d8cf0b3739f93e58e93aff0cdb8a99fbdcca2ffb"
+SRC_URI[sha256sum] = 
"806271fa5bf31de0600315e8720004a8f529954480e991ca84a9868dc1cae97e"
 
 UPSTREAM_CHECK_URI = "https://github.com/mellowcandle/bitwise/releases";
 
-- 
2.41.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184714): 
https://lists.openembedded.org/g/openembedded-core/message/184714
Mute This Topic: https://lists.openembedded.org/mt/100291403/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] make-mod-scripts doesn't know KERNEL_LOCALVERSION

[Bruce Ashfield]

On Thu, Jul 20, 2023 at 4:12 PM Bruce Ashfield via
lists.openembedded.org
 wrote:
>
> On Thu, Jul 20, 2023 at 9:19 AM Bruce Ashfield via
> lists.openembedded.org
>  wrote:
> >
> > On Thu, Jul 20, 2023 at 9:16 AM Petr Gotthard
> >  wrote:
> > >
> > > > My question was about CONFIG_LOCALVERSION_AUTO being something that you
> > > > changed after the first issue popped up (I understood what it was 
> > > > changing from
> > > > your first description) I can't clearly see if you turned it on in 
> > > > response to the
> > > > breakage, but I'm assuming that the answer is yes.
> > >
> > > Oh, sorry for the consuion. Yes, I changed the CONFIG_LOCALVERSION_AUTO 
> > > only to reduce the number of suffixes.
> >
> > Ack'd. Thanks for confirming.
> >
> > I'm coming up with something that will keep 6.3+ working, and not
> > break older/existing recipes.
> >
>
> I have a fix under test. I'm just running into a bit of sstate
> oddities that I need to sort out!

The first iteration of the fix is on the list.

As you mentioned and Richard reminded me, rather than doing some
fragile logic to make the variable consistent, I've followed the lead of
the abiversion files and we are now saving the localversion info as
well.

Bruce

>
> Bruce
>
>
> > Cheers,
> >
> > Bruce
> >
> > >
> > >
> > > Cheers,
> > > Petr
> >
> >
> >
> > --
> > - Thou shalt not follow the NULL pointer, for chaos and madness await
> > thee at its end
> > - "Use the force Harry" - Gandalf, Star Trek II
> >
> >
> >
>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end
> - "Use the force Harry" - Gandalf, Star Trek II
>
> 
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184713): 
https://lists.openembedded.org/g/openembedded-core/message/184713
Mute This Topic: https://lists.openembedded.org/mt/100240236/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] kernel: make LOCALVERSION consistent between recipes

[Bruce Ashfield]

From: Bruce Ashfield 

The initial fix for localversion setting in 6.3+ broke older
recipes and also broke recipes setting localversion in a kernel
recipe, as make-mod-scripts (and other locations) can trigger
a regeneration of files and don't have access to the variable.

Moving the setting of this variable to the global namespace
doesn't make sense, so we follow the example of the kernel-abiversion
and save a kernel-localversion to the build artifacts.

Recipes that may regenerate scripts/dynamic files, must
depend on the do_shared_workedir of the kernel and use the helper
function to read the file storing the localversion.

Signed-off-by: Bruce Ashfield 
---

Richard,

This is the first iteration of the localversion fix. I tested this
against 6.1 and 6.4, both with and without a KERNEL_LOCALVERSION
set, and I was able to build and load external modules in all
configurations.

I made the export of LOCALVERSION broad enough that any kernel
build component that needs to regenerate scripts should pick up
the value and we'll have a consistent localversion.

This of course follows the lead of what we did with abiversion,
but is a bit simpler, since we don't need it for depmod, etc.

I've noticed a few issues with the way that the -abiversion and
-localversion files are handled with respect to package names,
as well as how on-target module compilation can have issues
outside of a .config based localversion .. but those are existing
issues and they can be addressed once we've fixed up module
loading when LOCALVERSION is set.

I say "first iteration", as I'm sure there's some sstate or
corner case I missed, but I have broad enough testing now that
it needs more eyes and soaking.

Bruce


 meta/classes-recipe/kernel-arch.bbclass|  8 
 meta/classes-recipe/kernel.bbclass | 14 ++
 meta/classes-recipe/kernelsrc.bbclass  |  1 +
 meta/classes-recipe/linux-kernel-base.bbclass  | 11 +++
 meta/classes-recipe/module-base.bbclass|  1 +
 .../make-mod-scripts/make-mod-scripts_1.0.bb   |  3 +++
 6 files changed, 30 insertions(+), 8 deletions(-)

diff --git a/meta/classes-recipe/kernel-arch.bbclass 
b/meta/classes-recipe/kernel-arch.bbclass
index df4884b6c4..b0db99faa3 100644
--- a/meta/classes-recipe/kernel-arch.bbclass
+++ b/meta/classes-recipe/kernel-arch.bbclass
@@ -79,11 +79,3 @@ KERNEL_AR = "${CCACHE}${HOST_PREFIX}ar 
${HOST_AR_KERNEL_ARCH}"
 KERNEL_OBJCOPY = "${CCACHE}${HOST_PREFIX}objcopy ${HOST_OBJCOPY_KERNEL_ARCH}"
 KERNEL_STRIP = "${CCACHE}${HOST_PREFIX}strip ${HOST_STRIP_KERNEL_ARCH}"
 TOOLCHAIN ?= "gcc"
-
-# 6.3+ requires the variable LOCALVERSION to be set to not get a "+" in
-# the local version. Having it empty means nothing will be added, and any
-# value will be appended to the local kernel version. This replaces the
-# use of .scmversion file for setting a localversion without using
-# the CONFIG_LOCALVERSION option.
-KERNEL_LOCALVERSION ??= ""
-export LOCALVERSION ?= "${KERNEL_LOCALVERSION}"
diff --git a/meta/classes-recipe/kernel.bbclass 
b/meta/classes-recipe/kernel.bbclass
index b3865dcb0f..907cc4f61a 100644
--- a/meta/classes-recipe/kernel.bbclass
+++ b/meta/classes-recipe/kernel.bbclass
@@ -550,6 +550,7 @@ do_shared_workdir () {
#
 
echo "${KERNEL_VERSION}" > $kerneldir/${KERNEL_PACKAGE_NAME}-abiversion
+   echo "${KERNEL_LOCALVERSION}" > 
$kerneldir/${KERNEL_PACKAGE_NAME}-localversion
 
# Copy files required for module builds
cp System.map $kerneldir/System.map-${KERNEL_VERSION}
@@ -639,6 +640,19 @@ python check_oldest_kernel() {
 check_oldest_kernel[vardepsexclude] += "OLDEST_KERNEL KERNEL_VERSION"
 do_configure[prefuncs] += "check_oldest_kernel"
 
+KERNEL_LOCALVERSION ??= ""
+
+# 6.3+ requires the variable LOCALVERSION to be set to not get a "+" in
+# the local version. Having it empty means nothing will be added, and any
+# value will be appended to the local kernel version. This replaces the
+# use of .scmversion file for setting a localversion without using
+# the CONFIG_LOCALVERSION option.
+#
+# Note: This class saves the value of localversion to a file
+# so other recipes like make-mod-scripts can restore it via the
+# helper function get_kernellocalversion_file
+export LOCALVERSION="${KERNEL_LOCALVERSION}"
+
 kernel_do_configure() {
# fixes extra + in /lib/modules/2.6.37+
# $ scripts/setlocalversion . => +
diff --git a/meta/classes-recipe/kernelsrc.bbclass 
b/meta/classes-recipe/kernelsrc.bbclass
index a32882a5d2..ecb02dc9ed 100644
--- a/meta/classes-recipe/kernelsrc.bbclass
+++ b/meta/classes-recipe/kernelsrc.bbclass
@@ -11,6 +11,7 @@ do_patch[depends] += "virtual/kernel:do_shared_workdir"
 do_patch[noexec] = "1"
 do_package[depends] += "virtual/kernel:do_populate_sysroot"
 KERNEL_VERSION = "${@get_kernelversion_file("${STAGING_KERNEL_BUILDDIR}")}"
+LOCAL_VERSION = "${@get_kernellocalversion_file("${STAGING_KERNEL_BUILDDIR}")}"
 
 inherit linux-kernel-bas

ODP: [OE-Core][PATCH v7][master-next 1/5] package_ipk.bbclass: add support for ACLs and xattr

[Piotr Łobacz]

Alexandre, Is it possible for you to create a docker file or some image etc. 
with all commands from autobuilder which will re-create the failure and pass it 
to me?

Because can grope, find nothing and waste our time...

Cheers,
Piotr


Od: Alexandre Belloni 
Wysłane: sobota, 22 lipca 2023 00:01
Do: Piotr Łobacz 
DW: openembedded-core@lists.openembedded.org 

Temat: Re: [OE-Core][PATCH v7][master-next 1/5] package_ipk.bbclass: add 
support for ACLs and xattr

I confirm this still fails on the autobuilders:

This is a-full:
https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fautobuilder.yoctoproject.org%2Ftyphoon%2F%23%2Fbuilders%2F83%2Fbuilds%2F5631&data=05%7C01%7Cp.lobacz%40welotec.com%7C308b241fa77c483b937808db8a360827%7C25111a7f1d5a4c51a4ca7f8e44011b39%7C0%7C0%7C638255736894248112%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=YHOXoiEiIYhWMLP%2FvytWKdXpcSpTDfKzwf8MEyGzWQ0%3D&reserved=0

On 21/07/2023 14:07:19+0200, Piotr Łobacz wrote:
> Extend OPKGBUILDCMD variable, with additional parameters, depending
> on target distro features, in order to support ACLs and xattr.
>
> With fix pushed to the opkg-devel:
> https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fg%2Fopkg-devel%2Fc%2FdYNHrLjDwg8&data=05%7C01%7Cp.lobacz%40welotec.com%7C308b241fa77c483b937808db8a360827%7C25111a7f1d5a4c51a4ca7f8e44011b39%7C0%7C0%7C638255736894248112%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Hhix8F4A6m9r0tFljzmTUXwQdBUPeV6X8g4c0Nm%2Favw%3D&reserved=0
> opkg-build is able to create tar archives with ACLs and xattr.
>
> Signed-off-by: Piotr Łobacz 
> ---
>  meta/classes-global/package_ipk.bbclass | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes-global/package_ipk.bbclass 
> b/meta/classes-global/package_ipk.bbclass
> index b4b7bc9ac2..5e151be3cd 100644
> --- a/meta/classes-global/package_ipk.bbclass
> +++ b/meta/classes-global/package_ipk.bbclass
> @@ -15,7 +15,7 @@ IPKGCONF_SDK_TARGET = "${WORKDIR}/opkg-sdk-target.conf"
>  PKGWRITEDIRIPK = "${WORKDIR}/deploy-ipks"
>
>  # Program to be used to build opkg packages
> -OPKGBUILDCMD ??= 'opkg-build -Z xz -a "${XZ_DEFAULTS}"'
> +OPKGBUILDCMD ??= 'opkg-build -Z xz -a "${XZ_DEFAULTS}" 
> "${@bb.utils.contains('DISTRO_FEATURES', 'acl', '-A', '', d)}" 
> "${@bb.utils.contains('DISTRO_FEATURES', 'xattr', '-X', '', d)}"'
>
>  OPKG_ARGS += "--force_postinstall --prefer-arch-to-version"
>  OPKG_ARGS += "${@['', 
> '--no-install-recommends'][d.getVar("NO_RECOMMENDATIONS") == "1"]}"
> --
> 2.34.1
>

>
> 
>


--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbootlin.com%2F&data=05%7C01%7Cp.lobacz%40welotec.com%7C308b241fa77c483b937808db8a360827%7C25111a7f1d5a4c51a4ca7f8e44011b39%7C0%7C0%7C638255736894248112%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qcJ5Tbo%2BeuKHZTpYlA5WJWQUekULrpnkHDmNnRAvEqo%3D&reserved=0

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184711): 
https://lists.openembedded.org/g/openembedded-core/message/184711
Mute This Topic: https://lists.openembedded.org/mt/100287357/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 v7][master-next 1/5] package_ipk.bbclass: add support for ACLs and xattr

[Alexandre Belloni via lists.openembedded.org]

I confirm this still fails on the autobuilders:

This is a-full:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/5631

On 21/07/2023 14:07:19+0200, Piotr Łobacz wrote:
> Extend OPKGBUILDCMD variable, with additional parameters, depending
> on target distro features, in order to support ACLs and xattr.
> 
> With fix pushed to the opkg-devel:
> https://groups.google.com/g/opkg-devel/c/dYNHrLjDwg8
> opkg-build is able to create tar archives with ACLs and xattr.
> 
> Signed-off-by: Piotr Łobacz 
> ---
>  meta/classes-global/package_ipk.bbclass | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/classes-global/package_ipk.bbclass 
> b/meta/classes-global/package_ipk.bbclass
> index b4b7bc9ac2..5e151be3cd 100644
> --- a/meta/classes-global/package_ipk.bbclass
> +++ b/meta/classes-global/package_ipk.bbclass
> @@ -15,7 +15,7 @@ IPKGCONF_SDK_TARGET = "${WORKDIR}/opkg-sdk-target.conf"
>  PKGWRITEDIRIPK = "${WORKDIR}/deploy-ipks"
>  
>  # Program to be used to build opkg packages
> -OPKGBUILDCMD ??= 'opkg-build -Z xz -a "${XZ_DEFAULTS}"'
> +OPKGBUILDCMD ??= 'opkg-build -Z xz -a "${XZ_DEFAULTS}" 
> "${@bb.utils.contains('DISTRO_FEATURES', 'acl', '-A', '', d)}" 
> "${@bb.utils.contains('DISTRO_FEATURES', 'xattr', '-X', '', d)}"'
>  
>  OPKG_ARGS += "--force_postinstall --prefer-arch-to-version"
>  OPKG_ARGS += "${@['', 
> '--no-install-recommends'][d.getVar("NO_RECOMMENDATIONS") == "1"]}"
> -- 
> 2.34.1
> 

> 
> 
> 


-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

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

[OE-core][dunfell] openssl: fix intermittent openssl-ptest reproducibility issue

[Steve Sakoman]

Adds two missing key sorts in generation of unified_info

Backported from a similar (but more invasive)  patch in the 3.x source code:

https://github.com/openssl/openssl/commit/764cf5b26306a8712e8b3d41599c44dc5ed07a25]

Signed-off-by: Steve Sakoman 
---
 ...01-Configure-add-2-missing-key-sorts.patch | 38 +++
 .../openssl/openssl_1.1.1t.bb |  1 +
 2 files changed, 39 insertions(+)
 create mode 100644 
meta/recipes-connectivity/openssl/openssl/0001-Configure-add-2-missing-key-sorts.patch

diff --git 
a/meta/recipes-connectivity/openssl/openssl/0001-Configure-add-2-missing-key-sorts.patch
 
b/meta/recipes-connectivity/openssl/openssl/0001-Configure-add-2-missing-key-sorts.patch
new file mode 100644
index 00..e2a65d0998
--- /dev/null
+++ 
b/meta/recipes-connectivity/openssl/openssl/0001-Configure-add-2-missing-key-sorts.patch
@@ -0,0 +1,38 @@
+From 679ae2f72ef8cf37609cb0eff5de3b98aa85e395 Mon Sep 17 00:00:00 2001
+From: Steve Sakoman 
+Date: Thu, 20 Jul 2023 04:14:42 -1000
+Subject: [PATCH] Configure: add 2 missing key sorts in generation of 
unified_info
+
+Otherwise generation of this section in configdata.pm is not reproducible
+
+Signed-off-by: Steve Sakoman 
+Upstream-Status: Backport [adapted from 3.x commit 
https://github.com/openssl/openssl/commit/764cf5b26306a8712e8b3d41599c44dc5ed07a25]
+---
+ Configure | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/Configure b/Configure
+index 2a01746..8fc5a2c 100755
+--- a/Configure
 b/Configure
+@@ -2326,7 +2326,7 @@ EOF
+  "dso" => [ @{$unified_info{engines}} ],
+  "bin" => [ @{$unified_info{programs}} ],
+  "script" => [ @{$unified_info{scripts}} ] );
+-foreach my $type (keys %loopinfo) {
++foreach my $type (sort keys %loopinfo) {
+ foreach my $product (@{$loopinfo{$type}}) {
+ my %dirs = ();
+ my $pd = dirname($product);
+@@ -2347,7 +2347,7 @@ EOF
+ push @{$unified_info{dirinfo}->{$d}->{deps}}, $_
+ if $d ne $pd;
+ }
+-foreach (keys %dirs) {
++foreach (sort keys %dirs) {
+ push @{$unified_info{dirinfo}->{$_}->{products}->{$type}},
+ $product;
+ }
+-- 
+2.34.1
+
diff --git a/meta/recipes-connectivity/openssl/openssl_1.1.1t.bb 
b/meta/recipes-connectivity/openssl/openssl_1.1.1t.bb
index 75fc3c5c1a..eea8ef64af 100644
--- a/meta/recipes-connectivity/openssl/openssl_1.1.1t.bb
+++ b/meta/recipes-connectivity/openssl/openssl_1.1.1t.bb
@@ -18,6 +18,7 @@ SRC_URI = "http://www.openssl.org/source/openssl-${PV}.tar.gz 
\
file://afalg.patch \
file://reproducible.patch \
file://reproducibility.patch \
+   file://0001-Configure-add-2-missing-key-sorts.patch \
file://CVE-2023-0464.patch \
file://CVE-2023-0465.patch \
file://CVE-2023-0466.patch \
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184709): 
https://lists.openembedded.org/g/openembedded-core/message/184709
Mute This Topic: https://lists.openembedded.org/mt/100285135/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][kirkstone][PATCH 1/1] bind: fix CVE-2023-2911

[Steve Sakoman]

There is already a fix for this CVE in kirkstone:

https://git.openembedded.org/openembedded-core/commit/?h=kirkstone&id=08810d3fe6988ea821805eca16105b4632335654

Steve

On Thu, Jul 20, 2023 at 8:50 PM Urade, Yogita via lists.openembedded.org
 wrote:

> If the `recursive-clients` quota is reached on a BIND 9 resolver
> configured with both `stale-answer-enable yes;` and
> `stale-answer-client-timeout 0;`, a sequence of serve-stale-related
> lookups could cause `named` to loop and terminate unexpectedly due
> to a stack overflow.
> This issue affects BIND 9 versions 9.16.33 through 9.16.41, 9.18.7
> through 9.18.15, 9.16.33-S1 through 9.16.41-S1, and 9.18.11-S1
> through 9.18.15-S1.
>
> References:
> https://kb.isc.org/docs/cve-2023-2911
>
> https://downloads.isc.org/isc/bind9/9.18.16/doc/arm/html/notes.html#notes-for-bind-9-18-16
>
> Signed-off-by: Yogita Urade 
> ---
>  .../bind/bind-9.18.11/CVE-2023-2911.patch | 109 ++
>  .../recipes-connectivity/bind/bind_9.18.11.bb |   1 +
>  2 files changed, 110 insertions(+)
>  create mode 100644
> meta/recipes-connectivity/bind/bind-9.18.11/CVE-2023-2911.patch
>
> diff --git
> a/meta/recipes-connectivity/bind/bind-9.18.11/CVE-2023-2911.patch
> b/meta/recipes-connectivity/bind/bind-9.18.11/CVE-2023-2911.patch
> new file mode 100644
> index 00..729d13ee18
> --- /dev/null
> +++ b/meta/recipes-connectivity/bind/bind-9.18.11/CVE-2023-2911.patch
> @@ -0,0 +1,109 @@
> +From 2d6982985021ee354469a0fc380008d6c6fa8ae2 Mon Sep 17 00:00:00 2001
> +From: Michal Nowak 
> +Date: Thu, 20 Jul 2023 08:07:32 +
> +Subject: [PATCH] Merge branch
> '4089-confidential-stale-query-loop-bind-9.18'
> + into 'security-bind-9.18'
> +
> +[9.18][CVE-2023-2911] Fix stale-answer-client-timeout 0 crash
> +
> +See merge request isc-private/bind9!523
> +
> +CVE-2023-2911
> +
> +Upstream-Status: Backport [
> https://gitlab.isc.org/isc-projects/bind9/-/commit/2d6982985021ee354469a0fc380008d6c6fa8ae2
> ]
> +
> +Signed-off-by: Yogita Urade 
> +---
> + CHANGES|  7 +++
> + lib/ns/query.c | 29 +
> + 2 files changed, 28 insertions(+), 8 deletions(-)
> +
> +diff --git a/CHANGES b/CHANGES
> +index ca2f3a3..0e18f27 100644
> +--- a/CHANGES
>  b/CHANGES
> +@@ -1,3 +1,10 @@
> ++6192. [security]  A query that prioritizes stale data over lookup
> ++  triggers a fetch to refresh the stale data in
> cache.
> ++  If the fetch is aborted for exceeding the recursion
> ++  quota, it was possible for 'named' to enter an
> infinite
> ++  callback loop and crash due to stack overflow.
> This has
> ++  been fixed. (CVE-2023-2911) [GL #4089]
> ++
> +   --- 9.18.11 released ---
> +
> + 6067. [security]  Fix serve-stale crash when recursive clients soft
> quota
> +diff --git a/lib/ns/query.c b/lib/ns/query.c
> +index 0d2ba6b..7a812e6 100644
> +--- a/lib/ns/query.c
>  b/lib/ns/query.c
> +@@ -5824,6 +5824,7 @@ query_refresh_rrset(query_ctx_t *orig_qctx) {
> +   qctx.client->query.dboptions &= ~(DNS_DBFIND_STALETIMEOUT |
> + DNS_DBFIND_STALEOK |
> + DNS_DBFIND_STALEENABLED);
> ++  qctx.client->nodetach = false;
> +
> +   /*
> +* We'll need some resources...
> +@@ -6076,7 +6077,13 @@ query_lookup(query_ctx_t *qctx) {
> +   "%s stale answer used, an attempt
> to "
> +   "refresh the RRset will still be
> made",
> +   namebuf);
> ++
> +   qctx->refresh_rrset =
> STALE(qctx->rdataset);
> ++  /*
> ++   * If we are refreshing the RRSet, we must
> not
> ++   * detach from the client in query_send().
> ++   */
> ++  qctx->client->nodetach =
> qctx->refresh_rrset;
> +   ns_client_extendederror(
> +   qctx->client, ede,
> +   "stale data prioritized over
> lookup");
> +@@ -6503,7 +6510,7 @@ ns_query_recurse(ns_client_t *client,
> dns_rdatatype_t qtype, dns_name_t *qname,
> +   if (recparam_match(&client->query.recparam, qtype, qname,
> qdomain)) {
> +   ns_client_log(client, NS_LOGCATEGORY_CLIENT,
> NS_LOGMODULE_QUERY,
> + ISC_LOG_INFO, "recursion loop detected");
> +-  return (ISC_R_FAILURE);
> ++  return (ISC_R_ALREADYRUNNING);
> +   }
> +
> +   recparam_update(&client->query.recparam, qtype, qname, qdomain);
> +@@ -7620,10 +7627,21 @@ query_usestale(query_ctx_t *qctx, isc_result_t
> result) {
> +   return (false);
> +   }
> +
> +-  if (result == DNS_R_DUPLICATE || result == DNS_R_DROP) {
> +

[OE-core] [mickledore][PATCH] go: fix CVE-2023-24531

[Sakib Sajal via lists.openembedded.org]

Backport required commits to fix CVE-2023-24531.

Signed-off-by: Sakib Sajal 
---
 meta/recipes-devtools/go/go-1.20.5.inc|   2 +
 .../go/go/CVE-2023-24531_1.patch  | 266 ++
 .../go/go/CVE-2023-24531_2.patch  |  47 
 3 files changed, 315 insertions(+)
 create mode 100644 meta/recipes-devtools/go/go/CVE-2023-24531_1.patch
 create mode 100644 meta/recipes-devtools/go/go/CVE-2023-24531_2.patch

diff --git a/meta/recipes-devtools/go/go-1.20.5.inc 
b/meta/recipes-devtools/go/go-1.20.5.inc
index 4e4e57d5cb..9cc79a8073 100644
--- a/meta/recipes-devtools/go/go-1.20.5.inc
+++ b/meta/recipes-devtools/go/go-1.20.5.inc
@@ -14,5 +14,7 @@ SRC_URI += "\
 file://0007-exec.go-do-not-write-linker-flags-into-buildids.patch \
 file://0008-src-cmd-dist-buildgo.go-do-not-hardcode-host-compile.patch \
 file://0009-go-Filter-build-paths-on-staticly-linked-arches.patch \
+file://CVE-2023-24531_1.patch \
+file://CVE-2023-24531_2.patch \
 "
 SRC_URI[main.sha256sum] = 
"9a15c133ba2cfafe79652f4815b62e7cfc267f68df1b9454c6ab2a3ca8b96a88"
diff --git a/meta/recipes-devtools/go/go/CVE-2023-24531_1.patch 
b/meta/recipes-devtools/go/go/CVE-2023-24531_1.patch
new file mode 100644
index 00..9de701b64b
--- /dev/null
+++ b/meta/recipes-devtools/go/go/CVE-2023-24531_1.patch
@@ -0,0 +1,266 @@
+From c5463ec922a57d8b175c6639186ba9cbe15e6bc1 Mon Sep 17 00:00:00 2001
+From: Michael Matloob 
+Date: Mon, 24 Apr 2023 16:57:28 -0400
+Subject: [PATCH 1/2] cmd/go: sanitize go env outputs
+
+go env, without any arguments, outputs the environment variables in
+the form of a script that can be run on the host OS. On Unix, single
+quote the strings and place single quotes themselves outside the
+single quoted strings. On windows use the set "var=val" syntax with
+the quote starting before the variable.
+
+Fixes #58508
+
+Change-Id: Iecd379a4af7285ea9b2024f0202250c74fd9a2bd
+Reviewed-on: https://go-review.googlesource.com/c/go/+/488375
+TryBot-Result: Gopher Robot 
+Reviewed-by: Michael Matloob 
+Reviewed-by: Damien Neil 
+Run-TryBot: Michael Matloob 
+Reviewed-by: Bryan Mills 
+Reviewed-by: Quim Muntal 
+
+CVE: CVE-2023-24531
+Upstream-Status: Backport [f379e78951a405e7e99a60fb231eeedbf976c108]
+
+Signed-off-by: Sakib Sajal 
+---
+ src/cmd/go/internal/envcmd/env.go   | 60 -
+ src/cmd/go/internal/envcmd/env_test.go  | 94 +
+ src/cmd/go/testdata/script/env_sanitize.txt |  5 ++
+ src/cmd/go/testdata/script/work_env.txt |  2 +-
+ 4 files changed, 158 insertions(+), 3 deletions(-)
+ create mode 100644 src/cmd/go/internal/envcmd/env_test.go
+ create mode 100644 src/cmd/go/testdata/script/env_sanitize.txt
+
+diff --git a/src/cmd/go/internal/envcmd/env.go 
b/src/cmd/go/internal/envcmd/env.go
+index fb7448a..5b52fad 100644
+--- a/src/cmd/go/internal/envcmd/env.go
 b/src/cmd/go/internal/envcmd/env.go
+@@ -6,6 +6,7 @@
+ package envcmd
+ 
+ import (
++  "bytes"
+   "context"
+   "encoding/json"
+   "fmt"
+@@ -17,6 +18,7 @@ import (
+   "runtime"
+   "sort"
+   "strings"
++  "unicode"
+   "unicode/utf8"
+ 
+   "cmd/go/internal/base"
+@@ -413,9 +415,12 @@ func checkBuildConfig(add map[string]string, del 
map[string]bool) error {
+ func PrintEnv(w io.Writer, env []cfg.EnvVar) {
+   for _, e := range env {
+   if e.Name != "TERM" {
++  if runtime.GOOS != "plan9" && 
bytes.Contains([]byte(e.Value), []byte{0}) {
++  base.Fatalf("go: internal error: encountered 
null byte in environment variable %s on non-plan9 platform", e.Name)
++  }
+   switch runtime.GOOS {
+   default:
+-  fmt.Fprintf(w, "%s=\"%s\"\n", e.Name, e.Value)
++  fmt.Fprintf(w, "%s=%s\n", e.Name, 
shellQuote(e.Value))
+   case "plan9":
+   if strings.IndexByte(e.Value, '\x00') < 0 {
+   fmt.Fprintf(w, "%s='%s'\n", e.Name, 
strings.ReplaceAll(e.Value, "'", "''"))
+@@ -426,17 +431,68 @@ func PrintEnv(w io.Writer, env []cfg.EnvVar) {
+   if x > 0 {
+   fmt.Fprintf(w, " ")
+   }
++  // TODO(#59979): Does this need 
to be quoted like above?
+   fmt.Fprintf(w, "%s", s)
+   }
+   fmt.Fprintf(w, ")\n")
+   }
+   case "windows":
+-  fmt.Fprintf(w, "set %s=%s\n", e.Name, e.Value)
++  if hasNonGraphic(e.Value) {
++  base.Errorf("go: stripping unprintable 
or unescapab

Re: [OE-core][PATCH v2] iproute2: upgrade 6.3.0 -> 6.4.0

[Alexander Kanavin]

Thanks!

Alex

On Fri 21. Jul 2023 at 15.48, Trevor Gamblin  wrote:

> Changelog:
> https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/log/
>
> Added a patch for including limits.h with musl builds, or else
> we get failures such as:
>
> | mdb.c: In function 'mdb_parse_vni':
> | mdb.c:666:47: error: 'ULONG_MAX' undeclared (first use in this function)
> |   666 | if ((endptr && *endptr) || vni_num == ULONG_MAX)
> |   |   ^
> | mdb.c:666:47: note: 'ULONG_MAX' is defined in header ''; did
> you forget to '#include '?
>
> Signed-off-by: Trevor Gamblin 
> ---
> v2 modifies the included patch to reflect that it has been submitted to
> the upstream iproute2 project.
>
>  .../0001-bridge-mdb.c-include-limits.h.patch  | 41 +++
>  .../{iproute2_6.3.0.bb => iproute2_6.4.0.bb}  |  3 +-
>  2 files changed, 43 insertions(+), 1 deletion(-)
>  create mode 100644
> meta/recipes-connectivity/iproute2/iproute2/0001-bridge-mdb.c-include-limits.h.patch
>  rename meta/recipes-connectivity/iproute2/{iproute2_6.3.0.bb =>
> iproute2_6.4.0.bb} (95%)
>
> diff --git
> a/meta/recipes-connectivity/iproute2/iproute2/0001-bridge-mdb.c-include-limits.h.patch
> b/meta/recipes-connectivity/iproute2/iproute2/0001-bridge-mdb.c-include-limits.h.patch
> new file mode 100644
> index 00..f9a0e35d83
> --- /dev/null
> +++
> b/meta/recipes-connectivity/iproute2/iproute2/0001-bridge-mdb.c-include-limits.h.patch
> @@ -0,0 +1,41 @@
> +From b13f04c0c685b6d2474aa7d97e191531f327bc45 Mon Sep 17 00:00:00 2001
> +From: Trevor Gamblin 
> +Date: Thu, 20 Jul 2023 14:32:23 -0400
> +Subject: [PATCH] bridge/mdb.c: include limits.h
> +
> +Upstream-Status: Submitted
> +(
> https://lore.kernel.org/netdev/20230720203726.2316251-1-tgamb...@baylibre.com/
> )
> +
> +While building iproute2 6.4.0 with musl using Yocto Project, errors such
> +as the following were encountered:
> +
> +| mdb.c: In function 'mdb_parse_vni':
> +| mdb.c:666:47: error: 'ULONG_MAX' undeclared (first use in this function)
> +|   666 | if ((endptr && *endptr) || vni_num == ULONG_MAX)
> +|   |   ^
> +| mdb.c:666:47: note: 'ULONG_MAX' is defined in header ''; did
> you forget to '#include '?
> +
> +Include limits.h in bridge/mdb.c to fix this issue. This change is based
> +on one in Alpine Linux, but the author there had no plans to submit:
> +
> https://git.alpinelinux.org/aports/commit/main/iproute2/include.patch?id=bd46efb8a8da54948639cebcfa5b37bd608f1069
> +
> +Signed-off-by: Trevor Gamblin 
> +---
> + bridge/mdb.c | 1 +
> + 1 file changed, 1 insertion(+)
> +
> +diff --git a/bridge/mdb.c b/bridge/mdb.c
> +index fbb4f704..18793458 100644
> +--- a/bridge/mdb.c
>  b/bridge/mdb.c
> +@@ -15,6 +15,7 @@
> + #include 
> + #include 
> + #include 
> ++#include 
> +
> + #include "libnetlink.h"
> + #include "utils.h"
> +--
> +2.41.0
> +
> diff --git a/meta/recipes-connectivity/iproute2/iproute2_6.3.0.bb
> b/meta/recipes-connectivity/iproute2/iproute2_6.4.0.bb
> similarity index 95%
> rename from meta/recipes-connectivity/iproute2/iproute2_6.3.0.bb
> rename to meta/recipes-connectivity/iproute2/iproute2_6.4.0.bb
> index 892fa854da..32e2f8176b 100644
> --- a/meta/recipes-connectivity/iproute2/iproute2_6.3.0.bb
> +++ b/meta/recipes-connectivity/iproute2/iproute2_6.4.0.bb
> @@ -13,9 +13,10 @@ DEPENDS = "flex-native bison-native iptables libcap"
>
>  SRC_URI = "${KERNELORG_MIRROR}/linux/utils/net/${BPN}/${BP}.tar.xz \
> file://0001-libc-compat.h-add-musl-workaround.patch \
> +   file://0001-bridge-mdb.c-include-limits.h.patch \
> "
>
> -SRC_URI[sha256sum] =
> "dfb2a98db96e7a653cffc6693335a1a466e29a34b6ac528be48f35e1d2766732"
> +SRC_URI[sha256sum] =
> "4c51b8decbc7e4da159ffb066f590cfb93dbf9af7ff86b1647ce42b7c179a272"
>
>  inherit update-alternatives bash-completion pkgconfig
>
> --
> 2.41.0
>
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184706): 
https://lists.openembedded.org/g/openembedded-core/message/184706
Mute This Topic: https://lists.openembedded.org/mt/100275858/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] git: upgrade 2.39.3 -> 2.41.0

[Trevor Gamblin]

Changelog for 2.41.0: 
https://github.com/git/git/blob/master/Documentation/RelNotes/2.41.0.txt
Changelog for 2.40.0: 
https://github.com/git/git/blob/master/Documentation/RelNotes/2.40.0.txt

git-add--interactive was removed in 2.40.0 in favor of git add -i, which
caused the AUH upgrade failure as that PERLTOOLS entry was no longer
relevant.

Signed-off-by: Trevor Gamblin 
---
 meta/recipes-devtools/git/{git_2.39.3.bb => git_2.41.0.bb} | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)
 rename meta/recipes-devtools/git/{git_2.39.3.bb => git_2.41.0.bb} (97%)

diff --git a/meta/recipes-devtools/git/git_2.39.3.bb 
b/meta/recipes-devtools/git/git_2.41.0.bb
similarity index 97%
rename from meta/recipes-devtools/git/git_2.39.3.bb
rename to meta/recipes-devtools/git/git_2.41.0.bb
index 3393550c85..b84be24b94 100644
--- a/meta/recipes-devtools/git/git_2.39.3.bb
+++ b/meta/recipes-devtools/git/git_2.41.0.bb
@@ -117,7 +117,6 @@ FILES:${PN} += "${datadir}/git-core ${libexecdir}/git-core/"
 
 PERLTOOLS = " \
 ${bindir}/git-cvsserver \
-${libexecdir}/git-core/git-add--interactive \
 ${libexecdir}/git-core/git-archimport \
 ${libexecdir}/git-core/git-cvsexportcommit \
 ${libexecdir}/git-core/git-cvsimport \
@@ -161,4 +160,4 @@ EXTRA_OECONF += "ac_cv_snprintf_returns_bogus=no \
  "
 EXTRA_OEMAKE += "NO_GETTEXT=1"
 
-SRC_URI[tarball.sha256sum] = 
"2f9aa93c548941cc5aff641cedc24add15b912ad8c9b36ff5a41b1a9dcad783e"
+SRC_URI[tarball.sha256sum] = 
"c4a6a3dd1827895a80cbd824e14d94811796ae54037549e0da93f7b84cb45b9f"
-- 
2.41.0


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

[OE-core] [nvd-news] Keyword and Keyword Exact Match Searches Temporarily Disabled

[Marta Rybczynska]

We might see some difficulties in the next days.

Marta

-- Forwarded message -
From: nvd-news 
Date: Fri, Jul 21, 2023 at 5:57 PM
Subject: [nvd-news] Keyword and Keyword Exact Match Searches Temporarily
Disabled
To: nvd-news 


*Keyword and Keyword Exact Match Searches Temporarily Disabled*

The NVD has been experiencing issues with website and API availability. We
have identified the root cause, however, due to the particular complexities
and other operational needs, a larger scale solution must be put into
place. This will take time to implement and resolve. In the interim, to
ensure continuity of services that are not impacted, we will be disabling
both the keyword and keyword exact match capabilities of the vulnerability
search page and APIs. We are aware that this will impact the daily efforts
of many that make use of our data and request understanding and patience
while we move towards a viable solution.

For questions and concerns you can contact n...@nist.gov . Please refrain
from requesting timelines on resolution, we will notify all users through
the various channels available when we have information to share on the
topic.

V/r,
The National Vulnerability Database Team

-- 
To unsubscribe from this group, send email to
nvd-news+unsubscr...@list.nist.gov
View this group at https://list.nist.gov/nvd-news
---
To unsubscribe from this group and stop receiving emails from it, send an
email to nvd-news+unsubscr...@list.nist.gov.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184704): 
https://lists.openembedded.org/g/openembedded-core/message/184704
Mute This Topic: https://lists.openembedded.org/mt/100279398/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 v2] python3-dtc: add from meta-virtualization

[Trevor Gamblin]

This provides pylibfdt, which is a runtime dependency for the dtschema
module that we already carry in oe-core.

Signed-off-by: Trevor Gamblin 
---
v2 adds maintainer info to maintainers.inc.

 meta/conf/distro/include/maintainers.inc  |   1 +
 ...erlay-make-overlay_get_target-public.patch | 132 ++
 .../python/python3-dtc_1.6.1.bb   |  26 
 3 files changed, 159 insertions(+)
 create mode 100644 
meta/recipes-devtools/python/python3-dtc/0001-Revert-libfdt-overlay-make-overlay_get_target-public.patch
 create mode 100644 meta/recipes-devtools/python/python3-dtc_1.6.1.bb

diff --git a/meta/conf/distro/include/maintainers.inc 
b/meta/conf/distro/include/maintainers.inc
index 6e82e943fa..17f038c71e 100644
--- a/meta/conf/distro/include/maintainers.inc
+++ b/meta/conf/distro/include/maintainers.inc
@@ -614,6 +614,7 @@ RECIPE_MAINTAINER:pn-python3-cython = "Unassigned 
"
 RECIPE_MAINTAINER:pn-python3-dbus = "Zang Ruochen "
 RECIPE_MAINTAINER:pn-python3-dbusmock = "Unassigned 
"
 RECIPE_MAINTAINER:pn-python3-docutils = "Unassigned 
"
+RECIPE_MAINTAINER:pn-python3-dtc = "Trevor Gamblin "
 RECIPE_MAINTAINER:pn-python3-dtschema = "Bruce Ashfield 
"
 RECIPE_MAINTAINER:pn-python3-dtschema-wrapper = "Bruce Ashfield 
"
 RECIPE_MAINTAINER:pn-python3-editables = "Ross Burton "
diff --git 
a/meta/recipes-devtools/python/python3-dtc/0001-Revert-libfdt-overlay-make-overlay_get_target-public.patch
 
b/meta/recipes-devtools/python/python3-dtc/0001-Revert-libfdt-overlay-make-overlay_get_target-public.patch
new file mode 100644
index 00..a2df482e3a
--- /dev/null
+++ 
b/meta/recipes-devtools/python/python3-dtc/0001-Revert-libfdt-overlay-make-overlay_get_target-public.patch
@@ -0,0 +1,132 @@
+From 4d4703e0199fb3556c37694e4d951785abca22fd Mon Sep 17 00:00:00 2001
+From: Bruce Ashfield 
+Date: Wed, 19 Jan 2022 12:46:42 -0500
+Subject: [PATCH] Revert "libfdt: overlay: make overlay_get_target() public"
+
+This reverts commit 45f3d1a095dd3440578d5c6313eba555a791f3fb.
+
+Upstream-Status: Inappropriate [embedded specific]
+
+---
+ libfdt/fdt_overlay.c | 29 ++---
+ libfdt/libfdt.h  | 18 --
+ libfdt/version.lds   |  1 -
+ 3 files changed, 22 insertions(+), 26 deletions(-)
+
+diff --git a/libfdt/fdt_overlay.c b/libfdt/fdt_overlay.c
+index 5c0c398..d217e79 100644
+--- a/libfdt/fdt_overlay.c
 b/libfdt/fdt_overlay.c
+@@ -40,22 +40,37 @@ static uint32_t overlay_get_target_phandle(const void 
*fdto, int fragment)
+   return fdt32_to_cpu(*val);
+ }
+ 
+-int fdt_overlay_target_offset(const void *fdt, const void *fdto,
+-int fragment_offset, char const **pathp)
++/**
++ * overlay_get_target - retrieves the offset of a fragment's target
++ * @fdt: Base device tree blob
++ * @fdto: Device tree overlay blob
++ * @fragment: node offset of the fragment in the overlay
++ * @pathp: pointer which receives the path of the target (or NULL)
++ *
++ * overlay_get_target() retrieves the target offset in the base
++ * device tree of a fragment, no matter how the actual targeting is
++ * done (through a phandle or a path)
++ *
++ * returns:
++ *  the targeted node offset in the base device tree
++ *  Negative error code on error
++ */
++static int overlay_get_target(const void *fdt, const void *fdto,
++int fragment, char const **pathp)
+ {
+   uint32_t phandle;
+   const char *path = NULL;
+   int path_len = 0, ret;
+ 
+   /* Try first to do a phandle based lookup */
+-  phandle = overlay_get_target_phandle(fdto, fragment_offset);
++  phandle = overlay_get_target_phandle(fdto, fragment);
+   if (phandle == (uint32_t)-1)
+   return -FDT_ERR_BADPHANDLE;
+ 
+   /* no phandle, try path */
+   if (!phandle) {
+   /* And then a path based lookup */
+-  path = fdt_getprop(fdto, fragment_offset, "target-path", 
&path_len);
++  path = fdt_getprop(fdto, fragment, "target-path", &path_len);
+   if (path)
+   ret = fdt_path_offset(fdt, path);
+   else
+@@ -621,7 +636,7 @@ static int overlay_merge(void *fdt, void *fdto)
+   if (overlay < 0)
+   return overlay;
+ 
+-  target = fdt_overlay_target_offset(fdt, fdto, fragment, NULL);
++  target = overlay_get_target(fdt, fdto, fragment, NULL);
+   if (target < 0)
+   return target;
+ 
+@@ -764,7 +779,7 @@ static int overlay_symbol_update(void *fdt, void *fdto)
+   return -FDT_ERR_BADOVERLAY;
+ 
+   /* get the target of the fragment */
+-  ret = fdt_overlay_target_offset(fdt, fdto, fragment, 
&target_path);
++  ret = overlay_get_target(fdt, fdto, fragment, &target_path);
+   if (ret < 0)
+   return ret;
+   target = ret;
+@@ -786,7 +801,7 @@ static int overlay_symbol_

Re: [OE-core] [PATCH 1/2] tunes: Add support for sve instructions on armv8/armv9

[Alexandre Belloni via lists.openembedded.org]

Hello Khem,

On 12/07/2023 09:12:54-0700, Khem Raj wrote:
> On Wed, Jul 12, 2023 at 3:29 AM Ross Burton  wrote:
> >
> > On 11 Jul 2023, at 21:10, Khem Raj via lists.openembedded.org 
> >  wrote:
> > >
> > > This helps in defining correct compiler options and configure options
> > > for glibc and overall ABI for toolchain
> >
> > Given this, shouldn’t the glibc patch respect the tune flags instead of 
> > forcibly turning sve off?
> 
> It will as a follow up.

I think we are still waiting for the follow up.



-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184701): 
https://lists.openembedded.org/g/openembedded-core/message/184701
Mute This Topic: https://lists.openembedded.org/mt/100086804/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 2/3] python3-dtc: add from meta-virtualization

[Trevor Gamblin]

On 2023-07-21 10:15, Alexandre Belloni wrote:

The following recipes do not have a maintainer assigned to them. Please add an 
entry to meta/conf/distro/include/maintainers.inc file.
python3-dtc 
(/home/pokybuild/yocto-worker/oe-selftest-centos/build/meta/recipes-devtools/python/python3-dtc_1.6.1.bb)

;)

My bad. v2 coming shortly.


On 17/07/2023 12:41:23-0400, Trevor Gamblin wrote:

This provides pylibfdt, which is a runtime dependency for the dtschema
module that we already carry in oe-core.

Signed-off-by: Trevor Gamblin 
---
  ...erlay-make-overlay_get_target-public.patch | 132 ++
  .../python/python3-dtc_1.6.1.bb   |  26 
  2 files changed, 158 insertions(+)
  create mode 100644 
meta/recipes-devtools/python/python3-dtc/0001-Revert-libfdt-overlay-make-overlay_get_target-public.patch
  create mode 100644 meta/recipes-devtools/python/python3-dtc_1.6.1.bb

diff --git 
a/meta/recipes-devtools/python/python3-dtc/0001-Revert-libfdt-overlay-make-overlay_get_target-public.patch
 
b/meta/recipes-devtools/python/python3-dtc/0001-Revert-libfdt-overlay-make-overlay_get_target-public.patch
new file mode 100644
index 00..a2df482e3a
--- /dev/null
+++ 
b/meta/recipes-devtools/python/python3-dtc/0001-Revert-libfdt-overlay-make-overlay_get_target-public.patch
@@ -0,0 +1,132 @@
+From 4d4703e0199fb3556c37694e4d951785abca22fd Mon Sep 17 00:00:00 2001
+From: Bruce Ashfield 
+Date: Wed, 19 Jan 2022 12:46:42 -0500
+Subject: [PATCH] Revert "libfdt: overlay: make overlay_get_target() public"
+
+This reverts commit 45f3d1a095dd3440578d5c6313eba555a791f3fb.
+
+Upstream-Status: Inappropriate [embedded specific]
+
+---
+ libfdt/fdt_overlay.c | 29 ++---
+ libfdt/libfdt.h  | 18 --
+ libfdt/version.lds   |  1 -
+ 3 files changed, 22 insertions(+), 26 deletions(-)
+
+diff --git a/libfdt/fdt_overlay.c b/libfdt/fdt_overlay.c
+index 5c0c398..d217e79 100644
+--- a/libfdt/fdt_overlay.c
 b/libfdt/fdt_overlay.c
+@@ -40,22 +40,37 @@ static uint32_t overlay_get_target_phandle(const void 
*fdto, int fragment)
+   return fdt32_to_cpu(*val);
+ }
+
+-int fdt_overlay_target_offset(const void *fdt, const void *fdto,
+-int fragment_offset, char const **pathp)
++/**
++ * overlay_get_target - retrieves the offset of a fragment's target
++ * @fdt: Base device tree blob
++ * @fdto: Device tree overlay blob
++ * @fragment: node offset of the fragment in the overlay
++ * @pathp: pointer which receives the path of the target (or NULL)
++ *
++ * overlay_get_target() retrieves the target offset in the base
++ * device tree of a fragment, no matter how the actual targeting is
++ * done (through a phandle or a path)
++ *
++ * returns:
++ *  the targeted node offset in the base device tree
++ *  Negative error code on error
++ */
++static int overlay_get_target(const void *fdt, const void *fdto,
++int fragment, char const **pathp)
+ {
+   uint32_t phandle;
+   const char *path = NULL;
+   int path_len = 0, ret;
+
+   /* Try first to do a phandle based lookup */
+-  phandle = overlay_get_target_phandle(fdto, fragment_offset);
++  phandle = overlay_get_target_phandle(fdto, fragment);
+   if (phandle == (uint32_t)-1)
+   return -FDT_ERR_BADPHANDLE;
+
+   /* no phandle, try path */
+   if (!phandle) {
+   /* And then a path based lookup */
+-  path = fdt_getprop(fdto, fragment_offset, "target-path", 
&path_len);
++  path = fdt_getprop(fdto, fragment, "target-path", &path_len);
+   if (path)
+   ret = fdt_path_offset(fdt, path);
+   else
+@@ -621,7 +636,7 @@ static int overlay_merge(void *fdt, void *fdto)
+   if (overlay < 0)
+   return overlay;
+
+-  target = fdt_overlay_target_offset(fdt, fdto, fragment, NULL);
++  target = overlay_get_target(fdt, fdto, fragment, NULL);
+   if (target < 0)
+   return target;
+
+@@ -764,7 +779,7 @@ static int overlay_symbol_update(void *fdt, void *fdto)
+   return -FDT_ERR_BADOVERLAY;
+
+   /* get the target of the fragment */
+-  ret = fdt_overlay_target_offset(fdt, fdto, fragment, 
&target_path);
++  ret = overlay_get_target(fdt, fdto, fragment, &target_path);
+   if (ret < 0)
+   return ret;
+   target = ret;
+@@ -786,7 +801,7 @@ static int overlay_symbol_update(void *fdt, void *fdto)
+
+   if (!target_path) {
+   /* again in case setprop_placeholder changed it */
+-  ret = fdt_overlay_target_offset(fdt, fdto, fragment, 
&target_path);
++  ret = overlay_get_target(fdt, fdto, fragment, 
&target_path);
+   if (ret < 0)
+   return ret;
+

[OE-core] [RFC v2 2/2] scripts/bblock: add a script to lock/unlock recipes

[Julien Stephan]

bblock script allows to lock/unlock recipes to latest signatures. The idea is
to prevent some recipes to be rebuilt during development. For example
when working on rust recipe, one may not want rust-native to be
rebuilt.

This tool can be used, with proper environment set up, using the following
command:

bblock 

if 's task signatures change it will not be built again and
sstate cache will be used.

[YOCTO #13425]

Signed-off-by: Julien Stephan 
---
 scripts/bblock | 184 +
 1 file changed, 184 insertions(+)
 create mode 100755 scripts/bblock

diff --git a/scripts/bblock b/scripts/bblock
new file mode 100755
index 000..5a269b33806
--- /dev/null
+++ b/scripts/bblock
@@ -0,0 +1,184 @@
+#!/usr/bin/env python3
+# bblock
+# lock/unlock task to latest signature
+#
+# Copyright (c) 2020 BayLibre, SAS
+# Author: Julien Stepahn 
+#
+# SPDX-License-Identifier: GPL-2.0-only
+#
+
+import os
+import sys
+import logging
+
+scripts_path = os.path.dirname(os.path.realpath(__file__))
+lib_path = scripts_path + "/lib"
+sys.path = sys.path + [lib_path]
+
+import scriptpath
+
+scriptpath.add_bitbake_lib_path()
+
+import bb.tinfoil
+import bb.msg
+
+import argparse_oe
+
+myname = os.path.basename(sys.argv[0])
+logger = bb.msg.logger_create(myname)
+
+
+def find_siginfo(tinfoil, pn, taskname, sigs=None):
+result = None
+tinfoil.set_event_mask(
+[
+"bb.event.FindSigInfoResult",
+"logging.LogRecord",
+"bb.command.CommandCompleted",
+"bb.command.CommandFailed",
+]
+)
+ret = tinfoil.run_command("findSigInfo", pn, taskname, sigs)
+if ret:
+while True:
+event = tinfoil.wait_event(1)
+if event:
+if isinstance(event, bb.command.CommandCompleted):
+break
+elif isinstance(event, bb.command.CommandFailed):
+logger.error(str(event))
+sys.exit(2)
+elif isinstance(event, bb.event.FindSigInfoResult):
+result = event.result
+elif isinstance(event, logging.LogRecord):
+logger.handle(event)
+else:
+logger.error("No result returned from findSigInfo command")
+sys.exit(2)
+return result
+
+
+def parse_recipe(tinfoil, recipe):
+try:
+tinfoil.parse_recipes()
+d = tinfoil.parse_recipe(recipe)
+except Exception:
+logger.error("Failed to get recipe info for: %s" % recipe)
+sys.exit(1)
+return d
+
+
+def dump(lockfile):
+with open(lockfile, "r") as lockfile:
+for line in lockfile:
+print(line.strip())
+return 0
+
+
+def reset(lockfile, pns, package_archs, tasks):
+if not pns:
+logger.info("Unlocking all recipes")
+os.remove(lockfile)
+else:
+logger.info("Unlocking {pns}".format(pns=pns))
+tmp_lockfile = lockfile + ".tmp"
+with open(lockfile, "r") as infile, open(tmp_lockfile, "w") as outfile:
+for line in infile:
+if not (
+any(element in line for element in pns)
+and any(element in line for element in 
package_archs.split())
+):
+outfile.write(line)
+else:
+if tasks and not any(element in line for element in tasks):
+outfile.write(line)
+os.remove(lockfile)
+os.rename(tmp_lockfile, lockfile)
+sys.exit(0)
+
+
+def main():
+parser = argparse_oe.ArgumentParser(description="Lock and unlock a recipe")
+parser.add_argument("pn", nargs="*", help="Space separated list of recipe 
to lock")
+parser.add_argument(
+"-t",
+"--tasks",
+help="Comma separated list of tasks",
+type=lambda s: [task for task in s.split(",")],
+)
+parser.add_argument(
+"-r",
+"--reset",
+action="store_true",
+help="Unlock pn recipes, or all recipes if pn is empty",
+)
+
+parser.add_argument(
+"-d",
+"--dump",
+action="store_true",
+help="Dump generated bblock.conf file",
+)
+
+global_args, unparsed_args = parser.parse_known_args()
+
+with bb.tinfoil.Tinfoil() as tinfoil:
+tinfoil.prepare(config_only=True)
+
+package_archs = tinfoil.config_data.getVar("PACKAGE_ARCHS")
+builddir = tinfoil.config_data.getVar("TOPDIR")
+lockfile = "{builddir}/conf/bblock.conf".format(builddir=builddir)
+
+if global_args.dump:
+dump(lockfile)
+
+tasks = global_args.tasks
+
+if global_args.reset:
+reset(lockfile, global_args.pn, package_archs, tasks)
+
+with open(lockfile, "a") as lockfile:
+s = ""
+if lockfile.tell() == 0:
+s = "# Generated by bblock\n"
+s += 'SIGGEN_LOCKEDSIGS_TASKSI

[OE-core] [RFC v2 1/2] bitbake.conf: include bblock.conf

[Julien Stephan]

include conf/bblock.conf. This file is generated by the bblock tool. It
locks some package tasks by fixing their signature. See bblock -h for
more details

Signed-off-by: Julien Stephan 
---
 meta/conf/bitbake.conf | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 9625a6fef4c..a4b2b4b0380 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -831,6 +831,7 @@ include conf/distro/defaultsetup.conf
 include conf/documentation.conf
 include conf/licenses.conf
 require conf/sanity.conf
+include conf/bblock.conf
 
 ##
 # Weak variables (usually to retain backwards compatibility)
-- 
2.41.0


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

[OE-core] [RFC v2 0/2] Add bblock helper script

[Julien Stephan]

Hi all,

This is the v2 of bblock script.

Improvement from V1:
* Signatures are now package architecture specific meaning that if you
  switch MACHINE, the lock sig will not be taken into account
* I added the -r option to unlock recipes
* I added a -d option to display the current bblock.conf
* Added an include directive for conf/bblock.conf inside bitbake.conf
* Added -t option to specify the tasks to lock/unlock

Limitations:
* I may be still missing some checks on user input
* I need to find a way to get the list of tasks ( by default still lock
  only the do_compile for now, unless -t is specified)
* Do not check if a particular recipe/task is already locked when trying
  to add lock. So entries may appear multiple times
* We still need the signature of the tasks to be already computed before
  locking. Need to find a way to generate it if missing

I did some tests using qemux86-64 and qemuarm but I may be missing some
corner cases.

I force pushed my branch on poky-contrib [1]

Any feedback are welcome!

Cheers
Julien

V1:
I am currently working on bug #13425 and I would like to post my wip
script as an RFC to get feedback on it, before going further in the
development.

The script `script/bblock` can be used with the following command:

bblock [list of recipes to lock]

Here is a summary of what is currently implemented:
* can lock several recipes at once
* on first execution bblock will append `require bblock.inc` in
  `build/conf/auto.conf` (creates `auto.conf` if it doesn't exist)
* on first execution creates the file `build/conf/bblock.inc` with a
  dedicated header and:
 - adds SIGGEN_LOCKEDSIGS_TYPES += "t-bblock"
 - adds SIGGEN_LOCKEDSIGS_TASKSIG_CHECK = "warn" to display warning but
   do not stop the build
* loops over all recipes to lock and adds entry with latest "do_compile"
  signature in `conf/bblock.inc`, such as: SIGGEN_LOCKEDSIGS_t-bblock += 
"bc:do_compile:e233cd793137a92dd575a417a2877e324ce526c4dc4a7db652abb9512f406f1f"

Limitations:
* only gets do_compile signature for now as a POC
* `bblock reset [list of recipes]` not yet implemented
* no check if a recipe is already locked

Steps to test the script:
bitbake bc --> generate a signature for bc's tasks
bblock bc
# modify do_compile in bc recipe to force signature change
bitbake bc --> throws the following warning: `WARNING: The bc:do_compile sig is 
computed to be 
680bd6c291bf88e379e0c405a773cf5f81851e1a52570398cefd0196000ac1ef, but the sig 
is locked to e233cd793137a92dd575a417a2877e324ce526c4dc4a7db652abb9512f406f1f 
in SIGGEN_LOCKEDSIGS_t-bblock`

I also have a point I would like to discuss: I only get signature for
do_compile for the POC but wondering what should I do here:
* have a set of predefined task to lock, in that case how to choose the
  tasks?
* compute the list of all available tasks for a given recipe and get
  signature for all? Is there a way to get such list without using
  `infoil.build_targets(pn, "listtasks", handle_events=True)` as this
  will start bitbake, takes some time and requires some processing of
  the output
* add an option for the user to specify the task he wants to lock? (this
  may be useful to add anyway)

My branch is available here [1]

Am I going into the right direction?

Cheers
Julien

[1]: https://git.yoctoproject.org/poky-contrib/commit/?h=jstephan/bblock
Julien Stephan (2):
  bitbake.conf: include bblock.conf
  scripts/bblock: add a script to lock/unlock recipes

 meta/conf/bitbake.conf |   1 +
 scripts/bblock | 184 +
 2 files changed, 185 insertions(+)
 create mode 100755 scripts/bblock

--
2.41.0

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184697): 
https://lists.openembedded.org/g/openembedded-core/message/184697
Mute This Topic: https://lists.openembedded.org/mt/100277504/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] kirkstone boost upgrade?

[Thomas Roos via lists.openembedded.org]

thank you, Ross - will try.
Cheers, Thomas


Von: Ross Burton 
Gesendet: Freitag, 21. Juli 2023 13:42:02
An: Roos, Thomas
Cc: Vyacheslav Yurkov; openembedded-core@lists.openembedded.org
Betreff: RE: [EXTERNAL][OE-core] kirkstone boost upgrade?

CAUTION: This email originated from outside of the organization. Do not click 
links or open attachments unless you can confirm the sender and know the 
content is safe.



On 21 Jul 2023, at 09:25, Thomas Roos via lists.openembedded.org 
 wrote:
>
> Hi Vyacheslav,
> I think it's this error: boost beast "Fixed WebSocket handshake response on 
> failure."
> Fixed in 1.79.
> My question was what is the policy of upgrading boost in an LTS branch? I 
> guess there is no change?
> I totally agree that there are breaking changes - I had experienced a lot in 
> the past...

If you can isolate the fix to a small patch that doesn’t break anything else, 
then you can submit that as a patch.  If it needs to be an invasive upgrade, 
that’s less likely to happen.

Ross



Amazon Web Services EMEA SARL
38 avenue John F. Kennedy, L-1855 Luxembourg
Sitz der Gesellschaft: L-1855 Luxemburg
eingetragen im Luxemburgischen Handelsregister unter R.C.S. B186284

Amazon Web Services EMEA SARL, Niederlassung Deutschland
Marcel-Breuer-Str. 12, D-80807 Muenchen
Sitz der Zweigniederlassung: Muenchen
eingetragen im Handelsregister des Amtsgerichts Muenchen unter HRB 242240, 
USt-ID DE317013094




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184696): 
https://lists.openembedded.org/g/openembedded-core/message/184696
Mute This Topic: https://lists.openembedded.org/mt/100271099/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 2/3] python3-dtc: add from meta-virtualization

[Alexandre Belloni via lists.openembedded.org]

The following recipes do not have a maintainer assigned to them. Please add an 
entry to meta/conf/distro/include/maintainers.inc file.
python3-dtc 
(/home/pokybuild/yocto-worker/oe-selftest-centos/build/meta/recipes-devtools/python/python3-dtc_1.6.1.bb)

;)

On 17/07/2023 12:41:23-0400, Trevor Gamblin wrote:
> This provides pylibfdt, which is a runtime dependency for the dtschema
> module that we already carry in oe-core.
> 
> Signed-off-by: Trevor Gamblin 
> ---
>  ...erlay-make-overlay_get_target-public.patch | 132 ++
>  .../python/python3-dtc_1.6.1.bb   |  26 
>  2 files changed, 158 insertions(+)
>  create mode 100644 
> meta/recipes-devtools/python/python3-dtc/0001-Revert-libfdt-overlay-make-overlay_get_target-public.patch
>  create mode 100644 meta/recipes-devtools/python/python3-dtc_1.6.1.bb
> 
> diff --git 
> a/meta/recipes-devtools/python/python3-dtc/0001-Revert-libfdt-overlay-make-overlay_get_target-public.patch
>  
> b/meta/recipes-devtools/python/python3-dtc/0001-Revert-libfdt-overlay-make-overlay_get_target-public.patch
> new file mode 100644
> index 00..a2df482e3a
> --- /dev/null
> +++ 
> b/meta/recipes-devtools/python/python3-dtc/0001-Revert-libfdt-overlay-make-overlay_get_target-public.patch
> @@ -0,0 +1,132 @@
> +From 4d4703e0199fb3556c37694e4d951785abca22fd Mon Sep 17 00:00:00 2001
> +From: Bruce Ashfield 
> +Date: Wed, 19 Jan 2022 12:46:42 -0500
> +Subject: [PATCH] Revert "libfdt: overlay: make overlay_get_target() public"
> +
> +This reverts commit 45f3d1a095dd3440578d5c6313eba555a791f3fb.
> +
> +Upstream-Status: Inappropriate [embedded specific]
> +
> +---
> + libfdt/fdt_overlay.c | 29 ++---
> + libfdt/libfdt.h  | 18 --
> + libfdt/version.lds   |  1 -
> + 3 files changed, 22 insertions(+), 26 deletions(-)
> +
> +diff --git a/libfdt/fdt_overlay.c b/libfdt/fdt_overlay.c
> +index 5c0c398..d217e79 100644
> +--- a/libfdt/fdt_overlay.c
>  b/libfdt/fdt_overlay.c
> +@@ -40,22 +40,37 @@ static uint32_t overlay_get_target_phandle(const void 
> *fdto, int fragment)
> + return fdt32_to_cpu(*val);
> + }
> + 
> +-int fdt_overlay_target_offset(const void *fdt, const void *fdto,
> +-  int fragment_offset, char const **pathp)
> ++/**
> ++ * overlay_get_target - retrieves the offset of a fragment's target
> ++ * @fdt: Base device tree blob
> ++ * @fdto: Device tree overlay blob
> ++ * @fragment: node offset of the fragment in the overlay
> ++ * @pathp: pointer which receives the path of the target (or NULL)
> ++ *
> ++ * overlay_get_target() retrieves the target offset in the base
> ++ * device tree of a fragment, no matter how the actual targeting is
> ++ * done (through a phandle or a path)
> ++ *
> ++ * returns:
> ++ *  the targeted node offset in the base device tree
> ++ *  Negative error code on error
> ++ */
> ++static int overlay_get_target(const void *fdt, const void *fdto,
> ++  int fragment, char const **pathp)
> + {
> + uint32_t phandle;
> + const char *path = NULL;
> + int path_len = 0, ret;
> + 
> + /* Try first to do a phandle based lookup */
> +-phandle = overlay_get_target_phandle(fdto, fragment_offset);
> ++phandle = overlay_get_target_phandle(fdto, fragment);
> + if (phandle == (uint32_t)-1)
> + return -FDT_ERR_BADPHANDLE;
> + 
> + /* no phandle, try path */
> + if (!phandle) {
> + /* And then a path based lookup */
> +-path = fdt_getprop(fdto, fragment_offset, "target-path", 
> &path_len);
> ++path = fdt_getprop(fdto, fragment, "target-path", &path_len);
> + if (path)
> + ret = fdt_path_offset(fdt, path);
> + else
> +@@ -621,7 +636,7 @@ static int overlay_merge(void *fdt, void *fdto)
> + if (overlay < 0)
> + return overlay;
> + 
> +-target = fdt_overlay_target_offset(fdt, fdto, fragment, NULL);
> ++target = overlay_get_target(fdt, fdto, fragment, NULL);
> + if (target < 0)
> + return target;
> + 
> +@@ -764,7 +779,7 @@ static int overlay_symbol_update(void *fdt, void *fdto)
> + return -FDT_ERR_BADOVERLAY;
> + 
> + /* get the target of the fragment */
> +-ret = fdt_overlay_target_offset(fdt, fdto, fragment, 
> &target_path);
> ++ret = overlay_get_target(fdt, fdto, fragment, &target_path);
> + if (ret < 0)
> + return ret;
> + target = ret;
> +@@ -786,7 +801,7 @@ static int overlay_symbol_update(void *fdt, void *fdto)
> + 
> + if (!target_path) {
> + /* again in case setprop_placeholder changed it */
> +-ret = fdt_overlay_target_offset(fdt, fdto, fragment, 
> &target_path);
> ++ret = overlay_get_target(fdt, fdto, fragment, 
> &target_path);
> +

[OE-core][PATCH v2] iproute2: upgrade 6.3.0 -> 6.4.0

[Trevor Gamblin]

Changelog: https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/log/

Added a patch for including limits.h with musl builds, or else
we get failures such as:

| mdb.c: In function 'mdb_parse_vni':
| mdb.c:666:47: error: 'ULONG_MAX' undeclared (first use in this function)
|   666 | if ((endptr && *endptr) || vni_num == ULONG_MAX)
|   |   ^
| mdb.c:666:47: note: 'ULONG_MAX' is defined in header ''; did you 
forget to '#include '?

Signed-off-by: Trevor Gamblin 
---
v2 modifies the included patch to reflect that it has been submitted to
the upstream iproute2 project.

 .../0001-bridge-mdb.c-include-limits.h.patch  | 41 +++
 .../{iproute2_6.3.0.bb => iproute2_6.4.0.bb}  |  3 +-
 2 files changed, 43 insertions(+), 1 deletion(-)
 create mode 100644 
meta/recipes-connectivity/iproute2/iproute2/0001-bridge-mdb.c-include-limits.h.patch
 rename meta/recipes-connectivity/iproute2/{iproute2_6.3.0.bb => 
iproute2_6.4.0.bb} (95%)

diff --git 
a/meta/recipes-connectivity/iproute2/iproute2/0001-bridge-mdb.c-include-limits.h.patch
 
b/meta/recipes-connectivity/iproute2/iproute2/0001-bridge-mdb.c-include-limits.h.patch
new file mode 100644
index 00..f9a0e35d83
--- /dev/null
+++ 
b/meta/recipes-connectivity/iproute2/iproute2/0001-bridge-mdb.c-include-limits.h.patch
@@ -0,0 +1,41 @@
+From b13f04c0c685b6d2474aa7d97e191531f327bc45 Mon Sep 17 00:00:00 2001
+From: Trevor Gamblin 
+Date: Thu, 20 Jul 2023 14:32:23 -0400
+Subject: [PATCH] bridge/mdb.c: include limits.h
+
+Upstream-Status: Submitted
+(https://lore.kernel.org/netdev/20230720203726.2316251-1-tgamb...@baylibre.com/)
+
+While building iproute2 6.4.0 with musl using Yocto Project, errors such
+as the following were encountered:
+
+| mdb.c: In function 'mdb_parse_vni':
+| mdb.c:666:47: error: 'ULONG_MAX' undeclared (first use in this function)
+|   666 | if ((endptr && *endptr) || vni_num == ULONG_MAX)
+|   |   ^
+| mdb.c:666:47: note: 'ULONG_MAX' is defined in header ''; did you 
forget to '#include '?
+
+Include limits.h in bridge/mdb.c to fix this issue. This change is based
+on one in Alpine Linux, but the author there had no plans to submit:
+https://git.alpinelinux.org/aports/commit/main/iproute2/include.patch?id=bd46efb8a8da54948639cebcfa5b37bd608f1069
+
+Signed-off-by: Trevor Gamblin 
+---
+ bridge/mdb.c | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/bridge/mdb.c b/bridge/mdb.c
+index fbb4f704..18793458 100644
+--- a/bridge/mdb.c
 b/bridge/mdb.c
+@@ -15,6 +15,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ 
+ #include "libnetlink.h"
+ #include "utils.h"
+-- 
+2.41.0
+
diff --git a/meta/recipes-connectivity/iproute2/iproute2_6.3.0.bb 
b/meta/recipes-connectivity/iproute2/iproute2_6.4.0.bb
similarity index 95%
rename from meta/recipes-connectivity/iproute2/iproute2_6.3.0.bb
rename to meta/recipes-connectivity/iproute2/iproute2_6.4.0.bb
index 892fa854da..32e2f8176b 100644
--- a/meta/recipes-connectivity/iproute2/iproute2_6.3.0.bb
+++ b/meta/recipes-connectivity/iproute2/iproute2_6.4.0.bb
@@ -13,9 +13,10 @@ DEPENDS = "flex-native bison-native iptables libcap"
 
 SRC_URI = "${KERNELORG_MIRROR}/linux/utils/net/${BPN}/${BP}.tar.xz \
file://0001-libc-compat.h-add-musl-workaround.patch \
+   file://0001-bridge-mdb.c-include-limits.h.patch \
"
 
-SRC_URI[sha256sum] = 
"dfb2a98db96e7a653cffc6693335a1a466e29a34b6ac528be48f35e1d2766732"
+SRC_URI[sha256sum] = 
"4c51b8decbc7e4da159ffb066f590cfb93dbf9af7ff86b1647ce42b7c179a272"
 
 inherit update-alternatives bash-completion pkgconfig
 
-- 
2.41.0


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

ODP: ODP: [OE-Core][PATCH v6 1/6] bitbake.conf: add acl and xattr distro native features support

[Piotr Łobacz]

I haven't noticed due to rebasing:P nevertheless I have done it on top of 
master-next from openembedded-core and verified
if patches apply on openembedded-core-contrib/abelloni/master-next and it works.

Please check the latest v7 patchset release.


Cheers,
Piotr

Od: Alexandre Belloni 
Wysłane: piątek, 21 lipca 2023 14:00
Do: Piotr Łobacz 
DW: openembedded-core@lists.openembedded.org 

Temat: Re: ODP: [OE-Core][PATCH v6 1/6] bitbake.conf: add acl and xattr distro 
native features support

On 21/07/2023 11:23:10+, Piotr Łobacz wrote:
> OK do you want it to be on top of 
> openembedded-core-contrib/origin/abelloni/master-next or just 
> openembedded-core/master-next?

Now that the opkg upgrade had been merged in master, you can rebase on
top of master.

> 
> Od: openembedded-core@lists.openembedded.org 
>  w imieniu użytkownika Piotr Łobacz 
> via lists.openembedded.org 
> Wysłane: piątek, 21 lipca 2023 11:31
> Do: Alexandre Belloni 
> DW: openembedded-core@lists.openembedded.org 
> 
> Temat: Re: [OE-Core][PATCH v6 1/6] bitbake.conf: add acl and xattr distro 
> native features support
>
> Yes but within an hour?
>
> Wysyłane z aplikacji Outlook dla systemu 
> iOS>
> 
> Od: Alexandre Belloni 
> Wysłane: Friday, July 21, 2023 11:30:54 AM
> Do: Piotr Łobacz 
> DW: openembedded-core@lists.openembedded.org 
> 
> Temat: Re: [OE-Core][PATCH v6 1/6] bitbake.conf: add acl and xattr distro 
> native features support
>
> Hello,
>
> I want to give this a shot again, can you rebase on top of my
> master-next branch ?
>
> On 19/07/2023 21:48:38+0200, Piotr Łobacz wrote:
> > Include support for ACLs and extended file attributes for native
> > builds, by default.
> >
> > Signed-off-by: Piotr Łobacz 
> > ---
> >  meta/conf/bitbake.conf | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> > index 9625a6fef4..8dd615 100644
> > --- a/meta/conf/bitbake.conf
> > +++ b/meta/conf/bitbake.conf
> > @@ -904,7 +904,7 @@ IMAGE_FEATURES += "${EXTRA_IMAGE_FEATURES}"
> >
> >  # Native distro features (will always be used for -native, even if they
> >  # are not enabled for target)
> > -DISTRO_FEATURES_NATIVE ?= "x11 ipv6 xattr"
> > +DISTRO_FEATURES_NATIVE ?= "acl x11 ipv6 xattr"
> >  DISTRO_FEATURES_NATIVESDK ?= "x11"
> >
> >  # Normally target distro features will not be applied to native builds:
> > --
> > 2.34.1
> >
>
> >
> >
> >
>
>
> --
> Alexandre Belloni, co-owner and COO, Bootlin
> Embedded Linux and Kernel engineering
> https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbootlin.com%2F&data=05%7C01%7Cp.lobacz%40welotec.com%7Cbcc6e73fc3ae4ba1373f08db89e20bfe%7C25111a7f1d5a4c51a4ca7f8e44011b39%7C0%7C0%7C638255376186578362%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3RBLK%2BVcr81hdPmPfGMJ4%2BFCq8UOr6sCuyOG5hYdd3I%3D&reserved=0

--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbootlin.com%2F&data=05%7C01%7Cp.lobacz%40welotec.com%7Cbcc6e73fc3ae4ba1373f08db89e20bfe%7C25111a7f1d5a4c51a4ca7f8e44011b39%7C0%7C0%7C638255376186578362%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3RBLK%2BVcr81hdPmPfGMJ4%2BFCq8UOr6sCuyOG5hYdd3I%3D&reserved=0

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184693): 
https://lists.openembedded.org/g/openembedded-core/message/184693
Mute This Topic: https://lists.openembedded.org/mt/100275390/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 v7][master-next 3/5] opkg-utils: add acl and xattr support

[Piotr Łobacz]

Add support for tar archives created with --acls and/or --xattrs options,
PAX header format.

GNU tar and libarchive already supports ACLs and extended attributes.
We can now add this support as well to opkg-build script in order to use
fsetattr or setcap inside do_install command and end up with a file in
an image with the relevant ACLs and xattrs.

Signed-off-by: Piotr Łobacz 
---
 ...kg-build-Add-acls-and-xattrs-support.patch | 80 +++
 .../opkg-utils/opkg-utils_0.6.2.bb|  1 +
 2 files changed, 81 insertions(+)
 create mode 100644 
meta/recipes-devtools/opkg-utils/opkg-utils/0002-opkg-build-Add-acls-and-xattrs-support.patch

diff --git 
a/meta/recipes-devtools/opkg-utils/opkg-utils/0002-opkg-build-Add-acls-and-xattrs-support.patch
 
b/meta/recipes-devtools/opkg-utils/opkg-utils/0002-opkg-build-Add-acls-and-xattrs-support.patch
new file mode 100644
index 00..a9e5f0e191
--- /dev/null
+++ 
b/meta/recipes-devtools/opkg-utils/opkg-utils/0002-opkg-build-Add-acls-and-xattrs-support.patch
@@ -0,0 +1,80 @@
+From 5664c17923cc1ab9644ef01f549bc8d352dd8868 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Piotr=20=C5=81obacz?= 
+Date: Wed, 5 Jul 2023 10:31:13 +0200
+Subject: [PATCH] opkg-build: Add acls and xattrs support
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+Add support for tar archives created with --acls and/or --xattrs options,
+PAX header format.
+
+GNU tar and libarchive already supports ACLs and extended attributes.
+We can now add this support as well to opkg-build script in order to use
+fsetattr or setcap inside do_install command and end up with a file in
+an image with the relevant ACLs and xattrs.
+
+Upstream-Status: Accepted 
[https://groups.google.com/g/opkg-devel/c/dYNHrLjDwg8]
+
+[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=15097
+[2] https://groups.google.com/g/opkg-devel/c/aEGL7XRXfaA
+
+Signed-off-by: Piotr Łobacz 
+---
+ opkg-build | 15 ++-
+ 1 file changed, 10 insertions(+), 5 deletions(-)
+
+diff --git a/opkg-build b/opkg-build
+index a9e45d4..8d9bcfa 100755
+--- a/opkg-build
 b/opkg-build
+@@ -145,6 +145,7 @@ You probably want to chown these to a system user: " >&2
+ ###
+ # opkg-build "main"
+ ###
++attributesargs=""
+ ogargs=""
+ outer=ar
+ noclean=0
+@@ -166,7 +167,7 @@ compressorargs=""
+ tarformat=""
+ if tar --help 2>&1 | grep -- "--format" > /dev/null;
+ then
+-tarformat="--format=gnu"
++tarformat="--format=posix"
+ fi
+ 
+ compressor_ext() {
+@@ -197,13 +198,17 @@ compressor_ext() {
+ : <<=cut
+ =head1 SYNOPSIS
+ 
+-B [B<-c>] [B<-C>] [B<-Z> I] [B<-a>] [B<-O>] [B<-o> 
I] [B<-g> I] I [I]
++B [B<-A>] [B<-X>] [B<-c>] [B<-C>] [B<-Z> I] [B<-a>] 
[B<-O>] [B<-o> I] [B<-g> I] I 
[I]
+ 
+ =cut
+ 
+-usage="Usage: $0 [-c] [-C] [-Z compressor] [-a compressor_args] [-O] [-o 
owner] [-g group]  []"
+-while getopts "a:cCg:ho:vOZ:" opt; do
++usage="Usage: $0 [-A] [-X] [-c] [-C] [-Z compressor] [-a compressor_args] 
[-O] [-o owner] [-g group]  []"
++while getopts "Aa:cCg:ho:vOXZ:" opt; do
+ case $opt in
++A ) attributesargs="--acls"
++;;
++X ) attributesargs="$attributesargs --xattrs"
++;;
+   o ) owner=$OPTARG
+   ogargs="--owner=$owner"
+   ;;
+@@ -314,7 +319,7 @@ export LANG=C
+ export LC_ALL=C
+ ( cd $pkg_dir/$CONTROL && find . -type f | sort > $tmp_dir/control_list )
+ ( cd $pkg_dir && find . -path ./$CONTROL -prune -o -path . -o -print  | sort 
> $tmp_dir/file_list )
+-( cd $pkg_dir && tar $ogargs $tsortargs --no-recursion $mtime_args -c 
$tarformat -T $tmp_dir/file_list | $compressor $compressorargs > 
$tmp_dir/data.tar.$cext )
++( cd $pkg_dir && tar $attributesargs $ogargs $tsortargs --no-recursion 
$mtime_args -c $tarformat -T $tmp_dir/file_list | $compressor $compressorargs > 
$tmp_dir/data.tar.$cext )
+ ( cd $pkg_dir/$CONTROL && tar $ogargs $tsortargs --no-recursion 
--mtime=@$build_date -c $tarformat -T $tmp_dir/control_list | gzip $zipargs > 
$tmp_dir/control.tar.gz )
+ rm $tmp_dir/file_list
+ rm $tmp_dir/control_list
+-- 
+2.34.1
+
diff --git a/meta/recipes-devtools/opkg-utils/opkg-utils_0.6.2.bb 
b/meta/recipes-devtools/opkg-utils/opkg-utils_0.6.2.bb
index eb88b9b734..d5ce2cfbe2 100644
--- a/meta/recipes-devtools/opkg-utils/opkg-utils_0.6.2.bb
+++ b/meta/recipes-devtools/opkg-utils/opkg-utils_0.6.2.bb
@@ -9,6 +9,7 @@ PROVIDES += "${@bb.utils.contains('PACKAGECONFIG', 
'update-alternatives', 'virtu
 
 SRC_URI = "git://git.yoctoproject.org/opkg-utils;protocol=https;branch=master \
file://0001-update-alternatives-correctly-match-priority.patch \
+   file://0002-opkg-build-Add-acls-and-xattrs-support.patch \
"
 SRCREV = "67994e62dc598282830385da75ba9b1abbbda941"
 
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184690): 
https://lists.openembedded.org/g/openembedded-core/message/184690
Mute This Topic: https://lists.opene

[OE-Core][PATCH v7][master-next 5/5] opkg: set locale from system environment variables

[Piotr Łobacz]

A C program inherits its locale environment variables when it starts up.
This happens automatically. However, these variables do not automatically
control the locale used by the library functions, because ISO C says that
all programs start by default in the standard ‘C’ locale.

Fixes warnings:
Warning when reading ar archive header: Pathname can't be converted from UTF-8 
to current locale. (errno=84)

Signed-off-by: Piotr Łobacz 
---
 ...le-from-system-environment-variables.patch | 48 +++
 meta/recipes-devtools/opkg/opkg_0.6.2.bb  |  1 +
 2 files changed, 49 insertions(+)
 create mode 100644 
meta/recipes-devtools/opkg/opkg/0003-opkg-set-locale-from-system-environment-variables.patch

diff --git 
a/meta/recipes-devtools/opkg/opkg/0003-opkg-set-locale-from-system-environment-variables.patch
 
b/meta/recipes-devtools/opkg/opkg/0003-opkg-set-locale-from-system-environment-variables.patch
new file mode 100644
index 00..71240ec8fd
--- /dev/null
+++ 
b/meta/recipes-devtools/opkg/opkg/0003-opkg-set-locale-from-system-environment-variables.patch
@@ -0,0 +1,48 @@
+From 712895b1914bf63ee4d669863bfd106814329076 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Piotr=20=C5=81obacz?= 
+Date: Wed, 19 Jul 2023 21:26:09 +0200
+Subject: [PATCH] opkg: set locale from system environment variables
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+A C program inherits its locale environment variables when it starts up.
+This happens automatically. However, these variables do not automatically
+control the locale used by the library functions, because ISO C says that
+all programs start by default in the standard ‘C’ locale.
+
+Fixes warnings:
+Warning when reading ar archive header: Pathname can't be converted from UTF-8 
to current locale. (errno=84)
+
+Upstream-Status: Submitted 
[https://groups.google.com/g/opkg-devel/c/16kgZfJ26mQ]
+
+[1] https://www.gnu.org/software/libc/manual/html_node/Setting-the-Locale.html
+
+Signed-off-by: Piotr Łobacz 
+---
+ src/opkg.c | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/src/opkg.c b/src/opkg.c
+index 544c58a..0c729ff 100644
+--- a/src/opkg.c
 b/src/opkg.c
+@@ -27,6 +27,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ 
+ #include "opkg_conf.h"
+ #include "opkg_cmd.h"
+@@ -408,6 +409,7 @@ int main(int argc, char *argv[])
+ if (opkg_conf_init())
+ goto err0;
+ 
++setlocale(LC_ALL, "");
+ opkg_config->verbosity = NOTICE;
+ 
+ opts = args_parse(argc, argv);
+-- 
+2.34.1
+
diff --git a/meta/recipes-devtools/opkg/opkg_0.6.2.bb 
b/meta/recipes-devtools/opkg/opkg_0.6.2.bb
index d7dc6ab715..3b5d51d74a 100644
--- a/meta/recipes-devtools/opkg/opkg_0.6.2.bb
+++ b/meta/recipes-devtools/opkg/opkg_0.6.2.bb
@@ -16,6 +16,7 @@ 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://0002-Add-options-to-enable-support-for-acl-and-xattr.patch \
+   file://0003-opkg-set-locale-from-system-environment-variables.patch 
\
file://run-ptest \
"
 
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184692): 
https://lists.openembedded.org/g/openembedded-core/message/184692
Mute This Topic: https://lists.openembedded.org/mt/100275322/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 v7][master-next 2/5] package.bbclass: add support for ACLs and xattr

[Piotr Łobacz]

Extend `tar` command, with additional parameters, depending
on choosen package class and target distro features, in order
to support ACLs and xattr.

Currently only `package_ipk` supports fully ACLs and xattr.

Signed-off-by: Piotr Łobacz 
---
 meta/classes-global/package.bbclass | 9 +++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/meta/classes-global/package.bbclass 
b/meta/classes-global/package.bbclass
index e8055a9cdc..6e5d0dd4dc 100644
--- a/meta/classes-global/package.bbclass
+++ b/meta/classes-global/package.bbclass
@@ -342,8 +342,13 @@ python perform_packagecopy () {
 
 # Start by package population by taking a copy of the installed
 # files to operate on
-# Preserve sparse files and hard links
-cmd = 'tar --exclude=./sysroot-only -cf - -C %s -p -S . | tar -xf - -C %s' 
% (dest, dvar)
+# Preserve sparse files, hard links, ACLs and extended attributes
+# TODO: for the moment only ipk packages are supporting ACLs and extended 
attributes
+# we need to add support for other package systems as well, but that 
doesn't bother
+# tar from creating archives with acl and/or xattr support
+acl = bb.utils.contains('DISTRO_FEATURES', 'acl', '--acls', '', d)
+xattr = bb.utils.contains('DISTRO_FEATURES', 'xattr', '--xattrs', '', d)
+cmd = f'tar {acl} {xattr} --numeric-owner --exclude=./sysroot-only -cf - 
-C {dest} -p -S . | tar {acl} {xattr} -xf - -C {dvar}'
 subprocess.check_output(cmd, shell=True, stderr=subprocess.STDOUT)
 
 # replace RPATHs for the nativesdk binaries, to make them relocatable
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184689): 
https://lists.openembedded.org/g/openembedded-core/message/184689
Mute This Topic: https://lists.openembedded.org/mt/100275319/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 v7][master-next 4/5] opkg: add options to enable support for acl and xattr

[Piotr Łobacz]

The libarchive library, which is being used by opkg, supports ACLs
and xattr already.

More informations can be read at this link:
https://github.com/libarchive/libarchive/pull/691

Signed-off-by: Piotr Łobacz 
---
 ...-to-enable-support-for-acl-and-xattr.patch | 70 +++
 meta/recipes-devtools/opkg/opkg_0.6.2.bb  |  5 +-
 2 files changed, 74 insertions(+), 1 deletion(-)
 create mode 100644 
meta/recipes-devtools/opkg/opkg/0002-Add-options-to-enable-support-for-acl-and-xattr.patch

diff --git 
a/meta/recipes-devtools/opkg/opkg/0002-Add-options-to-enable-support-for-acl-and-xattr.patch
 
b/meta/recipes-devtools/opkg/opkg/0002-Add-options-to-enable-support-for-acl-and-xattr.patch
new file mode 100644
index 00..d6cb1d79fb
--- /dev/null
+++ 
b/meta/recipes-devtools/opkg/opkg/0002-Add-options-to-enable-support-for-acl-and-xattr.patch
@@ -0,0 +1,70 @@
+From 1c935e994bd572d9fff436f660ac1a060a434df0 Mon Sep 17 00:00:00 2001
+From: Maciej Liszewski 
+Date: Tue, 4 Jul 2023 22:01:58 +0200
+Subject: [PATCH] Add options to enable support for acl and xattr
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+The libarchive library, which is being used by opkg, supports ACLs
+and xattr already.
+
+More informations can be read at this link:
+https://github.com/libarchive/libarchive/pull/691
+
+Upstream-Status: Accepted 
[https://groups.google.com/g/opkg-devel/c/aEGL7XRXfaA]
+
+[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=15097
+
+Signed-off-by: Maciej Liszewski 
+Signed-off-by: Piotr Łobacz 
+---
+ configure.ac   | 12 
+ libopkg/opkg_archive.c |  8 
+ 2 files changed, 20 insertions(+)
+
+diff --git a/configure.ac b/configure.ac
+index 389a818..46949cd 100644
+--- a/configure.ac
 b/configure.ac
+@@ -158,6 +158,18 @@ return OPENSSL_VERSION_NUMBER; ],
+   AC_SUBST(OPENSSL_LIBS)
+ fi
+ 
++# check for ACL support
++AC_ARG_WITH([acl], [AS_HELP_STRING([--with-acl], [Enable ACL support])])
++if test "x$with_acl" = "xyes"; then
++  AC_DEFINE([ENABLE_ACL], [1], [Enable ACL support])
++fi
++
++# check for xattr support
++AC_ARG_WITH([xattr], [AS_HELP_STRING([--with-xattr], [Enable xattr support])])
++if test "x$with_xattr" = "xyes"; then
++  AC_DEFINE([ENABLE_XATTR], [1], [Enable xattr support])
++fi
++
+ # check for libsolv solver
+ AC_ARG_WITH(libsolv, AC_HELP_STRING([--with-libsolv], [Use libsolv solver 
support.
+   ]), [], [with_libsolv="no"])
+diff --git a/libopkg/opkg_archive.c b/libopkg/opkg_archive.c
+index 03a4afb..8dd902d 100644
+--- a/libopkg/opkg_archive.c
 b/libopkg/opkg_archive.c
+@@ -912,6 +912,14 @@ struct opkg_ar *ar_open_pkg_data_archive(const char 
*filename)
+ ar->extract_flags = ARCHIVE_EXTRACT_OWNER | ARCHIVE_EXTRACT_PERM |
+ ARCHIVE_EXTRACT_TIME | ARCHIVE_EXTRACT_UNLINK | 
ARCHIVE_EXTRACT_NO_OVERWRITE;
+ 
++#ifdef ENABLE_ACL
++ar->extract_flags |= ARCHIVE_EXTRACT_ACL;
++#endif
++
++#ifdef ENABLE_XATTR
++ar->extract_flags |= ARCHIVE_EXTRACT_FFLAGS | ARCHIVE_EXTRACT_XATTR;
++#endif
++
+ if (opkg_config->ignore_uid)
+ ar->extract_flags &= ~ARCHIVE_EXTRACT_OWNER;
+ 
+-- 
+2.34.1
+
diff --git a/meta/recipes-devtools/opkg/opkg_0.6.2.bb 
b/meta/recipes-devtools/opkg/opkg_0.6.2.bb
index 46be137354..d7dc6ab715 100644
--- a/meta/recipes-devtools/opkg/opkg_0.6.2.bb
+++ b/meta/recipes-devtools/opkg/opkg_0.6.2.bb
@@ -15,6 +15,7 @@ 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://0002-Add-options-to-enable-support-for-acl-and-xattr.patch \
file://run-ptest \
"
 
@@ -30,8 +31,10 @@ inherit autotools pkgconfig ptest
 target_localstatedir := "${localstatedir}"
 OPKGLIBDIR ??= "${target_localstatedir}/lib"
 
-PACKAGECONFIG ??= "libsolv"
+PACKAGECONFIG ??= "libsolv ${@bb.utils.filter('DISTRO_FEATURES', 'acl xattr', 
d)}"
 
+PACKAGECONFIG[acl] = "--with-acl,--without-acl"
+PACKAGECONFIG[xattr] = "--with-xattr,--without-xattr"
 PACKAGECONFIG[gpg] = "--enable-gpg,--disable-gpg,\
 gnupg gpgme libgpg-error,\
 ${@ "gnupg" if ("native" in d.getVar("PN")) else "gnupg-gpg"}\
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184691): 
https://lists.openembedded.org/g/openembedded-core/message/184691
Mute This Topic: https://lists.openembedded.org/mt/100275321/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 v7][master-next 1/5] package_ipk.bbclass: add support for ACLs and xattr

[Piotr Łobacz]

Extend OPKGBUILDCMD variable, with additional parameters, depending
on target distro features, in order to support ACLs and xattr.

With fix pushed to the opkg-devel:
https://groups.google.com/g/opkg-devel/c/dYNHrLjDwg8
opkg-build is able to create tar archives with ACLs and xattr.

Signed-off-by: Piotr Łobacz 
---
 meta/classes-global/package_ipk.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes-global/package_ipk.bbclass 
b/meta/classes-global/package_ipk.bbclass
index b4b7bc9ac2..5e151be3cd 100644
--- a/meta/classes-global/package_ipk.bbclass
+++ b/meta/classes-global/package_ipk.bbclass
@@ -15,7 +15,7 @@ IPKGCONF_SDK_TARGET = "${WORKDIR}/opkg-sdk-target.conf"
 PKGWRITEDIRIPK = "${WORKDIR}/deploy-ipks"
 
 # Program to be used to build opkg packages
-OPKGBUILDCMD ??= 'opkg-build -Z xz -a "${XZ_DEFAULTS}"'
+OPKGBUILDCMD ??= 'opkg-build -Z xz -a "${XZ_DEFAULTS}" 
"${@bb.utils.contains('DISTRO_FEATURES', 'acl', '-A', '', d)}" 
"${@bb.utils.contains('DISTRO_FEATURES', 'xattr', '-X', '', d)}"'
 
 OPKG_ARGS += "--force_postinstall --prefer-arch-to-version"
 OPKG_ARGS += "${@['', 
'--no-install-recommends'][d.getVar("NO_RECOMMENDATIONS") == "1"]}"
-- 
2.34.1


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

Re: ODP: [OE-Core][PATCH v6 1/6] bitbake.conf: add acl and xattr distro native features support

[Alexandre Belloni via lists.openembedded.org]

On 21/07/2023 11:23:10+, Piotr Łobacz wrote:
> OK do you want it to be on top of 
> openembedded-core-contrib/origin/abelloni/master-next or just 
> openembedded-core/master-next?

Now that the opkg upgrade had been merged in master, you can rebase on
top of master.

> 
> Od: openembedded-core@lists.openembedded.org 
>  w imieniu użytkownika Piotr Łobacz 
> via lists.openembedded.org 
> Wysłane: piątek, 21 lipca 2023 11:31
> Do: Alexandre Belloni 
> DW: openembedded-core@lists.openembedded.org 
> 
> Temat: Re: [OE-Core][PATCH v6 1/6] bitbake.conf: add acl and xattr distro 
> native features support
> 
> Yes but within an hour?
> 
> Wysyłane z aplikacji Outlook dla systemu iOS
> 
> Od: Alexandre Belloni 
> Wysłane: Friday, July 21, 2023 11:30:54 AM
> Do: Piotr Łobacz 
> DW: openembedded-core@lists.openembedded.org 
> 
> Temat: Re: [OE-Core][PATCH v6 1/6] bitbake.conf: add acl and xattr distro 
> native features support
> 
> Hello,
> 
> I want to give this a shot again, can you rebase on top of my
> master-next branch ?
> 
> On 19/07/2023 21:48:38+0200, Piotr Łobacz wrote:
> > Include support for ACLs and extended file attributes for native
> > builds, by default.
> >
> > Signed-off-by: Piotr Łobacz 
> > ---
> >  meta/conf/bitbake.conf | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> > index 9625a6fef4..8dd615 100644
> > --- a/meta/conf/bitbake.conf
> > +++ b/meta/conf/bitbake.conf
> > @@ -904,7 +904,7 @@ IMAGE_FEATURES += "${EXTRA_IMAGE_FEATURES}"
> >
> >  # Native distro features (will always be used for -native, even if they
> >  # are not enabled for target)
> > -DISTRO_FEATURES_NATIVE ?= "x11 ipv6 xattr"
> > +DISTRO_FEATURES_NATIVE ?= "acl x11 ipv6 xattr"
> >  DISTRO_FEATURES_NATIVESDK ?= "x11"
> >
> >  # Normally target distro features will not be applied to native builds:
> > --
> > 2.34.1
> >
> 
> >
> >
> >
> 
> 
> --
> Alexandre Belloni, co-owner and COO, Bootlin
> Embedded Linux and Kernel engineering
> https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbootlin.com%2F&data=05%7C01%7Cp.lobacz%40welotec.com%7C2fcf33853c84429feb0708db89cd2f44%7C25111a7f1d5a4c51a4ca7f8e44011b39%7C0%7C0%7C638255286582480321%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VzoZv0Pjtc0D2%2FwMEi32VYkRde7xvWr4b5hHMopFJN0%3D&reserved=0

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184687): 
https://lists.openembedded.org/g/openembedded-core/message/184687
Mute This Topic: https://lists.openembedded.org/mt/100274821/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] kirkstone boost upgrade?

[Ross Burton]

On 21 Jul 2023, at 09:25, Thomas Roos via lists.openembedded.org 
 wrote:
> 
> Hi Vyacheslav,
> I think it's this error: boost beast "Fixed WebSocket handshake response on 
> failure."
> Fixed in 1.79.
> My question was what is the policy of upgrading boost in an LTS branch? I 
> guess there is no change?
> I totally agree that there are breaking changes - I had experienced a lot in 
> the past...

If you can isolate the fix to a small patch that doesn’t break anything else, 
then you can submit that as a patch.  If it needs to be an invasive upgrade, 
that’s less likely to happen.

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

ODP: [OE-Core][PATCH v6 1/6] bitbake.conf: add acl and xattr distro native features support

[Piotr Łobacz]

OK do you want it to be on top of 
openembedded-core-contrib/origin/abelloni/master-next or just 
openembedded-core/master-next?

Od: openembedded-core@lists.openembedded.org 
 w imieniu użytkownika Piotr Łobacz 
via lists.openembedded.org 
Wysłane: piątek, 21 lipca 2023 11:31
Do: Alexandre Belloni 
DW: openembedded-core@lists.openembedded.org 

Temat: Re: [OE-Core][PATCH v6 1/6] bitbake.conf: add acl and xattr distro 
native features support

Yes but within an hour?

Wysyłane z aplikacji Outlook dla systemu iOS

Od: Alexandre Belloni 
Wysłane: Friday, July 21, 2023 11:30:54 AM
Do: Piotr Łobacz 
DW: openembedded-core@lists.openembedded.org 

Temat: Re: [OE-Core][PATCH v6 1/6] bitbake.conf: add acl and xattr distro 
native features support

Hello,

I want to give this a shot again, can you rebase on top of my
master-next branch ?

On 19/07/2023 21:48:38+0200, Piotr Łobacz wrote:
> Include support for ACLs and extended file attributes for native
> builds, by default.
>
> Signed-off-by: Piotr Łobacz 
> ---
>  meta/conf/bitbake.conf | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index 9625a6fef4..8dd615 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -904,7 +904,7 @@ IMAGE_FEATURES += "${EXTRA_IMAGE_FEATURES}"
>
>  # Native distro features (will always be used for -native, even if they
>  # are not enabled for target)
> -DISTRO_FEATURES_NATIVE ?= "x11 ipv6 xattr"
> +DISTRO_FEATURES_NATIVE ?= "acl x11 ipv6 xattr"
>  DISTRO_FEATURES_NATIVESDK ?= "x11"
>
>  # Normally target distro features will not be applied to native builds:
> --
> 2.34.1
>

>
>
>


--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbootlin.com%2F&data=05%7C01%7Cp.lobacz%40welotec.com%7C2fcf33853c84429feb0708db89cd2f44%7C25111a7f1d5a4c51a4ca7f8e44011b39%7C0%7C0%7C638255286582480321%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VzoZv0Pjtc0D2%2FwMEi32VYkRde7xvWr4b5hHMopFJN0%3D&reserved=0

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

[OE-core] [yocto][bitbake] variable expansion in files

[Corey Cothrum]

Can confirm that no attempt or submission was made to merge
meta-bitbake-variable-substitution into mainline/core. I'm happy if people
are finding it useful, but it was written very much for my use case(s). I
didn't spend much time designing it or thinking through how other people
may prefer it to work. Not to disparage it; I just mean to say there is
likely room for improvement.

Ross is also correct that automatic expansion shouldn't be the only mode of
operation. That's why meta-bitbake-variable-substitution has the option to
specify search and replace file paths:

${@bitbake_variables_search_and_sub("${PATH_OR_FILE_TO_PROCESS}",
r"${BITBAKE_VAR_SUB_DELIM}", d)}


I found cases where it was attempting variable substitution where I didn't
want it (e.g. when appending a recipe), and needed a method to be a bit
more surgical.

thanks,
Corey

On Fri, Jul 21, 2023 at 4:39 AM Ross Burton  wrote:

> On 21 Jul 2023, at 10:24, Yann CARDAILLAC via lists.openembedded.org
>  wrote:
> > There's something that has always been missing in my experience of
> Yocto, it's the ability to simply configure files with yocto variables.
> >
> > Basically the idea is to have a class that will automatically sed all
> variables from yocto inside a file using a delimiter, or to reuse the way
> it is done with .wks.in with the ${var} syntax, even if I can already see
> some limitations with shell scripts.
> >
> > What I intend to do is to provide some variables to a recipe and then to
> use them to complete a template.
> >
> > For instance I'd like to put some stuff inside my machine.conf and want
> those variables to be filled inside my templated script.
> >
> > Is there any official way to do this?
> >
> > As far as I can see there's not, the only examples I've found are using
> hand made seds. But I might not be looking in the right place.
> >
> > If I'm right, I'm wondering why this is not generalized inside a poky
> class. I've found this meta :
> https://github.com/coreycothrum/meta-bitbake-variable-substitution doing
> exactly what I needed, but since it's not mainline I assume that as always
> there's a good reason why it's not something you want to have in mainline.
> >
> > If that's only because there wasn't any submission and If you're up for
> it going mainline, I can work (with coreycothrum if he wants to?) it
> through the patch submission process.
>
> There’s also a class that I hacked up a while ago that I never finished
> because I wanted to automatically handle variable dependencies, otherwise
> it’s no good:
>
> https://github.com/rossburton/meta-ross/blob/master/classes/bbin.bbclass
>
> I’d like to see something in core, but the scope should be relatively
> tight.  I don’t like the automatic expansion that
> meta-bitbake-variable-substitution does, I’m thinking of a pathological
> case where piglit wanted to use @@bindir@@ in a wrapper script: it would
> also attempt to process many gigabytes of installed files.
>
> The bbin class _only_ works on files in SRC_URI, so foo.sh.bbin would be
> processed at do_unpack and end up in WORKDIR/foo.sh.  The scope is more
> limited but you know exactly what it’s doing.
>
> Ross

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184684): 
https://lists.openembedded.org/g/openembedded-core/message/184684
Mute This Topic: https://lists.openembedded.org/mt/100273728/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] scripts/resulttool: add mention about new detected tests

[Alexis Lothoré via lists . openembedded . org]

From: Alexis Lothoré 

Some regression reports show a lot of "PASSED->None" transitions. When such
big lot of identical transitions are observed, it could be that tests are
now failing, but it could also be that some tests has been renamed.

To detect such case, add a log in regression report to report the number of
new tests (i.e: tests that are present in target results but not in base
result). This new log also allows to know about newly added tests bases

Signed-off-by: Alexis Lothoré 
---
This commit is a follow-up to [1], which discusses the issue with the
regression report from 4.3_M2 build.
A example of this regression report being updated with the "newly added
tests count" log can be found here: [2]

[1] 
https://lore.kernel.org/yocto/e7e05ead7e1740041e7633d71943345460472964.ca...@linuxfoundation.org/
[2] https://pastebin.com/WQdgrpA0
---
 scripts/lib/resulttool/regression.py | 16 ++--
 1 file changed, 14 insertions(+), 2 deletions(-)

diff --git a/scripts/lib/resulttool/regression.py 
b/scripts/lib/resulttool/regression.py
index 1facbcd85e1e..f80a9182a9a9 100644
--- a/scripts/lib/resulttool/regression.py
+++ b/scripts/lib/resulttool/regression.py
@@ -178,6 +178,8 @@ def compare_result(logger, base_name, target_name, 
base_result, target_result):
 base_result = base_result.get('result')
 target_result = target_result.get('result')
 result = {}
+new_tests = 0
+
 if base_result and target_result:
 for k in base_result:
 base_testcase = base_result[k]
@@ -189,6 +191,13 @@ def compare_result(logger, base_name, target_name, 
base_result, target_result):
 result[k] = {'base': base_status, 'target': target_status}
 else:
 logger.error('Failed to retrieved base test case status: %s' % 
k)
+
+# Also count new tests that were not present in base results: it
+# could be newly added tests, but it could also highlights some tests
+# renames or fixed faulty ptests
+for k in target_result:
+if k not in base_result:
+new_tests += 1
 if result:
 new_pass_count = sum(test['target'] is not None and 
test['target'].startswith("PASS") for test in result.values())
 # Print a regression report only if at least one test has a regression 
status (FAIL, SKIPPED, absent...)
@@ -200,10 +209,13 @@ def compare_result(logger, base_name, target_name, 
base_result, target_result):
 if new_pass_count > 0:
 resultstring += f'Additionally, {new_pass_count} 
previously failing test(s) is/are now passing\n'
 else:
-resultstring = "Improvement: %s\n %s\n 
(+%d test(s) passing)" % (base_name, target_name, new_pass_count)
+resultstring = "Improvement: %s\n %s\n 
(+%d test(s) passing)\n" % (base_name, target_name, new_pass_count)
 result = None
 else:
-resultstring = "Match:   %s\n %s" % (base_name, 
target_name)
+resultstring = "Match:   %s\n %s\n" % (base_name, 
target_name)
+
+if new_tests > 0:
+resultstring += f'Additionally, {new_tests} new test(s) is/are 
present\n'
 return result, resultstring
 
 def get_results(logger, source):
-- 
2.41.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184683): 
https://lists.openembedded.org/g/openembedded-core/message/184683
Mute This Topic: https://lists.openembedded.org/mt/100274589/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] mdadm: add util-linux-blockdev ptest dependency

[Ovidiu Panait via lists.openembedded.org]

From: Ovidiu Panait 

07revert-inplace test logs contain the following:
func.sh: line 335: /sbin/blockdev: No such file or directory

Add the missing util-linux-blockdev dependency.

Signed-off-by: Ovidiu Panait 
---
 meta/recipes-extended/mdadm/mdadm_4.2.bb | 9 -
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-extended/mdadm/mdadm_4.2.bb 
b/meta/recipes-extended/mdadm/mdadm_4.2.bb
index 50d9548747..fa50325f1f 100644
--- a/meta/recipes-extended/mdadm/mdadm_4.2.bb
+++ b/meta/recipes-extended/mdadm/mdadm_4.2.bb
@@ -107,7 +107,14 @@ do_install_ptest() {
 }
 
 RDEPENDS:${PN} += "bash"
-RDEPENDS:${PN}-ptest += "bash e2fsprogs-mke2fs util-linux-lsblk 
util-linux-losetup strace"
+RDEPENDS:${PN}-ptest += " \
+bash \
+e2fsprogs-mke2fs \
+util-linux-lsblk \
+util-linux-losetup \
+util-linux-blockdev \
+strace \
+"
 RRECOMMENDS:${PN}-ptest += " \
 coreutils \
 kernel-module-loop \
-- 
2.39.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184682): 
https://lists.openembedded.org/g/openembedded-core/message/184682
Mute This Topic: https://lists.openembedded.org/mt/100274537/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] [yocto][bitbake] variable expansion in files

[Ross Burton]

On 21 Jul 2023, at 10:24, Yann CARDAILLAC via lists.openembedded.org 
 wrote:
> There's something that has always been missing in my experience of Yocto, 
> it's the ability to simply configure files with yocto variables.
> 
> Basically the idea is to have a class that will automatically sed all 
> variables from yocto inside a file using a delimiter, or to reuse the way it 
> is done with .wks.in with the ${var} syntax, even if I can already see some 
> limitations with shell scripts.
> 
> What I intend to do is to provide some variables to a recipe and then to use 
> them to complete a template. 
> 
> For instance I'd like to put some stuff inside my machine.conf and want those 
> variables to be filled inside my templated script.
> 
> Is there any official way to do this?
> 
> As far as I can see there's not, the only examples I've found are using hand 
> made seds. But I might not be looking in the right place.
> 
> If I'm right, I'm wondering why this is not generalized inside a poky class. 
> I've found this meta : 
> https://github.com/coreycothrum/meta-bitbake-variable-substitution doing 
> exactly what I needed, but since it's not mainline I assume that as always 
> there's a good reason why it's not something you want to have in mainline.
> 
> If that's only because there wasn't any submission and If you're up for it 
> going mainline, I can work (with coreycothrum if he wants to?) it through the 
> patch submission process.

There’s also a class that I hacked up a while ago that I never finished because 
I wanted to automatically handle variable dependencies, otherwise it’s no good:

https://github.com/rossburton/meta-ross/blob/master/classes/bbin.bbclass

I’d like to see something in core, but the scope should be relatively tight.  I 
don’t like the automatic expansion that meta-bitbake-variable-substitution 
does, I’m thinking of a pathological case where piglit wanted to use @@bindir@@ 
in a wrapper script: it would also attempt to process many gigabytes of 
installed files.

The bbin class _only_ works on files in SRC_URI, so foo.sh.bbin would be 
processed at do_unpack and end up in WORKDIR/foo.sh.  The scope is more limited 
but you know exactly what it’s doing.

Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184681): 
https://lists.openembedded.org/g/openembedded-core/message/184681
Mute This Topic: https://lists.openembedded.org/mt/100273728/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 v6 1/6] bitbake.conf: add acl and xattr distro native features support

[Piotr Łobacz]

Yes but within an hour?

Wysyłane z aplikacji Outlook dla systemu iOS

Od: Alexandre Belloni 
Wysłane: Friday, July 21, 2023 11:30:54 AM
Do: Piotr Łobacz 
DW: openembedded-core@lists.openembedded.org 

Temat: Re: [OE-Core][PATCH v6 1/6] bitbake.conf: add acl and xattr distro 
native features support

Hello,

I want to give this a shot again, can you rebase on top of my
master-next branch ?

On 19/07/2023 21:48:38+0200, Piotr Łobacz wrote:
> Include support for ACLs and extended file attributes for native
> builds, by default.
>
> Signed-off-by: Piotr Łobacz 
> ---
>  meta/conf/bitbake.conf | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index 9625a6fef4..8dd615 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -904,7 +904,7 @@ IMAGE_FEATURES += "${EXTRA_IMAGE_FEATURES}"
>
>  # Native distro features (will always be used for -native, even if they
>  # are not enabled for target)
> -DISTRO_FEATURES_NATIVE ?= "x11 ipv6 xattr"
> +DISTRO_FEATURES_NATIVE ?= "acl x11 ipv6 xattr"
>  DISTRO_FEATURES_NATIVESDK ?= "x11"
>
>  # Normally target distro features will not be applied to native builds:
> --
> 2.34.1
>

>
> 
>


--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbootlin.com%2F&data=05%7C01%7Cp.lobacz%40welotec.com%7C2fcf33853c84429feb0708db89cd2f44%7C25111a7f1d5a4c51a4ca7f8e44011b39%7C0%7C0%7C638255286582480321%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VzoZv0Pjtc0D2%2FwMEi32VYkRde7xvWr4b5hHMopFJN0%3D&reserved=0

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184680): 
https://lists.openembedded.org/g/openembedded-core/message/184680
Mute This Topic: https://lists.openembedded.org/mt/100242732/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 v6 1/6] bitbake.conf: add acl and xattr distro native features support

[Alexandre Belloni via lists.openembedded.org]

Hello,

I want to give this a shot again, can you rebase on top of my
master-next branch ?

On 19/07/2023 21:48:38+0200, Piotr Łobacz wrote:
> Include support for ACLs and extended file attributes for native
> builds, by default.
> 
> Signed-off-by: Piotr Łobacz 
> ---
>  meta/conf/bitbake.conf | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index 9625a6fef4..8dd615 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -904,7 +904,7 @@ IMAGE_FEATURES += "${EXTRA_IMAGE_FEATURES}"
>  
>  # Native distro features (will always be used for -native, even if they
>  # are not enabled for target)
> -DISTRO_FEATURES_NATIVE ?= "x11 ipv6 xattr"
> +DISTRO_FEATURES_NATIVE ?= "acl x11 ipv6 xattr"
>  DISTRO_FEATURES_NATIVESDK ?= "x11"
>  
>  # Normally target distro features will not be applied to native builds:
> -- 
> 2.34.1
> 

> 
> 
> 


-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

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

[OE-core] [yocto][bitbake] variable expansion in files

[Yann CARDAILLAC]

Hi,

There's something that has always been missing in my experience of Yocto,
it's the ability to simply configure files with yocto variables.

Basically the idea is to have a class that will automatically sed all
variables from yocto inside a file using a delimiter, or to reuse the way
it is done with .wks.in with the ${var} syntax, even if I can already see
some limitations with shell scripts.

What I intend to do is to provide some variables to a recipe and then to
use them to complete a template.

For instance I'd like to put some stuff inside my machine.conf and want
those variables to be filled inside my templated script.

Is there any official way to do this?

As far as I can see there's not, the only examples I've found are using
hand made seds. But I might not be looking in the right place.

If I'm right, I'm wondering why this is not generalized inside a poky
class. I've found this meta :
https://github.com/coreycothrum/meta-bitbake-variable-substitution doing
exactly what I needed, but since it's not mainline I assume that as always
there's a good reason why it's not something you want to have in mainline.

If that's only because there wasn't any submission and If you're up for it
going mainline, I can work (with coreycothrum if he wants to?) it through
the patch submission process.

Best regards,

Yann CARDAILLAC,

Embedded Linux Engineer
Embedded Systems, Computer Science & Electronics, @Polytech Sorbone

Phone : +33669909858

Linkedin : https://www.linkedin.com/in/yann-c-39b64012b/
Website: https://ycardaillac.fr

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184678): 
https://lists.openembedded.org/g/openembedded-core/message/184678
Mute This Topic: https://lists.openembedded.org/mt/100273728/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] [RFC PATCH 0/4] Bump Protobuf/gRPC

[Clément Péron]

Hi Martin,

On Thu, 20 Jul 2023 at 18:38, Martin Jansa  wrote:

> These patches should be sent to openembedded-devel not openembedded-core.
>

Sorry about that. I will send the next version in the correct ML


> > ERROR: abseil-cpp-20230125.3-r0 do_package: Variable Requires:
> absl_config = 20230125, absl_core_headers = 20230125,
> absl_log_internal_append_truncated = 20230125, absl_log_internal_config =
> 20230125, absl_log_internal_globals = 20230125, absl_log_severity =
> 20230125, absl_strings = 20230125, absl_str_format = 20230125, absl_time =
> 20230125, absl_span  contains an operation using the old override syntax.
> Please convert this layer/metadata before attempting to use with a newer
> bitbake.
>
> Do you have this change in your build?
> https://lists.openembedded.org/g/openembedded-core/message/179019
>

No, thanks for pointing out this fix, I have proposed a backport to
kirkstone.

Regards,
Clement


>
> On Thu, Jul 20, 2023 at 6:25 PM Clément Péron 
> wrote:
>
>> Hi,
>>
>> I'm trying to bump gRPC to a more recent version,
>> but it requires a bump of protobuf.
>>
>> I'm strugling with the following issue when compiling:
>>
>> ERROR: abseil-cpp-20230125.3-r0 do_package: Variable Requires:
>> absl_config = 20230125, absl_core_headers = 20230125,
>> absl_log_internal_append_truncated = 20230125, absl_log_internal_config =
>> 20230125, absl_log_internal_globals = 20230125, absl_log_severity =
>> 20230125, absl_strings = 20230125, absl_str_format = 20230125, absl_time =
>> 20230125, absl_span  contains an operation using the old override syntax.
>> Please convert this layer/metadata before attempting to use with a newer
>> bitbake.
>> ERROR: Logfile of failure stored in:
>> /build/tmp/work/armv8a-poky-linux/abseil-cpp/20230125.3-r0/temp/log.do_package.2192204
>> ERROR: Task
>> (/build/../meta-outsight/recipes-devtools/abseil-cpp/abseil-cpp_git.bb:do_package)
>> failed with exit code '1'
>>
>> Do you have an idea of what is happening?
>>
>> Thanks for your help
>>
>> Clément Péron (4):
>>   jsoncpp: extend with nativesdk
>>   devtools: protobuf: add utf8-range recipe
>>   protobuf: bump to 3.23.4
>>   devtools: grpc: bump to 1.56.2
>>
>>  ...RPCPP_ABSEIL_SYNC-to-GPR_ABSEIL_SYNC.patch | 62 -
>>  ...d-separate-export-for-plugin-targets.patch | 93 ---
>>  .../grpc/{grpc_1.50.1.bb => grpc_1.56.2.bb}   |  6 +-
>>  .../recipes-devtools/jsoncpp/jsoncpp_1.9.5.bb |  2 +-
>>  .../0001-Fix-linking-error-with-ld-gold.patch | 69 --
>>  ...e-respect-CXX-LDFLAGS-variables-fix-.patch |  4 +-
>>  ...protobuf_3.21.12.bb => protobuf_3.23.4.bb} |  8 +-
>>  .../protobuf/utf8-range_git.bb| 22 +
>>  8 files changed, 32 insertions(+), 234 deletions(-)
>>  delete mode 100644
>> meta-oe/recipes-devtools/grpc/grpc/0001-Revert-Changed-GRPCPP_ABSEIL_SYNC-to-GPR_ABSEIL_SYNC.patch
>>  delete mode 100644
>> meta-oe/recipes-devtools/grpc/grpc/0001-cmake-add-separate-export-for-plugin-targets.patch
>>  rename meta-oe/recipes-devtools/grpc/{grpc_1.50.1.bb => grpc_1.56.2.bb}
>> (92%)
>>  delete mode 100644
>> meta-oe/recipes-devtools/protobuf/protobuf/0001-Fix-linking-error-with-ld-gold.patch
>>  rename meta-oe/recipes-devtools/protobuf/{protobuf_3.21.12.bb =>
>> protobuf_3.23.4.bb} (95%)
>>  create mode 100644 meta-oe/recipes-devtools/protobuf/utf8-range_git.bb
>>
>> --
>> 2.41.0
>>
>>
>> 
>>
>>

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

[OE-core] [kirkstone][PATCH] package.bbclass: moving field data process before variable process in process_pkgconfig

[Clément Péron]

From: Xiangyu Chen 

Currently, the latest version abseil-cpp contains a new library named 
"absl_log_internal_format", it's
basic package config(.pc file) as below:

prefix=/usr
exec_prefix=${prefix}

..

Requires: absl_config = 20230125, absl_core_headers = 20230125, 
absl_log_internal_append_truncated = 20230125,
absl_log_internal_config = 20230125, absl_log_internal_globals = 20230125, 
absl_log_severity = 20230125,
absl_strings = 20230125, absl_str_format = 20230125, absl_time = 20230125, 
absl_span = 20230125
..

Normally, the process_pkgconfig() would process variable data before field data 
in a .pc file, but in the
absl_log_internal_format, the field data in "Requires" section contains " = 
" format, the
process_pkgconfig() treats them as normal variable and using the setVar() in 
bitbake's data_smart.py
try to process. The absl_log_internal_format field data contains "_append_", 
this hit the setVar() checking
and finally bitbake stop building and reporting an error as below:

"Variable xxx contains an operation using the old override syntax. Please 
convert this layer/metadata before attempting to use with a newer bitbake."

This patch move the field data process before variable process to avoid the 
process_pkgconfig() treat the field
data as variable.

Signed-off-by: Xiangyu Chen 
(cherry picked from commit a73e269d3e591a10bb397b94b82e3fb960112d33)
Signed-off-by: Clément Péron 
---
 meta/classes/package.bbclass | 12 ++--
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass
index e3f0a7060b..433bc3dc4d 100644
--- a/meta/classes/package.bbclass
+++ b/meta/classes/package.bbclass
@@ -2090,18 +2090,18 @@ python package_do_pkgconfig () {
 with open(file, 'r') as f:
 lines = f.readlines()
 for l in lines:
-m = var_re.match(l)
-if m:
-name = m.group(1)
-val = m.group(2)
-pd.setVar(name, pd.expand(val))
-continue
 m = field_re.match(l)
 if m:
 hdr = m.group(1)
 exp = pd.expand(m.group(2))
 if hdr == 'Requires':
 pkgconfig_needed[pkg] += exp.replace(',', ' 
').split()
+continue
+m = var_re.match(l)
+if m:
+name = m.group(1)
+val = m.group(2)
+pd.setVar(name, pd.expand(val))
 
 for pkg in packages.split():
 pkgs_file = os.path.join(shlibswork_dir, pkg + ".pclist")
-- 
2.41.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184676): 
https://lists.openembedded.org/g/openembedded-core/message/184676
Mute This Topic: https://lists.openembedded.org/mt/100273532/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] kirkstone boost upgrade?

[Thomas Roos via lists.openembedded.org]

Hi Vyacheslav,
I think it's this error: boost beast "Fixed WebSocket handshake response on 
failure."
Fixed in 1.79.
My question was what is the policy of upgrading boost in an LTS branch? I guess 
there is no change?
I totally agree that there are breaking changes - I had experienced a lot in 
the past...
Cheers, Thomas


Von: Vyacheslav Yurkov 
Gesendet: Freitag, 21. Juli 2023 08:07:32
An: Roos, Thomas; openembedded-core@lists.openembedded.org
Betreff: RE: [EXTERNAL][OE-core] kirkstone boost upgrade?


CAUTION: This email originated from outside of the organization. Do not click 
links or open attachments unless you can confirm the sender and know the 
content is safe.


I would be cautious with boost upgrade in stable branch.

Boost is known for having breaking changes almost each new version. I only had 
a glance at 1.79-1.81 https://www.boost.org/users/history/ and there are a 
couple of them.

Are you affected by some particular bug or vulnerability in 1.78?

Vyacheslav

On 21.07.2023 06:49, Thomas Roos via lists.openembedded.org wrote:

Hi,
we are hitting an issue with boost version 1.78 and like to ask if and how 
there is a boost upgrade on kirkstone branch?
Cheers, Thomas



Amazon Web Services EMEA SARL
38 avenue John F. Kennedy, L-1855 Luxembourg
Sitz der Gesellschaft: L-1855 Luxemburg
eingetragen im Luxemburgischen Handelsregister unter R.C.S. B186284

Amazon Web Services EMEA SARL, Niederlassung Deutschland
Marcel-Breuer-Str. 12, D-80807 Muenchen
Sitz der Zweigniederlassung: Muenchen
eingetragen im Handelsregister des Amtsgerichts Muenchen unter HRB 242240, 
USt-ID DE317013094





Amazon Web Services EMEA SARL
38 avenue John F. Kennedy, L-1855 Luxembourg
Sitz der Gesellschaft: L-1855 Luxemburg
eingetragen im Luxemburgischen Handelsregister unter R.C.S. B186284

Amazon Web Services EMEA SARL, Niederlassung Deutschland
Marcel-Breuer-Str. 12, D-80807 Muenchen
Sitz der Zweigniederlassung: Muenchen
eingetragen im Handelsregister des Amtsgerichts Muenchen unter HRB 242240, 
USt-ID DE317013094




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184675): 
https://lists.openembedded.org/g/openembedded-core/message/184675
Mute This Topic: https://lists.openembedded.org/mt/100271099/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] kirkstone boost upgrade?

[Martin Jansa]

For this purpose @LGE we're using meta-webos-backports layers for various
backports we need as in:
https://github.com/webosose/meta-webosose/tree/master/meta-webos-backports
https://github.com/webosose/meta-webosose/commits/master/meta-webos-backports

So we can easily just drop the layers whenever upgrading to newer Yocto
release.

I think it's easier and much faster than creating new mixing branch - for
recipes where it's not clear that multiple projects would need the backport
(like this unspecified issue in boost) and where the recipes can be easily
just copied to older release with minimal or no changes at all (so there is
no significant afford duplicated by multiple projects).

Regards,

On Fri, Jul 21, 2023 at 8:30 AM Christian Eggers  wrote:

> On Friday, 21 July 2023, 06:49:24 CEST, Thomas Roos via
> lists.openembedded.org wrote:
> > Hi,
> > we are hitting an issue with boost version 1.78 and like to ask if and
> how there is a boost upgrade on kirkstone branch?
>
> Another option:
>
> Yesterday there were two posts on the d...@yoctoproject.org list about
> "mixin" layers [1][2].
> There is already an own repository for this [3].
>
> So the best option seems to be creating a branch like "kirkstone/boost"
> (for latest boost
> release) or "kirkstone/boost-1.82" (for a specific boost release).
>
> It looks like patches for the meta-lts-mixin layer should be posted to
> [4]. Searching for
> "mixin" on the web interface shows some example messages. If you could put
> me on CC, I am
> happy to test your patches.
>
> regards
> Christian
>
>
> [1] https://lists.yoctoproject.org/g/docs/message/4073
> [2] https://lists.yoctoproject.org/g/docs/message/4074
> [3] https://git.yoctoproject.org/meta-lts-mixins/
> [4] https://lists.yoctoproject.org/g/yocto/topics
>
>
>
> ___​
> Christian
> Eggers
> Software Engineer
> ​
> ARRI
> Arnold & Richter Cine Technik GmbH & Co. Betriebs KG
> Arriweg 17 ,
> 83071
> Stephanskirchen
> www.arri.com
>
> 
> +49 8036 3009-3118 <+49%208036%203009-3118>
> cegg...@arri.de
>
> ​
> [image: CCM1 Camera Control Monitor]
> 
> Get all the latest information from www.arri.com, Facebook
> , Twitter
> , Instagram
> , LinkedIn
>  and YouTube
> .
>
> Arnold & Richter Cine Technik GmbH & Co. Betriebs KG
>
> Sitz: München ‑ Registergericht: Amtsgericht München ‑ Handelsregisternummer: 
> HRA 57918
> Persönlich haftender Gesellschafter: Arnold & Richter Cine Technik GmbH
>
> Sitz: München ‑ Registergericht: Amtsgericht München ‑ Handelsregisternummer: 
> HRB 54477
>
> Geschäftsführer: Dr. Matthias Erb (Chairman); Lars Weyer; Stephan Schenk; 
> Walter Trauninger
>
> ​
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184674): 
https://lists.openembedded.org/g/openembedded-core/message/184674
Mute This Topic: https://lists.openembedded.org/mt/100271099/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] file: return wrapper to fix builds when file is in buildtools-tarball

[Oleksiy Obitotskyy via lists.openembedded.org]

From: Oleksandr Hnatiuk 

Wrapper that adds proper path to magic file was removed in
47db876d09d9a4394048579c21d0b394450ce681 in favor of
environment-setup.d/file.sh which now contains `MAGIC` environment variable.
This breaks builds that rely on external buildtools with `file` included in
buildtools-tarball (e.g. via TOOLCHAIN_HOST_TASK) because do_populate_sysroot
task invokes `file` via `subprocess.check_output` (in is_elf function) and
doesn't use variables from files in environment-setup.d. To address this use
case, we need to preserve the wrapper, but also have
environment-setup.d/file.sh for the purposes described in
47db876d09d9a4394048579c21d0b394450ce681.

Signed-off-by: Oleksandr Hnatiuk 
---
 meta/recipes-devtools/file/file_5.44.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-devtools/file/file_5.44.bb 
b/meta/recipes-devtools/file/file_5.44.bb
index 3090d346ed4f..08343842307c 100644
--- a/meta/recipes-devtools/file/file_5.44.bb
+++ b/meta/recipes-devtools/file/file_5.44.bb
@@ -45,6 +45,7 @@ do_install:append:class-native() {
 }
 
 do_install:append:class-nativesdk() {
+   create_wrapper ${D}/${bindir}/file MAGIC=${datadir}/misc/magic.mgc
mkdir -p ${D}${SDKPATHNATIVE}/environment-setup.d
cat <<- EOF > ${D}${SDKPATHNATIVE}/environment-setup.d/file.sh
export MAGIC="$OECORE_NATIVE_SYSROOT${datadir}/misc/magic.mgc"
-- 
2.35.6


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184673): 
https://lists.openembedded.org/g/openembedded-core/message/184673
Mute This Topic: https://lists.openembedded.org/mt/100273158/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][kirkstone][PATCH] json-c: disable -Werror for x86-64

[Rouven Czerwinski]

Hi,

On Thu, 20 Jul 2023 20:45:44 +0200
"Alexander Kanavin"  wrote:

> Also, does the issue occur on oe-core master?
> 

I couldn't reproduce on amster.

> Alex
> 
> On Thu, 20 Jul 2023 at 20:44, Alexander Kanavin
>  wrote:
> >
> > This needs to be reported upstream and the ticket linked (ideally,
> > develop a patch to fix the issue). The tweak needs to be
> > :class-native only.

And with a fresh container and only oe-core+bitbake I couldn't
reproduce this on kirkstone either.

Turns out the BSP I was working had ICECC enabled and json-c-native is
broken on ICECC. Apparently I was holding ICECC_RECIPE_DISABLE wrong,
since it works with ICECC_RECIPE_DISABLE += "json-c-native". I'll send a
patch for that instead.

In conclusion: please ignore this patch.

Thanks for the comments that nudged me to check this again!

Best regards,
Rouven

> >
> > Alex
> >
> > On Thu, 20 Jul 2023 at 15:37, Rouven Czerwinski
> >  wrote:  
> > >
> > > From: Rouven Czerwinski 
> > >
> > > Disable -Werror using OECMAKE_C_FLAGS on x86-64. This ensures
> > > that json-c can build on newer distributions where the host
> > > compiler is new enough to treat implicit fallthrough warnings as
> > > errors: | NOTE: VERBOSE=1 cmake --build
> > > /…/work/x86_64-linux/json-c-native/0.15-r0/build --target all --
> > > | [1/34]
> > > /…/work/x86_64-linux/json-c-native/0.15-r0/recipe-sysroot-native/usr/bin/ice/gcc
> > > -D_GNU_SOURCE -Djson_c_EXPORTS
> > > -I/…/work/x86_64-linux/json-c-native/0.15-r0/json-c-0.15
> > > -I/…/work/x86_64-linux/json-c-native/0.15-r0/build
> > > -isystem/…/work/x86_64-linux/j
> > > son-c-native/0.15-r0/recipe-sysroot-native/usr/include -O2 -pipe
> > > -ffunction-sections -fdata-sections -Werror -Wall -Wcast-qual
> > > -Wno-error=deprecated-declarations -Wextra -Wwrite-strings
> > > -Wno-unused-parameter -Wstrict-prototypes -g -fPIC -D_REENTRANT
> > > -MD -MT CMakeFiles/json-c.dir/linkhash.c.o -MF
> > > CMakeFiles/json-c.dir/linkhash.c.o.d -o
> > > CMakeFiles/json-c.dir/linkhash.c.o -c
> > > /…/work/x86_64-linux/json-c-native/0.15-r0/json-c
> > > -0.15/linkhash.c | FAILED: CMakeFiles/json-c.dir/linkhash.c.o |
> > > /…/work/x86_64-linux/json-c-native/0.15-r0/recipe-sysroot-native/usr/bin/ice/gcc
> > > -D_GNU_SOURCE -Djson_c_EXPORTS
> > > -I/…/work/x86_64-linux/json-c-native/0.15-r0/json-c-0.15
> > > -I/…/work/x86_64-linux/json-c-native/0.15-r0/build
> > > -isystem/…/work/x86_64-linux/json-c-n
> > > ative/0.15-r0/recipe-sysroot-native/usr/include -O2 -pipe
> > > -ffunction-sections -fdata-sections -Werror -Wall -Wcast-qual
> > > -Wno-error=deprecated-declarations -Wextra -Wwrite-strings
> > > -Wno-unused-parameter -Wstrict-prototypes -g -fPIC -D_REENTRANT
> > > -MD -MT CMakeFiles/json-c.dir/linkhash.c.o -MF
> > > CMakeFiles/json-c.dir/linkhash.c.o.d -o
> > > CMakeFiles/json-c.dir/linkhash.c.o -c
> > > /…/work/x86_64-linux/json-c-native/0.15-r0/json-c-0.15/l
> > > inkhash.c |
> > > /…/work/x86_64-linux/json-c-native/0.15-r0/json-c-0.15/linkhash.c:
> > > In function 'hashlittle': |
> > > /…/work/x86_64-linux/json-c-native/0.15-r0/json-c-0.15/linkhash.c:367:13:
> > > error: this statement may fall through
> > > [-Werror=implicit-fallthrough=] |
> > > /…/work/x86_64-linux/json-c-native/0.15-r0/json-c-0.15/linkhash.c:368:3:
> > > note: here |
> > > /…/work/x86_64-linux/json-c-native/0.15-r0/json-c-0.15/linkhash.c:372:13:
> > > error: this statement may fall through
> > > [-Werror=implicit-fallthrough=] |
> > > /…/work/x86_64-linux/json-c-native/0.15-r0/json-c-0.15/linkhash.c:373:3:
> > > note: here |
> > > /…/work/x86_64-linux/json-c-native/0.15-r0/json-c-0.15/linkhash.c:376:13:
> > > error: this statement may fall through
> > > [-Werror=implicit-fallthrough=] |
> > > /…/work/x86_64-linux/json-c-native/0.15-r0/json-c-0.15/linkhash.c:377:3:
> > > note: here |
> > > /…/work/x86_64-linux/json-c-native/0.15-r0/json-c-0.15/linkhash.c:380:13:
> > > error: this statement may fall through
> > > [-Werror=implicit-fallthrough=] |
> > > /…/work/x86_64-linux/json-c-native/0.15-r0/json-c-0.15/linkhash.c:381:3:
> > > note: here |
> > > /…/work/x86_64-linux/json-c-native/0.15-r0/json-c-0.15/linkhash.c:383:13:
> > > error: this statement may fall through
> > > [-Werror=implicit-fallthrough=] |
> > > /…/work/x86_64-linux/json-c-native/0.15-r0/json-c-0.15/linkhash.c:384:3:
> > > note: here |
> > > /…/work/x86_64-linux/json-c-native/0.15-r0/json-c-0.15/linkhash.c:420:13:
> > > error: this statement may fall through
> > > [-Werror=implicit-fallthrough=] |
> > > /…/work/x86_64-linux/json-c-native/0.15-r0/json-c-0.15/linkhash.c:421:3:
> > > note: here |
> > > /…/work/x86_64-linux/json-c-native/0.15-r0/json-c-0.15/linkhash.c:421:13:
> > > error: this statement may fall through
> > > [-Werror=implicit-fallthrough=] |
> > > /…/work/x86_64-linux/json-c-native/0.15-r0/json-c-0.15/linkhash.c:422:3:
> > > note: here |
> > > /…/work/x86_64-linux/json-c-native/0.15-r0/json-c-0.15/linkhash.c:422:13:
> > > error: this statement may fall through
> > > [-Wer