Re: [OE-Core][dunfell][PATCH] tiff: Fix for CVE-2022-2867/8/9

[Virendra Thakur via lists.openembedded.org]

Please take this patch .
removed change-ID as its not needed.


From: openembedded-core@lists.openembedded.org 
 on behalf of Virendra Thakur via 
lists.openembedded.org 
Sent: Friday, September 9, 2022 10:41 AM
To: Steve Sakoman 
Cc: openembedded-core@lists.openembedded.org 

Subject: Re: [OE-Core][dunfell][PATCH] tiff: Fix for CVE-2022-2867/8/9

Caution: This email originated from outside of the KPIT. Do not click links or 
open attachments unless you recognize the sender and know the content is safe.
Hi Steve,

I am attaching here with tiff patchset .
please let me know if its fine.




From: Steve Sakoman 
Sent: Friday, September 9, 2022 12:14 AM
To: Virendra Kumar Thakur 
Cc: openembedded-core@lists.openembedded.org 
; Virendra Kumar Thakur 

Subject: Re: [OE-Core][dunfell][PATCH] tiff: Fix for CVE-2022-2867/8/9

Caution: This email originated from outside of the KPIT. Do not click links or 
open attachments unless you recognize the sender and know the content is safe.

On Wed, Sep 7, 2022 at 7:04 PM Virendra Thakur via
lists.openembedded.org
 wrote:
>
> From: Virendra Thakur 
>
> Add Patch to fix CVE-2022-2867, CVE-2022-2868
> CVE-2022-2869

This fails on the autobuilder:

ERROR: tiff-4.1.0-r0 do_patch: Applying patch
'CVE-2022-2867-CVE-2022-2868-CVE-2022-2869.patch' on target directory
'/home/pokybuild/yocto-worker/reproducible/build/build-st-966841/reproducibleA/tmp/work/core2-64-poky-linux/tiff/4.1.0-r0/tiff-4.1.0'
Command Error: 'quilt --quiltrc
/home/pokybuild/yocto-worker/reproducible/build/build-st-966841/reproducibleA/tmp/work/core2-64-poky-linux/tiff/4.1.0-r0/recipe-sysroot-native/etc/quiltrc
push' exited with 0  Output:
Applying patch CVE-2022-2867-CVE-2022-2868-CVE-2022-2869.patch
patching file tools/tiffcrop.c
Hunk #1 FAILED at 5153.
Hunk #2 succeeded at 4782 with fuzz 2 (offset -423 lines).
Hunk #4 FAILED at 5332.
Hunk #5 succeeded at 5449 with fuzz 2.
Hunk #6 succeeded at 5588 with fuzz 2.
2 out of 6 hunks FAILED -- rejects in file tools/tiffcrop.c
Patch CVE-2022-2867-CVE-2022-2868-CVE-2022-2869.patch does not apply
(enforce with -f)

Perhaps your mailer is corrupting the patch?  This has been an issue
lately with other patches from kpit!

Steve

>
> Signed-off-by: Virendra Thakur 
> ---
>  ...022-2867-CVE-2022-2868-CVE-2022-2869.patch | 159 ++
>  meta/recipes-multimedia/libtiff/tiff_4.1.0.bb |   1 +
>  2 files changed, 160 insertions(+)
>  create mode 100644 
> meta/recipes-multimedia/libtiff/files/CVE-2022-2867-CVE-2022-2868-CVE-2022-2869.patch
>
> diff --git 
> a/meta/recipes-multimedia/libtiff/files/CVE-2022-2867-CVE-2022-2868-CVE-2022-2869.patch
>  
> b/meta/recipes-multimedia/libtiff/files/CVE-2022-2867-CVE-2022-2868-CVE-2022-2869.patch
> new file mode 100644
> index 00..131ff94119
> --- /dev/null
> +++ 
> b/meta/recipes-multimedia/libtiff/files/CVE-2022-2867-CVE-2022-2868-CVE-2022-2869.patch
> @@ -0,0 +1,159 @@
> +From 07d79fcac2ead271b60e32aeb80f7b4f3be9ac8c Mon Sep 17 00:00:00 2001
> +From: Su Laus 
> +Date: Wed, 9 Feb 2022 21:31:29 +
> +Subject: [PATCH] tiffcrop.c: Fix issue #352 heap-buffer-overflow by 
> correcting
> + uint32_t underflow.
> +
> +CVE: CVE-2022-2867 CVE-2022-2868 CVE-2022-2869
> +Upstream-Status: Backport 
> [https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.com%2Flibtiff%2Flibtiff%2F-%2Fcommit%2F07d79fcac2ead271b60e32aeb80f7b4f3be9ac8cdata=05%7C01%7Cvirendra.thakur%40kpit.com%7C06f4664a51014a38772c08da91ca2d06%7C3539451eb46e4a26a242ff61502855c7%7C0%7C0%7C637982594827918330%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=KeN8brH6XLpD8sQUvDQHUfeG7Ld%2BnFtGl%2Bgr5WCiJX4%3Dreserved=0]
> +Signed-off-by: Virendra Thakur 
> +---
> +Index: tiff-4.1.0/tools/tiffcrop.c
> +===
> +--- tiff-4.1.0.orig/tools/tiffcrop.c
>  tiff-4.1.0/tools/tiffcrop.c
> +@@ -5153,29 +5153,45 @@ computeInputPixelOffsets(struct crop_mas
> +   y1 = _TIFFClampDoubleToUInt32(crop->corners[i].Y1);
> +   y2 = _TIFFClampDoubleToUInt32(crop->corners[i].Y2);
> +   }
> +-  if (x1 < 1)
> +-crop->regionlist[i].x1 = 0;
> +-  else
> +-crop->regionlist[i].x1 = (uint32) (x1 - 1);
> ++  /* a) Region needs to be within image sizes 0.. width-1; 0..length-1
> ++   * b) Corners are expected to be submitted as top-left to 
> bottom-right.
> ++   *Therefore, check that and reorder 

Re: [OE-Core][dunfell][PATCH] tiff: Fix for CVE-2022-2867/8/9

[Virendra Thakur via lists.openembedded.org]

Hi Steve,

I am attaching here with tiff patchset .
please let me know if its fine.




From: Steve Sakoman 
Sent: Friday, September 9, 2022 12:14 AM
To: Virendra Kumar Thakur 
Cc: openembedded-core@lists.openembedded.org 
; Virendra Kumar Thakur 

Subject: Re: [OE-Core][dunfell][PATCH] tiff: Fix for CVE-2022-2867/8/9

Caution: This email originated from outside of the KPIT. Do not click links or 
open attachments unless you recognize the sender and know the content is safe.

On Wed, Sep 7, 2022 at 7:04 PM Virendra Thakur via
lists.openembedded.org
 wrote:
>
> From: Virendra Thakur 
>
> Add Patch to fix CVE-2022-2867, CVE-2022-2868
> CVE-2022-2869

This fails on the autobuilder:

ERROR: tiff-4.1.0-r0 do_patch: Applying patch
'CVE-2022-2867-CVE-2022-2868-CVE-2022-2869.patch' on target directory
'/home/pokybuild/yocto-worker/reproducible/build/build-st-966841/reproducibleA/tmp/work/core2-64-poky-linux/tiff/4.1.0-r0/tiff-4.1.0'
Command Error: 'quilt --quiltrc
/home/pokybuild/yocto-worker/reproducible/build/build-st-966841/reproducibleA/tmp/work/core2-64-poky-linux/tiff/4.1.0-r0/recipe-sysroot-native/etc/quiltrc
push' exited with 0  Output:
Applying patch CVE-2022-2867-CVE-2022-2868-CVE-2022-2869.patch
patching file tools/tiffcrop.c
Hunk #1 FAILED at 5153.
Hunk #2 succeeded at 4782 with fuzz 2 (offset -423 lines).
Hunk #4 FAILED at 5332.
Hunk #5 succeeded at 5449 with fuzz 2.
Hunk #6 succeeded at 5588 with fuzz 2.
2 out of 6 hunks FAILED -- rejects in file tools/tiffcrop.c
Patch CVE-2022-2867-CVE-2022-2868-CVE-2022-2869.patch does not apply
(enforce with -f)

Perhaps your mailer is corrupting the patch?  This has been an issue
lately with other patches from kpit!

Steve

>
> Signed-off-by: Virendra Thakur 
> ---
>  ...022-2867-CVE-2022-2868-CVE-2022-2869.patch | 159 ++
>  meta/recipes-multimedia/libtiff/tiff_4.1.0.bb |   1 +
>  2 files changed, 160 insertions(+)
>  create mode 100644 
> meta/recipes-multimedia/libtiff/files/CVE-2022-2867-CVE-2022-2868-CVE-2022-2869.patch
>
> diff --git 
> a/meta/recipes-multimedia/libtiff/files/CVE-2022-2867-CVE-2022-2868-CVE-2022-2869.patch
>  
> b/meta/recipes-multimedia/libtiff/files/CVE-2022-2867-CVE-2022-2868-CVE-2022-2869.patch
> new file mode 100644
> index 00..131ff94119
> --- /dev/null
> +++ 
> b/meta/recipes-multimedia/libtiff/files/CVE-2022-2867-CVE-2022-2868-CVE-2022-2869.patch
> @@ -0,0 +1,159 @@
> +From 07d79fcac2ead271b60e32aeb80f7b4f3be9ac8c Mon Sep 17 00:00:00 2001
> +From: Su Laus 
> +Date: Wed, 9 Feb 2022 21:31:29 +
> +Subject: [PATCH] tiffcrop.c: Fix issue #352 heap-buffer-overflow by 
> correcting
> + uint32_t underflow.
> +
> +CVE: CVE-2022-2867 CVE-2022-2868 CVE-2022-2869
> +Upstream-Status: Backport 
> [https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.com%2Flibtiff%2Flibtiff%2F-%2Fcommit%2F07d79fcac2ead271b60e32aeb80f7b4f3be9ac8cdata=05%7C01%7Cvirendra.thakur%40kpit.com%7C06f4664a51014a38772c08da91ca2d06%7C3539451eb46e4a26a242ff61502855c7%7C0%7C0%7C637982594827918330%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=KeN8brH6XLpD8sQUvDQHUfeG7Ld%2BnFtGl%2Bgr5WCiJX4%3Dreserved=0]
> +Signed-off-by: Virendra Thakur 
> +---
> +Index: tiff-4.1.0/tools/tiffcrop.c
> +===
> +--- tiff-4.1.0.orig/tools/tiffcrop.c
>  tiff-4.1.0/tools/tiffcrop.c
> +@@ -5153,29 +5153,45 @@ computeInputPixelOffsets(struct crop_mas
> +   y1 = _TIFFClampDoubleToUInt32(crop->corners[i].Y1);
> +   y2 = _TIFFClampDoubleToUInt32(crop->corners[i].Y2);
> +   }
> +-  if (x1 < 1)
> +-crop->regionlist[i].x1 = 0;
> +-  else
> +-crop->regionlist[i].x1 = (uint32) (x1 - 1);
> ++  /* a) Region needs to be within image sizes 0.. width-1; 0..length-1
> ++   * b) Corners are expected to be submitted as top-left to 
> bottom-right.
> ++   *Therefore, check that and reorder input.
> ++   * (be aware x,y are already casted to (uint32_t) and avoid (0 - 1) )
> ++   */
> ++  uint32_t aux;
> ++  if (x1 > x2) {
> ++aux = x1;
> ++x1 = x2;
> ++x2 = aux;
> ++  }
> ++  if (y1 > y2) {
> ++aux = y1;
> ++y1 = y2;
> ++y2 = aux;
> ++  }
> ++  if (x1 > image->width - 1)
> ++crop->regionlist[i].x1 = image->width - 1;
> ++  else if (x1 > 0)
> ++crop->regionlist[i].x1 = (uint32_t)(x1 - 1);
> +
> +   if (x2 > image->width - 1)
> + crop->regionlist[i].x2 = image->width - 1;
> +-  else
> +-crop->regionlist[i].x2 = (uint32) (x2 - 1);
> +-  zwidth  = crop->regionlist[i].x2 - crop->regionlist[i].x1 + 1;
> +-
> +-  if (y1 < 1)
> +-crop->regionlist[i].y1 = 0;
> +-  else
> +-crop->regionlist[i].y1 = (uint32) (y1 - 1);
> ++  else if (x2 > 0)
> ++crop->regionlist[i].x2 = (uint32_t)(x2 - 1);
> ++
> ++  zwidth 

[OE-core] [PATCH v2] rootfs.py: dont try to list installed packages for baremetal images

[Alejandro Hernandez Samaniego]

Theres not a rootfs for baremetal images, hence we should avoid
trying to list rootfs packages for them.

This fixes an issue where some classes (e.g. license_image) rely on
rootfs functionality when included for baremetal images even if its
nonexistent

Signed-off-by: Alejandro Enedino Hernandez Samaniego 
---
 meta/lib/oe/rootfs.py | 4 
 1 file changed, 4 insertions(+)

diff --git a/meta/lib/oe/rootfs.py b/meta/lib/oe/rootfs.py
index 0b9911e3a6..ad2a4c1441 100644
--- a/meta/lib/oe/rootfs.py
+++ b/meta/lib/oe/rootfs.py
@@ -386,6 +386,10 @@ def create_rootfs(d, manifest_dir=None, 
progress_reporter=None, logcatcher=None)
 
 
 def image_list_installed_packages(d, rootfs_dir=None):
+# Theres no rootfs for baremetal images
+if bb.data.inherits_class('baremetal-image', d):
+return ""
+
 if not rootfs_dir:
 rootfs_dir = d.getVar('IMAGE_ROOTFS')
 
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#170476): 
https://lists.openembedded.org/g/openembedded-core/message/170476
Mute This Topic: https://lists.openembedded.org/mt/93562486/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] rust-hello-world: move to meta-skeleton

[Richard Purdie]

On Thu, 2022-09-08 at 13:33 -0300, Otavio Salvador wrote:
> Signed-off-by: Otavio Salvador 
> ---
> 
>  .../hello-rust}/rust-hello-world/0001-enable-LTO.patch| 0
>  .../recipes-skeleton/hello-rust}/rust-hello-world_git.bb  | 0
>  2 files changed, 0 insertions(+), 0 deletions(-)
>  rename {meta/recipes-example/rust-hello-world => 
> meta-skeleton/recipes-skeleton/hello-rust}/rust-hello-world/0001-enable-LTO.patch
>  (100%)
>  rename {meta/recipes-example/rust-hello-world => 
> meta-skeleton/recipes-skeleton/hello-rust}/rust-hello-world_git.bb (100%)

https://autobuilder.yoctoproject.org/typhoon/#/builders/39/builds/5859/steps/15/logs/stdio

i.e. there are dependencies in other layers.

Cheers,

Richard




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#170475): 
https://lists.openembedded.org/g/openembedded-core/message/170475
Mute This Topic: https://lists.openembedded.org/mt/93553025/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 v3] webkitgtk: Fix build on 32bit arm

[Khem Raj]

Signed-off-by: Khem Raj 
Cc: Mingli Yu 
---
v2: Fix commit msg format
v3: Apply suggestion from 
https://github.com/WebKit/WebKit/pull/1233#discussion_r915217428

 ...44e17d258106617b0e6d783d073b188a2548.patch | 296 ++
 meta/recipes-sato/webkit/webkitgtk_2.36.7.bb  |   1 +
 2 files changed, 297 insertions(+)
 create mode 100644 
meta/recipes-sato/webkit/webkitgtk/0d3344e17d258106617b0e6d783d073b188a2548.patch

diff --git 
a/meta/recipes-sato/webkit/webkitgtk/0d3344e17d258106617b0e6d783d073b188a2548.patch
 
b/meta/recipes-sato/webkit/webkitgtk/0d3344e17d258106617b0e6d783d073b188a2548.patch
new file mode 100644
index 00..32f92f7ff5
--- /dev/null
+++ 
b/meta/recipes-sato/webkit/webkitgtk/0d3344e17d258106617b0e6d783d073b188a2548.patch
@@ -0,0 +1,296 @@
+From 0d3344e17d258106617b0e6d783d073b188a2548 Mon Sep 17 00:00:00 2001
+From: Adrian Perez de Castro 
+Date: Thu, 2 Jun 2022 11:19:06 +0300
+Subject: [PATCH] [ARM][NEON] FELightningNEON.cpp fails to build, NEON fast
+ path seems unused https://bugs.webkit.org/show_bug.cgi?id=241182
+
+Reviewed by NOBODY (OOPS!).
+
+Move the NEON fast path for the SVG lighting filter effects into
+FELightingSoftwareApplier, and arrange to actually use them by
+forwarding calls to applyPlatformGeneric() into applyPlatformNeon().
+
+Some changes were needed to adapt platformApplyNeon() to the current
+state of filters after r286140. This was not detected because the code
+bitrotted due to it being guarded with CPU(ARM_TRADITIONAL), which does
+not get used much these days: CPU(ARM_THUMB2) is more common. It should
+be possible to use the NEON fast paths also in Thumb mode, but that is
+left for a follow-up fix.
+
+* Source/WebCore/platform/graphics/cpu/arm/filters/FELightingNEON.cpp:
+(WebCore::FELightingSoftwareApplier::platformApplyNeonWorker):
+(WebCore::FELightingSoftwareApplier::getPowerCoefficients):
+(WebCore::FELighting::platformApplyNeonWorker): Deleted.
+(WebCore::FELighting::getPowerCoefficients): Deleted.
+* Source/WebCore/platform/graphics/cpu/arm/filters/FELightingNEON.h:
+(WebCore::FELightingSoftwareApplier::applyPlatformNeon):
+(WebCore::FELighting::platformApplyNeon): Deleted.
+* Source/WebCore/platform/graphics/filters/DistantLightSource.h:
+* Source/WebCore/platform/graphics/filters/FELighting.h:
+* Source/WebCore/platform/graphics/filters/PointLightSource.h:
+* Source/WebCore/platform/graphics/filters/SpotLightSource.h:
+* 
Source/WebCore/platform/graphics/filters/software/FELightingSoftwareApplier.h:
+---
+Upstream-Status: Submitted [https://github.com/WebKit/WebKit/pull/1233]
+Signed-off-by: Khem Raj 
+
+ .../cpu/arm/filters/FELightingNEON.cpp|  4 +-
+ .../graphics/cpu/arm/filters/FELightingNEON.h | 54 +--
+ .../graphics/filters/DistantLightSource.h |  4 ++
+ .../platform/graphics/filters/FELighting.h|  7 ---
+ .../graphics/filters/PointLightSource.h   |  4 ++
+ .../graphics/filters/SpotLightSource.h|  4 ++
+ .../software/FELightingSoftwareApplier.h  | 16 ++
+ 7 files changed, 57 insertions(+), 36 deletions(-)
+
+--- a/Source/WebCore/platform/graphics/cpu/arm/filters/FELightingNEON.cpp
 b/Source/WebCore/platform/graphics/cpu/arm/filters/FELightingNEON.cpp
+@@ -49,7 +49,7 @@ short* feLightingConstantsForNeon()
+ return s_FELightingConstantsForNeon;
+ }
+ 
+-void FELighting::platformApplyNeonWorker(FELightingPaintingDataForNeon* 
parameters)
++void 
FELightingSoftwareApplier::platformApplyNeonWorker(FELightingPaintingDataForNeon*
 parameters)
+ {
+ neonDrawLighting(parameters);
+ }
+@@ -464,7 +464,7 @@ TOSTRING(neonDrawLighting) ":" NL
+ "b .lightStrengthCalculated" NL
+ ); // NOLINT
+ 
+-int FELighting::getPowerCoefficients(float exponent)
++int FELightingSoftwareApplier::getPowerCoefficients(float exponent)
+ {
+ // Calling a powf function from the assembly code would require to save
+ // and reload a lot of NEON registers. Since the base is in range [0..1]
+--- a/Source/WebCore/platform/graphics/cpu/arm/filters/FELightingNEON.h
 b/Source/WebCore/platform/graphics/cpu/arm/filters/FELightingNEON.h
+@@ -24,14 +24,15 @@
+  * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+  */
+ 
+-#ifndef FELightingNEON_h
+-#define FELightingNEON_h
++#pragma once
+ 
+ #if CPU(ARM_NEON) && CPU(ARM_TRADITIONAL) && COMPILER(GCC_COMPATIBLE)
+ 
+-#include "FELighting.h"
++#include "FELightingSoftwareApplier.h"
++#include "ImageBuffer.h"
+ #include "PointLightSource.h"
+ #include "SpotLightSource.h"
++#include 
+ #include 
+ 
+ namespace WebCore {
+@@ -93,14 +94,14 @@ extern "C" {
+ void neonDrawLighting(FELightingPaintingDataForNeon*);
+ }
+ 
+-inline void FELighting::platformApplyNeon(const LightingData& data, const 
LightSource::PaintingData& paintingData)
++inline void FELightingSoftwareApplier::applyPlatformNeon(const 
FELightingSoftwareApplier::LightingData& data, const LightSource::PaintingData& 
paintingData)
+ {
+-alignas(16) 

[OE-core] [PATCH] gobject-introspection: Do not hardcode objdump name

[Khem Raj]

Use OBJDUMP variable in the script, this helps in using the lddwrapper
with recipes which maybe using different objdump tools e.g.l
llvm-objdump or vice-versa

Signed-off-by: Khem Raj 
---
 .../gobject-introspection/gobject-introspection_1.72.0.bb   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.72.0.bb 
b/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.72.0.bb
index 9a47e908b7..d935cbd905 100644
--- a/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.72.0.bb
+++ b/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.72.0.bb
@@ -103,7 +103,7 @@ EOF
 # for a different architecture
 cat > ${B}/g-ir-scanner-lddwrapper << EOF
 #!/bin/sh
-$OBJDUMP -p "\$@"
+\$OBJDUMP -p "\$@"
 EOF
 chmod +x ${B}/g-ir-scanner-lddwrapper
 
-- 
2.37.3


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#170473): 
https://lists.openembedded.org/g/openembedded-core/message/170473
Mute This Topic: https://lists.openembedded.org/mt/93558871/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] cairo: Adapt the license information based on what is being built

[Steve Sakoman]

On Thu, Sep 8, 2022 at 6:44 AM Peter Kjellerstedt
 wrote:
>
> Please cherry-pick this to Kirkstone.

Will do!

Steve
>
> //Peter
>
> > -Original Message-
> > From: openembedded-core@lists.openembedded.org 
> >  On Behalf Of Peter Kjellerstedt
> > Sent: den 6 september 2022 15:34
> > To: openembedded-core@lists.openembedded.org
> > Subject: [OE-core] [PATCH] cairo: Adapt the license information based on 
> > what is being built
> >
> > If the "trace" PACKAGECONFIG is removed to disable cairo-trace (the
> > only part of the code licensed as GPL-3.0), we can adapt the licenses
> > for cairo-dbg and cairo-src so that they do not include
> > "GPL-3.0-or-later" and thus they can be used also when, e.g., GPL-3.0
> > is blacklisted in INCOMPATIBLE_LICENSE. Also drop the GPL-3.0 license
> > text from LIC_FILES_CHKSUM in this case.
> >
> > Signed-off-by: Peter Kjellerstedt 
> > ---
> >
> > This applies the suggestion from commit f763b906 (cairo: Add missing
> > GPLv3 license checksum entry). I have verified that when disabling the
> > trace PACKAGECONFIG, then there is no trace (no pun intended) of the
> > GPL-3.0 code in the -dbg and -src packages.
> >
> >  meta/recipes-graphics/cairo/cairo_1.16.0.bb | 6 +-
> >  1 file changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/meta/recipes-graphics/cairo/cairo_1.16.0.bb 
> > b/meta/recipes-graphics/cairo/cairo_1.16.0.bb
> > index 67081bb8cb..ffb813d290 100644
> > --- a/meta/recipes-graphics/cairo/cairo_1.16.0.bb
> > +++ b/meta/recipes-graphics/cairo/cairo_1.16.0.bb
> > @@ -17,9 +17,13 @@ LICENSE:${PN}-doc = "MPL-1.1 | LGPL-2.1-only"
> >  LICENSE:${PN}-gobject = "MPL-1.1 | LGPL-2.1-only"
> >  LICENSE:${PN}-script-interpreter = "MPL-1.1 | LGPL-2.1-only"
> >  LICENSE:${PN}-perf-utils = "GPL-3.0-or-later"
> > +# Adapt the licenses for cairo-dbg and cairo-src depending on whether
> > +# cairo-trace is being built.
> > +LICENSE:${PN}-dbg = "(MPL-1.1 | 
> > LGPL-2.1-only)${@bb.utils.contains('PACKAGECONFIG', 'trace', ' & 
> > GPL-3.0-or-later', '', d)}"
> > +LICENSE:${PN}-src = "(MPL-1.1 | 
> > LGPL-2.1-only)${@bb.utils.contains('PACKAGECONFIG', 'trace', ' & 
> > GPL-3.0-or-later', '', d)}"
> >
> >  LIC_FILES_CHKSUM = "file://COPYING;md5=e73e999e0c72b5ac9012424fa157ad77 \
> > -
> > file://util/cairo-trace/COPYING-GPL-3;md5=d32239bcb673463ab874e80d47fae504"
> > +${@bb.utils.contains('PACKAGECONFIG', 'trace', 
> > 'file://util/cairo-trace/COPYING-GPL-3;md5=d32239bcb673463ab874e80d47fae504',
> >  '', d)}"
> >
> >
> >  DEPENDS = "fontconfig glib-2.0 libpng pixman zlib"

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#170472): 
https://lists.openembedded.org/g/openembedded-core/message/170472
Mute This Topic: https://lists.openembedded.org/mt/93500619/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 1/2] binutils-cross-canadian: Do not package gprofng.rc

[Khem Raj]

Thanks Alex,

sent a v2 which should address it.

On Thu, Sep 8, 2022 at 6:49 AM Alexandre Belloni
 wrote:
>
> Hi,
>
> This caused failures similar to this one:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/4110/steps/14/logs/stdio
>
> Full list here:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/4203
>
> On 07/09/2022 16:14:16-0700, Khem Raj wrote:
> > This file is already packaged via nativesdk-gprofng and can cause
> > populate SDK conflicts
> >
> > Signed-off-by: Khem Raj 
> > ---
> >  meta/recipes-devtools/binutils/binutils-cross-canadian.inc | 3 +--
> >  1 file changed, 1 insertion(+), 2 deletions(-)
> >
> > diff --git a/meta/recipes-devtools/binutils/binutils-cross-canadian.inc 
> > b/meta/recipes-devtools/binutils/binutils-cross-canadian.inc
> > index 4e8f10c1c4..c18468ad50 100644
> > --- a/meta/recipes-devtools/binutils/binutils-cross-canadian.inc
> > +++ b/meta/recipes-devtools/binutils/binutils-cross-canadian.inc
> > @@ -23,10 +23,9 @@ do_install () {
> >   rm -f ${D}${libdir}/libiberty*
> >   rm -f ${D}${libdir}/libopcodes*
> >   rm -f ${D}${includedir}/*.h
> > +rm -f ${D}${sysconfdir}/gprofng.rc
> >
> >   cross_canadian_bindirlinks
> >  }
> >
> > -FILES:${PN} += "${sysconfdir}/gprofng.rc"
> > -
> >  BBCLASSEXTEND = ""
> > --
> > 2.37.3
> >
>
> >
> > 
> >
>
>
> --
> 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 (#170471): 
https://lists.openembedded.org/g/openembedded-core/message/170471
Mute This Topic: https://lists.openembedded.org/mt/93537151/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] binutils-cross-canadian: Do not package gprofng.rc

[Khem Raj]

This file is already packaged via nativesdk-gprofng and can cause
populate SDK conflicts

Also delete the etc directory if its empty it can still cause packaging
QA errors

Signed-off-by: Khem Raj 
---
v2: Delete empty etc dir as well

 meta/recipes-devtools/binutils/binutils-cross-canadian.inc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-devtools/binutils/binutils-cross-canadian.inc 
b/meta/recipes-devtools/binutils/binutils-cross-canadian.inc
index 4e8f10c1c4..12e7d77d8d 100644
--- a/meta/recipes-devtools/binutils/binutils-cross-canadian.inc
+++ b/meta/recipes-devtools/binutils/binutils-cross-canadian.inc
@@ -23,10 +23,10 @@ do_install () {
rm -f ${D}${libdir}/libiberty*
rm -f ${D}${libdir}/libopcodes*
rm -f ${D}${includedir}/*.h
-   
+   rm -f ${D}${sysconfdir}/gprofng.rc
+   rmdir ${D}${sysconfdir} || :
+
cross_canadian_bindirlinks
 }
 
-FILES:${PN} += "${sysconfdir}/gprofng.rc"
-
 BBCLASSEXTEND = ""
-- 
2.37.3


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#170470): 
https://lists.openembedded.org/g/openembedded-core/message/170470
Mute This Topic: https://lists.openembedded.org/mt/93555979/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][dunfell][PATCH] tiff: Fix for CVE-2022-2867/8/9

[Steve Sakoman]

On Wed, Sep 7, 2022 at 7:04 PM Virendra Thakur via
lists.openembedded.org
 wrote:
>
> From: Virendra Thakur 
>
> Add Patch to fix CVE-2022-2867, CVE-2022-2868
> CVE-2022-2869

This fails on the autobuilder:

ERROR: tiff-4.1.0-r0 do_patch: Applying patch
'CVE-2022-2867-CVE-2022-2868-CVE-2022-2869.patch' on target directory
'/home/pokybuild/yocto-worker/reproducible/build/build-st-966841/reproducibleA/tmp/work/core2-64-poky-linux/tiff/4.1.0-r0/tiff-4.1.0'
Command Error: 'quilt --quiltrc
/home/pokybuild/yocto-worker/reproducible/build/build-st-966841/reproducibleA/tmp/work/core2-64-poky-linux/tiff/4.1.0-r0/recipe-sysroot-native/etc/quiltrc
push' exited with 0  Output:
Applying patch CVE-2022-2867-CVE-2022-2868-CVE-2022-2869.patch
patching file tools/tiffcrop.c
Hunk #1 FAILED at 5153.
Hunk #2 succeeded at 4782 with fuzz 2 (offset -423 lines).
Hunk #4 FAILED at 5332.
Hunk #5 succeeded at 5449 with fuzz 2.
Hunk #6 succeeded at 5588 with fuzz 2.
2 out of 6 hunks FAILED -- rejects in file tools/tiffcrop.c
Patch CVE-2022-2867-CVE-2022-2868-CVE-2022-2869.patch does not apply
(enforce with -f)

Perhaps your mailer is corrupting the patch?  This has been an issue
lately with other patches from kpit!

Steve

>
> Signed-off-by: Virendra Thakur 
> ---
>  ...022-2867-CVE-2022-2868-CVE-2022-2869.patch | 159 ++
>  meta/recipes-multimedia/libtiff/tiff_4.1.0.bb |   1 +
>  2 files changed, 160 insertions(+)
>  create mode 100644 
> meta/recipes-multimedia/libtiff/files/CVE-2022-2867-CVE-2022-2868-CVE-2022-2869.patch
>
> diff --git 
> a/meta/recipes-multimedia/libtiff/files/CVE-2022-2867-CVE-2022-2868-CVE-2022-2869.patch
>  
> b/meta/recipes-multimedia/libtiff/files/CVE-2022-2867-CVE-2022-2868-CVE-2022-2869.patch
> new file mode 100644
> index 00..131ff94119
> --- /dev/null
> +++ 
> b/meta/recipes-multimedia/libtiff/files/CVE-2022-2867-CVE-2022-2868-CVE-2022-2869.patch
> @@ -0,0 +1,159 @@
> +From 07d79fcac2ead271b60e32aeb80f7b4f3be9ac8c Mon Sep 17 00:00:00 2001
> +From: Su Laus 
> +Date: Wed, 9 Feb 2022 21:31:29 +
> +Subject: [PATCH] tiffcrop.c: Fix issue #352 heap-buffer-overflow by 
> correcting
> + uint32_t underflow.
> +
> +CVE: CVE-2022-2867 CVE-2022-2868 CVE-2022-2869
> +Upstream-Status: Backport 
> [https://gitlab.com/libtiff/libtiff/-/commit/07d79fcac2ead271b60e32aeb80f7b4f3be9ac8c]
> +Signed-off-by: Virendra Thakur 
> +---
> +Index: tiff-4.1.0/tools/tiffcrop.c
> +===
> +--- tiff-4.1.0.orig/tools/tiffcrop.c
>  tiff-4.1.0/tools/tiffcrop.c
> +@@ -5153,29 +5153,45 @@ computeInputPixelOffsets(struct crop_mas
> +   y1 = _TIFFClampDoubleToUInt32(crop->corners[i].Y1);
> +   y2 = _TIFFClampDoubleToUInt32(crop->corners[i].Y2);
> +   }
> +-  if (x1 < 1)
> +-crop->regionlist[i].x1 = 0;
> +-  else
> +-crop->regionlist[i].x1 = (uint32) (x1 - 1);
> ++  /* a) Region needs to be within image sizes 0.. width-1; 0..length-1
> ++   * b) Corners are expected to be submitted as top-left to 
> bottom-right.
> ++   *Therefore, check that and reorder input.
> ++   * (be aware x,y are already casted to (uint32_t) and avoid (0 - 1) )
> ++   */
> ++  uint32_t aux;
> ++  if (x1 > x2) {
> ++aux = x1;
> ++x1 = x2;
> ++x2 = aux;
> ++  }
> ++  if (y1 > y2) {
> ++aux = y1;
> ++y1 = y2;
> ++y2 = aux;
> ++  }
> ++  if (x1 > image->width - 1)
> ++crop->regionlist[i].x1 = image->width - 1;
> ++  else if (x1 > 0)
> ++crop->regionlist[i].x1 = (uint32_t)(x1 - 1);
> +
> +   if (x2 > image->width - 1)
> + crop->regionlist[i].x2 = image->width - 1;
> +-  else
> +-crop->regionlist[i].x2 = (uint32) (x2 - 1);
> +-  zwidth  = crop->regionlist[i].x2 - crop->regionlist[i].x1 + 1;
> +-
> +-  if (y1 < 1)
> +-crop->regionlist[i].y1 = 0;
> +-  else
> +-crop->regionlist[i].y1 = (uint32) (y1 - 1);
> ++  else if (x2 > 0)
> ++crop->regionlist[i].x2 = (uint32_t)(x2 - 1);
> ++
> ++  zwidth = crop->regionlist[i].x2 - crop->regionlist[i].x1 + 1;
> ++
> ++  if (y1 > image->length - 1)
> ++crop->regionlist[i].y1 = image->length - 1;
> ++  else if (y1 > 0)
> ++crop->regionlist[i].y1 = (uint32_t)(y1 - 1);
> +
> +   if (y2 > image->length - 1)
> + crop->regionlist[i].y2 = image->length - 1;
> +-  else
> +-crop->regionlist[i].y2 = (uint32) (y2 - 1);
> +-
> +-  zlength = crop->regionlist[i].y2 - crop->regionlist[i].y1 + 1;
> ++  else if (y2 > 0)
> ++crop->regionlist[i].y2 = (uint32_t)(y2 - 1);
> +
> ++  zlength = crop->regionlist[i].y2 - crop->regionlist[i].y1 + 1;
> +   if (zwidth > max_width)
> + max_width = zwidth;
> +   if (zlength > max_length)
> +@@ -5205,7 +5221,7 @@ computeInputPixelOffsets(struct crop_mas
> +   }
> +   }
> + return (0);
> +-}
> ++}  /* crop_mode == 

Re: [OE-core] [PATCH] linux-yocto: Enable mdio for qemu

[Khem Raj]

Cool, thanks!

On Thu, Sep 8, 2022 at 7:09 AM Bruce Ashfield  wrote:
>
> On Thu, Sep 8, 2022 at 9:48 AM Alexandre Belloni
>  wrote:
> >
> > Hi,
> >
> > This caused many failures like this one:
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/5847/steps/11/logs/stdio
> >
>
> Technically not an error, only an error in the eyes of the stricter testing.
>
> Khem: Let me queue the patch here, and I'll add a mask for that
> warning, since in this case =y is as good as =m
>
> Bruce
>
> > On 07/09/2022 15:05:35-0700, Khem Raj wrote:
> > > There are package like mdio-netlink in meta-oe which need this feature
> > > to be available, it has started to fail with 5.19
> > >
> > > Signed-off-by: Khem Raj 
> > > Cc: Bruce Ashfield 
> > > ---
> > >  meta/recipes-kernel/linux/linux-yocto_5.19.bb | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/meta/recipes-kernel/linux/linux-yocto_5.19.bb 
> > > b/meta/recipes-kernel/linux/linux-yocto_5.19.bb
> > > index 0ff28aa952..e96395d1bb 100644
> > > --- a/meta/recipes-kernel/linux/linux-yocto_5.19.bb
> > > +++ b/meta/recipes-kernel/linux/linux-yocto_5.19.bb
> > > @@ -56,7 +56,7 @@ COMPATIBLE_MACHINE = 
> > > "^(qemuarm|qemuarmv5|qemuarm64|qemux86|qemuppc|qemuppc64|qe
> > >  # Functionality flags
> > >  KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc"
> > >  KERNEL_FEATURES:append = " ${KERNEL_EXTRA_FEATURES}"
> > > -KERNEL_FEATURES:append:qemuall=" cfg/virtio.scc 
> > > features/drm-bochs/drm-bochs.scc"
> > > +KERNEL_FEATURES:append:qemuall=" cfg/virtio.scc 
> > > features/drm-bochs/drm-bochs.scc cfg/net/mdio.scc"
> > >  KERNEL_FEATURES:append:qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
> > >  KERNEL_FEATURES:append:qemux86-64=" cfg/sound.scc cfg/paravirt_kvm.scc"
> > >  KERNEL_FEATURES:append = " ${@bb.utils.contains("TUNE_FEATURES", "mx32", 
> > > " cfg/x32.scc", "", d)}"
> > > --
> > > 2.37.3
> > >
> >
> > >
> > > 
> > >
> >
> >
> > --
> > Alexandre Belloni, co-owner and COO, Bootlin
> > Embedded Linux and Kernel engineering
> > https://bootlin.com
>
>
>
> --
> - 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 (#170468): 
https://lists.openembedded.org/g/openembedded-core/message/170468
Mute This Topic: https://lists.openembedded.org/mt/93535950/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] boost: Refrain bjam from poking into host includes

[Khem Raj]

bjam's logic to find icu during build time tries to poke at /usr/ for
various files and it succeeds for 32bit target build on my host and it adds
-I/usr/inclue to search paths because I do have icu installed on build
host in /usr/lib and /usr/include but does not succeed
for 64-bit target builds because its searching for same in /usr/lib64

on 32-bit log_dompile shows

- icu  : yes [5]
on 64 bit

- icu  : no [2]

On 64bit its getting lucky because the test is failing due to mismatches
in size of 'uintptr_t' since its reading half the headers from build
host and remaining from target C++ library.

In file included from 
/mnt/b/yoe/master/build/tmp/work/riscv64-yoe-linux/boost/1.80.0-r0/boost_1_80_0/libs/locale/build/has_icu_test.cpp:7:
In file included from /usr/include/unicode/locid.h:38:
In file included from /usr/include/unicode/bytestream.h:45:
In file included from /usr/include/unicode/std_string.h:37:
In file included from 
/mnt/b/yoe/master/build/tmp/work/riscv64-yoe-linux/boost/1.80.0-r0/recipe-sysroot/usr/include/c++/v1/string:549:
In file included from 
/mnt/b/yoe/master/build/tmp/work/riscv64-yoe-linux/boost/1.80.0-r0/recipe-sysroot/usr/include/c++/v1/memory:853:
In file included from 
/mnt/b/yoe/master/build/tmp/work/riscv64-yoe-linux/boost/1.80.0-r0/recipe-sysroot/usr/include/c++/v1/__memory/compressed_pair.h:16:
In file included from 
/mnt/b/yoe/master/build/tmp/work/riscv64-yoe-linux/boost/1.80.0-r0/recipe-sysroot/usr/include/c++/v1/tuple:226:
/mnt/b/yoe/master/build/tmp/work/riscv64-yoe-linux/boost/1.80.0-r0/recipe-sysroot/usr/include/c++/v1/typeinfo:247:14:
 error: cast from pointer to smaller type 
'std::__type_info_implementations::__non_unique_arm_rtti_bit_impl::__type_name_t'
 (aka 'unsigned int') loses information
  return reinterpret_cast<__type_name_t>(__v);
 ^~~~

Therefore, help bjam avoid peeking into build system includes entirely.
now if ICU is staged in sysroot it will look there for all headers.

Look into libs/locale/build/Jamfile.v2 after 'Xlocale' section if
you seek further information

Signed-off-by: Khem Raj 
---
 meta/recipes-support/boost/boost.inc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-support/boost/boost.inc 
b/meta/recipes-support/boost/boost.inc
index 402f1592cf..4263e645de 100644
--- a/meta/recipes-support/boost/boost.inc
+++ b/meta/recipes-support/boost/boost.inc
@@ -151,6 +151,7 @@ BOOST_PARALLEL_MAKE = 
"${@oe.utils.parallel_make_argument(d, '-j%d')}"
 BJAM_OPTS= '${BOOST_PARALLEL_MAKE} -d+2 -q \
${BJAM_TOOLS} \
-sBOOST_BUILD_USER_CONFIG=${WORKDIR}/user-config.jam \
+   -sICU_PATH=${STAGING_EXECPREFIXDIR} \
--build-dir=${B} \
--disable-icu \
${BJAM_EXTRA}'
-- 
2.37.3


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#170467): 
https://lists.openembedded.org/g/openembedded-core/message/170467
Mute This Topic: https://lists.openembedded.org/mt/93555873/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] rust: Use variable to specify extra tools to install

[Khem Raj]

All architectures may not support same set of tools, therefore use a
variable to specify this. E.g. on riscv32 rustfmt is not buildable
right now.

Signed-off-by: Khem Raj 
---
v2: fix typo and only exclude rustfmt on rv32 since thats what does not
build

 meta/recipes-devtools/rust/rust_1.63.0.bb | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/rust/rust_1.63.0.bb 
b/meta/recipes-devtools/rust/rust_1.63.0.bb
index cf6468d212..3de6eea0c1 100644
--- a/meta/recipes-devtools/rust/rust_1.63.0.bb
+++ b/meta/recipes-devtools/rust/rust_1.63.0.bb
@@ -62,13 +62,15 @@ rust_do_install:class-nativesdk() {
 rm ${D}${libdir}/rustlib/manifest*
 }
 
+EXTRA_TOOLS ?= "cargo-clippy clippy-driver rustfmt"
+EXTRA_TOOLS:remove:riscv32 = "rustfmt"
 rust_do_install:class-target() {
 export PSEUDO_UNLOAD=1
 rust_runx install
 unset PSEUDO_UNLOAD
 
 install -d ${D}${bindir}
-for i in cargo-clippy clippy-driver rustfmt; do
+for i in ${EXTRA_TOOLS}; do
 cp build/${RUST_BUILD_SYS}/stage2-tools/${RUST_HOST_SYS}/release/$i 
${D}${bindir}
 chrpath -r "\$ORIGIN/../lib" ${D}${bindir}/$i
 done
-- 
2.37.3


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#170466): 
https://lists.openembedded.org/g/openembedded-core/message/170466
Mute This Topic: https://lists.openembedded.org/mt/93555864/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] cairo: Adapt the license information based on what is being built

[Peter Kjellerstedt]

Please cherry-pick this to Kirkstone.

//Peter

> -Original Message-
> From: openembedded-core@lists.openembedded.org 
>  On Behalf Of Peter Kjellerstedt
> Sent: den 6 september 2022 15:34
> To: openembedded-core@lists.openembedded.org
> Subject: [OE-core] [PATCH] cairo: Adapt the license information based on what 
> is being built
> 
> If the "trace" PACKAGECONFIG is removed to disable cairo-trace (the
> only part of the code licensed as GPL-3.0), we can adapt the licenses
> for cairo-dbg and cairo-src so that they do not include
> "GPL-3.0-or-later" and thus they can be used also when, e.g., GPL-3.0
> is blacklisted in INCOMPATIBLE_LICENSE. Also drop the GPL-3.0 license
> text from LIC_FILES_CHKSUM in this case.
> 
> Signed-off-by: Peter Kjellerstedt 
> ---
> 
> This applies the suggestion from commit f763b906 (cairo: Add missing
> GPLv3 license checksum entry). I have verified that when disabling the
> trace PACKAGECONFIG, then there is no trace (no pun intended) of the
> GPL-3.0 code in the -dbg and -src packages.
> 
>  meta/recipes-graphics/cairo/cairo_1.16.0.bb | 6 +-
>  1 file changed, 5 insertions(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-graphics/cairo/cairo_1.16.0.bb 
> b/meta/recipes-graphics/cairo/cairo_1.16.0.bb
> index 67081bb8cb..ffb813d290 100644
> --- a/meta/recipes-graphics/cairo/cairo_1.16.0.bb
> +++ b/meta/recipes-graphics/cairo/cairo_1.16.0.bb
> @@ -17,9 +17,13 @@ LICENSE:${PN}-doc = "MPL-1.1 | LGPL-2.1-only"
>  LICENSE:${PN}-gobject = "MPL-1.1 | LGPL-2.1-only"
>  LICENSE:${PN}-script-interpreter = "MPL-1.1 | LGPL-2.1-only"
>  LICENSE:${PN}-perf-utils = "GPL-3.0-or-later"
> +# Adapt the licenses for cairo-dbg and cairo-src depending on whether
> +# cairo-trace is being built.
> +LICENSE:${PN}-dbg = "(MPL-1.1 | 
> LGPL-2.1-only)${@bb.utils.contains('PACKAGECONFIG', 'trace', ' & 
> GPL-3.0-or-later', '', d)}"
> +LICENSE:${PN}-src = "(MPL-1.1 | 
> LGPL-2.1-only)${@bb.utils.contains('PACKAGECONFIG', 'trace', ' & 
> GPL-3.0-or-later', '', d)}"
> 
>  LIC_FILES_CHKSUM = "file://COPYING;md5=e73e999e0c72b5ac9012424fa157ad77 \
> -
> file://util/cairo-trace/COPYING-GPL-3;md5=d32239bcb673463ab874e80d47fae504"
> +${@bb.utils.contains('PACKAGECONFIG', 'trace', 
> 'file://util/cairo-trace/COPYING-GPL-3;md5=d32239bcb673463ab874e80d47fae504', 
> '', d)}"
> 
> 
>  DEPENDS = "fontconfig glib-2.0 libpng pixman zlib"

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#170465): 
https://lists.openembedded.org/g/openembedded-core/message/170465
Mute This Topic: https://lists.openembedded.org/mt/93500619/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] rust: Use variable to specify extra tools to install

[Otavio Salvador]

Em qui., 8 de set. de 2022 às 12:13, Khem Raj  escreveu:

> All architectures may not support same set of tools, therefore use a
> variable to specify this. E.g. on riscv32 only cargo-clippy is buildable
> right now.
>
> Signed-off-by: Khem Raj 
> ---
>  meta/recipes-devtools/rust/rust_1.63.0.bb | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/meta/recipes-devtools/rust/rust_1.63.0.bb
> b/meta/recipes-devtools/rust/rust_1.63.0.bb
> index cf6468d212..2f70b33c29 100644
> --- a/meta/recipes-devtools/rust/rust_1.63.0.bb
> +++ b/meta/recipes-devtools/rust/rust_1.63.0.bb
> @@ -62,13 +62,15 @@ rust_do_install:class-nativesdk() {
>  rm ${D}${libdir}/rustlib/manifest*
>  }
>
> +EXTRA_TOOLS ?= "cargo-clippy clippy-driver rustfmt"
> +EXTRA_TOOLS:remove:riscv32 = "cargo-driver rustfmt"
>

clippy driver is spelled wrong.

-- 
Otavio Salvador O.S. Systems
http://www.ossystems.com.brhttp://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854  Mobile: +1 (347) 903-9750

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#170464): 
https://lists.openembedded.org/g/openembedded-core/message/170464
Mute This Topic: https://lists.openembedded.org/mt/93550831/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] rust-hello-world: move to meta-skeleton

[Otavio Salvador]

Signed-off-by: Otavio Salvador 
---

 .../hello-rust}/rust-hello-world/0001-enable-LTO.patch| 0
 .../recipes-skeleton/hello-rust}/rust-hello-world_git.bb  | 0
 2 files changed, 0 insertions(+), 0 deletions(-)
 rename {meta/recipes-example/rust-hello-world => 
meta-skeleton/recipes-skeleton/hello-rust}/rust-hello-world/0001-enable-LTO.patch
 (100%)
 rename {meta/recipes-example/rust-hello-world => 
meta-skeleton/recipes-skeleton/hello-rust}/rust-hello-world_git.bb (100%)

diff --git 
a/meta/recipes-example/rust-hello-world/rust-hello-world/0001-enable-LTO.patch 
b/meta-skeleton/recipes-skeleton/hello-rust/rust-hello-world/0001-enable-LTO.patch
similarity index 100%
rename from 
meta/recipes-example/rust-hello-world/rust-hello-world/0001-enable-LTO.patch
rename to 
meta-skeleton/recipes-skeleton/hello-rust/rust-hello-world/0001-enable-LTO.patch
diff --git a/meta/recipes-example/rust-hello-world/rust-hello-world_git.bb 
b/meta-skeleton/recipes-skeleton/hello-rust/rust-hello-world_git.bb
similarity index 100%
rename from meta/recipes-example/rust-hello-world/rust-hello-world_git.bb
rename to meta-skeleton/recipes-skeleton/hello-rust/rust-hello-world_git.bb
-- 
2.37.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#170463): 
https://lists.openembedded.org/g/openembedded-core/message/170463
Mute This Topic: https://lists.openembedded.org/mt/93553025/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] rust: Use variable to specify extra tools to install

[Khem Raj]

All architectures may not support same set of tools, therefore use a
variable to specify this. E.g. on riscv32 only cargo-clippy is buildable
right now.

Signed-off-by: Khem Raj 
---
 meta/recipes-devtools/rust/rust_1.63.0.bb | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/rust/rust_1.63.0.bb 
b/meta/recipes-devtools/rust/rust_1.63.0.bb
index cf6468d212..2f70b33c29 100644
--- a/meta/recipes-devtools/rust/rust_1.63.0.bb
+++ b/meta/recipes-devtools/rust/rust_1.63.0.bb
@@ -62,13 +62,15 @@ rust_do_install:class-nativesdk() {
 rm ${D}${libdir}/rustlib/manifest*
 }
 
+EXTRA_TOOLS ?= "cargo-clippy clippy-driver rustfmt"
+EXTRA_TOOLS:remove:riscv32 = "cargo-driver rustfmt"
 rust_do_install:class-target() {
 export PSEUDO_UNLOAD=1
 rust_runx install
 unset PSEUDO_UNLOAD
 
 install -d ${D}${bindir}
-for i in cargo-clippy clippy-driver rustfmt; do
+for i in ${EXTRA_TOOLS}; do
 cp build/${RUST_BUILD_SYS}/stage2-tools/${RUST_HOST_SYS}/release/$i 
${D}${bindir}
 chrpath -r "\$ORIGIN/../lib" ${D}${bindir}/$i
 done
-- 
2.37.3


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#170462): 
https://lists.openembedded.org/g/openembedded-core/message/170462
Mute This Topic: https://lists.openembedded.org/mt/93550831/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] linux-yocto: Enable mdio for qemu

[Bruce Ashfield]

On Thu, Sep 8, 2022 at 9:48 AM Alexandre Belloni
 wrote:
>
> Hi,
>
> This caused many failures like this one:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/5847/steps/11/logs/stdio
>

Technically not an error, only an error in the eyes of the stricter testing.

Khem: Let me queue the patch here, and I'll add a mask for that
warning, since in this case =y is as good as =m

Bruce

> On 07/09/2022 15:05:35-0700, Khem Raj wrote:
> > There are package like mdio-netlink in meta-oe which need this feature
> > to be available, it has started to fail with 5.19
> >
> > Signed-off-by: Khem Raj 
> > Cc: Bruce Ashfield 
> > ---
> >  meta/recipes-kernel/linux/linux-yocto_5.19.bb | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta/recipes-kernel/linux/linux-yocto_5.19.bb 
> > b/meta/recipes-kernel/linux/linux-yocto_5.19.bb
> > index 0ff28aa952..e96395d1bb 100644
> > --- a/meta/recipes-kernel/linux/linux-yocto_5.19.bb
> > +++ b/meta/recipes-kernel/linux/linux-yocto_5.19.bb
> > @@ -56,7 +56,7 @@ COMPATIBLE_MACHINE = 
> > "^(qemuarm|qemuarmv5|qemuarm64|qemux86|qemuppc|qemuppc64|qe
> >  # Functionality flags
> >  KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc"
> >  KERNEL_FEATURES:append = " ${KERNEL_EXTRA_FEATURES}"
> > -KERNEL_FEATURES:append:qemuall=" cfg/virtio.scc 
> > features/drm-bochs/drm-bochs.scc"
> > +KERNEL_FEATURES:append:qemuall=" cfg/virtio.scc 
> > features/drm-bochs/drm-bochs.scc cfg/net/mdio.scc"
> >  KERNEL_FEATURES:append:qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
> >  KERNEL_FEATURES:append:qemux86-64=" cfg/sound.scc cfg/paravirt_kvm.scc"
> >  KERNEL_FEATURES:append = " ${@bb.utils.contains("TUNE_FEATURES", "mx32", " 
> > cfg/x32.scc", "", d)}"
> > --
> > 2.37.3
> >
>
> >
> > 
> >
>
>
> --
> Alexandre Belloni, co-owner and COO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com



-- 
- 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 (#170461): 
https://lists.openembedded.org/g/openembedded-core/message/170461
Mute This Topic: https://lists.openembedded.org/mt/93535950/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 1/2] binutils-cross-canadian: Do not package gprofng.rc

[Alexandre Belloni via lists.openembedded.org]

Hi,

This caused failures similar to this one:
https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/4110/steps/14/logs/stdio

Full list here:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/4203

On 07/09/2022 16:14:16-0700, Khem Raj wrote:
> This file is already packaged via nativesdk-gprofng and can cause
> populate SDK conflicts
> 
> Signed-off-by: Khem Raj 
> ---
>  meta/recipes-devtools/binutils/binutils-cross-canadian.inc | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/meta/recipes-devtools/binutils/binutils-cross-canadian.inc 
> b/meta/recipes-devtools/binutils/binutils-cross-canadian.inc
> index 4e8f10c1c4..c18468ad50 100644
> --- a/meta/recipes-devtools/binutils/binutils-cross-canadian.inc
> +++ b/meta/recipes-devtools/binutils/binutils-cross-canadian.inc
> @@ -23,10 +23,9 @@ do_install () {
>   rm -f ${D}${libdir}/libiberty*
>   rm -f ${D}${libdir}/libopcodes*
>   rm -f ${D}${includedir}/*.h
> +rm -f ${D}${sysconfdir}/gprofng.rc
>   
>   cross_canadian_bindirlinks
>  }
>  
> -FILES:${PN} += "${sysconfdir}/gprofng.rc"
> -
>  BBCLASSEXTEND = ""
> -- 
> 2.37.3
> 

> 
> 
> 


-- 
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 (#170460): 
https://lists.openembedded.org/g/openembedded-core/message/170460
Mute This Topic: https://lists.openembedded.org/mt/93537151/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] linux-yocto: Enable mdio for qemu

[Alexandre Belloni via lists.openembedded.org]

Hi,

This caused many failures like this one:
https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/5847/steps/11/logs/stdio

On 07/09/2022 15:05:35-0700, Khem Raj wrote:
> There are package like mdio-netlink in meta-oe which need this feature
> to be available, it has started to fail with 5.19
> 
> Signed-off-by: Khem Raj 
> Cc: Bruce Ashfield 
> ---
>  meta/recipes-kernel/linux/linux-yocto_5.19.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-kernel/linux/linux-yocto_5.19.bb 
> b/meta/recipes-kernel/linux/linux-yocto_5.19.bb
> index 0ff28aa952..e96395d1bb 100644
> --- a/meta/recipes-kernel/linux/linux-yocto_5.19.bb
> +++ b/meta/recipes-kernel/linux/linux-yocto_5.19.bb
> @@ -56,7 +56,7 @@ COMPATIBLE_MACHINE = 
> "^(qemuarm|qemuarmv5|qemuarm64|qemux86|qemuppc|qemuppc64|qe
>  # Functionality flags
>  KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc"
>  KERNEL_FEATURES:append = " ${KERNEL_EXTRA_FEATURES}"
> -KERNEL_FEATURES:append:qemuall=" cfg/virtio.scc 
> features/drm-bochs/drm-bochs.scc"
> +KERNEL_FEATURES:append:qemuall=" cfg/virtio.scc 
> features/drm-bochs/drm-bochs.scc cfg/net/mdio.scc"
>  KERNEL_FEATURES:append:qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
>  KERNEL_FEATURES:append:qemux86-64=" cfg/sound.scc cfg/paravirt_kvm.scc"
>  KERNEL_FEATURES:append = " ${@bb.utils.contains("TUNE_FEATURES", "mx32", " 
> cfg/x32.scc", "", d)}"
> -- 
> 2.37.3
> 

> 
> 
> 


-- 
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 (#170459): 
https://lists.openembedded.org/g/openembedded-core/message/170459
Mute This Topic: https://lists.openembedded.org/mt/93535950/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 1/1] externalsrc: Don't wipe out src dir when EXPORT_FUNCTIONS is used.

[Kristian Amlie via lists.openembedded.org]

When 73fa855f6af5ef9c3 was introduced, the "cleandirs" variable flag
started applying to functions exported using EXPORT_FUNCTIONS.
The externalsrc class is supposed to remove cleandirs in order to
prevent wiping out an external src folder (home directory?), but
doesn't take the previous point into account. The result is that
cleandirs is still in effect.

To fix this, apply the cleandirs manipulation to all variables, not
just predefined ones. This is expensive, but since it executes inside
an `if externalsrc` clause, and EXTERNALSRC is usually only set for
specific single recipes, it won't affect most recipes.

Richard Purdie  is the original
author of this patch. I just submitted it under my name for blame
purposes, and also we have been testing it a lot in my company.

This is the original discussion:
https://lists.openembedded.org/g/openembedded-core/topic/91374926

Signed-off-by: Kristian Amlie 
---
 meta/classes-recipe/externalsrc.bbclass | 8 +---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/meta/classes-recipe/externalsrc.bbclass 
b/meta/classes-recipe/externalsrc.bbclass
index 51dbe9ea5a..ce753fce76 100644
--- a/meta/classes-recipe/externalsrc.bbclass
+++ b/meta/classes-recipe/externalsrc.bbclass
@@ -91,16 +91,18 @@ python () {
 # Since configure will likely touch ${S}, ensure only we lock 
so one task has access at a time
 d.appendVarFlag(task, "lockfiles", " ${S}/singletask.lock")
 
-for funcname in [task, "base_" + task, "kernel_" + task]:
+for v in d.keys():
+cleandirs = d.getVarFlag(v, "cleandirs", False)
+if cleandirs:
 # We do not want our source to be wiped out, ever 
(kernel.bbclass does this for do_clean)
-cleandirs = 
oe.recipeutils.split_var_value(d.getVarFlag(funcname, 'cleandirs', False) or '')
+cleandirs = oe.recipeutils.split_var_value(cleandirs)
 setvalue = False
 for cleandir in cleandirs[:]:
 if oe.path.is_path_parent(externalsrc, d.expand(cleandir)):
 cleandirs.remove(cleandir)
 setvalue = True
 if setvalue:
-d.setVarFlag(funcname, 'cleandirs', ' '.join(cleandirs))
+d.setVarFlag(v, 'cleandirs', ' '.join(cleandirs))
 
 fetch_tasks = ['do_fetch', 'do_unpack']
 # If we deltask do_patch, there's no dependency to ensure do_unpack 
gets run, so add one
-- 
2.17.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#170458): 
https://lists.openembedded.org/g/openembedded-core/message/170458
Mute This Topic: https://lists.openembedded.org/mt/93546847/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] oeqa/selftest/debuginfod: don't re-use the database

[Ross Burton]

debuginfod writes the files it scans to a database in $HOME, which isn't
ideal when the build trees that get scanned typically are deleted after
the test has finished. This can result in debuginfod trying to return
objects that no longer exist on disk:

libc error: stat 
/home/pokybuild/yocto-worker/oe-selftest-debian/build/build-st-1032306/tmp/deploy/rpm/core2_64/elfutils-dbg-0.187-r0.core2_64.rpm:
 No such file or directory
libc error: stat 
/home/pokybuild/yocto-worker/oe-selftest-debian/build/build-st-1113320/tmp/deploy/rpm/core2_64/elfutils-dbg-0.187-r0.core2_64.rpm:
 No such file or directory
libc error: stat 
/home/pokybuild/yocto-worker/oe-selftest-debian/build/build-st-1113320/tmp/deploy/rpm/core2_64/elfutils-dbg-0.187-r0.core2_64.rpm:
 No such file or directory

Solve this, and save writing a database on disk at all, by using the
special database path :memory: which keeps the database in memory only,
so state can't leak between tests.

Signed-off-by: Ross Burton 
---
 meta/lib/oeqa/selftest/cases/debuginfod.py | 19 +++
 1 file changed, 15 insertions(+), 4 deletions(-)

diff --git a/meta/lib/oeqa/selftest/cases/debuginfod.py 
b/meta/lib/oeqa/selftest/cases/debuginfod.py
index 01359ec6499..3c401192829 100644
--- a/meta/lib/oeqa/selftest/cases/debuginfod.py
+++ b/meta/lib/oeqa/selftest/cases/debuginfod.py
@@ -10,16 +10,24 @@ import subprocess
 from oeqa.selftest.case import OESelftestTestCase
 from oeqa.utils.commands import bitbake, get_bb_var, runqemu
 
+
 class Debuginfod(OESelftestTestCase):
 def test_debuginfod(self):
-self.write_config("""
+self.write_config(
+"""
 DISTRO_FEATURES:append = " debuginfod"
 CORE_IMAGE_EXTRA_INSTALL += "elfutils"
-""")
+"""
+)
 bitbake("core-image-minimal elfutils-native:do_addto_recipe_sysroot")
 
 native_sysroot = get_bb_var("RECIPE_SYSROOT_NATIVE", "elfutils-native")
-cmd = [os.path.join(native_sysroot, "usr", "bin", "debuginfod"), 
"--verbose", get_bb_var("DEPLOY_DIR")]
+cmd = [
+os.path.join(native_sysroot, "usr", "bin", "debuginfod"),
+"--verbose",
+"--database=:memory:",
+get_bb_var("DEPLOY_DIR"),
+]
 for format in get_bb_var("PACKAGE_CLASSES").split():
 if format == "package_deb":
 cmd.append("--scan-deb-dir")
@@ -36,7 +44,10 @@ CORE_IMAGE_EXTRA_INSTALL += "elfutils"
 debuginfod = subprocess.Popen(cmd)
 
 with runqemu("core-image-minimal", runqemuparams="nographic") as 
qemu:
-cmd = "DEBUGINFOD_URLS=http://%s:%d/ debuginfod-find debuginfo 
/usr/bin/debuginfod" % (qemu.server_ip, port)
+cmd = (
+"DEBUGINFOD_URLS=http://%s:%d/ debuginfod-find debuginfo 
/usr/bin/debuginfod"
+% (qemu.server_ip, port)
+)
 status, output = qemu.run_serial(cmd)
 # This should be more comprehensive
 self.assertIn("/.cache/debuginfod_client/", output)
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#170457): 
https://lists.openembedded.org/g/openembedded-core/message/170457
Mute This Topic: https://lists.openembedded.org/mt/93546450/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 1/2] gcc: remove obsolete poisoned calloc workaround

[Ross Burton]

This was fixed upstream in de6f402a, as part of 12.2.

Signed-off-by: Ross Burton 
---
 meta/recipes-devtools/gcc/gcc-12.2.inc|  1 -
 ...ched.h-include-ahead-of-user-headers.patch | 56 ---
 2 files changed, 57 deletions(-)
 delete mode 100644 
meta/recipes-devtools/gcc/gcc/0025-Move-sched.h-include-ahead-of-user-headers.patch

diff --git a/meta/recipes-devtools/gcc/gcc-12.2.inc 
b/meta/recipes-devtools/gcc/gcc-12.2.inc
index 7cc34b26215..02dc59db631 100644
--- a/meta/recipes-devtools/gcc/gcc-12.2.inc
+++ b/meta/recipes-devtools/gcc/gcc-12.2.inc
@@ -61,7 +61,6 @@ SRC_URI = "${BASEURI} \
file://0022-mingw32-Enable-operation_not_supported.patch \
file://0023-libatomic-Do-not-enforce-march-on-aarch64.patch \
file://0024-Fix-install-path-of-linux64.h.patch \
-   file://0025-Move-sched.h-include-ahead-of-user-headers.patch \
file://0026-rust-recursion-limit.patch \
file://prefix-map-realpath.patch \
file://hardcoded-paths.patch \
diff --git 
a/meta/recipes-devtools/gcc/gcc/0025-Move-sched.h-include-ahead-of-user-headers.patch
 
b/meta/recipes-devtools/gcc/gcc/0025-Move-sched.h-include-ahead-of-user-headers.patch
deleted file mode 100644
index d4aeacfed51..000
--- 
a/meta/recipes-devtools/gcc/gcc/0025-Move-sched.h-include-ahead-of-user-headers.patch
+++ /dev/null
@@ -1,56 +0,0 @@
-From 7422adfb471f4b4f2ec870124064632d55f72e50 Mon Sep 17 00:00:00 2001
-From: Khem Raj 
-Date: Mon, 11 Apr 2022 15:46:18 -0700
-Subject: [PATCH] Move sched.h include ahead of user headers
-
-Fix attempt to use poisoned calloc error, this moves the sched.h before
-using system.h from gcc headers which includes #pragma GCC poison calloc
-
-Fixes
-In file included from 
/mnt/b/yoe/master/build/tmp/work/cortexa72-yoe-linux-musl/gcc/12.0.1-r0/recipe-sysroot/usr/include/pthread.h:30,
- from 
/mnt/b/yoe/master/build/tmp/work/cortexa72-yoe-linux-musl/gcc/12.0.1-r0/recipe-sysroot/usr/include/c++/12.0.1/aarch64-yoe-linux-musl/bits/gthr-default.h:35,
- from 
/mnt/b/yoe/master/build/tmp/work/cortexa72-yoe-linux-musl/gcc/12.0.1-r0/recipe-sysroot/usr/include/c++/12.0.1/aarch64-yoe-linux-musl/bits/gthr.h:148,
- from 
/mnt/b/yoe/master/build/tmp/work/cortexa72-yoe-linux-musl/gcc/12.0.1-r0/recipe-sysroot/usr/include/c++/12.0.1/ext/atomicity.h:35,
- from 
/mnt/b/yoe/master/build/tmp/work/cortexa72-yoe-linux-musl/gcc/12.0.1-r0/recipe-sysroot/usr/include/c++/12.0.1/bits/shared_ptr_base.h:61,
- from 
/mnt/b/yoe/master/build/tmp/work/cortexa72-yoe-linux-musl/gcc/12.0.1-r0/recipe-sysroot/usr/include/c++/12.0.1/bits/shared_ptr.h:53,
- from 
/mnt/b/yoe/master/build/tmp/work/cortexa72-yoe-linux-musl/gcc/12.0.1-r0/recipe-sysroot/usr/include/c++/12.0.1/memory:77,
- from 
../../../../../../../work-shared/gcc-12.0.1-r0/gcc-12-20220410/libcc1/deleter.hh:23,
- from 
../../../../../../../work-shared/gcc-12.0.1-r0/gcc-12-20220410/libcc1/rpc.hh:25,
- from 
../../../../../../../work-shared/gcc-12.0.1-r0/gcc-12-20220410/libcc1/libcc1plugin.cc:67:
-/mnt/b/yoe/master/build/tmp/work/cortexa72-yoe-linux-musl/gcc/12.0.1-r0/recipe-sysroot/usr/include/sched.h:84:7:
 error: attempt to use poisoned "calloc"
-   84 | void *calloc(size_t, size_t);
-  |   ^
-/mnt/b/yoe/master/build/tmp/work/cortexa72-yoe-linux-musl/gcc/12.0.1-r0/recipe-sysroot/usr/include/sched.h:124:36:
 error: attempt to use poisoned "calloc"
-  124 | #define CPU_ALLOC(n) ((cpu_set_t *)calloc(1,CPU_ALLOC_SIZE(n)))
-
-Upstream-Status: Pending
-Signed-off-by: Khem Raj 

- libcc1/libcc1plugin.cc | 1 +
- libcc1/libcp1plugin.cc | 1 +
- 2 files changed, 2 insertions(+)
-
-diff --git a/libcc1/libcc1plugin.cc b/libcc1/libcc1plugin.cc
-index 12ab5a57c8d..fff9bfab18b 100644
 a/libcc1/libcc1plugin.cc
-+++ b/libcc1/libcc1plugin.cc
-@@ -17,6 +17,7 @@
-along with GCC; see the file COPYING3.  If not see
-.  */
- 
-+#include 
- #include 
- 
- #undef PACKAGE_NAME
-diff --git a/libcc1/libcp1plugin.cc b/libcc1/libcp1plugin.cc
-index 83dab7f58b1..0b83ce7a09d 100644
 a/libcc1/libcp1plugin.cc
-+++ b/libcc1/libcp1plugin.cc
-@@ -18,6 +18,7 @@
-along with GCC; see the file COPYING3.  If not see
-.  */
- 
-+#include 
- #include 
- 
- #undef PACKAGE_NAME
-- 
2.34.1


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

[OE-core] [PATCH 2/2] gcc: remove obsolete MinGW patch

[Ross Burton]

This patch appears to be obsoleted by 217d5be, in GCC 11.1 onwards.

libstdc++: Test errno macros directly for all targets [PR 93151]

This applies the same changes to the djgpp and mingw versions of
error_constants.h as r11-6137 did for the generic version.

Signed-off-by: Ross Burton 
---
 meta/recipes-devtools/gcc/gcc-12.2.inc|  1 -
 ...ngw32-Enable-operation_not_supported.patch | 26 ---
 2 files changed, 27 deletions(-)
 delete mode 100644 
meta/recipes-devtools/gcc/gcc/0022-mingw32-Enable-operation_not_supported.patch

diff --git a/meta/recipes-devtools/gcc/gcc-12.2.inc 
b/meta/recipes-devtools/gcc/gcc-12.2.inc
index 02dc59db631..0dbbecad4ad 100644
--- a/meta/recipes-devtools/gcc/gcc-12.2.inc
+++ b/meta/recipes-devtools/gcc/gcc-12.2.inc
@@ -58,7 +58,6 @@ SRC_URI = "${BASEURI} \
file://0019-Re-introduce-spe-commandline-options.patch \

file://0020-libgcc_s-Use-alias-for-__cpu_indicator_init-instead-.patch \

file://0021-gentypes-genmodes-Do-not-use-__LINE__-for-maintainin.patch \
-   file://0022-mingw32-Enable-operation_not_supported.patch \
file://0023-libatomic-Do-not-enforce-march-on-aarch64.patch \
file://0024-Fix-install-path-of-linux64.h.patch \
file://0026-rust-recursion-limit.patch \
diff --git 
a/meta/recipes-devtools/gcc/gcc/0022-mingw32-Enable-operation_not_supported.patch
 
b/meta/recipes-devtools/gcc/gcc/0022-mingw32-Enable-operation_not_supported.patch
deleted file mode 100644
index f88ad51ee8a..000
--- 
a/meta/recipes-devtools/gcc/gcc/0022-mingw32-Enable-operation_not_supported.patch
+++ /dev/null
@@ -1,26 +0,0 @@
-From 061cf79e7b6e89fdf0f2630ddaebbf1d7b271ac3 Mon Sep 17 00:00:00 2001
-From: Khem Raj 
-Date: Tue, 12 May 2020 10:39:09 -0700
-Subject: [PATCH] mingw32: Enable operation_not_supported
-
-Fixes nativesdk build errors on mingw32 gcc-runtime
-
-Upstream-Status: Pending
-Signed-off-by: Khem Raj 

- libstdc++-v3/config/os/mingw32/error_constants.h | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/libstdc++-v3/config/os/mingw32/error_constants.h 
b/libstdc++-v3/config/os/mingw32/error_constants.h
-index da5f4c2ac85..e855c86267c 100644
 a/libstdc++-v3/config/os/mingw32/error_constants.h
-+++ b/libstdc++-v3/config/os/mingw32/error_constants.h
-@@ -107,7 +107,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
- #ifdef EPERM
-   operation_not_permitted =   EPERM,
- #endif
--//operation_not_supported =   EOPNOTSUPP,
-+  operation_not_supported =   EOPNOTSUPP,
- #ifdef EWOULDBLOCK
-   operation_would_block = EWOULDBLOCK,
- #endif
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#170456): 
https://lists.openembedded.org/g/openembedded-core/message/170456
Mute This Topic: https://lists.openembedded.org/mt/93545503/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 v2] webkitgtk: Fix build on 32bit arm

[Yu, Mingli]

Hi Khem,

Thanks for your update!

But after apply your patch, there comes below issue:
/build/tmp-glibc/work/cortexa8hf-neon-wrs-linux-gnueabi/webkitgtk/2.36.7-r0/webkitgtk-2.36.7/Source/W
ebCore/platform/graphics/cpu/arm/filters/FELightingNEON.h:101:22: error: 
'JSC::Uint8ClampedArray' {aka 'class 
JSC::GenericTypedArrayView
edAdaptor>'} has no member named 'bytes'
  101 | data.pixels->bytes(),
  |  ^


Thanks,

On 9/8/22 13:31, Khem Raj wrote:

[Please note: This e-mail is from an EXTERNAL e-mail address]

Signed-off-by: Khem Raj 
Cc: Mingli Yu 
---
v2: Fix commit msg format

  ...44e17d258106617b0e6d783d073b188a2548.patch | 311 ++
  meta/recipes-sato/webkit/webkitgtk_2.36.7.bb  |   1 +
  2 files changed, 312 insertions(+)
  create mode 100644 
meta/recipes-sato/webkit/webkitgtk/0d3344e17d258106617b0e6d783d073b188a2548.patch

diff --git 
a/meta/recipes-sato/webkit/webkitgtk/0d3344e17d258106617b0e6d783d073b188a2548.patch
 
b/meta/recipes-sato/webkit/webkitgtk/0d3344e17d258106617b0e6d783d073b188a2548.patch
new file mode 100644
index 00..204f76633f
--- /dev/null
+++ 
b/meta/recipes-sato/webkit/webkitgtk/0d3344e17d258106617b0e6d783d073b188a2548.patch
@@ -0,0 +1,311 @@
+From 0d3344e17d258106617b0e6d783d073b188a2548 Mon Sep 17 00:00:00 2001
+From: Adrian Perez de Castro 
+Date: Thu, 2 Jun 2022 11:19:06 +0300
+Subject: [PATCH] [ARM][NEON] FELightningNEON.cpp fails to build, NEON fast
+ path seems unused https://bugs.webkit.org/show_bug.cgi?id=241182
+
+Reviewed by NOBODY (OOPS!).
+
+Move the NEON fast path for the SVG lighting filter effects into
+FELightingSoftwareApplier, and arrange to actually use them by
+forwarding calls to applyPlatformGeneric() into applyPlatformNeon().
+
+Some changes were needed to adapt platformApplyNeon() to the current
+state of filters after r286140. This was not detected because the code
+bitrotted due to it being guarded with CPU(ARM_TRADITIONAL), which does
+not get used much these days: CPU(ARM_THUMB2) is more common. It should
+be possible to use the NEON fast paths also in Thumb mode, but that is
+left for a follow-up fix.
+
+* Source/WebCore/platform/graphics/cpu/arm/filters/FELightingNEON.cpp:
+(WebCore::FELightingSoftwareApplier::platformApplyNeonWorker):
+(WebCore::FELightingSoftwareApplier::getPowerCoefficients):
+(WebCore::FELighting::platformApplyNeonWorker): Deleted.
+(WebCore::FELighting::getPowerCoefficients): Deleted.
+* Source/WebCore/platform/graphics/cpu/arm/filters/FELightingNEON.h:
+(WebCore::FELightingSoftwareApplier::applyPlatformNeon):
+(WebCore::FELighting::platformApplyNeon): Deleted.
+* Source/WebCore/platform/graphics/filters/DistantLightSource.h:
+* Source/WebCore/platform/graphics/filters/FELighting.h:
+* Source/WebCore/platform/graphics/filters/PointLightSource.h:
+* Source/WebCore/platform/graphics/filters/SpotLightSource.h:
+* 
Source/WebCore/platform/graphics/filters/software/FELightingSoftwareApplier.h:
+---
+Upstream-Status: Submitted [https://github.com/WebKit/WebKit/pull/1233]
+Signed-off-by: Khem Raj 
+
+ .../cpu/arm/filters/FELightingNEON.cpp|  4 +-
+ .../graphics/cpu/arm/filters/FELightingNEON.h | 54 +--
+ .../graphics/filters/DistantLightSource.h |  4 ++
+ .../platform/graphics/filters/FELighting.h|  7 ---
+ .../graphics/filters/PointLightSource.h   |  4 ++
+ .../graphics/filters/SpotLightSource.h|  4 ++
+ .../software/FELightingSoftwareApplier.h  | 16 ++
+ 7 files changed, 57 insertions(+), 36 deletions(-)
+
+diff --git 
a/Source/WebCore/platform/graphics/cpu/arm/filters/FELightingNEON.cpp 
b/Source/WebCore/platform/graphics/cpu/arm/filters/FELightingNEON.cpp
+index f6ff8c20a5a8..42a97ffc5372 100644
+--- a/Source/WebCore/platform/graphics/cpu/arm/filters/FELightingNEON.cpp
 b/Source/WebCore/platform/graphics/cpu/arm/filters/FELightingNEON.cpp
+@@ -49,7 +49,7 @@ short* feLightingConstantsForNeon()
+ return s_FELightingConstantsForNeon;
+ }
+
+-void FELighting::platformApplyNeonWorker(FELightingPaintingDataForNeon* 
parameters)
++void 
FELightingSoftwareApplier::platformApplyNeonWorker(FELightingPaintingDataForNeon*
 parameters)
+ {
+ neonDrawLighting(parameters);
+ }
+@@ -464,7 +464,7 @@ TOSTRING(neonDrawLighting) ":" NL
+ "b .lightStrengthCalculated" NL
+ ); // NOLINT
+
+-int FELighting::getPowerCoefficients(float exponent)
++int FELightingSoftwareApplier::getPowerCoefficients(float exponent)
+ {
+ // Calling a powf function from the assembly code would require to save
+ // and reload a lot of NEON registers. Since the base is in range [0..1]
+diff --git a/Source/WebCore/platform/graphics/cpu/arm/filters/FELightingNEON.h 
b/Source/WebCore/platform/graphics/cpu/arm/filters/FELightingNEON.h
+index b17c603d40d3..c6d17f573eca 100644
+--- a/Source/WebCore/platform/graphics/cpu/arm/filters/FELightingNEON.h
 b/Source/WebCore/platform/graphics/cpu/arm/filters/FELightingNEON.h
+@@ -24,14 +24,15 @@
+  * OF 

Re: [OE-core] [PATCH v11] Rust Oe-Selftest implementation

[Richard Purdie]

On Wed, 2022-09-07 at 20:27 +0530, pgowda@gmail.com wrote:
> From: pgowda 
> 
> The patch implements Rust testing framework similar to other selftest,
> specifically the gcc selftest in OE. It uses the client and server
> based method to test the binaries for cross-target on the image.
> The test framework is a wrapper around the Rust build system as ./x.py
> test. It tests many functionalities of Rust distribution like tools,
> documentation, libraries, packages, tools, Cargo, Crater etc.
> Please refer the following link for detailed description of Rust
> testing:-
> https://rustc-dev-guide.rust-lang.org/tests/intro.html#tool-tests
> 
> To support the rust tests in oe-core, the following functions were
> added:-
> setup_cargo_environment(): Build bootstrap and some early stage tools.
> do_rust_setup_snapshot(): Install the snapshot version of rust binaries.
> do_configure(): To generate config.toml
> do_compile(): To build "remote-test-server" for qemu target image.
> 
> Approximate Number of Tests Run in the Rust Testsuite :- 18000
> Approximate Number of Tests that FAIL in bitbake environment :- 100-150
> Normally majority of the testcases are present in major folder "test/"
> It contributes to more than 80% of the testcases present in Rust test
> framework. These tests pass as expected on any Rust versions without
> much fuss. The tests that fail are of less important and contribute to
> less than 2% of the total testcases. These minor tests are observed to
> work on some versions and fail on others. They have to be added, ignored
> or excluded for different versions as per the behavior.
> These tests have been ignored or excluded in the Rust selftest
> environment to generate success of completing the testsuite.
> 
> These tests work in parallel mode even in the skipped test mode as
> expected. Although the patch to disable tests is large, it is very simple
> in that it only disables tests. When updating to a newer version of Rust,
> the patch can usually be ported in a day.
> 
> Signed-off-by: pgowda 
> Signed-off-by: Vinay Kumar 
> ---
>  meta/lib/oeqa/selftest/cases/rust.py  |  54 ++
>  meta/recipes-devtools/rust/rust-source.inc|   3 +-
>  meta/recipes-devtools/rust/rust.inc   |   1 +
>  .../rust/rust/rust-oe-selftest.patch  | 508 ++
>  meta/recipes-devtools/rust/rust_1.63.0.bb |   5 +
>  5 files changed, 570 insertions(+), 1 deletion(-)
>  create mode 100644 meta/lib/oeqa/selftest/cases/rust.py
>  create mode 100644 meta/recipes-devtools/rust/rust/rust-oe-selftest.patch

I ran this through some testing on the autobuilder. The first time was
ok, it only ran on qemux86 and qemux86-64 as it was only enabled for
toolchain-system but ran successfully. 

On the second run I added @OETestTag("toolchain-user") as well which
meant it ran for arm/mips/powerpc. It looks like there was one worrying
intermittent failure:

qemux86-64 intermittent issue:
https://autobuilder.yoctoproject.org/typhoon/#/builders/73/builds/5788/steps/19/logs/stdio

and then some arch specific failures:

qemuppc failed in the test:
https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/5790/steps/19/logs/stdio

qemumips64 failed in the test:
https://autobuilder.yoctoproject.org/typhoon/#/builders/74/builds/5786/steps/20/logs/stdio

qemumips failed in the test:
https://autobuilder.yoctoproject.org/typhoon/#/builders/60/builds/5804/steps/20/logs/stdio

qemuarm64, qemuarm and qemux86 passed on this run.

We need to understand and fix that qemux86-64 intermittent issue before
this can merge. I wasn't sure what we want to do with mips and ppc.

Cheers,

Richard


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

[OE-core] [meta][dunfell][PATCH 2/2] sdbus-c++-tools: Upgrade sdbus-c++-tools 1.1.0 to 1.2.0

[Riyaz Ahmed Khan]

From: Riyaz Khan 

Update SHA value in SRCREV.

Reference link:
https://github.com/Kistler-Group/sdbus-cpp/releases/tag/v1.2.0

Signed-off-by: Riyaz Khan 
---
 .../{sdbus-c++-tools_1.1.0.bb => sdbus-c++-tools_1.2.0.bb}  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta-oe/recipes-core/sdbus-c++/{sdbus-c++-tools_1.1.0.bb => 
sdbus-c++-tools_1.2.0.bb} (88%)

diff --git a/meta-oe/recipes-core/sdbus-c++/sdbus-c++-tools_1.1.0.bb 
b/meta-oe/recipes-core/sdbus-c++/sdbus-c++-tools_1.2.0.bb
similarity index 88%
rename from meta-oe/recipes-core/sdbus-c++/sdbus-c++-tools_1.1.0.bb
rename to meta-oe/recipes-core/sdbus-c++/sdbus-c++-tools_1.2.0.bb
index 01f66c3f2..27b965ac1 100644
--- a/meta-oe/recipes-core/sdbus-c++/sdbus-c++-tools_1.1.0.bb
+++ b/meta-oe/recipes-core/sdbus-c++/sdbus-c++-tools_1.2.0.bb
@@ -8,7 +8,7 @@ inherit cmake
 
 DEPENDS += "expat"
 
-SRCREV = "bca8e81037766a0454740c40307eea32831c101f"
+SRCREV = "751c1addc4fd2f949a466f488c1b7de2ca3b76dc"
 SRC_URI = 
"git://github.com/Kistler-Group/sdbus-cpp.git;protocol=https;branch=master;subpath=tools"
 
 S = "${WORKDIR}/tools"
-- 
2.17.1


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

[OE-core] [meta][dunfell][PATCH 1/2] sdbus-c++: Upgrade sdbus-c++ 1.1.0 to 1.2.0

[Riyaz Ahmed Khan]

From: Riyaz Khan 

Add SHA value in SRCREV and remove
7f437a6e06d2ec3abd3e2fd1101ab6aab386bc44.patch as this this patch is
already part of 1.2.0 Source.

Reference link:
https://github.com/Kistler-Group/sdbus-cpp/releases/tag/v1.2.0

Signed-off-by: Riyaz Khan 
---
 ...7a6e06d2ec3abd3e2fd1101ab6aab386bc44.patch | 54 ---
 .../run-ptest |  0
 ...{sdbus-c++_1.1.0.bb => sdbus-c++_1.2.0.bb} |  5 +-
 3 files changed, 2 insertions(+), 57 deletions(-)
 delete mode 100644 
meta-oe/recipes-core/sdbus-c++/sdbus-c++-1.1.0/7f437a6e06d2ec3abd3e2fd1101ab6aab386bc44.patch
 rename meta-oe/recipes-core/sdbus-c++/{sdbus-c++-1.1.0 => 
sdbus-c++-1.2.0}/run-ptest (100%)
 rename meta-oe/recipes-core/sdbus-c++/{sdbus-c++_1.1.0.bb => 
sdbus-c++_1.2.0.bb} (91%)

diff --git 
a/meta-oe/recipes-core/sdbus-c++/sdbus-c++-1.1.0/7f437a6e06d2ec3abd3e2fd1101ab6aab386bc44.patch
 
b/meta-oe/recipes-core/sdbus-c++/sdbus-c++-1.1.0/7f437a6e06d2ec3abd3e2fd1101ab6aab386bc44.patch
deleted file mode 100644
index 641935f68..0
--- 
a/meta-oe/recipes-core/sdbus-c++/sdbus-c++-1.1.0/7f437a6e06d2ec3abd3e2fd1101ab6aab386bc44.patch
+++ /dev/null
@@ -1,54 +0,0 @@
-commit 7f437a6e06d2ec3abd3e2fd1101ab6aab386bc44
-Author: Stanislav Angelovic 
-Date:   Thu Jan 27 13:38:19 2022 +0100
-
-fix(tests): printer for std::chrono in googletest v1.11.0
-
-diff --git a/tests/CMakeLists.txt b/tests/CMakeLists.txt
-index fbf198c..ec42e55 100644
 a/tests/CMakeLists.txt
-+++ b/tests/CMakeLists.txt
-@@ -19,7 +19,7 @@ if (NOT TARGET GTest::gmock)
- if (NOT TARGET GTest::gmock)
- include(FetchContent)
- 
--message("Fetching googletest...")
-+message("Fetching googletest v${GOOGLETEST_VERSION}...")
- FetchContent_Declare(googletest
- GIT_REPOSITORY ${GOOGLETEST_GIT_REPO}
- GIT_TAGrelease-${GOOGLETEST_VERSION}
-diff --git a/tests/integrationtests/Defs.h b/tests/integrationtests/Defs.h
-index 2f129a4..2bfc7c9 100644
 a/tests/integrationtests/Defs.h
-+++ b/tests/integrationtests/Defs.h
-@@ -56,20 +56,18 @@ const bool DEFAULT_BLOCKING_VALUE{true};
- 
- constexpr const double DOUBLE_VALUE{3.24L};
- 
--/** Duration stream operator for human readable gtest value output.
-- *
-- * Note that the conversion to double is lossy if the input type has 64 or 
more bits.
-- * This is ok for our integration tests because they don't have very
-- * accurate timing requirements.
-- *
-- * @return human readable duration in seconds
-- */
-+}}
-+
-+namespace testing::internal {
-+
-+// Printer for std::chrono::duration types.
-+// This is a workaround, since it's not a good thing to add this to std 
namespace.
- template< class Rep, class Period >
--static std::ostream& operator<<(std::ostream& os, const 
std::chrono::duration& d)
--{
-+void PrintTo(const ::std::chrono::duration& d, ::std::ostream* 
os) {
- auto seconds = 
std::chrono::duration_cast>(d);
--return os << seconds.count() << " s";
-+*os << seconds.count() << "s";
-+}
-+
- }
--}}
- 
- #endif /* SDBUS_CPP_INTEGRATIONTESTS_DEFS_H_ */
diff --git a/meta-oe/recipes-core/sdbus-c++/sdbus-c++-1.1.0/run-ptest 
b/meta-oe/recipes-core/sdbus-c++/sdbus-c++-1.2.0/run-ptest
similarity index 100%
rename from meta-oe/recipes-core/sdbus-c++/sdbus-c++-1.1.0/run-ptest
rename to meta-oe/recipes-core/sdbus-c++/sdbus-c++-1.2.0/run-ptest
diff --git a/meta-oe/recipes-core/sdbus-c++/sdbus-c++_1.1.0.bb 
b/meta-oe/recipes-core/sdbus-c++/sdbus-c++_1.2.0.bb
similarity index 91%
rename from meta-oe/recipes-core/sdbus-c++/sdbus-c++_1.1.0.bb
rename to meta-oe/recipes-core/sdbus-c++/sdbus-c++_1.2.0.bb
index 107dbc6c9..75cd81553 100644
--- a/meta-oe/recipes-core/sdbus-c++/sdbus-c++_1.1.0.bb
+++ b/meta-oe/recipes-core/sdbus-c++/sdbus-c++_1.2.0.bb
@@ -16,11 +16,10 @@ PACKAGECONFIG[with-tests] = "-DBUILD_TESTS=ON 
-DTESTS_INSTALL_PATH=${libdir}/${B
 
 DEPENDS += "expat"
 
-SRCREV = "bca8e81037766a0454740c40307eea32831c101f"
+SRCREV = "751c1addc4fd2f949a466f488c1b7de2ca3b76dc"
 
 SRC_URI = 
"git://github.com/Kistler-Group/sdbus-cpp.git;protocol=https;branch=master"
-SRC_URI += "file://run-ptest \
-file://7f437a6e06d2ec3abd3e2fd1101ab6aab386bc44.patch "
+SRC_URI += "file://run-ptest"
 
 EXTRA_OECMAKE = "-DBUILD_CODE_GEN=OFF \
  -DBUILD_DOC=ON \
-- 
2.17.1


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