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

2023-02-22 Thread Markus Volk
- Allow to build the gtk4 widget and vapi This is needed to build gtk4 based terminals like blackbox - Update dependencies - Cleanup recipe Signed-off-by: Markus Volk --- .../vte/{vte_0.70.2.bb => vte_0.70.3.bb} | 22 +-- 1 file changed, 11 insertions(+), 11 deletions(-)

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

2023-02-22 Thread Markus Volk
Am Do, 23. Feb 2023 um 00:42:15 +0100 schrieb Alexandre Belloni : This fails on musl: I've missinterpreted that this patch is not needed anymore 0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch After following the conversation Ross Burton started some years ago it turned out, that the

[OE-core] [PATCH] mc: set ac_cv_path_PERL_FOR_BUILD

2023-02-22 Thread Yu, Mingli
From: Mingli Yu After mc upgrade to 4.8.29, it introduces PERL_FOR_BUILD [1] and will result in the below build failure on some system when we build under a project with long path. | make[4]: Entering directory

[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

[OE-core] [PATCH v12] Rust Oe-Selftest implementation

2023-02-22 Thread Pgowda
From: pgowda The patch implements Rust testing framework similar to other selftest, specifically the gcc selftest in OE. It uses the client and server based method to test the binaries for cross-target on the image. The test framework is a wrapper around the Rust build system as ./x.py test. It

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,

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

2023-02-22 Thread Lee Chee Yang
From: Chee Yang Lee yocto-check-layer to check all .patch file in layer for Upstream-status and list down all .patch file without Upstream-Status. Since upstream-status is additional Yocto Compatible requirement, set this test as expected failure for now so it wont fail final result. [YOCTO

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)': > |

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)': > |

[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

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

2023-02-22 Thread Martin Jansa
From: Joel Stanley When building native qemu with 6.2 kernel headers, qemu fails to build: In file included from /usr/include/linux/btrfs.h:29, from ../qemu-7.2.0/linux-user/syscall.c:165: /usr/include/linux/fs.h:50:8: error: redefinition of ‘struct file_clone_range’ 50

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

2023-02-22 Thread Joel Stanley
On Thu, 23 Feb 2023 at 00:11, Martin Jansa wrote: > > On Thu, Feb 23, 2023 at 1:08 AM Joel Stanley wrote: >> >> On Wed, 22 Feb 2023 at 15:28, Martin Jansa wrote: >> > >> > Hi, >> > >> > I've seen this build issue on my gentoo builder today with qemu-native, so >> > I've removed the stray

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

2023-02-22 Thread Martin Jansa
On Thu, Feb 23, 2023 at 1:08 AM Joel Stanley wrote: > On Wed, 22 Feb 2023 at 15:28, Martin Jansa wrote: > > > > Hi, > > > > I've seen this build issue on my gentoo builder today with qemu-native, > so I've removed the stray cross.patch and sent v2. > > > > Then RP had good question how to

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

2023-02-22 Thread Joel Stanley
On Wed, 22 Feb 2023 at 15:28, Martin Jansa wrote: > > Hi, > > I've seen this build issue on my gentoo builder today with qemu-native, so > I've removed the stray cross.patch and sent v2. > > Then RP had good question how to reproduce this failure and I've checked when > I've updated glibc in

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

2023-02-22 Thread Alexandre Belloni via lists.openembedded.org
x32 also failed: https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/6593/steps/11/logs/stdio On 23/02/2023 00:42:17+0100, Alexandre Belloni wrote: > This fails on musl: > > https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/6703/steps/11/logs/stdio >

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

2023-02-22 Thread Alexandre Belloni via lists.openembedded.org
Hello, This failed on musl: | checking minix/config.h usability... ../../gdb-13.1/gdbserver/linux-low.cc: In function 'int proc_xfer_memory(CORE_ADDR, unsigned char*, const gdb_byte*, int)': | ../../gdb-13.1/gdbserver/linux-low.cc:5393:45: error: expected ':' before ')' token | 5393 |

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

2023-02-22 Thread Alexandre Belloni via lists.openembedded.org
This fails on musl: https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/6703/steps/11/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/6722/steps/12/logs/stdio On 22/02/2023 12:48:47+0100, Markus Volk wrote: > - Allow to build the gtk4 widget and vapi >

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

2023-02-22 Thread Pavel Zhukov
Alexandre Belloni writes: > Hello, > > This is the cause of: Hi Alex, Yes, my fault, sorry about that. Arm64 is valid U-boot/mkimage architecture. Proper fix sent as: "[PATCH] u-boot: Map arm64 into map for u-boot dts installation" This patch can be dropped. > >

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

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

Re: [OE-core] sstate cache management

2023-02-22 Thread Alex Kiernan
On Wed, Feb 22, 2023 at 8:33 PM Richard Purdie wrote: > > On Wed, 2023-02-22 at 17:56 +, Alex Kiernan wrote: > > I needed to do something about our shared sstate store and waded into > > the sstate cache management problem as the existing script takes hours > > to run over NFS (which for

Re: [OE-core] [PATCH 08/11] build-appliance-image: use a real /tmp

2023-02-22 Thread Trevor Woerner
On Wed 2023-02-22 @ 02:46:30 PM, Richard Purdie wrote: > On Tue, 2023-02-21 at 21:25 -0500, Trevor Woerner wrote: > > On Tue 2023-02-21 @ 03:44:42 PM, Trevor Woerner via lists.openembedded.org > > wrote: > > > Make /tmp a real directory in the root filesystem and not a link to an > > > in-memory

Re: [OE-core] sstate cache management

2023-02-22 Thread Richard Purdie
On Wed, 2023-02-22 at 17:56 +, Alex Kiernan wrote: > I needed to do something about our shared sstate store and waded into > the sstate cache management problem as the existing script takes hours > to run over NFS (which for better or worse is where ours is). I've set > myself the problem of

Re: [OE-core] sstate cache management

2023-02-22 Thread Alex Kiernan
On Wed, Feb 22, 2023 at 7:36 PM Alexandre Belloni wrote: > > Hello, > > This doesn't answer your question but did you look into > https://lore.kernel.org/all/2022112102.5556-1-tomasz.dziendziel...@gmail.com/? > Thanks, yeah, I did... it really didn't scratch the particular itch I had, mostly

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

Re: [OE-core] sstate cache management

2023-02-22 Thread Alexandre Belloni via lists.openembedded.org
Hello, This doesn't answer your question but did you look into https://lore.kernel.org/all/2022112102.5556-1-tomasz.dziendziel...@gmail.com/? On 22/02/2023 17:56:35+, Alex Kiernan wrote: > I needed to do something about our shared sstate store and waded into > the sstate cache management

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

2023-02-22 Thread Alexandre Belloni via lists.openembedded.org
Hello, This is the cause of: https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/995/steps/14/logs/stdio 2023-02-22 11:33:00,834 - oe-selftest - INFO - fitimage.FitImageTests.test_fit_image (subunit.RemotedTestCase) 2023-02-22 11:33:00,835 - oe-selftest - INFO - ... FAIL |

[OE-core] sstate cache management

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

[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* *

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

2023-02-22 Thread Denys Dmytriyenko
All, You are cordially invited to the next OpenEmbedded Happy Hour on February 22 for Asia/Pacific timezones @ 2100/9pm UTC (4pm ET / 1pm PT): https://www.openembedded.org/wiki/Calendar https://www.openembedded.org/wiki/Happy_Hours

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

2023-02-22 Thread Alexandre Belloni via lists.openembedded.org
Hello Khem, Unfortunately, this fails: https://autobuilder.yoctoproject.org/typhoon/#/builders/52/builds/6608/steps/12/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/2435/steps/13/logs/stdio |

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

2023-02-22 Thread Ross Burton
On 21 Feb 2023, at 14:14, Richard Elberger via lists.openembedded.org wrote: > > Hello Ross, > > It wasn't entirely clear to me that the patch would be required if taken > from docbook, but I see that my "test scope" was not appropriate and you > have surfaced why patching is required. Now

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

2023-02-22 Thread Martin Jansa
Hi, I've seen this build issue on my gentoo builder today with qemu-native, so I've removed the stray cross.patch and sent v2. Then RP had good question how to reproduce this failure and I've checked when I've updated glibc in gentoo for last time and it was a month ago (and I've rebuilt

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

2023-02-22 Thread Martin Jansa
From: Joel Stanley When building native qemu with glibc 2.36 (including latest changes from the glibc stable branch), qemu fails to build: In file included from /usr/include/linux/btrfs.h:29, from ../qemu-7.2.0/linux-user/syscall.c:165: /usr/include/linux/fs.h:50:8: error:

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

2023-02-22 Thread Richard Purdie
Add in the new 'check' calls which mean that the code can exit from longer running code loops if requested by the user. This covers sstate checks and sstate manifest cleanup code which currently couldn't be interrupted by the user from the UI. Increase the minimum bitbake version which brings in

Re: [OE-core] [PATCH 08/11] build-appliance-image: use a real /tmp

2023-02-22 Thread Richard Purdie
On Tue, 2023-02-21 at 21:25 -0500, Trevor Woerner wrote: > On Tue 2023-02-21 @ 03:44:42 PM, Trevor Woerner via lists.openembedded.org > wrote: > > Make /tmp a real directory in the root filesystem and not a link to an > > in-memory tmpfs. Otherwise bitbake will run out of inodes on /tmp very > >

[OE-core] [PATCH] docbook-xml: Switch from debian packages to upstream docbook sources

2023-02-22 Thread Richard Elberger
This patch changes the docbook-xml distribution package source from debian to docbook which aligns the recipe with the source originator. Other changes made to the recipe include: This patch resolves [YOCTO #13270]. - removal of version 4.0 given docbook no longer distributes version 4.0 -

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

2023-02-22 Thread Richard Elberger
Ross, I found the problem. Since I can't build world I will do best effort and build core-image-minimal through. In the patch I with put comment, with additional explanation in the commit message, about the magic variable. In my opinion a couple lines are misplaced but for sake of not causing

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

2023-02-22 Thread Markus Volk
Verified that both ways would work and sent a patch for the second approach. Looks easier for now Am Mi, 22. Feb 2023 um 12:31:26 +0100 schrieb Markus Volk : What would be the preferred way to fix it? I'd prefer the more progressive way and add BBCLASSEXTEND +="nativesdk" to gtk.bb But this

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

2023-02-22 Thread Markus Volk
- Allow to build the gtk4 widget and vapi This is needed to build gtk4 based terminals like blackbox - Update dependencies - Cleanup recipe and remove unneeded patch Signed-off-by: Markus Volk --- ...EXITCODE-macro-for-non-glibc-systems.patch | 42 --- .../vte/{vte_0.70.2.bb

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

2023-02-22 Thread Markus Volk
What would be the preferred way to fix it? I'd prefer the more progressive way and add BBCLASSEXTEND +="nativesdk" to gtk.bb But this would also add the need to build libxkbcommon and xkeyboard-config for nativesdk vte recipe already has a PACKAGECONFIG:remove line, so i guess it will be

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

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

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

2023-02-22 Thread Alexandre Belloni via lists.openembedded.org
Hello, This causes: stdio: WARNING: Nothing PROVIDES 'nativesdk-gtk4' (but virtual:nativesdk:/home/pokybuild/yocto-worker/a-full/build/meta/recipes-support/vte/vte_0.70.3.bb DEPENDS on or otherwise requires it). Close matches: stdio: WARNING: Nothing RPROVIDES 'nativesdk-vte' (but

Re: [OE-core] Cve fetcher update

2023-02-22 Thread Marta Rybczynska
On Tue, Feb 21, 2023 at 2:47 PM Ross Burton wrote: > Hi Marta, > > > On 21 Feb 2023, at 13:20, Marta Rybczynska wrote: > > I'm finishing the new fetcher for cve check using the 2.0 NVD API. Will > need testers to check as many configurations as possible before we switch > the format. > > > >

Re: [OE-core] [kirkstone][PATCH 0/1] Update webkitgtk to 2.38.4 for CVEs

2023-02-22 Thread Alexander Kanavin
The other option is to make a mixin layer, they're meant exactly for backporting version updates that aren't eligible for direct availability. We've done this for pieces like go, docker and the kernel. https://git.yoctoproject.org/meta-lts-mixins/ Alex On Wed, 22 Feb 2023 at 01:59, Kai Kang