Re: [OE-core] [PATCH] nghttp2: Fix do_rootfs error as following:

[leimaohui]

Hi Alex,

> Lei, I'd suggest that you make a patch that simply deletes the entries for 
> -client
> and -server, and removes a dependency on them from the main package. If
> someone later needs to enable them, it should be done by creating a correct,
> working build configuration, and then re-adding packaging rules is 
> comparatively
> trivial.

Ok, I got it. I'll fix this patch in V2. Thank you for your comment. 

Best regards
Lei



> -Original Message-
> From: Alexander Kanavin 
> Sent: Friday, February 24, 2023 2:33 PM
> To: Chen Qi 
> Cc: Lei, Maohui ;
> openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH] nghttp2: Fix do_rootfs error as following:
> 
> On Fri, 24 Feb 2023 at 04:27, Chen Qi  wrote:
> > > This recipe is special. Libsoup has a hard dependency on nghttp2, so it 
> > > can't
> be moved to meta-oe. But nghttp2-client and nghttp2-server depend on recipes
> of meta-oe.
> >
> > Hi Lei,
> >
> > Which ones? Do you have some local patch or some bbappend files? Also,
> > if this is the case, I think Yocto's autobuilder will detect such
> > issue by doing pure poky world build. I also just ran `bitbake -n
> > nghttp2' and there's no error.
> 
> I have built this locally. The recipe unconditionally disables client and 
> server with
> -DENABLE_APP=OFF (no packageconfig entries to change that), and at the same
> time defines packaging for items that would otherwise be built. But there is
> nothing to put into those packages.
> 
> Lei, I'd suggest that you make a patch that simply deletes the entries for 
> -client
> and -server, and removes a dependency on them from the main package. If
> someone later needs to enable them, it should be done by creating a correct,
> working build configuration, and then re-adding packaging rules is 
> comparatively
> trivial.
> 
> Alex

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177660): 
https://lists.openembedded.org/g/openembedded-core/message/177660
Mute This Topic: https://lists.openembedded.org/mt/96872036/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] nghttp2: Fix do_rootfs error as following:

[Alexander Kanavin]

On Fri, 24 Feb 2023 at 04:27, Chen Qi  wrote:
> > This recipe is special. Libsoup has a hard dependency on nghttp2, so it 
> > can't be moved to meta-oe. But nghttp2-client and nghttp2-server depend on 
> > recipes of meta-oe.
>
> Hi Lei,
>
> Which ones? Do you have some local patch or some bbappend files? Also,
> if this is the case, I think Yocto's autobuilder will detect such issue
> by doing pure poky world build. I also just ran `bitbake -n nghttp2' and
> there's no error.

I have built this locally. The recipe unconditionally disables client
and server with -DENABLE_APP=OFF (no packageconfig entries to change
that), and at the same time defines packaging for items that would
otherwise be built. But there is nothing to put into those packages.

Lei, I'd suggest that you make a patch that simply deletes the entries
for -client and -server, and removes a dependency on them from the
main package. If someone later needs to enable them, it should be done
by creating a correct, working build configuration, and then re-adding
packaging rules is comparatively trivial.

Alex

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177659): 
https://lists.openembedded.org/g/openembedded-core/message/177659
Mute This Topic: https://lists.openembedded.org/mt/96872036/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] xcb-proto: Fix install conflict when enable multilib.

[wangmy]

From: Wang Mingyu 

Error: Transaction test error:
  file /usr/share/pkgconfig/xcb-proto.pc conflicts between attempted installs 
of lib32-xcb-proto-dev-1.15.2-r0.armv7ahf_neon and 
xcb-proto-dev-1.15.2-r0.cortexa57

Signed-off-by: Wang Mingyu 
---
 meta/recipes-graphics/xorg-proto/xcb-proto_1.15.2.bb | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-graphics/xorg-proto/xcb-proto_1.15.2.bb 
b/meta/recipes-graphics/xorg-proto/xcb-proto_1.15.2.bb
index 4e4472a9c1..0fdca732e8 100644
--- a/meta/recipes-graphics/xorg-proto/xcb-proto_1.15.2.bb
+++ b/meta/recipes-graphics/xorg-proto/xcb-proto_1.15.2.bb
@@ -28,3 +28,6 @@ DEV_PKG_DEPENDENCY = ""
 RRECOMMENDS:${PN}-dbg = "${PN}-dev (= ${EXTENDPKGV})"
 
 BBCLASSEXTEND = "native nativesdk"
+inherit multilib_script
+MULTILIB_SCRIPTS = "${PN}-dev:${datadir}/pkgconfig/xcb-proto.pc"
+
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177658): 
https://lists.openembedded.org/g/openembedded-core/message/177658
Mute This Topic: https://lists.openembedded.org/mt/97201250/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] dhcpcd: Fix install conflict when enable multilib.

[wangmy]

From: Wang Mingyu 

Error: Transaction test error:
   file /usr/share/man/man8/dhcpcd.8 conflicts between attempted installs of 
dhcpcd-doc-9.4.1-r0.cortexa57 and lib32-dhcpcd-doc-9.4.1-r0.armv7ahf_neon

Signed-off-by: Wang Mingyu 
---
 meta/recipes-connectivity/dhcpcd/dhcpcd_9.4.1.bb | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-connectivity/dhcpcd/dhcpcd_9.4.1.bb 
b/meta/recipes-connectivity/dhcpcd/dhcpcd_9.4.1.bb
index 39e689d2f6..03dbf31b35 100644
--- a/meta/recipes-connectivity/dhcpcd/dhcpcd_9.4.1.bb
+++ b/meta/recipes-connectivity/dhcpcd/dhcpcd_9.4.1.bb
@@ -62,3 +62,6 @@ do_install:append () {
 }
 
 FILES:${PN}-dbg += "${libdir}/dhcpcd/dev/.debug"
+
+inherit multilib_script
+MULTILIB_SCRIPTS = "${PN}-doc:${datadir}/man/man8/dhcpcd.8"
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177657): 
https://lists.openembedded.org/g/openembedded-core/message/177657
Mute This Topic: https://lists.openembedded.org/mt/97201249/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] checklayer: check for patch file upstream status

[Lee Chee Yang]

From: Chee Yang Lee 

yocto-check-layer to check all .patch file in layer for
Upstream-status and list down all .patch file without Upstream-Status.

set this test as expected failure for now, so this wont fail the check
layer while still able to capture any patches with malformed or missing
Upstream-Status in report.

[YOCTO #14642]

Signed-off-by: Chee Yang Lee 
---
v2:
amended commit message
switch to oe.qa.check_upstream_status to verify upstream status

 scripts/lib/checklayer/cases/common.py | 15 +++
 1 file changed, 15 insertions(+)

diff --git a/scripts/lib/checklayer/cases/common.py 
b/scripts/lib/checklayer/cases/common.py
index 722d3cf638..97b16f78c8 100644
--- a/scripts/lib/checklayer/cases/common.py
+++ b/scripts/lib/checklayer/cases/common.py
@@ -72,6 +72,21 @@ class CommonCheckLayer(OECheckLayerTestCase):
 self.tc.layer['name'])
 self.fail('\n'.join(msg))
 
+@unittest.expectedFailure
+def test_patches_upstream_status(self):
+import sys
+sys.path.append(os.path.join(sys.path[0], '../../../../meta/lib/'))
+import oe.qa
+patches = []
+for dirpath, dirs, files in os.walk(self.tc.layer['path']):
+for filename in files:
+if filename.endswith(".patch"):
+ppath = os.path.join(dirpath, filename)
+if oe.qa.check_upstream_status(ppath):
+patches.append(ppath)
+self.assertEqual(len(patches), 0 , \
+msg="Found following patches with malformed or missing 
upstream status:\n%s" % '\n'.join([str(patch) for patch in patches]))
+
 def test_signatures(self):
 if self.tc.layer['type'] == LayerType.SOFTWARE and \
not self.tc.test_software_layer_signatures:
-- 
2.37.3


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177656): 
https://lists.openembedded.org/g/openembedded-core/message/177656
Mute This Topic: https://lists.openembedded.org/mt/97199757/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] nghttp2: Fix do_rootfs error as following:

[Chen Qi]

On 2/24/23 09:45, leimao...@fujitsu.com wrote:

Hi

I'm sorry I missed this patch.


This does not seem correct. These two packages have FILES specified, and
ALLOW_EMPTY:${PN} is set to "1". I suspect the actually problem lies in
somewhere else.

This recipe is special. Libsoup has a hard dependency on nghttp2, so it can't 
be moved to meta-oe. But nghttp2-client and nghttp2-server depend on recipes of 
meta-oe.


Hi Lei,

Which ones? Do you have some local patch or some bbappend files? Also, 
if this is the case, I think Yocto's autobuilder will detect such issue 
by doing pure poky world build. I also just ran `bitbake -n nghttp2' and 
there's no error.


Regards,

Qi


I tried to fix this error according to Alex's comment by PACKAGECONFIG entries. 
But dependences is too complex to complete.
My patch is just following the existing code. But maybe it is not a best way.
I'm talking this patch with Alex, welcome to give me some suggestion.

Best regards
Lei




-Original Message-
From: ChenQi 
Sent: Friday, February 10, 2023 3:49 PM
To: Lei, Maohui ;
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] nghttp2: Fix do_rootfs error as following:

This does not seem correct. These two packages have FILES specified, and
ALLOW_EMPTY:${PN} is set to "1". I suspect the actually problem lies in
somewhere else.

Regards,
Qi

On 2/10/23 15:34, leimaohui wrote:

Problem: conflicting requests
- nothing provides nghttp2-client >= 1.51.0 needed by

nghttp2-1.51.0-r0.core2_64

- nothing provides nghttp2-server >= 1.51.0 needed by
nghttp2-1.51.0-r0.core2_64

Signed-off-by: Lei Maohui 
---
   meta/recipes-support/nghttp2/nghttp2_1.51.0.bb | 2 ++
   1 file changed, 2 insertions(+)

diff --git a/meta/recipes-support/nghttp2/nghttp2_1.51.0.bb
b/meta/recipes-support/nghttp2/nghttp2_1.51.0.bb
index 8ddb851f71..72a4372214 100644
--- a/meta/recipes-support/nghttp2/nghttp2_1.51.0.bb
+++ b/meta/recipes-support/nghttp2/nghttp2_1.51.0.bb
@@ -24,6 +24,8 @@ RDEPENDS:${PN}:class-native = ""
   RDEPENDS:${PN}-proxy = "openssl python3-core python3-io python3-shell"

   ALLOW_EMPTY:${PN} = "1"
+ALLOW_EMPTY:${PN}-server = "1"
+ALLOW_EMPTY:${PN}-client = "1"
   FILES:${PN} = ""
   FILES:lib${BPN} = "${libdir}/*${SOLIBS}"
   FILES:${PN}-client = "${bindir}/h2load ${bindir}/nghttp"






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177655): 
https://lists.openembedded.org/g/openembedded-core/message/177655
Mute This Topic: https://lists.openembedded.org/mt/96872036/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/2] Handling of ${PN}-dev RRECOMMENDS non-existent ${PN}

[Chen Qi]

I have some concerns about this series of patches.
1. The QA check is not checking for RRECOMMENDS on non-existentent 
packages, it's only checking for non-existent in-recipe packages. That 
is, it's not checking packages from other recipes.
2. If patch 2 is sent, then the patch for 'a general way to fix the 
case' should also be sent, otherwise, we'll be in a situation that a 
bunch of warnings are there but there's no suggested fix and current 
workarounds have been explicitly removed.

3. There are some typos. s/existant/existent.

Looking at the original two issues, Yocto#6839 & Yocto#8222, I agree 
that the appropriate approach is to first create a QA check. However, I 
think this QA check should either:
1. only check for non-existent main package for the dev package (as the 
default value of -dev package is the main package)

or
2. thoroughly check for non-existent packages across recipes (maybe by 
using pkgdata)


Regards,
Qi



On 2/24/23 07:29, Yoann Congal via lists.openembedded.org wrote:

This series is a work in progress on 2 related bugs :
* [YOCTO #6839] Handle dev package with no main package more gracefully
* [YOCTO #8222] Elide dependency from -dev package on main package if
   there are no shared libraries in it

An empty package ${PN} is not generated by default. This has been a
problem most frequently seen because ${PN}-dev depends on it. This case
has been handled by :
* Using ALLOW_EMPTY:${PN} = "1" : forcing ${PN} to be created even
   empty.
* DEV_PKG_DEPENDENCY = "" : Implicitly removing the dependency on ${PN}
* And finally and globally making the ${PN}-dev -> ${PN} relation a
   RRECOMMENDS.

2 patches :
* insane: Add QA check for RRECOMMENDS on non-existent packages
* meta/recipes: Remove empty ${PN}/DEV_PKG_DEPENDENCY workaround

First one create a QA check to try to detect the problematic situation.
The second removes workarounds setup to hide to problematic case.

Together they will prominently show where the problematic cases are.
Next step will be to find a generic way to fix the case.

Fawzi KHABER (2):
   insane: Add QA check for RRECOMMENDS on non-existent packages
   meta/recipes: Remove empty ${PN}/DEV_PKG_DEPENDENCY workarounds

  meta/classes-global/insane.bbclass| 11 +++
  meta/recipes-connectivity/bind/bind_9.18.11.bb|  1 -
  meta/recipes-core/musl/bsd-headers.bb |  1 -
  meta/recipes-core/musl/libssp-nonshared.bb|  1 -
  meta/recipes-core/newlib/newlib_git.bb|  3 ---
  meta/recipes-devtools/gcc/libgcc-common.inc   |  4 
  meta/recipes-devtools/python/python3_3.11.2.bb|  1 -
  meta/recipes-graphics/mesa/libglu_9.0.2.bb|  3 ---
  meta/recipes-graphics/mesa/mesa.inc   |  3 ---
  .../recipes-graphics/xorg-lib/libpthread-stubs_0.4.bb |  1 -
  meta/recipes-graphics/xorg-lib/xtrans_1.4.0.bb|  1 -
  meta/recipes-graphics/xorg-proto/xcb-proto_1.15.2.bb  |  1 -
  meta/recipes-graphics/xorg-proto/xorgproto_2022.2.bb  |  3 +--
  meta/recipes-graphics/xorg-util/util-macros_1.20.0.bb |  3 +--
  .../linux-libc-headers/linux-libc-headers.inc |  1 -
  .../make-mod-scripts/make-mod-scripts_1.0.bb  |  1 -
  .../argp-standalone/argp-standalone_1.4.1.bb  |  1 -
  17 files changed, 13 insertions(+), 27 deletions(-)







-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177654): 
https://lists.openembedded.org/g/openembedded-core/message/177654
Mute This Topic: https://lists.openembedded.org/mt/97195657/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 00/23] Pull request (cover letter only)

[Steve Sakoman]

This is the final pull request for the upcoming 4.0.8 release.

The following changes since commit 54c30e509074073b99a7a8890482ba1af2abbab9:

  oeqa context.py: fix --target-ip comment to include ssh port number 
(2023-02-11 04:06:51 -1000)

are available in the Git repository at:

  https://git.openembedded.org/openembedded-core-contrib stable/kirkstone-next
  
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/kirkstone-next

Alexander Kanavin (8):
  diffutils: update 3.8 -> 3.9
  lttng-tools: update 2.13.8 -> 2.13.9
  apr: update 1.7.0 -> 1.7.2
  apr-util: update 1.6.1 -> 1.6.3
  bind: upgrade 9.18.10 -> 9.18.11
  libjpeg-turbo: upgrade 2.1.4 -> 2.1.5
  linux-firmware: upgrade 20221214 -> 20230117
  sudo: upgrade 1.9.12p1 -> 1.9.12p2

Alexandre Belloni (1):
  oeqa/selftest/bbtests: Update message lookup for
test_git_unpack_nonetwork_fail

Kai Kang (1):
  qemu: fix compile error

Mauro Queiros (1):
  image.bbclass: print all QA functions exceptions

Mikko Rapeli (6):
  oeqa ssh.py: move output prints to new line
  oeqa ssh.py: add connection keep alive options to ssh client
  oeqa dump.py: add error counter and stop after 5 failures
  oeqa qemurunner: read more data at a time from serial
  oeqa qemurunner.py: add timeout to QMP calls
  oeqa qemurunner.py: try to avoid reading one character at a time

Peter Kjellerstedt (1):
  devshell: Do not add scripts/git-intercept to PATH

Rodolfo Quesada Zumbado (1):
  tar: CVE-2022-48303

Sakib Sajal (1):
  git: upgrade 2.35.6 -> 2.35.7

Steve Sakoman (2):
  libgit2: uprade 1.4.3 -> 1.4.4
  libgit2: upgrade 1.4.4 -> 1.4.5

Ulrich Ölmann (1):
  update-alternatives: fix typos

 meta/classes/devshell.bbclass |   2 -
 meta/classes/image.bbclass|   2 +-
 meta/classes/update-alternatives.bbclass  |   6 +-
 meta/lib/oeqa/core/target/ssh.py  |   8 +-
 meta/lib/oeqa/selftest/cases/bbtests.py   |   2 +-
 meta/lib/oeqa/utils/dump.py   |  23 +-
 meta/lib/oeqa/utils/qemurunner.py |   9 +-
 ...1-avoid-start-failure-with-bind-user.patch |   0
 ...d-V-and-start-log-hide-build-options.patch |   0
 ...ching-for-json-headers-searches-sysr.patch |   0
 .../bind/{bind-9.18.10 => bind-9.18.11}/bind9 |   0
 .../{bind-9.18.10 => bind-9.18.11}/conf.patch |   0
 .../generate-rndc-key.sh  |   0
 ...t.d-add-support-for-read-only-rootfs.patch |   0
 .../make-etc-initd-bind-stop-work.patch   |   0
 .../named.service |   0
 .../bind/{bind_9.18.10.bb => bind_9.18.11.bb} |   4 +-
 .../git/{git_2.35.6.bb => git_2.35.7.bb}  |   2 +-
 meta/recipes-devtools/qemu/qemu.inc   |   2 +
 ...ave-qxl_log_command-Return-early-if-.patch |  57 +
 ...ass-requested-buffer-size-to-qxl_phy.patch | 217 ++
 ...001-Skip-strip-trailing-cr-test-case.patch |  11 +-
 ...a-standard-layout-so-glibc-and-musl-.patch |  33 ---
 .../{diffutils_3.8.bb => diffutils_3.9.bb}|   3 +-
 .../{sudo_1.9.12p1.bb => sudo_1.9.12p2.bb}|   2 +-
 .../tar/tar/CVE-2022-48303.patch  |  43 
 meta/recipes-extended/tar/tar_1.34.bb |   4 +-
 ...-turbo_2.1.4.bb => libjpeg-turbo_2.1.5.bb} |   2 +-
 ...20221214.bb => linux-firmware_20230117.bb} |   6 +-
 .../lttng/lttng-tools/determinism.patch   |  64 --
 ...-tools_2.13.8.bb => lttng-tools_2.13.9.bb} |   3 +-
 .../0001-Fix-error-handling-in-gdbm.patch | 134 ---
 .../{apr-util_1.6.1.bb => apr-util_1.6.3.bb}  |   6 +-
 ...ion-to-disable-timed-dependant-tests.patch |  20 +-
 ...CHE_CHECK-for-strerror_r-return-type.patch |  52 -
 ...-runtime-test-for-mmap-that-can-map-.patch |  26 +--
 ...ir-path-references-from-installed-ap.patch |  25 +-
 ...configure.in-support-cross-compiling.patch |  63 -
 ...ze-doesn-t-match-in-glibc-when-cross.patch |  76 --
 .../apr/apr/CVE-2021-35940.patch  |  58 -
 .../recipes-support/apr/apr/autoconf270.patch |  22 --
 .../apr/apr/libtoolize_check.patch|  21 +-
 .../apr/{apr_1.7.0.bb => apr_1.7.2.bb}|   8 +-
 .../{libgit2_1.4.3.bb => libgit2_1.4.5.bb}|   2 +-
 44 files changed, 430 insertions(+), 588 deletions(-)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => 
bind-9.18.11}/0001-avoid-start-failure-with-bind-user.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => 
bind-9.18.11}/0001-named-lwresd-V-and-start-log-hide-build-options.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => 
bind-9.18.11}/bind-ensure-searching-for-json-headers-searches-sysr.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => bind-9.18.11}/bind9 
(100%)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => 
bind-9.18.11}/conf.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => 
bind-9.18.11}/generate-rndc-key.sh (100%)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => 
bind-9.18.11}/init.d-add-support-for-read-only-rootfs.patch (100%)

[OE-core] [PATCH 4/4] vala: Fix install conflict when enable multilib.

[wangmy]

From: Wang Mingyu 

Error: Transaction test error:
  file /usr/bin/padsp conflicts between attempted installs of 
lib32-pulseaudio-misc-16.1-r0.armv7ahf_neon and pulseaudio-misc-16.1-r0.aarch64

Signed-off-by: Wang Mingyu 
---
 meta/recipes-multimedia/pulseaudio/pulseaudio_16.1.bb | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-multimedia/pulseaudio/pulseaudio_16.1.bb 
b/meta/recipes-multimedia/pulseaudio/pulseaudio_16.1.bb
index 64002cd1cc..686ffe9203 100644
--- a/meta/recipes-multimedia/pulseaudio/pulseaudio_16.1.bb
+++ b/meta/recipes-multimedia/pulseaudio/pulseaudio_16.1.bb
@@ -8,3 +8,6 @@ SRC_URI = 
"http://freedesktop.org/software/pulseaudio/releases/${BP}.tar.xz \
"
 SRC_URI[sha256sum] = 
"8eef32ce91d47979f95fd9a935e738cd7eb7463430dabc72863251751e504ae4"
 UPSTREAM_CHECK_REGEX = "pulseaudio-(?P\d+(\.(?!99)\d+)+)\.tar"
+
+inherit multilib_script
+MULTILIB_SCRIPTS = "${PN}-misc:${bindir}/padsp"
-- 
2.34.1


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

[OE-core] [PATCH 3/4] bash: Fix install conflict when enable multilib.

[wangmy]

From: Wang Mingyu 

Error: Transaction test error:
  file /usr/bin/bashbug conflicts between attempted installs of 
lib32-bash-bashbug-5.2.15-r0.armv7ahf_neon and bash-bashbug-5.2.15-r0.aarch64

Signed-off-by: Wang Mingyu 
---
 meta/recipes-extended/bash/bash_5.2.15.bb | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-extended/bash/bash_5.2.15.bb 
b/meta/recipes-extended/bash/bash_5.2.15.bb
index f78f79fcc5..ce81496f52 100644
--- a/meta/recipes-extended/bash/bash_5.2.15.bb
+++ b/meta/recipes-extended/bash/bash_5.2.15.bb
@@ -20,3 +20,6 @@ DEBUG_OPTIMIZATION:append:armv4 = " 
${@bb.utils.contains('TUNE_CCARGS', '-mthumb
 DEBUG_OPTIMIZATION:append:armv5 = " ${@bb.utils.contains('TUNE_CCARGS', 
'-mthumb', '-fomit-frame-pointer', '', d)}"
 
 BBCLASSEXTEND = "nativesdk"
+
+inherit multilib_script
+MULTILIB_SCRIPTS = "${PN}-bashbug:${bindir}/bashbug"
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177651): 
https://lists.openembedded.org/g/openembedded-core/message/177651
Mute This Topic: https://lists.openembedded.org/mt/97198853/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/4] vala: Fix install conflict when enable multilib.

[wangmy]

From: Wang Mingyu 

Error: Transaction test error:
  file /usr/bin/vala-gen-introspect-0.56 conflicts between attempted installs 
of lib32-vala-0.56.3-r0.armv7ahf_neon and vala-0.56.3-r0.aarch64
  file /usr/bin/vapigen-wrapper conflicts between attempted installs of 
lib32-vala-0.56.3-r0.armv7ahf_neon and vala-0.56.3-r0.aarch64

Signed-off-by: Wang Mingyu 
---
 meta/recipes-devtools/vala/vala.inc | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-devtools/vala/vala.inc 
b/meta/recipes-devtools/vala/vala.inc
index d3daee37dc..90689662cb 100644
--- a/meta/recipes-devtools/vala/vala.inc
+++ b/meta/recipes-devtools/vala/vala.inc
@@ -66,3 +66,6 @@ PACKAGE_PREPROCESS_FUNCS += "vala_package_preprocess"
 vala_package_preprocess () {
sed -i -e 's:${RECIPE_SYSROOT}::g;' 
${PKGD}${bindir_crossscripts}/vapigen-wrapper
 }
+
+inherit multilib_script
+MULTILIB_SCRIPTS = "${PN}:${bindir}/crossscripts/vapigen-wrapper 
${PN}:${bindir}/vala-gen-introspect-0.56"
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177650): 
https://lists.openembedded.org/g/openembedded-core/message/177650
Mute This Topic: https://lists.openembedded.org/mt/97198850/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/4] lua: Fix install conflict when enable multilib.

[wangmy]

From: Wang Mingyu 

Error: Transaction test error:
  file /usr/include/luaconf.h conflicts between attempted installs of 
lua-dev-5.4.4-r0.aarch64 and lib32-lua-dev-5.4.4-r0.armv7ahf_neon

Signed-off-by: Wang Mingyu 
---
 meta/recipes-devtools/lua/lua_5.4.4.bb | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-devtools/lua/lua_5.4.4.bb 
b/meta/recipes-devtools/lua/lua_5.4.4.bb
index 0b2e754b31..a39d888ec2 100644
--- a/meta/recipes-devtools/lua/lua_5.4.4.bb
+++ b/meta/recipes-devtools/lua/lua_5.4.4.bb
@@ -57,3 +57,6 @@ do_install_ptest () {
 }
 
 BBCLASSEXTEND = "native nativesdk"
+
+inherit multilib_script
+MULTILIB_SCRIPTS = "${PN}-dev:${includedir}/luaconf.h"
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177649): 
https://lists.openembedded.org/g/openembedded-core/message/177649
Mute This Topic: https://lists.openembedded.org/mt/97198848/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] binutils: Enable --enable-new-dtags

[Khem Raj]

On Thu, Feb 23, 2023 at 3:34 PM Alexandre Belloni
 wrote:
>
> Could this be the cause of this?
>
> https://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20230223-79c9rmcw/packages/diff-html/

most likely yes. I will take a look. Lets work on merging the other
binutils and gdb upgrade patch meanwhile.

>
> On 22/02/2023 22:58:16-0800, Khem Raj wrote:
> > Use DT_RUNPATH over DT_RPATH. If DT_RUNPATH is present, LD_LIBRARY_PATH is 
> > searched before
> > DT_RUNPATH, Search order is DT_RPATH then LD_LIBRARY_PATH then
> > DT_RUNPATH, this order ensures that injecting
> > malicious shared objects is way harder with DT_RUNPATH.
> >
> > This is now default on major linux distributions already
> >
> > Signed-off-by: Khem Raj 
> > ---
> >  meta/recipes-devtools/binutils/binutils.inc | 1 +
> >  1 file changed, 1 insertion(+)
> >
> > diff --git a/meta/recipes-devtools/binutils/binutils.inc 
> > b/meta/recipes-devtools/binutils/binutils.inc
> > index b2dbf241df..c69d29448f 100644
> > --- a/meta/recipes-devtools/binutils/binutils.inc
> > +++ b/meta/recipes-devtools/binutils/binutils.inc
> > @@ -96,6 +96,7 @@ EXTRA_OECONF = "--program-prefix=${TARGET_PREFIX} \
> >  --disable-werror \
> >  --enable-deterministic-archives \
> >  --enable-plugins \
> > +--enable-new-dtags \
> >  --disable-gdb \
> >  --disable-gdbserver \
> >  --disable-libdecnumber \
> > --
> > 2.39.2
> >
>
> >
> > 
> >
>
>
> --
> 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 (#177648): 
https://lists.openembedded.org/g/openembedded-core/message/177648
Mute This Topic: https://lists.openembedded.org/mt/97178429/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] checklayer: check for patch file upstream status

[Lee Chee Yang]

> -Original Message-
> From: Richard Purdie 
> Sent: Thursday, February 23, 2023 9:49 PM
> To: Bruce Ashfield ; Lee, Chee Yang
> 
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH] checklayer: check for patch file upstream
> status
> 
> On Thu, 2023-02-23 at 08:33 -0500, Bruce Ashfield wrote:
> > I don't recall the upstream-status being added as a yocto
> > compatibility requirement. Can someone point me to a discussion that I
> > missed ?
> 
> It isn't a requirement at this time and there isn't any recent discussion 
> you've
> missed.

Sorry that I misunderstand the discussion in the bug ticket.
Would update the commit message to avoid confusion.


> 
> The topic has come up now and again at various points, including with the YP
> TSC and I suspect that was why we have
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=14642 from back in 2021. I
> think the view of the YP TSC was that we probably should warn about things
> like this from yocto-check-layer perspective as it is a best practise we want 
> to
> raise the profile of.
> 
> > As everyone can recall, I wasn't on board with this being a default QA
> > check and error, and I'm also not on board with it being a yocto
> > compliance error.
> >
> > I realize it isn't being made an error in this patch, but I wanted to
> > raise my concerns now, before someone throws that switch.
> 
> Your concerns are definitely known! As I said at the time in the discussion,
> the TSC does intend to add some extra checks around QA issues to YP
> Compatible but no decision on which ones has been made yet, I think that
> action rests with me to make a proposal. My view is this one can remain a
> warning, I can't speak for the rest of the TSC. I do think having yocto-check-
> layer show more warnings about best practises if the direction things will
> move though even if it doesn't change the resulting compatibility status.
> 
> There is an intent to improve "quality" over time so I can't promise this will
> never become an error but I don't have any plans to push this beyond a
> warning. As above, I can't speak for all TSC members though.
> 
> Cheers,
> 
> Richard
> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177647): 
https://lists.openembedded.org/g/openembedded-core/message/177647
Mute This Topic: https://lists.openembedded.org/mt/97178225/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] nghttp2: Fix do_rootfs error as following:

[leimaohui]

Hi

I'm sorry I missed this patch.

> This does not seem correct. These two packages have FILES specified, and
> ALLOW_EMPTY:${PN} is set to "1". I suspect the actually problem lies in
> somewhere else.

This recipe is special. Libsoup has a hard dependency on nghttp2, so it can't 
be moved to meta-oe. But nghttp2-client and nghttp2-server depend on recipes of 
meta-oe.
I tried to fix this error according to Alex's comment by PACKAGECONFIG entries. 
But dependences is too complex to complete.
My patch is just following the existing code. But maybe it is not a best way.
I'm talking this patch with Alex, welcome to give me some suggestion.

Best regards
Lei



> -Original Message-
> From: ChenQi 
> Sent: Friday, February 10, 2023 3:49 PM
> To: Lei, Maohui ;
> openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH] nghttp2: Fix do_rootfs error as following:
> 
> This does not seem correct. These two packages have FILES specified, and
> ALLOW_EMPTY:${PN} is set to "1". I suspect the actually problem lies in
> somewhere else.
> 
> Regards,
> Qi
> 
> On 2/10/23 15:34, leimaohui wrote:
> > Problem: conflicting requests
> >- nothing provides nghttp2-client >= 1.51.0 needed by
> nghttp2-1.51.0-r0.core2_64
> >- nothing provides nghttp2-server >= 1.51.0 needed by
> > nghttp2-1.51.0-r0.core2_64
> >
> > Signed-off-by: Lei Maohui 
> > ---
> >   meta/recipes-support/nghttp2/nghttp2_1.51.0.bb | 2 ++
> >   1 file changed, 2 insertions(+)
> >
> > diff --git a/meta/recipes-support/nghttp2/nghttp2_1.51.0.bb
> > b/meta/recipes-support/nghttp2/nghttp2_1.51.0.bb
> > index 8ddb851f71..72a4372214 100644
> > --- a/meta/recipes-support/nghttp2/nghttp2_1.51.0.bb
> > +++ b/meta/recipes-support/nghttp2/nghttp2_1.51.0.bb
> > @@ -24,6 +24,8 @@ RDEPENDS:${PN}:class-native = ""
> >   RDEPENDS:${PN}-proxy = "openssl python3-core python3-io python3-shell"
> >
> >   ALLOW_EMPTY:${PN} = "1"
> > +ALLOW_EMPTY:${PN}-server = "1"
> > +ALLOW_EMPTY:${PN}-client = "1"
> >   FILES:${PN} = ""
> >   FILES:lib${BPN} = "${libdir}/*${SOLIBS}"
> >   FILES:${PN}-client = "${bindir}/h2load ${bindir}/nghttp"
> >
> > 
> >


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177646): 
https://lists.openembedded.org/g/openembedded-core/message/177646
Mute This Topic: https://lists.openembedded.org/mt/96872036/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] nghttp2: Fix do_rootfs error as following:

[leimaohui]

Hi, Alex

I'm sorry for late reply.

> If neither client nor server packages contain any files, then what is 
> installed? Is
> there some other useful package than nghttp2 package pulls in, or does it 
> itself
> contain something useful?

I found this conflicting requests error when I added nghttp2 package into my 
image file by accident. 
Although there is no files in nghttp2 package, it is really an issue, isn't it?

My patch is just following the existing code. But maybe it is not a best way.
How about deleted the RDEPENDS relationships among nghttp2, -client and -server?

$ cat ./meta/recipes-support/nghttp2/nghttp2_1.52.0.bb
..
RDEPENDS:${PN} = "${PN}-client (>= ${PV}) ${PN}-proxy (>= ${PV}) ${PN}-server 
(>= ${PV})"
..


Best regards
Lei

> -Original Message-
> From: Alexander Kanavin 
> Sent: Friday, February 10, 2023 3:44 PM
> To: Lei, Maohui 
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH] nghttp2: Fix do_rootfs error as following:
> 
> If neither client nor server packages contain any files, then what is 
> installed? Is
> there some other useful package than nghttp2 package pulls in, or does it 
> itself
> contain something useful?
> 
> Alex
> 
> On Fri, 10 Feb 2023 at 08:35, leimaohui  wrote:
> >
> > Problem: conflicting requests
> >   - nothing provides nghttp2-client >= 1.51.0 needed by
> nghttp2-1.51.0-r0.core2_64
> >   - nothing provides nghttp2-server >= 1.51.0 needed by
> > nghttp2-1.51.0-r0.core2_64
> >
> > Signed-off-by: Lei Maohui 
> > ---
> >  meta/recipes-support/nghttp2/nghttp2_1.51.0.bb | 2 ++
> >  1 file changed, 2 insertions(+)
> >
> > diff --git a/meta/recipes-support/nghttp2/nghttp2_1.51.0.bb
> > b/meta/recipes-support/nghttp2/nghttp2_1.51.0.bb
> > index 8ddb851f71..72a4372214 100644
> > --- a/meta/recipes-support/nghttp2/nghttp2_1.51.0.bb
> > +++ b/meta/recipes-support/nghttp2/nghttp2_1.51.0.bb
> > @@ -24,6 +24,8 @@ RDEPENDS:${PN}:class-native = ""
> >  RDEPENDS:${PN}-proxy = "openssl python3-core python3-io python3-shell"
> >
> >  ALLOW_EMPTY:${PN} = "1"
> > +ALLOW_EMPTY:${PN}-server = "1"
> > +ALLOW_EMPTY:${PN}-client = "1"
> >  FILES:${PN} = ""
> >  FILES:lib${BPN} = "${libdir}/*${SOLIBS}"
> >  FILES:${PN}-client = "${bindir}/h2load ${bindir}/nghttp"
> > --
> > 2.34.1
> >
> >
> > 
> >

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177645): 
https://lists.openembedded.org/g/openembedded-core/message/177645
Mute This Topic: https://lists.openembedded.org/mt/96872036/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][PATCHv3] vte: update 0.70.2 -> 0.70.3

[Markus Volk]

I cant reproduce this. I've built core-image-sato multilib and rootfs 
was created without an issue


Am Fr, 24. Feb 2023 um 00:28:30 +0100 schrieb Alexandre Belloni via 
lists.openembedded.org 
:

I'm sorry I didn't catch it earlier but this is also the cause of:

ERROR: core-image-sato-1.0-r0 do_rootfs: Multilib check error: 
duplicate files 
/home/pokybuild/yocto-worker/multilib/build/build/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0-r0/multilib/lib32/usr/share/glib-2.0/schemas/gschemas.compiled 
/home/pokybuild/yocto-worker/multilib/build/build/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0-r0/rootfs/usr/share/glib-2.0/schemas/gschemas.compiled 
is not the same




On 23/02/2023 08:52:56+0100, Markus Volk wrote:

 - Allow to build the gtk4 widget and vapi
   This is needed to build gtk4 based terminals like blackbox
 - Update dependencies
 - Cleanup recipe

 Signed-off-by: Markus Volk >

 ---
  .../vte/{vte_0.70.2.bb => vte_0.70.3.bb}  | 22 
+--

  1 file changed, 11 insertions(+), 11 deletions(-)
  rename meta/recipes-support/vte/{vte_0.70.2.bb => vte_0.70.3.bb} 
(71%)


 diff --git a/meta/recipes-support/vte/vte_0.70.2.bb 
b/meta/recipes-support/vte/vte_0.70.3.bb

 similarity index 71%
 rename from meta/recipes-support/vte/vte_0.70.2.bb
 rename to meta/recipes-support/vte/vte_0.70.3.bb
 index ec2fb1f522..474ed87a88 100644
 --- a/meta/recipes-support/vte/vte_0.70.2.bb
 +++ b/meta/recipes-support/vte/vte_0.70.3.bb
 @@ -11,34 +11,34 @@ LIC_FILES_CHKSUM = " \
  file://COPYING.XTERM;md5=d7fc3a23c16c039afafe2e042030f057 
 \

  "

 -DEPENDS = "glib-2.0 gtk+3 libpcre2 libxml2-native gperf-native icu"
 +DEPENDS = "fribidi glib-2.0 gtk+3 libpcre2 libxml2-native 
gperf-native icu pango zlib"


  GNOMEBASEBUILDCLASS = "meson"
  GIR_MESON_OPTION = 'gir'
  GIDOCGEN_MESON_OPTION = "docs"

 -inherit gnomebase gi-docgen features_check 
upstream-version-is-even gobject-introspection
 +inherit gnomebase gi-docgen features_check 
upstream-version-is-even gobject-introspection vala


 -# vapigen.m4 is required when vala is not present (but the one 
from vala should be used normally)
  SRC_URI += 
"file://0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch" 

 -SRC_URI[archive.sha256sum] = 
"4d15b4380de3f564d57eabd006389c407c705df5b0c70030fdcc24971a334d80"
 +SRC_URI[archive.sha256sum] = 
"9457134a02f3157fca04f7e0d39bdb0f3099be0a3ce82b7139d0c98a80748f23"


  ANY_OF_DISTRO_FEATURES = "${GTK3DISTROFEATURES}"

 -# Help g-ir-scanner find the .so for linking
 -do_compile:prepend() {
 -export GIR_EXTRA_LIBS_PATH="${B}/src/.libs"
 -}
 -
  # Package additional files
  FILES:${PN}-dev += "${datadir}/vala/vapi/*"

 -PACKAGECONFIG ??= "gnutls"
 -PACKAGECONFIG[vala] = "-Dvapi=true,-Dvapi=false,vala-native vala"
 +PACKAGECONFIG ??= " \
 +gnutls \
 +${@bb.utils.contains 
('DISTRO_FEATURES', 
'gobject-introspection-data', 'vala', '', d)} \
 +${@bb.utils.contains 
('DISTRO_FEATURES', 'opengl', 'gtk4', 
'', d)} \

 +"
 +PACKAGECONFIG[gtk4] = "-Dgtk4=true,-Dgtk4=false,gtk4"
 +PACKAGECONFIG[vala] = "-Dvapi=true,-Dvapi=false"
  PACKAGECONFIG[gnutls] = "-Dgnutls=true,-Dgnutls=false,gnutls"
  PACKAGECONFIG[systemd] = "-D_systemd=true,-D_systemd=false,systemd"
  # vala requires gir
  PACKAGECONFIG:remove:class-native = "vala"
 +PACKAGECONFIG:remove:class-nativesdk = "vala gtk4"

  CFLAGS += "-D_GNU_SOURCE"

 --
 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 (#177644): 
https://lists.openembedded.org/g/openembedded-core/message/177644
Mute This Topic: https://lists.openembedded.org/mt/97178843/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] binutils: Enable --enable-new-dtags

[Alexandre Belloni via lists.openembedded.org]

Could this be the cause of this?

https://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20230223-79c9rmcw/packages/diff-html/

On 22/02/2023 22:58:16-0800, Khem Raj wrote:
> Use DT_RUNPATH over DT_RPATH. If DT_RUNPATH is present, LD_LIBRARY_PATH is 
> searched before
> DT_RUNPATH, Search order is DT_RPATH then LD_LIBRARY_PATH then
> DT_RUNPATH, this order ensures that injecting
> malicious shared objects is way harder with DT_RUNPATH.
> 
> This is now default on major linux distributions already
> 
> Signed-off-by: Khem Raj 
> ---
>  meta/recipes-devtools/binutils/binutils.inc | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/meta/recipes-devtools/binutils/binutils.inc 
> b/meta/recipes-devtools/binutils/binutils.inc
> index b2dbf241df..c69d29448f 100644
> --- a/meta/recipes-devtools/binutils/binutils.inc
> +++ b/meta/recipes-devtools/binutils/binutils.inc
> @@ -96,6 +96,7 @@ EXTRA_OECONF = "--program-prefix=${TARGET_PREFIX} \
>  --disable-werror \
>  --enable-deterministic-archives \
>  --enable-plugins \
> +--enable-new-dtags \
>  --disable-gdb \
>  --disable-gdbserver \
>  --disable-libdecnumber \
> -- 
> 2.39.2
> 

> 
> 
> 


-- 
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 (#177643): 
https://lists.openembedded.org/g/openembedded-core/message/177643
Mute This Topic: https://lists.openembedded.org/mt/97178429/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] meta/recipes: Remove empty ${PN}/DEV_PKG_DEPENDENCY workarounds

[Yoann Congal]

From: Fawzi KHABER 

Remove superfluous DEV_PKG_DEPENDENCY = "" previously used to bypass
${PN}-dev package RDEPENDS on empty ${PN}. DEV_PKG_DEPENDENCY
applies RRECOMMENDS now, all workarounds are not needed anymore.

Related to [YOCTO #6839]

Signed-off-by: Yoann CONGAL 
Signed-off-by: Fawzi KHABER 
---
 meta/recipes-connectivity/bind/bind_9.18.11.bb| 1 -
 meta/recipes-core/musl/bsd-headers.bb | 1 -
 meta/recipes-core/musl/libssp-nonshared.bb| 1 -
 meta/recipes-core/newlib/newlib_git.bb| 3 ---
 meta/recipes-devtools/gcc/libgcc-common.inc   | 4 
 meta/recipes-devtools/python/python3_3.11.2.bb| 1 -
 meta/recipes-graphics/mesa/libglu_9.0.2.bb| 3 ---
 meta/recipes-graphics/mesa/mesa.inc   | 3 ---
 meta/recipes-graphics/xorg-lib/libpthread-stubs_0.4.bb| 1 -
 meta/recipes-graphics/xorg-lib/xtrans_1.4.0.bb| 1 -
 meta/recipes-graphics/xorg-proto/xcb-proto_1.15.2.bb  | 1 -
 meta/recipes-graphics/xorg-proto/xorgproto_2022.2.bb  | 3 +--
 meta/recipes-graphics/xorg-util/util-macros_1.20.0.bb | 3 +--
 meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc | 1 -
 meta/recipes-kernel/make-mod-scripts/make-mod-scripts_1.0.bb  | 1 -
 meta/recipes-support/argp-standalone/argp-standalone_1.4.1.bb | 1 -
 16 files changed, 2 insertions(+), 27 deletions(-)

diff --git a/meta/recipes-connectivity/bind/bind_9.18.11.bb 
b/meta/recipes-connectivity/bind/bind_9.18.11.bb
index 55a06eae5f..b2e8e615c9 100644
--- a/meta/recipes-connectivity/bind/bind_9.18.11.bb
+++ b/meta/recipes-connectivity/bind/bind_9.18.11.bb
@@ -111,4 +111,3 @@ FILES_SOLIBSDEV = "${libdir}/*[!0-9].so 
${libdir}/libbind9.so"
 FILES:${PN}-libs = "${libdir}/named/*.so* ${libdir}/*-${PV}.so"
 FILES:${PN}-staticdev += "${libdir}/*.la"
 
-DEV_PKG_DEPENDENCY = ""
diff --git a/meta/recipes-core/musl/bsd-headers.bb 
b/meta/recipes-core/musl/bsd-headers.bb
index 887a816031..8a2f4177a7 100644
--- a/meta/recipes-core/musl/bsd-headers.bb
+++ b/meta/recipes-core/musl/bsd-headers.bb
@@ -27,5 +27,4 @@ do_install() {
 #
 
 COMPATIBLE_HOST = ".*-musl.*"
-DEV_PKG_DEPENDENCY = ""
 RRECOMMENDS:${PN}-dbg = "${PN}-dev (= ${EXTENDPKGV})"
diff --git a/meta/recipes-core/musl/libssp-nonshared.bb 
b/meta/recipes-core/musl/libssp-nonshared.bb
index 3faf8f00c3..982bcc47a5 100644
--- a/meta/recipes-core/musl/libssp-nonshared.bb
+++ b/meta/recipes-core/musl/libssp-nonshared.bb
@@ -31,5 +31,4 @@ do_install() {
 #
 COMPATIBLE_HOST = ".*-musl.*"
 RDEPENDS:${PN}-staticdev = ""
-DEV_PKG_DEPENDENCY = ""
 RRECOMMENDS:${PN}-dbg = "${PN}-staticdev (= ${EXTENDPKGV})"
diff --git a/meta/recipes-core/newlib/newlib_git.bb 
b/meta/recipes-core/newlib/newlib_git.bb
index fb922d65d1..a3687f5e67 100644
--- a/meta/recipes-core/newlib/newlib_git.bb
+++ b/meta/recipes-core/newlib/newlib_git.bb
@@ -15,6 +15,3 @@ do_install:append() {
# Remove original directory
rmdir ${D}${prefix}/${TARGET_SYS}
 }
-
-# No rpm package is actually created but -dev depends on it, avoid dnf error
-DEV_PKG_DEPENDENCY:libc-newlib = ""
diff --git a/meta/recipes-devtools/gcc/libgcc-common.inc 
b/meta/recipes-devtools/gcc/libgcc-common.inc
index d9084af51a..7e357af3b9 100644
--- a/meta/recipes-devtools/gcc/libgcc-common.inc
+++ b/meta/recipes-devtools/gcc/libgcc-common.inc
@@ -54,10 +54,6 @@ do_install:append:libc-newlib () {
fi
 }
 
-# No rpm package is actually created but -dev depends on it, avoid dnf error
-DEV_PKG_DEPENDENCY:libc-baremetal = ""
-DEV_PKG_DEPENDENCY:libc-newlib = ""
-
 BBCLASSEXTEND = "nativesdk"
 
 addtask multilib_install after do_install before do_package do_populate_sysroot
diff --git a/meta/recipes-devtools/python/python3_3.11.2.bb 
b/meta/recipes-devtools/python/python3_3.11.2.bb
index 43c147ca6d..52a75faf7d 100644
--- a/meta/recipes-devtools/python/python3_3.11.2.bb
+++ b/meta/recipes-devtools/python/python3_3.11.2.bb
@@ -430,7 +430,6 @@ RDEPENDS:${PN}-ptest = "${PN}-modules ${PN}-tests ${PN}-dev 
unzip bzip2 libgcc t
 RDEPENDS:${PN}-ptest:append:libc-glibc = " locale-base-tr-tr.iso-8859-9"
 RDEPENDS:${PN}-tkinter += "${@bb.utils.contains('PACKAGECONFIG', 'tk', 
'${MLPREFIX}tk ${MLPREFIX}tk-lib', '', d)}"
 RDEPENDS:${PN}-idle += "${@bb.utils.contains('PACKAGECONFIG', 'tk', 
'${PN}-tkinter ${MLPREFIX}tcl', '', d)}"
-DEV_PKG_DEPENDENCY = ""
 RDEPENDS:${PN}-pydoc += "${PN}-io"
 
 RDEPENDS:${PN}-tests:append:class-target = " ${MLPREFIX}bash"
diff --git a/meta/recipes-graphics/mesa/libglu_9.0.2.bb 
b/meta/recipes-graphics/mesa/libglu_9.0.2.bb
index 525d631611..30d6034cee 100644
--- a/meta/recipes-graphics/mesa/libglu_9.0.2.bb
+++ b/meta/recipes-graphics/mesa/libglu_9.0.2.bb
@@ -25,6 +25,3 @@ inherit autotools pkgconfig features_check
 
 # Requires libGL.so which is provided by mesa when x11 in DISTRO_FEATURES
 REQUIRED_DISTRO_FEATURES = "x11 opengl"
-
-# Remove the mesa-glu 

[OE-core] [PATCH 1/2] insane: Add QA check for RRECOMMENDS on non-existent packages

[Yoann Congal]

From: Fawzi KHABER 

Add a package QA check for when a package RRECOMMENDS another that won't
be built because it is empty and ALLOW_EMPTY is not set. This happens
usually when ${PN}-dev RRECOMMENDS ${PN} but ${PN} is empty. This is not
an error but might be something to look into.

Example of a generated warning:
WARNING: python3-3.11.2-r0 do_package_qa:
QA Issue: python3-dev -> python3 but won't be build [rrecommends-non-existant]

This will make [YOCTO #8222] appears in the QA logs.

Signed-off-by: Yoann Congal 
Signed-off-by: Fawzi KHABER 
---
 meta/classes-global/insane.bbclass | 11 +++
 1 file changed, 11 insertions(+)

diff --git a/meta/classes-global/insane.bbclass 
b/meta/classes-global/insane.bbclass
index ee34d5208d..a3e8c57955 100644
--- a/meta/classes-global/insane.bbclass
+++ b/meta/classes-global/insane.bbclass
@@ -34,6 +34,7 @@ WARN_QA ?= " libdir xorg-driver-abi buildpaths \
 missing-update-alternatives native-last missing-ptest \
 license-exists license-no-generic license-syntax license-format \
 license-incompatible license-file-missing obsolete-license \
+rrecommends-non-existant \
 "
 ERROR_QA ?= "dev-so debug-deps dev-deps debug-files arch pkgconfig la \
 perms dep-cmp pkgvarcheck perm-config perm-line perm-link \
@@ -1089,6 +1090,16 @@ def package_qa_check_empty_dirs(pkg, d, messages):
 msg = "%s installs files in %s, %s" % (pkg, dir, recommendation)
 oe.qa.add_message(messages, "empty-dirs", msg)
 
+QAPKGTEST[rrecommends-non-existant] = 
"package_qa_check_rrecommends_non_existant"
+def package_qa_check_rrecommends_non_existant(pkg, d, messages):
+localdata = bb.data.createCopy(d)
+localdata.setVar('OVERRIDES', pkg)
+for rec in bb.utils.explode_dep_versions2(localdata.getVar("RRECOMMENDS") 
or ""):
+if rec in (d.getVar("PACKAGES") or "").split() and not 
os.listdir(os.path.join(d.getVar("PKGDEST"), rec)):
+localdata.setVar("OVERRIDES", rec)
+if not bb.utils.to_boolean(localdata.getVar("ALLOW_EMPTY"), False):
+oe.qa.add_message(messages, "rrecommends-non-existant", "{0} 
-> {1} but won't be build".format(pkg, rec))
+
 def package_qa_check_encoding(keys, encode, d):
 def check_encoding(key, enc):
 sane = True
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177641): 
https://lists.openembedded.org/g/openembedded-core/message/177641
Mute This Topic: https://lists.openembedded.org/mt/97195661/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 PATCH 0/2] Handling of ${PN}-dev RRECOMMENDS non-existent ${PN}

[Yoann Congal]

This series is a work in progress on 2 related bugs :
* [YOCTO #6839] Handle dev package with no main package more gracefully
* [YOCTO #8222] Elide dependency from -dev package on main package if
  there are no shared libraries in it

An empty package ${PN} is not generated by default. This has been a
problem most frequently seen because ${PN}-dev depends on it. This case
has been handled by :
* Using ALLOW_EMPTY:${PN} = "1" : forcing ${PN} to be created even
  empty.
* DEV_PKG_DEPENDENCY = "" : Implicitly removing the dependency on ${PN}
* And finally and globally making the ${PN}-dev -> ${PN} relation a
  RRECOMMENDS.

2 patches :
* insane: Add QA check for RRECOMMENDS on non-existent packages
* meta/recipes: Remove empty ${PN}/DEV_PKG_DEPENDENCY workaround

First one create a QA check to try to detect the problematic situation.
The second removes workarounds setup to hide to problematic case.

Together they will prominently show where the problematic cases are.
Next step will be to find a generic way to fix the case.

Fawzi KHABER (2):
  insane: Add QA check for RRECOMMENDS on non-existent packages
  meta/recipes: Remove empty ${PN}/DEV_PKG_DEPENDENCY workarounds

 meta/classes-global/insane.bbclass| 11 +++
 meta/recipes-connectivity/bind/bind_9.18.11.bb|  1 -
 meta/recipes-core/musl/bsd-headers.bb |  1 -
 meta/recipes-core/musl/libssp-nonshared.bb|  1 -
 meta/recipes-core/newlib/newlib_git.bb|  3 ---
 meta/recipes-devtools/gcc/libgcc-common.inc   |  4 
 meta/recipes-devtools/python/python3_3.11.2.bb|  1 -
 meta/recipes-graphics/mesa/libglu_9.0.2.bb|  3 ---
 meta/recipes-graphics/mesa/mesa.inc   |  3 ---
 .../recipes-graphics/xorg-lib/libpthread-stubs_0.4.bb |  1 -
 meta/recipes-graphics/xorg-lib/xtrans_1.4.0.bb|  1 -
 meta/recipes-graphics/xorg-proto/xcb-proto_1.15.2.bb  |  1 -
 meta/recipes-graphics/xorg-proto/xorgproto_2022.2.bb  |  3 +--
 meta/recipes-graphics/xorg-util/util-macros_1.20.0.bb |  3 +--
 .../linux-libc-headers/linux-libc-headers.inc |  1 -
 .../make-mod-scripts/make-mod-scripts_1.0.bb  |  1 -
 .../argp-standalone/argp-standalone_1.4.1.bb  |  1 -
 17 files changed, 13 insertions(+), 27 deletions(-)

-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177640): 
https://lists.openembedded.org/g/openembedded-core/message/177640
Mute This Topic: https://lists.openembedded.org/mt/97195657/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][PATCHv3] vte: update 0.70.2 -> 0.70.3

[Alexandre Belloni via lists.openembedded.org]

I'm sorry I didn't catch it earlier but this is also the cause of:

ERROR: core-image-sato-1.0-r0 do_rootfs: Multilib check error: duplicate files 
/home/pokybuild/yocto-worker/multilib/build/build/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0-r0/multilib/lib32/usr/share/glib-2.0/schemas/gschemas.compiled
 
/home/pokybuild/yocto-worker/multilib/build/build/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0-r0/rootfs/usr/share/glib-2.0/schemas/gschemas.compiled
 is not the same

https://autobuilder.yoctoproject.org/typhoon/#/builders/44/builds/6745/steps/20/logs/stdio

On 23/02/2023 08:52:56+0100, Markus Volk wrote:
> - Allow to build the gtk4 widget and vapi
>   This is needed to build gtk4 based terminals like blackbox
> - Update dependencies
> - Cleanup recipe
> 
> Signed-off-by: Markus Volk 
> ---
>  .../vte/{vte_0.70.2.bb => vte_0.70.3.bb}  | 22 +--
>  1 file changed, 11 insertions(+), 11 deletions(-)
>  rename meta/recipes-support/vte/{vte_0.70.2.bb => vte_0.70.3.bb} (71%)
> 
> diff --git a/meta/recipes-support/vte/vte_0.70.2.bb 
> b/meta/recipes-support/vte/vte_0.70.3.bb
> similarity index 71%
> rename from meta/recipes-support/vte/vte_0.70.2.bb
> rename to meta/recipes-support/vte/vte_0.70.3.bb
> index ec2fb1f522..474ed87a88 100644
> --- a/meta/recipes-support/vte/vte_0.70.2.bb
> +++ b/meta/recipes-support/vte/vte_0.70.3.bb
> @@ -11,34 +11,34 @@ LIC_FILES_CHKSUM = " \
>  file://COPYING.XTERM;md5=d7fc3a23c16c039afafe2e042030f057 \
>  "
>  
> -DEPENDS = "glib-2.0 gtk+3 libpcre2 libxml2-native gperf-native icu"
> +DEPENDS = "fribidi glib-2.0 gtk+3 libpcre2 libxml2-native gperf-native icu 
> pango zlib"
>  
>  GNOMEBASEBUILDCLASS = "meson"
>  GIR_MESON_OPTION = 'gir'
>  GIDOCGEN_MESON_OPTION = "docs"
>  
> -inherit gnomebase gi-docgen features_check upstream-version-is-even 
> gobject-introspection
> +inherit gnomebase gi-docgen features_check upstream-version-is-even 
> gobject-introspection vala
>  
> -# vapigen.m4 is required when vala is not present (but the one from vala 
> should be used normally)
>  SRC_URI += "file://0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch"
> -SRC_URI[archive.sha256sum] = 
> "4d15b4380de3f564d57eabd006389c407c705df5b0c70030fdcc24971a334d80"
> +SRC_URI[archive.sha256sum] = 
> "9457134a02f3157fca04f7e0d39bdb0f3099be0a3ce82b7139d0c98a80748f23"
>  
>  ANY_OF_DISTRO_FEATURES = "${GTK3DISTROFEATURES}"
>  
> -# Help g-ir-scanner find the .so for linking
> -do_compile:prepend() {
> -export GIR_EXTRA_LIBS_PATH="${B}/src/.libs"
> -}
> -
>  # Package additional files
>  FILES:${PN}-dev += "${datadir}/vala/vapi/*"
>  
> -PACKAGECONFIG ??= "gnutls"
> -PACKAGECONFIG[vala] = "-Dvapi=true,-Dvapi=false,vala-native vala"
> +PACKAGECONFIG ??= " \
> +gnutls \
> +${@bb.utils.contains('DISTRO_FEATURES', 'gobject-introspection-data', 
> 'vala', '', d)} \
> +${@bb.utils.contains('DISTRO_FEATURES', 'opengl', 'gtk4', '', d)} \
> +"
> +PACKAGECONFIG[gtk4] = "-Dgtk4=true,-Dgtk4=false,gtk4"
> +PACKAGECONFIG[vala] = "-Dvapi=true,-Dvapi=false"
>  PACKAGECONFIG[gnutls] = "-Dgnutls=true,-Dgnutls=false,gnutls"
>  PACKAGECONFIG[systemd] = "-D_systemd=true,-D_systemd=false,systemd"
>  # vala requires gir
>  PACKAGECONFIG:remove:class-native = "vala"
> +PACKAGECONFIG:remove:class-nativesdk = "vala gtk4"
>  
>  CFLAGS += "-D_GNU_SOURCE"
>  
> -- 
> 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 (#177639): 
https://lists.openembedded.org/g/openembedded-core/message/177639
Mute This Topic: https://lists.openembedded.org/mt/97178843/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] [DISTRO|MACHINE]_FEATURES_BACKFILL_CONSIDERED: confusing variable names?

[Tom Hochstein]

I agree. The problem I have with these variable names is that it's ambiguous 
whether the features will be included or excluded from the backfill. All you 
can tell from the names is that the values were 'considered'. What does that 
mean? You have to go to the manual to find the full meaning.

What's important about the variables is that they will be 'excluded' from the 
backfill, so this does look much clearer to me:

DISTRO_FEATURES_BACKFILL_EXCLUDED += "some-feature"

Is there a good reason why we have this separate variable and can't just do 
this?

DISTRO_FEATURES_BACKFILL:remove = "some-feature"

Tom

-Original Message-
From: openembedded-core@lists.openembedded.org 
 On Behalf Of Michael Opdenacker via 
lists.openembedded.org
Sent: Thursday, February 23, 2023 11:00 AM
To: OE-core 
Cc: YP docs mailing list 
Subject: [OE-core] [DISTRO|MACHINE]_FEATURES_BACKFILL_CONSIDERED: confusing 
variable names?

Greetings

Anybody else finding the DISTRO_FEATURES_BACKFILL_CONSIDERED and 
MACHINE_FEATURES_BACKFILL_CONSIDERED variable names confusing?

According to the documentation about "feature backfilling" 
(https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.yoctoproject.org%2Fref-manual%2Ffeatures.html%23ref-features-backfill=05%7C01%7Ctom.hochstein%40nxp.com%7Cf4e5b1f4523a469612dc08db15bf5d8e%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C638127683879148065%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=4i2IX0GpQlQXAh8Jausfvb2o1oF6MBZaU144KHKjcKg%3D=0),
 
these variables allow to exclude some features from being backfilled.

I'm not a native English speaker, but for me, "considered" carries the 
intention to include a feature, not to exclude one.

Shouldn't we call these variables DISTRO_FEATURES_BACKFILL_EXCLUDED and 
MACHINE_FEATURES_BACKFILL_EXCLUDED instead ?

Thanks in advance
Cheers
Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbootlin.com%2F=05%7C01%7Ctom.hochstein%40nxp.com%7Cf4e5b1f4523a469612dc08db15bf5d8e%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C638127683879148065%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=S4rZtW35Uxk1ww8OkrPlCJdlI2FWgIpxHcq7PDq2M1o%3D=0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177638): 
https://lists.openembedded.org/g/openembedded-core/message/177638
Mute This Topic: https://lists.openembedded.org/mt/97187180/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 v12] Rust Oe-Selftest implementation

[Richard Purdie]

On Thu, 2023-02-23 at 21:04 +, Richard Purdie via
lists.openembedded.org wrote:
> On Thu, 2023-02-23 at 13:55 -0500, Randy MacLeod wrote:
> > Thanks Naveen,
> > 
> > With a large patch like this it would be good if you could provide a
> >  cover letter that summarized what is different in v12, compared to
> > v11.
> > 
> > I've looked at the diff and my summary is below. There are some
> > changes
> >  which I see but would benefit from an explanation.
> > 
> > Finally, please change your SOB line to @windriver.com. 
> > 
> 
> Changelogs definitely help, thanks Randy!
> 
> Thanks for putting this patch together Naveen, we are getting there. I
> ran this through the autobuilder and the good news is we only saw one
> failure related to the patch, in oe-selftest on an ARM host:
> 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/1004
> (from
> https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/4962
> )
> 
> We could disable the rust tests on arm host systems to get this to
> merge however ideally it would be fixed to run there properly as well.
> I'm not even sure this should actually be running there at all now I
> look at things. The other toolchain/machine specific tests are tagged
> as "machine", e.g. meta_ide.py has:
> 
> @OETestTag("machine")
> class MetaIDE(OESelftestTestCase):
> 
> or they're marked as @OETestTag("toolchain-user") or
> @OETestTag("toolchain-system") in the case of the glibc/gcc tests. The
> difference is how the tests are run so "toolchain-system" would be most
> appropriate for rust. This means that the tests are run per MACHINE
> target instead of once overall.
> 
> The second issue I noticed is that the test results are not appearing
> in the test report. For the build above, this is here:
> 
> https://autobuilder.yocto.io/pub/non-release/20230223-9/testresults/testresult-report.txt
> 
> 
> and I can't see the rust tests at all. This will need to be fixed
> before the patches can merge. It may be changing to be
> machine/toolchain might fix that, I don't remember the details.

I found some time to check into this a little further. We definitely
need to mark the test as a toolchain-system test so it is run in the
right places.

Aside from that, there is also no individual test result reporting in
place for it, either the test suite passes or it does not.

With the gcc tests, you'll see there is the self.ptest_result() call
which logs the individual test pass/fail/skip value. We'll need to do
something similar with rust so we don't just have one overall
pass/fail.

Cheers,

Richard




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

[oe-core][PATCHv5] vte: update 0.70.2 -> 0.70.3

[Markus Volk]

- Allow to build the gtk4 widget and vapi
  This is needed to build gtk4 based terminals like blackbox
- Update dependencies
- Cleanup recipe

Signed-off-by: Markus Volk 
---
 .../vte/{vte_0.70.2.bb => vte_0.70.3.bb}  | 24 +--
 1 file changed, 11 insertions(+), 13 deletions(-)
 rename meta/recipes-support/vte/{vte_0.70.2.bb => vte_0.70.3.bb} (70%)

diff --git a/meta/recipes-support/vte/vte_0.70.2.bb 
b/meta/recipes-support/vte/vte_0.70.3.bb
similarity index 70%
rename from meta/recipes-support/vte/vte_0.70.2.bb
rename to meta/recipes-support/vte/vte_0.70.3.bb
index ec2fb1f522..a194b4067f 100644
--- a/meta/recipes-support/vte/vte_0.70.2.bb
+++ b/meta/recipes-support/vte/vte_0.70.3.bb
@@ -11,34 +11,32 @@ LIC_FILES_CHKSUM = " \
 file://COPYING.XTERM;md5=d7fc3a23c16c039afafe2e042030f057 \
 "
 
-DEPENDS = "glib-2.0 gtk+3 libpcre2 libxml2-native gperf-native icu"
+DEPENDS = "fribidi glib-2.0 gtk+3 libpcre2 libxml2-native gperf-native icu 
pango zlib"
 
 GNOMEBASEBUILDCLASS = "meson"
 GIR_MESON_OPTION = 'gir'
 GIDOCGEN_MESON_OPTION = "docs"
 
-inherit gnomebase gi-docgen features_check upstream-version-is-even 
gobject-introspection
+inherit gnomebase gi-docgen features_check upstream-version-is-even 
gobject-introspection vala
 
-# vapigen.m4 is required when vala is not present (but the one from vala 
should be used normally)
 SRC_URI += "file://0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch"
-SRC_URI[archive.sha256sum] = 
"4d15b4380de3f564d57eabd006389c407c705df5b0c70030fdcc24971a334d80"
+SRC_URI[archive.sha256sum] = 
"9457134a02f3157fca04f7e0d39bdb0f3099be0a3ce82b7139d0c98a80748f23"
 
 ANY_OF_DISTRO_FEATURES = "${GTK3DISTROFEATURES}"
 
-# Help g-ir-scanner find the .so for linking
-do_compile:prepend() {
-export GIR_EXTRA_LIBS_PATH="${B}/src/.libs"
-}
-
 # Package additional files
 FILES:${PN}-dev += "${datadir}/vala/vapi/*"
 
-PACKAGECONFIG ??= "gnutls"
-PACKAGECONFIG[vala] = "-Dvapi=true,-Dvapi=false,vala-native vala"
+PACKAGECONFIG:class-target ??= " \
+gnutls \
+${@bb.utils.contains('GI_DATA_ENABLED', 'True', 'gir vala', '', d)} \
+${@bb.utils.contains('DISTRO_FEATURES', 'opengl', 'gtk4', '', d)} \
+"
+PACKAGECONFIG[gtk4] = "-Dgtk4=true,-Dgtk4=false,gtk4"
+PACKAGECONFIG[gir] = "-Dgir=true,-Dgir=false"
+PACKAGECONFIG[vala] = "-Dvapi=true,-Dvapi=false"
 PACKAGECONFIG[gnutls] = "-Dgnutls=true,-Dgnutls=false,gnutls"
 PACKAGECONFIG[systemd] = "-D_systemd=true,-D_systemd=false,systemd"
-# vala requires gir
-PACKAGECONFIG:remove:class-native = "vala"
 
 CFLAGS += "-D_GNU_SOURCE"
 
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177636): 
https://lists.openembedded.org/g/openembedded-core/message/177636
Mute This Topic: https://lists.openembedded.org/mt/97194854/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 v3] gdb: Upgrade to 13.1

[Richard Purdie]

On Wed, 2023-02-22 at 22:34 -0800, Khem Raj wrote:
> On Wed, Feb 22, 2023 at 5:35 PM Khem Raj  wrote:
> > 
> > On Wed, Feb 22, 2023 at 3:43 PM Alexandre Belloni
> >  wrote:
> > > 
> > > Hello,
> > > 
> > > This failed on musl:
> > > 
> > > > checking minix/config.h usability... 
> > > > ../../gdb-13.1/gdbserver/linux-low.cc: In function 'int 
> > > > proc_xfer_memory(CORE_ADDR, unsigned char*, const gdb_byte*, int)':
> > > > ../../gdb-13.1/gdbserver/linux-low.cc:5393:45: error: expected ':' 
> > > > before ')' token
> > > >  5393 |  ? write (fd, writebuf, len));
> > > >   | ^
> > > >   | :
> > > > ../../gdb-13.1/gdbserver/linux-low.cc:5393:45: error: expected 
> > > > primary-expression before ')' token
> > > > ../../gdb-13.1/gdbserver/linux-low.cc:5393:45: error: expected ':' 
> > > > before ')' token
> > > >  5393 |  ? write (fd, writebuf, len));
> > > >   | ^
> > > >   | :
> > > > ../../gdb-13.1/gdbserver/linux-low.cc:5393:45: error: expected 
> > > > primary-expression before ')' token
> > > 
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/6703/steps/11/logs/stdio
> > > 
> > > Note that reproducible still failed:
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/2438/steps/13/logs/stdio
> > > 
> > 
> > I looked into the configure logs on builder as I was not able to
> > reproduce here locally. Here is what I see in gdb/config.log, I think
> > this node is using buildtools stuff and seems
> > its getting libpthread.so.0 from host which needs certain symbols from
> > libc which I guess are missing because its linking libc from
> > buildtools tarball as well.
> > 
> > configure:28568: checking for ELF support in BFD
> > configure:28588: ./libtool --quiet --mode=link gcc  -o conftest
> > -I../../gdb-13.1/gdb/../include -I../bfd -I../../gdb-13.1/gdb/../bfd
> > -isystem/home/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB/tmp/work/x86_64-linux/gdb-cross-x86_64/13.1-r0/recipe-sysroot-native/usr/include
> > -O2 -pipe 
> > -isystem/home/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB/tmp/work/x86_64-linux/gdb-cross-x86_64/13.1-r0/recipe-sysroot-native/usr/include
> > -I/home/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB/tmp/work/x86_64-linux/gdb-cross-x86_64/13.1-r0/recipe-sysroot-native/usr/include
> > -L../bfd -L../libiberty conftest.c -lbfd -liberty  -lncursesw -lm  >&5
> > /home/pokybuild/yocto-worker/reproducible/build/buildtools/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/12.2.0/../../../../x86_64-pokysdk-linux/bin/ld:
> > /lib64/libpthread.so.0: undefined reference to
> > `__pause_nocancel@GLIBC_PRIVATE'
> > /home/pokybuild/yocto-worker/reproducible/build/buildtools/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/12.2.0/../../../../x86_64-pokysdk-linux/bin/ld:
> > /lib64/libpthread.so.0: undefined reference to
> > `__libc_dlclose@GLIBC_PRIVATE'
> > /home/pokybuild/yocto-worker/reproducible/build/buildtools/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/12.2.0/../../../../x86_64-pokysdk-linux/bin/ld:
> > /lib64/libpthread.so.0: undefined reference to
> > `__libc_allocate_rtsig_private@GLIBC_PRIVATE'
> > /home/pokybuild/yocto-worker/reproducible/build/buildtools/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/12.2.0/../../../../x86_64-pokysdk-linux/bin/ld:
> > /lib64/libpthread.so.0: undefined reference to
> > `__nanosleep_nocancel@GLIBC_PRIVATE'
> > /home/pokybuild/yocto-worker/reproducible/build/buildtools/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/12.2.0/../../../../x86_64-pokysdk-linux/bin/ld:
> > /lib64/libpthread.so.0: undefined reference to
> > `__libc_dlsym@GLIBC_PRIVATE'
> > /home/pokybuild/yocto-worker/reproducible/build/buildtools/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/12.2.0/../../../../x86_64-pokysdk-linux/bin/ld:
> > /lib64/libpthread.so.0: undefined reference to
> > `__libc_siglongjmp@GLIBC_PRIVATE'
> > /home/pokybuild/yocto-worker/reproducible/build/buildtools/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/12.2.0/../../../../x86_64-pokysdk-linux/bin/ld:
> > /lib64/libpthread.so.0: undefined reference to
> > `__libc_thread_freeres@GLIBC_PRIVATE'
> > /home/pokybuild/yocto-worker/reproducible/build/buildtools/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/12.2.0/../../../../x86_64-pokysdk-linux/bin/ld:
> > /lib64/libpthread.so.0: undefined reference to
> > `__libc_current_sigrtmax_private@GLIBC_PRIVATE'
> > /home/pokybuild/yocto-worker/reproducible/build/buildtools/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/12.2.0/../../../../x86_64-pokysdk-linux/bin/ld:
> > /lib64/libpthread.so.0: undefined reference to
> > 

Re: [oe-core][PATCHv4] vte: update 0.70.2 -> 0.70.3

[Markus Volk]

Am Do, 23. Feb 2023 um 21:27:25 + schrieb Richard Purdie 
:

Not necessarily. The question is whether we need gtk4 support in our
SDK? I've prefer not to build/include things we don't need and I'm not
sure where gtk4 is being used there as yet?


Also, I was wrong. Things are not that simple. gtk4 requires 
graphene-gobject and that is disabled by default for nativesdk. I 
really don't know why this didn't show up yesterday when I tested the 
build for nativesdk.


Using GI_DATA_ENABLED helped partially, but 'vala' still needs to be 
removed for nativesdk. Otherwise this looks pretty good now, builds for 
musl,x32,nativesdk. Fingers crossed that it passes the test now.



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177634): 
https://lists.openembedded.org/g/openembedded-core/message/177634
Mute This Topic: https://lists.openembedded.org/mt/97190638/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 1/1] nghttp2: never build python bindings

[Joe Slater]

This has already been done for oe-core/master.

Signed-off-by: Joe Slater 
---
 meta/recipes-support/nghttp2/nghttp2_1.47.0.bb | 4 
 1 file changed, 4 insertions(+)

diff --git a/meta/recipes-support/nghttp2/nghttp2_1.47.0.bb 
b/meta/recipes-support/nghttp2/nghttp2_1.47.0.bb
index 58ce08084d..becacd4502 100644
--- a/meta/recipes-support/nghttp2/nghttp2_1.47.0.bb
+++ b/meta/recipes-support/nghttp2/nghttp2_1.47.0.bb
@@ -19,6 +19,10 @@ PACKAGECONFIG[manpages] = ""
 # first place
 EXTRA_OECMAKE = "-DENABLE_EXAMPLES=OFF -DENABLE_APP=OFF 
-DENABLE_HPACK_TOOLS=OFF"
 
+# Do not let configure try to decide this.
+#
+EXTRA_OECMAKE += "-DENABLE_PYTHON_BINDINGS=OFF"
+
 PACKAGES =+ "lib${BPN} ${PN}-client ${PN}-proxy ${PN}-server"
 
 RDEPENDS:${PN} = "${PN}-client (>= ${PV}) ${PN}-proxy (>= ${PV}) ${PN}-server 
(>= ${PV})"
-- 
2.32.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177633): 
https://lists.openembedded.org/g/openembedded-core/message/177633
Mute This Topic: https://lists.openembedded.org/mt/97193381/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][PATCHv4] vte: update 0.70.2 -> 0.70.3

[Richard Purdie]

On Thu, 2023-02-23 at 21:10 +0100, Alexander Kanavin wrote:
> On Thu, 23 Feb 2023 at 21:04, Markus Volk  wrote:
> > 
> > Am Do, 23. Feb 2023 um 20:46:03 +0100 schrieb Alexander Kanavin 
> > :
> > 
> > Why does gtk4 need to be removed as well in this case?
> > 
> > 
> > Because gtk4 is not allowed to build for nativesdk yet, only for
> > native. I've tested that it'll work, if 'nativesdk' is added to
> > BBCLASSEXTEND for gtk4, xkeyboard-config and libxkbcommon
> 
> Then that would be the correct fix.

Not necessarily. The question is whether we need gtk4 support in our
SDK? I've prefer not to build/include things we don't need and I'm not
sure where gtk4 is being used there as yet?

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177632): 
https://lists.openembedded.org/g/openembedded-core/message/177632
Mute This Topic: https://lists.openembedded.org/mt/97190638/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] grub: Handle R_RISCV_CALL_PLT reloc

[Khem Raj]

These are new in binutils 2.40+

Signed-off-by: Khem Raj 
---
 ...risc-v-Handle-R_RISCV_CALL_PLT-reloc.patch | 48 +++
 meta/recipes-bsp/grub/grub2.inc   |  1 +
 2 files changed, 49 insertions(+)
 create mode 100644 
meta/recipes-bsp/grub/files/0001-risc-v-Handle-R_RISCV_CALL_PLT-reloc.patch

diff --git 
a/meta/recipes-bsp/grub/files/0001-risc-v-Handle-R_RISCV_CALL_PLT-reloc.patch 
b/meta/recipes-bsp/grub/files/0001-risc-v-Handle-R_RISCV_CALL_PLT-reloc.patch
new file mode 100644
index 00..f3f12b6f0e
--- /dev/null
+++ 
b/meta/recipes-bsp/grub/files/0001-risc-v-Handle-R_RISCV_CALL_PLT-reloc.patch
@@ -0,0 +1,48 @@
+From 64be669638e198bc0c7c1a344547265dfacd2470 Mon Sep 17 00:00:00 2001
+From: Khem Raj 
+Date: Mon, 23 Jan 2023 15:29:02 -0800
+Subject: [PATCH] risc-v: Handle R_RISCV_CALL_PLT reloc
+
+GNU assembler starting 2.40 release always generates R_RISCV_CALL_PLT
+reloc for call in assembler [1], similarly llvm does not make
+distinction between R_RISCV_CALL_PLT and R_RISCV_CALL [2]
+
+Upstream-Status: Submitted 
[https://lists.gnu.org/archive/html/grub-devel/2023-02/msg00143.html]
+
+[1] 
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=70f35d72ef04cd23771875c1661c9975044a749c
+[2] https://reviews.llvm.org/D132530
+
+Upstream-Status: Pending
+Signed-off-by: Khem Raj 
+---
+ grub-core/kern/riscv/dl.c | 1 +
+ 1 file changed, 1 insertion(+)
+
+--- a/grub-core/kern/riscv/dl.c
 b/grub-core/kern/riscv/dl.c
+@@ -188,6 +188,7 @@ grub_arch_dl_relocate_symbols (grub_dl_t
+ break;
+ 
+   case R_RISCV_CALL:
++  case R_RISCV_CALL_PLT:
+ {
+   grub_uint32_t *abs_place = place;
+   grub_ssize_t off = sym_addr - (grub_addr_t) place;
+--- a/util/grub-mkimagexx.c
 b/util/grub-mkimagexx.c
+@@ -1294,6 +1294,7 @@ SUFFIX (relocate_addrs) (Elf_Ehdr *e, st
+}
+break;
+  case R_RISCV_CALL:
++ case R_RISCV_CALL_PLT:
+{
+  grub_uint32_t hi20, lo12;
+ 
+@@ -1725,6 +1726,7 @@ translate_relocation_pe (struct translat
+   case R_RISCV_BRANCH:
+   case R_RISCV_JAL:
+   case R_RISCV_CALL:
++  case R_RISCV_CALL_PLT:
+   case R_RISCV_PCREL_HI20:
+   case R_RISCV_PCREL_LO12_I:
+   case R_RISCV_PCREL_LO12_S:
diff --git a/meta/recipes-bsp/grub/grub2.inc b/meta/recipes-bsp/grub/grub2.inc
index bf7aba6b1c..b92cbc2654 100644
--- a/meta/recipes-bsp/grub/grub2.inc
+++ b/meta/recipes-bsp/grub/grub2.inc
@@ -40,6 +40,7 @@ SRC_URI = "${GNU_MIRROR}/grub/grub-${PV}.tar.gz \

file://0001-font-Fix-size-overflow-in-grub_font_get_glyph_intern.patch \
file://CVE-2022-2601.patch \
file://CVE-2022-3775.patch \
+   file://0001-risc-v-Handle-R_RISCV_CALL_PLT-reloc.patch \
 "
 
 SRC_URI[sha256sum] = 
"23b64b4c741569f9426ed2e3d0e6780796fca081bee4c99f62aa3f53ae803f5f"
-- 
2.39.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177631): 
https://lists.openembedded.org/g/openembedded-core/message/177631
Mute This Topic: https://lists.openembedded.org/mt/97193187/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 v12] Rust Oe-Selftest implementation

[Richard Purdie]

On Thu, 2023-02-23 at 13:55 -0500, Randy MacLeod wrote:
> Thanks Naveen,
> 
> With a large patch like this it would be good if you could provide a
>  cover letter that summarized what is different in v12, compared to
> v11.
> 
> I've looked at the diff and my summary is below. There are some
> changes
>  which I see but would benefit from an explanation.
> 
> Finally, please change your SOB line to @windriver.com. 
> 

Changelogs definitely help, thanks Randy!

Thanks for putting this patch together Naveen, we are getting there. I
ran this through the autobuilder and the good news is we only saw one
failure related to the patch, in oe-selftest on an ARM host:

https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/1004
(from
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/4962
)

We could disable the rust tests on arm host systems to get this to
merge however ideally it would be fixed to run there properly as well.
I'm not even sure this should actually be running there at all now I
look at things. The other toolchain/machine specific tests are tagged
as "machine", e.g. meta_ide.py has:

@OETestTag("machine")
class MetaIDE(OESelftestTestCase):

or they're marked as @OETestTag("toolchain-user") or
@OETestTag("toolchain-system") in the case of the glibc/gcc tests. The
difference is how the tests are run so "toolchain-system" would be most
appropriate for rust. This means that the tests are run per MACHINE
target instead of once overall.

The second issue I noticed is that the test results are not appearing
in the test report. For the build above, this is here:

https://autobuilder.yocto.io/pub/non-release/20230223-9/testresults/testresult-report.txt


and I can't see the rust tests at all. This will need to be fixed
before the patches can merge. It may be changing to be
machine/toolchain might fix that, I don't remember the details.

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177630): 
https://lists.openembedded.org/g/openembedded-core/message/177630
Mute This Topic: https://lists.openembedded.org/mt/97178295/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] dtc: update DESCRIPTION

[Trevor Woerner]

Update the description to align with the current goals of the dtc project.

Signed-off-by: Trevor Woerner 
---
 meta/recipes-kernel/dtc/dtc_1.7.0.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-kernel/dtc/dtc_1.7.0.bb 
b/meta/recipes-kernel/dtc/dtc_1.7.0.bb
index 7d064ed127c1..4ab8451c60fe 100644
--- a/meta/recipes-kernel/dtc/dtc_1.7.0.bb
+++ b/meta/recipes-kernel/dtc/dtc_1.7.0.bb
@@ -1,6 +1,6 @@
 SUMMARY = "Device Tree Compiler"
 HOMEPAGE = "https://devicetree.org/;
-DESCRIPTION = "The Device Tree Compiler is a tool used to manipulate the 
Open-Firmware-like device tree used by PowerPC kernels."
+DESCRIPTION = "The Device Tree Compiler is a toolchain for working with device 
tree source and binary files."
 SECTION = "bootloader"
 LICENSE = "GPL-2.0-only | BSD-2-Clause"
 
-- 
2.36.0.rc2.17.g4027e30c53


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177629): 
https://lists.openembedded.org/g/openembedded-core/message/177629
Mute This Topic: https://lists.openembedded.org/mt/97192096/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] dtc: update license checks

[Trevor Woerner]

The dtc project is dual licensed, and includes the text of both licenses as
part of its sources as well as a README documenting its license situation.
Use these sources to verify the licensing, and to monitor if it changes,
rather than a copyright line in a source file.

Signed-off-by: Trevor Woerner 
---
 meta/recipes-kernel/dtc/dtc_1.7.0.bb | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-kernel/dtc/dtc_1.7.0.bb 
b/meta/recipes-kernel/dtc/dtc_1.7.0.bb
index 0fc3eca00218..7d064ed127c1 100644
--- a/meta/recipes-kernel/dtc/dtc_1.7.0.bb
+++ b/meta/recipes-kernel/dtc/dtc_1.7.0.bb
@@ -5,7 +5,8 @@ SECTION = "bootloader"
 LICENSE = "GPL-2.0-only | BSD-2-Clause"
 
 LIC_FILES_CHKSUM = "file://GPL;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
-
file://libfdt/libfdt.h;beginline=4;endline=7;md5=05bb357cfb75cae7d2b01d2ee8d76407"
+file://BSD-2-Clause;md5=5d6306d1b08f8df623178dfd81880927 \
+file://README.license;md5=a1eb22e37f09df5b5511b8a278992d0e"
 
 SRC_URI = "git://git.kernel.org/pub/scm/utils/dtc/dtc.git;branch=main" 
 SRCREV = "039a99414e778332d8f9c04cbd3072e1dcc62798"
-- 
2.36.0.rc2.17.g4027e30c53


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177628): 
https://lists.openembedded.org/g/openembedded-core/message/177628
Mute This Topic: https://lists.openembedded.org/mt/97192095/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][PATCHv4] vte: update 0.70.2 -> 0.70.3

[Alexander Kanavin]

On Thu, 23 Feb 2023 at 21:04, Markus Volk  wrote:
>
> Am Do, 23. Feb 2023 um 20:46:03 +0100 schrieb Alexander Kanavin 
> :
>
> Why does gtk4 need to be removed as well in this case?
>
>
> Because gtk4 is not allowed to build for nativesdk yet, only for native. I've 
> tested that it'll work, if 'nativesdk' is added to BBCLASSEXTEND for gtk4, 
> xkeyboard-config and libxkbcommon

Then that would be the correct fix.

Alex

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177627): 
https://lists.openembedded.org/g/openembedded-core/message/177627
Mute This Topic: https://lists.openembedded.org/mt/97190638/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][PATCHv4] vte: update 0.70.2 -> 0.70.3

[Markus Volk]

Am Do, 23. Feb 2023 um 20:46:03 +0100 schrieb Alexander Kanavin 
:

Why does gtk4 need to be removed as well in this case?


Because gtk4 is not allowed to build for nativesdk yet, only for 
native. I've tested that it'll work, if 'nativesdk' is added to 
BBCLASSEXTEND for gtk4, xkeyboard-config and libxkbcommon



you need to use GI_DATA_ENABLED variable instead here.


Aah, thanks


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177626): 
https://lists.openembedded.org/g/openembedded-core/message/177626
Mute This Topic: https://lists.openembedded.org/mt/97190638/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][PATCHv4] vte: update 0.70.2 -> 0.70.3

[Alexander Kanavin]

On Thu, 23 Feb 2023 at 20:19, Markus Volk  wrote:
> +${@bb.utils.contains('DISTRO_FEATURES', 'gobject-introspection-data', 
> 'vala', '', d)} \

You need to use GI_DATA_ENABLED variable instead here. Then the
:remove statements with vala in them below will not be needed.

Yes, I messed this up myself in the gcr recipe a few days ago, that
needs to be fixed too.

> +PACKAGECONFIG:remove:class-nativesdk = "vala gtk4"

Why does gtk4 need to be removed as well in this case?

Alex

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177625): 
https://lists.openembedded.org/g/openembedded-core/message/177625
Mute This Topic: https://lists.openembedded.org/mt/97190638/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] tune-riscv.inc: Add riscv64nc to available tunes list

[Khem Raj]

This was missed when riscv64nc was added

Signed-off-by: Khem Raj 
---
 meta/conf/machine/include/riscv/tune-riscv.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/conf/machine/include/riscv/tune-riscv.inc 
b/meta/conf/machine/include/riscv/tune-riscv.inc
index 659801496c..804712077e 100644
--- a/meta/conf/machine/include/riscv/tune-riscv.inc
+++ b/meta/conf/machine/include/riscv/tune-riscv.inc
@@ -10,7 +10,7 @@ TUNEVALID[riscv64nc] = "Enable 64-bit RISC-V optimizations 
without compressed in
 
 TUNEVALID[bigendian] = "Big endian mode"
 
-AVAILTUNES += "riscv64 riscv32 riscv64nf riscv32nf"
+AVAILTUNES += "riscv64 riscv32 riscv64nc riscv64nf riscv32nf"
 
 # Default
 TUNE_FEATURES:tune-riscv64 = "riscv64"
-- 
2.39.2


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

[oe-core][PATCHv4] vte: update 0.70.2 -> 0.70.3

[Markus Volk]

- Allow to build the gtk4 widget and vapi
  This is needed to build gtk4 based terminals like blackbox
- Update dependencies
- Cleanup recipe

Signed-off-by: Markus Volk 
---
 .../vte/{vte_0.70.2.bb => vte_0.70.3.bb}  | 25 +++
 1 file changed, 14 insertions(+), 11 deletions(-)
 rename meta/recipes-support/vte/{vte_0.70.2.bb => vte_0.70.3.bb} (69%)

diff --git a/meta/recipes-support/vte/vte_0.70.2.bb 
b/meta/recipes-support/vte/vte_0.70.3.bb
similarity index 69%
rename from meta/recipes-support/vte/vte_0.70.2.bb
rename to meta/recipes-support/vte/vte_0.70.3.bb
index ec2fb1f522..0c782b8c2f 100644
--- a/meta/recipes-support/vte/vte_0.70.2.bb
+++ b/meta/recipes-support/vte/vte_0.70.3.bb
@@ -11,34 +11,37 @@ LIC_FILES_CHKSUM = " \
 file://COPYING.XTERM;md5=d7fc3a23c16c039afafe2e042030f057 \
 "
 
-DEPENDS = "glib-2.0 gtk+3 libpcre2 libxml2-native gperf-native icu"
+DEPENDS = "fribidi glib-2.0 gtk+3 libpcre2 libxml2-native gperf-native icu 
pango zlib"
 
 GNOMEBASEBUILDCLASS = "meson"
 GIR_MESON_OPTION = 'gir'
 GIDOCGEN_MESON_OPTION = "docs"
 
-inherit gnomebase gi-docgen features_check upstream-version-is-even 
gobject-introspection
+inherit gnomebase gi-docgen features_check upstream-version-is-even 
gobject-introspection vala
 
-# vapigen.m4 is required when vala is not present (but the one from vala 
should be used normally)
 SRC_URI += "file://0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch"
-SRC_URI[archive.sha256sum] = 
"4d15b4380de3f564d57eabd006389c407c705df5b0c70030fdcc24971a334d80"
+SRC_URI[archive.sha256sum] = 
"9457134a02f3157fca04f7e0d39bdb0f3099be0a3ce82b7139d0c98a80748f23"
 
 ANY_OF_DISTRO_FEATURES = "${GTK3DISTROFEATURES}"
 
-# Help g-ir-scanner find the .so for linking
-do_compile:prepend() {
-export GIR_EXTRA_LIBS_PATH="${B}/src/.libs"
-}
-
 # Package additional files
 FILES:${PN}-dev += "${datadir}/vala/vapi/*"
 
-PACKAGECONFIG ??= "gnutls"
-PACKAGECONFIG[vala] = "-Dvapi=true,-Dvapi=false,vala-native vala"
+
+
+PACKAGECONFIG ??= " \
+gnutls \
+${@bb.utils.contains('DISTRO_FEATURES', 'gobject-introspection-data', 
'vala', '', d)} \
+${@bb.utils.contains('DISTRO_FEATURES', 'opengl', 'gtk4', '', d)} \
+"
+PACKAGECONFIG[gtk4] = "-Dgtk4=true,-Dgtk4=false,gtk4"
+PACKAGECONFIG[vala] = "-Dvapi=true,-Dvapi=false"
 PACKAGECONFIG[gnutls] = "-Dgnutls=true,-Dgnutls=false,gnutls"
 PACKAGECONFIG[systemd] = "-D_systemd=true,-D_systemd=false,systemd"
 # vala requires gir
+PACKAGECONFIG:remove:x86-x32 = "vala"
 PACKAGECONFIG:remove:class-native = "vala"
+PACKAGECONFIG:remove:class-nativesdk = "vala gtk4"
 
 CFLAGS += "-D_GNU_SOURCE"
 
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177623): 
https://lists.openembedded.org/g/openembedded-core/message/177623
Mute This Topic: https://lists.openembedded.org/mt/97190638/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][PATCHv3] vte: update 0.70.2 -> 0.70.3

[Markus Volk]

Am Do, 23. Feb 2023 um 17:47:20 +0100 schrieb Alexandre Belloni 
:

It failed on qemux86-64-x32:


Now that's unruly

I did a test build for qemux86-64-x32. For some reason gir gets 
disabled while vala still is requested to be built and thus configure 
fails. Not sure, why gir gets disabled here without disable vala as 
well. Maybe there is a global setting for this somewhere?


However, adding another PACKAGECONFIG:remove line for x86-x32 did solve 
the issue



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177622): 
https://lists.openembedded.org/g/openembedded-core/message/177622
Mute This Topic: https://lists.openembedded.org/mt/97178843/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 v12] Rust Oe-Selftest implementation

[Randy MacLeod]

Thanks Naveen,

With a large patch like this it would be good if you could provide a
cover letter that summarized what is different in v12, compared to v11.

I've looked at the diff and my summary is below. There are some changes
which I see but would benefit from an explanation.

Finally, please change your SOB line to @windriver.com.


Summary of what changed in v12:
=

Rebase Rust tests to 1.67.1.

Switch from ssh-server-openssh to ssh-server-dropbear.
--> Why?
I know you were having problems with scp not working for qemux86
but either server should work in theory.

Tell the Rust remote-test-server to bind to port 12345.
--> Why?


Also add: --exclude src/tools/rust-analyzer to testargs.
--> Why?
I don't object but ideally the commit log would explain this decision.

As far as the tests go, you've :

 -  added 3 more 'ignore-stage1' comments :
$ rg ignore-stage1 /tmp/rust-test-v11.eml | wc -l
41
$ rg ignore-stage1 /tmp/rust-test-v12.eml | wc -l
44


 - added 20 more #[ignore] directives:
$ rg "ignore]" /tmp/rust-test-v11.eml | wc -l
4
$ rg "ignore]" /tmp/rust-test-v12.eml  | wc -l
24

Those additional test skip directives doesn't change the overall pass 
rate significantly

since the test suite has ~ 18,000 tests so they're find with me .

I think that's about it. Did I miss anything?


Key, very abbreviated differences b/w v11, v12 are shown below .

../Randy


+Tested for X86, X86-64, ARM, ARM64 and MIPS64 on CentOS release 6.10
+
 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(-)
+ .../rust/files/rust-oe-selftest.patch | 736 ++
+ meta/recipes-devtools/rust/rust-source.inc    |   1 +
+ meta/recipes-devtools/rust/rust_1.67.1.bb |   6 +
+ 4 files changed, 797 insertions(+)
  create mode 100644 meta/lib/oeqa/selftest/cases/rust.py
- create mode 100644 meta/recipes-devtools/rust/rust/rust-oe-selftest.patch
+ create mode 100644 meta/recipes-devtools/rust/files/rust-oe-selftest.patch

 diff --git a/meta/lib/oeqa/selftest/cases/rust.py 
b/meta/lib/oeqa/selftest/cases/rust.py

 new file mode 100644
-index 00..e06ddaa6d7
+index 00..f9889b840c
 --- /dev/null
 +++ b/meta/lib/oeqa/selftest/cases/rust.py
 @@ -0,0 +1,54 @@
@@ -237,7 +239,7 @@
 +    # build core-image-minimal with required packages
 +    default_installed_packages = ["libgcc", "libstdc++", 
"libatomic", "libgomp"]

 +    features = []
-+    features.append('IMAGE_FEATURES += "ssh-server-openssh"')
++    features.append('IMAGE_FEATURES += "ssh-server-dropbear"')
 +    features.append('CORE_IMAGE_EXTRA_INSTALL += "{0}"'.format(" 
".join(default_installed_packages)))

 +    self.write_config("\n".join(features))
 +    bitbake("core-image-minimal")

@@ -248,7 +250,7 @@
 +    ssh = SSHControl(ip=qemu.ip, logfile=qemu.sshlog, 
user="root")
 +    ssh.copy_to(builddir + "/" + 
"build/x86_64-unknown-linux-gnu/stage1-tools-bin/remote-test-server","~/")

 +    # Execute remote-test-server on image through background ssh
-+    command = '~/remote-test-server -v remote'
++    command = '~/remote-test-server --bind 0.0.0.0:12345 -v'


--
# Randy MacLeod
# Wind River Linux

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177621): 
https://lists.openembedded.org/g/openembedded-core/message/177621
Mute This Topic: https://lists.openembedded.org/mt/97178295/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] binutils: Fix nativesdk ld.so search

[Khem Raj]

Thanks for the patch it seems ok to me
At least it’s not poking at build machine for ld.so.conf anymore

On Thu, Feb 23, 2023 at 9:56 AM Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:

> Currently binutils in buildtools is searching for /etc/etc/ld.so.conf
> which makes no sense. ld_sysconfdir already contains /etc so we need to
> drop the /etc from the fixed string.
>
> Signed-off-by: Richard Purdie 
> ---
>  ...3-binutils-nativesdk-Search-for-alternative-ld.so.conf.patch | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
> a/meta/recipes-devtools/binutils/binutils/0003-binutils-nativesdk-Search-for-alternative-ld.so.conf.patch
> b/meta/recipes-devtools/binutils/binutils/0003-binutils-nativesdk-Search-for-alternative-ld.so.conf.patch
> index 8e5e2be81dd..54967b9362f 100644
> ---
> a/meta/recipes-devtools/binutils/binutils/0003-binutils-nativesdk-Search-for-alternative-ld.so.conf.patch
> +++
> b/meta/recipes-devtools/binutils/binutils/0003-binutils-nativesdk-Search-for-alternative-ld.so.conf.patch
> @@ -65,7 +65,7 @@ index eff6693e052..95787012b89 100644
> info.path = NULL;
> info.len = info.alloc = 0;
>  -  tmppath = concat (ld_sysroot, prefix, "/etc/ld.so.conf",
> -+  tmppath = concat (ld_sysconfdir, "/etc/ld.so.conf",
> ++  tmppath = concat (ld_sysconfdir, "/ld.so.conf",
> (const char *) NULL);
> if (!ldelf_parse_ld_so_conf (, tmppath))
> {
> --
> 2.37.2
>
>
> 
>
>

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

Re: [docs] [OE-core] Difference between INIT_MANAGER="none" and INIT_MANAGER="sysvinit"?

[Alexander Kanavin]

none is a confusing name though. Should it be dropped and nodistro
tweaked to use sysvinit?

Alex

On Thu, 23 Feb 2023 at 18:39, Khem Raj  wrote:
>
> On Thu, Feb 23, 2023 at 9:09 AM Michael Opdenacker via
> lists.openembedded.org
>  wrote:
> >
> > Greetings
> >
> > I'm trying to document the possible values of INIT_MANAGER.
> >
> > I'm using the master branch of Poky, and whether I'm using
> > INIT_MANAGER="none" or INIT_MANAGER="sysvinit" in conf/local.conf, I'm
> > getting the exact same "core-image-minimal" image (it's not even rebuilt).
> >
> > Anyway, ./meta/conf/distro/include/init-manager-sysvinit.inc and
> > ./meta/conf/distro/include/init-manager-none.inc look very similar and
> > even seem to be equivalent as I'm getting the same image anyway.
> >
> > So, what's the use of INIT_MANAGER = "none"?
> >
>
> It basically sets a nodistro default which is sysvinit like atm.
>
> > Thanks in advance
> > Cheers
> > Michael.
> >
> > --
> > Michael Opdenacker, Bootlin
> > Embedded Linux and Kernel engineering
> > https://bootlin.com
> >
> >
> >
> >
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177619): 
https://lists.openembedded.org/g/openembedded-core/message/177619
Mute This Topic: https://lists.openembedded.org/mt/97189211/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] binutils: Fix nativesdk ld.so search

[Richard Purdie]

Currently binutils in buildtools is searching for /etc/etc/ld.so.conf
which makes no sense. ld_sysconfdir already contains /etc so we need to
drop the /etc from the fixed string.

Signed-off-by: Richard Purdie 
---
 ...3-binutils-nativesdk-Search-for-alternative-ld.so.conf.patch | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/meta/recipes-devtools/binutils/binutils/0003-binutils-nativesdk-Search-for-alternative-ld.so.conf.patch
 
b/meta/recipes-devtools/binutils/binutils/0003-binutils-nativesdk-Search-for-alternative-ld.so.conf.patch
index 8e5e2be81dd..54967b9362f 100644
--- 
a/meta/recipes-devtools/binutils/binutils/0003-binutils-nativesdk-Search-for-alternative-ld.so.conf.patch
+++ 
b/meta/recipes-devtools/binutils/binutils/0003-binutils-nativesdk-Search-for-alternative-ld.so.conf.patch
@@ -65,7 +65,7 @@ index eff6693e052..95787012b89 100644
info.path = NULL;
info.len = info.alloc = 0;
 -  tmppath = concat (ld_sysroot, prefix, "/etc/ld.so.conf",
-+  tmppath = concat (ld_sysconfdir, "/etc/ld.so.conf",
++  tmppath = concat (ld_sysconfdir, "/ld.so.conf",
(const char *) NULL);
if (!ldelf_parse_ld_so_conf (, tmppath))
{
-- 
2.37.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177618): 
https://lists.openembedded.org/g/openembedded-core/message/177618
Mute This Topic: https://lists.openembedded.org/mt/97188650/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] Difference between INIT_MANAGER="none" and INIT_MANAGER="sysvinit"?

[Khem Raj]

On Thu, Feb 23, 2023 at 9:09 AM Michael Opdenacker via
lists.openembedded.org
 wrote:
>
> Greetings
>
> I'm trying to document the possible values of INIT_MANAGER.
>
> I'm using the master branch of Poky, and whether I'm using
> INIT_MANAGER="none" or INIT_MANAGER="sysvinit" in conf/local.conf, I'm
> getting the exact same "core-image-minimal" image (it's not even rebuilt).
>
> Anyway, ./meta/conf/distro/include/init-manager-sysvinit.inc and
> ./meta/conf/distro/include/init-manager-none.inc look very similar and
> even seem to be equivalent as I'm getting the same image anyway.
>
> So, what's the use of INIT_MANAGER = "none"?
>

It basically sets a nodistro default which is sysvinit like atm.

> Thanks in advance
> Cheers
> Michael.
>
> --
> Michael Opdenacker, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>
>
> 
>

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

[OE-core] Difference between INIT_MANAGER="none" and INIT_MANAGER="sysvinit"?

[Michael Opdenacker via lists.openembedded.org]

Greetings

I'm trying to document the possible values of INIT_MANAGER.

I'm using the master branch of Poky, and whether I'm using 
INIT_MANAGER="none" or INIT_MANAGER="sysvinit" in conf/local.conf, I'm 
getting the exact same "core-image-minimal" image (it's not even rebuilt).


Anyway, ./meta/conf/distro/include/init-manager-sysvinit.inc and 
./meta/conf/distro/include/init-manager-none.inc look very similar and 
even seem to be equivalent as I'm getting the same image anyway.


So, what's the use of INIT_MANAGER = "none"?

Thanks in advance
Cheers
Michael.

--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177616): 
https://lists.openembedded.org/g/openembedded-core/message/177616
Mute This Topic: https://lists.openembedded.org/mt/97187470/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] [docs] [DISTRO|MACHINE]_FEATURES_BACKFILL_CONSIDERED: confusing variable names?

[Joshua Watt]

On Thu, Feb 23, 2023 at 10:59 AM Michael Opdenacker via
lists.yoctoproject.org
 wrote:
>
> Greetings
>
> Anybody else finding the DISTRO_FEATURES_BACKFILL_CONSIDERED and
> MACHINE_FEATURES_BACKFILL_CONSIDERED variable names confusing?

I believe the history there is that those are "features" that were
just always available and couldn't be turned off (e.g. they were
implicit). When they became available to be turned off, it was desired
to not break existing setups by making them "off by default", so you
have to explicitly opt-out of said feature. I always think of it as "I
CONSIDERED this features and don't want it"


>
> According to the documentation about "feature backfilling"
> (https://docs.yoctoproject.org/ref-manual/features.html#ref-features-backfill),
> these variables allow to exclude some features from being backfilled.
>
> I'm not a native English speaker, but for me, "considered" carries the
> intention to include a feature, not to exclude one.
>
> Shouldn't we call these variables DISTRO_FEATURES_BACKFILL_EXCLUDED and
> MACHINE_FEATURES_BACKFILL_EXCLUDED instead ?
>
> Thanks in advance
> Cheers
> Michael.
>
> --
> Michael Opdenacker, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>
>
> 
>

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

[OE-core] [DISTRO|MACHINE]_FEATURES_BACKFILL_CONSIDERED: confusing variable names?

[Michael Opdenacker via lists.openembedded.org]

Greetings

Anybody else finding the DISTRO_FEATURES_BACKFILL_CONSIDERED and 
MACHINE_FEATURES_BACKFILL_CONSIDERED variable names confusing?


According to the documentation about "feature backfilling" 
(https://docs.yoctoproject.org/ref-manual/features.html#ref-features-backfill), 
these variables allow to exclude some features from being backfilled.


I'm not a native English speaker, but for me, "considered" carries the 
intention to include a feature, not to exclude one.


Shouldn't we call these variables DISTRO_FEATURES_BACKFILL_EXCLUDED and 
MACHINE_FEATURES_BACKFILL_EXCLUDED instead ?


Thanks in advance
Cheers
Michael.

--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177614): 
https://lists.openembedded.org/g/openembedded-core/message/177614
Mute This Topic: https://lists.openembedded.org/mt/97187180/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][PATCHv3] vte: update 0.70.2 -> 0.70.3

[Alexandre Belloni via lists.openembedded.org]

It failed on qemux86-64-x32:

https://autobuilder.yoctoproject.org/typhoon/#/builders/57/builds/6598/steps/11/logs/stdio

On 23/02/2023 08:52:56+0100, Markus Volk wrote:
> - Allow to build the gtk4 widget and vapi
>   This is needed to build gtk4 based terminals like blackbox
> - Update dependencies
> - Cleanup recipe
> 
> Signed-off-by: Markus Volk 
> ---
>  .../vte/{vte_0.70.2.bb => vte_0.70.3.bb}  | 22 +--
>  1 file changed, 11 insertions(+), 11 deletions(-)
>  rename meta/recipes-support/vte/{vte_0.70.2.bb => vte_0.70.3.bb} (71%)
> 
> diff --git a/meta/recipes-support/vte/vte_0.70.2.bb 
> b/meta/recipes-support/vte/vte_0.70.3.bb
> similarity index 71%
> rename from meta/recipes-support/vte/vte_0.70.2.bb
> rename to meta/recipes-support/vte/vte_0.70.3.bb
> index ec2fb1f522..474ed87a88 100644
> --- a/meta/recipes-support/vte/vte_0.70.2.bb
> +++ b/meta/recipes-support/vte/vte_0.70.3.bb
> @@ -11,34 +11,34 @@ LIC_FILES_CHKSUM = " \
>  file://COPYING.XTERM;md5=d7fc3a23c16c039afafe2e042030f057 \
>  "
>  
> -DEPENDS = "glib-2.0 gtk+3 libpcre2 libxml2-native gperf-native icu"
> +DEPENDS = "fribidi glib-2.0 gtk+3 libpcre2 libxml2-native gperf-native icu 
> pango zlib"
>  
>  GNOMEBASEBUILDCLASS = "meson"
>  GIR_MESON_OPTION = 'gir'
>  GIDOCGEN_MESON_OPTION = "docs"
>  
> -inherit gnomebase gi-docgen features_check upstream-version-is-even 
> gobject-introspection
> +inherit gnomebase gi-docgen features_check upstream-version-is-even 
> gobject-introspection vala
>  
> -# vapigen.m4 is required when vala is not present (but the one from vala 
> should be used normally)
>  SRC_URI += "file://0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch"
> -SRC_URI[archive.sha256sum] = 
> "4d15b4380de3f564d57eabd006389c407c705df5b0c70030fdcc24971a334d80"
> +SRC_URI[archive.sha256sum] = 
> "9457134a02f3157fca04f7e0d39bdb0f3099be0a3ce82b7139d0c98a80748f23"
>  
>  ANY_OF_DISTRO_FEATURES = "${GTK3DISTROFEATURES}"
>  
> -# Help g-ir-scanner find the .so for linking
> -do_compile:prepend() {
> -export GIR_EXTRA_LIBS_PATH="${B}/src/.libs"
> -}
> -
>  # Package additional files
>  FILES:${PN}-dev += "${datadir}/vala/vapi/*"
>  
> -PACKAGECONFIG ??= "gnutls"
> -PACKAGECONFIG[vala] = "-Dvapi=true,-Dvapi=false,vala-native vala"
> +PACKAGECONFIG ??= " \
> +gnutls \
> +${@bb.utils.contains('DISTRO_FEATURES', 'gobject-introspection-data', 
> 'vala', '', d)} \
> +${@bb.utils.contains('DISTRO_FEATURES', 'opengl', 'gtk4', '', d)} \
> +"
> +PACKAGECONFIG[gtk4] = "-Dgtk4=true,-Dgtk4=false,gtk4"
> +PACKAGECONFIG[vala] = "-Dvapi=true,-Dvapi=false"
>  PACKAGECONFIG[gnutls] = "-Dgnutls=true,-Dgnutls=false,gnutls"
>  PACKAGECONFIG[systemd] = "-D_systemd=true,-D_systemd=false,systemd"
>  # vala requires gir
>  PACKAGECONFIG:remove:class-native = "vala"
> +PACKAGECONFIG:remove:class-nativesdk = "vala gtk4"
>  
>  CFLAGS += "-D_GNU_SOURCE"
>  
> -- 
> 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 (#177613): 
https://lists.openembedded.org/g/openembedded-core/message/177613
Mute This Topic: https://lists.openembedded.org/mt/97178843/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][langdale 00/22] Pull request (cover letter only)

[Steve Sakoman]

The following changes since commit 62b894d75fb3361ed4d5473ae69188bce390980a:

  oeqa context.py: fix --target-ip comment to include ssh port number 
(2023-02-11 04:03:34 -1000)

are available in the Git repository at:

  https://git.openembedded.org/openembedded-core-contrib stable/langdale-next
  
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/langdale-next

Alexander Kanavin (10):
  diffutils: update 3.8 -> 3.9
  lttng-tools: update 2.13.8 -> 2.13.9
  apr: update 1.7.0 -> 1.7.2
  apr-util: update 1.6.1 -> 1.6.3
  bind: upgrade 9.18.10 -> 9.18.11
  libjpeg-turbo: upgrade 2.1.4 -> 2.1.5
  pkgconf: upgrade 1.9.3 -> 1.9.4
  linux-firmware: upgrade 20221214 -> 20230117
  sudo: upgrade 1.9.12p1 -> 1.9.12p2
  libgit2: upgrade 1.5.0 -> 1.5.1

Chen Qi (1):
  ffmpeg: fix configure failure on noexec /tmp host

Mauro Queiros (1):
  image.bbclass: print all QA functions exceptions

Mikko Rapeli (6):
  oeqa ssh.py: move output prints to new line
  oeqa ssh.py: add connection keep alive options to ssh client
  oeqa dump.py: add error counter and stop after 5 failures
  oeqa qemurunner: read more data at a time from serial
  oeqa qemurunner.py: add timeout to QMP calls
  oeqa qemurunner.py: try to avoid reading one character at a time

Peter Kjellerstedt (1):
  devshell: Do not add scripts/git-intercept to PATH

Rodolfo Quesada Zumbado (1):
  tar: CVE-2022-48303

Sakib Sajal (1):
  git: upgrade 2.37.5 -> 2.37.6

Ulrich Ölmann (1):
  update-alternatives: fix typos

 meta/classes-global/devshell.bbclass  |   2 -
 meta/classes-recipe/image.bbclass |   2 +-
 .../update-alternatives.bbclass   |   6 +-
 meta/lib/oeqa/core/target/ssh.py  |   8 +-
 meta/lib/oeqa/utils/dump.py   |  23 ++-
 meta/lib/oeqa/utils/qemurunner.py |   9 +-
 ...1-avoid-start-failure-with-bind-user.patch |   0
 ...d-V-and-start-log-hide-build-options.patch |   0
 ...ching-for-json-headers-searches-sysr.patch |   0
 .../bind/{bind-9.18.10 => bind-9.18.11}/bind9 |   0
 .../{bind-9.18.10 => bind-9.18.11}/conf.patch |   0
 .../generate-rndc-key.sh  |   0
 ...t.d-add-support-for-read-only-rootfs.patch |   0
 .../make-etc-initd-bind-stop-work.patch   |   0
 .../named.service |   0
 .../bind/{bind_9.18.10.bb => bind_9.18.11.bb} |   4 +-
 .../git/{git_2.37.5.bb => git_2.37.6.bb}  |   2 +-
 .../{pkgconf_1.9.3.bb => pkgconf_1.9.4.bb}|   2 +-
 ...001-Skip-strip-trailing-cr-test-case.patch |  11 +-
 ...a-standard-layout-so-glibc-and-musl-.patch |  33 -
 .../{diffutils_3.8.bb => diffutils_3.9.bb}|   3 +-
 .../{sudo_1.9.12p1.bb => sudo_1.9.12p2.bb}|   2 +-
 .../tar/tar/CVE-2022-48303.patch  |  43 ++
 meta/recipes-extended/tar/tar_1.34.bb |   4 +-
 ...-turbo_2.1.4.bb => libjpeg-turbo_2.1.5.bb} |   2 +-
 ...20221214.bb => linux-firmware_20230117.bb} |   6 +-
 .../lttng/lttng-tools/determinism.patch   |  64 -
 ...-tools_2.13.8.bb => lttng-tools_2.13.9.bb} |   3 +-
 .../recipes-multimedia/ffmpeg/ffmpeg_5.1.2.bb |   2 +
 .../0001-Fix-error-handling-in-gdbm.patch | 134 --
 .../{apr-util_1.6.1.bb => apr-util_1.6.3.bb}  |   6 +-
 ...ion-to-disable-timed-dependant-tests.patch |  20 +--
 ...CHE_CHECK-for-strerror_r-return-type.patch |  52 ---
 ...-runtime-test-for-mmap-that-can-map-.patch |  26 ++--
 ...ir-path-references-from-installed-ap.patch |  25 ++--
 ...configure.in-support-cross-compiling.patch |  63 
 ...ze-doesn-t-match-in-glibc-when-cross.patch |  76 --
 .../apr/apr/CVE-2021-35940.patch  |  58 
 .../recipes-support/apr/apr/autoconf270.patch |  22 ---
 .../apr/apr/libtoolize_check.patch|  21 ++-
 .../apr/{apr_1.7.0.bb => apr_1.7.2.bb}|   8 +-
 .../{libgit2_1.5.0.bb => libgit2_1.5.1.bb}|   4 +-
 42 files changed, 157 insertions(+), 589 deletions(-)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => 
bind-9.18.11}/0001-avoid-start-failure-with-bind-user.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => 
bind-9.18.11}/0001-named-lwresd-V-and-start-log-hide-build-options.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => 
bind-9.18.11}/bind-ensure-searching-for-json-headers-searches-sysr.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => bind-9.18.11}/bind9 
(100%)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => 
bind-9.18.11}/conf.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => 
bind-9.18.11}/generate-rndc-key.sh (100%)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => 
bind-9.18.11}/init.d-add-support-for-read-only-rootfs.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => 
bind-9.18.11}/make-etc-initd-bind-stop-work.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => 
bind-9.18.11}/named.service (100%)
 rename meta/recipes-connectivity/bind/{bind_9.18.10.bb => 

[OE-core][dunfell 00/16] Pull request (cover letter only)

[Steve Sakoman]

The following changes since commit daaee6fcb0d201f041678af433d8e1cd6f924d09:

  build-appliance-image: Update to dunfell head revision (2023-02-13 07:48:21 
+)

are available in the Git repository at:

  https://git.openembedded.org/openembedded-core-contrib stable/dunfell-next
  
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-next

Alexander Kanavin (1):
  oeqa/qemurunner: do not use Popen.poll() when terminating runqemu with
a signal

Antonin Godard (2):
  busybox: always start do_compile with orig config files
  busybox: rm temporary files if do_compile was interrupted

Hitendra Prajapati (1):
  git: CVE-2022-23521 gitattributes parsing integer overflow

Martin Jansa (1):
  meta: remove True option to getVar and getVarFlag calls (again)

Mikko Rapeli (1):
  oeqa context.py: fix --target-ip comment to include ssh port number

Omkar Patil (1):
  sudo: Fix CVE-2023-22809

Pawel Zalewski (1):
  classes/fs-uuid: Fix command output decoding issue

Richard Purdie (3):
  nativesdk: Handle chown/chgrp calls in nativesdk do_install tasks
  make-mod-scripts: Ensure kernel build output is deterministic
  libc-locale: Fix on target locale generation

Ross Burton (3):
  quilt: fix intermittent failure in faildiff.test
  quilt: use upstreamed faildiff.test fix
  git: ignore CVE-2022-41953

Steve Sakoman (1):
  qemu: Fix slirp determinism issue

Vivek Kumbhar (1):
  qemu: fix CVE-2021-3929 nvme DMA reentrancy issue leads to
use-after-free

 meta/classes/fs-uuid.bbclass  |   2 +-
 meta/classes/image.bbclass|   2 +-
 meta/classes/libc-package.bbclass |   1 +
 meta/classes/license_image.bbclass|   2 +-
 meta/classes/nativesdk.bbclass|   2 +
 meta/lib/oeqa/runtime/context.py  |   4 +-
 meta/lib/oeqa/utils/qemurunner.py |  11 +-
 meta/recipes-core/busybox/busybox.inc |  27 +-
 .../git/files/CVE-2022-23521.patch| 367 ++
 meta/recipes-devtools/git/git.inc |   4 +-
 meta/recipes-devtools/go/go_1.14.bb   |   4 +-
 .../qemu/qemu-system-native_4.2.0.bb  |   2 +-
 meta/recipes-devtools/qemu/qemu.inc   |   3 +
 .../qemu/qemu/CVE-2021-3929.patch |  78 
 meta/recipes-devtools/qemu/qemu_4.2.0.bb  |   4 +-
 meta/recipes-devtools/quilt/quilt.inc |   1 +
 .../quilt/quilt/faildiff-order.patch  |  41 ++
 .../sudo/files/CVE-2023-22809.patch   | 113 ++
 meta/recipes-extended/sudo/sudo_1.8.32.bb |   1 +
 .../make-mod-scripts/make-mod-scripts_1.0.bb  |   2 +-
 scripts/lib/devtool/menuconfig.py |   2 +-
 scripts/nativesdk-intercept/chgrp |  27 ++
 scripts/nativesdk-intercept/chown |  27 ++
 23 files changed, 702 insertions(+), 25 deletions(-)
 create mode 100644 meta/recipes-devtools/git/files/CVE-2022-23521.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2021-3929.patch
 create mode 100644 meta/recipes-devtools/quilt/quilt/faildiff-order.patch
 create mode 100644 meta/recipes-extended/sudo/files/CVE-2023-22809.patch
 create mode 100755 scripts/nativesdk-intercept/chgrp
 create mode 100755 scripts/nativesdk-intercept/chown

-- 
2.34.1


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

[Alexander Kanavin]

I suspect there isn't. You need to write a recipe.

Alex

On Thu, 23 Feb 2023 at 14:56, Zoltan Boszormenyi  wrote:
>
> Hi,
>
> I have tried to upgrade the Mesa recipe to use 23.0.0
> and tried to enable Rusticl by adding these:
>
> inherit rust
> PACKAGECONFIG[rusticl] = "-Dgallium-rusticl=true
> -Drust_std=2021,-Dgallium-rusticl=false,libclc spirv-tools 
> spirv-llvm-translator,libclc
> spirv-tools spirv-llvm-translator"
> PACKAGECONFIG:append:x86-64:class-target = " rusticl"
>
> To do that on Kirkstone, meson 1.0.0 needs to be backported, which is not an 
> issue.
>
> Configure stage fails with:
>
> Program bindgen found: NO
>
> Where is bindgen in Yocto?
>
> Thanks in advance,
> Zoltán Böszörményi
>
>
> 
>

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

[OE-core] bindgen missing?

[Zoltan Boszormenyi]

Hi,

I have tried to upgrade the Mesa recipe to use 23.0.0
and tried to enable Rusticl by adding these:

inherit rust
PACKAGECONFIG[rusticl] = "-Dgallium-rusticl=true 
-Drust_std=2021,-Dgallium-rusticl=false,libclc spirv-tools spirv-llvm-translator,libclc 
spirv-tools spirv-llvm-translator"

PACKAGECONFIG:append:x86-64:class-target = " rusticl"

To do that on Kirkstone, meson 1.0.0 needs to be backported, which is not an 
issue.

Configure stage fails with:

Program bindgen found: NO

Where is bindgen in Yocto?

Thanks in advance,
Zoltán Böszörményi


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177609): 
https://lists.openembedded.org/g/openembedded-core/message/177609
Mute This Topic: https://lists.openembedded.org/mt/97182761/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] checklayer: check for patch file upstream status

[Bruce Ashfield]

On Thu, Feb 23, 2023 at 8:48 AM Richard Purdie
 wrote:
>
> On Thu, 2023-02-23 at 08:33 -0500, Bruce Ashfield wrote:
> > I don't recall the upstream-status being added as a yocto
> > compatibility requirement. Can someone point me to a discussion that I
> > missed ?
>
> It isn't a requirement at this time and there isn't any recent
> discussion you've missed.
>
> The topic has come up now and again at various points, including with
> the YP TSC and I suspect that was why we have
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=14642 from back in
> 2021. I think the view of the YP TSC was that we probably should warn
> about things like this from yocto-check-layer perspective as it is a
> best practise we want to raise the profile of.
>
> > As everyone can recall, I wasn't on board with this being a default QA
> > check and error, and I'm also not on board with it being a yocto
> > compliance error.
> >
> > I realize it isn't being made an error in this patch, but I wanted to
> > raise my concerns now, before someone throws that switch.
>
> Your concerns are definitely known! As I said at the time in the
> discussion, the TSC does intend to add some extra checks around QA
> issues to YP Compatible but no decision on which ones has been made
> yet, I think that action rests with me to make a proposal. My view is
> this one can remain a warning, I can't speak for the rest of the TSC. I
> do think having yocto-check-layer show more warnings about best
> practises if the direction things will move though even if it doesn't
> change the resulting compatibility status.
>
> There is an intent to improve "quality" over time so I can't promise
> this will never become an error but I don't have any plans to push this
> beyond a warning. As above, I can't speak for all TSC members though.
>

Sounds good.

Summary: Everything is under control, and I didn't manage to zone out
and miss something while battling with the latest round of golang
craziness.

I've already gone through my layers and updated the formatting and put
inappropriate on most of the patches (I may have missed some), so my
argument isn't really an argument at this point. With the QA check
being around now, and anyone being able to turn it on, patches without
a status should be fairly rare.

If it did become a compatibility requirement, I'd of course make the
changes and stay compatible (maybe grumbling a bit at the same time
;))

Cheers,

Bruce

> Cheers,
>
> Richard
>
>
>
>


-- 
- 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 (#177608): 
https://lists.openembedded.org/g/openembedded-core/message/177608
Mute This Topic: https://lists.openembedded.org/mt/97178225/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] checklayer: check for patch file upstream status

[Richard Purdie]

On Thu, 2023-02-23 at 08:33 -0500, Bruce Ashfield wrote:
> I don't recall the upstream-status being added as a yocto
> compatibility requirement. Can someone point me to a discussion that I
> missed ?

It isn't a requirement at this time and there isn't any recent
discussion you've missed. 

The topic has come up now and again at various points, including with
the YP TSC and I suspect that was why we have
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14642 from back in
2021. I think the view of the YP TSC was that we probably should warn
about things like this from yocto-check-layer perspective as it is a
best practise we want to raise the profile of.

> As everyone can recall, I wasn't on board with this being a default QA
> check and error, and I'm also not on board with it being a yocto
> compliance error.
> 
> I realize it isn't being made an error in this patch, but I wanted to
> raise my concerns now, before someone throws that switch.

Your concerns are definitely known! As I said at the time in the
discussion, the TSC does intend to add some extra checks around QA
issues to YP Compatible but no decision on which ones has been made
yet, I think that action rests with me to make a proposal. My view is
this one can remain a warning, I can't speak for the rest of the TSC. I
do think having yocto-check-layer show more warnings about best
practises if the direction things will move though even if it doesn't
change the resulting compatibility status.

There is an intent to improve "quality" over time so I can't promise
this will never become an error but I don't have any plans to push this
beyond a warning. As above, I can't speak for all TSC members though.

Cheers,

Richard





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177607): 
https://lists.openembedded.org/g/openembedded-core/message/177607
Mute This Topic: https://lists.openembedded.org/mt/97178225/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] checklayer: check for patch file upstream status

[Bruce Ashfield]

I don't recall the upstream-status being added as a yocto
compatibility requirement. Can someone point me to a discussion that I
missed ?

As everyone can recall, I wasn't on board with this being a default QA
check and error, and I'm also not on board with it being a yocto
compliance error.

I realize it isn't being made an error in this patch, but I wanted to
raise my concerns now, before someone throws that switch.

Bruce

On Thu, Feb 23, 2023 at 1:28 AM Lee Chee Yang  wrote:
>
> From: Chee Yang Lee 
>
> yocto-check-layer to check all .patch file in layer for
> Upstream-status and list down all .patch file without Upstream-Status.
> Since upstream-status is additional Yocto Compatible requirement,
> set this test as expected failure for now so it wont fail final
> result.
>
> [YOCTO #14642]
>
> Signed-off-by: Chee Yang Lee 
> ---
>  scripts/lib/checklayer/cases/common.py | 15 +++
>  1 file changed, 15 insertions(+)
>
> diff --git a/scripts/lib/checklayer/cases/common.py 
> b/scripts/lib/checklayer/cases/common.py
> index 722d3cf638..8fb37e175f 100644
> --- a/scripts/lib/checklayer/cases/common.py
> +++ b/scripts/lib/checklayer/cases/common.py
> @@ -72,6 +72,21 @@ class CommonCheckLayer(OECheckLayerTestCase):
>  self.tc.layer['name'])
>  self.fail('\n'.join(msg))
>
> +@unittest.expectedFailure
> +def test_patches_upstream_status(self):
> +patches = []
> +for dirpath, dirs, files in os.walk(self.tc.layer['path']):
> +for filename in files:
> +if filename.endswith(".patch"):
> +data = ""
> +ppath = os.path.join(dirpath, filename)
> +with open(ppath, 'r', encoding='utf-8', errors='ignore') 
> as f:
> +data = f.read()
> +if not re.search(r'^Upstream-Status', data, flags=re.I + 
> re.M):
> +patches.append(ppath)
> +self.assertEqual(len(patches), 0 , \
> +msg="Layer contains patches without upstream status:\n%s" % 
> '\n'.join([str(patch) for patch in patches]))
> +
>  def test_signatures(self):
>  if self.tc.layer['type'] == LayerType.SOFTWARE and \
> not self.tc.test_software_layer_signatures:
> --
> 2.37.3
>
>
> 
>


-- 
- 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 (#177606): 
https://lists.openembedded.org/g/openembedded-core/message/177606
Mute This Topic: https://lists.openembedded.org/mt/97178225/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-