Re: [OE-core] [PATCH] btrfs-tools: upgrade 6.1.3 -> 6.2.1

2023-03-17 Thread Khem Raj
FWIW it also fails compiling with clang compiler

https://errors.yoctoproject.org/Errors/Details/698109/

On Thu, Mar 16, 2023 at 2:46 PM Alexandre Belloni via
lists.openembedded.org
 wrote:
>
> Hello,
>
> This fails on the AB for edgerouter-alt and meta-intel:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/111/builds/4406/steps/11/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/100/builds/4205/steps/13/logs/stdio
>
> | gcc  
> -isystem/home/pokybuild/yocto-worker/edgerouter-alt/build/build/tmp/work/x86_64-linux/btrfs-tools-native/6.2.1-r0/recipe-sysroot-native/usr/include
>  -O2 -pipe -std=gnu11 -D_GNU_SOURCE -fPIC -fvisibility=hidden 
> -I./libbtrfsutil-o libbtrfsutil/stubs.o -c libbtrfsutil/stubs.c -o 
> libbtrfsutil/stubs.o
> | In file included from crypto/blake2b-round.h:140,
> |  from crypto/blake2b-sse2.c:33:
> | crypto/blake2b-sse2.c: In function ‘blake2b_compress_sse2’:
> | crypto/blake2b-load-sse41.h:21:25: error: incompatible type for argument 1 
> of ‘_mm_unpacklo_epi64’
> |21 | b0 = _mm_unpacklo_epi64(m0, m1); \
> |   | ^~
> |   | |
> |   | uint64_t {aka long unsigned int}
> | crypto/blake2b-round.h:146:3: note: in expansion of macro ‘LOAD_MSG_0_1’
> |   146 |   LOAD_MSG_ ##r ##_1(b0, b1); \
> |   |   ^
> | crypto/blake2b-sse2.c:80:3: note: in expansion of macro ‘ROUND’
> |80 |   ROUND( 0 );
> |   |   ^
> | In file included from crypto/blake2b-sse2.c:25:
> | /usr/lib/gcc/x86_64-redhat-linux/11/include/emmintrin.h:1046:29: note: 
> expected ‘__m128i’ but argument is of type ‘uint64_t’ {aka ‘long unsigned 
> int’}
> |  1046 | _mm_unpacklo_epi64 (__m128i __A, __m128i __B)
> |   | ^~~
> | In file included from crypto/blake2b-round.h:140,
> |  from crypto/blake2b-sse2.c:33:
>
> On 16/03/2023 08:28:44+0800, wangmy wrote:
> > From: Wang Mingyu 
> >
> > Changelog:
> > =
> >  * fix build with crypto libraries
> >  * CI images updated, build tests extended
> >
> > Signed-off-by: Wang Mingyu 
> > ---
> >  .../btrfs-tools/{btrfs-tools_6.1.3.bb => btrfs-tools_6.2.1.bb}  | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >  rename meta/recipes-devtools/btrfs-tools/{btrfs-tools_6.1.3.bb => 
> > btrfs-tools_6.2.1.bb} (98%)
> >
> > diff --git a/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.1.3.bb 
> > b/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.2.1.bb
> > similarity index 98%
> > rename from meta/recipes-devtools/btrfs-tools/btrfs-tools_6.1.3.bb
> > rename to meta/recipes-devtools/btrfs-tools/btrfs-tools_6.2.1.bb
> > index b4dfc5b3f3..a6ff87a90c 100644
> > --- a/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.1.3.bb
> > +++ b/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.2.1.bb
> > @@ -19,7 +19,7 @@ SRC_URI = 
> > "git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git;b
> > 
> > file://0001-Add-a-possibility-to-specify-where-python-modules-ar.patch \
> > 
> > file://0001-Use-pread-pwrite-ftruncate-stat-instead-of-64bit-equ.patch \
> > "
> > -SRCREV = "908b4b4450320e30fdef693f09b42f4eb93702c3"
> > +SRCREV = "366cd079bc43241b27e0838be0c5369aa00716f8"
> >  S = "${WORKDIR}/git"
> >
> >  PACKAGECONFIG ??= " \
> > --
> > 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 (#178754): 
https://lists.openembedded.org/g/openembedded-core/message/178754
Mute This Topic: https://lists.openembedded.org/mt/97641211/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] glibc: Disable warnings as errors

2023-03-17 Thread Khem Raj
As distro builders this option helps using different compilers to build
glibc

Signed-off-by: Khem Raj 
---
 meta/recipes-core/glibc/glibc_2.37.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-core/glibc/glibc_2.37.bb 
b/meta/recipes-core/glibc/glibc_2.37.bb
index 762a2793ad..b27f98fb19 100644
--- a/meta/recipes-core/glibc/glibc_2.37.bb
+++ b/meta/recipes-core/glibc/glibc_2.37.bb
@@ -74,6 +74,7 @@ EXTRA_OECONF = "--enable-kernel=${OLDEST_KERNEL} \
 --enable-stack-protector=strong \
 --disable-crypt \
 --with-default-link \
+--disable-werror \
 ${@bb.utils.contains_any('SELECTED_OPTIMIZATION', '-O0 -Og', 
'--disable-werror', '', d)} \
 ${GLIBCPIE} \
 ${GLIBC_EXTRA_OECONF}"
-- 
2.40.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#178753): 
https://lists.openembedded.org/g/openembedded-core/message/178753
Mute This Topic: https://lists.openembedded.org/mt/97672607/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] systemtap: Disable dangling-pointer warning

2023-03-14 Thread Khem Raj
This is to fix build in RISCV64

| In constructor 'symresolution_info::symresolution_info(systemtap_session&, 
bool)',
| inlined from 'int semantic_pass_symbols(systemtap_session&)' at 
../git/elaborate.cxx:1884:28:
| ../git/elaborate.cxx:2601:21: error: storing the address of local variable 
'sym' in '*s.systemtap_session::symbol_resolver' [-Werror=dangling-pointer=]
|  2601 |   s.symbol_resolver = this; // save resolver for early PR25841 
function resolution
|   |   ~~^~
| ../git/elaborate.cxx: In function 'int 
semantic_pass_symbols(systemtap_session&)':
| ../git/elaborate.cxx:1884:22: note: 'sym' declared here
|  1884 |   symresolution_info sym (s);
|   |  ^~~
| ../git/elaborate.cxx:1884:22: note: 's' declared here

Signed-off-by: Khem Raj 
---
 meta/recipes-kernel/systemtap/systemtap_git.bb | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-kernel/systemtap/systemtap_git.bb 
b/meta/recipes-kernel/systemtap/systemtap_git.bb
index 072fcb310a..d320a8a5e0 100644
--- a/meta/recipes-kernel/systemtap/systemtap_git.bb
+++ b/meta/recipes-kernel/systemtap/systemtap_git.bb
@@ -34,6 +34,9 @@ PACKAGECONFIG[python3-probes] = 
"--with-python3-probes,--without-python3-probes,
 inherit autotools gettext pkgconfig systemd
 inherit ${@bb.utils.contains('PACKAGECONFIG', 'python3-probes', 
'setuptools3-base', '', d)}
 
+# | ../git/elaborate.cxx:2601:21: error: storing the address of local variable 
'sym' in '*s.systemtap_session::symbol_resolver' [-Werror=dangling-pointer=]
+CXXFLAGS += "-Wno-dangling-pointer"
+
 # exporter comes with python3-probes
 PACKAGES =+ "${PN}-exporter"
 FILES:${PN}-exporter = "${sysconfdir}/stap-exporter/* \
-- 
2.40.0


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



Re: [OE-core] [PATCH 2/7] bitbake.conf: do not set native opengl distro feature from target

2023-03-13 Thread Khem Raj
also seeing below errors which are related too

ERROR: Nothing PROVIDES 'gtk4-native' (but
/mnt/b/yoe/master/sources/meta-openembedded/meta-gnome/recipes-gnome/gnome-bluetooth/gnome-bluetooth_42.5.bb,
/mnt/b/yoe/master/
sources/meta-openembedded/meta-gnome/recipes-gnome/gnome-text-editor/gnome-text-editor_43.1.bb,
/mnt/b/yoe/master/sources/meta-openembedded/meta-gnome/recipes-gnome/gnome-
chess/gnome-chess_43.1.bb,
/mnt/b/yoe/master/sources/meta-openembedded/meta-gnome/recipes-gnome/gnome-calculator/gnome-calculator_43.0.1.bb
DEPENDS on or otherwise require
s it)
gtk4-native was skipped: missing required distro feature 'opengl' (not
in DISTRO_FEATURES)

On Mon, Mar 13, 2023 at 3:45 PM Khem Raj  wrote:
>
> I am seeing waylandpp failing to build and YP layer compatibility tests 
> failing.
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/88/builds/2557/steps/11/logs/stdio
>
> On Sun, Mar 12, 2023 at 7:51 AM Alexander Kanavin
>  wrote:
> >
> > This makes native opengl (and thus accelerated graphics in qemu) opt-in;
> > the reason is that latest mesa tightly couples hardware drivers with its 
> > libraries,
> > so we have to build both in mesa-native. Doing so significantly lengthens
> > the builds, and so cannot be imposed by default.
> >
> > Add a check and a hint to runqemu so that there is a helpful error when
> > there is no native/nativesdk opengl/virgl support.
> >
> > Signed-off-by: Alexander Kanavin 
> > ---
> >  meta/conf/bitbake.conf   |  4 ++--
> >  meta/lib/oeqa/selftest/cases/runtime_test.py |  4 ++--
> >  scripts/runqemu  | 11 ++-
> >  3 files changed, 14 insertions(+), 5 deletions(-)
> >
> > diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> > index afd9e2f552..d1dc428583 100644
> > --- a/meta/conf/bitbake.conf
> > +++ b/meta/conf/bitbake.conf
> > @@ -912,8 +912,8 @@ DISTRO_FEATURES_NATIVESDK ?= "x11"
> >
> >  # Normally target distro features will not be applied to native builds:
> >  # Native distro features on this list will use the target feature value
> > -DISTRO_FEATURES_FILTER_NATIVE ?= "api-documentation debuginfod opengl 
> > wayland"
> > -DISTRO_FEATURES_FILTER_NATIVESDK ?= "api-documentation debuginfod opengl 
> > wayland"
> > +DISTRO_FEATURES_FILTER_NATIVE ?= "api-documentation debuginfod wayland"
> > +DISTRO_FEATURES_FILTER_NATIVESDK ?= "api-documentation debuginfod wayland"
> >
> >  DISTRO_FEATURES_BACKFILL = "pulseaudio sysvinit gobject-introspection-data 
> > ldconfig"
> >  MACHINE_FEATURES_BACKFILL = "rtc qemu-usermode"
> > diff --git a/meta/lib/oeqa/selftest/cases/runtime_test.py 
> > b/meta/lib/oeqa/selftest/cases/runtime_test.py
> > index 81b8d056cc..661c09c109 100644
> > --- a/meta/lib/oeqa/selftest/cases/runtime_test.py
> > +++ b/meta/lib/oeqa/selftest/cases/runtime_test.py
> > @@ -232,7 +232,7 @@ class TestImage(OESelftestTestCase):
> >  if 'sdl' not in qemu_packageconfig:
> >  features += 'PACKAGECONFIG:append:pn-qemu-system-native = " 
> > sdl"\n'
> >  if 'opengl' not in qemu_distrofeatures:
> > -features += 'DISTRO_FEATURES:append = " opengl"\n'
> > +features += 'DISTRO_FEATURES_NATIVE:append = " opengl"\n'
> >  features += 'TEST_SUITES = "ping ssh virgl"\n'
> >  features += 'IMAGE_FEATURES:append = " ssh-server-dropbear"\n'
> >  features += 'IMAGE_INSTALL:append = " kmscube"\n'
> > @@ -264,7 +264,7 @@ class TestImage(OESelftestTestCase):
> >  qemu_distrofeatures = get_bb_var('DISTRO_FEATURES', 
> > 'qemu-system-native')
> >  features = 'IMAGE_CLASSES += "testimage"\n'
> >  if 'opengl' not in qemu_distrofeatures:
> > -features += 'DISTRO_FEATURES:append = " opengl"\n'
> > +features += 'DISTRO_FEATURES_NATIVE:append = " opengl"\n'
> >  features += 'TEST_SUITES = "ping ssh virgl"\n'
> >  features += 'IMAGE_FEATURES:append = " ssh-server-dropbear"\n'
> >  features += 'IMAGE_INSTALL:append = " kmscube"\n'
> > diff --git a/scripts/runqemu b/scripts/runqemu
> > index 8e915f3d4c..9f82aa12f1 100755
> > --- a/scripts/runqemu
> > +++ b/scripts/runqemu
> > @@ -447,7 +447,16 @@ class BaseConfig(object):
> >  self.set("MACHINE", arg)
> >
> >  def set_dri_path(self):
> > -self.qemu_environ['LIBGL_DR

Re: [OE-core] [PATCH 2/7] bitbake.conf: do not set native opengl distro feature from target

2023-03-13 Thread Khem Raj
I am seeing waylandpp failing to build and YP layer compatibility tests failing.

https://autobuilder.yoctoproject.org/typhoon/#/builders/88/builds/2557/steps/11/logs/stdio

On Sun, Mar 12, 2023 at 7:51 AM Alexander Kanavin
 wrote:
>
> This makes native opengl (and thus accelerated graphics in qemu) opt-in;
> the reason is that latest mesa tightly couples hardware drivers with its 
> libraries,
> so we have to build both in mesa-native. Doing so significantly lengthens
> the builds, and so cannot be imposed by default.
>
> Add a check and a hint to runqemu so that there is a helpful error when
> there is no native/nativesdk opengl/virgl support.
>
> Signed-off-by: Alexander Kanavin 
> ---
>  meta/conf/bitbake.conf   |  4 ++--
>  meta/lib/oeqa/selftest/cases/runtime_test.py |  4 ++--
>  scripts/runqemu  | 11 ++-
>  3 files changed, 14 insertions(+), 5 deletions(-)
>
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index afd9e2f552..d1dc428583 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -912,8 +912,8 @@ DISTRO_FEATURES_NATIVESDK ?= "x11"
>
>  # Normally target distro features will not be applied to native builds:
>  # Native distro features on this list will use the target feature value
> -DISTRO_FEATURES_FILTER_NATIVE ?= "api-documentation debuginfod opengl 
> wayland"
> -DISTRO_FEATURES_FILTER_NATIVESDK ?= "api-documentation debuginfod opengl 
> wayland"
> +DISTRO_FEATURES_FILTER_NATIVE ?= "api-documentation debuginfod wayland"
> +DISTRO_FEATURES_FILTER_NATIVESDK ?= "api-documentation debuginfod wayland"
>
>  DISTRO_FEATURES_BACKFILL = "pulseaudio sysvinit gobject-introspection-data 
> ldconfig"
>  MACHINE_FEATURES_BACKFILL = "rtc qemu-usermode"
> diff --git a/meta/lib/oeqa/selftest/cases/runtime_test.py 
> b/meta/lib/oeqa/selftest/cases/runtime_test.py
> index 81b8d056cc..661c09c109 100644
> --- a/meta/lib/oeqa/selftest/cases/runtime_test.py
> +++ b/meta/lib/oeqa/selftest/cases/runtime_test.py
> @@ -232,7 +232,7 @@ class TestImage(OESelftestTestCase):
>  if 'sdl' not in qemu_packageconfig:
>  features += 'PACKAGECONFIG:append:pn-qemu-system-native = " 
> sdl"\n'
>  if 'opengl' not in qemu_distrofeatures:
> -features += 'DISTRO_FEATURES:append = " opengl"\n'
> +features += 'DISTRO_FEATURES_NATIVE:append = " opengl"\n'
>  features += 'TEST_SUITES = "ping ssh virgl"\n'
>  features += 'IMAGE_FEATURES:append = " ssh-server-dropbear"\n'
>  features += 'IMAGE_INSTALL:append = " kmscube"\n'
> @@ -264,7 +264,7 @@ class TestImage(OESelftestTestCase):
>  qemu_distrofeatures = get_bb_var('DISTRO_FEATURES', 
> 'qemu-system-native')
>  features = 'IMAGE_CLASSES += "testimage"\n'
>  if 'opengl' not in qemu_distrofeatures:
> -features += 'DISTRO_FEATURES:append = " opengl"\n'
> +features += 'DISTRO_FEATURES_NATIVE:append = " opengl"\n'
>  features += 'TEST_SUITES = "ping ssh virgl"\n'
>  features += 'IMAGE_FEATURES:append = " ssh-server-dropbear"\n'
>  features += 'IMAGE_INSTALL:append = " kmscube"\n'
> diff --git a/scripts/runqemu b/scripts/runqemu
> index 8e915f3d4c..9f82aa12f1 100755
> --- a/scripts/runqemu
> +++ b/scripts/runqemu
> @@ -447,7 +447,16 @@ class BaseConfig(object):
>  self.set("MACHINE", arg)
>
>  def set_dri_path(self):
> -self.qemu_environ['LIBGL_DRIVERS_PATH'] = 
> os.path.join(self.bindir_native, '../lib/dri')
> +drivers_path = os.path.join(self.bindir_native, '../lib/dri')
> +if not os.path.exists(drivers_path) or not os.listdir(drivers_path):
> +raise RunQemuError("""
> +qemu has been built without opengl support and accelerated graphics support 
> is not available.
> +To enable it, add:
> +DISTRO_FEATURES_NATIVE:append = " opengl"
> +DISTRO_FEATURES_NATIVESDK:append = " opengl"
> +to your build configuration.
> +""")
> +self.qemu_environ['LIBGL_DRIVERS_PATH'] = drivers_path
>
>  def check_args(self):
>  for debug in ("-d", "--debug"):
> --
> 2.30.2
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#178470): 
https://lists.openembedded.org/g/openembedded-core/message/178470
Mute This Topic: https://lists.openembedded.org/mt/97560251/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] systemd: Fix musl fix patch

2023-03-13 Thread Khem Raj
On Mon, Mar 13, 2023 at 12:56 AM Alexander Kanavin
 wrote:
>
> On Mon, 13 Mar 2023 at 01:12, Khem Raj  wrote:
>
> > This is working as intended, unlike glibc, musl provides stddef.h and
> > it wants musl based platforms to use that,
> > OE clang won't do that when the selected libc is glibc.
>
> But this means gcc is not doing the right thing. It does take its own
> stddef.h (rather than one from musl), and this leads to undetected
> breakage like this one and general inconsistency between which set of
> headers is used.

probably, but there maybe some reasons why its not done which I am not aware of.

>
> It's gcc that is the default, AB-tested choice with musl, shouldn't it
> work correctly?
>
> Alex

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#178469): 
https://lists.openembedded.org/g/openembedded-core/message/178469
Mute This Topic: https://lists.openembedded.org/mt/97555854/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] systemd: Fix musl fix patch

2023-03-12 Thread Khem Raj
On Sun, Mar 12, 2023 at 1:54 PM Alexander Kanavin
 wrote:
>
> On Sun, 12 Mar 2023 at 21:19, Khem Raj  wrote:
> > alltypes.h is generated by musl during its build which is used by all
> > system headers on musl systems it contains
> >
> > #if defined(__NEED_wchar_t) && !defined(__DEFINED_wchar_t)
> > typedef unsigned wchar_t;
> > #define __DEFINED_wchar_t
> > #endif
> >
> > stddef.h defines __NEED_wchar_t which is included from efi-string.h
> > and stddef.h immediately includes alltypes.h. so unless somewhere
> > __DEFINED_wchar_t
> > is pre-defined above will be included and that's what the problem is.
> >
> > The patch you created makes efi-string.c to type define wchar_t before
> > including efi-string.h without blocking all possible ways for it to be
> > defined by system headers.
> > Hope that makes it clear.
>
> I understand this. The question was about why this happens with clang,
> but does not happen with gcc.
>
> I looked into this meanwhile. This seems to be a difference in how
> compilers look for headers.
>
> There are actually two versions of stddef.h, one provided by the
> compiler itself (which would be the correct, expected one), and the
> other coming from musl.
>
> gcc:
> alex@Zen2:/srv/storage/alex/yocto/build-musl-arm-64/tmp/work/cortexa57-poky-linux-musl/systemd-boot/253.1-r0$
> find . -name stddef.h
> ./recipe-sysroot-native/usr/lib/aarch64-poky-linux-musl/gcc/aarch64-poky-linux-musl/12.2.0/include/stddef.h
> ./recipe-sysroot/usr/include/linux/stddef.h
> ./recipe-sysroot/usr/include/stddef.h
> ./git/src/basic/linux/stddef.h
>
> clang:
> alex@Zen2:/srv/storage/alex/yocto/build-musl-arm-64/tmp/work/cortexa57-poky-linux-musl/systemd-boot/253.1-r0$
> find . -name stddef.h
> ./recipe-sysroot-native/usr/lib/clang/15.0.7/include/stddef.h
> ./recipe-sysroot/usr/include/linux/stddef.h
> ./recipe-sysroot/usr/include/stddef.h
> ./git/src/basic/linux/stddef.h
>
>
>
> gcc includes the correct header because its order of searching headers is:
> #include <...> search starts here:
>  
> /srv/storage/alex/yocto/build-musl-arm-64/tmp/work/cortexa57-poky-linux-musl/systemd-boot/253.1-r0/git/src/fundamental
>  
> /srv/storage/alex/yocto/build-musl-arm-64/tmp/work/cortexa57-poky-linux-musl/systemd-boot/253.1-r0/git/src/boot/efi
>  
> /srv/storage/alex/yocto/build-musl-arm-64/tmp/work/cortexa57-poky-linux-musl/systemd-boot/253.1-r0/recipe-sysroot/usr/include/efi/aarch64
>  
> /srv/storage/alex/yocto/build-musl-arm-64/tmp/work/cortexa57-poky-linux-musl/systemd-boot/253.1-r0/recipe-sysroot/usr/include/efi
>  
> /srv/storage/alex/yocto/build-musl-arm-64/tmp/work/cortexa57-poky-linux-musl/systemd-boot/253.1-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux-musl/../../lib/aarch64-poky-linux-musl/gcc/aarch64-poky-linux-musl/12.2.0/include
>  
> /srv/storage/alex/yocto/build-musl-arm-64/tmp/work/cortexa57-poky-linux-musl/systemd-boot/253.1-r0/recipe-sysroot/usr/lib/aarch64-poky-linux-musl/12.2.0/include
>  
> /srv/storage/alex/yocto/build-musl-arm-64/tmp/work/cortexa57-poky-linux-musl/systemd-boot/253.1-r0/recipe-sysroot/usr/include
> End of search list.
>
> clang includes the incorrect one:
>
> #include <...> search starts here:
>  
> /srv/storage/alex/yocto/build-musl-arm-64/tmp/work/cortexa57-poky-linux-musl/systemd-boot/253.1-r0/git/src/fundamental
>  
> /srv/storage/alex/yocto/build-musl-arm-64/tmp/work/cortexa57-poky-linux-musl/systemd-boot/253.1-r0/git/src/boot/efi
>  
> /srv/storage/alex/yocto/build-musl-arm-64/tmp/work/cortexa57-poky-linux-musl/systemd-boot/253.1-r0/recipe-sysroot/usr/include/efi/aarch64
>  
> /srv/storage/alex/yocto/build-musl-arm-64/tmp/work/cortexa57-poky-linux-musl/systemd-boot/253.1-r0/recipe-sysroot/usr/include/efi
>  
> /srv/storage/alex/yocto/build-musl-arm-64/tmp/work/cortexa57-poky-linux-musl/systemd-boot/253.1-r0/recipe-sysroot/usr/include
>  
> /srv/storage/alex/yocto/build-musl-arm-64/tmp/work/cortexa57-poky-linux-musl/systemd-boot/253.1-r0/recipe-sysroot-native/usr/lib/clang/15.0.7/include
> End of search list.
>

This is working as intended, unlike glibc, musl provides stddef.h and
it wants musl based platforms to use that,
OE clang won't do that when the selected libc is glibc.

> So I'd say the search order needs to be aligned with gcc, rather than
> having to patch around the issue.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#178405): 
https://lists.openembedded.org/g/openembedded-core/message/178405
Mute This Topic: https://lists.openembedded.org/mt/97555854/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] systemd: Fix musl fix patch

2023-03-12 Thread Khem Raj
On Sun, Mar 12, 2023 at 10:50 AM Alexander Kanavin
 wrote:
>
> Right, but what is the specific trigger for the error you are seeing that 
> requires this additional definition, compared to passing musl tests with gcc?
>
>  I’d like to understand that because your change should not be necessary and 
> I’ve had a long argument with upstream even for the existing patch.
>

alltypes.h is generated by musl during its build which is used by all
system headers on musl systems it contains

#if defined(__NEED_wchar_t) && !defined(__DEFINED_wchar_t)
typedef unsigned wchar_t;
#define __DEFINED_wchar_t
#endif

stddef.h defines __NEED_wchar_t which is included from efi-string.h
and stddef.h immediately includes alltypes.h. so unless somewhere
__DEFINED_wchar_t
is pre-defined above will be included and that's what the problem is.

The patch you created makes efi-string.c to type define wchar_t before
including efi-string.h without blocking all possible ways for it to be
defined by system headers.
Hope that makes it clear.

> Alex
>
> On Sun 12. Mar 2023 at 17.59, Khem Raj  wrote:
>>
>>
>>
>> On Sat, Mar 11, 2023 at 11:30 PM Alexander Kanavin  
>> wrote:
>>>
>>> How can the issue be triggered? I did test this on musl, and so did
>>> the autobuilder.
>>
>>
>> My setup is clang/musl on imx8
>> Which is similar to qemuarm64
>> And build works for systemd but
>> Fails for systemd-boot recipe
>>
>>>
>>>
>>> Alex
>>>
>>> On Sun, 12 Mar 2023 at 08:24, Khem Raj  wrote:
>>> >
>>> > Current patch with fail when stdint.h is in include path before this
>>> > typedef which can also happen with re-includes. Therefore shunt that
>>> > by defining __DEFINED_wchar_t which helps musl builds of systemd-boot
>>> > recipe
>>> >
>>> > Signed-off-by: Khem Raj 
>>> > Cc: Alexander Kanavin 
>>> > ---
>>> >  ...rc-boot-efi-efi-string.c-define-wchar_t-from-__WCHA.patch | 5 ++---
>>> >  1 file changed, 2 insertions(+), 3 deletions(-)
>>> >
>>> > diff --git 
>>> > a/meta/recipes-core/systemd/systemd/0004-src-boot-efi-efi-string.c-define-wchar_t-from-__WCHA.patch
>>> >  
>>> > b/meta/recipes-core/systemd/systemd/0004-src-boot-efi-efi-string.c-define-wchar_t-from-__WCHA.patch
>>> > index 927f914848..43173ac32d 100644
>>> > --- 
>>> > a/meta/recipes-core/systemd/systemd/0004-src-boot-efi-efi-string.c-define-wchar_t-from-__WCHA.patch
>>> > +++ 
>>> > b/meta/recipes-core/systemd/systemd/0004-src-boot-efi-efi-string.c-define-wchar_t-from-__WCHA.patch
>>> > @@ -21,17 +21,16 @@ Signed-off-by: Alexander Kanavin 
>>> >   src/boot/efi/efi-string.c | 5 +
>>> >   1 file changed, 5 insertions(+)
>>> >
>>> > -diff --git a/src/boot/efi/efi-string.c b/src/boot/efi/efi-string.c
>>> > -index 22923d60f6..22a8d1ef71 100644
>>> >  --- a/src/boot/efi/efi-string.c
>>> >  +++ b/src/boot/efi/efi-string.c
>>> > -@@ -2,7 +2,12 @@
>>> > +@@ -2,7 +2,13 @@
>>> >
>>> >   #include 
>>> >   #include 
>>> >  +
>>> >  +#if SD_BOOT
>>> >  +typedef __WCHAR_TYPE__ wchar_t;
>>> > ++#define __DEFINED_wchar_t
>>> >  +#else
>>> >   #include 
>>> >  +#endif
>>> > --
>>> > 2.39.2
>>> >

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#178402): 
https://lists.openembedded.org/g/openembedded-core/message/178402
Mute This Topic: https://lists.openembedded.org/mt/97555854/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] systemd: Fix musl fix patch

2023-03-12 Thread Khem Raj
On Sat, Mar 11, 2023 at 11:30 PM Alexander Kanavin 
wrote:

> How can the issue be triggered? I did test this on musl, and so did
> the autobuilder.


My setup is clang/musl on imx8
Which is similar to qemuarm64
And build works for systemd but
Fails for systemd-boot recipe


>
> Alex
>
> On Sun, 12 Mar 2023 at 08:24, Khem Raj  wrote:
> >
> > Current patch with fail when stdint.h is in include path before this
> > typedef which can also happen with re-includes. Therefore shunt that
> > by defining __DEFINED_wchar_t which helps musl builds of systemd-boot
> > recipe
> >
> > Signed-off-by: Khem Raj 
> > Cc: Alexander Kanavin 
> > ---
> >  ...rc-boot-efi-efi-string.c-define-wchar_t-from-__WCHA.patch | 5 ++---
> >  1 file changed, 2 insertions(+), 3 deletions(-)
> >
> > diff --git
> a/meta/recipes-core/systemd/systemd/0004-src-boot-efi-efi-string.c-define-wchar_t-from-__WCHA.patch
> b/meta/recipes-core/systemd/systemd/0004-src-boot-efi-efi-string.c-define-wchar_t-from-__WCHA.patch
> > index 927f914848..43173ac32d 100644
> > ---
> a/meta/recipes-core/systemd/systemd/0004-src-boot-efi-efi-string.c-define-wchar_t-from-__WCHA.patch
> > +++
> b/meta/recipes-core/systemd/systemd/0004-src-boot-efi-efi-string.c-define-wchar_t-from-__WCHA.patch
> > @@ -21,17 +21,16 @@ Signed-off-by: Alexander Kanavin  >
> >   src/boot/efi/efi-string.c | 5 +
> >   1 file changed, 5 insertions(+)
> >
> > -diff --git a/src/boot/efi/efi-string.c b/src/boot/efi/efi-string.c
> > -index 22923d60f6..22a8d1ef71 100644
> >  --- a/src/boot/efi/efi-string.c
> >  +++ b/src/boot/efi/efi-string.c
> > -@@ -2,7 +2,12 @@
> > +@@ -2,7 +2,13 @@
> >
> >   #include 
> >   #include 
> >  +
> >  +#if SD_BOOT
> >  +typedef __WCHAR_TYPE__ wchar_t;
> > ++#define __DEFINED_wchar_t
> >  +#else
> >   #include 
> >  +#endif
> > --
> > 2.39.2
> >
>

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



[OE-core] [PATCH] systemd: Fix musl fix patch

2023-03-11 Thread Khem Raj
Current patch with fail when stdint.h is in include path before this
typedef which can also happen with re-includes. Therefore shunt that
by defining __DEFINED_wchar_t which helps musl builds of systemd-boot
recipe

Signed-off-by: Khem Raj 
Cc: Alexander Kanavin 
---
 ...rc-boot-efi-efi-string.c-define-wchar_t-from-__WCHA.patch | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git 
a/meta/recipes-core/systemd/systemd/0004-src-boot-efi-efi-string.c-define-wchar_t-from-__WCHA.patch
 
b/meta/recipes-core/systemd/systemd/0004-src-boot-efi-efi-string.c-define-wchar_t-from-__WCHA.patch
index 927f914848..43173ac32d 100644
--- 
a/meta/recipes-core/systemd/systemd/0004-src-boot-efi-efi-string.c-define-wchar_t-from-__WCHA.patch
+++ 
b/meta/recipes-core/systemd/systemd/0004-src-boot-efi-efi-string.c-define-wchar_t-from-__WCHA.patch
@@ -21,17 +21,16 @@ Signed-off-by: Alexander Kanavin 
  src/boot/efi/efi-string.c | 5 +
  1 file changed, 5 insertions(+)
 
-diff --git a/src/boot/efi/efi-string.c b/src/boot/efi/efi-string.c
-index 22923d60f6..22a8d1ef71 100644
 --- a/src/boot/efi/efi-string.c
 +++ b/src/boot/efi/efi-string.c
-@@ -2,7 +2,12 @@
+@@ -2,7 +2,13 @@
  
  #include 
  #include 
 +
 +#if SD_BOOT
 +typedef __WCHAR_TYPE__ wchar_t;
++#define __DEFINED_wchar_t
 +#else
  #include 
 +#endif
-- 
2.39.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#178376): 
https://lists.openembedded.org/g/openembedded-core/message/178376
Mute This Topic: https://lists.openembedded.org/mt/97555854/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 10/16] gawk: Fix ptest dependency

2023-03-10 Thread Khem Raj
On Fri, Mar 10, 2023 at 4:27 PM Richard Purdie
 wrote:
>
> The gawk ptests need some locale information, add the missing dependency
> so tests work in minimal images.
>
> Signed-off-by: Richard Purdie 
> ---
>  meta/recipes-extended/gawk/gawk_5.2.1.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-extended/gawk/gawk_5.2.1.bb 
> b/meta/recipes-extended/gawk/gawk_5.2.1.bb
> index fbe6e7040b0..d13110ddbec 100644
> --- a/meta/recipes-extended/gawk/gawk_5.2.1.bb
> +++ b/meta/recipes-extended/gawk/gawk_5.2.1.bb
> @@ -62,7 +62,7 @@ do_install_ptest() {
> rm -f ${D}${PTEST_PATH}/test/timeout.*
>  }
>
> -RDEPENDS:${PN}-ptest += "make"
> +RDEPENDS:${PN}-ptest += "make locale-base-en-us"
>

I think it should be added below so it does not break musl builds.

>  RDEPENDS:${PN}-ptest:append:libc-glibc = " locale-base-en-us.iso-8859-1"
>
> --
> 2.38.1
>
>
> 
>

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



[OE-core] [PATCH] systemd.bbclass: Add /usr/lib/systemd to searchpaths as well

2023-03-10 Thread Khem Raj
Some packages like lirc places its unit files into $systemd_user_unitdir
and also uses them in SYSTEMD_SERVICE list in recipe. This fails in
do_package

ERROR: Didn't find service unit 'lircmd.service', specified in 
SYSTEMD_SERVICE:lirc.

here lircmd.service is installed in /usr/lib/systemd/system/lircmd.service

Signed-off-by: Khem Raj 
---
 meta/classes-recipe/systemd.bbclass | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/classes-recipe/systemd.bbclass 
b/meta/classes-recipe/systemd.bbclass
index f9c92e6c2a..9a16babe43 100644
--- a/meta/classes-recipe/systemd.bbclass
+++ b/meta/classes-recipe/systemd.bbclass
@@ -152,6 +152,7 @@ python systemd_populate_packages() {
 def systemd_check_services():
 searchpaths = [oe.path.join(d.getVar("sysconfdir"), "systemd", 
"system"),]
 searchpaths.append(d.getVar("systemd_system_unitdir"))
+searchpaths.append(d.getVar("systemd_user_unitdir"))
 systemd_packages = d.getVar('SYSTEMD_PACKAGES')
 
 keys = 'Also'
-- 
2.39.2


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



Re: [OE-core] [PATCH] binutils: Enable --enable-new-dtags

2023-03-08 Thread Khem Raj
Awesome, thanks!  I think any recipe which is using
INHIBIT_DEFAULT_DEPENDENCIES could
run into these sorts of errors.

On Wed, Mar 8, 2023 at 3:53 AM Richard Purdie
 wrote:
>
> On Wed, 2023-03-08 at 09:33 +, Richard Purdie via
> lists.openembedded.org wrote:
> > On Wed, 2023-02-22 at 22:58 -0800, Khem Raj wrote:
> > > Use DT_RUNPATH over DT_RPATH. If DT_RUNPATH is present, LD_LIBRARY_PATH 
> > > is searched before
> > > DT_RUNPATH, Search order is DT_RPATH then LD_LIBRARY_PATH then
> > > DT_RUNPATH, this order ensures that injecting
> > > malicious shared objects is way harder with DT_RUNPATH.
> > >
> > > This is now default on major linux distributions already
> > >
> > > Signed-off-by: Khem Raj 
> > > ---
> > >  meta/recipes-devtools/binutils/binutils.inc | 1 +
> > >  1 file changed, 1 insertion(+)
> > >
> > > diff --git a/meta/recipes-devtools/binutils/binutils.inc 
> > > b/meta/recipes-devtools/binutils/binutils.inc
> > > index b2dbf241df..c69d29448f 100644
> > > --- a/meta/recipes-devtools/binutils/binutils.inc
> > > +++ b/meta/recipes-devtools/binutils/binutils.inc
> > > @@ -96,6 +96,7 @@ EXTRA_OECONF = "--program-prefix=${TARGET_PREFIX} \
> > >  --disable-werror \
> > >  --enable-deterministic-archives \
> > >  --enable-plugins \
> > > +--enable-new-dtags \
> > >  --disable-gdb \
> > >  --disable-gdbserver \
> > >  --disable-libdecnumber \
> >
> > FWIW I 100% agree we should look to enable this.
> >
> > Sadly, doing so exposes a bug where things that should rebuild don't.
> > That manifests as a failure in the reproducible test builds on the
> > autobuilder. I suspect a taskhash problem somewhere, maybe hash
> > equivalence, maybe somewhere else, hard to say without debugging it.
> >
> > I've been trying to get to this to help. The first issue was to sort
> > the other gdb issue this appeared to trigger but was in fact unrelated
> > and an issue from the recent binutils/gdb version upgrade. I've
> > debugged the initial buildtools tarball bug and re-deployed buildtools
> > on the infrastructure. That fixed some of the manifestations but not
> > all, I then debugged the remaining ones, worked out the regression in
> > upstream gdb and sent a patch yesterday which was merged upstream to
> > fix it.
> >
> > I am trying to get to helping with the problem this patch causes but
> > these things take a ton of time. Whilst I may get paid to work on the
> > project, I am one person and I'm getting pulled in a ridiculous number
> > of directions at once.
> >
> > People should worry this triggers a reproducibility issue, it means
> > there is a bug somewhere.
> >
> > I am hoping to get to this and to help try and debug it but the patch
> > cannot merge until we get to the bottom of the issue it triggers.
>
> I did have a look and the issue is actually fairly simple, glibc is
> missing a dependency directly on binutils. Most recipes have this
> magically, the magic is disabled for glibc as it is part of toolchain
> bootstrap and has to be manually curated.
>
> Adding the missing dependency appears to resolve things locally so I'll
> send out a patch and we'll have to run some autobuilder tests.
>
> Cheers,
>
> Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#178177): 
https://lists.openembedded.org/g/openembedded-core/message/178177
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] rpm: Fix hdr_hash function prototype

2023-03-03 Thread Khem Raj
Signed-off-by: Khem Raj 
---
 ...y_hash_t-instead-of-long-in-hdr_hash.patch | 35 +++
 meta/recipes-devtools/rpm/rpm_4.18.0.bb   |  1 +
 2 files changed, 36 insertions(+)
 create mode 100644 
meta/recipes-devtools/rpm/files/0001-python-Use-Py_hash_t-instead-of-long-in-hdr_hash.patch

diff --git 
a/meta/recipes-devtools/rpm/files/0001-python-Use-Py_hash_t-instead-of-long-in-hdr_hash.patch
 
b/meta/recipes-devtools/rpm/files/0001-python-Use-Py_hash_t-instead-of-long-in-hdr_hash.patch
new file mode 100644
index 00..d0e637191a
--- /dev/null
+++ 
b/meta/recipes-devtools/rpm/files/0001-python-Use-Py_hash_t-instead-of-long-in-hdr_hash.patch
@@ -0,0 +1,35 @@
+From 6ef189c45b763aedac5ef57ed6a5fc125fa95b41 Mon Sep 17 00:00:00 2001
+From: Khem Raj 
+Date: Fri, 3 Mar 2023 09:54:48 -0800
+Subject: [PATCH] python: Use Py_hash_t instead of long in hdr_hash
+
+Fixes
+python/header-py.c:744:2: error: incompatible function pointer types 
initializing 'hashfunc' (aka 'int (*)(struct _object *)') with an expression of 
type 'long (PyObject *)' (aka 'long (struct _object *)') 
[-Wincompatible-function-pointer-types]
+| hdr_hash,   /* tp_hash */
+| ^~~~
+
+Upstream-Status: Submitted 
[https://github.com/rpm-software-management/rpm/pull/2409]
+Signed-off-by: Khem Raj 
+---
+ python/header-py.c | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/python/header-py.c b/python/header-py.c
+index 0aed0c9267..c15503f359 100644
+--- a/python/header-py.c
 b/python/header-py.c
+@@ -316,9 +316,9 @@ static PyObject * hdr_dsOfHeader(PyObject * s)
+  "(Oi)", s, RPMTAG_NEVR);
+ }
+ 
+-static long hdr_hash(PyObject * h)
++static Py_hash_t hdr_hash(PyObject * h)
+ {
+-return (long) h;
++return (Py_hash_t) h;
+ }
+ 
+ static PyObject * hdr_reduce(hdrObject *s)
+-- 
+2.39.2
+
diff --git a/meta/recipes-devtools/rpm/rpm_4.18.0.bb 
b/meta/recipes-devtools/rpm/rpm_4.18.0.bb
index 61e395a9d0..be81c3eb08 100644
--- a/meta/recipes-devtools/rpm/rpm_4.18.0.bb
+++ b/meta/recipes-devtools/rpm/rpm_4.18.0.bb
@@ -39,6 +39,7 @@ SRC_URI = 
"git://github.com/rpm-software-management/rpm;branch=rpm-4.18.x;protoc

file://0001-build-pack.c-do-not-insert-payloadflags-into-.rpm-me.patch \

file://0001-configure.ac-add-linux-gnux32-variant-to-triplet-han.patch \
file://fifofix.patch \
+   file://0001-python-Use-Py_hash_t-instead-of-long-in-hdr_hash.patch \
"
 
 PE = "1"
-- 
2.39.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#178020): 
https://lists.openembedded.org/g/openembedded-core/message/178020
Mute This Topic: https://lists.openembedded.org/mt/97368566/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] libcomps: Fix callback function prototype for PyCOMPS_hash

2023-03-03 Thread Khem Raj
Signed-off-by: Khem Raj 
---
 ...hash_t-instead-of-long-in-PyCOMPS_ha.patch | 66 +++
 .../libcomps/libcomps_0.1.19.bb   |  1 +
 2 files changed, 67 insertions(+)
 create mode 100644 
meta/recipes-devtools/libcomps/libcomps/0001-libcomps-Use-Py_hash_t-instead-of-long-in-PyCOMPS_ha.patch

diff --git 
a/meta/recipes-devtools/libcomps/libcomps/0001-libcomps-Use-Py_hash_t-instead-of-long-in-PyCOMPS_ha.patch
 
b/meta/recipes-devtools/libcomps/libcomps/0001-libcomps-Use-Py_hash_t-instead-of-long-in-PyCOMPS_ha.patch
new file mode 100644
index 00..dd9ebc8af4
--- /dev/null
+++ 
b/meta/recipes-devtools/libcomps/libcomps/0001-libcomps-Use-Py_hash_t-instead-of-long-in-PyCOMPS_ha.patch
@@ -0,0 +1,66 @@
+From 26a9647c832de15248ee649e5b77075521f3d4f0 Mon Sep 17 00:00:00 2001
+From: Khem Raj 
+Date: Fri, 3 Mar 2023 08:37:35 -0800
+Subject: [PATCH] libcomps: Use Py_hash_t instead of long in PyCOMPS_hash()
+
+This function is used as a hashfunc callback in
+_typeobject defined python3.11/cpython/object.h
+compilers detect the protype mismatch for function pointers
+with clang16+
+
+Fixes
+libcomps/src/python/src/pycomps_sequence.c:667:5: error: incompatible function 
pointer types initializing 'hashfunc' (aka 'int (*)(struct _object *)') with an 
expression of type 'long (*)(PyObject *)' (aka 'long (*)(struct _object *)') 
[-Wincompatible-function-pointer-types]
+_hash, /*tp_hash */
+
+Upstream-Status: Submitted 
[https://github.com/rpm-software-management/libcomps/pull/101]
+Signed-off-by: Khem Raj 
+---
+ libcomps/src/python/src/pycomps_hash.c  | 4 ++--
+ libcomps/src/python/src/pycomps_hash.h  | 2 +-
+ libcomps/src/python/src/pycomps_utils.h | 2 +-
+ 3 files changed, 4 insertions(+), 4 deletions(-)
+
+diff --git a/libcomps/src/python/src/pycomps_hash.c 
b/libcomps/src/python/src/pycomps_hash.c
+index 474afd5..4577769 100644
+--- a/libcomps/src/python/src/pycomps_hash.c
 b/libcomps/src/python/src/pycomps_hash.c
+@@ -20,9 +20,9 @@
+ #include "pycomps_hash.h"
+ #include "pycomps_utils.h"
+ 
+-long PyCOMPS_hash(PyObject *self) {
++Py_hash_t PyCOMPS_hash(PyObject *self) {
+ char *cstr = NULL;
+-long crc;
++Py_hash_t crc;
+ 
+ cstr = comps_object_tostr(((PyCompsObject*)self)->c_obj);
+ crc = crc32(0, cstr, strlen(cstr));
+diff --git a/libcomps/src/python/src/pycomps_hash.h 
b/libcomps/src/python/src/pycomps_hash.h
+index b664cae..54e08d9 100644
+--- a/libcomps/src/python/src/pycomps_hash.h
 b/libcomps/src/python/src/pycomps_hash.h
+@@ -26,6 +26,6 @@
+ #include "pycomps_utils.h"
+ 
+ 
+-long PyCOMPS_hash(PyObject *self);
++Py_hash_t PyCOMPS_hash(PyObject *self);
+ 
+ #endif
+diff --git a/libcomps/src/python/src/pycomps_utils.h 
b/libcomps/src/python/src/pycomps_utils.h
+index ba9bc2f..b34e4dc 100644
+--- a/libcomps/src/python/src/pycomps_utils.h
 b/libcomps/src/python/src/pycomps_utils.h
+@@ -137,7 +137,7 @@ COMPS_Object* __pycomps_bytes_in(PyObject *pobj);
+ PyObject* __pycomps_str_out(COMPS_Object *obj);
+ PyObject *str_to_unicode(void* str);
+ 
+-long PyCOMPS_hash(PyObject *self);
++Py_hash_t PyCOMPS_hash(PyObject *self);
+ 
+ PyObject* PyCOMPSSeq_extra_get(PyObject *self, PyObject *key);
+ 
+-- 
+2.39.2
+
diff --git a/meta/recipes-devtools/libcomps/libcomps_0.1.19.bb 
b/meta/recipes-devtools/libcomps/libcomps_0.1.19.bb
index fa1fbc8f0d..f8063d9400 100644
--- a/meta/recipes-devtools/libcomps/libcomps_0.1.19.bb
+++ b/meta/recipes-devtools/libcomps/libcomps_0.1.19.bb
@@ -5,6 +5,7 @@ LICENSE = "GPL-2.0-only"
 LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
 
 SRC_URI = 
"git://github.com/rpm-software-management/libcomps.git;branch=master;protocol=https
 \
+   
file://0001-libcomps-Use-Py_hash_t-instead-of-long-in-PyCOMPS_ha.patch \
file://0002-Do-not-set-PYTHON_INSTALL_DIR-by-running-python.patch \
"
 
-- 
2.39.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#178019): 
https://lists.openembedded.org/g/openembedded-core/message/178019
Mute This Topic: https://lists.openembedded.org/mt/97366367/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] vte: Fix -Wenum-constexpr-conversion warning

2023-03-01 Thread Khem Raj
Signed-off-by: Khem Raj 
---
 ...ty.cc-Do-not-typecast-to-GSpawnFlags.patch | 58 +++
 meta/recipes-support/vte/vte_0.70.2.bb|  3 +-
 2 files changed, 60 insertions(+), 1 deletion(-)
 create mode 100644 
meta/recipes-support/vte/vte/0001-vtepty.cc-Do-not-typecast-to-GSpawnFlags.patch

diff --git 
a/meta/recipes-support/vte/vte/0001-vtepty.cc-Do-not-typecast-to-GSpawnFlags.patch
 
b/meta/recipes-support/vte/vte/0001-vtepty.cc-Do-not-typecast-to-GSpawnFlags.patch
new file mode 100644
index 00..16553b506f
--- /dev/null
+++ 
b/meta/recipes-support/vte/vte/0001-vtepty.cc-Do-not-typecast-to-GSpawnFlags.patch
@@ -0,0 +1,58 @@
+From 9c7654e063d65fb2645459a32fd14eebab484857 Mon Sep 17 00:00:00 2001
+From: Khem Raj 
+Date: Wed, 1 Mar 2023 15:50:26 -0800
+Subject: [PATCH] vtepty.cc: Do not typecast to GSpawnFlags
+
+GSpawnFlags is enum with max value 1 << 15 which means it fits into a
+short int, however here we are OR'ing VTE_SPAWN_* as well which have
+higher values
+
+Fixes error like
+src/vtepty.cc:577:16: error: integer value 234881535 is outside the valid 
range of values [0, 4095] for this enumeration type 
[-Wenum-constexpr-conversion]
+
+Fixes issue https://gitlab.gnome.org/GNOME/vte/-/issues/2618
+
+Upstream-Status: Submitted [https://gitlab.gnome.org/GNOME/vte/-/issues/2618]
+Signed-off-by: Khem Raj 
+---
+ src/vtepty.cc | 24 
+ 1 file changed, 12 insertions(+), 12 deletions(-)
+
+diff --git a/src/vtepty.cc b/src/vtepty.cc
+index 3aaa0d6b..2da2675f 100644
+--- a/src/vtepty.cc
 b/src/vtepty.cc
+@@ -574,18 +574,18 @@ catch (...)
+ static constexpr inline auto
+ all_spawn_flags() noexcept
+ {
+-return GSpawnFlags(G_SPAWN_LEAVE_DESCRIPTORS_OPEN |
+-   G_SPAWN_DO_NOT_REAP_CHILD |
+-   G_SPAWN_SEARCH_PATH |
+-   G_SPAWN_STDOUT_TO_DEV_NULL |
+-   G_SPAWN_STDERR_TO_DEV_NULL |
+-   G_SPAWN_CHILD_INHERITS_STDIN |
+-   G_SPAWN_FILE_AND_ARGV_ZERO |
+-   G_SPAWN_SEARCH_PATH_FROM_ENVP |
+-   G_SPAWN_CLOEXEC_PIPES |
+-   VTE_SPAWN_NO_PARENT_ENVV |
+-   VTE_SPAWN_NO_SYSTEMD_SCOPE |
+-   VTE_SPAWN_REQUIRE_SYSTEMD_SCOPE);
++return (G_SPAWN_LEAVE_DESCRIPTORS_OPEN |
++G_SPAWN_DO_NOT_REAP_CHILD |
++G_SPAWN_SEARCH_PATH |
++G_SPAWN_STDOUT_TO_DEV_NULL |
++G_SPAWN_STDERR_TO_DEV_NULL |
++G_SPAWN_CHILD_INHERITS_STDIN |
++G_SPAWN_FILE_AND_ARGV_ZERO |
++G_SPAWN_SEARCH_PATH_FROM_ENVP |
++G_SPAWN_CLOEXEC_PIPES |
++VTE_SPAWN_NO_PARENT_ENVV |
++VTE_SPAWN_NO_SYSTEMD_SCOPE |
++VTE_SPAWN_REQUIRE_SYSTEMD_SCOPE);
+ }
+ 
+ static constexpr inline auto
+-- 
+2.39.2
+
diff --git a/meta/recipes-support/vte/vte_0.70.2.bb 
b/meta/recipes-support/vte/vte_0.70.2.bb
index ec2fb1f522..001f413c19 100644
--- a/meta/recipes-support/vte/vte_0.70.2.bb
+++ b/meta/recipes-support/vte/vte_0.70.2.bb
@@ -20,7 +20,8 @@ GIDOCGEN_MESON_OPTION = "docs"
 inherit gnomebase gi-docgen features_check upstream-version-is-even 
gobject-introspection
 
 # 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 += "file://0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch \
+file://0001-vtepty.cc-Do-not-typecast-to-GSpawnFlags.patch"
 SRC_URI[archive.sha256sum] = 
"4d15b4380de3f564d57eabd006389c407c705df5b0c70030fdcc24971a334d80"
 
 ANY_OF_DISTRO_FEATURES = "${GTK3DISTROFEATURES}"
-- 
2.39.2


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

2023-03-01 Thread Khem Raj
Here is list of changes in this major release

https://github.com/riscv-software-src/opensbi/compare/v1.1...v1.2

Signed-off-by: Khem Raj 
---
 meta/recipes-bsp/opensbi/{opensbi_1.1.bb => opensbi_1.2.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-bsp/opensbi/{opensbi_1.1.bb => opensbi_1.2.bb} (97%)

diff --git a/meta/recipes-bsp/opensbi/opensbi_1.1.bb 
b/meta/recipes-bsp/opensbi/opensbi_1.2.bb
similarity index 97%
rename from meta/recipes-bsp/opensbi/opensbi_1.1.bb
rename to meta/recipes-bsp/opensbi/opensbi_1.2.bb
index d3a6296533..a088fef419 100644
--- a/meta/recipes-bsp/opensbi/opensbi_1.1.bb
+++ b/meta/recipes-bsp/opensbi/opensbi_1.2.bb
@@ -8,7 +8,7 @@ require opensbi-payloads.inc
 
 inherit autotools-brokensep deploy
 
-SRCREV = "4489876e933d8ba0d8bc6c64bae71e295d45faac"
+SRCREV = "6b5188ca14e59ce7bf71afe4e7d3d557c3d31bf8"
 SRC_URI = "git://github.com/riscv/opensbi.git;branch=master;protocol=https"
 
 S = "${WORKDIR}/git"
-- 
2.39.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177883): 
https://lists.openembedded.org/g/openembedded-core/message/177883
Mute This Topic: https://lists.openembedded.org/mt/97311386/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] opensbi: Do not add dependencies if RISCV_SBI_FDT is not set

2023-03-01 Thread Khem Raj
Dependencies only make sense when opensbi is being used to deliver
payload which maybe an artifact of kernel or u-boot, otherwise it should
be not added. This avoids circular dependencies when RISCV machines do
not define RISCV_SBI_PAYLOAD but do define RISCV_SBI_FDT

Signed-off-by: Khem Raj 
---
 meta/recipes-bsp/opensbi/opensbi-payloads.inc | 12 +++-
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/meta/recipes-bsp/opensbi/opensbi-payloads.inc 
b/meta/recipes-bsp/opensbi/opensbi-payloads.inc
index e590a27573..a55679632e 100644
--- a/meta/recipes-bsp/opensbi/opensbi-payloads.inc
+++ b/meta/recipes-bsp/opensbi/opensbi-payloads.inc
@@ -1,13 +1,15 @@
 def riscv_get_extra_oemake_image(d):
 sbi_payload = d.getVar('RISCV_SBI_PAYLOAD')
-deploy_dir = d.getVar('DEPLOY_DIR_IMAGE')
-
 if sbi_payload is None:
 return ""
 
+deploy_dir = d.getVar('DEPLOY_DIR_IMAGE')
+
 return "FW_PAYLOAD_PATH=" + deploy_dir + "/" + sbi_payload
 
 def riscv_get_extra_oemake_fdt(d):
+if d.getVar('RISCV_SBI_PAYLOAD') is None:
+return ""
 sbi_fdt = d.getVar('RISCV_SBI_FDT')
 deploy_dir = d.getVar('DEPLOY_DIR_IMAGE')
 
@@ -18,11 +20,11 @@ def riscv_get_extra_oemake_fdt(d):
 
 def riscv_get_do_compile_depends(d):
 sbi_payload = d.getVar('RISCV_SBI_PAYLOAD') or ""
-sbi_fdt = d.getVar('RISCV_SBI_FDT') or ""
-
-if sbi_payload == "" and sbi_fdt == "":
+if sbi_payload == "":
 return ""
 
+sbi_fdt = d.getVar('RISCV_SBI_FDT') or ""
+
 if sbi_fdt != "" and 'u-boot.bin' in sbi_payload:
 return "virtual/kernel:do_deploy virtual/bootloader:do_deploy"
 
-- 
2.39.2


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



Re: [OE-core][dunfell][PATCH] gcc: Fix inconsistent noexcept specifier for valarray in libstdc++

2023-03-01 Thread Khem Raj
lgtm

On Tue, Feb 28, 2023 at 11:17 PM BINDU  wrote:
>
> From: Virendra Thakur 
>
> Backport of gcc upstream commit 2b2d97fc545635a0f6aa9c9ee3b017394bc494bf
> to gcc release 9.5.0. This fix is available to all release-branches
> except releases/gcc-9 because upstream do not support gcc-9 now.
>
> Signed-off-by: Virendra Thakur 
> ---
>  meta/recipes-devtools/gcc/gcc-9.5.inc |  1 +
>  ...nsistent-noexcept-specific-for-valar.patch | 44 +++
>  2 files changed, 45 insertions(+)
>  create mode 100644 
> meta/recipes-devtools/gcc/gcc-9.5/0002-libstdc-Fix-inconsistent-noexcept-specific-for-valar.patch
>
> diff --git a/meta/recipes-devtools/gcc/gcc-9.5.inc 
> b/meta/recipes-devtools/gcc/gcc-9.5.inc
> index 6a0a892b10..ec28246bf3 100644
> --- a/meta/recipes-devtools/gcc/gcc-9.5.inc
> +++ b/meta/recipes-devtools/gcc/gcc-9.5.inc
> @@ -69,6 +69,7 @@ SRC_URI = "\
> 
> file://0037-CVE-2019-14250-Check-zero-value-in-simple_object_elf.patch \
> 
> file://0038-gentypes-genmodes-Do-not-use-__LINE__-for-maintainin.patch \
> 
> file://0039-process_alt_operands-Don-t-match-user-defined-regs-o.patch \
> +   
> file://0002-libstdc-Fix-inconsistent-noexcept-specific-for-valar.patch \
>  "
>  S = "${TMPDIR}/work-shared/gcc-${PV}-${PR}/gcc-${PV}"
>  SRC_URI[sha256sum] = 
> "27769f64ef1d4cd5e2be8682c0c93f9887983e6cfd1a927ce5a0a2915a95cf8f"
> diff --git 
> a/meta/recipes-devtools/gcc/gcc-9.5/0002-libstdc-Fix-inconsistent-noexcept-specific-for-valar.patch
>  
> b/meta/recipes-devtools/gcc/gcc-9.5/0002-libstdc-Fix-inconsistent-noexcept-specific-for-valar.patch
> new file mode 100644
> index 00..506064bfc2
> --- /dev/null
> +++ 
> b/meta/recipes-devtools/gcc/gcc-9.5/0002-libstdc-Fix-inconsistent-noexcept-specific-for-valar.patch
> @@ -0,0 +1,44 @@
> +From 60d966708d7cf105dccf128d2b7a38b0b2580a1a Mon Sep 17 00:00:00 2001
> +From: Jonathan Wakely 
> +Date: Fri, 5 Nov 2021 21:42:20 +
> +Subject: [PATCH] libstdc++: Fix inconsistent noexcept-specific for valarray
> + begin/end
> +
> +These declarations should be noexcept after I added it to the
> +definitions in .
> +
> +libstdc++-v3/ChangeLog:
> +
> +   * include/bits/range_access.h (begin(valarray), end(valarray)):
> +   Add noexcept.
> +
> +(cherry picked from commit 2b2d97fc545635a0f6aa9c9ee3b017394bc494bf)
> +
> +Upstream-Status: Backport 
> [https://github.com/hkaelber/gcc/commit/2b2d97fc545635a0f6aa9c9ee3b017394bc494bf]
> +Signed-off-by: Virendra Thakur 
> +
> +---
> + libstdc++-v3/include/bits/range_access.h | 8 
> + 1 file changed, 4 insertions(+), 4 deletions(-)
> +
> +diff --git a/libstdc++-v3/include/bits/range_access.h 
> b/libstdc++-v3/include/bits/range_access.h
> +index 3d99ea92027..4736e75fda1 100644
> +--- a/libstdc++-v3/include/bits/range_access.h
>  b/libstdc++-v3/include/bits/range_access.h
> +@@ -101,10 +101,10 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
> +
> +   template class valarray;
> +   // These overloads must be declared for cbegin and cend to use them.
> +-  template _Tp* begin(valarray<_Tp>&);
> +-  template const _Tp* begin(const valarray<_Tp>&);
> +-  template _Tp* end(valarray<_Tp>&);
> +-  template const _Tp* end(const valarray<_Tp>&);
> ++  template _Tp* begin(valarray<_Tp>&) noexcept;
> ++  template const _Tp* begin(const valarray<_Tp>&) noexcept;
> ++  template _Tp* end(valarray<_Tp>&) noexcept;
> ++  template const _Tp* end(const valarray<_Tp>&) noexcept;
> +
> +   /**
> +*  @brief  Return an iterator pointing to the first element of
> +--
> +2.25.1
> \ No newline at end of file
> --
> 2.25.1
>
>
> 
>

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



[OE-core] [PATCH] kernel: Add kernel specific OBJDUMP

2023-02-28 Thread Khem Raj
This helps in switching toolchains cleanly for kernel build
between gcc and clang

Currently, some kernels allow building with clang but not all
the distro might use clang as default system compiler but kernel
may demand gcc which is provided via KERNEL_* variables, however
kernel does use OBJCOPY at places during build and it maybe set
to use llvm objcopy when using clang. That should be a deliberate
setting when clang is used for kernel as well, otherwise it should
use binutils provided objcopy

Signed-off-by: Khem Raj 
Cc: Bruce Ashfield 
---
 meta/classes-recipe/kernel-arch.bbclass  | 3 +++
 meta/classes-recipe/kernel-devicetree.bbclass| 2 +-
 meta/classes-recipe/kernel-uboot.bbclass | 2 +-
 meta/classes-recipe/kernel-yocto.bbclass | 4 +++-
 meta/classes-recipe/kernel.bbclass   | 2 +-
 meta/classes-recipe/module.bbclass   | 5 +++--
 meta/recipes-kernel/make-mod-scripts/make-mod-scripts_1.0.bb | 3 ++-
 meta/recipes-kernel/systemtap/systemtap-uprobes_git.bb   | 4 ++--
 8 files changed, 16 insertions(+), 9 deletions(-)

diff --git a/meta/classes-recipe/kernel-arch.bbclass 
b/meta/classes-recipe/kernel-arch.bbclass
index 777f900241..5877048916 100644
--- a/meta/classes-recipe/kernel-arch.bbclass
+++ b/meta/classes-recipe/kernel-arch.bbclass
@@ -68,9 +68,12 @@ TARGET_LD_KERNEL_ARCH ?= ""
 HOST_LD_KERNEL_ARCH ?= "${TARGET_LD_KERNEL_ARCH}"
 TARGET_AR_KERNEL_ARCH ?= ""
 HOST_AR_KERNEL_ARCH ?= "${TARGET_AR_KERNEL_ARCH}"
+TARGET_OBJCOPY_KERNEL_ARCH ?= ""
+HOST_OBJCOPY_KERNEL_ARCH ?= "${TARGET_OBJCOPY_KERNEL_ARCH}"
 
 KERNEL_CC = "${CCACHE}${HOST_PREFIX}gcc ${HOST_CC_KERNEL_ARCH} -fuse-ld=bfd 
${DEBUG_PREFIX_MAP} -fdebug-prefix-map=${STAGING_KERNEL_DIR}=${KERNEL_SRC_PATH} 
-fdebug-prefix-map=${STAGING_KERNEL_BUILDDIR}=${KERNEL_SRC_PATH}"
 KERNEL_LD = "${CCACHE}${HOST_PREFIX}ld.bfd ${HOST_LD_KERNEL_ARCH}"
 KERNEL_AR = "${CCACHE}${HOST_PREFIX}ar ${HOST_AR_KERNEL_ARCH}"
+KERNEL_OBJCOPY = "${CCACHE}${HOST_PREFIX}objcopy ${HOST_OBJCOPY_KERNEL_ARCH}"
 TOOLCHAIN ?= "gcc"
 
diff --git a/meta/classes-recipe/kernel-devicetree.bbclass 
b/meta/classes-recipe/kernel-devicetree.bbclass
index b2117de805..4d0ecb1032 100644
--- a/meta/classes-recipe/kernel-devicetree.bbclass
+++ b/meta/classes-recipe/kernel-devicetree.bbclass
@@ -68,7 +68,7 @@ do_compile:append() {
 
for dtbf in ${KERNEL_DEVICETREE}; do
dtb=`normalize_dtb "$dtbf"`
-   oe_runmake $dtb CC="${KERNEL_CC} $cc_extra " LD="${KERNEL_LD}" 
${KERNEL_EXTRA_ARGS}
+   oe_runmake $dtb CC="${KERNEL_CC} $cc_extra " LD="${KERNEL_LD}" 
OBJCOPY="${KERNEL_OBJCOPY}" ${KERNEL_EXTRA_ARGS}
done
 }
 
diff --git a/meta/classes-recipe/kernel-uboot.bbclass 
b/meta/classes-recipe/kernel-uboot.bbclass
index 4aab02671e..30a85ccc28 100644
--- a/meta/classes-recipe/kernel-uboot.bbclass
+++ b/meta/classes-recipe/kernel-uboot.bbclass
@@ -34,7 +34,7 @@ uboot_prep_kimage() {
linux_comp="${FIT_KERNEL_COMP_ALG}"
fi
 
-   [ -n "${vmlinux_path}" ] && ${OBJCOPY} -O binary -R .note -R .comment 
-S "${vmlinux_path}" linux.bin
+   [ -n "${vmlinux_path}" ] && ${KERNEL_OBJCOPY} -O binary -R .note -R 
.comment -S "${vmlinux_path}" linux.bin
 
if [ "${linux_comp}" != "none" ] ; then
if [ "${linux_comp}" = "gzip" ] ; then
diff --git a/meta/classes-recipe/kernel-yocto.bbclass 
b/meta/classes-recipe/kernel-yocto.bbclass
index 7de99cff56..108b7e6752 100644
--- a/meta/classes-recipe/kernel-yocto.bbclass
+++ b/meta/classes-recipe/kernel-yocto.bbclass
@@ -455,7 +455,7 @@ do_kernel_configme() {
bbfatal_log "Could not find configuration queue 
(${meta_dir}/config.queue)"
fi
 
-   CFLAGS="${CFLAGS} ${TOOLCHAIN_OPTIONS}" HOSTCC="${BUILD_CC} 
${BUILD_CFLAGS} ${BUILD_LDFLAGS}" HOSTCPP="${BUILD_CPP}" CC="${KERNEL_CC}" 
LD="${KERNEL_LD}" ARCH=${ARCH} merge_config.sh -O ${B} ${config_flags} 
${configs} > ${meta_dir}/cfg/merge_config_build.log 2>&1
+   CFLAGS="${CFLAGS} ${TOOLCHAIN_OPTIONS}" HOSTCC="${BUILD_CC} 
${BUILD_CFLAGS} ${BUILD_LDFLAGS}" HOSTCPP="${BUILD_CPP}" CC="${KERNEL_CC}" 
LD="${KERNEL_LD}" OBJCOPY="${KERNEL_OBJCOPY}" ARCH=${ARCH} merge_config.sh -O 
${B} ${config_flags} ${configs} > ${meta_dir}/cfg/merge_config_build.log 2>&1
if [ $? -ne 0 -o ! -f ${B}/.config ]; then
bberror "Could not generate a .config for 
${KMACHINE}-${LINUX_KERNEL_TYPE}"
if [ ${KCONF_AUDIT_LEVEL} -gt 1 ]; then
@@ -

Re: [OE-core] [PATCH] binutils: Enable --enable-new-dtags

2023-02-28 Thread Khem Raj
On Tue, Feb 28, 2023 at 8:18 AM Alexandre Belloni
 wrote:
>
> Hello Khem,
>
> As discussed I gave it a go again and got this:
>
> | /home/pokybuild/yocto-worker/qemuarm/build/build/tmp/hosttools/ld: 
> linux-tdep.o: in function `linux_corefile_thread(thread_info*, 
> linux_corefile_thread_data*)':
> | linux-tdep.c:(.text+0x13ac): undefined reference to 
> `gcore_elf_build_thread_register_notes(gdbarch*, thread_info*, gdb_signal, 
> bfd*, std::unique_ptr >*, int*)'
> | /home/pokybuild/yocto-worker/qemuarm/build/build/tmp/hosttools/ld: 
> linux-tdep.o: in function `linux_make_corefile_notes(gdbarch*, bfd*, int*)':
> | linux-tdep.c:(.text+0x49d7): undefined reference to 
> `gcore_elf_make_tdesc_note(bfd*, std::unique_ptr gdb::xfree_deleter >*, int*)'
> | collect2: error: ld returned 1 exit status
> | make[2]: *** [Makefile:2149: gdb] Error 1
> | make[2]: Leaving directory 
> '/home/pokybuild/yocto-worker/qemuarm/build/build/tmp/work/x86_64-linux/gdb-cross-arm/13.1-r0/build-arm-poky-linux-gnueabi/gdb'
> | make[1]: *** [Makefile:11122: all-gdb] Error 2
> | make[1]: Leaving directory 
> '/home/pokybuild/yocto-worker/qemuarm/build/build/tmp/work/x86_64-linux/gdb-cross-arm/13.1-r0/build-arm-poky-linux-gnueabi'
> | make: *** [Makefile:1005: all] Error 2
> | ERROR: oe_runmake failed

Is this host running updated buildtools tarball after the binutils ld
search path fix ?

>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/53/builds/6741/steps/14/logs/stdio
>
> I already reported it on the gdb upgrade:
>
> https://lists.openembedded.org/g/openembedded-core/topic/97152035#177576
>
>
> On 22/02/2023 22:58:16-0800, Khem Raj wrote:
> > Use DT_RUNPATH over DT_RPATH. If DT_RUNPATH is present, LD_LIBRARY_PATH is 
> > searched before
> > DT_RUNPATH, Search order is DT_RPATH then LD_LIBRARY_PATH then
> > DT_RUNPATH, this order ensures that injecting
> > malicious shared objects is way harder with DT_RUNPATH.
> >
> > This is now default on major linux distributions already
> >
> > Signed-off-by: Khem Raj 
> > ---
> >  meta/recipes-devtools/binutils/binutils.inc | 1 +
> >  1 file changed, 1 insertion(+)
> >
> > diff --git a/meta/recipes-devtools/binutils/binutils.inc 
> > b/meta/recipes-devtools/binutils/binutils.inc
> > index b2dbf241df..c69d29448f 100644
> > --- a/meta/recipes-devtools/binutils/binutils.inc
> > +++ b/meta/recipes-devtools/binutils/binutils.inc
> > @@ -96,6 +96,7 @@ EXTRA_OECONF = "--program-prefix=${TARGET_PREFIX} \
> >  --disable-werror \
> >  --enable-deterministic-archives \
> >  --enable-plugins \
> > +--enable-new-dtags \
> >  --disable-gdb \
> >  --disable-gdbserver \
> >  --disable-libdecnumber \
> > --
> > 2.39.2
> >
>
> >
> > 
> >
>
>
> --
> Alexandre Belloni, co-owner and COO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com

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



Re: [OE-core] [PATCH] binutils: Enable --enable-new-dtags

2023-02-26 Thread Khem Raj
On Thu, Feb 23, 2023 at 5:56 PM Khem Raj  wrote:
>
> On Thu, Feb 23, 2023 at 3:34 PM Alexandre Belloni
>  wrote:
> >
> > Could this be the cause of this?
> >
> > https://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20230223-79c9rmcw/packages/diff-html/
>
> most likely yes. I will take a look. Lets work on merging the other
> binutils and gdb upgrade patch meanwhile.

I looked at the diffoscope outputs you posted and it is noting the
difference in EFL flags

changing from
 0x0018 (BIND_NOW)
to
 0x001e (FLAGS)  BIND_NOW

However, in my local build I see that when I enable --enable-new-dtags
 than I always get
 0x001e (FLAGS)  BIND_NOW


but when I check the glibc builds without the patch then I get flags
to be 0x0018

So I wonder if we are comparing previously built glibc ( using
binutils without this patch )
with glibc compiled with binutils using this patch.

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

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13): 
https://lists.openembedded.org/g/openembedded-core/message/13
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] musl: Update to tip of trunk

2023-02-24 Thread Khem Raj
This brings in following changes

* 7d756e1c (upstream/master, origin/master) dns: prefer monotonic clock for 
timeouts
* 07616721 fix return value of wcs{,n}cmp for extreme wchar_t values
* 35fdfe62 math: fix undefined shift in logf
* 7e13e5ae inet_pton: fix uninitialized memory use for IPv4-mapped IPv6 
addresses
* 7e6da7ac hsearch: fix null pointer arithmetic UB
* f79b973d increase sendmsg internal buffer to support SCM_MAX_FD
* 0ab97350 mq_notify: block all (application) signals in the worker thread
* 711673ee mq_notify: join worker thread before returning in error path
* 8c0c9c69 mq_notify: rework to fix use-after-close/double-close bugs
* fde6891e mq_notify: use semaphore instead of barrier to sync args consumption
* c3cd04fa fix pthread_detach inadvertently acting as cancellation point in 
race case
* 115149c0 powerpc-sf longjmp clobbering of val argument
* 5763f003 riscv64: add vfork
* 269d1938 fix wrong sigaction syscall ABI on mips*, or1k, microblaze, riscv64
* ea3b40a3 fix integer overflow in WIFSTOPPED macro
* f897461d fix debugger tracking of shared libraries on mips with PIE main 
program
* a4b0a665 expose memmem under baseline POSIX feature profile
* 9532ae13 use libc-internal malloc for pthread_atfork
* 7d358599 prevent invalid reads of nl_arg in printf_core
* c5f4b2df elf.h: add ELFCOMPRESS_ZSTD
* 159d1f6c semaphores: fix missed wakes from ABA bug in waiter count logic

Signed-off-by: Khem Raj 
---
 meta/recipes-core/musl/musl_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-core/musl/musl_git.bb 
b/meta/recipes-core/musl/musl_git.bb
index 7749495ec6..39f6dd8219 100644
--- a/meta/recipes-core/musl/musl_git.bb
+++ b/meta/recipes-core/musl/musl_git.bb
@@ -4,7 +4,7 @@
 require musl.inc
 inherit linuxloader
 
-SRCREV = "f47a8cdd250d9163fcfb39bf4e9d813957c0b187"
+SRCREV = "7d756e1c04de6eb3f2b3d3e1141a218bb329fcfb"
 
 BASEVER = "1.2.3"
 
-- 
2.39.2


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



Re: [OE-core] [PATCH] binutils: Enable --enable-new-dtags

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

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

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

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



[OE-core] [PATCH] grub: Handle R_RISCV_CALL_PLT reloc

2023-02-23 Thread Khem Raj
These are new in binutils 2.40+

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

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

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


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



[OE-core] [PATCH] tune-riscv.inc: Add riscv64nc to available tunes list

2023-02-23 Thread Khem Raj
This was missed when riscv64nc was added

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

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


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



Re: [OE-core] [PATCH] binutils: Fix nativesdk ld.so search

2023-02-23 Thread Khem Raj
Thanks for the patch it seems ok to me
At least it’s not poking at build machine for ld.so.conf anymore

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

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

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



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

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

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

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

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



[OE-core] [PATCH] binutils: Enable --enable-new-dtags

2023-02-22 Thread Khem Raj
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]
-=-=-=-=-=-=-=-=-=-=-=-



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

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

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

2023-02-22 Thread Khem Raj
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_longjmp@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_dlopen_mode@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_pthread_init@GLIBC_PRIVATE'
collect2: error: ld returned 1 exit status
configure:28588: $? = 1



>
> 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 'disa

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

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

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

2023-02-22 Thread Khem Raj
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_re

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

2023-02-22 Thread Khem Raj
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]
-=-=-=-=-=-=-=-=-=-=-=-



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

2023-02-22 Thread Khem Raj
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 "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 ++--

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

2023-02-21 Thread Khem Raj
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 "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

 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 ++

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

2023-02-21 Thread Khem Raj
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 
---
 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 => 0004-use-asm-sgidefs.h.patch} |  9 ++---

Re: [OE-core] [PATCH 09/11] build-appliance-image: QB_MEM: allow user config

2023-02-21 Thread Khem Raj
On Tue, Feb 21, 2023 at 12:45 PM Trevor Woerner  wrote:
>
> Allow the user to specify a QB_MEM value of their choosing, otherwise set it
> to a default value.
>
> Signed-off-by: Trevor Woerner 
> ---
>  meta/recipes-core/images/build-appliance-image_15.0.0.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> 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 1f7b96a9fcf4..aa1e87763d57 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
> @@ -11,7 +11,7 @@ IMAGE_INSTALL = "packagegroup-core-boot 
> packagegroup-core-ssh-openssh packagegro
>
>  IMAGE_FEATURES += "x11-base package-management splash"
>
> -QB_MEM = '${@bb.utils.contains("DISTRO_FEATURES", "opengl", "-m 512", "-m 
> 256", d)}'
> +QB_MEM ?= '${@bb.utils.contains("DISTRO_FEATURES", "opengl", "-m 512", "-m 
> 256", d)}'
>

it would be good to see if we can say something like minimum memory
needed so it should be a fallback
if user sets higher value then it should use that. So for that matter
it looks its fine unless someone sets
QB_MEM < minmem then it will get some trouble.

>  # Ensure there's enough space to do a core-image-sato build, with rm_work 
> enabled
>  IMAGE_ROOTFS_EXTRA_SPACE = "41943040"
> --
> 2.36.0.rc2.17.g4027e30c53
>
>
> 
>

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

2023-02-21 Thread Khem Raj
On Tue, Feb 21, 2023 at 5:27 PM Randy MacLeod 
wrote:

> On 2022-05-12 15:28, Khem Raj wrote:
>
> Release Announcement [1] and Notes [2]
>
> [1] https://lists.gnu.org/archive/html/info-gnu/2022-05/msg0.html
> [2] 
> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=gdb/NEWS;hb=gdb-12.1-release
>
> I just noticed that gdb-13.1 was released 2 days ago (Feb 19, 2023) .
>
> It seems like a good candidate to be included in the 4.2 release.
>
> $ git diff gdb-12-branch  gdb-13-branch gdb | diffstat | tail -1
>  6222 files changed, 142614 insertions(+), 63875 deletions(-)
>
> and  notes linked below.
>
> Khem,
>
> Are you working on that or should someone else start on it?
>

I have branch for 13.x already so will send patches tonight

../Randy
>
>
> https://www.sourceware.org/gdb/download/ANNOUNCEMENT
>
> https://www.sourceware.org/gdb/
>
>
> Signed-off-by: Khem Raj  
> ---
>  meta/conf/distro/include/tcmode-default.inc|  2 +-
>  ...canadian_11.2.bb => gdb-cross-canadian_12.1.bb} |  0
>  .../gdb/{gdb-cross_11.2.bb => gdb-cross_12.1.bb}   |  0
>  meta/recipes-devtools/gdb/gdb.inc  | 14 +++---
>  ...0001-make-man-install-relative-to-DESTDIR.patch | 10 +-
>  ...s-linux-nat-Define-_ABIO32-if-not-defined.patch |  8 
>  ...Define-pt_regs-uapi_pt_regs-on-GLIBC-syst.patch | 11 +--
>  ...-libreadline.a-when-using-disable-static.patch} | 14 +++---
>  ...gidefs.h.patch => 0005-use-asm-sgidefs.h.patch} |  8 
>  ...AGS.patch => 0006-Change-order-of-CFLAGS.patch} | 10 +-
>  ...> 0007-resolve-restrict-keyword-conflict.patch} |  6 +++---
>  ...tch => 0008-Fix-invalid-sigprocmask-call.patch} |  8 
>  patch => 0009-gdbserver-ctrl-c-handling.patch} | 10 +-
>  .../gdb/{gdb_11.2.bb => gdb_12.1.bb}   |  0
>  14 files changed, 50 insertions(+), 51 deletions(-)
>  rename meta/recipes-devtools/gdb/{gdb-cross-canadian_11.2.bb => 
> gdb-cross-canadian_12.1.bb} (100%)
>  rename meta/recipes-devtools/gdb/{gdb-cross_11.2.bb => gdb-cross_12.1.bb} 
> (100%)
>  rename 
> meta/recipes-devtools/gdb/gdb/{0005-Dont-disable-libreadline.a-when-using-disable-static.patch
>  => 0004-Dont-disable-libreadline.a-when-using-disable-static.patch} (80%)
>  rename meta/recipes-devtools/gdb/gdb/{0006-use-asm-sgidefs.h.patch => 
> 0005-use-asm-sgidefs.h.patch} (84%)
>  rename meta/recipes-devtools/gdb/gdb/{0007-Change-order-of-CFLAGS.patch => 
> 0006-Change-order-of-CFLAGS.patch} (80%)
>  rename 
> meta/recipes-devtools/gdb/gdb/{0008-resolve-restrict-keyword-conflict.patch 
> => 0007-resolve-restrict-keyword-conflict.patch} (93%)
>  rename 
> meta/recipes-devtools/gdb/gdb/{0009-Fix-invalid-sigprocmask-call.patch => 
> 0008-Fix-invalid-sigprocmask-call.patch} (90%)
>  rename meta/recipes-devtools/gdb/gdb/{0010-gdbserver-ctrl-c-handling.patch 
> => 0009-gdbserver-ctrl-c-handling.patch} (82%)
>  rename meta/recipes-devtools/gdb/{gdb_11.2.bb => gdb_12.1.bb} (100%)
>
> diff --git a/meta/conf/distro/include/tcmode-default.inc 
> b/meta/conf/distro/include/tcmode-default.inc
> index 9660f2804a7..1179ba172ff 100644
> --- a/meta/conf/distro/include/tcmode-default.inc
> +++ b/meta/conf/distro/include/tcmode-default.inc
> @@ -19,7 +19,7 @@ PREFERRED_PROVIDER_virtual/gettext ??= "gettext"
>  GCCVERSION ?= "12.%"
>  SDKGCCVERSION ?= "${GCCVERSION}"
>  BINUVERSION ?= "2.38%"
> -GDBVERSION ?= "11.%"
> +GDBVERSION ?= "12.%"
>  GLIBCVERSION ?= "2.35"
>  LINUXLIBCVERSION ?= "5.16%"
>  QEMUVERSION ?= "7.0%"
> diff --git a/meta/recipes-devtools/gdb/gdb-cross-canadian_11.2.bb 
> b/meta/recipes-devtools/gdb/gdb-cross-canadian_12.1.bb
> similarity index 100%
> rename from meta/recipes-devtools/gdb/gdb-cross-canadian_11.2.bb
> rename to meta/recipes-devtools/gdb/gdb-cross-canadian_12.1.bb
> diff --git a/meta/recipes-devtools/gdb/gdb-cross_11.2.bb 
> b/meta/recipes-devtools/gdb/gdb-cross_12.1.bb
> similarity index 100%
> rename from meta/recipes-devtools/gdb/gdb-cross_11.2.bb
> rename to meta/recipes-devtools/gdb/gdb-cross_12.1.bb
> diff --git a/meta/recipes-devtools/gdb/gdb.inc 
> b/meta/recipes-devtools/gdb/gdb.inc
> index 649ee287276..3b569fd40e7 100644
> --- a/meta/recipes-devtools/gdb/gdb.inc
> +++ b/meta/recipes-devtools/gdb/gdb.inc
> @@ -8,11 +8,11 @@ SRC_URI = "${GNU_MIRROR}/gdb/gdb-${PV}.tar.xz \
> file://0001-make-man-install-relative-to-DESTDIR.patch \
> file://0002-mips-linux-nat-Define-_ABIO32-if-not-defined.patch \
> 
> file://0003-ppc-ptrace-Define-pt_regs-

Re: [OE-core] [RFC][PATCH] libssh2: Update patch to apply and fix malformed Upstream-Status

2023-02-15 Thread Khem Raj
On Wed, Feb 15, 2023 at 12:46 PM Martin Jansa  wrote:
>
> patchreview.py will care about the space (like insane.bbclass does) if 
> https://lists.openembedded.org/g/openembedded-core/message/177207 is merged
>

I see. thanks. I think this should be something every developer should
then be able to run on the patchset they are about to post for review.
Otherwise, it just
add on to upstreaming friction that developer experiences and it won't scale.

> On Wed, Feb 15, 2023 at 9:35 PM Khem Raj  wrote:
>>
>> On Wed, Feb 15, 2023 at 11:26 AM Khem Raj  wrote:
>> >
>> > On Wed, Feb 15, 2023 at 9:18 AM Martin Jansa  
>> > wrote:
>> > >
>> > > * I've noticed this, because patchreview.py reports Malformed
>> > >   Upstream-Status in this one now, but the QA check in insane.bbclass
>> > >   wasn't reporting it before
>> > >
>> > > * the reason why insane.bbclass doesn't report it is because:
>> > >   SRC_URI:append:ptest = " 
>> > > file://0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch"
>> > >   doesn't work and probably never did as "ptest" is not an override
>> > >   and patch-status-core checks only the .patch files which are really
>> > >   in SRC_URI.
>> > >
>> > > * I've added it directly to SRC_URI and it also didn't apply:
>> > >   http://errors.yoctoproject.org/Errors/Details/689955/
>> > >   as the "endif" at the end was removed in 1.10.0 version:
>> > >   
>> > > https://github.com/libssh2/libssh2/commit/ecd6a74e44562797a1e92186ad4a402c5641720e#diff-32103f666ff2fb42b025a47ccf1b959bbcc6db89f217e5943b1de73c81a4f9db
>> > >
>> > >   after updating the patch to apply I got expected patch-status-core 
>> > > failure:
>> > >   http://errors.yoctoproject.org/Errors/Details/689956/
>> > >   ERROR: QA Issue: Malformed Upstream-Status in patch
>> > >   
>> > > TOPDIR/openembedded-core/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch
>> > >   Please correct according to 
>> > > https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#Patch_Header_Recommendations:_Upstream-Status
>> > >  :
>> > >   Upstream-Status: Inappropriate[oe specific] [patch-status-core]
>> > >
>> > > * so the mystery is solved, but what should be do with this never-used
>> > >   patch, I think we should just delete it together with
>> > >   SRC_URI:append:ptest, but please Changqing Li confirm it's not needed
>> > >
>> > > * it was originally added by Changqing Li in meta-oe with:
>> > >   
>> > > https://git.openembedded.org/meta-openembedded/commit/?id=d7aa7173405c3b36235af736cd31dbe110708787
>> > >   then imported to oe-core by Randy MacLeod with:
>> > >   
>> > > https://git.openembedded.org/openembedded-core/commit/?id=57df134b1be56a688f41851e5ff014dd859c0bc3
>> > >
>> > > Signed-off-by: Martin Jansa 
>> > > ---
>> > >  ...nviroment-to-decide-if-a-test-is-bui.patch | 22 ++-
>> > >  1 file changed, 7 insertions(+), 15 deletions(-)
>> > >
>> > > diff --git 
>> > > a/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch
>> > >  
>> > > b/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch
>> > > index b1204e49eb..eb2658 100644
>> > > --- 
>> > > a/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch
>> > > +++ 
>> > > b/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch
>> > > @@ -1,24 +1,23 @@
>> > > -From f6abce5ba41a412a247250dcd80e387e53474466 Mon Sep 17 00:00:00 2001
>> > > -From: Your Name 
>> > > +From 7ffa1773be8d262bed0f5c8bdcb4dd8f906de095 Mon Sep 17 00:00:00 2001
>> > > +From: Changqing Li 
>> > >  Date: Mon, 28 Dec 2020 02:08:03 +
>> > >  Subject: [PATCH] Don't let host enviroment to decide if a test is build
>> > >
>> > >  test ssh2.sh need sshd, for cross compile, we need it on target, so
>> > >  don't use SSHD on host to decide weither to build a test
>> > >
>> > > -Upstream-Status: Inappropriate[oe specific]
>> > > +Upstream-Status: Inappropriate [oe specific]
>&

Re: [OE-core] [RFC][PATCH] libssh2: Update patch to apply and fix malformed Upstream-Status

2023-02-15 Thread Khem Raj
On Wed, Feb 15, 2023 at 11:26 AM Khem Raj  wrote:
>
> On Wed, Feb 15, 2023 at 9:18 AM Martin Jansa  wrote:
> >
> > * I've noticed this, because patchreview.py reports Malformed
> >   Upstream-Status in this one now, but the QA check in insane.bbclass
> >   wasn't reporting it before
> >
> > * the reason why insane.bbclass doesn't report it is because:
> >   SRC_URI:append:ptest = " 
> > file://0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch"
> >   doesn't work and probably never did as "ptest" is not an override
> >   and patch-status-core checks only the .patch files which are really
> >   in SRC_URI.
> >
> > * I've added it directly to SRC_URI and it also didn't apply:
> >   http://errors.yoctoproject.org/Errors/Details/689955/
> >   as the "endif" at the end was removed in 1.10.0 version:
> >   
> > https://github.com/libssh2/libssh2/commit/ecd6a74e44562797a1e92186ad4a402c5641720e#diff-32103f666ff2fb42b025a47ccf1b959bbcc6db89f217e5943b1de73c81a4f9db
> >
> >   after updating the patch to apply I got expected patch-status-core 
> > failure:
> >   http://errors.yoctoproject.org/Errors/Details/689956/
> >   ERROR: QA Issue: Malformed Upstream-Status in patch
> >   
> > TOPDIR/openembedded-core/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch
> >   Please correct according to 
> > https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#Patch_Header_Recommendations:_Upstream-Status
> >  :
> >   Upstream-Status: Inappropriate[oe specific] [patch-status-core]
> >
> > * so the mystery is solved, but what should be do with this never-used
> >   patch, I think we should just delete it together with
> >   SRC_URI:append:ptest, but please Changqing Li confirm it's not needed
> >
> > * it was originally added by Changqing Li in meta-oe with:
> >   
> > https://git.openembedded.org/meta-openembedded/commit/?id=d7aa7173405c3b36235af736cd31dbe110708787
> >   then imported to oe-core by Randy MacLeod with:
> >   
> > https://git.openembedded.org/openembedded-core/commit/?id=57df134b1be56a688f41851e5ff014dd859c0bc3
> >
> > Signed-off-by: Martin Jansa 
> > ---
> >  ...nviroment-to-decide-if-a-test-is-bui.patch | 22 ++-
> >  1 file changed, 7 insertions(+), 15 deletions(-)
> >
> > diff --git 
> > a/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch
> >  
> > b/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch
> > index b1204e49eb..eb2658 100644
> > --- 
> > a/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch
> > +++ 
> > b/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch
> > @@ -1,24 +1,23 @@
> > -From f6abce5ba41a412a247250dcd80e387e53474466 Mon Sep 17 00:00:00 2001
> > -From: Your Name 
> > +From 7ffa1773be8d262bed0f5c8bdcb4dd8f906de095 Mon Sep 17 00:00:00 2001
> > +From: Changqing Li 
> >  Date: Mon, 28 Dec 2020 02:08:03 +
> >  Subject: [PATCH] Don't let host enviroment to decide if a test is build
> >
> >  test ssh2.sh need sshd, for cross compile, we need it on target, so
> >  don't use SSHD on host to decide weither to build a test
> >
> > -Upstream-Status: Inappropriate[oe specific]
> > +Upstream-Status: Inappropriate [oe specific]
>
> Since we are already using a special token '[' to separate reason from
> status, I always wondered if having this space before '[' is something
> that could be ignored.
>

I see that scripts/contrib/patchreview.py does not care for space,
that answers my question. Maybe it would be
good to tabulate reason as well perhaps.

> >
> >  Signed-off-by: Changqing Li 
> > -
> >  ---
> > - tests/Makefile.am | 6 +-
> > - 1 file changed, 1 insertion(+), 5 deletions(-)
> > + tests/Makefile.am | 4 
> > + 1 file changed, 4 deletions(-)
> >
> >  diff --git a/tests/Makefile.am b/tests/Makefile.am
> > -index dc0922f..6cbc35d 100644
> > +index 27ddc2d..13de8ab 100644
> >  --- a/tests/Makefile.am
> >  +++ b/tests/Makefile.am
> > -@@ -1,16 +1,12 @@
> > +@@ -3,16 +3,12 @@ SUBDIRS = ossfuzz
> >   AM_CPPFLAGS = -I$(top_srcdir)/src -I$(top_srcdir)/include 
> > -I$(top_builddir)/src
> >   LDADD = ../src/libssh2.la
> >
> > @@ -35,10 +34,3 @@ index dc0922f..6cbc35d 100644
> >   check_PROGRAMS = $(ctests)
> >
> >   TESTS_ENVIRO

Re: [OE-core] [RFC][PATCH] libssh2: Update patch to apply and fix malformed Upstream-Status

2023-02-15 Thread Khem Raj
On Wed, Feb 15, 2023 at 9:18 AM Martin Jansa  wrote:
>
> * I've noticed this, because patchreview.py reports Malformed
>   Upstream-Status in this one now, but the QA check in insane.bbclass
>   wasn't reporting it before
>
> * the reason why insane.bbclass doesn't report it is because:
>   SRC_URI:append:ptest = " 
> file://0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch"
>   doesn't work and probably never did as "ptest" is not an override
>   and patch-status-core checks only the .patch files which are really
>   in SRC_URI.
>
> * I've added it directly to SRC_URI and it also didn't apply:
>   http://errors.yoctoproject.org/Errors/Details/689955/
>   as the "endif" at the end was removed in 1.10.0 version:
>   
> https://github.com/libssh2/libssh2/commit/ecd6a74e44562797a1e92186ad4a402c5641720e#diff-32103f666ff2fb42b025a47ccf1b959bbcc6db89f217e5943b1de73c81a4f9db
>
>   after updating the patch to apply I got expected patch-status-core failure:
>   http://errors.yoctoproject.org/Errors/Details/689956/
>   ERROR: QA Issue: Malformed Upstream-Status in patch
>   
> TOPDIR/openembedded-core/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch
>   Please correct according to 
> https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#Patch_Header_Recommendations:_Upstream-Status
>  :
>   Upstream-Status: Inappropriate[oe specific] [patch-status-core]
>
> * so the mystery is solved, but what should be do with this never-used
>   patch, I think we should just delete it together with
>   SRC_URI:append:ptest, but please Changqing Li confirm it's not needed
>
> * it was originally added by Changqing Li in meta-oe with:
>   
> https://git.openembedded.org/meta-openembedded/commit/?id=d7aa7173405c3b36235af736cd31dbe110708787
>   then imported to oe-core by Randy MacLeod with:
>   
> https://git.openembedded.org/openembedded-core/commit/?id=57df134b1be56a688f41851e5ff014dd859c0bc3
>
> Signed-off-by: Martin Jansa 
> ---
>  ...nviroment-to-decide-if-a-test-is-bui.patch | 22 ++-
>  1 file changed, 7 insertions(+), 15 deletions(-)
>
> diff --git 
> a/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch
>  
> b/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch
> index b1204e49eb..eb2658 100644
> --- 
> a/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch
> +++ 
> b/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch
> @@ -1,24 +1,23 @@
> -From f6abce5ba41a412a247250dcd80e387e53474466 Mon Sep 17 00:00:00 2001
> -From: Your Name 
> +From 7ffa1773be8d262bed0f5c8bdcb4dd8f906de095 Mon Sep 17 00:00:00 2001
> +From: Changqing Li 
>  Date: Mon, 28 Dec 2020 02:08:03 +
>  Subject: [PATCH] Don't let host enviroment to decide if a test is build
>
>  test ssh2.sh need sshd, for cross compile, we need it on target, so
>  don't use SSHD on host to decide weither to build a test
>
> -Upstream-Status: Inappropriate[oe specific]
> +Upstream-Status: Inappropriate [oe specific]

Since we are already using a special token '[' to separate reason from
status, I always wondered if having this space before '[' is something
that could be ignored.

>
>  Signed-off-by: Changqing Li 
> -
>  ---
> - tests/Makefile.am | 6 +-
> - 1 file changed, 1 insertion(+), 5 deletions(-)
> + tests/Makefile.am | 4 
> + 1 file changed, 4 deletions(-)
>
>  diff --git a/tests/Makefile.am b/tests/Makefile.am
> -index dc0922f..6cbc35d 100644
> +index 27ddc2d..13de8ab 100644
>  --- a/tests/Makefile.am
>  +++ b/tests/Makefile.am
> -@@ -1,16 +1,12 @@
> +@@ -3,16 +3,12 @@ SUBDIRS = ossfuzz
>   AM_CPPFLAGS = -I$(top_srcdir)/src -I$(top_srcdir)/include 
> -I$(top_builddir)/src
>   LDADD = ../src/libssh2.la
>
> @@ -35,10 +34,3 @@ index dc0922f..6cbc35d 100644
>   check_PROGRAMS = $(ctests)
>
>   TESTS_ENVIRONMENT = SSHD=$(SSHD) EXEEXT=$(EXEEXT)
> -@@ -38,4 +34,4 @@ if OPENSSL
> - # EXTRA_DIST += 
> test_public_key_auth_succeeds_with_correct_encrypted_ed25519_key.c
> - # EXTRA_DIST += 
> test_public_key_auth_succeeds_with_correct_ed25519_key_from_mem.c
> - EXTRA_DIST += test_public_key_auth_succeeds_with_correct_rsa_openssh_key.c
> --endif
> -\ No newline at end of file
> -+endif
> --
> 2.39.2
>
>
> 
>

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



Re: [OE-core] [PATCH 2/2] site: remove at-spi2-core values

2023-02-14 Thread Khem Raj
these would need some testing, I wonder if there are other autotooled
recipes which indirectly are using these cached values.

On Tue, Feb 14, 2023 at 7:56 AM Ross Burton  wrote:
>
> at-spi2-core is built with Meson now, so these values are not needed.
>
> Signed-off-by: Ross Burton 
> ---
>  meta/site/arm-32 | 10 --
>  meta/site/arm-64 |  9 -
>  meta/site/ix86-common| 10 --
>  meta/site/mips-common| 10 --
>  meta/site/powerpc-common |  9 -
>  meta/site/x86_64-linux   | 10 --
>  6 files changed, 58 deletions(-)
>  delete mode 100644 meta/site/powerpc-common
>
> diff --git a/meta/site/arm-32 b/meta/site/arm-32
> index c6af852354e..be741617b67 100644
> --- a/meta/site/arm-32
> +++ b/meta/site/arm-32
> @@ -6,13 +6,3 @@ ac_cv_sizeof_ssize_t=${ac_cv_sizeof_ssize_t=4}
>
>  # jikes
>  ac_cv_sizeof_wchar_t=4
> -
> -# at-spi2-core
> -ac_cv_alignof_char=1
> -ac_cv_alignof_dbind_pointer=4
> -ac_cv_alignof_dbind_struct=1
> -ac_cv_alignof_dbus_bool_t=4
> -ac_cv_alignof_dbus_int16_t=2
> -ac_cv_alignof_dbus_int32_t=4
> -ac_cv_alignof_dbus_int64_t=8
> -ac_cv_alignof_double=8
> diff --git a/meta/site/arm-64 b/meta/site/arm-64
> index 79c10dab0e8..f4eae88471e 100644
> --- a/meta/site/arm-64
> +++ b/meta/site/arm-64
> @@ -6,12 +6,3 @@ ac_cv_sizeof_size_t=8
>  ac_cv_sizeof_ssize_t=8
>  ac_cv_alignof_char=1
>  ac_cv_alignof_double=8
> -
> -# at-spi2-core
> -ac_cv_alignof_dbind_pointer=8
> -ac_cv_alignof_dbind_struct=1
> -ac_cv_alignof_dbus_bool_t=4
> -ac_cv_alignof_dbus_int16_t=2
> -ac_cv_alignof_dbus_int32_t=4
> -ac_cv_alignof_dbus_int64_t=8
> -
> diff --git a/meta/site/ix86-common b/meta/site/ix86-common
> index b97b2e3f60c..eae5670d937 100644
> --- a/meta/site/ix86-common
> +++ b/meta/site/ix86-common
> @@ -170,13 +170,3 @@ ac_cv_lib_c_signalfd=${ac_cv_lib_c_signalfd=yes}
>  nfsd_cv_broken_setfsuid=${nfsd_cv_broken_setfsuid=0}
>  nfsd_cv_func_statfs=${nfsd_cv_func_statfs=statfs2_bsize}
>  nfsd_cv_bsd_signals=${nfsd_cv_bsd_signals=yes}
> -
> -# at-spi2-core
> -ac_cv_alignof_char=1
> -ac_cv_alignof_dbind_pointer=4
> -ac_cv_alignof_dbind_struct=1
> -ac_cv_alignof_dbus_bool_t=4
> -ac_cv_alignof_dbus_int16_t=2
> -ac_cv_alignof_dbus_int32_t=4
> -ac_cv_alignof_dbus_int64_t=4
> -ac_cv_alignof_double=4
> diff --git a/meta/site/mips-common b/meta/site/mips-common
> index ff1b7f4e5e0..55dc50beb18 100644
> --- a/meta/site/mips-common
> +++ b/meta/site/mips-common
> @@ -20,13 +20,3 @@ ac_cv_sizeof_ssize_t=${ac_cv_sizeof_ssize_t=4}
>
>  # slrn
>  slrn_cv_va_val_copy=${slrn_cv_va_val_copy=yes}
> -
> -# at-spi2-core
> -ac_cv_alignof_char=1
> -ac_cv_alignof_dbind_pointer=4
> -ac_cv_alignof_dbind_struct=1
> -ac_cv_alignof_dbus_bool_t=4
> -ac_cv_alignof_dbus_int16_t=2
> -ac_cv_alignof_dbus_int32_t=4
> -ac_cv_alignof_dbus_int64_t=8
> -ac_cv_alignof_double=8
> diff --git a/meta/site/powerpc-common b/meta/site/powerpc-common
> deleted file mode 100644
> index 02217c70f94..000
> --- a/meta/site/powerpc-common
> +++ /dev/null
> @@ -1,9 +0,0 @@
> -# at-spi2-core
> -ac_cv_alignof_char=1
> -ac_cv_alignof_dbind_pointer=4
> -ac_cv_alignof_dbind_struct=1
> -ac_cv_alignof_dbus_bool_t=4
> -ac_cv_alignof_dbus_int16_t=2
> -ac_cv_alignof_dbus_int32_t=4
> -ac_cv_alignof_dbus_int64_t=8
> -ac_cv_alignof_double=8
> diff --git a/meta/site/x86_64-linux b/meta/site/x86_64-linux
> index d7b7a530ff5..b9ee141fd5c 100644
> --- a/meta/site/x86_64-linux
> +++ b/meta/site/x86_64-linux
> @@ -83,13 +83,3 @@ ac_cv_func__restgpr_14_x=no
>
>  # cvs
>  cvs_cv_func_printf_ptr=${cvs_cv_func_printf_ptr=yes}
> -
> -# at-spi2-core
> -ac_cv_alignof_char=1
> -ac_cv_alignof_dbind_pointer=8
> -ac_cv_alignof_dbind_struct=1
> -ac_cv_alignof_dbus_bool_t=4
> -ac_cv_alignof_dbus_int16_t=2
> -ac_cv_alignof_dbus_int32_t=4
> -ac_cv_alignof_dbus_int64_t=8
> -ac_cv_alignof_double=8
> --
> 2.34.1
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177175): 
https://lists.openembedded.org/g/openembedded-core/message/177175
Mute This Topic: https://lists.openembedded.org/mt/96962710/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] libcgroup: clean up musl DEPENDS

2023-02-14 Thread Khem Raj
On Tue, Feb 14, 2023 at 8:42 AM Ross Burton  wrote:
>
> libcgroup uses fts_* functions, but these are not implemented in musl so
> we depend on the fts recipe and force a link to libfts.
>
> However since 3.0.0 libcgroup will automatically look for fts_open in
> both libc and libfts[1], so this can be simplified to just a conditional
> DEPENDS.
>
> [1] 
> https://github.com/libcgroup/libcgroup/commit/27ba904355575153308bdc0fa48344ef1be55ca1
>

cool. LGTM

> Signed-off-by: Ross Burton 
> ---
>  meta/recipes-core/libcgroup/libcgroup_3.0.0.bb | 4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/meta/recipes-core/libcgroup/libcgroup_3.0.0.bb 
> b/meta/recipes-core/libcgroup/libcgroup_3.0.0.bb
> index 9937a17fb51..457b965481d 100644
> --- a/meta/recipes-core/libcgroup/libcgroup_3.0.0.bb
> +++ b/meta/recipes-core/libcgroup/libcgroup_3.0.0.bb
> @@ -10,6 +10,7 @@ LIC_FILES_CHKSUM = 
> "file://COPYING;md5=4d794c5d710e5b3547a6cc6a6609a641"
>  inherit autotools pkgconfig github-releases
>
>  DEPENDS = "bison-native flex-native"
> +DEPENDS:append:libc-musl = " fts"
>
>  SRC_URI = "${GITHUB_BASE_URI}/download/v3.0/${BP}.tar.gz \
> file://0001-api-Use-GNU-strerror_r-when-available.patch \
> @@ -18,9 +19,6 @@ UPSTREAM_CHECK_URI = 
> "https://github.com/libcgroup/libcgroup/tags;
>
>  SRC_URI[sha256sum] = 
> "8d284d896fca1c981b55850e92acd3ad9648a69227c028dda7ae3402af878edd"
>
> -DEPENDS:append:libc-musl = " fts "
> -EXTRA_OEMAKE:append:libc-musl = " LIBS=-lfts"
> -
>  PACKAGECONFIG = "${@bb.utils.filter('DISTRO_FEATURES', 'pam', d)}"
>  PACKAGECONFIG[pam] = "--enable-pam-module-dir=${base_libdir}/security 
> --enable-pam=yes,--enable-pam=no,libpam"
>
> --
> 2.34.1
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177169): 
https://lists.openembedded.org/g/openembedded-core/message/177169
Mute This Topic: https://lists.openembedded.org/mt/96963828/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] elfutils: Backport fix for DW_TAG_unspecified_type handling

2023-02-14 Thread Khem Raj
Re-enable funcretval tests

Signed-off-by: Khem Raj 
---
 .../elfutils/elfutils_0.188.bb|  3 +-
 .../handle_DW_TAG_unspecified_type.patch  | 88 +++
 2 files changed, 89 insertions(+), 2 deletions(-)
 create mode 100644 
meta/recipes-devtools/elfutils/files/handle_DW_TAG_unspecified_type.patch

diff --git a/meta/recipes-devtools/elfutils/elfutils_0.188.bb 
b/meta/recipes-devtools/elfutils/elfutils_0.188.bb
index 182229becf..74271b2411 100644
--- a/meta/recipes-devtools/elfutils/elfutils_0.188.bb
+++ b/meta/recipes-devtools/elfutils/elfutils_0.188.bb
@@ -23,6 +23,7 @@ SRC_URI = 
"https://sourceware.org/elfutils/ftp/${PV}/${BP}.tar.bz2 \

file://0001-tests-Makefile.am-compile-test_nlist-with-standard-C.patch \

file://0001-PR29926-debuginfod-Fix-usage-of-deprecated-CURLINFO_.patch \

file://0002-debuginfod-client-Use-CURLOPT_PROTOCOLS_STR-for-libc.patch \
+   file://handle_DW_TAG_unspecified_type.patch \
"
 SRC_URI:append:libc-musl = " \
file://0003-musl-utils.patch \
@@ -98,8 +99,6 @@ do_install_ptest() {
cp -r ${B}/debuginfod   ${D}${PTEST_PATH}
sed -i '/^Makefile:/c Makefile:'
${D}${PTEST_PATH}/tests/Makefile
find ${D}${PTEST_PATH} -type f -name *.[hoc] | xargs -i rm {}
-   # TODO: remove below filter after 
https://sourceware.org/bugzilla/show_bug.cgi?id=30047 is fixed
-   sed -i -e '/funcretval/d' 
${D}${PTEST_PATH}/tests/run-native-test.sh
fi
 }
 
diff --git 
a/meta/recipes-devtools/elfutils/files/handle_DW_TAG_unspecified_type.patch 
b/meta/recipes-devtools/elfutils/files/handle_DW_TAG_unspecified_type.patch
new file mode 100644
index 00..8cab01c29a
--- /dev/null
+++ b/meta/recipes-devtools/elfutils/files/handle_DW_TAG_unspecified_type.patch
@@ -0,0 +1,88 @@
+From: Mark Wielaard 
+Date: Thu, 26 Jan 2023 17:19:15 + (+0100)
+Subject: backends: Handle DW_TAG_unspecified_type in dwarf_peeled_die_type
+X-Git-Url: 
https://sourceware.org/git/?p=elfutils.git;a=commitdiff_plain;h=f2c522567ad63ac293535fba9704895e685ab5bc;hp=3fa98a6f29b0f370e32549ead7eb897c839af980
+
+backends: Handle DW_TAG_unspecified_type in dwarf_peeled_die_type
+
+binutils 2.40 introduces DW_TAG_unspecified_type for assembly
+functions with an unknown return type. This breaks the
+run-funcretval.sh testcase because dwfl_module_return_value_location
+returns an error for such functions because it cannot determine the
+return value location. Fix that by treating DW_TAG_unspecified_type
+as if the DIE doesn't have a DW_AT_type.
+
+Also update the testcase to explicitly checking for
+DW_TAG_unspecified_type and printing "returns unspecified type".
+
+https://sourceware.org/bugzilla/show_bug.cgi?id=30047
+
+Upstream-Status: Backport 
[https://sourceware.org/git/?p=elfutils.git;a=commitdiff;h=f2c522567ad63ac293535fba9704895e685ab5bc;hp=3fa98a6f29b0f370e32549ead7eb897c839af980]
+Signed-off-by: Mark Wielaard 
+---
+
+--- a/backends/libebl_CPU.h
 b/backends/libebl_CPU.h
+@@ -1,5 +1,6 @@
+ /* Common interface for libebl modules.
+Copyright (C) 2000, 2001, 2002, 2003, 2005, 2013, 2014 Red Hat, Inc.
++   Copyright (C) 2023 Mark J. Wielaard 
+This file is part of elfutils.
+ 
+This file is free software; you can redistribute it and/or modify
+@@ -53,7 +54,9 @@ extern bool (*generic_debugscn_p) (const
+  dwarf_tag (_die); })
+ 
+ /* Get a type die corresponding to DIE.  Peel CV qualifiers off
+-   it.  */
++   it.  Returns zero if the DIE doesn't have a type, or the type
++   is DW_TAG_unspecified_type.  Returns -1 on error.  Otherwise
++   returns the result tag DW_AT value.  */
+ static inline int
+ dwarf_peeled_die_type (Dwarf_Die *die, Dwarf_Die *result)
+ {
+@@ -69,7 +72,14 @@ dwarf_peeled_die_type (Dwarf_Die *die, D
+   if (dwarf_peel_type (result, result) != 0)
+ return -1;
+ 
+-  return DWARF_TAG_OR_RETURN (result);
++  if (result == NULL)
++return -1;
++
++  int tag = dwarf_tag (result);
++  if (tag == DW_TAG_unspecified_type)
++return 0; /* Treat an unspecified type as if there was no type.  */
++
++  return tag;
+ }
+ 
+ #endif/* libebl_CPU.h */
+--- a/tests/funcretval.c
 b/tests/funcretval.c
+@@ -1,5 +1,6 @@
+ /* Test program for dwfl_module_return_value_location.
+Copyright (C) 2005 Red Hat, Inc.
++   Copyright (C) 2023 Mark J. Wielaard 
+This file is part of elfutils.
+ 
+This file is free software; you can redistribute it and/or modify
+@@ -67,7 +68,18 @@ handle_function (Dwarf_Die *funcdie, voi
+ error (EXIT_FAILURE, 0, "dwfl_module_return_value_location: %s",
+  dwfl_errmsg (-1));
+   else if (nlocops == 0)
+-puts ("returns no value");
++{
++  // Check if this is the special unspecified type
++  // https://sourceware.org/bugzilla/show_bug.cgi?id=30047
++  Dwarf_Die die_mem, *typedie = 

[OE-core] [PATCH 2/3] stress-ng: Add missing header files for clock_adjtime

2023-02-13 Thread Khem Raj
Signed-off-by: Khem Raj 
---
 ...nclude-sys-futex.h-for-clock_adjtime.patch | 32 +++
 .../stress-ng/stress-ng_0.15.03.bb|  1 +
 2 files changed, 33 insertions(+)
 create mode 100644 
meta/recipes-extended/stress-ng/stress-ng/0001-Include-sys-futex.h-for-clock_adjtime.patch

diff --git 
a/meta/recipes-extended/stress-ng/stress-ng/0001-Include-sys-futex.h-for-clock_adjtime.patch
 
b/meta/recipes-extended/stress-ng/stress-ng/0001-Include-sys-futex.h-for-clock_adjtime.patch
new file mode 100644
index 00..87d2ead46a
--- /dev/null
+++ 
b/meta/recipes-extended/stress-ng/stress-ng/0001-Include-sys-futex.h-for-clock_adjtime.patch
@@ -0,0 +1,32 @@
+From 57f207ec7fb39c8b502f40dbdabd568f6b866a82 Mon Sep 17 00:00:00 2001
+From: Khem Raj 
+Date: Mon, 13 Feb 2023 12:18:08 -0800
+Subject: [PATCH] Include sys/futex.h for clock_adjtime
+
+Fixes
+core-shim.c:1942:9: error: call to undeclared function 'clock_adjtime'; ISO 
C99 and later do not support implicit function declarations 
[-Wimplicit-function-declaration]
+
+Upstream-Status: Submitted [https://github.com/ColinIanKing/stress-ng/pull/261]
+Signed-off-by: Khem Raj 
+---
+ core-shim.c | 4 
+ 1 file changed, 4 insertions(+)
+
+diff --git a/core-shim.c b/core-shim.c
+index dc539c64..de38e908 100644
+--- a/core-shim.c
 b/core-shim.c
+@@ -66,6 +66,10 @@ UNEXPECTED
+ #include 
+ #endif
+ 
++#if defined(HAVE_SYS_TIMEX_H)
++#include 
++#endif
++
+ #if defined(HAVE_SYS_RANDOM_H)
+ #include 
+ #endif
+-- 
+2.39.1
+
diff --git a/meta/recipes-extended/stress-ng/stress-ng_0.15.03.bb 
b/meta/recipes-extended/stress-ng/stress-ng_0.15.03.bb
index 13a8b49f70..cd7f41a016 100644
--- a/meta/recipes-extended/stress-ng/stress-ng_0.15.03.bb
+++ b/meta/recipes-extended/stress-ng/stress-ng_0.15.03.bb
@@ -7,6 +7,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
 
 SRC_URI = 
"git://github.com/ColinIanKing/stress-ng.git;protocol=https;branch=master \
file://0001-test-float-Make-variables-global.patch \
+   file://0001-Include-sys-futex.h-for-clock_adjtime.patch \
file://0001-Pass-LD_GOLD-1-via-makefile-to-enable-gold-linker.patch"
 SRCREV = "f3be0447c10fd5652b4c3753d56bcaac13fd8917"
 S = "${WORKDIR}/git"
-- 
2.39.1


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



[OE-core] [PATCH 3/3] gstreamer1.0-plugins-good: Fix build with musl

2023-02-13 Thread Khem Raj
musl's definition of ioctl() API is different from glibc's and gst has
built upon definition from glibc which was being warned about but now
compilers can check signatures of funciton pointers, means it becomes an
error with clang16+

Signed-off-by: Khem Raj 
---
 ...ine-ioctl_req_t-for-posix-linux-case.patch | 40 +++
 .../gstreamer1.0-plugins-good_1.22.0.bb   |  2 +-
 2 files changed, 41 insertions(+), 1 deletion(-)
 create mode 100644 
meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good/0001-v4l2-Define-ioctl_req_t-for-posix-linux-case.patch

diff --git 
a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good/0001-v4l2-Define-ioctl_req_t-for-posix-linux-case.patch
 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good/0001-v4l2-Define-ioctl_req_t-for-posix-linux-case.patch
new file mode 100644
index 00..fbbf029a2c
--- /dev/null
+++ 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good/0001-v4l2-Define-ioctl_req_t-for-posix-linux-case.patch
@@ -0,0 +1,40 @@
+From 5ce1e410965ed047a03c09b17796162f0363e396 Mon Sep 17 00:00:00 2001
+From: Khem Raj 
+Date: Mon, 13 Feb 2023 12:47:31 -0800
+Subject: [PATCH] v4l2: Define ioctl_req_t for posix/linux case
+
+this is an issue seen with musl based linux distros e.g. alpine [1]
+musl is not going to change this since it breaks ABI/API interfaces
+Newer compilers are stringent ( e.g. clang16 ) which can now detect
+signature mismatches in function pointers too, existing code warned but
+did not error with older clang
+
+Fixes
+gstv4l2object.c:544:23: error: incompatible function pointer types assigning 
to 'gint (*)(gint, ioctl_req_t, ...)' (aka 'int (*)(int, unsigned long, ...)') 
from 'int (int, int, ...)' [-Wincompatible-function-pointer-types]
+v4l2object->ioctl = ioctl;
+  ^ ~
+
+[1] https://gitlab.alpinelinux.org/alpine/aports/-/issues/7580
+
+Upstream-Status: Submitted 
[https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/3950]
+Signed-off-by: Khem Raj 
+---
+ sys/v4l2/gstv4l2object.h | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/sys/v4l2/gstv4l2object.h b/sys/v4l2/gstv4l2object.h
+index 3a5c961..4f43008 100644
+--- a/sys/v4l2/gstv4l2object.h
 b/sys/v4l2/gstv4l2object.h
+@@ -76,6 +76,8 @@ typedef gboolean  (*GstV4l2UpdateFpsFunction) (GstV4l2Object 
* v4l2object);
+  * 'unsigned long' for the 2nd parameter */
+ #ifdef __ANDROID__
+ typedef unsigned ioctl_req_t;
++#elif defined(__linux__) && !defined(__GLIBC__) /* musl/linux */
++typedef int ioctl_req_t;
+ #else
+ typedef gulong ioctl_req_t;
+ #endif
+-- 
+2.39.1
+
diff --git 
a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good_1.22.0.bb 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good_1.22.0.bb
index 85f8a247b1..ef4d82c598 100644
--- a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good_1.22.0.bb
+++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good_1.22.0.bb
@@ -6,7 +6,7 @@ BUGTRACKER = 
"https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/-/issues
 
 SRC_URI = 
"https://gstreamer.freedesktop.org/src/gst-plugins-good/gst-plugins-good-${PV}.tar.xz
 \

file://0001-qt-include-ext-qt-gstqtgl.h-instead-of-gst-gl-gstglf.patch \
-   "
+   file://0001-v4l2-Define-ioctl_req_t-for-posix-linux-case.patch"
 
 SRC_URI[sha256sum] = 
"582e617271e7f314d1a2211e3e3856ae2e4303c8c0d6114e9c4a5ea5719294b0"
 
-- 
2.39.1


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



[OE-core] [PATCH 1/3] unfs3: Add missing header files

2023-02-13 Thread Khem Raj
These enable builds with additional warnings as errors

Signed-off-by: Khem Raj 
---
 .../unfs3/0001-fix-building-on-macOS.patch| 27 +++
 meta/recipes-devtools/unfs3/unfs3_git.bb  |  1 +
 2 files changed, 28 insertions(+)
 create mode 100644 
meta/recipes-devtools/unfs3/unfs3/0001-fix-building-on-macOS.patch

diff --git a/meta/recipes-devtools/unfs3/unfs3/0001-fix-building-on-macOS.patch 
b/meta/recipes-devtools/unfs3/unfs3/0001-fix-building-on-macOS.patch
new file mode 100644
index 00..f18ffd3711
--- /dev/null
+++ b/meta/recipes-devtools/unfs3/unfs3/0001-fix-building-on-macOS.patch
@@ -0,0 +1,27 @@
+From 989b87ae46b3183a742031373fbb3e912ab9b666 Mon Sep 17 00:00:00 2001
+From: Andrey Filipenkov 
+Date: Wed, 2 Nov 2022 13:38:40 +0300
+Subject: [PATCH] fix building on macOS
+
+Signed-off-by: Khem Raj 
+Upstream-Status: Backport 
[https://github.com/unfs3/unfs3/commit/989b87ae46b3183a742031373fbb3e912ab9b666]
+---
+ attr.c | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/attr.c b/attr.c
+index 6253e84..0ce9375 100644
+--- a/attr.c
 b/attr.c
+@@ -18,6 +18,8 @@
+ #include 
+ #include 
+ #include 
++#include 
++#include 
+ 
+ #include "backend.h"
+ #include "nfs.h"
+-- 
+2.39.1
+
diff --git a/meta/recipes-devtools/unfs3/unfs3_git.bb 
b/meta/recipes-devtools/unfs3/unfs3_git.bb
index be3870b8a4..9913a503e8 100644
--- a/meta/recipes-devtools/unfs3/unfs3_git.bb
+++ b/meta/recipes-devtools/unfs3/unfs3_git.bb
@@ -16,6 +16,7 @@ SRC_URI = 
"git://github.com/unfs3/unfs3.git;protocol=https;branch=master \

file://0001-daemon.c-Fix-race-window-for-writing-of-the-pid-file.patch \
file://0001-Alias-off64_t-to-off_t-on-linux-if-not-defined.patch \
file://0001-locate.c-Include-attr.h.patch \
+   file://0001-fix-building-on-macOS.patch \
"
 SRCREV = "c8f2d2cd4529955419bad0e163f88d47ff176b8d"
 UPSTREAM_CHECK_GITTAGREGEX = "unfs3\-(?P\d+(\.\d+)+)"
-- 
2.39.1


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

2023-02-09 Thread Khem Raj
Is there some reading material for quick highlights of dnf5 and its future ?

On Thu, Feb 9, 2023 at 4:05 AM Ross Burton  wrote:
>
> Hi,
>
> At FOSDEM there were was a session about DNF 5 and someone (sorry if you’re 
> reading this, I can’t remember your name) came to the stand to ask if we’ve 
> looked at it.  I was aware of a DNF replacement but wasn’t aware that it had 
> actually started making releases.
>
> I’ve just pushed a branch to poky-contrib:ross/dnf5 which adds recipes for 
> DNF5 and any new dependencies (it also needs meta-oe right now, as some 
> dependencies are there).  It builds a dnf-native, but the blocker is that it 
> doesn’t yet implement —repofrompath to add a repository without a 
> corresponding configuration file, which is what we use at rootfs time.  We 
> can probably work around that by writing a temporary repo file, or just 
> implement the feature upstream.
>
> If anyone is interested in helping the port to DNF5 then your help would be 
> appreciated!
>
> Ross
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#176965): 
https://lists.openembedded.org/g/openembedded-core/message/176965
Mute This Topic: https://lists.openembedded.org/mt/96851390/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] glibc: unify wordsize.h between arm and aarch64

2023-02-09 Thread Khem Raj
thanks for finding and fixing it. It has  happened with every upgrade
that this file goes out of sync due to copyright headers change.
its perhaps worth trying to use a symlink instead try this patch and
see if it works in your settings

https://uclibc.org/~kraj/0001-wordsize.h-Unify-the-header-between-arm-and-aarch64.patch

if it does then we should use this instead of the original patch

On Thu, Feb 9, 2023 at 2:00 AM Yi Zhao  wrote:
>
> There is a redundant change in
> 0016-wordsize.h-Unify-the-header-between-arm-and-aarch64.patch that
> causes wordsize.h to be different in arm and aarch64. This causes the
> build error when enable multilib:
>
> Error: Transaction test error:
>   file /usr/include/bits/wordsize.h conflicts between attempted installs of 
> lib32-libc6-dev-2.37-r0.armv7vet2hf_vfp and libc6-dev-2.37-r0.cortexa57
>
> Signed-off-by: Yi Zhao 
> ---
>  ...y-the-header-between-arm-and-aarch64.patch | 20 ++-
>  1 file changed, 6 insertions(+), 14 deletions(-)
>
> diff --git 
> a/meta/recipes-core/glibc/glibc/0016-wordsize.h-Unify-the-header-between-arm-and-aarch64.patch
>  
> b/meta/recipes-core/glibc/glibc/0016-wordsize.h-Unify-the-header-between-arm-and-aarch64.patch
> index 9ed89c93da..90a6cc2363 100644
> --- 
> a/meta/recipes-core/glibc/glibc/0016-wordsize.h-Unify-the-header-between-arm-and-aarch64.patch
> +++ 
> b/meta/recipes-core/glibc/glibc/0016-wordsize.h-Unify-the-header-between-arm-and-aarch64.patch
> @@ -11,10 +11,10 @@ Upstream-Status: Inappropriate [ OE-Specific ]
>
>  Signed-off-by: Khem Raj 
>  ---
> - sysdeps/aarch64/bits/wordsize.h  |  8 ++--
> - sysdeps/{aarch64 => arm}/bits/wordsize.h | 10 +++---
> - 2 files changed, 13 insertions(+), 5 deletions(-)
> - copy sysdeps/{aarch64 => arm}/bits/wordsize.h (80%)
> + sysdeps/aarch64/bits/wordsize.h  | 8 ++--
> + sysdeps/{aarch64 => arm}/bits/wordsize.h | 8 ++--
> + 2 files changed, 12 insertions(+), 4 deletions(-)
> + copy sysdeps/{aarch64 => arm}/bits/wordsize.h (85%)
>
>  diff --git a/sysdeps/aarch64/bits/wordsize.h 
> b/sysdeps/aarch64/bits/wordsize.h
>  index 04d4be9519..63876a7830 100644
> @@ -40,20 +40,12 @@ index 04d4be9519..63876a7830 100644
>
>   #define __WORDSIZE_TIME64_COMPAT320
>  diff --git a/sysdeps/aarch64/bits/wordsize.h b/sysdeps/arm/bits/wordsize.h
> -similarity index 80%
> +similarity index 85%
>  copy from sysdeps/aarch64/bits/wordsize.h
>  copy to sysdeps/arm/bits/wordsize.h
> -index 04d4be9519..5ef0ed21f3 100644
> +index 04d4be9519..63876a7830 100644
>  --- a/sysdeps/aarch64/bits/wordsize.h
>  +++ b/sysdeps/arm/bits/wordsize.h
> -@@ -1,6 +1,6 @@
> - /* Determine the wordsize from the preprocessor defines.
> -
> --   Copyright (C) 2016-2023 Free Software Foundation, Inc.
> -+   Copyright (C) 2016-2022 Free Software Foundation, Inc.
> -This file is part of the GNU C Library.
> -
> -The GNU C Library is free software; you can redistribute it and/or
>  @@ -17,12 +17,16 @@
>  License along with the GNU C Library; if not, see
>  <https://www.gnu.org/licenses/>.  */
> --
> 2.25.1
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#176963): 
https://lists.openembedded.org/g/openembedded-core/message/176963
Mute This Topic: https://lists.openembedded.org/mt/96850115/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] lttng-tools: Update LFS64 patch with upstream feedback

2023-02-08 Thread Khem Raj
See https://review.lttng.org/c/lttng-tools/+/9268

Signed-off-by: Khem Raj 
---
 ...pat-Define-off64_t-as-off_t-on-linux.patch | 26 ++-
 1 file changed, 14 insertions(+), 12 deletions(-)

diff --git 
a/meta/recipes-kernel/lttng/lttng-tools/0001-compat-Define-off64_t-as-off_t-on-linux.patch
 
b/meta/recipes-kernel/lttng/lttng-tools/0001-compat-Define-off64_t-as-off_t-on-linux.patch
index ef81703bc3..4e21d1e9f1 100644
--- 
a/meta/recipes-kernel/lttng/lttng-tools/0001-compat-Define-off64_t-as-off_t-on-linux.patch
+++ 
b/meta/recipes-kernel/lttng/lttng-tools/0001-compat-Define-off64_t-as-off_t-on-linux.patch
@@ -22,7 +22,14 @@ Change-Id: If2c6007a8c85bc3f3065002af8a7538b882fb4a8
 
 --- a/src/common/compat/compat-fcntl.c
 +++ b/src/common/compat/compat-fcntl.c
-@@ -13,7 +13,7 @@
+@@ -8,14 +8,17 @@
+ #define _LGPL_SOURCE
+ #include 
+ #include 
++#include 
++#include 
+ #include 
+ 
  #ifdef __linux__
  
  LTTNG_HIDDEN
@@ -30,25 +37,20 @@ Change-Id: If2c6007a8c85bc3f3065002af8a7538b882fb4a8
 +int compat_sync_file_range(int fd, off_t offset, off_t nbytes,
unsigned int flags)
  {
++  LTTNG_BUILD_BUG_ON(sizeof(off_t) != sizeof(int64_t));
  #ifdef HAVE_SYNC_FILE_RANGE
+   return sync_file_range(fd, offset, nbytes, flags);
+ #else
 --- a/src/common/compat/fcntl.h
 +++ b/src/common/compat/fcntl.h
-@@ -8,21 +8,21 @@
- #ifndef _COMPAT_FCNTL_H
- #define _COMPAT_FCNTL_H
- 
-+#include 
- #include 
- #include 
+@@ -13,16 +13,12 @@
  
  #include 
  
 -#if (defined(__CYGWIN__))
 -typedef long long off64_t;
 -#endif
-+static_assert(sizeof(off_t) == sizeof(int64_t),
-+"Build system is misconfigured, off_t must be 64-bit wide");
- 
+-
  #if (defined(__FreeBSD__) || defined(__sun__))
  typedef off64_t loff_t;
  #endif
@@ -59,7 +61,7 @@ Change-Id: If2c6007a8c85bc3f3065002af8a7538b882fb4a8
unsigned int flags);
  #define lttng_sync_file_range(fd, offset, nbytes, flags) \
compat_sync_file_range(fd, offset, nbytes, flags)
-@@ -37,8 +37,8 @@ extern int compat_sync_file_range(int fd
+@@ -37,8 +33,8 @@ extern int compat_sync_file_range(int fd
  #define SYNC_FILE_RANGE_WAIT_BEFORE   0
  #define SYNC_FILE_RANGE_WRITE 0
  
-- 
2.39.1


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



Re: [OE-core] [meta-oe][PATCH] nlohmann-json: Allow empty main package for SDK

2023-02-06 Thread Khem Raj
On Mon, Feb 6, 2023 at 1:36 PM Tom Hochstein  wrote:
>
> Oops, I don’t often send for non OE-Core and I forgot there was a separate 
> mailing list for that. I usually just cut and paste from here:
>
>
>
> http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded#Sending_patches
>
>
>
> Which makes it easy to overlook the mailing list requirement.
>
>
>
> There are several examples in the repo that use this same pattern. Here’s one:
>
>
>
> https://github.com/openembedded/meta-openembedded/commit/7163946b56539725d5a5868a9318e56e713a4a95
>
>
>
> It has the advantage of not installing the header in the image. Should the 
> -dev solution be preferred?

if these are development headers and libs then yes its better since it
goes with the general philosophy of putting these files in -dev pkgs.

>
>
>
> Tom
>
>
>
> From: Martin Jansa 
> Sent: Monday, February 6, 2023 3:13 PM
> To: Tom Hochstein 
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [meta-oe][PATCH] nlohmann-json: Allow empty main 
> package for SDK
>
>
>
> Wrong ML and why do you want to install empty package? Add nlohmann-json-dev 
> to imx-gpu-sdk recipe instead.
>
>
>
> On Mon, Feb 6, 2023 at 10:09 PM Tom Hochstein  wrote:
>
> The header-only package cannot be included in the SDK without marking
> the main package with ALLOW_EMPTY.
>
> Fixes rootfs problem:
> ```
> The following packages have unmet dependencies:
>  imx-gpu-sdk : Depends: nlohmann-json but it is not installable
> E: Unable to correct problems, you have held broken packages.
> ```
>
> Signed-off-by: Tom Hochstein 
> ---
>  meta-oe/recipes-devtools/nlohmann-json/nlohmann-json_3.11.2.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta-oe/recipes-devtools/nlohmann-json/nlohmann-json_3.11.2.bb 
> b/meta-oe/recipes-devtools/nlohmann-json/nlohmann-json_3.11.2.bb
> index 502262820..6cf27755e 100644
> --- a/meta-oe/recipes-devtools/nlohmann-json/nlohmann-json_3.11.2.bb
> +++ b/meta-oe/recipes-devtools/nlohmann-json/nlohmann-json_3.11.2.bb
> @@ -18,7 +18,7 @@ inherit cmake
>  EXTRA_OECMAKE += "-DJSON_BuildTests=OFF"
>
>  # nlohmann-json is a header only C++ library, so the main package will be 
> empty.
> -
> +ALLOW_EMPTY:${PN} = "1"
>  RDEPENDS:${PN}-dev = ""
>
>  BBCLASSEXTEND = "native nativesdk"
> --
> 2.25.1
>
>
>
> 
>

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



Re: [OE-core] [PATCH 2/3] libc-locale: Fix on target locale generation

2023-02-04 Thread Khem Raj
On Sat, Feb 4, 2023 at 3:41 AM Richard Purdie
 wrote:
>
> If on target locale generation is used, it fails at first boot showing
> errors about a missing directory. Ensure the directory exists.
>
> Signed-off-by: Richard Purdie 
> ---
>  meta/classes-recipe/libc-package.bbclass | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/meta/classes-recipe/libc-package.bbclass 
> b/meta/classes-recipe/libc-package.bbclass
> index de3d4223a8c..8a99f73ae72 100644
> --- a/meta/classes-recipe/libc-package.bbclass
> +++ b/meta/classes-recipe/libc-package.bbclass
> @@ -51,6 +51,7 @@ PACKAGE_NO_GCONV ?= "0"
>  OVERRIDES:append = ":${TARGET_ARCH}-${TARGET_OS}"
>
>  locale_base_postinst_ontarget() {
> +mkdir ${libdir}/locale

should it be mkdir -p for when it does exist beforehand ?

>  localedef --inputfile=${datadir}/i18n/locales/%s --charmap=%s %s
>  }
>
> --
> 2.37.2
>
>
> 
>

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

2023-02-03 Thread Khem Raj
Details are here [1] and summary of changes is here [2]

[1] https://sourceware.org/glibc/wiki/Release/2.37
[2] https://sourceware.org/pipermail/libc-announce/2023/35.html

Signed-off-by: Khem Raj 
---
 meta/conf/distro/include/tcmode-default.inc   |   2 +-
 ...2.36.bb => cross-localedef-native_2.37.bb} |   4 +-
 meta/recipes-core/glibc/glibc-common.inc  |   2 +-
 ...bc-locale_2.36.bb => glibc-locale_2.37.bb} |   0
 ...bc-mtrace_2.36.bb => glibc-mtrace_2.37.bb} |   0
 ...-scripts_2.36.bb => glibc-scripts_2.37.bb} |   0
 ...libc-tests_2.36.bb => glibc-tests_2.37.bb} |   0
 ...tsuite_2.36.bb => glibc-testsuite_2.37.bb} |   0
 meta/recipes-core/glibc/glibc-version.inc |   6 +-
 ...fortify-symbol-for-64-bit-time_t-BZ-.patch | 528 --
 ...dd-hardlink-resolver-from-util-linux.patch |   2 +-
 ...-fix-ups-hardlink-to-make-it-compile.patch |   2 +-
 ...Look-for-host-system-ld.so.cache-as-.patch |   4 +-
 ...Fix-buffer-overrun-with-a-relocated-.patch |   4 +-
 ...Raise-the-size-of-arrays-containing-.patch |  39 +-
 ...k-glibc-Allow-64-bit-atomics-for-x86.patch |   4 +-
 ...Make-relocatable-install-for-locales.patch |  10 +-
 ...Fall-back-to-faccessat-on-faccess2-r.patch |   4 +-
 ...the-path-sets-wrong-config-variables.patch |   6 +-
 ...ss-building-and-testing-instructions.patch |   2 +-
 ...glibc-Help-bootstrap-cross-toolchain.patch |   4 +-
 ...eglibc-Resolve-__fpscr_values-on-SH4.patch |   4 +-
 ...port-cross-locale-generation-support.patch |  24 +-
 ...-archive-uses-a-hard-coded-locale-pa.patch |   4 +-
 ...aybe-uninitialized-errors-with-Os-BZ.patch |  53 --
 ...o-not-ask-compiler-for-finding-arch.patch} |   2 +-
 ...RE_KNOWN_INTERPRETER_NAMES-to-known-.patch |  29 -
 ...-the-header-between-arm-and-aarch64.patch} |  24 +-
 ...-printf-builtin-in-nscd-init-script.patch} |   2 +-
 ...gure.ac-Set-libc_cv_rootsbindir-onl.patch} |   2 +-
 ...ll-interpreter-overridable-in-tzsel.patch} |  10 +-
 ...se-bin-sh-default-shell-interpreter.patch} |   2 +-
 ...-failed-in-unprivileged-process-BZ-.patch} |   4 +-
 ...uild-time-paths-in-the-output-binar.patch} |   6 +-
 .../glibc/glibc/0025-startup-Force-O2.patch   |  28 -
 .../glibc/{glibc_2.36.bb => glibc_2.37.bb}|  20 +-
 36 files changed, 101 insertions(+), 736 deletions(-)
 rename meta/recipes-core/glibc/{cross-localedef-native_2.36.bb => 
cross-localedef-native_2.37.bb} (94%)
 rename meta/recipes-core/glibc/{glibc-locale_2.36.bb => glibc-locale_2.37.bb} 
(100%)
 rename meta/recipes-core/glibc/{glibc-mtrace_2.36.bb => glibc-mtrace_2.37.bb} 
(100%)
 rename meta/recipes-core/glibc/{glibc-scripts_2.36.bb => 
glibc-scripts_2.37.bb} (100%)
 rename meta/recipes-core/glibc/{glibc-tests_2.36.bb => glibc-tests_2.37.bb} 
(100%)
 rename meta/recipes-core/glibc/{glibc-testsuite_2.36.bb => 
glibc-testsuite_2.37.bb} (100%)
 delete mode 100644 
meta/recipes-core/glibc/glibc/0001-Linux-Add-ppoll-fortify-symbol-for-64-bit-time_t-BZ-.patch
 delete mode 100644 
meta/recipes-core/glibc/glibc/0015-locale-prevent-maybe-uninitialized-errors-with-Os-BZ.patch
 rename 
meta/recipes-core/glibc/glibc/{0017-powerpc-Do-not-ask-compiler-for-finding-arch.patch
 => 0015-powerpc-Do-not-ask-compiler-for-finding-arch.patch} (96%)
 delete mode 100644 
meta/recipes-core/glibc/glibc/0016-readlib-Add-OECORE_KNOWN_INTERPRETER_NAMES-to-known-.patch
 rename 
meta/recipes-core/glibc/glibc/{0018-wordsize.h-Unify-the-header-between-arm-and-aarch64.patch
 => 0016-wordsize.h-Unify-the-header-between-arm-and-aarch64.patch} (72%)
 rename 
meta/recipes-core/glibc/glibc/{0019-Replace-echo-with-printf-builtin-in-nscd-init-script.patch
 => 0017-Replace-echo-with-printf-builtin-in-nscd-init-script.patch} (96%)
 rename 
meta/recipes-core/glibc/glibc/{0020-sysdeps-gnu-configure.ac-Set-libc_cv_rootsbindir-onl.patch
 => 0018-sysdeps-gnu-configure.ac-Set-libc_cv_rootsbindir-onl.patch} (94%)
 rename 
meta/recipes-core/glibc/glibc/{0021-timezone-Make-shell-interpreter-overridable-in-tzsel.patch
 => 0019-timezone-Make-shell-interpreter-overridable-in-tzsel.patch} (84%)
 rename 
meta/recipes-core/glibc/glibc/{0022-tzselect.ksh-Use-bin-sh-default-shell-interpreter.patch
 => 0020-tzselect.ksh-Use-bin-sh-default-shell-interpreter.patch} (93%)
 rename 
meta/recipes-core/glibc/glibc/{0023-fix-create-thread-failed-in-unprivileged-process-BZ-.patch
 => 0021-fix-create-thread-failed-in-unprivileged-process-BZ-.patch} (96%)
 rename 
meta/recipes-core/glibc/glibc/{0024-Avoid-hardcoded-build-time-paths-in-the-output-binar.patch
 => 0022-Avoid-hardcoded-build-time-paths-in-the-output-binar.patch} (88%)
 delete mode 100644 meta/recipes-core/glibc/glibc/0025-startup-Force-O2.patch
 rename meta/recipes-core/glibc/{glibc_2.36.bb => glibc_2.37.bb} (85%)

diff --git a/meta/conf/distro/include/tcmode-default.inc 
b/meta/conf/distro/include/tcmode-default.inc
index 7cd0b004e9..9236f8bf37 100644
--- a/meta/conf/distro/include/tcmode-default.inc
+++ b/meta/c

[OE-core] [PATCH] scons.bbclass: Make MAXLINELENGTH overridable

2023-02-02 Thread Khem Raj
older scons do not support MAXLINELENGTH and some packages still may be
using older scons, these recipes can clear SCONS_MAXLINELENGTH in them
and get going. Set

SCONS_MAXLINELENGTH = ""

in such recipes.

Signed-off-by: Khem Raj 
Cc: Martin Jansa 
---
 meta/classes-recipe/scons.bbclass | 9 +
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/meta/classes-recipe/scons.bbclass 
b/meta/classes-recipe/scons.bbclass
index d510c12b9b..d20a78dc6e 100644
--- a/meta/classes-recipe/scons.bbclass
+++ b/meta/classes-recipe/scons.bbclass
@@ -10,11 +10,12 @@ DEPENDS += "python3-scons-native"
 
 EXTRA_OESCONS ?= ""
 # This value below is derived from $(getconf ARG_MAX)
-SCONS_MAXLINELENGTH ?= "2097152"
+SCONS_MAXLINELENGTH ?= "MAXLINELENGTH=2097152"
+EXTRA_OESCONS:append = " ${SCONS_MAXLINELENGTH}"
 do_configure() {
if [ -n "${CONFIGURESTAMPFILE}" -a "${S}" = "${B}" ]; then
if [ -e "${CONFIGURESTAMPFILE}" -a "`cat 
${CONFIGURESTAMPFILE}`" != "${BB_TASKHASH}" -a "${CLEANBROKEN}" != "1" ]; then
-   ${STAGING_BINDIR_NATIVE}/scons --directory=${S} --clean 
PREFIX=${prefix} MAXLINELENGTH=${SCONS_MAXLINELENGTH} prefix=${prefix} 
${EXTRA_OESCONS}
+   ${STAGING_BINDIR_NATIVE}/scons --directory=${S} --clean 
PREFIX=${prefix} prefix=${prefix} ${EXTRA_OESCONS}
fi
 
mkdir -p `dirname ${CONFIGURESTAMPFILE}`
@@ -23,12 +24,12 @@ do_configure() {
 }
 
 scons_do_compile() {
-   ${STAGING_BINDIR_NATIVE}/scons --directory=${S} ${PARALLEL_MAKE} 
PREFIX=${prefix} prefix=${prefix} MAXLINELENGTH=${SCONS_MAXLINELENGTH} 
${EXTRA_OESCONS} || \
+   ${STAGING_BINDIR_NATIVE}/scons --directory=${S} ${PARALLEL_MAKE} 
PREFIX=${prefix} prefix=${prefix} ${EXTRA_OESCONS} || \
die "scons build execution failed."
 }
 
 scons_do_install() {
-   ${STAGING_BINDIR_NATIVE}/scons --directory=${S} 
install_root=${D}${prefix} PREFIX=${prefix} prefix=${prefix} 
MAXLINELENGTH=${SCONS_MAXLINELENGTH} ${EXTRA_OESCONS} install || \
+   ${STAGING_BINDIR_NATIVE}/scons --directory=${S} 
install_root=${D}${prefix} PREFIX=${prefix} prefix=${prefix} ${EXTRA_OESCONS} 
install || \
die "scons install execution failed."
 }
 
-- 
2.39.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#176684): 
https://lists.openembedded.org/g/openembedded-core/message/176684
Mute This Topic: https://lists.openembedded.org/mt/96696439/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] scons: Pass MAXLINELENGTH to scons invocation

2023-01-29 Thread Khem Raj
This helps in overcoming a problem when using scons with ccache enabled.
When commands get longer, then it resorts to using response files to do
the operations e.g. @/tmp/tmp96j6icra.lnk when this response file is
inboked by compiler it works ok, however, this does not when ccache is
used to invoke the complilation. We see errors e.g.

ccache @/tmp/tmppsyij_0v.lnk
ccache: error: execute_noreturn of @/tmp/tmppsyij_0v.lnk failed: No such file 
or directory

Using MAXLINELENGTH setting ensures that we can use ARG_MAX to extend
the length of commandline and hence avoid using response files. This
issue is also reported in mongodb [1]

[1] https://jira.mongodb.org/browse/SERVER-38389

Signed-off-by: Khem Raj 
---
 meta/classes-recipe/scons.bbclass | 13 +
 1 file changed, 9 insertions(+), 4 deletions(-)

diff --git a/meta/classes-recipe/scons.bbclass 
b/meta/classes-recipe/scons.bbclass
index 5f0d4a910b..d510c12b9b 100644
--- a/meta/classes-recipe/scons.bbclass
+++ b/meta/classes-recipe/scons.bbclass
@@ -9,11 +9,12 @@ inherit python3native
 DEPENDS += "python3-scons-native"
 
 EXTRA_OESCONS ?= ""
-
+# This value below is derived from $(getconf ARG_MAX)
+SCONS_MAXLINELENGTH ?= "2097152"
 do_configure() {
if [ -n "${CONFIGURESTAMPFILE}" -a "${S}" = "${B}" ]; then
if [ -e "${CONFIGURESTAMPFILE}" -a "`cat 
${CONFIGURESTAMPFILE}`" != "${BB_TASKHASH}" -a "${CLEANBROKEN}" != "1" ]; then
-   ${STAGING_BINDIR_NATIVE}/scons --directory=${S} --clean 
PREFIX=${prefix} prefix=${prefix} ${EXTRA_OESCONS}
+   ${STAGING_BINDIR_NATIVE}/scons --directory=${S} --clean 
PREFIX=${prefix} MAXLINELENGTH=${SCONS_MAXLINELENGTH} prefix=${prefix} 
${EXTRA_OESCONS}
fi
 
mkdir -p `dirname ${CONFIGURESTAMPFILE}`
@@ -22,13 +23,17 @@ do_configure() {
 }
 
 scons_do_compile() {
-   ${STAGING_BINDIR_NATIVE}/scons --directory=${S} ${PARALLEL_MAKE} 
PREFIX=${prefix} prefix=${prefix} ${EXTRA_OESCONS} || \
+   ${STAGING_BINDIR_NATIVE}/scons --directory=${S} ${PARALLEL_MAKE} 
PREFIX=${prefix} prefix=${prefix} MAXLINELENGTH=${SCONS_MAXLINELENGTH} 
${EXTRA_OESCONS} || \
die "scons build execution failed."
 }
 
 scons_do_install() {
-   ${STAGING_BINDIR_NATIVE}/scons --directory=${S} 
install_root=${D}${prefix} PREFIX=${prefix} prefix=${prefix} ${EXTRA_OESCONS} 
install || \
+   ${STAGING_BINDIR_NATIVE}/scons --directory=${S} 
install_root=${D}${prefix} PREFIX=${prefix} prefix=${prefix} 
MAXLINELENGTH=${SCONS_MAXLINELENGTH} ${EXTRA_OESCONS} install || \
die "scons install execution failed."
 }
 
+do_configure[vardepsexclude] = "SCONS_MAXLINELENGTH"
+do_compile[vardepsexclude] = "SCONS_MAXLINELENGTH"
+do_install[vardepsexclude] = "SCONS_MAXLINELENGTH"
+
 EXPORT_FUNCTIONS do_compile do_install
-- 
2.39.1


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



Re: [OE-core] [PATCH] nghttp2: Always enable python bindings

2023-01-28 Thread Khem Raj
I have sent a v2, please disregard this one.

On Sat, Jan 28, 2023 at 3:30 PM Khem Raj  wrote:
>
> This makes the build host agnostic, otherwise on some hosts e.g. (archlinux)
> it ends up using cython compiler from build host, mixing python3-native
> and cython from host is not a tested combination and can result in
> obscure errors. Lets make it use cython from OE native packages and also
> enable the bindings explicitly.
>
> Signed-off-by: Khem Raj 
> ---
>  meta/recipes-support/nghttp2/nghttp2_1.51.0.bb | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/meta/recipes-support/nghttp2/nghttp2_1.51.0.bb 
> b/meta/recipes-support/nghttp2/nghttp2_1.51.0.bb
> index fc1a592200..4402b80d1a 100644
> --- a/meta/recipes-support/nghttp2/nghttp2_1.51.0.bb
> +++ b/meta/recipes-support/nghttp2/nghttp2_1.51.0.bb
> @@ -4,6 +4,8 @@ SECTION = "libs"
>  LICENSE = "MIT"
>  LIC_FILES_CHKSUM = "file://COPYING;md5=764abdf30b2eadd37ce47dcbce0ea1ec"
>
> +DEPENDS += "python3-cython-native"
> +
>  SRC_URI = "\
>  ${GITHUB_BASE_URI}/download/v${PV}/nghttp2-${PV}.tar.xz \
>  file://0001-fetch-ocsp-response-use-python3.patch \
> @@ -15,7 +17,7 @@ PACKAGECONFIG[manpages] = ""
>
>  # examples are never installed, and don't need to be built in the
>  # first place
> -EXTRA_OECMAKE = "-DENABLE_EXAMPLES=OFF -DENABLE_APP=OFF 
> -DENABLE_HPACK_TOOLS=OFF"
> +EXTRA_OECMAKE = "-DENABLE_EXAMPLES=OFF -DENABLE_APP=OFF 
> -DENABLE_HPACK_TOOLS=OFF -DENABLE_PYTHON_BINDINGS=ON"
>
>  PACKAGES =+ "lib${BPN} ${PN}-client ${PN}-proxy ${PN}-server"
>
> --
> 2.39.1
>

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



[OE-core] [PATCH v2] nghttp2: Disable python bindings

2023-01-28 Thread Khem Raj
python bindings need cython to build, moreover they have been removed
from future releases upstream nghttp2 [1]

This ensures consistent builds as it does not need cython which was
being used from build host if it is installed. With some distros e.g.
archlinux it caused conflicts with python from python-native

[1] 
https://github.com/nghttp2/nghttp2/commit/b4cb3b0090b704f2461766c455568b311013272f

Signed-off-by: Khem Raj 
---
v2: Disable python bindings

 meta/recipes-support/nghttp2/nghttp2_1.51.0.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-support/nghttp2/nghttp2_1.51.0.bb 
b/meta/recipes-support/nghttp2/nghttp2_1.51.0.bb
index fc1a592200..8ddb851f71 100644
--- a/meta/recipes-support/nghttp2/nghttp2_1.51.0.bb
+++ b/meta/recipes-support/nghttp2/nghttp2_1.51.0.bb
@@ -15,7 +15,7 @@ PACKAGECONFIG[manpages] = ""
 
 # examples are never installed, and don't need to be built in the
 # first place
-EXTRA_OECMAKE = "-DENABLE_EXAMPLES=OFF -DENABLE_APP=OFF 
-DENABLE_HPACK_TOOLS=OFF"
+EXTRA_OECMAKE = "-DENABLE_EXAMPLES=OFF -DENABLE_APP=OFF 
-DENABLE_HPACK_TOOLS=OFF -DENABLE_PYTHON_BINDINGS=OFF"
 
 PACKAGES =+ "lib${BPN} ${PN}-client ${PN}-proxy ${PN}-server"
 
-- 
2.39.1


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



Re: [OE-core] [PATCH 2/2] curl: enable nghttp2 for support HTTP2

2023-01-28 Thread Khem Raj
I have sent a fix for nghttp2 which unblocks builds on archlinux build
hosts atleast.

On Sat, Jan 28, 2023 at 3:17 PM Khem Raj  wrote:
>
> still failing on archlinux
>
> | [26/27] Generating nghttp2.c
> | /usr/lib/python3.10/site-packages/Cython/Compiler/Main.py:369:
> FutureWarning: Cython directive 'language_level' not set, using 2 for
> now (Py2). This will change in a later release! File:
> /mnt/b/yoe/master/build/tmp/work/x86_64-linux/nghttp2-native/1.51.0-r0/nghttp2-1.51.0/python/nghttp2.pyx
> |   tree = Parsing.p_module(s, pxd, full_module_name)
> | [27/27] cd 
> /mnt/b/yoe/master/build/tmp/work/x86_64-linux/nghttp2-native/1.51.0-r0/build/python
> && 
> /mnt/b/yoe/master/build/tmp/work/x86_64-linux/nghttp2-native/1.51.0-r0/recipe-sysroot-native/usr/bin/python3-native/python3
> setup.py build
> | FAILED: python/CMakeFiles/python
> /mnt/b/yoe/master/build/tmp/work/x86_64-linux/nghttp2-native/1.51.0-r0/build/python/CMakeFiles/python
> | cd 
> /mnt/b/yoe/master/build/tmp/work/x86_64-linux/nghttp2-native/1.51.0-r0/build/python
> && 
> /mnt/b/yoe/master/build/tmp/work/x86_64-linux/nghttp2-native/1.51.0-r0/recipe-sysroot-native/usr/bin/python3-native/python3
> setup.py build
> | Traceback (most recent call last):
> |   File 
> "/mnt/b/yoe/master/build/tmp/work/x86_64-linux/nghttp2-native/1.51.0-r0/build/python/setup.py",
> line 24, in 
> | from setuptools import setup, Extension
> | ModuleNotFoundError: No module named 'setuptools'
> | ninja: build stopped: subcommand failed.
> | WARNING: 
> /mnt/b/yoe/master/build/tmp/work/x86_64-linux/nghttp2-native/1.51.0-r0/temp/run.do_compile.2200023:167
> exit 1 from 'eval ${DESTDIR:+DESTDIR=${DESTDIR} } cmake --build
> '/mnt/b/yoe/master/build/tmp/work/x86_64-linux/nghttp2-native/1.51.0-r0/build'
> "$@" -- ${EXTRA_OECMAKE_BUILD}'
>
>
>
> On Sat, Jan 28, 2023 at 12:03 AM Changqing Li
>  wrote:
> >
> > On 1/20/23 09:48, Changqing Li wrote:
> > >
> > > On 1/16/23 05:30, Alexandre Belloni wrote:
> > >> CAUTION: This email comes from a non Wind River email account!
> > >> Do not click links or open attachments unless you recognize the
> > >> sender and know the content is safe.
> > >>
> > >> On 13/01/2023 16:04:42+0800, Changqing Li wrote:
> > >>> On 1/5/23 22:09, Alexandre Belloni wrote:
> > >>>> CAUTION: This email comes from a non Wind River email account!
> > >>>> Do not click links or open attachments unless you recognize the
> > >>>> sender and know the content is safe.
> > >>>>
> > >>>> This fails on the AB:
> > >>>>
> > >>>> https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/4580/steps/14/logs/stdio
> > >>>>
> > >>> Hi, Alexandre
> > >>>
> > >>> I need some help to debug this issue.
> > >>>
> > >>> I cannot reproduce this issue on my host. First,  the gcc command
> > >>> used to
> > >>> build the binary conftest will
> > >>>
> > >>> have as-needed enabled by default,  so actually,  these libs will
> > >>> not be
> > >>> linked, and runtime check will passed.
> > >>>
> > >>> Refer the command:
> > >>>
> > >>> gcc -o conftest
> > >>> -isystem/mnt/lincd/build/tmp-glibc/work/x86_64-linux/curl-native/7.87.0-r0/recipe-sysroot-native/usr/include
> > >>> -pipe -Werror-implicit-function-declaration -g -O2 -std=gnu89 -pedantic
> > >>> -Wall -W -Wpointer-arith -Wwrite-strings -Wunused -Wshadow -Winline
> > >>> -Wnested-externs -Wmissing-declarations -Wmissing-prototypes
> > >>> -Wno-long-long
> > >>> -Wbad-function-cast -Wfloat-equal -Wno-multichar -Wsign-compare -Wundef
> > >>> -Wno-format-nonliteral -Wendif-labels -Wstrict-prototypes
> > >>> -Wdeclaration-after-statement -Wold-style-definition
> > >>> -Wstrict-aliasing=3
> > >>> -Wcast-align -Wtype-limits -Wold-style-declaration
> > >>> -Wmissing-parameter-type
> > >>> -Wempty-body -Wclobbered -Wignored-qualifiers -Wconversion
> > >>> -Wno-sign-conversion -Wvla -ftree-vrp -Wdouble-promotion -Wformat=2
> > >>> -Warray-bounds=2 -Wshift-negative-value -Wshift-overflow=2
> > >>> -Wnull-dereference -fdelete-null-pointer-checks -Wduplicated-cond
> > >>> -Wunused-const-variable -Wduplicated-branches -Wrestrict -Walloc-zero
> > >>> -Wformat-ove

[OE-core] [PATCH] nghttp2: Always enable python bindings

2023-01-28 Thread Khem Raj
This makes the build host agnostic, otherwise on some hosts e.g. (archlinux)
it ends up using cython compiler from build host, mixing python3-native
and cython from host is not a tested combination and can result in
obscure errors. Lets make it use cython from OE native packages and also
enable the bindings explicitly.

Signed-off-by: Khem Raj 
---
 meta/recipes-support/nghttp2/nghttp2_1.51.0.bb | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-support/nghttp2/nghttp2_1.51.0.bb 
b/meta/recipes-support/nghttp2/nghttp2_1.51.0.bb
index fc1a592200..4402b80d1a 100644
--- a/meta/recipes-support/nghttp2/nghttp2_1.51.0.bb
+++ b/meta/recipes-support/nghttp2/nghttp2_1.51.0.bb
@@ -4,6 +4,8 @@ SECTION = "libs"
 LICENSE = "MIT"
 LIC_FILES_CHKSUM = "file://COPYING;md5=764abdf30b2eadd37ce47dcbce0ea1ec"
 
+DEPENDS += "python3-cython-native"
+
 SRC_URI = "\
 ${GITHUB_BASE_URI}/download/v${PV}/nghttp2-${PV}.tar.xz \
 file://0001-fetch-ocsp-response-use-python3.patch \
@@ -15,7 +17,7 @@ PACKAGECONFIG[manpages] = ""
 
 # examples are never installed, and don't need to be built in the
 # first place
-EXTRA_OECMAKE = "-DENABLE_EXAMPLES=OFF -DENABLE_APP=OFF 
-DENABLE_HPACK_TOOLS=OFF"
+EXTRA_OECMAKE = "-DENABLE_EXAMPLES=OFF -DENABLE_APP=OFF 
-DENABLE_HPACK_TOOLS=OFF -DENABLE_PYTHON_BINDINGS=ON"
 
 PACKAGES =+ "lib${BPN} ${PN}-client ${PN}-proxy ${PN}-server"
 
-- 
2.39.1


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



Re: [OE-core] [PATCH 2/2] curl: enable nghttp2 for support HTTP2

2023-01-28 Thread Khem Raj
still failing on archlinux

| [26/27] Generating nghttp2.c
| /usr/lib/python3.10/site-packages/Cython/Compiler/Main.py:369:
FutureWarning: Cython directive 'language_level' not set, using 2 for
now (Py2). This will change in a later release! File:
/mnt/b/yoe/master/build/tmp/work/x86_64-linux/nghttp2-native/1.51.0-r0/nghttp2-1.51.0/python/nghttp2.pyx
|   tree = Parsing.p_module(s, pxd, full_module_name)
| [27/27] cd 
/mnt/b/yoe/master/build/tmp/work/x86_64-linux/nghttp2-native/1.51.0-r0/build/python
&& 
/mnt/b/yoe/master/build/tmp/work/x86_64-linux/nghttp2-native/1.51.0-r0/recipe-sysroot-native/usr/bin/python3-native/python3
setup.py build
| FAILED: python/CMakeFiles/python
/mnt/b/yoe/master/build/tmp/work/x86_64-linux/nghttp2-native/1.51.0-r0/build/python/CMakeFiles/python
| cd 
/mnt/b/yoe/master/build/tmp/work/x86_64-linux/nghttp2-native/1.51.0-r0/build/python
&& 
/mnt/b/yoe/master/build/tmp/work/x86_64-linux/nghttp2-native/1.51.0-r0/recipe-sysroot-native/usr/bin/python3-native/python3
setup.py build
| Traceback (most recent call last):
|   File 
"/mnt/b/yoe/master/build/tmp/work/x86_64-linux/nghttp2-native/1.51.0-r0/build/python/setup.py",
line 24, in 
| from setuptools import setup, Extension
| ModuleNotFoundError: No module named 'setuptools'
| ninja: build stopped: subcommand failed.
| WARNING: 
/mnt/b/yoe/master/build/tmp/work/x86_64-linux/nghttp2-native/1.51.0-r0/temp/run.do_compile.2200023:167
exit 1 from 'eval ${DESTDIR:+DESTDIR=${DESTDIR} } cmake --build
'/mnt/b/yoe/master/build/tmp/work/x86_64-linux/nghttp2-native/1.51.0-r0/build'
"$@" -- ${EXTRA_OECMAKE_BUILD}'



On Sat, Jan 28, 2023 at 12:03 AM Changqing Li
 wrote:
>
> On 1/20/23 09:48, Changqing Li wrote:
> >
> > On 1/16/23 05:30, Alexandre Belloni wrote:
> >> CAUTION: This email comes from a non Wind River email account!
> >> Do not click links or open attachments unless you recognize the
> >> sender and know the content is safe.
> >>
> >> On 13/01/2023 16:04:42+0800, Changqing Li wrote:
> >>> On 1/5/23 22:09, Alexandre Belloni wrote:
>  CAUTION: This email comes from a non Wind River email account!
>  Do not click links or open attachments unless you recognize the
>  sender and know the content is safe.
> 
>  This fails on the AB:
> 
>  https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/4580/steps/14/logs/stdio
> 
> >>> Hi, Alexandre
> >>>
> >>> I need some help to debug this issue.
> >>>
> >>> I cannot reproduce this issue on my host. First,  the gcc command
> >>> used to
> >>> build the binary conftest will
> >>>
> >>> have as-needed enabled by default,  so actually,  these libs will
> >>> not be
> >>> linked, and runtime check will passed.
> >>>
> >>> Refer the command:
> >>>
> >>> gcc -o conftest
> >>> -isystem/mnt/lincd/build/tmp-glibc/work/x86_64-linux/curl-native/7.87.0-r0/recipe-sysroot-native/usr/include
> >>> -pipe -Werror-implicit-function-declaration -g -O2 -std=gnu89 -pedantic
> >>> -Wall -W -Wpointer-arith -Wwrite-strings -Wunused -Wshadow -Winline
> >>> -Wnested-externs -Wmissing-declarations -Wmissing-prototypes
> >>> -Wno-long-long
> >>> -Wbad-function-cast -Wfloat-equal -Wno-multichar -Wsign-compare -Wundef
> >>> -Wno-format-nonliteral -Wendif-labels -Wstrict-prototypes
> >>> -Wdeclaration-after-statement -Wold-style-definition
> >>> -Wstrict-aliasing=3
> >>> -Wcast-align -Wtype-limits -Wold-style-declaration
> >>> -Wmissing-parameter-type
> >>> -Wempty-body -Wclobbered -Wignored-qualifiers -Wconversion
> >>> -Wno-sign-conversion -Wvla -ftree-vrp -Wdouble-promotion -Wformat=2
> >>> -Warray-bounds=2 -Wshift-negative-value -Wshift-overflow=2
> >>> -Wnull-dereference -fdelete-null-pointer-checks -Wduplicated-cond
> >>> -Wunused-const-variable -Wduplicated-branches -Wrestrict -Walloc-zero
> >>> -Wformat-overflow=2 -Wformat-truncation=2 -Wimplicit-fallthrough=4
> >>> -Wno-system-headers
> >>> -isystem/mnt/lincd/build/tmp-glibc/work/x86_64-linux/curl-native/7.87.0-r0/recipe-sysroot-native/usr/include
> >>> -I/mnt/lincd/build/tmp-glibc/work/x86_64-linux/curl-native/7.87.0-r0/recipe-sysroot-native/usr/lib/..//include
> >>> -I/mnt/lincd/build/tmp-glibc/work/x86_64-linux/curl-native/7.87.0-r0/recipe-sysroot-native/usr/lib/pkgconfig/../../../usr/include
> >>>
> >>> -DOPENSSL_SUPPRESS_DEPRECATED
> >>> -I/mnt/lincd/build/tmp-glibc/work/x86_64-linux/curl-native/7.87.0-r0/recipe-sysroot-native/usr/lib/pkgconfig/../../../usr/include
> >>> -L/mnt/lincd/build/tmp-glibc/work/x86_64-linux/curl-native/7.87.0-r0/recipe-sysroot-native/usr/lib
> >>> -L/mnt/lincd/build/tmp-glibc/work/x86_64-linux/curl-native/7.87.0-r0/recipe-sysroot-native/lib
> >>>
> >>> -Wl,--enable-new-dtags
> >>> -Wl,-rpath-link,/mnt/lincd/build/tmp-glibc/work/x86_64-linux/curl-native/7.87.0-r0/recipe-sysroot-native/usr/lib
> >>> -Wl,-rpath-link,/mnt/lincd/build/tmp-glibc/work/x86_64-linux/curl-native/7.87.0-r0/recipe-sysroot-native/lib
> >>> 

[OE-core] [PATCH v2 1/2] busybox: 1.35.0 -> 1.36.0

2023-01-26 Thread Khem Raj
From: Andrej Valek 

- update to next (un)stable version 1.36.0
- refresh defconfig
 - disable new applets (tree, tsort, seedrng)
 - use hw-accel for sha1/256 sums when available
- remove and refresh already merged patches

Signed-off-by: Andrej Valek 
Signed-off-by: Khem Raj 
---
v2: Rebased

 ...ab_1.35.0.bb => busybox-inittab_1.36.0.bb} |   0
 .../0001-devmem-add-128-bit-width.patch   | 128 --
 .../busybox/busybox/CVE-2022-30065.patch  |  29 
 meta/recipes-core/busybox/busybox/defconfig   |  10 +-
 .../busybox/busybox/recognize_connmand.patch  |  10 +-
 meta/recipes-core/busybox/busybox/sha1sum.cfg |   2 +
 .../busybox/busybox/sha256sum.cfg |   1 +
 .../{busybox_1.35.0.bb => busybox_1.36.0.bb}  |   4 +-
 8 files changed, 17 insertions(+), 167 deletions(-)
 rename meta/recipes-core/busybox/{busybox-inittab_1.35.0.bb => 
busybox-inittab_1.36.0.bb} (100%)
 delete mode 100644 
meta/recipes-core/busybox/busybox/0001-devmem-add-128-bit-width.patch
 delete mode 100644 meta/recipes-core/busybox/busybox/CVE-2022-30065.patch
 rename meta/recipes-core/busybox/{busybox_1.35.0.bb => busybox_1.36.0.bb} (92%)

diff --git a/meta/recipes-core/busybox/busybox-inittab_1.35.0.bb 
b/meta/recipes-core/busybox/busybox-inittab_1.36.0.bb
similarity index 100%
rename from meta/recipes-core/busybox/busybox-inittab_1.35.0.bb
rename to meta/recipes-core/busybox/busybox-inittab_1.36.0.bb
diff --git 
a/meta/recipes-core/busybox/busybox/0001-devmem-add-128-bit-width.patch 
b/meta/recipes-core/busybox/busybox/0001-devmem-add-128-bit-width.patch
deleted file mode 100644
index 985e2bf1d9..00
--- a/meta/recipes-core/busybox/busybox/0001-devmem-add-128-bit-width.patch
+++ /dev/null
@@ -1,128 +0,0 @@
-From d432049f288c9acdc4a7caa729c68ceba3c5dca1 Mon Sep 17 00:00:00 2001
-From: Aaro Koskinen 
-Date: Thu, 25 Aug 2022 18:47:02 +0300
-Subject: [PATCH] devmem: add 128-bit width
-
-Add 128-bit width if the compiler provides the needed type.
-
-function old new   delta
-devmem_main  405 464 +59
-.rodata   109025  109043 +18
---
-(add/remove: 0/0 grow/shrink: 2/0 up/down: 77/0)   Total: 77 bytes
-
-Upstream-Status: Backport 
[https://git.busybox.net/busybox/commit/?id=d432049f288c9acdc4a7caa729c68ceba3c5dca1]
-
-Signed-off-by: Aaro Koskinen 
-Signed-off-by: Aaro Koskinen 
-Signed-off-by: Denys Vlasenko 
-Signed-off-by: Mingli Yu 

- miscutils/devmem.c | 68 ++
- 1 file changed, 44 insertions(+), 24 deletions(-)
-
-diff --git a/miscutils/devmem.c b/miscutils/devmem.c
-index f9f0276bc..f21621bd6 100644
 a/miscutils/devmem.c
-+++ b/miscutils/devmem.c
-@@ -29,7 +29,6 @@ int devmem_main(int argc UNUSED_PARAM, char **argv)
- {
-   void *map_base, *virt_addr;
-   uint64_t read_result;
--  uint64_t writeval = writeval; /* for compiler */
-   off_t target;
-   unsigned page_size, mapped_size, offset_in_page;
-   int fd;
-@@ -64,9 +63,6 @@ int devmem_main(int argc UNUSED_PARAM, char **argv)
-   width = strchrnul(bhwl, (argv[2][0] | 0x20)) - bhwl;
-   width = sizes[width];
-   }
--  /* VALUE */
--  if (argv[3])
--  writeval = bb_strtoull(argv[3], NULL, 0);
-   } else { /* argv[2] == NULL */
-   /* make argv[3] to be a valid thing to fetch */
-   argv--;
-@@ -96,28 +92,46 @@ int devmem_main(int argc UNUSED_PARAM, char **argv)
-   virt_addr = (char*)map_base + offset_in_page;
- 
-   if (!argv[3]) {
--  switch (width) {
--  case 8:
--  read_result = *(volatile uint8_t*)virt_addr;
--  break;
--  case 16:
--  read_result = *(volatile uint16_t*)virt_addr;
--  break;
--  case 32:
--  read_result = *(volatile uint32_t*)virt_addr;
--  break;
--  case 64:
--  read_result = *(volatile uint64_t*)virt_addr;
--  break;
--  default:
--  bb_simple_error_msg_and_die("bad width");
-+#ifdef __SIZEOF_INT128__
-+  if (width == 128) {
-+  unsigned __int128 rd =
-+  *(volatile unsigned __int128 *)virt_addr;
-+  printf("0x%016llX%016llX\n",
-+  (unsigned long long)(uint64_t)(rd >> 64),
-+  (unsigned long long)(uint64_t)rd
-+  );
-+  } else
-+#endif
-+  {
-+  switch (width) {
-+  case 8:
-+

[OE-core] [PATCH 2/2] busybox: Make provisions to disable sha256/sha1 accelaration on x86

2023-01-26 Thread Khem Raj
busybox 1.36 has an ongoing regression on musl/i386 [1] we see same on
glibc systems too.
therefore avoid the affected code by disabling sha256/sha1 sum accelaration
meanwhile

CONFIG_SHA256_HWACCEL and CONFIG_SHA1_HWACCEL are enabled by default

[1] http://lists.busybox.net/pipermail/busybox/2023-January/090078.html

Signed-off-by: Khem Raj 
Cc: Andrej Valek 
---
v2: Disable sha accels on glibc/x86 as well

 meta/recipes-core/busybox/busybox/sha1sum.cfg   | 1 -
 meta/recipes-core/busybox/busybox/sha256sum.cfg | 1 -
 meta/recipes-core/busybox/busybox/sha_accel.cfg | 2 ++
 meta/recipes-core/busybox/busybox_1.36.0.bb | 3 ++-
 4 files changed, 4 insertions(+), 3 deletions(-)
 create mode 100644 meta/recipes-core/busybox/busybox/sha_accel.cfg

diff --git a/meta/recipes-core/busybox/busybox/sha1sum.cfg 
b/meta/recipes-core/busybox/busybox/sha1sum.cfg
index 01137a2486..afd4da4ea1 100644
--- a/meta/recipes-core/busybox/busybox/sha1sum.cfg
+++ b/meta/recipes-core/busybox/busybox/sha1sum.cfg
@@ -1,3 +1,2 @@
 CONFIG_SHA1SUM=y
 CONFIG_SHA1_SMALL=3
-CONFIG_SHA1_HWACCEL=y
diff --git a/meta/recipes-core/busybox/busybox/sha256sum.cfg 
b/meta/recipes-core/busybox/busybox/sha256sum.cfg
index a5b0ab22d1..ce652ae4c6 100644
--- a/meta/recipes-core/busybox/busybox/sha256sum.cfg
+++ b/meta/recipes-core/busybox/busybox/sha256sum.cfg
@@ -1,2 +1 @@
 CONFIG_SHA256SUM=y
-CONFIG_SHA256_HWACCEL=y
diff --git a/meta/recipes-core/busybox/busybox/sha_accel.cfg 
b/meta/recipes-core/busybox/busybox/sha_accel.cfg
new file mode 100644
index 00..8900305a11
--- /dev/null
+++ b/meta/recipes-core/busybox/busybox/sha_accel.cfg
@@ -0,0 +1,2 @@
+# CONFIG_SHA256_HWACCEL is not set
+# CONFIG_SHA1_HWACCEL is not set
diff --git a/meta/recipes-core/busybox/busybox_1.36.0.bb 
b/meta/recipes-core/busybox/busybox_1.36.0.bb
index e46d43e681..8014a5c7bf 100644
--- a/meta/recipes-core/busybox/busybox_1.36.0.bb
+++ b/meta/recipes-core/busybox/busybox_1.36.0.bb
@@ -51,5 +51,6 @@ SRC_URI = 
"https://busybox.net/downloads/busybox-${PV}.tar.bz2;name=tarball \

file://0002-nslookup-sanitize-all-printed-strings-with-printable.patch \
"
 SRC_URI:append:libc-musl = " file://musl.cfg "
-
+# TODO http://lists.busybox.net/pipermail/busybox/2023-January/090078.html
+SRC_URI:append:x86 = " file://sha_accel.cfg"
 SRC_URI[tarball.sha256sum] = 
"542750c8af7cb2630e201780b4f99f3dcceeb06f505b479ec68241c1e6af61a5"
-- 
2.39.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#176429): 
https://lists.openembedded.org/g/openembedded-core/message/176429
Mute This Topic: https://lists.openembedded.org/mt/96553635/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] gdb: Define alignof using _Alignof when using C11 or newer

2023-01-26 Thread Khem Raj
Signed-off-by: Khem Raj 
---
 meta/recipes-devtools/gdb/gdb.inc |  1 +
 ...sing-_Alignof-when-using-C11-or-newe.patch | 55 +++
 2 files changed, 56 insertions(+)
 create mode 100644 
meta/recipes-devtools/gdb/gdb/0008-Define-alignof-using-_Alignof-when-using-C11-or-newe.patch

diff --git a/meta/recipes-devtools/gdb/gdb.inc 
b/meta/recipes-devtools/gdb/gdb.inc
index 5a9fe271b9..a5dc554581 100644
--- a/meta/recipes-devtools/gdb/gdb.inc
+++ b/meta/recipes-devtools/gdb/gdb.inc
@@ -15,5 +15,6 @@ SRC_URI = "${GNU_MIRROR}/gdb/gdb-${PV}.tar.xz \
file://0008-Fix-invalid-sigprocmask-call.patch \
file://0009-gdbserver-ctrl-c-handling.patch \
file://readline-8.2.patch \
+   
file://0008-Define-alignof-using-_Alignof-when-using-C11-or-newe.patch \
"
 SRC_URI[sha256sum] = 
"0e1793bf8f2b54d53f46dea84ccfd446f48f81b297b28c4f7fc017b818d69fed"
diff --git 
a/meta/recipes-devtools/gdb/gdb/0008-Define-alignof-using-_Alignof-when-using-C11-or-newe.patch
 
b/meta/recipes-devtools/gdb/gdb/0008-Define-alignof-using-_Alignof-when-using-C11-or-newe.patch
new file mode 100644
index 00..3e29327613
--- /dev/null
+++ 
b/meta/recipes-devtools/gdb/gdb/0008-Define-alignof-using-_Alignof-when-using-C11-or-newe.patch
@@ -0,0 +1,55 @@
+From 48906e1038e469b429aa35d0f967730a929c3880 Mon Sep 17 00:00:00 2001
+From: Khem Raj 
+Date: Sun, 15 Jan 2023 00:16:25 -0800
+Subject: [PATCH 8/8] Define alignof using _Alignof when using C11 or newer
+
+WG14 N2350 made very clear that it is an UB having type definitions
+within "offsetof" [1]. This patch enhances the implementation of macro
+alignof_slot to use builtin "_Alignof" to avoid undefined behavior on
+when using std=c11 or newer
+
+clang 16+ has started to flag this [2]
+
+Fixes build when using -std >= gnu11 and using clang16+
+
+Older compilers gcc < 4.9 or clang < 8 has buggy _Alignof even though it
+may support C11, exclude those compilers too
+
+gnulib needs this fix and then it will be applied to downstream packages
+like gdb [3]
+
+[1] https://www.open-std.org/jtc1/sc22/wg14/www/docs/n2350.htm
+[2] https://reviews.llvm.org/D133574
+[3] 
https://public-inbox.org/bug-gnulib/20230114232744.215167-1-raj.k...@gmail.com/T/#u
+
+Upstream-Status: Backport 
[https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=2d404c7dd974cc65f894526f4a1b76bc1dcd8d82]
+Signed-off-by: Khem Raj 
+---
+ libiberty/sha1.c | 10 ++
+ 1 file changed, 10 insertions(+)
+
+diff --git a/libiberty/sha1.c b/libiberty/sha1.c
+index 504f06d3b9b..790ada82443 100644
+--- a/libiberty/sha1.c
 b/libiberty/sha1.c
+@@ -229,7 +229,17 @@ sha1_process_bytes (const void *buffer, size_t len, 
struct sha1_ctx *ctx)
+   if (len >= 64)
+ {
+ #if !_STRING_ARCH_unaligned
++/* GCC releases before GCC 4.9 had a bug in _Alignof.  See GCC bug 52023
++   <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52023>.
++   clang versions < 8.0.0 have the same bug.  */
++#if (!defined __STDC_VERSION__ || __STDC_VERSION__ < 201112 \
++ || (defined __GNUC__ && __GNUC__ < 4 + (__GNUC_MINOR__ < 9) \
++  && !defined __clang__) \
++ || (defined __clang__ && __clang_major__ < 8))
+ # define alignof(type) offsetof (struct { char c; type x; }, x)
++#else
++# define alignof(type) _Alignof(type)
++#endif
+ # define UNALIGNED_P(p) (((size_t) p) % alignof (sha1_uint32) != 0)
+   if (UNALIGNED_P (buffer))
+   while (len > 64)
+-- 
+2.39.0
+
-- 
2.39.1


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



Re: [OE-core] [PATCH 2/2] wic/efi-bootdisk.wks: Fix for 6.1 kernel versions

2023-01-26 Thread Khem Raj
On Thu, Jan 26, 2023 at 9:16 AM Richard Purdie
 wrote:
>
> oe-selftest efibootpartition.GenericEFITest.test_boot_efi was failing for 6.1 
> kernels with:
>
> | ERROR: _exec_cmd: export PATH=[...] mcopy -i [...]/rootfs_boot.1.vfat -s 
> [...]/rootfs1/* ::/ returned '1' instead of 0
> | output: Disk full
>
> I believe we hit a file boundary size and having "0" overhead in the image 
> meant
> the files couldn't be installed. Allow a small amount of overhead to avoid
> the error.

Just curious. how big is 6.1 size compared to 5.19 ?

>
> Signed-off-by: Richard Purdie 
> ---
>  scripts/lib/wic/canned-wks/efi-bootdisk.wks.in | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/lib/wic/canned-wks/efi-bootdisk.wks.in 
> b/scripts/lib/wic/canned-wks/efi-bootdisk.wks.in
> index 7300e65e32d..2fd286ff982 100644
> --- a/scripts/lib/wic/canned-wks/efi-bootdisk.wks.in
> +++ b/scripts/lib/wic/canned-wks/efi-bootdisk.wks.in
> @@ -1,3 +1,3 @@
>  bootloader --ptable gpt
> -part /boot --source rootfs --rootfs-dir=${IMAGE_ROOTFS}/boot --fstype=vfat 
> --label boot --active --align 1024 --use-uuid --overhead-factor 1.0
> +part /boot --source rootfs --rootfs-dir=${IMAGE_ROOTFS}/boot --fstype=vfat 
> --label boot --active --align 1024 --use-uuid --overhead-factor 1.1
>  part / --source rootfs --fstype=ext4 --label root --align 1024 
> --exclude-path boot/
> --
> 2.37.2
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#176420): 
https://lists.openembedded.org/g/openembedded-core/message/176420
Mute This Topic: https://lists.openembedded.org/mt/96547775/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 0/2] kernel-yocto: drop 5.19 recipes and make 6.1 default

2023-01-26 Thread Khem Raj
On Thu, Jan 26, 2023 at 10:06 AM Bruce Ashfield
 wrote:
>
> On Thu, Jan 26, 2023 at 12:58 PM Khem Raj  wrote:
> >
> > we need to define
> >
> > KBUILD_BUILD_USER="yocto"
> > KBUILD_BUILD_HOST="yocto"
> >
> > in linux-yocto defconfigs
> >
>
> No, we really don't want to do that.
>
> There's an environment variable that is supposed to be reflected in
> the build. Which we already set.

a better location would be distro config defining it and derived
distros can override it if needed.

>
> If that has changed in 6.1, then I'll come up with a patch as required.
>
> Bruce
>
> > You can use my name too :)
> >
> > On Thu, Jan 26, 2023 at 9:34 AM Richard Purdie
> >  wrote:
> > >
> > > On Thu, 2023-01-26 at 12:07 -0500, Bruce Ashfield wrote:
> > > > On Thu, Jan 26, 2023 at 11:36 AM Richard Purdie
> > > >  wrote:
> > > > >
> > > > > On Thu, 2023-01-26 at 17:21 +0100, Alexandre Belloni wrote:
> > > > > > On 26/01/2023 12:39:02+, Richard Purdie wrote:
> > > > > > > On Tue, 2023-01-24 at 16:59 -0500, bruce.ashfi...@gmail.com wrote:
> > > > > > > > From: Bruce Ashfield 
> > > > > > > >
> > > > > > > > Richard,
> > > > > > > >
> > > > > > > > As promised, here are the commits to switch us over to 6.1 as 
> > > > > > > > the
> > > > > > > > default.
> > > > > > > >
> > > > > > > > I'll also send a series for poky to bump things there as well.
> > > > > > > >
> > > > > > > > Also, if there are any significant problems, we'll just shelve 
> > > > > > > > this
> > > > > > > > while I look at any issues. But at this point, it is worth 
> > > > > > > > getting
> > > > > > > > the patches out there to move the needle to 6.1
> > > > > > >
> > > > > > > Thanks!
> > > > > > >
> > > > > > > I think the issues are:
> > > > > > >
> > > > > > > a) two selftest failures:
> > > > > > >
> > > > > > >   oe-selftest -r 
> > > > > > > devtool.DevtoolUpgradeTests.test_devtool_virtual_kernel_modify
> > > > > > >   oe-selftest -r efibootpartition.GenericEFITest.test_boot_efi
> > > > > > >
> > > > > > > b) meta-arm issues
> > > > > > >
> > > > > > > c) meta-virt issue (which you have a patch pending for in -next)
> > > > > > >
> > > > > >
> > > > > > Unfortunately, I have to add
> > > > > >
> > > > > > d) perf reproducibility issues:
> > > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/2294/steps/13/logs/stdio
> > > > >
> > > > > Ahrrg.
> > > > >
> > > > > http://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20230126-poma_o8v/packages/diff-html/
> > > > >
> > > > >
> > > > > /lib/modules/6.1.5-yocto-standard/build/include/generated/compile.h
> > > > >
> > > > > from
> > > > >
> > > > > #define·LINUX_COMPILE_HOST»  "alma8-ty-2.yocto.io
> > > > >
> > > > > to
> > > > >
> > > > > #define·LINUX_COMPILE_HOST»  "ubuntu2004-ty-1"
> > > > >
> > > > > Bruce: Any idea if we can set that to some specific value?
> > > > >
> > > > > We probably should start by fixing that and then see if that improves
> > > > > things...
> > > >
> > > > Interesting. In my local builds:
> > > >
> > > > #define LINUX_COMPILE_HOST  "oe-host"
> > > >
> > > > I'm building 6.1.7, but that shouldn't be the difference.
> > > >
> > > > The value comes from: classes-recipe/kernel.bbclass:export
> > > > KBUILD_BUILD_HOST ?= "oe-host",
> > > > and has been that way for a while.
> > > >
> > > > I'm also grepping for other BUILDPATHS references, but the QA test
> > > > should have caught
> > > > those if that was the issue.
> > >
> > >
> > > I just realised that there are two issues, one is perf, the other is
> > > kernel-devsrc. The compile.h issue is in kernel-devsrc and that did
> > > reproduce for my locally just now. I'm not sure what is wrong with
> > > perf...
> > >
> > > Cheers,
> > >
> > > Richard
> > >
> > >
> > >
> > >
> > > 
> > >
>
>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end
> - "Use the force Harry" - Gandalf, Star Trek II

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#176419): 
https://lists.openembedded.org/g/openembedded-core/message/176419
Mute This Topic: https://lists.openembedded.org/mt/96508797/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 0/2] kernel-yocto: drop 5.19 recipes and make 6.1 default

2023-01-26 Thread Khem Raj
we need to define

KBUILD_BUILD_USER="yocto"
KBUILD_BUILD_HOST="yocto"

in linux-yocto defconfigs

You can use my name too :)

On Thu, Jan 26, 2023 at 9:34 AM Richard Purdie
 wrote:
>
> On Thu, 2023-01-26 at 12:07 -0500, Bruce Ashfield wrote:
> > On Thu, Jan 26, 2023 at 11:36 AM Richard Purdie
> >  wrote:
> > >
> > > On Thu, 2023-01-26 at 17:21 +0100, Alexandre Belloni wrote:
> > > > On 26/01/2023 12:39:02+, Richard Purdie wrote:
> > > > > On Tue, 2023-01-24 at 16:59 -0500, bruce.ashfi...@gmail.com wrote:
> > > > > > From: Bruce Ashfield 
> > > > > >
> > > > > > Richard,
> > > > > >
> > > > > > As promised, here are the commits to switch us over to 6.1 as the
> > > > > > default.
> > > > > >
> > > > > > I'll also send a series for poky to bump things there as well.
> > > > > >
> > > > > > Also, if there are any significant problems, we'll just shelve this
> > > > > > while I look at any issues. But at this point, it is worth getting
> > > > > > the patches out there to move the needle to 6.1
> > > > >
> > > > > Thanks!
> > > > >
> > > > > I think the issues are:
> > > > >
> > > > > a) two selftest failures:
> > > > >
> > > > >   oe-selftest -r 
> > > > > devtool.DevtoolUpgradeTests.test_devtool_virtual_kernel_modify
> > > > >   oe-selftest -r efibootpartition.GenericEFITest.test_boot_efi
> > > > >
> > > > > b) meta-arm issues
> > > > >
> > > > > c) meta-virt issue (which you have a patch pending for in -next)
> > > > >
> > > >
> > > > Unfortunately, I have to add
> > > >
> > > > d) perf reproducibility issues:
> > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/2294/steps/13/logs/stdio
> > >
> > > Ahrrg.
> > >
> > > http://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20230126-poma_o8v/packages/diff-html/
> > >
> > >
> > > /lib/modules/6.1.5-yocto-standard/build/include/generated/compile.h
> > >
> > > from
> > >
> > > #define·LINUX_COMPILE_HOST»  "alma8-ty-2.yocto.io
> > >
> > > to
> > >
> > > #define·LINUX_COMPILE_HOST»  "ubuntu2004-ty-1"
> > >
> > > Bruce: Any idea if we can set that to some specific value?
> > >
> > > We probably should start by fixing that and then see if that improves
> > > things...
> >
> > Interesting. In my local builds:
> >
> > #define LINUX_COMPILE_HOST  "oe-host"
> >
> > I'm building 6.1.7, but that shouldn't be the difference.
> >
> > The value comes from: classes-recipe/kernel.bbclass:export
> > KBUILD_BUILD_HOST ?= "oe-host",
> > and has been that way for a while.
> >
> > I'm also grepping for other BUILDPATHS references, but the QA test
> > should have caught
> > those if that was the issue.
>
>
> I just realised that there are two issues, one is perf, the other is
> kernel-devsrc. The compile.h issue is in kernel-devsrc and that did
> reproduce for my locally just now. I'm not sure what is wrong with
> perf...
>
> Cheers,
>
> Richard
>
>
>
>
> 
>

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



[OE-core] [PATCH 1/2] valgrind: Include missing

2023-01-26 Thread Khem Raj
Signed-off-by: Khem Raj 
---
 ...01-drd-tests-Include-missing-cstdint.patch | 34 +++
 .../valgrind/valgrind_3.20.0.bb   |  1 +
 2 files changed, 35 insertions(+)
 create mode 100644 
meta/recipes-devtools/valgrind/valgrind/0001-drd-tests-Include-missing-cstdint.patch

diff --git 
a/meta/recipes-devtools/valgrind/valgrind/0001-drd-tests-Include-missing-cstdint.patch
 
b/meta/recipes-devtools/valgrind/valgrind/0001-drd-tests-Include-missing-cstdint.patch
new file mode 100644
index 00..fbee24a538
--- /dev/null
+++ 
b/meta/recipes-devtools/valgrind/valgrind/0001-drd-tests-Include-missing-cstdint.patch
@@ -0,0 +1,34 @@
+From 687d9fb9e3de832379680e9d5268331011c92afa Mon Sep 17 00:00:00 2001
+From: Khem Raj 
+Date: Thu, 26 Jan 2023 08:53:26 -0800
+Subject: [PATCH] drd/tests: Include missing 
+
+gcc 13 moved some includes around and as a result  is no longer
+transitively included [1]. Explicitly include it for uint{32,64}_t.
+
+Fixes
+tsan_thread_wrappers_pthread.h:91:9: error: 'int64_t' does not name a type
+
+[1] https://gcc.gnu.org/gcc-13/porting_to.html#header-dep-changes
+
+Upstream-Status: Submitted [https://bugs.kde.org/show_bug.cgi?id=464859]
+Signed-off-by: Khem Raj 
+---
+ drd/tests/tsan_thread_wrappers_pthread.h | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/drd/tests/tsan_thread_wrappers_pthread.h 
b/drd/tests/tsan_thread_wrappers_pthread.h
+index f15e6ad..4cc8062 100644
+--- a/drd/tests/tsan_thread_wrappers_pthread.h
 b/drd/tests/tsan_thread_wrappers_pthread.h
+@@ -55,6 +55,7 @@
+ #define NO_TLS
+ #endif
+ 
++#include 
+ #include 
+ using namespace std;
+ 
+-- 
+2.39.1
+
diff --git a/meta/recipes-devtools/valgrind/valgrind_3.20.0.bb 
b/meta/recipes-devtools/valgrind/valgrind_3.20.0.bb
index 1e1f0ccdd3..701dbf3833 100644
--- a/meta/recipes-devtools/valgrind/valgrind_3.20.0.bb
+++ b/meta/recipes-devtools/valgrind/valgrind_3.20.0.bb
@@ -39,6 +39,7 @@ SRC_URI = 
"https://sourceware.org/pub/valgrind/valgrind-${PV}.tar.bz2 \

file://0001-none-tests-fdleak_cmsg.stderr.exp-adjust-tmp-paths.patch \
file://0001-memcheck-tests-Fix-timerfd-syscall-test.patch \
file://0001-docs-Disable-manual-validation.patch \
+   file://0001-drd-tests-Include-missing-cstdint.patch \
"
 SRC_URI[sha256sum] = 
"8536c031dbe078d342f121fa881a9ecd205cb5a78e639005ad570011bdb9f3c6"
 UPSTREAM_CHECK_REGEX = "valgrind-(?P\d+(\.\d+)+)\.tar"
-- 
2.39.1


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



[OE-core] [PATCH 1/3] systemd: Add another fix for using XSI strerror_r

2023-01-24 Thread Khem Raj
This makes systemd continue to work on musl

Signed-off-by: Khem Raj 
---
 ...util-Make-STRERROR-portable-for-musl.patch | 42 +++
 meta/recipes-core/systemd/systemd_252.4.bb|  1 +
 2 files changed, 43 insertions(+)
 create mode 100644 
meta/recipes-core/systemd/systemd/0001-errno-util-Make-STRERROR-portable-for-musl.patch

diff --git 
a/meta/recipes-core/systemd/systemd/0001-errno-util-Make-STRERROR-portable-for-musl.patch
 
b/meta/recipes-core/systemd/systemd/0001-errno-util-Make-STRERROR-portable-for-musl.patch
new file mode 100644
index 00..2fb8985ad1
--- /dev/null
+++ 
b/meta/recipes-core/systemd/systemd/0001-errno-util-Make-STRERROR-portable-for-musl.patch
@@ -0,0 +1,42 @@
+From f66b5c802ce0a3310f5580cfc1b02446f8087568 Mon Sep 17 00:00:00 2001
+From: Khem Raj 
+Date: Mon, 23 Jan 2023 23:39:46 -0800
+Subject: [PATCH] errno-util: Make STRERROR portable for musl
+
+Sadly, systemd has decided to use yet another GNU extention in a macro
+lets make this such that we can use XSI compliant strerror_r() for
+non-glibc hosts
+
+Upstream-Status: Inappropriate [musl specific]
+
+Signed-off-by: Khem Raj 
+---
+ src/basic/errno-util.h | 12 ++--
+ 1 file changed, 10 insertions(+), 2 deletions(-)
+
+diff --git a/src/basic/errno-util.h b/src/basic/errno-util.h
+index 091f99c590..eb5c1f9961 100644
+--- a/src/basic/errno-util.h
 b/src/basic/errno-util.h
+@@ -14,8 +14,16 @@
+  * 
https://stackoverflow.com/questions/34880638/compound-literal-lifetime-and-if-blocks
+  *
+  * Note that we use the GNU variant of strerror_r() here. */
+-#define STRERROR(errnum) strerror_r(abs(errnum), (char[ERRNO_BUF_LEN]){}, 
ERRNO_BUF_LEN)
+-
++static inline const char * STRERROR(int errnum);
++
++static inline const char * STRERROR(int errnum) {
++#ifdef __GLIBC__
++return strerror_r(abs(errnum), (char[ERRNO_BUF_LEN]){}, 
ERRNO_BUF_LEN);
++#else
++static __thread char buf[ERRNO_BUF_LEN];
++return strerror_r(abs(errnum), buf, ERRNO_BUF_LEN) ? "unknown error" 
: buf;
++#endif
++}
+ /* A helper to print an error message or message for functions that return 0 
on EOF.
+  * Note that we can't use ({ … }) to define a temporary variable, so errnum is
+  * evaluated twice. */
+-- 
+2.39.1
+
diff --git a/meta/recipes-core/systemd/systemd_252.4.bb 
b/meta/recipes-core/systemd/systemd_252.4.bb
index d291a2a9a1..e6c873f53b 100644
--- a/meta/recipes-core/systemd/systemd_252.4.bb
+++ b/meta/recipes-core/systemd/systemd_252.4.bb
@@ -50,6 +50,7 @@ SRC_URI_MUSL = "\
file://0002-Add-sys-stat.h-for-S_IFDIR.patch \
file://0001-Adjust-for-musl-headers.patch \

file://0001-test-bus-error-strerror-is-assumed-to-be-GNU-specifi.patch \
+   file://0001-errno-util-Make-STRERROR-portable-for-musl.patch \
"
 
 PAM_PLUGINS = " \
-- 
2.39.1


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



[OE-core] [PATCH 2/3] texinfo: Add missing rdep on needed perl-modules

2023-01-24 Thread Khem Raj
Fixes
Can't locate Encode.pm in @INC (you may need to install the Encode module) 
(@INC contains: /usr/lib/perl5/site_perl/5.36.0/x86_64-linux 
/usr/lib/perl5/site_perl/5.36.0 /usr/lib/perl5/vendor_perl/5.36.0/x86_64-linux
 /usr/lib/perl5/vendor_perl/5.36.0 /usr/lib/perl5/5.36.0/x86_64-linux 
/usr/lib/perl5/5.36.0) at /usr/bin/makeinfo line 29.

The slew of indirect dependencies

Signed-off-by: Khem Raj 
---
 meta/recipes-extended/texinfo/texinfo_7.0.1.bb | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-extended/texinfo/texinfo_7.0.1.bb 
b/meta/recipes-extended/texinfo/texinfo_7.0.1.bb
index f0f9211594..4c8608b745 100644
--- a/meta/recipes-extended/texinfo/texinfo_7.0.1.bb
+++ b/meta/recipes-extended/texinfo/texinfo_7.0.1.bb
@@ -76,7 +76,9 @@ FILES:info-doc = "${infodir}/info.info* ${infodir}/dir 
${infodir}/info-*.info* \
   ${mandir}/man1/infokey.1* ${mandir}/man1/install-info.1*"
 
 FILES:${PN} = "${bindir}/makeinfo ${bindir}/texi* ${bindir}/pdftexi2dvi 
${bindir}/pod2texi ${datadir}/texinfo"
-RDEPENDS:${PN} = "perl"
+RDEPENDS:${PN} = "perl perl-module-encode perl-module-encode-encoding 
perl-module-locale perl-module-integer \
+  perl-module-if perl-module-unicode-normalize 
perl-module-base perl-module-feature \
+  perl-module-perlio"
 FILES:${PN}-doc = "${infodir}/texi* \
${datadir}/${tex_texinfo} \
${mandir}/man1 ${mandir}/man5"
-- 
2.39.1


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



[OE-core] [PATCH 3/3] elfutils: Remove funcretval test from run-native-test.sh for now

2023-01-24 Thread Khem Raj
Signed-off-by: Khem Raj 
---
 meta/recipes-devtools/elfutils/elfutils_0.188.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-devtools/elfutils/elfutils_0.188.bb 
b/meta/recipes-devtools/elfutils/elfutils_0.188.bb
index 65cae868c7..182229becf 100644
--- a/meta/recipes-devtools/elfutils/elfutils_0.188.bb
+++ b/meta/recipes-devtools/elfutils/elfutils_0.188.bb
@@ -98,6 +98,8 @@ do_install_ptest() {
cp -r ${B}/debuginfod   ${D}${PTEST_PATH}
sed -i '/^Makefile:/c Makefile:'
${D}${PTEST_PATH}/tests/Makefile
find ${D}${PTEST_PATH} -type f -name *.[hoc] | xargs -i rm {}
+   # TODO: remove below filter after 
https://sourceware.org/bugzilla/show_bug.cgi?id=30047 is fixed
+   sed -i -e '/funcretval/d' 
${D}${PTEST_PATH}/tests/run-native-test.sh
fi
 }
 
-- 
2.39.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#176340): 
https://lists.openembedded.org/g/openembedded-core/message/176340
Mute This Topic: https://lists.openembedded.org/mt/96514820/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 1/3] binutils: Upgrade to 2.40 release

2023-01-24 Thread Khem Raj
On Tue, Jan 24, 2023 at 12:58 AM Alexandre Belloni
 wrote:
>
> Hello,
>
> I guess this is the cause of this ptest failure:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/4587/steps/12/logs/stdio
>
> AssertionError: Failed ptests:
> {'elfutils': ['run-native-test.sh']}
>
>
> /usr/lib/elfutils/ptest/tests/funcretval: dwfl_module_return_value_location: 
> cannot handle DWARF type description
> FAIL: run-native-test.sh

I have looked into this a bit and it looks like a problem in
elfutils/libdw not being able to handle  DW_TAG_unspecified_type DIE
which is newly generated by assembler from binutils 2.40 release.
These DIEs are present in objects made out of assembly files
in glibc which are used during linking. So they also get into binaries
but libdw from elfutils is not able to handle them and thats why
we get this test failure. I have filed a bug for upstream elfutils [1]

We can wait for this to be resolved or exclude this test case for now
from ptests and move ahead. I am fine either way.

[1] https://sourceware.org/bugzilla/show_bug.cgi?id=30047

>
>
> On 20/01/2023 10:11:12-0800, Khem Raj wrote:
> > On Fri, Jan 20, 2023 at 3:47 AM Luca Ceresoli  
> > wrote:
> > >
> > > Hi Khem,
> > >
> > > On Thu, 19 Jan 2023 15:51:39 -0800
> > > "Khem Raj"  wrote:
> > >
> > > > Signed-off-by: Khem Raj 
> > >
> > > I'm afraid this time the patch does _really_ not apply, and the simple
> > > sorcery I did for v1 and v2 is not working anymore. If you could
> > > recreate the patches based on a clean oe-core master branch that would
> > > be good.
> >
> > I have pushed the related patchset to a branch on poky-contrib here
> >
> > https://git.yoctoproject.org/poky-contrib/log/?h=kraj/binutils-2.40
> >
> > Let me know how it goes.
> >
> > >
> > > Thank you!
> > >
> > > --
> > > Luca Ceresoli, Bootlin
> > > Embedded Linux and Kernel engineering
> > > https://bootlin.com
>
> >
> > 
> >
>
>
> --
> 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 (#176335): 
https://lists.openembedded.org/g/openembedded-core/message/176335
Mute This Topic: https://lists.openembedded.org/mt/96390083/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] ruby: Update the patch status

2023-01-24 Thread Khem Raj
It has been submitted to github as requested by ruby ml

Signed-off-by: Khem Raj 
---
 ...1-fiddle-Use-C11-_Alignof-to-define-ALIGN_OF-when-poss.patch | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/meta/recipes-devtools/ruby/ruby/0001-fiddle-Use-C11-_Alignof-to-define-ALIGN_OF-when-poss.patch
 
b/meta/recipes-devtools/ruby/ruby/0001-fiddle-Use-C11-_Alignof-to-define-ALIGN_OF-when-poss.patch
index 30caf2c2de..1dff9c0f8c 100644
--- 
a/meta/recipes-devtools/ruby/ruby/0001-fiddle-Use-C11-_Alignof-to-define-ALIGN_OF-when-poss.patch
+++ 
b/meta/recipes-devtools/ruby/ruby/0001-fiddle-Use-C11-_Alignof-to-define-ALIGN_OF-when-poss.patch
@@ -18,7 +18,7 @@ may support C11, exclude those compiler versions
 [1] https://www.open-std.org/jtc1/sc22/wg14/www/docs/n2350.htm
 [2] https://reviews.llvm.org/D133574
 
-Upstream-Status: Submitted 
[https://ml.ruby-lang.org/mailman3/hyperkitty/list/ruby-c...@ml.ruby-lang.org/thread/DLES4EPPXSPCHQMWJPPWMWXXS42AVPFA/]
+Upstream-Status: Submitted [https://github.com/ruby/fiddle/pull/120]
 Signed-off-by: Khem Raj 
 ---
  ext/fiddle/fiddle.h | 12 +++-
-- 
2.39.1


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



[OE-core] [PATCH 3/3] vulkan-samples: Include missing header cstdint for uint32_t

2023-01-23 Thread Khem Raj
Signed-off-by: Khem Raj 
---
 ...1-parser.h-Including-missing-cstdint.patch | 37 +++
 .../vulkan/vulkan-samples_git.bb  |  1 +
 2 files changed, 38 insertions(+)
 create mode 100644 
meta/recipes-graphics/vulkan/vulkan-samples/0001-parser.h-Including-missing-cstdint.patch

diff --git 
a/meta/recipes-graphics/vulkan/vulkan-samples/0001-parser.h-Including-missing-cstdint.patch
 
b/meta/recipes-graphics/vulkan/vulkan-samples/0001-parser.h-Including-missing-cstdint.patch
new file mode 100644
index 00..3f6b37dce1
--- /dev/null
+++ 
b/meta/recipes-graphics/vulkan/vulkan-samples/0001-parser.h-Including-missing-cstdint.patch
@@ -0,0 +1,37 @@
+From 590bd5f81207bb55bd02b4a37f73a1f64dac452d Mon Sep 17 00:00:00 2001
+From: Khem Raj 
+Date: Mon, 23 Jan 2023 13:20:58 -0800
+Subject: [PATCH] parser.h: Including missing 
+
+This is needed from gcc-13+ see [1]
+
+Fixes
+
+../git/framework/platform/parser.h:282:43: error: 'uint32_t' does not name a 
type
+  282 | *type   = static_cast(number);
+  |   ^~~~
+../git/framework/platform/parser.h:21:1: note: 'uint32_t' is defined in header 
''; did you forget to '#include '?
+
+[1] https://www.gnu.org/software/gcc/gcc-13/porting_to.html
+
+Upstream-Status: Submitted 
[https://github.com/KhronosGroup/Vulkan-Samples/pull/602]
+Signed-off-by: Khem Raj 
+---
+ framework/platform/parser.h | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/framework/platform/parser.h b/framework/platform/parser.h
+index 215f3d80..a5bd1344 100644
+--- a/framework/platform/parser.h
 b/framework/platform/parser.h
+@@ -18,6 +18,7 @@
+ #pragma once
+ 
+ #include 
++#include 
+ #include 
+ #include 
+ #include 
+-- 
+2.39.1
+
diff --git a/meta/recipes-graphics/vulkan/vulkan-samples_git.bb 
b/meta/recipes-graphics/vulkan/vulkan-samples_git.bb
index 7f52cb66c9..c0ce393201 100644
--- a/meta/recipes-graphics/vulkan/vulkan-samples_git.bb
+++ b/meta/recipes-graphics/vulkan/vulkan-samples_git.bb
@@ -9,6 +9,7 @@ SRC_URI = 
"gitsm://github.com/KhronosGroup/Vulkan-Samples.git;branch=master;prot
file://debugfix.patch \

file://0001-Do-not-use-LFS64-functions-on-linux-musl.patch;patchdir=third_party/spdlog
 \

file://0001-Deprecate-u8string_view.patch;patchdir=third_party/spdlog \
+   file://0001-parser.h-Including-missing-cstdint.patch \
"
 
 UPSTREAM_CHECK_COMMITS = "1"
-- 
2.39.1


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



[OE-core] [PATCH 1/3] harfbuzz: Add missing and includes

2023-01-23 Thread Khem Raj
Signed-off-by: Khem Raj 
---
 ...subset-threads.cc-add-missing-cstdio.patch | 34 +++
 .../harfbuzz/harfbuzz_6.0.0.bb|  3 +-
 2 files changed, 36 insertions(+), 1 deletion(-)
 create mode 100644 
meta/recipes-graphics/harfbuzz/harfbuzz/0001-test-threads-hb-subset-threads.cc-add-missing-cstdio.patch

diff --git 
a/meta/recipes-graphics/harfbuzz/harfbuzz/0001-test-threads-hb-subset-threads.cc-add-missing-cstdio.patch
 
b/meta/recipes-graphics/harfbuzz/harfbuzz/0001-test-threads-hb-subset-threads.cc-add-missing-cstdio.patch
new file mode 100644
index 00..13819f5cf8
--- /dev/null
+++ 
b/meta/recipes-graphics/harfbuzz/harfbuzz/0001-test-threads-hb-subset-threads.cc-add-missing-cstdio.patch
@@ -0,0 +1,34 @@
+From 7dfa672dac958bdbc7703ab0920e167eaa126754 Mon Sep 17 00:00:00 2001
+From: Sergei Trofimovich 
+Date: Mon, 16 Jan 2023 19:49:53 +
+Subject: [PATCH] test/threads/hb-subset-threads.cc: add missing  
include
+
+This week's `gcc-13` snapshot cleaned further up it's standard headers
+and exposed missing declaration as a build failure:
+
+../test/threads/hb-subset-threads.cc: In function 'void 
test_operation(operation_t, const char*, const test_input_t&)':
+../test/threads/hb-subset-threads.cc:127:3: error: 'printf' was not 
declared in this scope
+
+../test/threads/hb-subset-threads.cc: In function 'int main(int, char**)':
+../test/threads/hb-subset-threads.cc:157:19: error: 'atoi' was not 
declared in this scope
+
+Upstream-Status: Backport 
[https://github.com/harfbuzz/harfbuzz/commit/7dfa672dac958bdbc7703ab0920e167eaa126754]
+Signed-off-by: Khem Raj 
+---
+ test/threads/hb-subset-threads.cc | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/test/threads/hb-subset-threads.cc 
b/test/threads/hb-subset-threads.cc
+index 9d86d8d51..f0e4b7e2a 100644
+--- a/test/threads/hb-subset-threads.cc
 b/test/threads/hb-subset-threads.cc
+@@ -1,4 +1,6 @@
+ #include 
++#include 
++#include 
+ #include 
+ #include 
+ #include 
+-- 
+2.39.1
+
diff --git a/meta/recipes-graphics/harfbuzz/harfbuzz_6.0.0.bb 
b/meta/recipes-graphics/harfbuzz/harfbuzz_6.0.0.bb
index ae54bad643..1fce127d07 100644
--- a/meta/recipes-graphics/harfbuzz/harfbuzz_6.0.0.bb
+++ b/meta/recipes-graphics/harfbuzz/harfbuzz_6.0.0.bb
@@ -8,7 +8,8 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=6ee0f16281694fb6aa689cca1e0fb3da \
 
file://src/hb-ucd.cc;beginline=1;endline=15;md5=29d4dcb6410429195df67efe3382d8bc
 \
 "
 
-SRC_URI = "${GITHUB_BASE_URI}/download/${PV}/${BPN}-${PV}.tar.xz"
+SRC_URI = "${GITHUB_BASE_URI}/download/${PV}/${BPN}-${PV}.tar.xz \
+   
file://0001-test-threads-hb-subset-threads.cc-add-missing-cstdio.patch"
 SRC_URI[sha256sum] = 
"1d1010a1751d076d5291e433c138502a794d679a7498d1268ee21e2d4a140eb4"
 
 inherit meson pkgconfig lib_package gtk-doc gobject-introspection 
github-releases
-- 
2.39.1


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



[OE-core] [PATCH 2/3] apt: add missing for uint16_t

2023-01-23 Thread Khem Raj
Signed-off-by: Khem Raj 
---
 ...001-add-missing-cstdint-for-uint16_t.patch | 35 +++
 meta/recipes-devtools/apt/apt_2.4.5.bb|  1 +
 2 files changed, 36 insertions(+)
 create mode 100644 
meta/recipes-devtools/apt/apt/0001-add-missing-cstdint-for-uint16_t.patch

diff --git 
a/meta/recipes-devtools/apt/apt/0001-add-missing-cstdint-for-uint16_t.patch 
b/meta/recipes-devtools/apt/apt/0001-add-missing-cstdint-for-uint16_t.patch
new file mode 100644
index 00..44aa8a5873
--- /dev/null
+++ b/meta/recipes-devtools/apt/apt/0001-add-missing-cstdint-for-uint16_t.patch
@@ -0,0 +1,35 @@
+From 960d10e89cf60d39998dae6fdcd4f0866b753a79 Mon Sep 17 00:00:00 2001
+From: Khem Raj 
+Date: Mon, 23 Jan 2023 12:31:35 -0800
+Subject: [PATCH] add missing  for uint16_t
+
+This fixes build problems with gcc 13 snapshot [1]
+
+Fixes
+| include/apt-pkg/pkgcache.h:257:23: warning: cast from 'char*' to 'const 
uint16_t*' {aka 'const short unsigned int*'} increases required alignment of 
target type [-Wcast-align]
+|   257 |   uint16_t len = *reinterpret_cast(name - 
sizeof(uint16_t));
+|   |   
^~
+
+[1] https://www.gnu.org/software/gcc/gcc-13/porting_to.html
+
+Upstream-Status: Submitted 
[https://salsa.debian.org/apt-team/apt/-/merge_requests/276]
+Signed-off-by: Khem Raj 
+---
+ apt-pkg/contrib/mmap.cc | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/apt-pkg/contrib/mmap.cc b/apt-pkg/contrib/mmap.cc
+index 642e20473..0568e1cd0 100644
+--- a/apt-pkg/contrib/mmap.cc
 b/apt-pkg/contrib/mmap.cc
+@@ -23,6 +23,7 @@
+ #include 
+ #include 
+ 
++#include 
+ #include 
+ #include 
+ #include 
+-- 
+2.39.1
+
diff --git a/meta/recipes-devtools/apt/apt_2.4.5.bb 
b/meta/recipes-devtools/apt/apt_2.4.5.bb
index 4b9f804039..4ecbf98554 100644
--- a/meta/recipes-devtools/apt/apt_2.4.5.bb
+++ b/meta/recipes-devtools/apt/apt_2.4.5.bb
@@ -16,6 +16,7 @@ SRC_URI = "${DEBIAN_MIRROR}/main/a/apt/${BPN}_${PV}.tar.xz \
file://0001-Remove-using-std-binary_function.patch \
file://0001-typecast-time_t-and-suseconds_t-from-std-chrono.patch \
file://0002-interactive-helper-Undefine-_FORTIFY_SOURCE.patch \
+   file://0001-add-missing-cstdint-for-uint16_t.patch \
"
 
 SRC_URI:append:class-native = " \
-- 
2.39.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#176322): 
https://lists.openembedded.org/g/openembedded-core/message/176322
Mute This Topic: https://lists.openembedded.org/mt/96490026/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 1/3] binutils: Upgrade to 2.40 release

2023-01-23 Thread Khem Raj
On Thu, Jan 19, 2023 at 9:25 AM Jeff Law  wrote:
>
>
>
> On 1/18/23 21:27, Khem Raj wrote:
> > Signed-off-by: Khem Raj 
> > ---
> > v1 -> v2:
> > - Fix build on mingw
> > - Backport fix to build with --disable-gdb
> [ ... ]
> Note I think this is going to run afoul of grub2 mkimage.
>
> In binutils-2.40 the assembler for risc-v was changed to use CALL_PLT
> relocations rather than CALL relocations.  grub2 does not handle
> CALL_PLT relocations which in turn will cause a failure when
> grub2-mkimage is used on risc-v.
>
> As far as I can tell, the assembler change literally just changes the
> relocation number, they are otherwise treated the same.  So I think
> grub2 can be fixed by just treating R_RISCV_CALL_PLT just like
> R_RISCV_CALL in kern/riscv/dl.c.
>
> Nelson, can you confirm that all your assembler change did was change
> the relocation used in the resultant object?

The binutils change is here
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=70f35d72ef04cd23771875c1661c9975044a749c

I tried something like this

http://sprunge.us/ZjpFCI

I still get
| grub-mkimage: error: relocation 0x13 is not implemented yet.

need to look more.

>
> Jeff

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#176318): 
https://lists.openembedded.org/g/openembedded-core/message/176318
Mute This Topic: https://lists.openembedded.org/mt/96371613/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] stress-ng: Robustify test-float test

2023-01-23 Thread Khem Raj
Latest compilers are able to figure out that whole code can be optmized
away when CFLAGS has -O2 or more agressive optimizations. In order to
ensure the test is doing the right thing, make the variables global so
compiler is not able to optimize it away.

This fixes build on x86 especially when using clang compiler

Signed-off-by: Khem Raj 
---
 ...001-test-float-Make-variables-global.patch | 34 +++
 .../stress-ng/stress-ng_0.15.02.bb|  1 +
 2 files changed, 35 insertions(+)
 create mode 100644 
meta/recipes-extended/stress-ng/stress-ng/0001-test-float-Make-variables-global.patch

diff --git 
a/meta/recipes-extended/stress-ng/stress-ng/0001-test-float-Make-variables-global.patch
 
b/meta/recipes-extended/stress-ng/stress-ng/0001-test-float-Make-variables-global.patch
new file mode 100644
index 00..2e598ca4f4
--- /dev/null
+++ 
b/meta/recipes-extended/stress-ng/stress-ng/0001-test-float-Make-variables-global.patch
@@ -0,0 +1,34 @@
+From 958a86069c8d0149969b5c32212a28009c4a9ded Mon Sep 17 00:00:00 2001
+From: Khem Raj 
+Date: Sat, 21 Jan 2023 23:18:18 -0800
+Subject: [PATCH] test-float: Make variables global
+
+Latest clang ( clang 16+ ) is able to optimize everything out when -O2 is used 
and as
+a result build succeeds and test output comes out to be wrong. Therefore
+make the variables global, so clang does not optimize away the functions
+
+Upstream-Status: Backport 
[https://github.com/ColinIanKing/stress-ng/commit/e299eb60a3a029e975304cc43045aea6ab1fad70]
+Signed-off-by: Khem Raj 
+---
+ test/test-float.c | 3 +--
+ 1 file changed, 1 insertion(+), 2 deletions(-)
+
+diff --git a/test/test-float.c b/test/test-float.c
+index d2800cd3..ad5503c3 100644
+--- a/test/test-float.c
 b/test/test-float.c
+@@ -61,10 +61,9 @@
+ /* Avoid implicit int in the definition of test even if FLOAT is not known. */
+ typedef FLOAT float_type;
+ 
++FLOAT a = 0.0, b = 0.0, c = 0.0, d = 0.0;
+ static float_type HOT OPTIMIZE3 test(void)
+ {
+-  FLOAT a = 0.0, b = 0.0, c = 0.0, d = 0.0;
+-
+   float_ops(FLOAT, a, b, c, d, sin, cos);
+   float_ops(FLOAT, a, b, c, d, sinl, cosl);
+ 
+-- 
+2.39.1
+
diff --git a/meta/recipes-extended/stress-ng/stress-ng_0.15.02.bb 
b/meta/recipes-extended/stress-ng/stress-ng_0.15.02.bb
index c554bb403e..75400f589e 100644
--- a/meta/recipes-extended/stress-ng/stress-ng_0.15.02.bb
+++ b/meta/recipes-extended/stress-ng/stress-ng_0.15.02.bb
@@ -6,6 +6,7 @@ LICENSE = "GPL-2.0-only"
 LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
 
 SRC_URI = 
"git://github.com/ColinIanKing/stress-ng.git;protocol=https;branch=master \
+   file://0001-test-float-Make-variables-global.patch \
file://0001-Pass-LD_GOLD-1-via-makefile-to-enable-gold-linker.patch"
 SRCREV = "4164f6842c712c2d9a13619c3c70fd35d8d02cdb"
 S = "${WORKDIR}/git"
-- 
2.39.1


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



[OE-core] [PATCH 1/2] libusb1: Link with latomic only if compiler has no atomic builtins

2023-01-20 Thread Khem Raj
This makes build use compiler to decide from where to get atomics
instead of assuming that it should always come from libatomic, helps
sharing build artifacts with OSes which may not have libatomic installed
because it is not required on those hosts.

Signed-off-by: Khem Raj 
---
 ...k-with-latomic-only-if-no-atomic-bui.patch | 46 +++
 meta/recipes-support/libusb/libusb1_1.0.26.bb |  1 +
 2 files changed, 47 insertions(+)
 create mode 100644 
meta/recipes-support/libusb/libusb1/0001-configure.ac-Link-with-latomic-only-if-no-atomic-bui.patch

diff --git 
a/meta/recipes-support/libusb/libusb1/0001-configure.ac-Link-with-latomic-only-if-no-atomic-bui.patch
 
b/meta/recipes-support/libusb/libusb1/0001-configure.ac-Link-with-latomic-only-if-no-atomic-bui.patch
new file mode 100644
index 00..3c223e0822
--- /dev/null
+++ 
b/meta/recipes-support/libusb/libusb1/0001-configure.ac-Link-with-latomic-only-if-no-atomic-bui.patch
@@ -0,0 +1,46 @@
+From 95e601ce116dd46ea7915c171976b85ea0905d58 Mon Sep 17 00:00:00 2001
+From: Lonnie Abelbeck 
+Date: Sun, 8 May 2022 14:05:56 -0500
+Subject: [PATCH] configure.ac: Link with -latomic only if no atomic builtins
+
+Follow-up to 561dbda, a check of GCC atomic builtins needs to be done
+first.
+
+I'm no autoconf guru, but using this:
+https://github.com/mesa3d/mesa/blob/0df485c285b73c34ba9062f0c27e55c3c702930d/configure.ac#L469
+as inspiration, I created a pre-check before calling AC_SEARCH_LIBS(...)
+
+Fixes #1135
+Closes #1139
+Upstream-Status: Backport 
[https://github.com/kraj/libusb/commit/95e601ce116dd46ea7915c171976b85ea0905d58]
+Signed-off-by: Khem Raj 
+---
+ configure.ac  | 16 +++-
+ libusb/version_nano.h |  2 +-
+ 2 files changed, 16 insertions(+), 2 deletions(-)
+
+--- a/configure.ac
 b/configure.ac
+@@ -153,7 +153,21 @@ if test "x$platform" = xposix; then
+   AC_SEARCH_LIBS([pthread_create], [pthread],
+   [test "x$ac_cv_search_pthread_create" != "xnone required" && 
AC_SUBST(THREAD_LIBS, [-lpthread])],
+   [], [])
+-  AC_SEARCH_LIBS([__atomic_fetch_add_4], [atomic])
++  dnl Check for new-style atomic builtins. We first check without linking 
to -latomic.
++  AC_MSG_CHECKING(whether __atomic_load_n is supported)
++  AC_LINK_IFELSE([AC_LANG_SOURCE([[
++  #include 
++  int main() {
++  struct {
++  uint64_t *v;
++  } x;
++  return (int)__atomic_load_n(x.v, __ATOMIC_ACQUIRE) &
++ (int)__atomic_add_fetch(x.v, (uint64_t)1, 
__ATOMIC_ACQ_REL);
++  }]])], GCC_ATOMIC_BUILTINS_SUPPORTED=yes, 
GCC_ATOMIC_BUILTINS_SUPPORTED=no)
++  AC_MSG_RESULT($GCC_ATOMIC_BUILTINS_SUPPORTED)
++  if test "x$GCC_ATOMIC_BUILTINS_SUPPORTED" != xyes; then
++  AC_SEARCH_LIBS([__atomic_fetch_add_4], [atomic])
++  fi
+ elif test "x$platform" = xwindows; then
+   AC_DEFINE([PLATFORM_WINDOWS], [1], [Define to 1 if compiling for a 
Windows platform.])
+ else
diff --git a/meta/recipes-support/libusb/libusb1_1.0.26.bb 
b/meta/recipes-support/libusb/libusb1_1.0.26.bb
index 7371faf017..301e60c14f 100644
--- a/meta/recipes-support/libusb/libusb1_1.0.26.bb
+++ b/meta/recipes-support/libusb/libusb1_1.0.26.bb
@@ -11,6 +11,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=fbc093901857fcd118f065f900982c24"
 BBCLASSEXTEND = "native nativesdk"
 
 SRC_URI = "${GITHUB_BASE_URI}/download/v${PV}/libusb-${PV}.tar.bz2 \
+   
file://0001-configure.ac-Link-with-latomic-only-if-no-atomic-bui.patch \
file://run-ptest \
   "
 
-- 
2.39.1


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



[OE-core] [PATCH 2/2] libusb1: Strip trailing whitespaces

2023-01-20 Thread Khem Raj
Signed-off-by: Khem Raj 
---
 meta/recipes-support/libusb/libusb1_1.0.26.bb | 12 ++--
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/meta/recipes-support/libusb/libusb1_1.0.26.bb 
b/meta/recipes-support/libusb/libusb1_1.0.26.bb
index 301e60c14f..122c3d48b4 100644
--- a/meta/recipes-support/libusb/libusb1_1.0.26.bb
+++ b/meta/recipes-support/libusb/libusb1_1.0.26.bb
@@ -35,12 +35,12 @@ do_install:append() {
fi
 }
 
-do_compile_ptest() {   
  
-oe_runmake -C tests stress 
  
-}  
  
-   
  
-do_install_ptest() {   
  
-install -m 755 ${B}/tests/.libs/stress ${D}${PTEST_PATH} 
+do_compile_ptest() {
+oe_runmake -C tests stress
+}
+
+do_install_ptest() {
+install -m 755 ${B}/tests/.libs/stress ${D}${PTEST_PATH}
 }
 
 FILES:${PN} += "${base_libdir}/*.so.*"
-- 
2.39.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#176254): 
https://lists.openembedded.org/g/openembedded-core/message/176254
Mute This Topic: https://lists.openembedded.org/mt/96427836/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 1/3] binutils: Upgrade to 2.40 release

2023-01-20 Thread Khem Raj
On Fri, Jan 20, 2023 at 3:47 AM Luca Ceresoli  wrote:
>
> Hi Khem,
>
> On Thu, 19 Jan 2023 15:51:39 -0800
> "Khem Raj"  wrote:
>
> > Signed-off-by: Khem Raj 
>
> I'm afraid this time the patch does _really_ not apply, and the simple
> sorcery I did for v1 and v2 is not working anymore. If you could
> recreate the patches based on a clean oe-core master branch that would
> be good.

I have pushed the related patchset to a branch on poky-contrib here

https://git.yoctoproject.org/poky-contrib/log/?h=kraj/binutils-2.40

Let me know how it goes.

>
> Thank you!
>
> --
> Luca Ceresoli, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#176225): 
https://lists.openembedded.org/g/openembedded-core/message/176225
Mute This Topic: https://lists.openembedded.org/mt/96390083/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 1/3] binutils: Upgrade to 2.40 release

2023-01-19 Thread Khem Raj
On Thu, Jan 19, 2023 at 2:58 PM Luca Ceresoli  wrote:
>
> Hi Khem,
>
> On Thu, 19 Jan 2023 08:52:09 -0800
> "Khem Raj"  wrote:
>
> > On Thu, Jan 19, 2023 at 1:44 AM Luca Ceresoli  
> > wrote:
> > >
> > > Hi Khem,
> > >
> > > On Wed, 18 Jan 2023 20:27:22 -0800
> > > "Khem Raj"  wrote:
> > >
> > > > Signed-off-by: Khem Raj 
>
> This version is failing too:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/65/builds/6592/steps/14/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/122/builds/2263/steps/12/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/42/builds/6521/steps/14/logs/stdio
>

my bad. I have fixed the mingw32 patch and sent v3. Please try that
patchset out.

> ...
>
> > > > diff --git a/meta/conf/distro/include/tcmode-default.inc
> b/meta/conf/distro/include/tcmode-default.inc
> > > > index 4d4929529a..bcc5f7ce1f 100644
> > > > --- a/meta/conf/distro/include/tcmode-default.inc
> > > > +++ b/meta/conf/distro/include/tcmode-default.inc
> > > > @@ -18,7 +18,7 @@ PREFERRED_PROVIDER_virtual/gettext ??= "gettext"
> > > >
> > > >  GCCVERSION ?= "12.%"
> > > >  SDKGCCVERSION ?= "${GCCVERSION}"
> > > > -BINUVERSION ?= "2.39%"
> > > > +BINUVERSION ?= "2.40%"
> > > >  GDBVERSION ?= "12.%"
> > > >  GLIBCVERSION ?= "2.37"
> > > >  LINUXLIBCVERSION ?= "6.1%"
> > >
> > > Applying this patch on an oe-core repository fails with 'git am':
> > >
> > > error: sha1 information is lacking or useless 
> > > (meta/conf/distro/include/tcmode-default.inc).
> > > error: could not build fake ancestor
> > > Patch failed at 0001 binutils: Upgrade to 2.40 release
> > >
> > > And also with 'git apply'
> > >
> > > error: patch failed: meta/conf/distro/include/tcmode-default.inc:18
> > > error: meta/conf/distro/include/tcmode-default.inc: patch does not apply
> >
> > It might be due to glibc 2.37 upgrade which I have in my local tree
> > staged as well.
> > you might edit it locally. If you want I can push it to a dedicated branch
>
> Hm, maybe. I will try with your v3 I guess. :)
>
> Not a big problem so far, but an annoyance.
>
> --
> Luca Ceresoli, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#176176): 
https://lists.openembedded.org/g/openembedded-core/message/176176
Mute This Topic: https://lists.openembedded.org/mt/96371613/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 3/3] elfutils: Fix build with libcurl >= 7.87

2023-01-19 Thread Khem Raj
Signed-off-by: Khem Raj 
---
v2 -> v3:
- rebase

 .../elfutils/elfutils_0.188.bb|  4 +-
 ...od-Fix-usage-of-deprecated-CURLINFO_.patch | 49 +++
 ...t-Use-CURLOPT_PROTOCOLS_STR-for-libc.patch | 34 +
 3 files changed, 85 insertions(+), 2 deletions(-)
 create mode 100644 
meta/recipes-devtools/elfutils/files/0001-PR29926-debuginfod-Fix-usage-of-deprecated-CURLINFO_.patch
 create mode 100644 
meta/recipes-devtools/elfutils/files/0002-debuginfod-client-Use-CURLOPT_PROTOCOLS_STR-for-libc.patch

diff --git a/meta/recipes-devtools/elfutils/elfutils_0.188.bb 
b/meta/recipes-devtools/elfutils/elfutils_0.188.bb
index 084908a38c..65cae868c7 100644
--- a/meta/recipes-devtools/elfutils/elfutils_0.188.bb
+++ b/meta/recipes-devtools/elfutils/elfutils_0.188.bb
@@ -21,6 +21,8 @@ SRC_URI = 
"https://sourceware.org/elfutils/ftp/${PV}/${BP}.tar.bz2 \
file://0001-skip-the-test-when-gcc-not-deployed.patch \
file://ptest.patch \

file://0001-tests-Makefile.am-compile-test_nlist-with-standard-C.patch \
+   
file://0001-PR29926-debuginfod-Fix-usage-of-deprecated-CURLINFO_.patch \
+   
file://0002-debuginfod-client-Use-CURLOPT_PROTOCOLS_STR-for-libc.patch \
"
 SRC_URI:append:libc-musl = " \
file://0003-musl-utils.patch \
@@ -33,8 +35,6 @@ inherit autotools gettext ptest pkgconfig
 EXTRA_OECONF = "--program-prefix=eu-"
 
 BUILD_CFLAGS += "-Wno-error=stringop-overflow"
-# compatibility with curl 7.87; can be removed when elfutils upstream fixes 
the deprecation fails
-CFLAGS:append = " -Wno-error=deprecated-declarations"
 
 DEPENDS_BZIP2 = "bzip2-replacement-native"
 DEPENDS_BZIP2:class-target = "bzip2"
diff --git 
a/meta/recipes-devtools/elfutils/files/0001-PR29926-debuginfod-Fix-usage-of-deprecated-CURLINFO_.patch
 
b/meta/recipes-devtools/elfutils/files/0001-PR29926-debuginfod-Fix-usage-of-deprecated-CURLINFO_.patch
new file mode 100644
index 00..ee192e3581
--- /dev/null
+++ 
b/meta/recipes-devtools/elfutils/files/0001-PR29926-debuginfod-Fix-usage-of-deprecated-CURLINFO_.patch
@@ -0,0 +1,49 @@
+From d2bf497b12fbd49b4996ccf0744303ffd67735b1 Mon Sep 17 00:00:00 2001
+From: Andrew Paprocki 
+Date: Wed, 21 Dec 2022 11:15:00 -0500
+Subject: [PATCH] PR29926: debuginfod: Fix usage of deprecated CURLINFO_*
+
+The `CURLINFO_SIZE_DOWNLOAD_T` and `CURLINFO_CONTENT_LENGTH_DOWNLOAD_T`
+identifiers are `enum`s, not pre-processor definitions, so the current
+`#ifdef` logic is not selecting the newer API.  This results in the
+older identifiers being used and they now generate errors when compiled
+against Curl 7.87, which has silently deprecated them, causing GCC to
+emit `-Werror=deprecated-declarations`.
+
+Instead, the newer identifiers were added in Curl 7.55, so explicitly
+check for `CURL_AT_LEAST_VERSION(7, 55, 0)` instead of the current
+logic.  This eliminates the error when compiling against Curl 7.87.
+
+Ref: https://github.com/curl/curl/pull/1511
+
+Upstream-Status: Backport 
[https://sourceware.org/git/?p=elfutils.git;a=commit;h=d2bf497b12fbd49b4996ccf0744303ffd67735b1]
+Signed-off-by: Andrew Paprocki 
+---
+ debuginfod/debuginfod-client.c | 4 ++--
+ 2 files changed, 6 insertions(+), 2 deletions(-)
+
+diff --git a/debuginfod/debuginfod-client.c b/debuginfod/debuginfod-client.c
+index 8873fcc8..692aecce 100644
+--- a/debuginfod/debuginfod-client.c
 b/debuginfod/debuginfod-client.c
+@@ -1456,7 +1456,7 @@ debuginfod_query_server (debuginfod_client *c,
+  deflate-compressing proxies, this number is likely to be
+  unavailable, so -1 may show. */
+   CURLcode curl_res;
+-#ifdef CURLINFO_CONTENT_LENGTH_DOWNLOAD_T
++#if CURL_AT_LEAST_VERSION(7, 55, 0)
+   curl_off_t cl;
+   curl_res = curl_easy_getinfo(target_handle,
+CURLINFO_CONTENT_LENGTH_DOWNLOAD_T,
+@@ -1491,7 +1491,7 @@ debuginfod_query_server (debuginfod_client *c,
+   if (target_handle) /* we've committed to a server; report its 
download progress */
+ {
+   CURLcode curl_res;
+-#ifdef CURLINFO_SIZE_DOWNLOAD_T
++#if CURL_AT_LEAST_VERSION(7, 55, 0)
+   curl_off_t dl;
+   curl_res = curl_easy_getinfo(target_handle,
+CURLINFO_SIZE_DOWNLOAD_T,
+-- 
+2.39.1
+
diff --git 
a/meta/recipes-devtools/elfutils/files/0002-debuginfod-client-Use-CURLOPT_PROTOCOLS_STR-for-libc.patch
 
b/meta/recipes-devtools/elfutils/files/0002-debuginfod-client-Use-CURLOPT_PROTOCOLS_STR-for-libc.patch
new file mode 100644
index 00..2d4c912e82
--- /dev/null
+++ 
b/meta/recipes-devtools/elfutils/files/0002-debuginfod-client-Use-CURLOPT_PROTOCOLS_STR-for-libc.patch
@@ -0,0 +1,34 @@
+From 6560fb26a62ef135a804357ef4f15a47de3e49b3 Mon Sep 17 00:00:00 2001
+From: Mark Wielaard 
+Date: Tue, 10 Jan 2023 23:20:41 +0100
+Subje

[OE-core] [PATCH v3 2/3] binutils: Package libsframe

2023-01-19 Thread Khem Raj
libsframe is newly added in binutils 2.40

Signed-off-by: Khem Raj 
---
v1 -> v2:
- Rebase

v2 -> v3:
- Rebase

 meta/recipes-devtools/binutils/binutils_2.40.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/binutils/binutils_2.40.bb 
b/meta/recipes-devtools/binutils/binutils_2.40.bb
index 67240383f7..9087af87c5 100644
--- a/meta/recipes-devtools/binutils/binutils_2.40.bb
+++ b/meta/recipes-devtools/binutils/binutils_2.40.bb
@@ -66,7 +66,7 @@ PACKAGE_BEFORE_PN += "libbfd libopcodes gprofng"
 FILES:libbfd = "${libdir}/libbfd-*.so.* ${libdir}/libbfd-*.so"
 FILES:libopcodes = "${libdir}/libopcodes-*.so.* ${libdir}/libopcodes-*.so"
 FILES:gprofng = "${sysconfdir}/gprofng.rc ${libdir}/gprofng/libgp-*.so 
${libdir}/gprofng/libgprofng.so.* ${bindir}/gp-* ${bindir}/gprofng"
-FILES:${PN}-dev += "${libdir}/gprofng/libgprofng.so"
+FILES:${PN}-dev += "${libdir}/gprofng/libgprofng.so ${libdir}/libsframe.so"
 SRC_URI:append:class-nativesdk =  " 
file://0003-binutils-nativesdk-Search-for-alternative-ld.so.conf.patch "
 
 USE_ALTERNATIVES_FOR:class-nativesdk = ""
-- 
2.39.1


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



[OE-core] [PATCH 3/3] ruby: Use C11 _Alignof to define ALIGN_OF when possible

2023-01-19 Thread Khem Raj
Signed-off-by: Khem Raj 
---
 ...Alignof-to-define-ALIGN_OF-when-poss.patch | 52 +++
 meta/recipes-devtools/ruby/ruby_3.2.0.bb  |  1 +
 2 files changed, 53 insertions(+)
 create mode 100644 
meta/recipes-devtools/ruby/ruby/0001-fiddle-Use-C11-_Alignof-to-define-ALIGN_OF-when-poss.patch

diff --git 
a/meta/recipes-devtools/ruby/ruby/0001-fiddle-Use-C11-_Alignof-to-define-ALIGN_OF-when-poss.patch
 
b/meta/recipes-devtools/ruby/ruby/0001-fiddle-Use-C11-_Alignof-to-define-ALIGN_OF-when-poss.patch
new file mode 100644
index 00..30caf2c2de
--- /dev/null
+++ 
b/meta/recipes-devtools/ruby/ruby/0001-fiddle-Use-C11-_Alignof-to-define-ALIGN_OF-when-poss.patch
@@ -0,0 +1,52 @@
+From 6b3c202b46b9312c5bb0789145f13d8086e70948 Mon Sep 17 00:00:00 2001
+From: Khem Raj 
+Date: Sun, 15 Jan 2023 02:34:17 -0800
+Subject: [PATCH] fiddle: Use C11 _Alignof to define ALIGN_OF when possible
+
+WG14 N2350 made very clear that it is an UB having type definitions
+within "offsetof" [1]. This patch enhances the implementation of macro
+ALIGN_OF to use builtin "_Alignof" to avoid undefined behavior
+when using std=c11 or newer
+
+clang 16+ has started to flag this [2]
+
+Fixes build when using -std >= gnu11 and using clang16+
+
+Older compilers gcc < 4.9 or clang < 8 has buggy _Alignof even though it
+may support C11, exclude those compiler versions
+
+[1] https://www.open-std.org/jtc1/sc22/wg14/www/docs/n2350.htm
+[2] https://reviews.llvm.org/D133574
+
+Upstream-Status: Submitted 
[https://ml.ruby-lang.org/mailman3/hyperkitty/list/ruby-c...@ml.ruby-lang.org/thread/DLES4EPPXSPCHQMWJPPWMWXXS42AVPFA/]
+Signed-off-by: Khem Raj 
+---
+ ext/fiddle/fiddle.h | 12 +++-
+ 1 file changed, 11 insertions(+), 1 deletion(-)
+
+diff --git a/ext/fiddle/fiddle.h b/ext/fiddle/fiddle.h
+index 10eb9ce..ffb395e 100644
+--- a/ext/fiddle/fiddle.h
 b/ext/fiddle/fiddle.h
+@@ -196,7 +196,17 @@
+ #endif
+ #define TYPE_UINTPTR_T (-TYPE_INTPTR_T)
+ 
+-#define ALIGN_OF(type) offsetof(struct {char align_c; type align_x;}, align_x)
++/* GCC releases before GCC 4.9 had a bug in _Alignof.  See GCC bug 52023
++   <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52023>.
++   clang versions < 8.0.0 have the same bug.  */
++#if (!defined __STDC_VERSION__ || __STDC_VERSION__ < 201112 \
++ || (defined __GNUC__ && __GNUC__ < 4 + (__GNUC_MINOR__ < 9) \
++ && !defined __clang__) \
++ || (defined __clang__ && __clang_major__ < 8))
++# define ALIGN_OF(type) offsetof(struct {char align_c; type align_x;}, 
align_x)
++#else
++# define ALIGN_OF(type) _Alignof(type)
++#endif
+ 
+ #define ALIGN_VOIDP  ALIGN_OF(void*)
+ #define ALIGN_CHAR   ALIGN_OF(char)
+-- 
+2.39.0
+
diff --git a/meta/recipes-devtools/ruby/ruby_3.2.0.bb 
b/meta/recipes-devtools/ruby/ruby_3.2.0.bb
index 1981a7524c..0e1336f5b0 100644
--- a/meta/recipes-devtools/ruby/ruby_3.2.0.bb
+++ b/meta/recipes-devtools/ruby/ruby_3.2.0.bb
@@ -30,6 +30,7 @@ SRC_URI = 
"http://cache.ruby-lang.org/pub/ruby/${SHRT_VER}/ruby-${PV}.tar.gz \

file://0005-Mark-Gemspec-reproducible-change-fixing-784225-too.patch \
file://0006-Make-gemspecs-reproducible.patch \
file://0001-vm_dump.c-Define-REG_S1-and-REG_S2-for-musl-riscv.patch 
\
+   
file://0001-fiddle-Use-C11-_Alignof-to-define-ALIGN_OF-when-poss.patch \
"
 UPSTREAM_CHECK_URI = "https://www.ruby-lang.org/en/downloads/;
 
-- 
2.39.1


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



[OE-core] [PATCH 1/3] lttng-tools: Switch to alternative upstream submitted patch

2023-01-19 Thread Khem Raj
Signed-off-by: Khem Raj 
---
 ...pat-Define-off64_t-as-off_t-on-linux.patch | 75 ++-
 1 file changed, 56 insertions(+), 19 deletions(-)

diff --git 
a/meta/recipes-kernel/lttng/lttng-tools/0001-compat-Define-off64_t-as-off_t-on-linux.patch
 
b/meta/recipes-kernel/lttng/lttng-tools/0001-compat-Define-off64_t-as-off_t-on-linux.patch
index e3d421f730..ef81703bc3 100644
--- 
a/meta/recipes-kernel/lttng/lttng-tools/0001-compat-Define-off64_t-as-off_t-on-linux.patch
+++ 
b/meta/recipes-kernel/lttng/lttng-tools/0001-compat-Define-off64_t-as-off_t-on-linux.patch
@@ -1,35 +1,72 @@
-From cc3e1abaa1e7ad85c6a299fe30a36e0cb732e1c8 Mon Sep 17 00:00:00 2001
-From: Khem Raj 
-Date: Thu, 15 Dec 2022 14:51:20 -0800
-Subject: [PATCH] compat: Define off64_t as off_t on linux
+From 74b3844737b03492756b4f896c938b504b069f14 Mon Sep 17 00:00:00 2001
+From: Jérémie Galarneau 
+Date: Tue, 17 Jan 2023 16:57:35 -0500
+Subject: [PATCH] compat: off64_t is not defined by musl
 
-This helps compile with latest musl, where off64_t is not defined
-unless _LARGEFILE64_SOURCE is defined, on glibc _LARGEFILE64_SOURCE is
-defined if _GNU_SOURCE is defined, so the problem is only seen with musl
+This helps compile with latest musl, where off64_t is not defined unless
+_LARGEFILE64_SOURCE is defined. On glibc, _LARGEFILE64_SOURCE is defined
+if _GNU_SOURCE is defined, so the problem is only seen with musl.
 
-Upstream-Status: Submitted [https://github.com/lttng/lttng-tools/pull/164]
-Signed-off-by: Khem Raj 
+Since the project uses AC_SYS_LARGEFILE, which from the autoconf doc:
+"arrange for 64-bit file offsets, known as large-file support."
+
+As such, it is safe to assume off_t is 64-bit wide. This is checked by a
+static_assert to catch any platform where autoconf would let a 32-bit
+off_t slip.
+
+Upstream-Status: Submitted [https://review.lttng.org/c/lttng-tools/+/9268]
+Reported-by: Khem Raj 
+Signed-off-by: Jérémie Galarneau 
+Change-Id: If2c6007a8c85bc3f3065002af8a7538b882fb4a8
 ---
- src/common/compat/fcntl.h | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
 
-diff --git a/src/common/compat/fcntl.h b/src/common/compat/fcntl.h
-index 5e566e50..d19a6ece 100644
+--- a/src/common/compat/compat-fcntl.c
 b/src/common/compat/compat-fcntl.c
+@@ -13,7 +13,7 @@
+ #ifdef __linux__
+ 
+ LTTNG_HIDDEN
+-int compat_sync_file_range(int fd, off64_t offset, off64_t nbytes,
++int compat_sync_file_range(int fd, off_t offset, off_t nbytes,
+   unsigned int flags)
+ {
+ #ifdef HAVE_SYNC_FILE_RANGE
 --- a/src/common/compat/fcntl.h
 +++ b/src/common/compat/fcntl.h
-@@ -7,7 +7,6 @@
- 
+@@ -8,21 +8,21 @@
  #ifndef _COMPAT_FCNTL_H
  #define _COMPAT_FCNTL_H
--
+ 
++#include 
  #include 
  #include 
  
-@@ -22,6 +21,7 @@ typedef off64_t loff_t;
+ #include 
+ 
+-#if (defined(__CYGWIN__))
+-typedef long long off64_t;
+-#endif
++static_assert(sizeof(off_t) == sizeof(int64_t),
++"Build system is misconfigured, off_t must be 64-bit wide");
+ 
+ #if (defined(__FreeBSD__) || defined(__sun__))
+ typedef off64_t loff_t;
  #endif
  
  #ifdef __linux__
-+typedef off_t off64_t;
- extern int compat_sync_file_range(int fd, off64_t offset, off64_t nbytes,
+-extern int compat_sync_file_range(int fd, off64_t offset, off64_t nbytes,
++extern int compat_sync_file_range(int fd, off_t offset, off_t nbytes,
unsigned int flags);
  #define lttng_sync_file_range(fd, offset, nbytes, flags) \
+   compat_sync_file_range(fd, offset, nbytes, flags)
+@@ -37,8 +37,8 @@ extern int compat_sync_file_range(int fd
+ #define SYNC_FILE_RANGE_WAIT_BEFORE   0
+ #define SYNC_FILE_RANGE_WRITE 0
+ 
+-static inline int lttng_sync_file_range(int fd, off64_t offset,
+-  off64_t nbytes, unsigned int flags)
++static inline int lttng_sync_file_range(int fd, off_t offset,
++  off_t nbytes, unsigned int flags)
+ {
+   return -ENOSYS;
+ }
-- 
2.39.1


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



[OE-core] [PATCH 2/3] libtirpc: Check if file exists before operating on it

2023-01-19 Thread Khem Raj
In some cases (e.g. mingw) this file may not be installed

Signed-off-by: Khem Raj 
---
 meta/recipes-extended/libtirpc/libtirpc_1.3.3.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-extended/libtirpc/libtirpc_1.3.3.bb 
b/meta/recipes-extended/libtirpc/libtirpc_1.3.3.bb
index 8c6c20733c..f55e0b0ed1 100644
--- a/meta/recipes-extended/libtirpc/libtirpc_1.3.3.bb
+++ b/meta/recipes-extended/libtirpc/libtirpc_1.3.3.bb
@@ -22,7 +22,7 @@ inherit autotools pkgconfig
 EXTRA_OECONF = "--disable-gssapi"
 
 do_install:append() {
-   chown root:root ${D}${sysconfdir}/netconfig
+   test -e ${D}${sysconfdir}/netconfig && chown root:root 
${D}${sysconfdir}/netconfig
 }
 
 BBCLASSEXTEND = "native nativesdk"
-- 
2.39.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#176170): 
https://lists.openembedded.org/g/openembedded-core/message/176170
Mute This Topic: https://lists.openembedded.org/mt/96389606/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 1/3] binutils: Upgrade to 2.40 release

2023-01-19 Thread Khem Raj
On Thu, Jan 19, 2023 at 9:25 AM Jeff Law  wrote:

>
>
> On 1/18/23 21:27, Khem Raj wrote:
> > Signed-off-by: Khem Raj 
> > ---
> > v1 -> v2:
> > - Fix build on mingw
> > - Backport fix to build with --disable-gdb
> [ ... ]
> Note I think this is going to run afoul of grub2 mkimage.
>

Yes I am seeing that in local builds for both rv32 and rv64


> In binutils-2.40 the assembler for risc-v was changed to use CALL_PLT
> relocations rather than CALL relocations.  grub2 does not handle
> CALL_PLT relocations which in turn will cause a failure when
> grub2-mkimage is used on risc-v.
>
> As far as I can tell, the assembler change literally just changes the
> relocation number, they are otherwise treated the same.  So I think
> grub2 can be fixed by just treating R_RISCV_CALL_PLT just like
> R_RISCV_CALL in kern/riscv/dl.c.


I will try this and let you know


>
> Nelson, can you confirm that all your assembler change did was change
> the relocation used in the resultant object?
>
> Jeff
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#176161): 
https://lists.openembedded.org/g/openembedded-core/message/176161
Mute This Topic: https://lists.openembedded.org/mt/96371613/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 1/3] binutils: Upgrade to 2.40 release

2023-01-19 Thread Khem Raj
On Thu, Jan 19, 2023 at 1:44 AM Luca Ceresoli  wrote:
>
> Hi Khem,
>
> On Wed, 18 Jan 2023 20:27:22 -0800
> "Khem Raj"  wrote:
>
> > Signed-off-by: Khem Raj 
> > ---
> > v1 -> v2:
> > - Fix build on mingw
> > - Backport fix to build with --disable-gdb
> >
> >  meta/conf/distro/include/tcmode-default.inc   | 2 +-
> >  .../{binutils-2.39.inc => binutils-2.40.inc}  |22 +-
> >  39.bb => binutils-cross-canadian_2.40.bb} | 0
> >  ...39.bb => binutils-cross-testsuite_2.40.bb} | 0
> >  ...s-cross_2.39.bb => binutils-cross_2.40.bb} | 0
> >  ...ssdk_2.39.bb => binutils-crosssdk_2.40.bb} | 0
> >  ...s-crosssdk-Generate-relocatable-SDKs.patch |10 +-
> >  ...o-not-generate-linker-script-directo.patch | 4 +-
> >  ...dk-Search-for-alternative-ld.so.conf.patch |18 +-
> >  ...004-Point-scripts-location-to-libdir.patch |10 +-
> >  ...stro-compiler-point-to-the-wrong-ins.patch | 4 +-
> >  ...-system-directories-when-cross-linki.patch |44 +-
> >  ...ect-assembling-for-ppc-wait-mnemonic.patch | 8 +-
> >  .../binutils/0008-Use-libtool-2.4.patch   | 19254 ++--
> >  ...h-in-libtool-when-sysroot-is-enabled.patch | 2 +-
> >  .../0010-sync-with-OE-libtool-changes.patch   | 2 +-
> >  ...or-clang-before-checking-gcc-version.patch |10 +-
> >  ...-RPATH-entry-if-LD_RUN_PATH-is-not-e.patch | 4 +-
> >  .../binutils/0013-CVE-2022-38533.patch|36 -
> >  ...sing-_Alignof-when-using-C11-or-newe.patch |48 +
> >  .../binutils/0014-CVE-2022-38128-1.patch  |   350 -
> >  .../binutils/0014-CVE-2022-38128-2.patch  |   536 -
> >  .../binutils/0014-CVE-2022-38128-3.patch  |95 -
> >  ...-dependencies-on-gmp-and-mpfr-when-g.patch |56 +
> >  .../binutils/0015-CVE-2022-4285.patch |37 -
> >  ...-pe-dll.o-entry-deom-targ_extra_ofil.patch |41 +
> >  .../{binutils_2.39.bb => binutils_2.40.bb}| 0
> >  27 files changed, 11820 insertions(+), 8773 deletions(-)
> >  rename meta/recipes-devtools/binutils/{binutils-2.39.inc => 
> > binutils-2.40.inc} (71%)
> >  rename meta/recipes-devtools/binutils/{binutils-cross-canadian_2.39.bb => 
> > binutils-cross-canadian_2.40.bb} (100%)
> >  rename meta/recipes-devtools/binutils/{binutils-cross-testsuite_2.39.bb => 
> > binutils-cross-testsuite_2.40.bb} (100%)
> >  rename meta/recipes-devtools/binutils/{binutils-cross_2.39.bb => 
> > binutils-cross_2.40.bb} (100%)
> >  rename meta/recipes-devtools/binutils/{binutils-crosssdk_2.39.bb => 
> > binutils-crosssdk_2.40.bb} (100%)
> >  delete mode 100644 
> > meta/recipes-devtools/binutils/binutils/0013-CVE-2022-38533.patch
> >  create mode 100644 
> > meta/recipes-devtools/binutils/binutils/0013-Define-alignof-using-_Alignof-when-using-C11-or-newe.patch
> >  delete mode 100644 
> > meta/recipes-devtools/binutils/binutils/0014-CVE-2022-38128-1.patch
> >  delete mode 100644 
> > meta/recipes-devtools/binutils/binutils/0014-CVE-2022-38128-2.patch
> >  delete mode 100644 
> > meta/recipes-devtools/binutils/binutils/0014-CVE-2022-38128-3.patch
> >  create mode 100644 
> > meta/recipes-devtools/binutils/binutils/0014-configure-remove-dependencies-on-gmp-and-mpfr-when-g.patch
> >  delete mode 100644 
> > meta/recipes-devtools/binutils/binutils/0015-CVE-2022-4285.patch
> >  create mode 100644 
> > meta/recipes-devtools/binutils/binutils/0015-Remove-duplicate-pe-dll.o-entry-deom-targ_extra_ofil.patch
> >  rename meta/recipes-devtools/binutils/{binutils_2.39.bb => 
> > binutils_2.40.bb} (100%)
> >
> > diff --git a/meta/conf/distro/include/tcmode-default.inc 
> > b/meta/conf/distro/include/tcmode-default.inc
> > index 4d4929529a..bcc5f7ce1f 100644
> > --- a/meta/conf/distro/include/tcmode-default.inc
> > +++ b/meta/conf/distro/include/tcmode-default.inc
> > @@ -18,7 +18,7 @@ PREFERRED_PROVIDER_virtual/gettext ??= "gettext"
> >
> >  GCCVERSION ?= "12.%"
> >  SDKGCCVERSION ?= "${GCCVERSION}"
> > -BINUVERSION ?= "2.39%"
> > +BINUVERSION ?= "2.40%"
> >  GDBVERSION ?= "12.%"
> >  GLIBCVERSION ?= "2.37"
> >  LINUXLIBCVERSION ?= "6.1%"
>
> Applying this patch on an oe-core repository fails with 'git am':
>
> error: sha1 information is lacking or useless 
> (meta/conf/distro/include/tcmode-default.inc).
> error: could not build fake ancestor
> Patch failed at 0001 binutils: Upgrade to 2.40 release
>
> And also with 'git a

Re: [OE-core] [PATCH v2 5/5] defaultsetup: Enable largefile and 64bit time_t support systemwide

2023-01-18 Thread Khem Raj
On Wed, Jan 18, 2023 at 7:59 AM Richard Purdie
 wrote:
>
> On Tue, 2023-01-03 at 12:05 -0800, Khem Raj wrote:
> > Signed-off-by: Khem Raj 
> > ---
> >  meta/conf/distro/defaultsetup.conf | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta/conf/distro/defaultsetup.conf 
> > b/meta/conf/distro/defaultsetup.conf
> > index f6894f3ab5..1abb509629 100644
> > --- a/meta/conf/distro/defaultsetup.conf
> > +++ b/meta/conf/distro/defaultsetup.conf
> > @@ -2,7 +2,7 @@ include conf/distro/include/default-providers.inc
> >  include conf/distro/include/default-versions.inc
> >  include conf/distro/include/default-distrovars.inc
> >  include conf/distro/include/maintainers.inc
> > -
> > +include conf/distro/include/time64.inc
> >  require conf/distro/include/tcmode-${TCMODE}.inc
> >  require conf/distro/include/tclibc-${TCLIBC}.inc
> >
>
>
> I tried this as requested. I saw:
>
> x86 binutils do_compile failure:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/48/builds/6562/steps/11/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/103/builds/5424/steps/12/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/50/builds/6572/steps/12/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/76/builds/6493/steps/11/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/61/builds/6528/steps/11/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/59/builds/6481/steps/13/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/101/builds/5304/steps/13/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/52/builds/6437/steps/11/logs/stdio
>
> lib32-binutils do_compile failure:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/52/builds/6437/steps/11/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/108/builds/4042/steps/12/logs/stdio
>
> mingw binutils do_compile:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/89/builds/6562/steps/13/logs/stdio
>

all binutils errors reduce to a single problem, its in gprofng and
uses *64 versions of syscall
functions which are not available when using 64bit off_t. I have some
ideas about fixing it

> meta-virt xen-tools do_compile:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/128/builds/1166/steps/20/logs/stdio
>

This looks like a simple printf format error which can be fixed easily
by using %j printf format
and typecasting now - conn->ta_start_time to intmax_t(now - conn->ta_start_time)

> qemuarm glibc-testsuite issue:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/53/builds/6539/steps/19/logs/stdio
>
> qemumips glibc-testsuite issue:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/60/builds/6500/steps/20/logs/stdio
>
> qemux86 glibc-testsuite issue:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/59/builds/6481/steps/20/logs/stdio
>

as mentioned in previous email. We can try it with upcoming glibc.

> Close, but not quite there!

indeed

>
>
> Cheers,
>
> Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#176121): 
https://lists.openembedded.org/g/openembedded-core/message/176121
Mute This Topic: https://lists.openembedded.org/mt/96036256/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 5/5] defaultsetup: Enable largefile and 64bit time_t support systemwide

2023-01-18 Thread Khem Raj
On Wed, Jan 18, 2023 at 7:59 AM Richard Purdie
 wrote:
>
> On Tue, 2023-01-03 at 12:05 -0800, Khem Raj wrote:
> > Signed-off-by: Khem Raj 
> > ---
> >  meta/conf/distro/defaultsetup.conf | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta/conf/distro/defaultsetup.conf 
> > b/meta/conf/distro/defaultsetup.conf
> > index f6894f3ab5..1abb509629 100644
> > --- a/meta/conf/distro/defaultsetup.conf
> > +++ b/meta/conf/distro/defaultsetup.conf
> > @@ -2,7 +2,7 @@ include conf/distro/include/default-providers.inc
> >  include conf/distro/include/default-versions.inc
> >  include conf/distro/include/default-distrovars.inc
> >  include conf/distro/include/maintainers.inc
> > -
> > +include conf/distro/include/time64.inc
> >  require conf/distro/include/tcmode-${TCMODE}.inc
> >  require conf/distro/include/tclibc-${TCLIBC}.inc
> >
>
>
> I tried this as requested. I saw:
>
> x86 binutils do_compile failure:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/48/builds/6562/steps/11/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/103/builds/5424/steps/12/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/50/builds/6572/steps/12/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/76/builds/6493/steps/11/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/61/builds/6528/steps/11/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/59/builds/6481/steps/13/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/101/builds/5304/steps/13/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/52/builds/6437/steps/11/logs/stdio
>
> lib32-binutils do_compile failure:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/52/builds/6437/steps/11/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/108/builds/4042/steps/12/logs/stdio
>
> mingw binutils do_compile:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/89/builds/6562/steps/13/logs/stdio
>
> meta-virt xen-tools do_compile:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/128/builds/1166/steps/20/logs/stdio
>
> qemuarm glibc-testsuite issue:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/53/builds/6539/steps/19/logs/stdio
>
> qemumips glibc-testsuite issue:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/60/builds/6500/steps/20/logs/stdio
>
> qemux86 glibc-testsuite issue:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/59/builds/6481/steps/20/logs/stdio
>
> Close, but not quite there!

Thanks for trying it out. I did realize that we will be better off
trying with upcoming glibc 2.37
I have a patch for the upgrade on the yoe/mut  poky-contrib branch. cherry-pick

[WIP] glibc: Upgrade to 2.37

on

https://git.yoctoproject.org/poky-contrib/log/?h=yoe/mut

as is with glibc upgrade, there might be other gotchas e.g. uninative
generation etc. but
meta-oe AB job has been using this glibc for some time now.

>
>
> Cheers,
>
> Richard

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



[OE-core] [PATCH v2 3/3] elfutils: Fix build with libcurl >= 7.87

2023-01-18 Thread Khem Raj
Backport needed patches and remove local workaround

Signed-off-by: Khem Raj 
---
 .../elfutils/elfutils_0.188.bb|  4 +-
 ...od-Fix-usage-of-deprecated-CURLINFO_.patch | 49 +++
 ...t-Use-CURLOPT_PROTOCOLS_STR-for-libc.patch | 34 +
 3 files changed, 85 insertions(+), 2 deletions(-)
 create mode 100644 
meta/recipes-devtools/elfutils/files/0001-PR29926-debuginfod-Fix-usage-of-deprecated-CURLINFO_.patch
 create mode 100644 
meta/recipes-devtools/elfutils/files/0002-debuginfod-client-Use-CURLOPT_PROTOCOLS_STR-for-libc.patch

diff --git a/meta/recipes-devtools/elfutils/elfutils_0.188.bb 
b/meta/recipes-devtools/elfutils/elfutils_0.188.bb
index 084908a38c..65cae868c7 100644
--- a/meta/recipes-devtools/elfutils/elfutils_0.188.bb
+++ b/meta/recipes-devtools/elfutils/elfutils_0.188.bb
@@ -21,6 +21,8 @@ SRC_URI = 
"https://sourceware.org/elfutils/ftp/${PV}/${BP}.tar.bz2 \
file://0001-skip-the-test-when-gcc-not-deployed.patch \
file://ptest.patch \

file://0001-tests-Makefile.am-compile-test_nlist-with-standard-C.patch \
+   
file://0001-PR29926-debuginfod-Fix-usage-of-deprecated-CURLINFO_.patch \
+   
file://0002-debuginfod-client-Use-CURLOPT_PROTOCOLS_STR-for-libc.patch \
"
 SRC_URI:append:libc-musl = " \
file://0003-musl-utils.patch \
@@ -33,8 +35,6 @@ inherit autotools gettext ptest pkgconfig
 EXTRA_OECONF = "--program-prefix=eu-"
 
 BUILD_CFLAGS += "-Wno-error=stringop-overflow"
-# compatibility with curl 7.87; can be removed when elfutils upstream fixes 
the deprecation fails
-CFLAGS:append = " -Wno-error=deprecated-declarations"
 
 DEPENDS_BZIP2 = "bzip2-replacement-native"
 DEPENDS_BZIP2:class-target = "bzip2"
diff --git 
a/meta/recipes-devtools/elfutils/files/0001-PR29926-debuginfod-Fix-usage-of-deprecated-CURLINFO_.patch
 
b/meta/recipes-devtools/elfutils/files/0001-PR29926-debuginfod-Fix-usage-of-deprecated-CURLINFO_.patch
new file mode 100644
index 00..ee192e3581
--- /dev/null
+++ 
b/meta/recipes-devtools/elfutils/files/0001-PR29926-debuginfod-Fix-usage-of-deprecated-CURLINFO_.patch
@@ -0,0 +1,49 @@
+From d2bf497b12fbd49b4996ccf0744303ffd67735b1 Mon Sep 17 00:00:00 2001
+From: Andrew Paprocki 
+Date: Wed, 21 Dec 2022 11:15:00 -0500
+Subject: [PATCH] PR29926: debuginfod: Fix usage of deprecated CURLINFO_*
+
+The `CURLINFO_SIZE_DOWNLOAD_T` and `CURLINFO_CONTENT_LENGTH_DOWNLOAD_T`
+identifiers are `enum`s, not pre-processor definitions, so the current
+`#ifdef` logic is not selecting the newer API.  This results in the
+older identifiers being used and they now generate errors when compiled
+against Curl 7.87, which has silently deprecated them, causing GCC to
+emit `-Werror=deprecated-declarations`.
+
+Instead, the newer identifiers were added in Curl 7.55, so explicitly
+check for `CURL_AT_LEAST_VERSION(7, 55, 0)` instead of the current
+logic.  This eliminates the error when compiling against Curl 7.87.
+
+Ref: https://github.com/curl/curl/pull/1511
+
+Upstream-Status: Backport 
[https://sourceware.org/git/?p=elfutils.git;a=commit;h=d2bf497b12fbd49b4996ccf0744303ffd67735b1]
+Signed-off-by: Andrew Paprocki 
+---
+ debuginfod/debuginfod-client.c | 4 ++--
+ 2 files changed, 6 insertions(+), 2 deletions(-)
+
+diff --git a/debuginfod/debuginfod-client.c b/debuginfod/debuginfod-client.c
+index 8873fcc8..692aecce 100644
+--- a/debuginfod/debuginfod-client.c
 b/debuginfod/debuginfod-client.c
+@@ -1456,7 +1456,7 @@ debuginfod_query_server (debuginfod_client *c,
+  deflate-compressing proxies, this number is likely to be
+  unavailable, so -1 may show. */
+   CURLcode curl_res;
+-#ifdef CURLINFO_CONTENT_LENGTH_DOWNLOAD_T
++#if CURL_AT_LEAST_VERSION(7, 55, 0)
+   curl_off_t cl;
+   curl_res = curl_easy_getinfo(target_handle,
+CURLINFO_CONTENT_LENGTH_DOWNLOAD_T,
+@@ -1491,7 +1491,7 @@ debuginfod_query_server (debuginfod_client *c,
+   if (target_handle) /* we've committed to a server; report its 
download progress */
+ {
+   CURLcode curl_res;
+-#ifdef CURLINFO_SIZE_DOWNLOAD_T
++#if CURL_AT_LEAST_VERSION(7, 55, 0)
+   curl_off_t dl;
+   curl_res = curl_easy_getinfo(target_handle,
+CURLINFO_SIZE_DOWNLOAD_T,
+-- 
+2.39.1
+
diff --git 
a/meta/recipes-devtools/elfutils/files/0002-debuginfod-client-Use-CURLOPT_PROTOCOLS_STR-for-libc.patch
 
b/meta/recipes-devtools/elfutils/files/0002-debuginfod-client-Use-CURLOPT_PROTOCOLS_STR-for-libc.patch
new file mode 100644
index 00..2d4c912e82
--- /dev/null
+++ 
b/meta/recipes-devtools/elfutils/files/0002-debuginfod-client-Use-CURLOPT_PROTOCOLS_STR-for-libc.patch
@@ -0,0 +1,34 @@
+From 6560fb26a62ef135a804357ef4f15a47de3e49b3 Mon Sep 17 00:00:00 2001
+From: Mark Wielaard 
+Date: Tue, 10

[OE-core] [PATCH v2 2/3] binutils: Package libsframe

2023-01-18 Thread Khem Raj
libsframe is newly added in binutils 2.40

Signed-off-by: Khem Raj 
---
v1 -> v2:
- Rebase

 meta/recipes-devtools/binutils/binutils_2.40.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/binutils/binutils_2.40.bb 
b/meta/recipes-devtools/binutils/binutils_2.40.bb
index 67240383f7..9087af87c5 100644
--- a/meta/recipes-devtools/binutils/binutils_2.40.bb
+++ b/meta/recipes-devtools/binutils/binutils_2.40.bb
@@ -66,7 +66,7 @@ PACKAGE_BEFORE_PN += "libbfd libopcodes gprofng"
 FILES:libbfd = "${libdir}/libbfd-*.so.* ${libdir}/libbfd-*.so"
 FILES:libopcodes = "${libdir}/libopcodes-*.so.* ${libdir}/libopcodes-*.so"
 FILES:gprofng = "${sysconfdir}/gprofng.rc ${libdir}/gprofng/libgp-*.so 
${libdir}/gprofng/libgprofng.so.* ${bindir}/gp-* ${bindir}/gprofng"
-FILES:${PN}-dev += "${libdir}/gprofng/libgprofng.so"
+FILES:${PN}-dev += "${libdir}/gprofng/libgprofng.so ${libdir}/libsframe.so"
 SRC_URI:append:class-nativesdk =  " 
file://0003-binutils-nativesdk-Search-for-alternative-ld.so.conf.patch "
 
 USE_ALTERNATIVES_FOR:class-nativesdk = ""
-- 
2.39.1


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



[OE-core] [PATCH v2] mdadm: Define alignof using _Alignof when using C11 or newer

2023-01-18 Thread Khem Raj
Signed-off-by: Khem Raj 
---
v2: Update patch status

 ...sing-_Alignof-when-using-C11-or-newe.patch | 52 +++
 meta/recipes-extended/mdadm/mdadm_4.2.bb  |  1 +
 2 files changed, 53 insertions(+)
 create mode 100644 
meta/recipes-extended/mdadm/files/0001-Define-alignof-using-_Alignof-when-using-C11-or-newe.patch

diff --git 
a/meta/recipes-extended/mdadm/files/0001-Define-alignof-using-_Alignof-when-using-C11-or-newe.patch
 
b/meta/recipes-extended/mdadm/files/0001-Define-alignof-using-_Alignof-when-using-C11-or-newe.patch
new file mode 100644
index 00..9e3a30be23
--- /dev/null
+++ 
b/meta/recipes-extended/mdadm/files/0001-Define-alignof-using-_Alignof-when-using-C11-or-newe.patch
@@ -0,0 +1,52 @@
+From 82c893bb9e01f914a6bdef1bef943af746cfc3e1 Mon Sep 17 00:00:00 2001
+From: Khem Raj 
+Date: Sun, 15 Jan 2023 12:42:18 -0800
+Subject: [PATCH] Define alignof using _Alignof when using C11 or newer
+
+WG14 N2350 made very clear that it is an UB having type definitions
+within "offsetof" [1]. This patch enhances the implementation of macro
+alignof_slot to use builtin "_Alignof" to avoid undefined behavior on
+when using std=c11 or newer
+
+clang 16+ has started to flag this [2]
+
+Fixes build when using -std >= gnu11 and using clang16+
+
+Older compilers gcc < 4.9 or clang < 8 has buggy _Alignof even though it
+may support C11, exclude those compilers too
+
+[1] https://www.open-std.org/jtc1/sc22/wg14/www/docs/n2350.htm
+[2] https://reviews.llvm.org/D133574
+
+Upstream-Status: Submitted 
[https://lore.kernel.org/linux-raid/20230118083236.24418-1-raj.k...@gmail.com/T/#u]
+Signed-off-by: Khem Raj 
+---
+ sha1.c | 12 +++-
+ 1 file changed, 11 insertions(+), 1 deletion(-)
+
+diff --git a/sha1.c b/sha1.c
+index 89b32f4..1e4ad5d 100644
+--- a/sha1.c
 b/sha1.c
+@@ -229,7 +229,17 @@ sha1_process_bytes (const void *buffer, size_t len, 
struct sha1_ctx *ctx)
+   if (len >= 64)
+ {
+ #if !_STRING_ARCH_unaligned
+-# define alignof(type) offsetof (struct { char c; type x; }, x)
++/* GCC releases before GCC 4.9 had a bug in _Alignof.  See GCC bug 52023
++   <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52023>.
++   clang versions < 8.0.0 have the same bug.  */
++# if (!defined __STDC_VERSION__ || __STDC_VERSION__ < 201112 \
++  || (defined __GNUC__ && __GNUC__ < 4 + (__GNUC_MINOR__ < 9) \
++   && !defined __clang__) \
++  || (defined __clang__ && __clang_major__ < 8))
++#  define alignof(type) offsetof (struct { char c; type x; }, x)
++# else
++#  define alignof(type) _Alignof(type)
++# endif
+ # define UNALIGNED_P(p) (((size_t) p) % alignof (sha1_uint32) != 0)
+   if (UNALIGNED_P (buffer))
+   while (len > 64)
+-- 
+2.39.0
+
diff --git a/meta/recipes-extended/mdadm/mdadm_4.2.bb 
b/meta/recipes-extended/mdadm/mdadm_4.2.bb
index 7298860241..1c4397509b 100644
--- a/meta/recipes-extended/mdadm/mdadm_4.2.bb
+++ b/meta/recipes-extended/mdadm/mdadm_4.2.bb
@@ -25,6 +25,7 @@ SRC_URI = 
"${KERNELORG_MIRROR}/linux/utils/raid/mdadm/${BPN}-${PV}.tar.xz \
file://0001-Fix-parsing-of-r-in-monitor-manager-mode.patch \
file://0001-Makefile-install-mdcheck.patch \

file://0001-restripe.c-Use-_FILE_OFFSET_BITS-to-enable-largefile.patch \
+   
file://0001-Define-alignof-using-_Alignof-when-using-C11-or-newe.patch \
"
 
 SRC_URI[sha256sum] = 
"461c215670864bb74a4d1a3620684aa2b2f8296dffa06743f26dda5557acf01d"
-- 
2.39.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#176112): 
https://lists.openembedded.org/g/openembedded-core/message/176112
Mute This Topic: https://lists.openembedded.org/mt/96359487/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 3/3] binutils: Delete gdb and supporting sources

2023-01-18 Thread Khem Raj
On Wed, Jan 18, 2023 at 12:47 AM Alejandro Hernandez  wrote:
>
> Hey Khem,
>
> On Sun, 15 Jan 2023 at 11:44, Khem Raj  wrote:
>>
>> Signed-off-by: Khem Raj 
>> ---
>>  meta/recipes-devtools/binutils/binutils.inc | 10 ++
>>  1 file changed, 10 insertions(+)
>>
>> diff --git a/meta/recipes-devtools/binutils/binutils.inc 
>> b/meta/recipes-devtools/binutils/binutils.inc
>> index 98acf0a222..2b38aeb62d 100644
>> --- a/meta/recipes-devtools/binutils/binutils.inc
>> +++ b/meta/recipes-devtools/binutils/binutils.inc
>> @@ -140,6 +140,16 @@ export CC_FOR_BUILD = "LD_LIBRARY_PATH= ${BUILD_CC}"
>>
>>  MULTIARCH := "${@bb.utils.contains("DISTRO_FEATURES", "multiarch", "yes", 
>> "no", d)}"
>>  do_configure[vardeps] += "MULTIARCH"
>> +
>> +addtask do_prepare_sources after do_patch before do_configure
>> +
>> +# Remove gdb and supporting source directories, they are detected by
>> +# configure otherwise and demands additional gdb deps e.g. gmp, mpc, mpfr
>> +do_prepare_sources () {
>> +   rm -rf ${S}/gdb ${S}/gdbserver ${S}/gdbsupport ${S}/gnulib \
>> +   ${S}/libbacktrace ${S}/libdecnumber ${S}/readline ${S}/sim
>> +}
>> +
>
>
> This seems to have been fixed upstream, I wonder if its better to backport 
> that patch to 2.40 so it aligns properly with the --disable-gdb flag we are 
> passing:
> https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=5fb0e308577143ceb313fde5538dc9ecb038f29f
>

Thanks yes its better to backport it, I will add it to v2.

> Cheers,
>
> Alejandro
>>
>>  do_configure () {
>> (cd ${S} && gnu-configize)
>>
>> --
>> 2.39.0
>>
>>
>> 
>>

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



[OE-core] [PATCH 3/4] vulkan-samples: Drop using u8string_view

2023-01-17 Thread Khem Raj
Its deprecated in upstream fmt as well. Moreover it helps compile with
latest compiler

Signed-off-by: Khem Raj 
---
 .../0001-Deprecate-u8string_view.patch| 59 +++
 .../vulkan/vulkan-samples_git.bb  |  1 +
 2 files changed, 60 insertions(+)
 create mode 100644 
meta/recipes-graphics/vulkan/vulkan-samples/0001-Deprecate-u8string_view.patch

diff --git 
a/meta/recipes-graphics/vulkan/vulkan-samples/0001-Deprecate-u8string_view.patch
 
b/meta/recipes-graphics/vulkan/vulkan-samples/0001-Deprecate-u8string_view.patch
new file mode 100644
index 00..c2304bdd48
--- /dev/null
+++ 
b/meta/recipes-graphics/vulkan/vulkan-samples/0001-Deprecate-u8string_view.patch
@@ -0,0 +1,59 @@
+From 93987b1ce7d6f91387202495aac61026070597df Mon Sep 17 00:00:00 2001
+From: Khem Raj 
+Date: Sun, 15 Jan 2023 21:37:52 -0800
+Subject: [PATCH] Deprecate u8string_view
+
+Use basic_string_view instead
+
+Upstream-Status: Backport 
[https://github.com/fmtlib/fmt/commit/dea7fde8b7d649923dd41b0766bdf076033c62a2]
+Signed-off-by: Khem Raj 
+---
+ include/spdlog/fmt/bundled/core.h   |  3 ++-
+ include/spdlog/fmt/bundled/format.h | 15 ++-
+ 2 files changed, 4 insertions(+), 14 deletions(-)
+
+diff --git a/include/spdlog/fmt/bundled/core.h 
b/include/spdlog/fmt/bundled/core.h
+index 50b79351..e8b029ef 100644
+--- a/include/spdlog/fmt/bundled/core.h
 b/include/spdlog/fmt/bundled/core.h
+@@ -1484,7 +1484,8 @@ FMT_API void vprint(wstring_view format_str, 
wformat_args args);
+ 
+ /**
+   \rst
+-  Prints formatted data to ``stdout``.
++  Formats ``args`` according to specifications in ``format_str`` and writes 
the
++  output to ``stdout``.
+ 
+   **Example**::
+ 
+diff --git a/include/spdlog/fmt/bundled/format.h 
b/include/spdlog/fmt/bundled/format.h
+index 1bb24a52..39426361 100644
+--- a/include/spdlog/fmt/bundled/format.h
 b/include/spdlog/fmt/bundled/format.h
+@@ -407,21 +407,10 @@ void basic_buffer::append(const U *begin, const U 
*end) {
+ enum char8_t: unsigned char {};
+ #endif
+ 
+-// A UTF-8 string view.
+-class u8string_view : public basic_string_view {
+- public:
+-  typedef char8_t char_type;
+-
+-  u8string_view(const char *s):
+-basic_string_view(reinterpret_cast(s)) {}
+-  u8string_view(const char *s, size_t count) FMT_NOEXCEPT:
+-basic_string_view(reinterpret_cast(s), count) {}
+-};
+-
+ #if FMT_USE_USER_DEFINED_LITERALS
+ inline namespace literals {
+-inline u8string_view operator"" _u(const char *s, std::size_t n) {
+-  return {s, n};
++inline basic_string_view operator"" _u(const char* s, std::size_t n) 
{
++  return {reinterpret_cast(s), n};
+ }
+ }
+ #endif
+-- 
+2.39.0
+
diff --git a/meta/recipes-graphics/vulkan/vulkan-samples_git.bb 
b/meta/recipes-graphics/vulkan/vulkan-samples_git.bb
index 26300ecb1d..7f52cb66c9 100644
--- a/meta/recipes-graphics/vulkan/vulkan-samples_git.bb
+++ b/meta/recipes-graphics/vulkan/vulkan-samples_git.bb
@@ -8,6 +8,7 @@ LIC_FILES_CHKSUM = 
"file://LICENSE;md5=48aa35cefb768436223a6e7f18dc2a2a"
 SRC_URI = 
"gitsm://github.com/KhronosGroup/Vulkan-Samples.git;branch=master;protocol=https;lfs=0
 \
file://debugfix.patch \

file://0001-Do-not-use-LFS64-functions-on-linux-musl.patch;patchdir=third_party/spdlog
 \
+   
file://0001-Deprecate-u8string_view.patch;patchdir=third_party/spdlog \
"
 
 UPSTREAM_CHECK_COMMITS = "1"
-- 
2.39.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#176068): 
https://lists.openembedded.org/g/openembedded-core/message/176068
Mute This Topic: https://lists.openembedded.org/mt/96343399/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 4/4] musl-obstack: Update to 1.2.3

2023-01-17 Thread Khem Raj
Switch to void-linux github handle, void-linux is the upstream anyway this 
brings

Signed-off-by: Khem Raj 
---
 meta/recipes-core/musl/musl-obstack.bb | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-core/musl/musl-obstack.bb 
b/meta/recipes-core/musl/musl-obstack.bb
index 5c95ddbc94..4c71a141b2 100644
--- a/meta/recipes-core/musl/musl-obstack.bb
+++ b/meta/recipes-core/musl/musl-obstack.bb
@@ -8,9 +8,9 @@ LICENSE = "GPL-2.0-or-later"
 LIC_FILES_CHKSUM = "file://COPYING;md5=3d23e4eef8243efcaab6f0a438078932"
 SECTION = "libs"
 
-PV = "1.2"
-SRCREV = "466f773fe171da427e28be79b9cf48ccfddfb7e2"
-SRC_URI = "git://github.com/pullmoll/musl-obstack;branch=master;protocol=https"
+PV = "1.2.3"
+SRCREV = "f4385255be1615688c6a5f042277304d7ab288b1"
+SRC_URI = 
"git://github.com/void-linux/musl-obstack;branch=master;protocol=https"
 
 UPSTREAM_CHECK_COMMITS = "1"
 
-- 
2.39.0


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



[OE-core] [PATCH 1/4] mdadm: Define alignof using _Alignof when using C11 or newer

2023-01-17 Thread Khem Raj
Signed-off-by: Khem Raj 
---
 ...sing-_Alignof-when-using-C11-or-newe.patch | 52 +++
 meta/recipes-extended/mdadm/mdadm_4.2.bb  |  1 +
 2 files changed, 53 insertions(+)
 create mode 100644 
meta/recipes-extended/mdadm/files/0001-Define-alignof-using-_Alignof-when-using-C11-or-newe.patch

diff --git 
a/meta/recipes-extended/mdadm/files/0001-Define-alignof-using-_Alignof-when-using-C11-or-newe.patch
 
b/meta/recipes-extended/mdadm/files/0001-Define-alignof-using-_Alignof-when-using-C11-or-newe.patch
new file mode 100644
index 00..1c472886b3
--- /dev/null
+++ 
b/meta/recipes-extended/mdadm/files/0001-Define-alignof-using-_Alignof-when-using-C11-or-newe.patch
@@ -0,0 +1,52 @@
+From 82c893bb9e01f914a6bdef1bef943af746cfc3e1 Mon Sep 17 00:00:00 2001
+From: Khem Raj 
+Date: Sun, 15 Jan 2023 12:42:18 -0800
+Subject: [PATCH] Define alignof using _Alignof when using C11 or newer
+
+WG14 N2350 made very clear that it is an UB having type definitions
+within "offsetof" [1]. This patch enhances the implementation of macro
+alignof_slot to use builtin "_Alignof" to avoid undefined behavior on
+when using std=c11 or newer
+
+clang 16+ has started to flag this [2]
+
+Fixes build when using -std >= gnu11 and using clang16+
+
+Older compilers gcc < 4.9 or clang < 8 has buggy _Alignof even though it
+may support C11, exclude those compilers too
+
+[1] https://www.open-std.org/jtc1/sc22/wg14/www/docs/n2350.htm
+[2] https://reviews.llvm.org/D133574
+
+Upstream-Status: Pending
+Signed-off-by: Khem Raj 
+---
+ sha1.c | 12 +++-
+ 1 file changed, 11 insertions(+), 1 deletion(-)
+
+diff --git a/sha1.c b/sha1.c
+index 89b32f4..1e4ad5d 100644
+--- a/sha1.c
 b/sha1.c
+@@ -229,7 +229,17 @@ sha1_process_bytes (const void *buffer, size_t len, 
struct sha1_ctx *ctx)
+   if (len >= 64)
+ {
+ #if !_STRING_ARCH_unaligned
+-# define alignof(type) offsetof (struct { char c; type x; }, x)
++/* GCC releases before GCC 4.9 had a bug in _Alignof.  See GCC bug 52023
++   <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52023>.
++   clang versions < 8.0.0 have the same bug.  */
++# if (!defined __STDC_VERSION__ || __STDC_VERSION__ < 201112 \
++  || (defined __GNUC__ && __GNUC__ < 4 + (__GNUC_MINOR__ < 9) \
++   && !defined __clang__) \
++  || (defined __clang__ && __clang_major__ < 8))
++#  define alignof(type) offsetof (struct { char c; type x; }, x)
++# else
++#  define alignof(type) _Alignof(type)
++# endif
+ # define UNALIGNED_P(p) (((size_t) p) % alignof (sha1_uint32) != 0)
+   if (UNALIGNED_P (buffer))
+   while (len > 64)
+-- 
+2.39.0
+
diff --git a/meta/recipes-extended/mdadm/mdadm_4.2.bb 
b/meta/recipes-extended/mdadm/mdadm_4.2.bb
index 7298860241..1c4397509b 100644
--- a/meta/recipes-extended/mdadm/mdadm_4.2.bb
+++ b/meta/recipes-extended/mdadm/mdadm_4.2.bb
@@ -25,6 +25,7 @@ SRC_URI = 
"${KERNELORG_MIRROR}/linux/utils/raid/mdadm/${BPN}-${PV}.tar.xz \
file://0001-Fix-parsing-of-r-in-monitor-manager-mode.patch \
file://0001-Makefile-install-mdcheck.patch \

file://0001-restripe.c-Use-_FILE_OFFSET_BITS-to-enable-largefile.patch \
+   
file://0001-Define-alignof-using-_Alignof-when-using-C11-or-newe.patch \
"
 
 SRC_URI[sha256sum] = 
"461c215670864bb74a4d1a3620684aa2b2f8296dffa06743f26dda5557acf01d"
-- 
2.39.0


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



[OE-core] [PATCH 2/4] python3-numpy: Define _ALIGN using _Alignof when using C11 or newer

2023-01-17 Thread Khem Raj
Signed-off-by: Khem Raj 
---
 ...ing-_Alignof-when-using-C11-or-newer.patch | 77 +++
 .../python/python3-numpy_1.24.1.bb|  1 +
 2 files changed, 78 insertions(+)
 create mode 100644 
meta/recipes-devtools/python/python3-numpy/0001-Define-_ALIGN-using-_Alignof-when-using-C11-or-newer.patch

diff --git 
a/meta/recipes-devtools/python/python3-numpy/0001-Define-_ALIGN-using-_Alignof-when-using-C11-or-newer.patch
 
b/meta/recipes-devtools/python/python3-numpy/0001-Define-_ALIGN-using-_Alignof-when-using-C11-or-newer.patch
new file mode 100644
index 00..97391e2c12
--- /dev/null
+++ 
b/meta/recipes-devtools/python/python3-numpy/0001-Define-_ALIGN-using-_Alignof-when-using-C11-or-newer.patch
@@ -0,0 +1,77 @@
+From f9ac08a0fea543d68b2dba540093bd079e50be47 Mon Sep 17 00:00:00 2001
+From: Khem Raj 
+Date: Sun, 15 Jan 2023 15:49:09 -0800
+Subject: [PATCH] Define _ALIGN using _Alignof when using C11 or newer
+
+WG14 N2350 made very clear that it is an UB having type definitions
+within "offsetof" [1]. This patch enhances the implementation of macro
+_ALIGN to use builtin "_Alignof" to avoid undefined behavior on
+when using std=c11 or newer
+
+clang 16+ has started to flag this [2]
+
+Fixes build when using -std >= gnu11 and using clang16+
+
+Older compilers gcc < 4.9 or clang < 8 has buggy _Alignof even though it
+may support C11, exclude those compilers too
+
+[1] https://www.open-std.org/jtc1/sc22/wg14/www/docs/n2350.htm
+[2] https://reviews.llvm.org/D133574
+
+Upstream-Status: Submitted [https://github.com/numpy/numpy/pull/23016]
+Signed-off-by: Khem Raj 
+---
+ numpy/core/src/multiarray/arraytypes.c.src | 13 +++--
+ numpy/core/src/multiarray/common.h | 12 +++-
+ 2 files changed, 22 insertions(+), 3 deletions(-)
+
+diff --git a/numpy/core/src/multiarray/arraytypes.c.src 
b/numpy/core/src/multiarray/arraytypes.c.src
+index c03d09784..683917220 100644
+--- a/numpy/core/src/multiarray/arraytypes.c.src
 b/numpy/core/src/multiarray/arraytypes.c.src
+@@ -224,8 +224,17 @@ MyPyLong_AsUnsigned@Type@(PyObject *obj)
+  ** GETITEM AND SETITEM **
+  *
+  */
+-
+-#define _ALIGN(type) offsetof(struct {char c; type v;}, v)
++/* GCC releases before GCC 4.9 had a bug in _Alignof.  See GCC bug 52023
++   <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52023>.
++   clang versions < 8.0.0 have the same bug.  */
++#if (!defined __STDC_VERSION__ || __STDC_VERSION__ < 201112 \
++ || (defined __GNUC__ && __GNUC__ < 4 + (__GNUC_MINOR__ < 9) \
++  && !defined __clang__) \
++ || (defined __clang__ && __clang_major__ < 8))
++# define _ALIGN(type) offsetof(struct {char c; type v;}, v)
++#else
++# define _ALIGN(type) _Alignof(type)
++#endif
+ /*
+  * Disable harmless compiler warning "4116: unnamed type definition in
+  * parentheses" which is caused by the _ALIGN macro.
+diff --git a/numpy/core/src/multiarray/common.h 
b/numpy/core/src/multiarray/common.h
+index 3de8c842d..d01074c45 100644
+--- a/numpy/core/src/multiarray/common.h
 b/numpy/core/src/multiarray/common.h
+@@ -178,7 +178,17 @@ check_and_adjust_axis(int *axis, int ndim)
+ }
+ 
+ /* used for some alignment checks */
+-#define _ALIGN(type) offsetof(struct {char c; type v;}, v)
++/* GCC releases before GCC 4.9 had a bug in _Alignof.  See GCC bug 52023
++   <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52023>.
++   clang versions < 8.0.0 have the same bug.  */
++#if (!defined __STDC_VERSION__ || __STDC_VERSION__ < 201112 \
++ || (defined __GNUC__ && __GNUC__ < 4 + (__GNUC_MINOR__ < 9) \
++  && !defined __clang__) \
++ || (defined __clang__ && __clang_major__ < 8))
++# define _ALIGN(type) offsetof(struct {char c; type v;}, v)
++#else
++# define _ALIGN(type) _Alignof(type)
++#endif
+ #define _UINT_ALIGN(type) npy_uint_alignment(sizeof(type))
+ /*
+  * Disable harmless compiler warning "4116: unnamed type definition in
+-- 
+2.39.0
+
diff --git a/meta/recipes-devtools/python/python3-numpy_1.24.1.bb 
b/meta/recipes-devtools/python/python3-numpy_1.24.1.bb
index 83b8ac4232..adac08b3e1 100644
--- a/meta/recipes-devtools/python/python3-numpy_1.24.1.bb
+++ b/meta/recipes-devtools/python/python3-numpy_1.24.1.bb
@@ -10,6 +10,7 @@ SRCNAME = "numpy"
 SRC_URI = "${GITHUB_BASE_URI}/download/v${PV}/${SRCNAME}-${PV}.tar.gz \

file://0001-Don-t-search-usr-and-so-on-for-libraries-by-default-.patch \
file://0001-numpy-core-Define-RISCV-32-support.patch \
+   
file://0001-Define-_ALIGN-using-_Alignof-when-using-C11-or-newer.patch \
file://run-ptest \
"
 SRC_URI[sha256sum] = 
"2386da9a471cc00a1f47845e27d916d5ec5346ae9696e01a8a34760858fe9dd2"
-- 
2.39.0


-=-=-=-=-=-=-=-=-=-=-=-
Links:

Re: [OE-Core][PATCH 3/3] qemuppc64: set the qemuppc64 nfs r/wsize mount options to 524288

2023-01-16 Thread Khem Raj
On Mon, Jan 16, 2023 at 6:05 PM Xiangyu Chen
 wrote:
>
> From: Xiangyu Chen 
>
> On master oe, build a qemuppc64 with systemd as default init, when we
> use nfs bootup, the kernel might panic due to missing symbol in dynamic
> libraries as below:
>
>   hid-generic 0003:0627:0001.0003: input: USB HID v0.01 Mouse [QEMU QEMU USB 
> Tablet] on usb-:00:01.0-3/input0
>   /sbin/init: /lib64/libm.so.6: version `XZ_5.0' not found (required by 
> /usr/lib64/libkmod.so.2)
>   Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00
>   CPU: 0 PID: 1 Comm: init Not tainted 5.15.78-yocto-standard #1
>   Call Trace:
>   [c7443ba0] [c09538d0] dump_stack_lvl+0x74/0xa8 (unreliable)
>   [c7443be0] [c0103524] panic+0x170/0x3cc
>   [c7443c80] [c010cf64] do_exit+0xb44/0xb50
>   [c7443d50] [c010d040] do_group_exit+0x60/0xd0
>   [c7443d90] [c010d0d4] sys_exit_group+0x24/0x30
>   [c7443db0] [c002cfd4] system_call_exception+0x194/0x2f0
>   [c7443e10] [c000c2cc] system_call_common+0xec/0x250
>   --- interrupt: c00 at 0x7fff9ed9e840
>   NIP:  7fff9ed9e840 LR: 7fff9ed7da20 CTR: 
>   REGS: c7443e80 TRAP: 0c00   Not tainted (5.15.78-yocto-standard)
>   MSR:  8280f033   CR: 24022442  
> XER: 
>
> One or more of the libraries systemd depends on failed to load due to
> unresolved symbols/functions.  This was intermittent - with a failure
> rate estimated between 5% and 30%.
>
> After checking the code, this issue happens on gcc 12, kirkstone is using
> gcc 11 works well, with both using the exact same v5.15.84 kernel commit.
>
> There is a kernel fix from upstream [1], they changed the rsize / wsize
> to a multiple of PAGE_SIZE, when we applied this patch, the qemuppc64's
> default r/wsize went from 4096 to 524288.But the qemuppc64 doesn't have
> its own linux-yocto kernel branch, so apply this change might cause
> regression with other platforms which share branch with qemuppc64.
>
> So, we added an extra option for nfs rootfs, and set the qemuppc64 default
> r/w size to 524288 to line up with the kernel fix[1].
>
> Yocto did a similar thing in the distant past[2] - prior to boot-arg
> adjustments existing - by allowing a Kconfig to set the defaults on
> nfsboot, in order to work around hardware limitations.
>
> Reference:
> [1] 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=940261a195080cf
> [2] 
> https://git.yoctoproject.org/linux-yocto-4.1/commit/?h=standard/base=a96cfd98add95
>
> Signed-off-by: Xiangyu Chen 
> ---
>  meta/conf/machine/qemuppc64.conf | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/meta/conf/machine/qemuppc64.conf 
> b/meta/conf/machine/qemuppc64.conf
> index 304f06a30d..7709339313 100644
> --- a/meta/conf/machine/qemuppc64.conf
> +++ b/meta/conf/machine/qemuppc64.conf
> @@ -15,6 +15,7 @@ QB_MACHINE = "-machine pseries"
>  QB_CPU = "-cpu POWER9"
>  QB_SMP = "-smp 2"
>
> +QB_NFSROOTFS_EXTRA_OPT = "wsize=524288,rsize=524288"

lgtm

>  QB_KERNEL_CMDLINE_APPEND = "console=hvc0 nohugevmalloc"
>  #QB_OPT_APPEND += "-device qemu-xhci -device usb-tablet -device usb-kbd"
>  QB_OPT_APPEND = "-usb -device usb-tablet"
> --
> 2.34.1
>
>
> 
>

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



<    3   4   5   6   7   8   9   10   11   12   >