date:20230222

- 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


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

Am Do, 23. Feb 2023 um 00:42:15 +0100 schrieb Alexandre Belloni 
:

This fails on musl:


I've missinterpreted that this patch is not needed anymore
0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch

After following the conversation Ross Burton started some years ago it 
turned out, that the issue is 'wont fix', because the vte maintainer 
refuses to support musl.


Adding back the patch fixes the issue


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177604): 
https://lists.openembedded.org/g/openembedded-core/message/177604
Mute This Topic: https://lists.openembedded.org/mt/97115916/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] mc: set ac_cv_path_PERL_FOR_BUILD

2023-02-22 Thread Yu, Mingli

From: Mingli Yu 

After mc upgrade to 4.8.29, it introduces PERL_FOR_BUILD [1] and will
result in the below build failure on some system when we build under
a project with long path.
 | make[4]: Entering directory 
'/buildarea2/WTEST_Regression/Rerun/build_dir/02161802-multilib_pkgs_conflict/qemux86-64-standard-std-OE/build1/tmp-glibc/work/core2-64-wrs-linux/mc/4.8.29-r0/build/doc/hlp/es'
 make[4]: Nothing to be done for 'install-exec-am'.
 | ../../../src/man2hlp/man2hlp ../../../doc/man/es/mc.1 
../../../../mc-4.8.29/doc/hlp/es/xnc.hlp mc.hlp.es
 | ../../../src/man2hlp/man2hlp: line 32: use: command not found
 | ../../../src/man2hlp/man2hlp: line 33: use: command not found
 | ../../../src/man2hlp/man2hlp: line 36: syntax error near unexpected token `('
 | ../../../src/man2hlp/man2hlp: line 36: `my %static = ('
 | make[4]: [Makefile:632: mc.hlp.es] Error 2 (ignored)

 $ head -n 5 
tmp-glibc/work/core2-64-wrs-linux/mc/4.8.29-r0/build/src/man2hlp/man2hlp
 #! 
/buildarea2/WTEST_Regression/Rerun/build_dir/02161802-multilib_pkgs_conflict/qemux86-64-standard-std-OE/build1/tmp-glibc/hosttools/perl
 #
 #  Man page to help file converter
 #  Copyright (C) 1994, 1995, 1998, 2000, 2001, 2002, 2003, 2004, 2005,
 #  2007, 2010, 2011

It's beacause the shebang line exceeds 128 which is usually the max
length.

So set ac_cv_path_PERL_FOR_BUILD to fix the above issue and altogether
to remove the build path issue.

[1] 
https://github.com/MidnightCommander/mc/commit/6b67d231a2f447cf5f33180c618c2a67849e6d15

Signed-off-by: Mingli Yu 
---
 meta/recipes-extended/mc/mc_4.8.29.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-extended/mc/mc_4.8.29.bb 
b/meta/recipes-extended/mc/mc_4.8.29.bb
index c9db172183..7aac352ab5 100644
--- a/meta/recipes-extended/mc/mc_4.8.29.bb
+++ b/meta/recipes-extended/mc/mc_4.8.29.bb
@@ -32,6 +32,7 @@ EXTRA_OECONF = "--with-screen=ncurses --without-gpm-mouse 
--without-x --disable-
 EXTRANATIVEPATH += "file-native"
 
 CACHED_CONFIGUREVARS += "ac_cv_path_PERL='/usr/bin/env perl'"
+CACHED_CONFIGUREVARS += "ac_cv_path_PERL_FOR_BUILD='/usr/bin/env perl'"
 CACHED_CONFIGUREVARS += "ac_cv_path_PYTHON='/usr/bin/env python'"
 CACHED_CONFIGUREVARS += "ac_cv_path_GREP='/usr/bin/env grep'"
 CACHED_CONFIGUREVARS += "mc_cv_have_zipinfo=yes"
-- 
2.25.1


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

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


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

2023-02-22 Thread Pgowda

From: pgowda 

The patch implements Rust testing framework similar to other selftest,
specifically the gcc selftest in OE. It uses the client and server
based method to test the binaries for cross-target on the image.
The test framework is a wrapper around the Rust build system as ./x.py
test. It tests many functionalities of Rust distribution like tools,
documentation, libraries, packages, tools, Cargo, Crater etc.
Please refer the following link for detailed description of Rust
testing:-
https://rustc-dev-guide.rust-lang.org/tests/intro.html#tool-tests

To support the rust tests in oe-core, the following functions were
added:-
setup_cargo_environment(): Build bootstrap and some early stage tools.
do_rust_setup_snapshot(): Install the snapshot version of rust binaries.
do_configure(): To generate config.toml
do_compile(): To build "remote-test-server" for qemu target image.

Approximate Number of Tests Run in the Rust Testsuite :- 18000
Approximate Number of Tests that FAIL in bitbake environment :- 100-150
Normally majority of the testcases are present in major folder "test/"
It contributes to more than 80% of the testcases present in Rust test
framework. These tests pass as expected on any Rust versions without
much fuss. The tests that fail are of less important and contribute to
less than 2% of the total testcases. These minor tests are observed to
work on some versions and fail on others. They have to be added, ignored
or excluded for different versions as per the behavior.
These tests have been ignored or excluded in the Rust selftest
environment to generate success of completing the testsuite.

These tests work in parallel mode even in the skipped test mode as
expected. Although the patch to disable tests is large, it is very simple
in that it only disables tests. When updating to a newer version of Rust,
the patch can usually be ported in a day.

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 ++
 .../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/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..f9889b840c
--- /dev/null
+++ b/meta/lib/oeqa/selftest/cases/rust.py
@@ -0,0 +1,54 @@
+# SPDX-License-Identifier: MIT
+import os
+import subprocess
+from oeqa.core.decorator import OETestTag
+from oeqa.core.case import OEPTestResultTestCase
+from oeqa.selftest.case import OESelftestTestCase
+from oeqa.utils.commands import runCmd, bitbake, get_bb_var, get_bb_vars, 
runqemu, Command
+from oeqa.utils.sshcontrol import SSHControl
+
+# Total time taken for testing is of about 2hr 20min, with PARALLEL_MAKE set 
to 40 number of jobs.
+class RustSelfTestSystemEmulated(OESelftestTestCase, OEPTestResultTestCase):
+def test_rust(self, *args, **kwargs):
+# build remote-test-server before image build
+recipe = "rust"
+bitbake("{} -c test_compile".format(recipe))
+builddir = get_bb_var("RUSTSRC", "rust")
+# build core-image-minimal with required packages
+default_installed_packages = ["libgcc", "libstdc++", "libatomic", 
"libgomp"]
+features = []
+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")
+# wrap the execution with a qemu instance.
+# Tests are run with 512 tasks in parallel to execute all tests very 
quickly
+with runqemu("core-image-minimal", runqemuparams = "nographic", 
qemuparams = "-m 512") as qemu:
+# Copy remote-test-server to image through scp
+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 --bind 0.0.0.0:12345 -v'
+sshrun=subprocess.Popen(("ssh", '-o',  
'UserKnownHostsFile=/dev/null', '-o',  'StrictHostKeyChecking=no', '-f', 
"root@%s" % qemu.ip, command), shell=False, stdout=subprocess.PIPE, 
stderr=subprocess.PIPE)
+# Get the values of variables.
+tcpath = get_bb_var("TARGET_SYS", "rust")
+targetsys = get_bb_var("RUST_TARGET_SYS", "rust")
+rustlibpath = get_bb_var("WORKDIR", "rust")
+tmpdir = get_bb_var("TMPDIR", "rust")
+
+# Exclude the test folders

Re: [OE-core] [PATCH v3] gdb: Upgrade to 13.1

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
> `__libc_current_sigrtmin_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:
>

[OE-core] [PATCH] checklayer: check for patch file upstream status

2023-02-22 Thread 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.
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


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

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
`__libc_current_sigrtmin_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
`_dl_make_stack_executable@GLIBC_PRIVATE'

Re: [OE-core] [PATCH v3] gdb: Upgrade to 13.1

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
>

send a v4 which should fix musl issue, I was able to reproduce it.

> Note that reproducible still failed:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/2438/steps/13/logs/stdio
>

This I need to reproduce first.

>
> On 22/02/2023 08:53:58-0800, Khem Raj wrote:
> > Pass -Wno-enum-constexpr-conversion with clang
> >
> > GDB 13.1 includes the following changes and enhancements:
> >
> > * Support for the following new targets has been added in both
> >   GDB and GDBserver:
> >
> >   ** GNU/Linux/LoongArch (gdbserver) loongarch*-*-linux*
> >
> >   ** GNU/Linux/CSKY (gdbserver) csky*-*linux*
> >
> > * The Windows native target now supports target async.
> >
> > * FreeBSD:
> >
> >   ** Arm and AArch64: Support for Thread Local Storage (TLS) variables
> >
> >   ** Hardware watchpoint support on AArch64 FreeBSD
> >
> > * Floating-point support has now been added on LoongArch GNU/Linux.
> >
> > * New commands:
> >
> >  ** set print nibbles [on|off]
> > show print nibbles
> >
> > This controls whether the 'print/t' command will display binary values
> > in groups of four bits, known as "nibbles".  The default is 'off'.
> >
> >  ** Various styling-related commands. See the gdb/NEWS file for more
> > details (see link at the bottom).
> >
> >  ** Various maintenance commands.  These are normally aimed at GDB
> > experts or developers. See the gdb/NEWS file for more details
> > (see link at the bottom).
> >
> > * Python API improvements:
> >
> >  ** New Python API for instruction disassembly.
> > The new attribute 'locations' of gdb.Breakpoint returns a list of
> > gdb.BreakpointLocation objects specifying the locations where the
> > breakpoint is inserted into the debuggee.
> >
> >  ** New Python type gdb.BreakpointLocation.
> >
> >  ** New function gdb.format_address(ADDRESS, PROGSPACE, ARCHITECTURE)
> > that formats ADDRESS as 'address '
> >
> >  ** New function gdb.current_language that returns the name of the
> > current language.  Unlike gdb.parameter('language'), this will
> > never return 'auto'.
> >
> >  ** New function gdb.print_options that returns a dictionary of the
> > prevailing print options, in the form accepted by 
> > gdb.Value.format_string.
> >
> >  ** New method gdb.Frame.language that returns the name of the
> > frame's language.
> >
> >  ** gdb.Value.format_string now uses the format provided by 'print',
> > if it is called during a 'print' or other similar operation.
> >
> >  ** gdb.Value.format_string now accepts the 'summary' keyword.  This
> > can be used to request a shorter representation of a value, the
> > way that 'set print frame-arguments scalars' does.
> >
> >  ** The gdb.register_window_type method now restricts the set of
> > acceptable window names.  The first character of a window's name
> > must start with a character in the set [a-zA-Z], every subsequent
> > character of a window's name must be in the set [-_.a-zA-Z0-9].
> >
> > * GDB/MI changes:
> >
> >   ** MI version 1 is deprecated, and will be removed in GDB 14.
> >
> >   ** The async record stating the stopped reason 'breakpoint-hit' now
> >  contains an optional field locno.
> >
> > * Miscellaneous improvements:
> >
> >   ** gdb now supports zstd compressed debug sections (ELFCOMPRESS_ZSTD) for 
> > ELF.
> >
> >   ** New convenience variable $_inferior_thread_count contains the number
> >  of live threads in the current inferior.
> >
> >   ** New convenience variables $_hit_bpnum and $_hit_locno, set to
> >  the breakpoint number and the breakpoint location number of
> >  the breakpoint last hit.
> >
> >   ** The "info breakpoints" now displays enabled breakpoint locations
> >  of disabled breakpoints as in the "y-" state.
> >
> >   ** The format of 'disassemble /r' and 'record instruction-history /r'
> >

[OE-core] [PATCH v4] gdb: Upgrade to 13.1

Add patch to fix typo for build on musl

GDB 13.1 includes the following changes and enhancements:

* Support for the following new targets has been added in both
GDB and GDBserver:

** GNU/Linux/LoongArch (gdbserver) loongarch*-*-linux*

** GNU/Linux/CSKY (gdbserver) csky*-*linux*

* The Windows native target now supports target async.

* FreeBSD:

** Arm and AArch64: Support for Thread Local Storage (TLS) variables

** Hardware watchpoint support on AArch64 FreeBSD

* Floating-point support has now been added on LoongArch GNU/Linux.

* New commands:

** set print nibbles [on|off]
show print nibbles

This controls whether the 'print/t' command will display binary values
in groups of four bits, known as "nibbles". The default is 'off'.

** Various styling-related commands. See the gdb/NEWS file for more
details (see link at the bottom).

** Various maintenance commands. These are normally aimed at GDB
experts or developers. See the gdb/NEWS file for more details
(see link at the bottom).

* Python API improvements:

** New Python API for instruction disassembly.
The new attribute 'locations' of gdb.Breakpoint returns a list of
gdb.BreakpointLocation objects specifying the locations where the
breakpoint is inserted into the debuggee.

** New Python type gdb.BreakpointLocation.

** New function gdb.format_address(ADDRESS, PROGSPACE, ARCHITECTURE)
that formats ADDRESS as 'address '

** New function gdb.current_language that returns the name of the
current language. Unlike gdb.parameter('language'), this will
never return 'auto'.

** New function gdb.print_options that returns a dictionary of the
prevailing print options, in the form accepted by gdb.Value.format_string.

** New method gdb.Frame.language that returns the name of the
frame's language.

** gdb.Value.format_string now uses the format provided by 'print',
if it is called during a 'print' or other similar operation.

** gdb.Value.format_string now accepts the 'summary' keyword. This
can be used to request a shorter representation of a value, the
way that 'set print frame-arguments scalars' does.

** The gdb.register_window_type method now restricts the set of
acceptable window names. The first character of a window's name
must start with a character in the set [a-zA-Z], every subsequent
character of a window's name must be in the set [-_.a-zA-Z0-9].

* GDB/MI changes:

** MI version 1 is deprecated, and will be removed in GDB 14.

** The async record stating the stopped reason 'breakpoint-hit' now
contains an optional field locno.

* Miscellaneous improvements:

** gdb now supports zstd compressed debug sections (ELFCOMPRESS_ZSTD) for ELF.

** New convenience variable $_inferior_thread_count contains the number
of live threads in the current inferior.

** New convenience variables $_hit_bpnum and $_hit_locno, set to
the breakpoint number and the breakpoint location number of
the breakpoint last hit.

** The "info breakpoints" now displays enabled breakpoint locations
of disabled breakpoints as in the "y-" state.

** The format of 'disassemble /r' and 'record instruction-history /r'
has changed to match the layout of GNU objdump when disassembling.

A new format "/b" has been introduce to provide the old behavior
of "/r".

** The TUI no longer styles the source and assembly code highlighted
by the current position indicator by default. You can however
re-enable styling using the new "set style tui-current-position"
command.

** It is now possible to use the "document" command to document
user-defined commands.

** Support for memory tag data for AArch64 MTE.

* Support Removal notices:

** DBX mode has been removed.

** Support for building against Python version 2 has been removed.
It is now only possible to build GDB against Python 3.

** Support for the following commands has been removed:

set debug aix-solib on|off
show debug aix-solib
set debug solib-frv on|off
show debug solib-frv

Use the "set/show debug solib" commands instead.

For a complete list and more details on each item, please see the gdb/NEWS
file, available at [1]:

[1]
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=gdb/NEWS;hb=gdb-13.1-release

Signed-off-by: Khem Raj
---
v2: Rebase on master
v3: Drop a clang-16 specific quirk, accidentally added
v4: Add patch to fix build with musl

meta/conf/distro/include/tcmode-default.inc | 2 +-
...ian_12.1.bb => gdb-cross-canadian_13.1.bb} | 0
.../{gdb-cross_12.1.bb => gdb-cross_13.1.bb} | 0
meta/recipes-devtools/gdb/gdb.inc | 22 +-
...make-man-install-relative-to-DESTDIR.patch | 28 -
...x-nat-Define-_ABIO32-if-not-defined.patch} | 9 ++---
...-pt_regs-uapi_pt_regs-on-GLIBC-syst.patch} | 11 ++---
...eadline.a-when-using-disable-static.patch} | 13

[OE-core] [PATCHv3] qemu: Fix building with 6.2 kernel headers

From: Joel Stanley 

When building native qemu with 6.2 kernel headers, qemu fails to build:

 In file included from /usr/include/linux/btrfs.h:29,
  from ../qemu-7.2.0/linux-user/syscall.c:165:
 /usr/include/linux/fs.h:50:8: error: redefinition of ‘struct file_clone_range’
50 | struct file_clone_range {
   |^~~~
 ../qemu-7.2.0/linux-user/syscall.c:129:8: note: originally defined here
   129 | struct file_clone_range {
   |^~~~

Backport changes to linux-user that remove the local copy of struct
file_clone_range.

Patches from 
https://lore.kernel.org/qemu-devel/20230110174901.2580297-1-berra...@redhat.com/

Signed-off-by: Joel Stanley 
Tested-by: Martin Jansa 
---
 meta/recipes-devtools/qemu/qemu.inc   |  2 +
 ...er-add-more-compat-ioctl-definitions.patch | 69 
 ...r-fix-compat-with-glibc-2.36-sys-mou.patch | 78 +++
 3 files changed, 149 insertions(+)
 create mode 100644 
meta/recipes-devtools/qemu/qemu/0001-Revert-linux-user-add-more-compat-ioctl-definitions.patch
 create mode 100644 
meta/recipes-devtools/qemu/qemu/0002-Revert-linux-user-fix-compat-with-glibc-2.36-sys-mou.patch

diff --git a/meta/recipes-devtools/qemu/qemu.inc 
b/meta/recipes-devtools/qemu/qemu.inc
index 92828e8f2d..1e768b560d 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -30,6 +30,8 @@ SRC_URI = "https://download.qemu.org/${BPN}-${PV}.tar.xz \
file://0001-contrib-vhost-user-blk-Replace-lseek64-with-lseek.patch 
\

file://0002-linux-user-Replace-use-of-lfs64-related-functions-an.patch \
file://0001-configure-Fix-check-tcg-not-executing-any-tests.patch \
+   
file://0001-Revert-linux-user-add-more-compat-ioctl-definitions.patch \
+   
file://0002-Revert-linux-user-fix-compat-with-glibc-2.36-sys-mou.patch \
"
 UPSTREAM_CHECK_REGEX = "qemu-(?P\d+(\.\d+)+)\.tar"
 
diff --git 
a/meta/recipes-devtools/qemu/qemu/0001-Revert-linux-user-add-more-compat-ioctl-definitions.patch
 
b/meta/recipes-devtools/qemu/qemu/0001-Revert-linux-user-add-more-compat-ioctl-definitions.patch
new file mode 100644
index 00..cd8121fed1
--- /dev/null
+++ 
b/meta/recipes-devtools/qemu/qemu/0001-Revert-linux-user-add-more-compat-ioctl-definitions.patch
@@ -0,0 +1,69 @@
+From afa96c55f2c270405de8984e2466067bbb44c0e4 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Daniel=20P=2E=20Berrang=C3=A9?= 
+Date: Tue, 10 Jan 2023 12:49:00 -0500
+Subject: [PATCH] Revert "linux-user: add more compat ioctl definitions"
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+This reverts commit c5495f4ecb0cdaaf2e9dddeb48f1689cdb520ca0.
+
+glibc has fixed (in 2.36.9000-40-g774058d729) the problem
+that caused a clash when both sys/mount.h annd linux/mount.h
+are included, and backported this to the 2.36 stable release
+too:
+
+  
https://sourceware.org/glibc/wiki/Release/2.36#Usage_of_.3Clinux.2Fmount.h.3E_and_.3Csys.2Fmount.h.3E
+
+It is saner for QEMU to remove the workaround it applied for
+glibc 2.36 and expect distros to ship the 2.36 maint release
+with the fix. This avoids needing to add a further workaround
+to QEMU to deal with the fact that linux/brtfs.h now also pulls
+in linux/mount.h via linux/fs.h since Linux 6.1
+
+Upstream-Status: Backport from v8.0 (master)
+
+Signed-off-by: Daniel P. Berrangé 
+Reviewed-by: Marc-André Lureau 
+Link: https://lore.kernel.org/r/20230110174901.2580297-2-berra...@redhat.com
+Signed-off-by: Joel Stanley 
+---
+ linux-user/syscall.c | 25 -
+ 1 file changed, 25 deletions(-)
+
+diff --git a/linux-user/syscall.c b/linux-user/syscall.c
+index f95a6161e..510de8edc 100644
+--- a/linux-user/syscall.c
 b/linux-user/syscall.c
+@@ -111,31 +111,6 @@
+ #define FS_IOC32_SETFLAGS  _IOW('f', 2, int)
+ #define FS_IOC32_GETVERSION_IOR('v', 1, int)
+ #define FS_IOC32_SETVERSION_IOW('v', 2, int)
+-
+-#define BLKGETSIZE64 _IOR(0x12,114,size_t)
+-#define BLKDISCARD _IO(0x12,119)
+-#define BLKIOMIN _IO(0x12,120)
+-#define BLKIOOPT _IO(0x12,121)
+-#define BLKALIGNOFF _IO(0x12,122)
+-#define BLKPBSZGET _IO(0x12,123)
+-#define BLKDISCARDZEROES _IO(0x12,124)
+-#define BLKSECDISCARD _IO(0x12,125)
+-#define BLKROTATIONAL _IO(0x12,126)
+-#define BLKZEROOUT _IO(0x12,127)
+-
+-#define FIBMAP _IO(0x00,1)
+-#define FIGETBSZ   _IO(0x00,2)
+-
+-struct file_clone_range {
+-__s64 src_fd;
+-__u64 src_offset;
+-__u64 src_length;
+-__u64 dest_offset;
+-};
+-
+-#define FICLONE _IOW(0x94, 9, int)
+-#define FICLONERANGE_IOW(0x94, 13, struct file_clone_range)
+-
+ #else
+ #include 
+ #endif
diff --git 
a/meta/recipes-devtools/qemu/qemu/0002-Revert-linux-user-fix-compat-with-glibc-2.36-sys-mou.patch
 
b/meta/recipes-devtools/qemu/qemu/0002-Revert-linux-user-fix-compat-with-glibc-2.36-sys-mou.patch
new file mode 100644

Re: [OE-core] [PATCHv2] qemu: Fix building with latest glibc 2.36

2023-02-22 Thread Joel Stanley

On Thu, 23 Feb 2023 at 00:11, Martin Jansa  wrote:
>
> On Thu, Feb 23, 2023 at 1:08 AM Joel Stanley  wrote:
>>
>> On Wed, 22 Feb 2023 at 15:28, Martin Jansa  wrote:
>> >
>> > Hi,
>> >
>> > I've seen this build issue on my gentoo builder today with qemu-native, so 
>> > I've removed the stray cross.patch and sent v2.
>> >
>> > Then RP had good question how to reproduce this failure and I've checked 
>> > when I've updated glibc in gentoo for last time and it was a month ago 
>> > (and I've rebuilt qemu-native few time since then).
>> >
>> > So in the end it was linux-libc-headers upgrade to 6.2 from yesterday 
>> > (sys-kernel/linux-headers-6.2 in gentoo) which caused this for me (if I 
>> > downgrade to 6.1 I can build qemu-native again even without this patch).
>> >
>> > Joel: Should I send v3 with updated commit message or will you do it?
>>
>> Thanks for picking this one up. Please continue the good work.
>
>
> Can you confirm if it was related to glibc upgrade for you or it might be 
> kernel headers like for me and it just looked like glibc related?

I pointed the fingers at glibc because of the comments in the qemu
revert, but you're probably on the money with kernel headers as
/usr/include/linux/fs.h comes from the kernel.

I run Debian testing so while I'm not sure what I changed when, I
would have upgraded the kernel headers recently.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177594): 
https://lists.openembedded.org/g/openembedded-core/message/177594
Mute This Topic: https://lists.openembedded.org/mt/97161162/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] [PATCHv2] qemu: Fix building with latest glibc 2.36

2023-02-22 Thread Alexandre Belloni via lists.openembedded.org

On Thu, Feb 23, 2023 at 1:08 AM Joel Stanley  wrote:

> On Wed, 22 Feb 2023 at 15:28, Martin Jansa  wrote:
> >
> > Hi,
> >
> > I've seen this build issue on my gentoo builder today with qemu-native,
> so I've removed the stray cross.patch and sent v2.
> >
> > Then RP had good question how to reproduce this failure and I've checked
> when I've updated glibc in gentoo for last time and it was a month ago (and
> I've rebuilt qemu-native few time since then).
> >
> > So in the end it was linux-libc-headers upgrade to 6.2 from yesterday
> (sys-kernel/linux-headers-6.2 in gentoo) which caused this for me (if I
> downgrade to 6.1 I can build qemu-native again even without this patch).
> >
> > Joel: Should I send v3 with updated commit message or will you do it?
>
> Thanks for picking this one up. Please continue the good work.
>

Can you confirm if it was related to glibc upgrade for you or it might be
kernel headers like for me and it just looked like glibc related?

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177593): 
https://lists.openembedded.org/g/openembedded-core/message/177593
Mute This Topic: https://lists.openembedded.org/mt/97161162/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] [PATCHv2] qemu: Fix building with latest glibc 2.36

2023-02-22 Thread Joel Stanley

On Wed, 22 Feb 2023 at 15:28, Martin Jansa  wrote:
>
> Hi,
>
> I've seen this build issue on my gentoo builder today with qemu-native, so 
> I've removed the stray cross.patch and sent v2.
>
> Then RP had good question how to reproduce this failure and I've checked when 
> I've updated glibc in gentoo for last time and it was a month ago (and I've 
> rebuilt qemu-native few time since then).
>
> So in the end it was linux-libc-headers upgrade to 6.2 from yesterday 
> (sys-kernel/linux-headers-6.2 in gentoo) which caused this for me (if I 
> downgrade to 6.1 I can build qemu-native again even without this patch).
>
> Joel: Should I send v3 with updated commit message or will you do it?

Thanks for picking this one up. Please continue the good work.

Cheers,

Joel

>
> Regards,
>
> On Wed, Feb 22, 2023 at 4:00 PM Martin Jansa via lists.openembedded.org 
>  wrote:
>>
>> From: Joel Stanley 
>>
>> When building native qemu with glibc 2.36 (including latest changes from
>> the glibc stable branch), qemu fails to build:
>>
>>  In file included from /usr/include/linux/btrfs.h:29,
>>   from ../qemu-7.2.0/linux-user/syscall.c:165:
>>  /usr/include/linux/fs.h:50:8: error: redefinition of ‘struct 
>> file_clone_range’
>> 50 | struct file_clone_range {
>>|^~~~
>>  ../qemu-7.2.0/linux-user/syscall.c:129:8: note: originally defined here
>>129 | struct file_clone_range {
>>|^~~~
>>
>> Backport changes to linux-user that remove the local copy of struct
>> file_clone_range.
>>
>> Patches from 
>> https://lore.kernel.org/qemu-devel/20230110174901.2580297-1-berra...@redhat.com/
>>
>> Signed-off-by: Joel Stanley 
>> Tested-by: Martin Jansa 
>> ---
>>  meta/recipes-devtools/qemu/qemu.inc   |  2 +
>>  ...er-add-more-compat-ioctl-definitions.patch | 69 
>>  ...r-fix-compat-with-glibc-2.36-sys-mou.patch | 78 +++
>>  3 files changed, 149 insertions(+)
>>  create mode 100644 
>> meta/recipes-devtools/qemu/qemu/0001-Revert-linux-user-add-more-compat-ioctl-definitions.patch
>>  create mode 100644 
>> meta/recipes-devtools/qemu/qemu/0002-Revert-linux-user-fix-compat-with-glibc-2.36-sys-mou.patch
>>
>> diff --git a/meta/recipes-devtools/qemu/qemu.inc 
>> b/meta/recipes-devtools/qemu/qemu.inc
>> index 92828e8f2d..1e768b560d 100644
>> --- a/meta/recipes-devtools/qemu/qemu.inc
>> +++ b/meta/recipes-devtools/qemu/qemu.inc
>> @@ -30,6 +30,8 @@ SRC_URI = "https://download.qemu.org/${BPN}-${PV}.tar.xz \
>> 
>> file://0001-contrib-vhost-user-blk-Replace-lseek64-with-lseek.patch \
>> 
>> file://0002-linux-user-Replace-use-of-lfs64-related-functions-an.patch \
>> 
>> file://0001-configure-Fix-check-tcg-not-executing-any-tests.patch \
>> +   
>> file://0001-Revert-linux-user-add-more-compat-ioctl-definitions.patch \
>> +   
>> file://0002-Revert-linux-user-fix-compat-with-glibc-2.36-sys-mou.patch \
>> "
>>  UPSTREAM_CHECK_REGEX = "qemu-(?P\d+(\.\d+)+)\.tar"
>>
>> diff --git 
>> a/meta/recipes-devtools/qemu/qemu/0001-Revert-linux-user-add-more-compat-ioctl-definitions.patch
>>  
>> b/meta/recipes-devtools/qemu/qemu/0001-Revert-linux-user-add-more-compat-ioctl-definitions.patch
>> new file mode 100644
>> index 00..cd8121fed1
>> --- /dev/null
>> +++ 
>> b/meta/recipes-devtools/qemu/qemu/0001-Revert-linux-user-add-more-compat-ioctl-definitions.patch
>> @@ -0,0 +1,69 @@
>> +From afa96c55f2c270405de8984e2466067bbb44c0e4 Mon Sep 17 00:00:00 2001
>> +From: =?UTF-8?q?Daniel=20P=2E=20Berrang=C3=A9?= 
>> +Date: Tue, 10 Jan 2023 12:49:00 -0500
>> +Subject: [PATCH] Revert "linux-user: add more compat ioctl definitions"
>> +MIME-Version: 1.0
>> +Content-Type: text/plain; charset=UTF-8
>> +Content-Transfer-Encoding: 8bit
>> +
>> +This reverts commit c5495f4ecb0cdaaf2e9dddeb48f1689cdb520ca0.
>> +
>> +glibc has fixed (in 2.36.9000-40-g774058d729) the problem
>> +that caused a clash when both sys/mount.h annd linux/mount.h
>> +are included, and backported this to the 2.36 stable release
>> +too:
>> +
>> +  
>> https://sourceware.org/glibc/wiki/Release/2.36#Usage_of_.3Clinux.2Fmount.h.3E_and_.3Csys.2Fmount.h.3E
>> +
>> +It is saner for QEMU to remove the workaround it applied for
>> +glibc 2.36 and expect distros to ship the 2.36 maint release
>> +with the fix. This avoids needing to add a further workaround
>> +to QEMU to deal with the fact that linux/brtfs.h now also pulls
>> +in linux/mount.h via linux/fs.h since Linux 6.1
>> +
>> +Upstream-Status: Backport from v8.0 (master)
>> +
>> +Signed-off-by: Daniel P. Berrangé 
>> +Reviewed-by: Marc-André Lureau 
>> +Link: https://lore.kernel.org/r/20230110174901.2580297-2-berra...@redhat.com
>> +Signed-off-by: Joel Stanley 
>> +---
>> + linux-user/syscall.c | 25 -
>> + 1 file changed, 25 deletions(-)
>> +
>> +diff --git a/linux-user/syscall.c b/linux-user/syscall.c
>> +index f95a6161e..510de8edc 100644
>>

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


x32 also failed:

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

On 23/02/2023 00:42:17+0100, Alexandre Belloni wrote:
> This fails on musl:
> 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/6703/steps/11/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/6722/steps/12/logs/stdio
> 
> On 22/02/2023 12:48:47+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 and remove unneeded patch
> > 
> > Signed-off-by: Markus Volk 
> > ---
> >  ...EXITCODE-macro-for-non-glibc-systems.patch | 42 ---
> >  .../vte/{vte_0.70.2.bb => vte_0.70.3.bb}  | 23 +-
> >  2 files changed, 11 insertions(+), 54 deletions(-)
> >  delete mode 100644 
> > meta/recipes-support/vte/vte/0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch
> >  rename meta/recipes-support/vte/{vte_0.70.2.bb => vte_0.70.3.bb} (69%)
> > 
> > diff --git 
> > a/meta/recipes-support/vte/vte/0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch
> >  
> > b/meta/recipes-support/vte/vte/0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch
> > deleted file mode 100644
> > index b4100fc381..00
> > --- 
> > a/meta/recipes-support/vte/vte/0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch
> > +++ /dev/null
> > @@ -1,42 +0,0 @@
> > -From de9639baac792327c701e509258b8a13f6959e82 Mon Sep 17 00:00:00 2001
> > -From: Danilo Spinella 
> > -Date: Thu, 21 Mar 2019 14:19:26 +0100
> > -Subject: [PATCH] Add W_EXITCODE macro for non-glibc systems
> > -MIME-Version: 1.0
> > -Content-Type: text/plain; charset=UTF-8
> > -Content-Transfer-Encoding: 8bit
> > -
> > -Upstream-Status: Submitted [1]
> > -
> > -Signed-off-by: Andreas Müller 
> > -
> > -[1] https://gitlab.gnome.org/GNOME/vte/issues/72
> > -
> > 
> > - src/missing.hh | 4 
> > - src/widget.cc  | 1 +
> > - 2 files changed, 5 insertions(+)
> > -
> >  a/src/missing.hh
> > -+++ b/src/missing.hh
> > -@@ -24,6 +24,10 @@
> > - #define NSIG (8 * sizeof(sigset_t))
> > - #endif
> > - 
> > -+#ifndef W_EXITCODE
> > -+#define W_EXITCODE(ret, sig) ((ret) << 8 | (sig))
> > -+#endif
> > -+
> > - #ifndef HAVE_FDWALK
> > - int fdwalk(int (*cb)(void* data, int fd),
> > -void* data);
> >  a/src/widget.cc
> > -+++ b/src/widget.cc
> > -@@ -21,6 +21,7 @@
> > - #include "widget.hh"
> > - 
> > - #include  // for W_EXITCODE
> > -+#include "missing.hh" // for W_EXITCODE on non-glibc systems
> > - 
> > - #include 
> > - #include 
> > 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..73b4666efc 100644
> > --- a/meta/recipes-support/vte/vte_0.70.2.bb
> > +++ b/meta/recipes-support/vte/vte_0.70.3.bb
> > @@ -11,34 +11,33 @@ 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"
> >

Re: [OE-core] [PATCH v3] gdb: Upgrade to 13.1

2023-02-22 Thread Alexandre Belloni via lists.openembedded.org

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


On 22/02/2023 08:53:58-0800, Khem Raj wrote:
> Pass -Wno-enum-constexpr-conversion with clang
> 
> GDB 13.1 includes the following changes and enhancements:
> 
> * Support for the following new targets has been added in both
>   GDB and GDBserver:
> 
>   ** GNU/Linux/LoongArch (gdbserver) loongarch*-*-linux*
> 
>   ** GNU/Linux/CSKY (gdbserver) csky*-*linux*
> 
> * The Windows native target now supports target async.
> 
> * FreeBSD:
> 
>   ** Arm and AArch64: Support for Thread Local Storage (TLS) variables
> 
>   ** Hardware watchpoint support on AArch64 FreeBSD
> 
> * Floating-point support has now been added on LoongArch GNU/Linux.
> 
> * New commands:
> 
>  ** set print nibbles [on|off]
> show print nibbles
> 
> This controls whether the 'print/t' command will display binary values
> in groups of four bits, known as "nibbles".  The default is 'off'.
> 
>  ** Various styling-related commands. See the gdb/NEWS file for more
> details (see link at the bottom).
> 
>  ** Various maintenance commands.  These are normally aimed at GDB
> experts or developers. See the gdb/NEWS file for more details
> (see link at the bottom).
> 
> * Python API improvements:
> 
>  ** New Python API for instruction disassembly.
> The new attribute 'locations' of gdb.Breakpoint returns a list of
> gdb.BreakpointLocation objects specifying the locations where the
> breakpoint is inserted into the debuggee.
> 
>  ** New Python type gdb.BreakpointLocation.
> 
>  ** New function gdb.format_address(ADDRESS, PROGSPACE, ARCHITECTURE)
> that formats ADDRESS as 'address '
> 
>  ** New function gdb.current_language that returns the name of the
> current language.  Unlike gdb.parameter('language'), this will
> never return 'auto'.
> 
>  ** New function gdb.print_options that returns a dictionary of the
> prevailing print options, in the form accepted by gdb.Value.format_string.
> 
>  ** New method gdb.Frame.language that returns the name of the
> frame's language.
> 
>  ** gdb.Value.format_string now uses the format provided by 'print',
> if it is called during a 'print' or other similar operation.
> 
>  ** gdb.Value.format_string now accepts the 'summary' keyword.  This
> can be used to request a shorter representation of a value, the
> way that 'set print frame-arguments scalars' does.
> 
>  ** The gdb.register_window_type method now restricts the set of
> acceptable window names.  The first character of a window's name
> must start with a character in the set [a-zA-Z], every subsequent
> character of a window's name must be in the set [-_.a-zA-Z0-9].
> 
> * GDB/MI changes:
> 
>   ** MI version 1 is deprecated, and will be removed in GDB 14.
> 
>   ** The async record stating the stopped reason 'breakpoint-hit' now
>  contains an optional field locno.
> 
> * Miscellaneous improvements:
> 
>   ** gdb now supports zstd compressed debug sections (ELFCOMPRESS_ZSTD) for 
> ELF.
> 
>   ** New convenience variable $_inferior_thread_count contains the number
>  of live threads in the current inferior.
> 
>   ** New convenience variables $_hit_bpnum and $_hit_locno, set to
>  the breakpoint number and the breakpoint location number of
>  the breakpoint last hit.
> 
>   ** The "info breakpoints" now displays enabled breakpoint locations
>  of disabled breakpoints as in the "y-" state.
> 
>   ** The format of 'disassemble /r' and 'record instruction-history /r'
>  has changed to match the layout of GNU objdump when disassembling.
> 
>  A new format "/b" has been introduce to provide the old behavior
>  of "/r".
> 
>   ** The TUI no longer styles the source and assembly code highlighted
>  by the current position indicator by default. You can however
>  re-enable styling using the new "set style tui-current-position"
>

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

2023-02-22 Thread Alexandre Belloni via lists.openembedded.org

This fails on musl:

https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/6703/steps/11/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/6722/steps/12/logs/stdio

On 22/02/2023 12:48:47+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 and remove unneeded patch
> 
> Signed-off-by: Markus Volk 
> ---
>  ...EXITCODE-macro-for-non-glibc-systems.patch | 42 ---
>  .../vte/{vte_0.70.2.bb => vte_0.70.3.bb}  | 23 +-
>  2 files changed, 11 insertions(+), 54 deletions(-)
>  delete mode 100644 
> meta/recipes-support/vte/vte/0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch
>  rename meta/recipes-support/vte/{vte_0.70.2.bb => vte_0.70.3.bb} (69%)
> 
> diff --git 
> a/meta/recipes-support/vte/vte/0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch
>  
> b/meta/recipes-support/vte/vte/0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch
> deleted file mode 100644
> index b4100fc381..00
> --- 
> a/meta/recipes-support/vte/vte/0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch
> +++ /dev/null
> @@ -1,42 +0,0 @@
> -From de9639baac792327c701e509258b8a13f6959e82 Mon Sep 17 00:00:00 2001
> -From: Danilo Spinella 
> -Date: Thu, 21 Mar 2019 14:19:26 +0100
> -Subject: [PATCH] Add W_EXITCODE macro for non-glibc systems
> -MIME-Version: 1.0
> -Content-Type: text/plain; charset=UTF-8
> -Content-Transfer-Encoding: 8bit
> -
> -Upstream-Status: Submitted [1]
> -
> -Signed-off-by: Andreas Müller 
> -
> -[1] https://gitlab.gnome.org/GNOME/vte/issues/72
> -
> 
> - src/missing.hh | 4 
> - src/widget.cc  | 1 +
> - 2 files changed, 5 insertions(+)
> -
>  a/src/missing.hh
> -+++ b/src/missing.hh
> -@@ -24,6 +24,10 @@
> - #define NSIG (8 * sizeof(sigset_t))
> - #endif
> - 
> -+#ifndef W_EXITCODE
> -+#define W_EXITCODE(ret, sig) ((ret) << 8 | (sig))
> -+#endif
> -+
> - #ifndef HAVE_FDWALK
> - int fdwalk(int (*cb)(void* data, int fd),
> -void* data);
>  a/src/widget.cc
> -+++ b/src/widget.cc
> -@@ -21,6 +21,7 @@
> - #include "widget.hh"
> - 
> - #include  // for W_EXITCODE
> -+#include "missing.hh" // for W_EXITCODE on non-glibc systems
> - 
> - #include 
> - #include 
> 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..73b4666efc 100644
> --- a/meta/recipes-support/vte/vte_0.70.2.bb
> +++ b/meta/recipes-support/vte/vte_0.70.3.bb
> @@ -11,34 +11,33 @@ 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 (#177589): 
https://lists.openembedded.org/g/openembedded-core/message/177589
Mute This Topic:

Re: [OE-core] [PATCH] kernel-arch.bbclass: Map arm64 to arm

2023-02-22 Thread Pavel Zhukov


Alexandre Belloni  writes:

> Hello,
>
> This is the cause of:
Hi Alex,
Yes, my fault, sorry about that.
Arm64 is valid U-boot/mkimage architecture. Proper fix sent as:
"[PATCH] u-boot: Map arm64 into map for u-boot dts installation"

This patch can be dropped. 

>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/995/steps/14/logs/stdio
>
> 2023-02-22 11:33:00,834 - oe-selftest - INFO - 
> fitimage.FitImageTests.test_fit_image (subunit.RemotedTestCase)
> 2023-02-22 11:33:00,835 - oe-selftest - INFO -  ... FAIL
>
> |   OBJCOPY arch/arm64/boot/Image
> | NOTE: make -j 16 -l 52 CC=aarch64-poky-linux-gcc -fuse-ld=bfd
> | 
> -fmacro-prefix-map=/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work-shared/qemuarm64/kernel-source=/usr/src/debug/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0
> | 
> -fdebug-prefix-map=/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work-shared/qemuarm64/kernel-source=/usr/src/debug/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0
> | 
> -fmacro-prefix-map=/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/linux-qemuarm64-standard-build=/usr/src/debug/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0
> | 
> -fdebug-prefix-map=/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/linux-qemuarm64-standard-build=/usr/src/debug/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0
> | 
> -fdebug-prefix-map=/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/recipe-sysroot=
> | 
> -fmacro-prefix-map=/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/recipe-sysroot=
> | 
> -fdebug-prefix-map=/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/recipe-sysroot-native=
> | 
> -fdebug-prefix-map=/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work-shared/qemuarm64/kernel-source=/usr/src/kernel
> | 
> -fdebug-prefix-map=/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work-shared/qemuarm64/kernel-build-artifacts=/usr/src/kernel
> | 
> --sysroot=/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/recipe-sysroot
> | LD=aarch64-poky-linux-ld.bfd
> | 
> --sysroot=/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/recipe-sysroot
> | HOSTCC=gcc
> | 
> HOSTCFLAGS=-isystem/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/recipe-sysroot-native/usr/include
> | -O2 -pipe
> | 
> HOSTLDFLAGS=-L/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/recipe-sysroot-native/usr/lib
> | 
> -L/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/recipe-sysroot-native/lib
> | -Wl,--enable-new-dtags
> | 
> -Wl,-rpath-link,/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/recipe-sysroot-native/usr/lib
> | 
> -Wl,-rpath-link,/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/recipe-sysroot-native/lib
> | 
> -Wl,-rpath,/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/recipe-sysroot-native/usr/lib
> | 
> -Wl,-rpath,/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/recipe-sysroot-native/lib
> | -Wl,-O1 -Wl,--allow-shlib-undefined
> | 
> -Wl,--dynamic-linker=/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/sysroots-uninative/aarch64-linux/lib/ld-linux-aarch64.so.1
> | HOSTCP
> =gcc -E HOSTCXX=g++
> HOSTCXXFLAGS=-isystem/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/recipe-sysroot-native/usr/include
> -O2 -pipe PAHOLE=false zImage
> | make: *** No rule to make target 'zImage'.  Stop.
> | ERROR: oe_runmake failed

[OE-core] [PATCH] u-boot: Map arm64 into map for u-boot dts installation

2023-02-22 Thread Pavel Zhukov

While arm64 is a valid UBOOT_ARCH (according to mkimage -A) u-boot
keeps arm64 specific dts under 'arch/arm' directory.
As the result the recipe tries to install arch/arm64 (if UBOOT_DTB
was specified) and fails with [1]. Remapping "arm64" to "arm" to fix this
issue.

[1]
| install: cannot stat 
'.../u-boot/1_2023.01-r0/build/arch/arm64/dts/u-boot.dtb': No such file or 
directory

Signed-off-by: Pavel Zhukov 
---
 meta/recipes-bsp/u-boot/u-boot.inc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-bsp/u-boot/u-boot.inc 
b/meta/recipes-bsp/u-boot/u-boot.inc
index 4636dd733b..b3482dcef3 100644
--- a/meta/recipes-bsp/u-boot/u-boot.inc
+++ b/meta/recipes-bsp/u-boot/u-boot.inc
@@ -32,7 +32,7 @@ do_savedefconfig() {
 }
 do_savedefconfig[nostamp] = "1"
 addtask savedefconfig after do_configure
-
+UBOOT_ARCH_DIR = "${@'arm' if d.getVar('UBOOT_ARCH').startswith('arm') else 
d.getVar('UBOOT_ARCH')}"
 do_compile () {
 if [ "${@bb.utils.filter('DISTRO_FEATURES', 'ld-is-gold', d)}" ]; then
 sed -i 's/$(CROSS_COMPILE)ld$/$(CROSS_COMPILE)ld.bfd/g' ${S}/config.mk
@@ -334,7 +334,7 @@ do_deploy () {
 
 if [ -n "${UBOOT_DTB}" ]
 then
-install -m 644 ${B}/arch/${UBOOT_ARCH}/dts/${UBOOT_DTB_BINARY} 
${DEPLOYDIR}/
+install -m 644 ${B}/arch/${UBOOT_ARCH_DIR}/dts/${UBOOT_DTB_BINARY} 
${DEPLOYDIR}/
 fi
 }
 
-- 
2.39.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177587): 
https://lists.openembedded.org/g/openembedded-core/message/177587
Mute This Topic: https://lists.openembedded.org/mt/97170621/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] sstate cache management

2023-02-22 Thread Alex Kiernan

On Wed, Feb 22, 2023 at 8:33 PM Richard Purdie
 wrote:
>
> On Wed, 2023-02-22 at 17:56 +, Alex Kiernan wrote:
> > I needed to do something about our shared sstate store and waded into
> > the sstate cache management problem as the existing script takes hours
> > to run over NFS (which for better or worse is where ours is). I've set
> > myself the problem of replacing the existing script with something
> > more extensible, understandable and performant.
> >
> > I've got something which I believed was roughly right, but I'm ending
> > up with questions I can't answer when comparing the two outputs...
> >
> > If I run the existing shell script against a tiny sstate-cache (on my
> > laptop) I get 420 duplicate files eligible for removal, if I run my
> > script I get 491, looking into the delta, I pick out things like
> > these:
> >
> > $ find sstate-cache/ -name
> > sstate:libcap-ng:core2-64-poky-linux:0.8.3:r0:core2-64:10:*_populate_sysroot.tar.zst*
> > -ls
> > 49067 16 -rw-r--r--   1 alexkalexk   14435 Feb 18
> > 15:29 
> > sstate-cache/25/59/sstate:libcap-ng:core2-64-poky-linux:0.8.3:r0:core2-64:10:2559429e2a553085bc657f3d2a21a111818061448e5fa2aa16398afb5dad8b90_populate_sysroot.tar.zst
> > 49129 16 -rw-r--r--   1 alexkalexk   15205 Feb 18
> > 15:29 
> > sstate-cache/25/59/sstate:libcap-ng:core2-64-poky-linux:0.8.3:r0:core2-64:10:2559429e2a553085bc657f3d2a21a111818061448e5fa2aa16398afb5dad8b90_populate_sysroot.tar.zst.siginfo
> >   2490392 16 -rw-r--r--   1 alexkalexk   15204 Feb 20
> > 13:24 
> > sstate-cache/bf/08/sstate:libcap-ng:core2-64-poky-linux:0.8.3:r0:core2-64:10:bf08f26e6bc5ab56ed128441fb05edeef41aa881330d04eea127a93ede51713d_populate_sysroot.tar.zst.siginfo
> >339439 16 -rw-r--r--   1 alexkalexk   14423 Feb 20
> > 13:24 
> > sstate-cache/bf/08/sstate:libcap-ng:core2-64-poky-linux:0.8.3:r0:core2-64:10:bf08f26e6bc5ab56ed128441fb05edeef41aa881330d04eea127a93ede51713d_populate_sysroot.tar.zst
> >
> > Which look to me like I should be able to delete the older ones, or am
> > I missing something? Trying to follow what the existing script is
> > supposed to do is challenging!
>
> I'd say delete the older one but it does depend a lot on what you're
> building against the cache (e.g. multiple releases). The system is
> meant to touch files it uses and the autobuilder just ages out things
> not touched for X time where X has varied depending on the pressure on
> our NAS.
>

Thanks, so seems like the existing script not spotting that those
could be removed (using `-d`) is just a bug?

-- 
Alex Kiernan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177586): 
https://lists.openembedded.org/g/openembedded-core/message/177586
Mute This Topic: https://lists.openembedded.org/mt/97165650/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 08/11] build-appliance-image: use a real /tmp

2023-02-22 Thread Trevor Woerner

On Wed 2023-02-22 @ 02:46:30 PM, Richard Purdie wrote:
> On Tue, 2023-02-21 at 21:25 -0500, Trevor Woerner wrote:
> > On Tue 2023-02-21 @ 03:44:42 PM, Trevor Woerner via lists.openembedded.org 
> > wrote:
> > > Make /tmp a real directory in the root filesystem and not a link to an
> > > in-memory tmpfs. Otherwise bitbake will run out of inodes on /tmp very 
> > > quickly
> > > and stop any build.
> > > 
> > > Signed-off-by: Trevor Woerner 
> > > ---
> > >  meta/recipes-core/images/build-appliance-image_15.0.0.bb | 6 ++
> > >  1 file changed, 6 insertions(+)
> > > 
> > > diff --git a/meta/recipes-core/images/build-appliance-image_15.0.0.bb 
> > > b/meta/recipes-core/images/build-appliance-image_15.0.0.bb
> > > index 3a84de0a2b43..1f7b96a9fcf4 100644
> > > --- a/meta/recipes-core/images/build-appliance-image_15.0.0.bb
> > > +++ b/meta/recipes-core/images/build-appliance-image_15.0.0.bb
> > > @@ -113,6 +113,12 @@ fakeroot do_tweak_image () {
> > >   # add a /lib64 symlink
> > >   # this is needed for building rust-native on a 64-bit build appliance
> > >   ln -rs ${IMAGE_ROOTFS}/lib ${IMAGE_ROOTFS}/lib64
> > > +
> > > + # make /tmp a real directory and not a link to an in-memory tmpfs
> > > + # otherwise /tmp will run out of inodes very quickly when bitbaking
> > > + sed -i -e 's#l root root 1777 /tmp /var/tmp#d root root 1777 /tmp 
> > > none#' ${IMAGE_ROOTFS}/etc/default/volatiles/00_core
> > > + mkdir -p ${IMAGE_ROOTFS}/tmp
> > > + chmod 1777 ${IMAGE_ROOTFS}/tmp
> > >  }
> > 
> > Richard, this feels rather "hacky" to me. I can't help wonder if it would be
> > better to implement a VOLATILE_TMP_DIR mechanism (along the same lines as
> > VOLATILE_LOG_DIR)?
> > 
> > https://docs.yoctoproject.org/dev/ref-manual/variables.html?highlight=volatile_log_dir#term-VOLATILE_LOG_DIR
> > https://git.openembedded.org/openembedded-core/tree/meta/recipes-core/initscripts/initscripts_1.0.bb#n107
> 
> When I saw this, I was wondering about that too...
> 
> I think I'll hold off this patch whilst we think about that a bit but
> my memory on this area is taking a bit of paging back in.

Sounds good. In that case I'll wait for the others to hit master then re-work
this patch to integrate a VOLATILE_TMP_DIR mechanism?

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177585): 
https://lists.openembedded.org/g/openembedded-core/message/177585
Mute This Topic: https://lists.openembedded.org/mt/97151865/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] sstate cache management

2023-02-22 Thread Richard Purdie

On Wed, 2023-02-22 at 17:56 +, Alex Kiernan wrote:
> I needed to do something about our shared sstate store and waded into
> the sstate cache management problem as the existing script takes hours
> to run over NFS (which for better or worse is where ours is). I've set
> myself the problem of replacing the existing script with something
> more extensible, understandable and performant.
> 
> I've got something which I believed was roughly right, but I'm ending
> up with questions I can't answer when comparing the two outputs...
> 
> If I run the existing shell script against a tiny sstate-cache (on my
> laptop) I get 420 duplicate files eligible for removal, if I run my
> script I get 491, looking into the delta, I pick out things like
> these:
> 
> $ find sstate-cache/ -name
> sstate:libcap-ng:core2-64-poky-linux:0.8.3:r0:core2-64:10:*_populate_sysroot.tar.zst*
> -ls
> 49067 16 -rw-r--r--   1 alexkalexk   14435 Feb 18
> 15:29 
> sstate-cache/25/59/sstate:libcap-ng:core2-64-poky-linux:0.8.3:r0:core2-64:10:2559429e2a553085bc657f3d2a21a111818061448e5fa2aa16398afb5dad8b90_populate_sysroot.tar.zst
> 49129 16 -rw-r--r--   1 alexkalexk   15205 Feb 18
> 15:29 
> sstate-cache/25/59/sstate:libcap-ng:core2-64-poky-linux:0.8.3:r0:core2-64:10:2559429e2a553085bc657f3d2a21a111818061448e5fa2aa16398afb5dad8b90_populate_sysroot.tar.zst.siginfo
>   2490392 16 -rw-r--r--   1 alexkalexk   15204 Feb 20
> 13:24 
> sstate-cache/bf/08/sstate:libcap-ng:core2-64-poky-linux:0.8.3:r0:core2-64:10:bf08f26e6bc5ab56ed128441fb05edeef41aa881330d04eea127a93ede51713d_populate_sysroot.tar.zst.siginfo
>339439 16 -rw-r--r--   1 alexkalexk   14423 Feb 20
> 13:24 
> sstate-cache/bf/08/sstate:libcap-ng:core2-64-poky-linux:0.8.3:r0:core2-64:10:bf08f26e6bc5ab56ed128441fb05edeef41aa881330d04eea127a93ede51713d_populate_sysroot.tar.zst
> 
> Which look to me like I should be able to delete the older ones, or am
> I missing something? Trying to follow what the existing script is
> supposed to do is challenging!

I'd say delete the older one but it does depend a lot on what you're
building against the cache (e.g. multiple releases). The system is
meant to touch files it uses and the autobuilder just ages out things
not touched for X time where X has varied depending on the pressure on
our NAS.

Cheers,

Richard




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177584): 
https://lists.openembedded.org/g/openembedded-core/message/177584
Mute This Topic: https://lists.openembedded.org/mt/97165650/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] sstate cache management

2023-02-22 Thread Alex Kiernan

On Wed, Feb 22, 2023 at 7:36 PM Alexandre Belloni
 wrote:
>
> Hello,
>
> This doesn't answer your question but did you look into
> https://lore.kernel.org/all/2022112102.5556-1-tomasz.dziendziel...@gmail.com/?
>

Thanks, yeah, I did... it really didn't scratch the particular itch I
had, mostly because I want to stuff other things in there. It feels a
bit like I'm rejecting it based on "not invented here", likely I just
need to get to a place where I can post what I have!

> On 22/02/2023 17:56:35+, Alex Kiernan wrote:
> > I needed to do something about our shared sstate store and waded into
> > the sstate cache management problem as the existing script takes hours
> > to run over NFS (which for better or worse is where ours is). I've set
> > myself the problem of replacing the existing script with something
> > more extensible, understandable and performant.
> >
> > I've got something which I believed was roughly right, but I'm ending
> > up with questions I can't answer when comparing the two outputs...
> >
> > If I run the existing shell script against a tiny sstate-cache (on my
> > laptop) I get 420 duplicate files eligible for removal, if I run my
> > script I get 491, looking into the delta, I pick out things like
> > these:
> >
> > $ find sstate-cache/ -name
> > sstate:libcap-ng:core2-64-poky-linux:0.8.3:r0:core2-64:10:*_populate_sysroot.tar.zst*
> > -ls
> > 49067 16 -rw-r--r--   1 alexkalexk   14435 Feb 18
> > 15:29 
> > sstate-cache/25/59/sstate:libcap-ng:core2-64-poky-linux:0.8.3:r0:core2-64:10:2559429e2a553085bc657f3d2a21a111818061448e5fa2aa16398afb5dad8b90_populate_sysroot.tar.zst
> > 49129 16 -rw-r--r--   1 alexkalexk   15205 Feb 18
> > 15:29 
> > sstate-cache/25/59/sstate:libcap-ng:core2-64-poky-linux:0.8.3:r0:core2-64:10:2559429e2a553085bc657f3d2a21a111818061448e5fa2aa16398afb5dad8b90_populate_sysroot.tar.zst.siginfo
> >   2490392 16 -rw-r--r--   1 alexkalexk   15204 Feb 20
> > 13:24 
> > sstate-cache/bf/08/sstate:libcap-ng:core2-64-poky-linux:0.8.3:r0:core2-64:10:bf08f26e6bc5ab56ed128441fb05edeef41aa881330d04eea127a93ede51713d_populate_sysroot.tar.zst.siginfo
> >339439 16 -rw-r--r--   1 alexkalexk   14423 Feb 20
> > 13:24 
> > sstate-cache/bf/08/sstate:libcap-ng:core2-64-poky-linux:0.8.3:r0:core2-64:10:bf08f26e6bc5ab56ed128441fb05edeef41aa881330d04eea127a93ede51713d_populate_sysroot.tar.zst
> >
> > Which look to me like I should be able to delete the older ones, or am
> > I missing something? Trying to follow what the existing script is
> > supposed to do is challenging!
> >
> > --
> > Alex Kiernan
>
> >
> > 
> >
>
>
> --
> Alexandre Belloni, co-owner and COO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com



-- 
Alex Kiernan

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

Re: [OE-core] Yocto reproducibilty issue :: rust-llvm binary differences

2023-02-22 Thread Alexandre Belloni via lists.openembedded.org

On Wed, Feb 22, 2023 at 3:10 AM Alexander Kanavin
 wrote:
>
> I took a look at libRemarks.so and libLTO.so. If you run 'objdump -s'
> on them, you'll see that they differ only in 'gnu.build-id' property,
> and are otherwise identical. So you need to look into why the id is
> different, I don't remember right now how it is created. Probably the
> compile log can give a clue.
>
> You can also confirm that it is indeed these two files that cause
> divergence in target rust by for example copying them from the A build
> into the B build just prior to building rust.

gnu.build-id in output means its using --build-id option during link so it will
be good to find out how this option is being constructed during link, usually
its SHA1 hash on parts of the output contents, so if these contents are
same then it should always come out to be same but it could be something
is changing in two cases perhaps some paths etc.

>
> Alex
>
> On Wed, 22 Feb 2023 at 04:58, Sundeep KOKKONDA
>  wrote:
> >
> > Hello Alex,
> >
> > files are here... https://we.tl/t-ijJJZnBvKh
> >
> >
> >
> > Thanks,
> > Sundeep K.
> >
> >
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177582): 
https://lists.openembedded.org/g/openembedded-core/message/177582
Mute This Topic: https://lists.openembedded.org/mt/97113152/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] sstate cache management

Hello,

This doesn't answer your question but did you look into
https://lore.kernel.org/all/2022112102.5556-1-tomasz.dziendziel...@gmail.com/?

On 22/02/2023 17:56:35+, Alex Kiernan wrote:
> I needed to do something about our shared sstate store and waded into
> the sstate cache management problem as the existing script takes hours
> to run over NFS (which for better or worse is where ours is). I've set
> myself the problem of replacing the existing script with something
> more extensible, understandable and performant.
> 
> I've got something which I believed was roughly right, but I'm ending
> up with questions I can't answer when comparing the two outputs...
> 
> If I run the existing shell script against a tiny sstate-cache (on my
> laptop) I get 420 duplicate files eligible for removal, if I run my
> script I get 491, looking into the delta, I pick out things like
> these:
> 
> $ find sstate-cache/ -name
> sstate:libcap-ng:core2-64-poky-linux:0.8.3:r0:core2-64:10:*_populate_sysroot.tar.zst*
> -ls
> 49067 16 -rw-r--r--   1 alexkalexk   14435 Feb 18
> 15:29 
> sstate-cache/25/59/sstate:libcap-ng:core2-64-poky-linux:0.8.3:r0:core2-64:10:2559429e2a553085bc657f3d2a21a111818061448e5fa2aa16398afb5dad8b90_populate_sysroot.tar.zst
> 49129 16 -rw-r--r--   1 alexkalexk   15205 Feb 18
> 15:29 
> sstate-cache/25/59/sstate:libcap-ng:core2-64-poky-linux:0.8.3:r0:core2-64:10:2559429e2a553085bc657f3d2a21a111818061448e5fa2aa16398afb5dad8b90_populate_sysroot.tar.zst.siginfo
>   2490392 16 -rw-r--r--   1 alexkalexk   15204 Feb 20
> 13:24 
> sstate-cache/bf/08/sstate:libcap-ng:core2-64-poky-linux:0.8.3:r0:core2-64:10:bf08f26e6bc5ab56ed128441fb05edeef41aa881330d04eea127a93ede51713d_populate_sysroot.tar.zst.siginfo
>339439 16 -rw-r--r--   1 alexkalexk   14423 Feb 20
> 13:24 
> sstate-cache/bf/08/sstate:libcap-ng:core2-64-poky-linux:0.8.3:r0:core2-64:10:bf08f26e6bc5ab56ed128441fb05edeef41aa881330d04eea127a93ede51713d_populate_sysroot.tar.zst
> 
> Which look to me like I should be able to delete the older ones, or am
> I missing something? Trying to follow what the existing script is
> supposed to do is challenging!
> 
> -- 
> Alex Kiernan

> 
> 
> 


-- 
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 (#177581): 
https://lists.openembedded.org/g/openembedded-core/message/177581
Mute This Topic: https://lists.openembedded.org/mt/97165650/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] kernel-arch.bbclass: Map arm64 to arm

2023-02-22 Thread Alexandre Belloni via lists.openembedded.org

Hello,

This is the cause of:

https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/995/steps/14/logs/stdio

2023-02-22 11:33:00,834 - oe-selftest - INFO - 
fitimage.FitImageTests.test_fit_image (subunit.RemotedTestCase)
2023-02-22 11:33:00,835 - oe-selftest - INFO -  ... FAIL

|   OBJCOPY arch/arm64/boot/Image
| NOTE: make -j 16 -l 52 CC=aarch64-poky-linux-gcc   -fuse-ld=bfd 
-fmacro-prefix-map=/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work-shared/qemuarm64/kernel-source=/usr/src/debug/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0
  
-fdebug-prefix-map=/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work-shared/qemuarm64/kernel-source=/usr/src/debug/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0
  
-fmacro-prefix-map=/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/linux-qemuarm64-standard-build=/usr/src/debug/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0
  
-fdebug-prefix-map=/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/linux-qemuarm64-standard-build=/usr/src/debug/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0
  
-fdebug-prefix-map=/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/recipe-sysroot=
  
-fmacro-prefix-map=/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/recipe-sysroot=
  
-fdebug-prefix-map=/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/recipe-sysroot-native=
  
-fdebug-prefix-map=/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work-shared/qemuarm64/kernel-source=/usr/src/kernel
 
-fdebug-prefix-map=/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work-shared/qemuarm64/kernel-build-artifacts=/usr/src/kernel
  
--sysroot=/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/recipe-sysroot
 LD=aarch64-poky-linux-ld.bfd
--sysroot=/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/recipe-sysroot
 HOSTCC=gcc  
HOSTCFLAGS=-isystem/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/recipe-sysroot-native/usr/include
 -O2 -pipe 
HOSTLDFLAGS=-L/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/recipe-sysroot-native/usr/lib
 
-L/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/recipe-sysroot-native/lib
 -Wl,--enable-new-dtags 
-Wl,-rpath-link,/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/recipe-sysroot-native/usr/lib
 
-Wl,-rpath-link,/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/recipe-sysroot-native/lib
 
-Wl,-rpath,/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/recipe-sysroot-native/usr/lib
 
-Wl,-rpath,/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/recipe-sysroot-native/lib
 -Wl,-O1 -Wl,--allow-shlib-undefined 
-Wl,--dynamic-linker=/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/sysroots-uninative/aarch64-linux/lib/ld-linux-aarch64.so.1
 HOSTCP
=gcc  -E HOSTCXX=g++  
HOSTCXXFLAGS=-isystem/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3486447/tmp/work/qemuarm64-poky-linux/linux-yocto/6.1.9+gitAUTOINC+d7393c5752_1caf99d568-r0/recipe-sysroot-native/usr/include
 -O2 -pipe PAHOLE=false zImage
| make: *** No rule to make target 'zImage'.  Stop.
| ERROR: oe_runmake failed

On 20/02/2023 13:42:31+0100, Pavel Zhukov wrote:
> The kernel calls AArch64 'arm64', but U-Boot calls it just 'arm' so
> adding arm64 case to existing map.
> 
> Fixes:
> | install: cannot stat

[OE-core] sstate cache management

2023-02-22 Thread Alex Kiernan

I needed to do something about our shared sstate store and waded into
the sstate cache management problem as the existing script takes hours
to run over NFS (which for better or worse is where ours is). I've set
myself the problem of replacing the existing script with something
more extensible, understandable and performant.

I've got something which I believed was roughly right, but I'm ending
up with questions I can't answer when comparing the two outputs...

If I run the existing shell script against a tiny sstate-cache (on my
laptop) I get 420 duplicate files eligible for removal, if I run my
script I get 491, looking into the delta, I pick out things like
these:

$ find sstate-cache/ -name
sstate:libcap-ng:core2-64-poky-linux:0.8.3:r0:core2-64:10:*_populate_sysroot.tar.zst*
-ls
49067 16 -rw-r--r--   1 alexkalexk   14435 Feb 18
15:29 
sstate-cache/25/59/sstate:libcap-ng:core2-64-poky-linux:0.8.3:r0:core2-64:10:2559429e2a553085bc657f3d2a21a111818061448e5fa2aa16398afb5dad8b90_populate_sysroot.tar.zst
49129 16 -rw-r--r--   1 alexkalexk   15205 Feb 18
15:29 
sstate-cache/25/59/sstate:libcap-ng:core2-64-poky-linux:0.8.3:r0:core2-64:10:2559429e2a553085bc657f3d2a21a111818061448e5fa2aa16398afb5dad8b90_populate_sysroot.tar.zst.siginfo
  2490392 16 -rw-r--r--   1 alexkalexk   15204 Feb 20
13:24 
sstate-cache/bf/08/sstate:libcap-ng:core2-64-poky-linux:0.8.3:r0:core2-64:10:bf08f26e6bc5ab56ed128441fb05edeef41aa881330d04eea127a93ede51713d_populate_sysroot.tar.zst.siginfo
   339439 16 -rw-r--r--   1 alexkalexk   14423 Feb 20
13:24 
sstate-cache/bf/08/sstate:libcap-ng:core2-64-poky-linux:0.8.3:r0:core2-64:10:bf08f26e6bc5ab56ed128441fb05edeef41aa881330d04eea127a93ede51713d_populate_sysroot.tar.zst

Which look to me like I should be able to delete the older ones, or am
I missing something? Trying to follow what the existing script is
supposed to do is challenging!

-- 
Alex Kiernan

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

[OE-core] [PATCH v3] gdb: Upgrade to 13.1

2023-02-22 Thread Alexandre Belloni via lists.openembedded.org

Pass -Wno-enum-constexpr-conversion with clang

GDB 13.1 includes the following changes and enhancements:

* Support for the following new targets has been added in both
GDB and GDBserver:

** GNU/Linux/LoongArch (gdbserver) loongarch*-*-linux*

** GNU/Linux/CSKY (gdbserver) csky*-*linux*

* The Windows native target now supports target async.

* FreeBSD:

** Arm and AArch64: Support for Thread Local Storage (TLS) variables

** Hardware watchpoint support on AArch64 FreeBSD

* Floating-point support has now been added on LoongArch GNU/Linux.

* New commands:

** set print nibbles [on|off]
show print nibbles

This controls whether the 'print/t' command will display binary values
in groups of four bits, known as "nibbles". The default is 'off'.

** Various styling-related commands. See the gdb/NEWS file for more
details (see link at the bottom).

** Various maintenance commands. These are normally aimed at GDB
experts or developers. See the gdb/NEWS file for more details
(see link at the bottom).

* Python API improvements:

** New Python type gdb.BreakpointLocation.

** New function gdb.format_address(ADDRESS, PROGSPACE, ARCHITECTURE)
that formats ADDRESS as 'address '

** New function gdb.current_language that returns the name of the
current language. Unlike gdb.parameter('language'), this will
never return 'auto'.

** New function gdb.print_options that returns a dictionary of the
prevailing print options, in the form accepted by gdb.Value.format_string.

** New method gdb.Frame.language that returns the name of the
frame's language.

** gdb.Value.format_string now uses the format provided by 'print',
if it is called during a 'print' or other similar operation.

** gdb.Value.format_string now accepts the 'summary' keyword. This
can be used to request a shorter representation of a value, the
way that 'set print frame-arguments scalars' does.

* GDB/MI changes:

** MI version 1 is deprecated, and will be removed in GDB 14.

** The async record stating the stopped reason 'breakpoint-hit' now
contains an optional field locno.

* Miscellaneous improvements:

** gdb now supports zstd compressed debug sections (ELFCOMPRESS_ZSTD) for ELF.

** New convenience variable $_inferior_thread_count contains the number
of live threads in the current inferior.

** New convenience variables $_hit_bpnum and $_hit_locno, set to
the breakpoint number and the breakpoint location number of
the breakpoint last hit.

** The "info breakpoints" now displays enabled breakpoint locations
of disabled breakpoints as in the "y-" state.

** The format of 'disassemble /r' and 'record instruction-history /r'
has changed to match the layout of GNU objdump when disassembling.

A new format "/b" has been introduce to provide the old behavior
of "/r".

** It is now possible to use the "document" command to document
user-defined commands.

** Support for memory tag data for AArch64 MTE.

* Support Removal notices:

** DBX mode has been removed.

** Support for building against Python version 2 has been removed.
It is now only possible to build GDB against Python 3.

** Support for the following commands has been removed:

set debug aix-solib on|off
show debug aix-solib
set debug solib-frv on|off
show debug solib-frv

Use the "set/show debug solib" commands instead.

For a complete list and more details on each item, please see the gdb/NEWS
file, available at [1]:

[1]
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=gdb/NEWS;hb=gdb-13.1-release

Signed-off-by: Khem Raj
---
v2: Rebase on master
v3: Drop a clang-16 specific quirk, accidentally added

meta/conf/distro/include/tcmode-default.inc | 2 +-
...ian_12.1.bb => gdb-cross-canadian_13.1.bb} | 0
.../{gdb-cross_12.1.bb => gdb-cross_13.1.bb} | 0
meta/recipes-devtools/gdb/gdb.inc | 19 -
...make-man-install-relative-to-DESTDIR.patch | 28 -
...x-nat-Define-_ABIO32-if-not-defined.patch} | 9 ++---
...-pt_regs-uapi_pt_regs-on-GLIBC-syst.patch} | 11 ++---
...eadline.a-when-using-disable-static.patch} | 13 +++---
...s.h.patch =>

[OE-core] OpenEmbedded Happy Hour February 22 9pm/2100 UTC

2023-02-22 Thread Denys Dmytriyenko

All,

You are cordially invited to the next OpenEmbedded Happy Hour on February 22 
for Asia/Pacific timezones @ 2100/9pm UTC (4pm ET / 1pm PT):

https://www.openembedded.org/wiki/Calendar
https://www.openembedded.org/wiki/Happy_Hours
https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+February+22=20230222T21

-- 
Regards,
Denys Dmytriyenko 
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

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

Re: [OE-core] [PATCH v2] gdb: Upgrade to 13.1

Hello Khem,

Unfortunately, this fails:

https://autobuilder.yoctoproject.org/typhoon/#/builders/52/builds/6608/steps/12/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/2435/steps/13/logs/stdio

| 
/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:
 linux-tdep.o: in function `linux_corefile_thread(thread_info*, 
linux_corefile_thread_data*)':
| linux-tdep.c:(.text+0x1e43): undefined reference to 
`gcore_elf_build_thread_register_notes(gdbarch*, thread_info*, gdb_signal, 
bfd*, std::unique_ptr >*, int*)'
| 
/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:
 linux-tdep.o: in function `linux_make_corefile_notes(gdbarch*, bfd*, int*)':
| linux-tdep.c:(.text+0x4479): undefined reference to 
`gcore_elf_make_tdesc_note(bfd*, std::unique_ptr 
>*, int*)'
| collect2: error: ld returned 1 exit status




On 21/02/2023 18:35:13-0800, Khem Raj wrote:
> Pass -Wno-enum-constexpr-conversion with clang
> 
> GDB 13.1 includes the following changes and enhancements:
> 
> * Support for the following new targets has been added in both
>   GDB and GDBserver:
> 
>   ** GNU/Linux/LoongArch (gdbserver) loongarch*-*-linux*
> 
>   ** GNU/Linux/CSKY (gdbserver) csky*-*linux*
> 
> * The Windows native target now supports target async.
> 
> * FreeBSD:
> 
>   ** Arm and AArch64: Support for Thread Local Storage (TLS) variables
> 
>   ** Hardware watchpoint support on AArch64 FreeBSD
> 
> * Floating-point support has now been added on LoongArch GNU/Linux.
> 
> * New commands:
> 
>  ** set print nibbles [on|off]
> show print nibbles
> 
> This controls whether the 'print/t' command will display binary values
> in groups of four bits, known as "nibbles".  The default is 'off'.
> 
>  ** Various styling-related commands. See the gdb/NEWS file for more
> details (see link at the bottom).
> 
>  ** Various maintenance commands.  These are normally aimed at GDB
> experts or developers. See the gdb/NEWS file for more details
> (see link at the bottom).
> 
> * Python API improvements:
> 
>  ** New Python API for instruction disassembly.
> The new attribute 'locations' of gdb.Breakpoint returns a list of
> gdb.BreakpointLocation objects specifying the locations where the
> breakpoint is inserted into the debuggee.
> 
>  ** New Python type gdb.BreakpointLocation.
> 
>  ** New function gdb.format_address(ADDRESS, PROGSPACE, ARCHITECTURE)
> that formats ADDRESS as 'address '
> 
>  ** New function gdb.current_language that returns the name of the
> current language.  Unlike gdb.parameter('language'), this will
> never return 'auto'.
> 
>  ** New function gdb.print_options that returns a dictionary of the
> prevailing print options, in the form accepted by gdb.Value.format_string.
> 
>  ** New method gdb.Frame.language that returns the name of the
> frame's language.
> 
>  ** gdb.Value.format_string now uses the format provided by 'print',
> if it is called during a 'print' or other similar operation.
> 
>  ** gdb.Value.format_string now accepts the 'summary' keyword.  This
> can be used to request a shorter representation of a value, the
> way that 'set print frame-arguments scalars' does.
> 
>  ** The gdb.register_window_type method now restricts the set of
> acceptable window names.  The first character of a window's name
> must start with a character in the set [a-zA-Z], every subsequent
> character of a window's name must be in the set [-_.a-zA-Z0-9].
> 
> * GDB/MI changes:
> 
>   ** MI version 1 is deprecated, and will be removed in GDB 14.
> 
>   ** The async record stating the stopped reason 'breakpoint-hit' now
>  contains an optional field locno.
> 
> * Miscellaneous improvements:
> 
>   ** gdb now supports zstd compressed debug sections (ELFCOMPRESS_ZSTD) for 
> ELF.
> 
>   ** New convenience variable $_inferior_thread_count contains the number
>  of live threads in the current inferior.
> 
>   ** New convenience variables $_hit_bpnum and $_hit_locno, set to
>  the breakpoint number and the breakpoint location number of
>  the breakpoint last hit.
> 
>   ** The "info breakpoints" now displays enabled breakpoint locations
>  of disabled breakpoints as in the "y-" state.
> 
>   ** The format of 'disassemble /r' and 'record instruction-history /r'
>  has changed to match the layout of GNU objdump when disassembling.
> 
>  A new format "/b" has been introduce to provide the old behavior
>  of "/r".
> 
>   ** The TUI no longer styles the source and assembly code highlighted
>  by the current position indicator by default. You can however
>  re-enable styling using the new "set style tui-current-position"
>  command.
> 
>   ** It is now possible to use the

Re: [OE-core] [PATCH 2/2] [YOCTO #13270] docbook-xml-dtd: refactor for style, add version check regex

2023-02-22 Thread Ross Burton

On 21 Feb 2023, at 14:14, Richard Elberger via lists.openembedded.org 
 wrote:
> 
> Hello Ross,
> 
> It wasn't entirely clear to me that the patch would be required if taken 
> from docbook, but I see that my "test scope" was not appropriate and you 
> have surfaced why patching is required. Now that I have a test target 
> this helps but in future I probably should build world but... just tried 
> that and got a gtk4 dependency error.

My test was to enable the api-documentation DISTRO_FEATURE and then build one 
of the many recipes that use xmlto (and thus, docbook) to make man pages, such 
as kmod.

Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177575): 
https://lists.openembedded.org/g/openembedded-core/message/177575
Mute This Topic: https://lists.openembedded.org/mt/97074293/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] [PATCHv2] qemu: Fix building with latest glibc 2.36

Hi,

I've seen this build issue on my gentoo builder today with qemu-native, so
I've removed the stray cross.patch and sent v2.

Then RP had good question how to reproduce this failure and I've checked
when I've updated glibc in gentoo for last time and it was a month ago (and
I've rebuilt qemu-native few time since then).

So in the end it was linux-libc-headers upgrade to 6.2 from yesterday
(sys-kernel/linux-headers-6.2 in gentoo) which caused this for me (if I
downgrade to 6.1 I can build qemu-native again even without this patch).

Joel: Should I send v3 with updated commit message or will you do it?

Regards,

On Wed, Feb 22, 2023 at 4:00 PM Martin Jansa via lists.openembedded.org
 wrote:

> From: Joel Stanley 
>
> When building native qemu with glibc 2.36 (including latest changes from
> the glibc stable branch), qemu fails to build:
>
>  In file included from /usr/include/linux/btrfs.h:29,
>   from ../qemu-7.2.0/linux-user/syscall.c:165:
>  /usr/include/linux/fs.h:50:8: error: redefinition of ‘struct
> file_clone_range’
> 50 | struct file_clone_range {
>|^~~~
>  ../qemu-7.2.0/linux-user/syscall.c:129:8: note: originally defined here
>129 | struct file_clone_range {
>|^~~~
>
> Backport changes to linux-user that remove the local copy of struct
> file_clone_range.
>
> Patches from
> https://lore.kernel.org/qemu-devel/20230110174901.2580297-1-berra...@redhat.com/
>
> Signed-off-by: Joel Stanley 
> Tested-by: Martin Jansa 
> ---
>  meta/recipes-devtools/qemu/qemu.inc   |  2 +
>  ...er-add-more-compat-ioctl-definitions.patch | 69 
>  ...r-fix-compat-with-glibc-2.36-sys-mou.patch | 78 +++
>  3 files changed, 149 insertions(+)
>  create mode 100644
> meta/recipes-devtools/qemu/qemu/0001-Revert-linux-user-add-more-compat-ioctl-definitions.patch
>  create mode 100644
> meta/recipes-devtools/qemu/qemu/0002-Revert-linux-user-fix-compat-with-glibc-2.36-sys-mou.patch
>
> diff --git a/meta/recipes-devtools/qemu/qemu.inc
> b/meta/recipes-devtools/qemu/qemu.inc
> index 92828e8f2d..1e768b560d 100644
> --- a/meta/recipes-devtools/qemu/qemu.inc
> +++ b/meta/recipes-devtools/qemu/qemu.inc
> @@ -30,6 +30,8 @@ SRC_URI = "https://download.qemu.org/${BPN}-${PV}.tar.xz
> \
>
> file://0001-contrib-vhost-user-blk-Replace-lseek64-with-lseek.patch \
>
> file://0002-linux-user-Replace-use-of-lfs64-related-functions-an.patch \
>
> file://0001-configure-Fix-check-tcg-not-executing-any-tests.patch \
> +
>  file://0001-Revert-linux-user-add-more-compat-ioctl-definitions.patch \
> +
>  file://0002-Revert-linux-user-fix-compat-with-glibc-2.36-sys-mou.patch \
> "
>  UPSTREAM_CHECK_REGEX = "qemu-(?P\d+(\.\d+)+)\.tar"
>
> diff --git
> a/meta/recipes-devtools/qemu/qemu/0001-Revert-linux-user-add-more-compat-ioctl-definitions.patch
> b/meta/recipes-devtools/qemu/qemu/0001-Revert-linux-user-add-more-compat-ioctl-definitions.patch
> new file mode 100644
> index 00..cd8121fed1
> --- /dev/null
> +++
> b/meta/recipes-devtools/qemu/qemu/0001-Revert-linux-user-add-more-compat-ioctl-definitions.patch
> @@ -0,0 +1,69 @@
> +From afa96c55f2c270405de8984e2466067bbb44c0e4 Mon Sep 17 00:00:00 2001
> +From: =?UTF-8?q?Daniel=20P=2E=20Berrang=C3=A9?= 
> +Date: Tue, 10 Jan 2023 12:49:00 -0500
> +Subject: [PATCH] Revert "linux-user: add more compat ioctl definitions"
> +MIME-Version: 1.0
> +Content-Type: text/plain; charset=UTF-8
> +Content-Transfer-Encoding: 8bit
> +
> +This reverts commit c5495f4ecb0cdaaf2e9dddeb48f1689cdb520ca0.
> +
> +glibc has fixed (in 2.36.9000-40-g774058d729) the problem
> +that caused a clash when both sys/mount.h annd linux/mount.h
> +are included, and backported this to the 2.36 stable release
> +too:
> +
> +
> https://sourceware.org/glibc/wiki/Release/2.36#Usage_of_.3Clinux.2Fmount.h.3E_and_.3Csys.2Fmount.h.3E
> +
> +It is saner for QEMU to remove the workaround it applied for
> +glibc 2.36 and expect distros to ship the 2.36 maint release
> +with the fix. This avoids needing to add a further workaround
> +to QEMU to deal with the fact that linux/brtfs.h now also pulls
> +in linux/mount.h via linux/fs.h since Linux 6.1
> +
> +Upstream-Status: Backport from v8.0 (master)
> +
> +Signed-off-by: Daniel P. Berrangé 
> +Reviewed-by: Marc-André Lureau 
> +Link:
> https://lore.kernel.org/r/20230110174901.2580297-2-berra...@redhat.com
> +Signed-off-by: Joel Stanley 
> +---
> + linux-user/syscall.c | 25 -
> + 1 file changed, 25 deletions(-)
> +
> +diff --git a/linux-user/syscall.c b/linux-user/syscall.c
> +index f95a6161e..510de8edc 100644
> +--- a/linux-user/syscall.c
>  b/linux-user/syscall.c
> +@@ -111,31 +111,6 @@
> + #define FS_IOC32_SETFLAGS  _IOW('f', 2, int)
> + #define FS_IOC32_GETVERSION_IOR('v', 1, int)
> + #define FS_IOC32_SETVERSION_IOW('v', 2, int)
> +-
> +-#define BLKGETSIZE64 _IOR(0x12,114,size_t)
> +-#define BLKDISCARD

[OE-core] [PATCHv2] qemu: Fix building with latest glibc 2.36

From: Joel Stanley 

When building native qemu with glibc 2.36 (including latest changes from
the glibc stable branch), qemu fails to build:

 In file included from /usr/include/linux/btrfs.h:29,
  from ../qemu-7.2.0/linux-user/syscall.c:165:
 /usr/include/linux/fs.h:50:8: error: redefinition of ‘struct file_clone_range’
50 | struct file_clone_range {
   |^~~~
 ../qemu-7.2.0/linux-user/syscall.c:129:8: note: originally defined here
   129 | struct file_clone_range {
   |^~~~

Backport changes to linux-user that remove the local copy of struct
file_clone_range.

Patches from 
https://lore.kernel.org/qemu-devel/20230110174901.2580297-1-berra...@redhat.com/

Signed-off-by: Joel Stanley 
Tested-by: Martin Jansa 
---
 meta/recipes-devtools/qemu/qemu.inc   |  2 +
 ...er-add-more-compat-ioctl-definitions.patch | 69 
 ...r-fix-compat-with-glibc-2.36-sys-mou.patch | 78 +++
 3 files changed, 149 insertions(+)
 create mode 100644 
meta/recipes-devtools/qemu/qemu/0001-Revert-linux-user-add-more-compat-ioctl-definitions.patch
 create mode 100644 
meta/recipes-devtools/qemu/qemu/0002-Revert-linux-user-fix-compat-with-glibc-2.36-sys-mou.patch

diff --git a/meta/recipes-devtools/qemu/qemu.inc 
b/meta/recipes-devtools/qemu/qemu.inc
index 92828e8f2d..1e768b560d 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -30,6 +30,8 @@ SRC_URI = "https://download.qemu.org/${BPN}-${PV}.tar.xz \
file://0001-contrib-vhost-user-blk-Replace-lseek64-with-lseek.patch 
\

file://0002-linux-user-Replace-use-of-lfs64-related-functions-an.patch \
file://0001-configure-Fix-check-tcg-not-executing-any-tests.patch \
+   
file://0001-Revert-linux-user-add-more-compat-ioctl-definitions.patch \
+   
file://0002-Revert-linux-user-fix-compat-with-glibc-2.36-sys-mou.patch \
"
 UPSTREAM_CHECK_REGEX = "qemu-(?P\d+(\.\d+)+)\.tar"
 
diff --git 
a/meta/recipes-devtools/qemu/qemu/0001-Revert-linux-user-add-more-compat-ioctl-definitions.patch
 
b/meta/recipes-devtools/qemu/qemu/0001-Revert-linux-user-add-more-compat-ioctl-definitions.patch
new file mode 100644
index 00..cd8121fed1
--- /dev/null
+++ 
b/meta/recipes-devtools/qemu/qemu/0001-Revert-linux-user-add-more-compat-ioctl-definitions.patch
@@ -0,0 +1,69 @@
+From afa96c55f2c270405de8984e2466067bbb44c0e4 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Daniel=20P=2E=20Berrang=C3=A9?= 
+Date: Tue, 10 Jan 2023 12:49:00 -0500
+Subject: [PATCH] Revert "linux-user: add more compat ioctl definitions"
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+This reverts commit c5495f4ecb0cdaaf2e9dddeb48f1689cdb520ca0.
+
+glibc has fixed (in 2.36.9000-40-g774058d729) the problem
+that caused a clash when both sys/mount.h annd linux/mount.h
+are included, and backported this to the 2.36 stable release
+too:
+
+  
https://sourceware.org/glibc/wiki/Release/2.36#Usage_of_.3Clinux.2Fmount.h.3E_and_.3Csys.2Fmount.h.3E
+
+It is saner for QEMU to remove the workaround it applied for
+glibc 2.36 and expect distros to ship the 2.36 maint release
+with the fix. This avoids needing to add a further workaround
+to QEMU to deal with the fact that linux/brtfs.h now also pulls
+in linux/mount.h via linux/fs.h since Linux 6.1
+
+Upstream-Status: Backport from v8.0 (master)
+
+Signed-off-by: Daniel P. Berrangé 
+Reviewed-by: Marc-André Lureau 
+Link: https://lore.kernel.org/r/20230110174901.2580297-2-berra...@redhat.com
+Signed-off-by: Joel Stanley 
+---
+ linux-user/syscall.c | 25 -
+ 1 file changed, 25 deletions(-)
+
+diff --git a/linux-user/syscall.c b/linux-user/syscall.c
+index f95a6161e..510de8edc 100644
+--- a/linux-user/syscall.c
 b/linux-user/syscall.c
+@@ -111,31 +111,6 @@
+ #define FS_IOC32_SETFLAGS  _IOW('f', 2, int)
+ #define FS_IOC32_GETVERSION_IOR('v', 1, int)
+ #define FS_IOC32_SETVERSION_IOW('v', 2, int)
+-
+-#define BLKGETSIZE64 _IOR(0x12,114,size_t)
+-#define BLKDISCARD _IO(0x12,119)
+-#define BLKIOMIN _IO(0x12,120)
+-#define BLKIOOPT _IO(0x12,121)
+-#define BLKALIGNOFF _IO(0x12,122)
+-#define BLKPBSZGET _IO(0x12,123)
+-#define BLKDISCARDZEROES _IO(0x12,124)
+-#define BLKSECDISCARD _IO(0x12,125)
+-#define BLKROTATIONAL _IO(0x12,126)
+-#define BLKZEROOUT _IO(0x12,127)
+-
+-#define FIBMAP _IO(0x00,1)
+-#define FIGETBSZ   _IO(0x00,2)
+-
+-struct file_clone_range {
+-__s64 src_fd;
+-__u64 src_offset;
+-__u64 src_length;
+-__u64 dest_offset;
+-};
+-
+-#define FICLONE _IOW(0x94, 9, int)
+-#define FICLONERANGE_IOW(0x94, 13, struct file_clone_range)
+-
+ #else
+ #include 
+ #endif
diff --git 
a/meta/recipes-devtools/qemu/qemu/0002-Revert-linux-user-fix-compat-with-glibc-2.36-sys-mou.patch

[OE-core] [PATCH] sstate: Add check_for_interrupts() call functionality added in bitbake

2023-02-22 Thread Richard Purdie

Add in the new 'check' calls which mean that the code can exit from longer
running code loops if requested by the user. This covers sstate checks and
sstate manifest cleanup code which currently couldn't be interrupted by the
user from the UI.

Increase the minimum bitbake version which brings in this API.

Signed-off-by: Richard Purdie 
---
 meta/classes-global/sstate.bbclass | 3 +++
 meta/conf/sanity.conf  | 2 +-
 2 files changed, 4 insertions(+), 1 deletion(-)

diff --git a/meta/classes-global/sstate.bbclass 
b/meta/classes-global/sstate.bbclass
index 567de4aba4d..5b63582b5ae 100644
--- a/meta/classes-global/sstate.bbclass
+++ b/meta/classes-global/sstate.bbclass
@@ -1023,6 +1023,7 @@ def sstate_checkhashes(sq_data, d, siginfo=False, 
currentcount=0, summary=True,
 
 if progress:
 bb.event.fire(bb.event.ProcessProgress(msg, 
next(cnt_tasks_done)), d)
+bb.event.check_for_interrupts(d)
 
 tasklist = []
 for tid in missed:
@@ -1296,6 +1297,7 @@ python sstate_eventhandler_reachablestamps() {
 lines.remove(r)
 removed = removed + 1
 bb.event.fire(bb.event.ProcessProgress(msg, removed), d)
+bb.event.check_for_interrupts(d)
 
 bb.event.fire(bb.event.ProcessFinished(msg), d)
 
@@ -1365,6 +1367,7 @@ python sstate_eventhandler_stalesstate() {
 bb.utils.remove(stamp)
 removed = removed + 1
 bb.event.fire(bb.event.ProcessProgress(msg, removed), d)
+bb.event.check_for_interrupts(d)
 
 bb.event.fire(bb.event.ProcessFinished(msg), d)
 }
diff --git a/meta/conf/sanity.conf b/meta/conf/sanity.conf
index fff1ad8246b..593419921f5 100644
--- a/meta/conf/sanity.conf
+++ b/meta/conf/sanity.conf
@@ -3,7 +3,7 @@
 # See sanity.bbclass
 #
 # Expert users can confirm their sanity with "touch conf/sanity.conf"
-BB_MIN_VERSION = "2.0.1"
+BB_MIN_VERSION = "2.3.1"
 
 SANITY_ABIFILE = "${TMPDIR}/abi_version"
 
-- 
2.37.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177572): 
https://lists.openembedded.org/g/openembedded-core/message/177572
Mute This Topic: https://lists.openembedded.org/mt/97160909/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 08/11] build-appliance-image: use a real /tmp

2023-02-22 Thread Richard Purdie

On Tue, 2023-02-21 at 21:25 -0500, Trevor Woerner wrote:
> On Tue 2023-02-21 @ 03:44:42 PM, Trevor Woerner via lists.openembedded.org 
> wrote:
> > Make /tmp a real directory in the root filesystem and not a link to an
> > in-memory tmpfs. Otherwise bitbake will run out of inodes on /tmp very 
> > quickly
> > and stop any build.
> > 
> > Signed-off-by: Trevor Woerner 
> > ---
> >  meta/recipes-core/images/build-appliance-image_15.0.0.bb | 6 ++
> >  1 file changed, 6 insertions(+)
> > 
> > diff --git a/meta/recipes-core/images/build-appliance-image_15.0.0.bb 
> > b/meta/recipes-core/images/build-appliance-image_15.0.0.bb
> > index 3a84de0a2b43..1f7b96a9fcf4 100644
> > --- a/meta/recipes-core/images/build-appliance-image_15.0.0.bb
> > +++ b/meta/recipes-core/images/build-appliance-image_15.0.0.bb
> > @@ -113,6 +113,12 @@ fakeroot do_tweak_image () {
> > # add a /lib64 symlink
> > # this is needed for building rust-native on a 64-bit build appliance
> > ln -rs ${IMAGE_ROOTFS}/lib ${IMAGE_ROOTFS}/lib64
> > +
> > +   # make /tmp a real directory and not a link to an in-memory tmpfs
> > +   # otherwise /tmp will run out of inodes very quickly when bitbaking
> > +   sed -i -e 's#l root root 1777 /tmp /var/tmp#d root root 1777 /tmp 
> > none#' ${IMAGE_ROOTFS}/etc/default/volatiles/00_core
> > +   mkdir -p ${IMAGE_ROOTFS}/tmp
> > +   chmod 1777 ${IMAGE_ROOTFS}/tmp
> >  }
> 
> Richard, this feels rather "hacky" to me. I can't help wonder if it would be
> better to implement a VOLATILE_TMP_DIR mechanism (along the same lines as
> VOLATILE_LOG_DIR)?
> 
> https://docs.yoctoproject.org/dev/ref-manual/variables.html?highlight=volatile_log_dir#term-VOLATILE_LOG_DIR
> https://git.openembedded.org/openembedded-core/tree/meta/recipes-core/initscripts/initscripts_1.0.bb#n107

When I saw this, I was wondering about that too...

I think I'll hold off this patch whilst we think about that a bit but
my memory on this area is taking a bit of paging back in.

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177571): 
https://lists.openembedded.org/g/openembedded-core/message/177571
Mute This Topic: https://lists.openembedded.org/mt/97151865/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] docbook-xml: Switch from debian packages to upstream docbook sources

2023-02-22 Thread Richard Elberger

This patch changes the docbook-xml distribution package source from
debian to docbook which aligns the recipe with the source
originator. Other changes made to the recipe include:

This patch resolves [YOCTO #13270].

- removal of version 4.0 given docbook no longer distributes version
  4.0
- simplification of the header description.
- inline comments to communicate the rationale behind gathering
  multiple versions and LICENSE file handling.
- minor ordering changes to align with styling conventions and better
  context to better communicate use
- Added commend about magic XMLCATALOGS variable. This variable and
  subsequent inherit might be better placed in recipes that depend on
  docbook-xml but leave it for now to not cause a patch landslide.
- Modify the related docbook-xml patch to remove docbook-xml-4.0 since
  it is no longer provided.
- Put BBCLASSEXTEND to end of recipe per RP note on convention

Signed-off-by: Richard Elberger 
---
 .../docbook-xml-update-catalog.xml.patch  | 89 +--
 .../docbook-xml/docbook-xml-dtd4_4.5.bb   | 60 +
 2 files changed, 43 insertions(+), 106 deletions(-)

diff --git 
a/meta/recipes-devtools/docbook-xml/docbook-xml-dtd4/docbook-xml-update-catalog.xml.patch
 
b/meta/recipes-devtools/docbook-xml/docbook-xml-dtd4/docbook-xml-update-catalog.xml.patch
index c1385631d7..1f3364900c 100644
--- 
a/meta/recipes-devtools/docbook-xml/docbook-xml-dtd4/docbook-xml-update-catalog.xml.patch
+++ 
b/meta/recipes-devtools/docbook-xml/docbook-xml-dtd4/docbook-xml-update-catalog.xml.patch
@@ -1,97 +1,12 @@
+21/3/2023: modified to remove 4.0
+
 docbook-xml: update catalog.xml
 
 Refer Ubuntu 13.04 to update catalog.xml
 
 Upstream-Status: Inappropriate [docbook 4.x development has ceased, docbook 5 
is entirely different]
 Signed-off-by: Hongxu Jia 

- docbook-4.0/catalog.xml   | 72 +++
- docbook-4.1.2/catalog.xml | 66 +++
- docbook-4.2/catalog.xml   | 69 ++---
- docbook-4.3/catalog.xml   | 72 ---
- docbook-4.4/catalog.xml   | 63 ++---
- docbook-4.5/catalog.xml   | 63 ++---
- 6 files changed, 165 insertions(+), 240 deletions(-)
- create mode 100644 docbook-4.0/catalog.xml
- create mode 100644 docbook-4.1.2/catalog.xml
 
-diff --git a/docbook-4.0/catalog.xml b/docbook-4.0/catalog.xml
-new file mode 100644
 /dev/null
-+++ b/docbook-4.0/catalog.xml
-@@ -0,0 +1,72 @@
-+
-+http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd;>
-+
-+
-+
-+
-+
-+
-+
-+
-+
-+
-+
-+
-+
-+
-+
-+
-+
-+
-+
-+http://www.oasis-open.org/docbook/xml/4.0/docbookx.dtd;
-+uri="docbookx.dtd"/>
-+
-+
-+
-+
-+
-+
-+
-+
-+
-+
-+
-+
-+
-+
-+
-+
-+
-+
-+
-+
-+
-+
-+
-+
-+
-+
-+
 diff --git a/docbook-4.1.2/catalog.xml b/docbook-4.1.2/catalog.xml
 new file mode 100644
 --- /dev/null
diff --git a/meta/recipes-devtools/docbook-xml/docbook-xml-dtd4_4.5.bb 
b/meta/recipes-devtools/docbook-xml/docbook-xml-dtd4_4.5.bb
index 2bec1442af..e4b4201b1f 100644
--- a/meta/recipes-devtools/docbook-xml/docbook-xml-dtd4_4.5.bb
+++ b/meta/recipes-devtools/docbook-xml/docbook-xml-dtd4_4.5.bb
@@ -1,30 +1,47 @@
 SUMMARY = "Document type definitions for verification of XML data files"
 DESCRIPTION = "Document type definitions for verification of XML data \
-files against the DocBook rule set, it ships with the latest DocBook 4.5 \
-XML DTD, as well as a selected set of legacy DTDs for use with older \
-documents, including 4.0, 4.1.2, 4.2, 4.3 and 4.4"
-HOMEPAGE = "http://www.docbook.org/xml/;
+files against the DocBook rule set."
+HOMEPAGE = "https://docbook.org;
+
+# The upstream sources are not distributed with a license file.
+# LICENSE-OASIS is included as a "patch" to workaround this. When
+# upgrading this recipe, please verify whether this is still needed.
 
 LICENSE = "OASIS"
 LIC_FILES_CHKSUM = 
"file://${WORKDIR}/LICENSE-OASIS;md5=c608985dd5f7f215e669e7639a0b1d2e"
 
-# Note: the upstream sources are not distributed with a license file.
-# LICENSE-OASIS is included as a "patch" to workaround this. When
-# upgrading this recipe, please verify whether this is still needed.
-SRC_URI = 
"http://snapshot.debian.org/archive/debian/20160728T043443Z/pool/main/d/docbook-xml/docbook-xml_${PV}.orig.tar.gz
 \
-   file://LICENSE-OASIS \
-   file://docbook-xml-update-catalog.xml.patch \
-"
+# To support apps with xml schema backward compatibility, we must
+# install a set of schemas. Install the latest based on PV and then
+# name any specific versions as required. TODO: Figure out a mechanism
+# to filter exactly which versions are necessary, if that's even
+# possible.
+#
+# DocBook.org lists available release packages at https://docbook.org/xml/.
+#
+# The release packages relate docbook source at
+# https://github.com/docbook/docbook

Re: [OE-core] [PATCH 2/2] [YOCTO #13270] docbook-xml-dtd: refactor for style, add version check regex

2023-02-22 Thread Richard Elberger

Ross, I found the problem. Since I can't build world I will do best 
effort and build core-image-minimal through. In the patch I with put 
comment, with additional explanation in the commit message, about the 
magic variable. In my opinion a couple lines are misplaced but for sake 
of not causing a patch domino effect I will revert to the old behavior. 
I'll let the core group decide if you want to live with it or make a 
workitem for future effort.

On 2/21/23 08:45, Ross Burton wrote:
> Sorry, but this doesn’t work:
>
> If you build xmlto-native:
>
>   validity error : Could not load the external subset 
> "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd;
>   Document 
> /yocto/ross/build/tmp/work/aarch64-linux/xmlto-native/0.0.28+0.0.29+gitAUTOINC+6fa6a0e076-r0/build/../git/doc/xmlif.xml
>  does not validate
>
>   
> /yocto/ross/build/tmp/work/aarch64-linux/xmlto-native/0.0.28+0.0.29+gitAUTOINC+6fa6a0e076-r0/build/../git/doc/xmlif.xml:4:
>  warning: failed to load external entity 
> "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd;
>  "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd”>
>
> Ross


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

Verified that both ways would work and sent a patch for the second 
approach. Looks easier for now


Am Mi, 22. Feb 2023 um 12:31:26 +0100 schrieb Markus Volk 
:

What would be the preferred way to fix it?

I'd prefer the more progressive way and add BBCLASSEXTEND 
+="nativesdk" to gtk.bb
But this would also add the need to build libxkbcommon and 
xkeyboard-config for nativesdk


vte recipe already has a PACKAGECONFIG:remove line, so i guess it 
will be less invasive to additionally add:

PACKAGECONFIG:remove:class-nativesdk = "gtk4"

Am Mi, 22. Feb 2023 um 12:08:45 +0100 schrieb Alexandre Belloni via 
lists.openembedded.org 
:

Hello,

This causes:

stdio: WARNING: Nothing PROVIDES 'nativesdk-gtk4' (but 
virtual:nativesdk:/home/pokybuild/yocto-worker/a-full/build/meta/recipes-support/vte/vte_0.70.3.bb 
DEPENDS on or otherwise requires it). Close matches:
stdio: WARNING: Nothing RPROVIDES 'nativesdk-vte' (but 
virtual:nativesdk:/home/pokybuild/yocto-worker/a-full/build/meta/recipes-support/vte/vte_0.70.3.bb 
RDEPENDS on or otherwise requires it)
stdio: WARNING: Nothing RPROVIDES 'nativesdk-vte-dev' (but 
virtual:nativesdk:/home/pokybuild/yocto-worker/a-full/build/meta/recipes-support/vte/vte_0.70.3.bb 
RDEPENDS on or otherwise requires it)


On 21/02/2023 19:52:31+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 and remove unneeded patch

 Signed-off-by: Markus Volk >

 ---
  ...EXITCODE-macro-for-non-glibc-systems.patch | 42 
---

  .../vte/{vte_0.70.2.bb => vte_0.70.3.bb}  | 22 +-
  2 files changed, 10 insertions(+), 54 deletions(-)
  delete mode 100644 
meta/recipes-support/vte/vte/0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch
  rename meta/recipes-support/vte/{vte_0.70.2.bb => vte_0.70.3.bb} 
(69%)


 diff --git 
a/meta/recipes-support/vte/vte/0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch 
b/meta/recipes-support/vte/vte/0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch

 deleted file mode 100644
 index b4100fc381..00
 --- 
a/meta/recipes-support/vte/vte/0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch

 +++ /dev/null
 @@ -1,42 +0,0 @@
 -From de9639baac792327c701e509258b8a13f6959e82 Mon Sep 17 00:00:00 
2001
 -From: Danilo Spinella >

 -Date: Thu, 21 Mar 2019 14:19:26 +0100
 -Subject: [PATCH] Add W_EXITCODE macro for non-glibc systems
 -MIME-Version: 1.0
 -Content-Type: text/plain; charset=UTF-8
 -Content-Transfer-Encoding: 8bit
 -
 -Upstream-Status: Submitted [1]
 -
 -Signed-off-by: Andreas Müller >

 -
 -[1] 
 -
 
 - src/missing.hh | 4 
 - src/widget.cc  | 1 +
 - 2 files changed, 5 insertions(+)
 -
  a/src/missing.hh
 -+++ b/src/missing.hh
 -@@ -24,6 +24,10 @@
 - #define NSIG (8 * sizeof(sigset_t))
 - #endif
 -
 -+#ifndef W_EXITCODE
 -+#define W_EXITCODE(ret, sig) ((ret) << 8 | (sig))
 -+#endif
 -+
 - #ifndef HAVE_FDWALK
 - int fdwalk(int (*cb)(void* data, int fd),
 -void* data);
  a/src/widget.cc
 -+++ b/src/widget.cc
 -@@ -21,6 +21,7 @@
 - #include "widget.hh"
 -
 - #include  // for W_EXITCODE
 -+#include "missing.hh" // for W_EXITCODE on non-glibc systems
 -
 - #include 
 - #include 
 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..a39598216b 100644
 --- a/meta/recipes-support/vte/vte_0.70.2.bb
 +++ b/meta/recipes-support/vte/vte_0.70.3.bb
 @@ -11,30 +11,28 @@ 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"

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

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

Signed-off-by: Markus Volk 
---
 ...EXITCODE-macro-for-non-glibc-systems.patch | 42 ---
 .../vte/{vte_0.70.2.bb => vte_0.70.3.bb}  | 23 +-
 2 files changed, 11 insertions(+), 54 deletions(-)
 delete mode 100644 
meta/recipes-support/vte/vte/0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch
 rename meta/recipes-support/vte/{vte_0.70.2.bb => vte_0.70.3.bb} (69%)

diff --git 
a/meta/recipes-support/vte/vte/0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch
 
b/meta/recipes-support/vte/vte/0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch
deleted file mode 100644
index b4100fc381..00
--- 
a/meta/recipes-support/vte/vte/0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch
+++ /dev/null
@@ -1,42 +0,0 @@
-From de9639baac792327c701e509258b8a13f6959e82 Mon Sep 17 00:00:00 2001
-From: Danilo Spinella 
-Date: Thu, 21 Mar 2019 14:19:26 +0100
-Subject: [PATCH] Add W_EXITCODE macro for non-glibc systems
-MIME-Version: 1.0
-Content-Type: text/plain; charset=UTF-8
-Content-Transfer-Encoding: 8bit
-
-Upstream-Status: Submitted [1]
-
-Signed-off-by: Andreas Müller 
-
-[1] https://gitlab.gnome.org/GNOME/vte/issues/72
-

- src/missing.hh | 4 
- src/widget.cc  | 1 +
- 2 files changed, 5 insertions(+)
-
 a/src/missing.hh
-+++ b/src/missing.hh
-@@ -24,6 +24,10 @@
- #define NSIG (8 * sizeof(sigset_t))
- #endif
- 
-+#ifndef W_EXITCODE
-+#define W_EXITCODE(ret, sig) ((ret) << 8 | (sig))
-+#endif
-+
- #ifndef HAVE_FDWALK
- int fdwalk(int (*cb)(void* data, int fd),
-void* data);
 a/src/widget.cc
-+++ b/src/widget.cc
-@@ -21,6 +21,7 @@
- #include "widget.hh"
- 
- #include  // for W_EXITCODE
-+#include "missing.hh" // for W_EXITCODE on non-glibc systems
- 
- #include 
- #include 
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..73b4666efc 100644
--- a/meta/recipes-support/vte/vte_0.70.2.bb
+++ b/meta/recipes-support/vte/vte_0.70.3.bb
@@ -11,34 +11,33 @@ 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


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