Re: [OE-core] [PATCH] libjpeg-turbo: fix do_compile error on armv5

On 6/9/21 10:49 AM, Khem Raj wrote: [Please note: This e-mail is from an EXTERNAL e-mail address] On Tue, Jun 8, 2021 at 7:37 PM Changqing Li wrote: From: Changqing Li fix below error: /include/arm_neon.h:31:2: error: #error "NEON intrinsics not available with the soft-float ABI. Please

Re: [OE-core] [PATCH] libjpeg-turbo: fix do_compile error on armv5

On Tue, Jun 8, 2021 at 7:37 PM Changqing Li wrote: > > From: Changqing Li > > fix below error: > /include/arm_neon.h:31:2: error: #error "NEON intrinsics not available with > the soft-float ABI. Please use -mfloat-abi=softfp or -mfloat-abi=hard" > 31 | #error "NEON intrinsics not available with

[OE-core] [PATCH] libjpeg-turbo: fix do_compile error on armv5

From: Changqing Li fix below error: /include/arm_neon.h:31:2: error: #error "NEON intrinsics not available with the soft-float ABI. Please use -mfloat-abi=softfp or -mfloat-abi=hard" 31 | #error "NEON intrinsics not available with the soft-float ABI. Please use -mfloat-abi=softfp or

[OE-core][PATCH] README.skeleton: add readme to meta-skeleton layer

Added to satisfy the yocto-check-layer tool readme file test. [YOCTO #13612] Signed-off-by: Scott Weaver --- meta-skeleton/README.skeleton | 7 +++ 1 file changed, 7 insertions(+) create mode 100644 meta-skeleton/README.skeleton diff --git a/meta-skeleton/README.skeleton

[OE-core] [PATCH] ffmpeg: Link in libatomic on riscv32

It needs some functions from libatomic e.g. libavformat/libavformat.so: undefined reference to `__atomic_fetch_sub_8' Signed-off-by: Khem Raj --- meta/recipes-multimedia/ffmpeg/ffmpeg_4.4.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/recipes-multimedia/ffmpeg/ffmpeg_4.4.bb

Re: [OE-core] [PATCH 04/10] cmake: update 3.20.2 -> 3.20.3

I can confirm that the previous kernel behaves correctly: utimensat_time64(AT_FDCWD, "../install/usr/local/lib/cmake/assimp-4.1/assimp-config.cmake", [{tv_sec=1623176017, tv_nsec=6290007298941124608}, {tv_sec=1622966579, tv_nsec=17838646317425885184}], 0) = -1 ENOSYS (Function not implemented)

Re: [OE-core] [PATCH] lib: oe: utils: always append host gcc version to NATIVELSBSTRING

On Tue, Jun 8, 2021 at 7:16 AM Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > > > There were specific issues with gcc 4.8 and 4.9 which required > separate sstate. Do we > > > know which gcc version switched the default and can we force older > gcc's to use the > > > same default

Re: [OE-core] [PATCH 04/10] cmake: update 3.20.2 -> 3.20.3

I've rebooted centos8-ty-1 using the previous 4.18.0-240.15.1.el8_3.x86_64 kernel and kept it in the pool. I've paused centos8-ty-2 so it won't interfere with builds and left it at the current 4.18.0-305.3.1.el8.x86_64 kernel for testing. On Mon, Jun 7, 2021 at 11:04 AM Alexander Kanavin wrote:

[OE-core] [PATCH] oeqa/core/target/qemu.py: display contents of dumped files

During do_testimage, if the target is not started within a certain timeout, TEST_QEMUBOOT_TIMEOUT, host data is dumped to files for each command in ${TMPDIR}/log/runtime-hostdump/_qemu/host__. Display the first 20 lines of top output and the last 20 lines of bootlog to standard output for more

[OE-core] openSUSE 15.2 support on dunfell

I'd like to work toward getting openSUSE 15.2 as a supported distro for the next dunfell release (3.1.9). Initial autobuilder testing looks fairly good, but I'd like to get some feedback from people who are already doing dunfell builds on openSUSE 15.2. Have you run into any issues? If

[OE-core][dunfell 5/6] kernel-fitimage: Don't use unit addresses on FIT

From: Klaus Heinrich Kiwi Das U-Boot 2021.4-rc1 has the following commit: commit 3f04db891a353f4b127ed57279279f851c6b4917 Author: Simon Glass Date: Mon Feb 15 17:08:12 2021 -0700 image: Check for unit addresses in FITs Using unit addresses in a FIT is a security

[OE-core][dunfell 4/6] linux-yocto/5.4: update to v5.4.123

From: Bruce Ashfield Updating linux-yocto/5.4 to the latest korg -stable release that comprises the following commits: 103f1dbea1ae Linux 5.4.123 af2a4426baf7 NFC: nci: fix memory leak in nci_allocate_device 45aef101ca44 perf unwind: Set userdata for all __report_module() paths

[OE-core][dunfell 6/6] kernel-devicetree: Introduce KERNEL_DTC_FLAGS to pass dtc flags

From: Ovidiu Panait Currently DTC_FLAGS kernel makefile parameter can be specified directly on the command line by adding it to KERNEL_EXTRA_ARGS. However, this prevents scripts/Makefile.lib logic from appending flags that silence dtc warnings (all assignments done from within a makefile, to a

[OE-core][dunfell 3/6] linux-yocto/5.4: update to v5.4.120

From: Bruce Ashfield Updating linux-yocto/5.4 to the latest korg -stable release that comprises the following commits: e05d387ba736 Linux 5.4.120 7f4ac21468b0 ASoC: rsnd: check all BUSIF status when error 7f6a9044ff24 nvme: do not try to reconfigure APST when the controller is not

[OE-core][dunfell 2/6] gnutls: fix CVE-2021-20231 CVE-2021-20232

From: Lee Chee Yang Signed-off-by: Lee Chee Yang Signed-off-by: Steve Sakoman --- .../gnutls/gnutls/CVE-2021-20231.patch| 67 +++ .../gnutls/gnutls/CVE-2021-20232.patch| 65 ++ meta/recipes-support/gnutls/gnutls_3.6.14.bb | 2 + 3 files

[OE-core][dunfell 1/6] libxml: fix CVE-2021-3517 CVE-2021-3537

From: Lee Chee Yang Signed-off-by: Lee Chee Yang Signed-off-by: Steve Sakoman --- .../libxml/libxml2/CVE-2021-3517.patch| 53 +++ .../libxml/libxml2/CVE-2021-3537.patch| 50 + meta/recipes-core/libxml/libxml2_2.9.10.bb| 2 + 3 files

[OE-core][dunfell 0/6] Patch review

Please review this next set of patches for dunfell and have comments back by end of day Thursday. Passed a-full on autobuilder: https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/2220 The following changes since commit 090452c5284181f18c32dc33887f4dda20c48004: Revert "busybox:

[OE-core] Yocto Project Status WW23`21

Current Dev Position: YP 3.4 M1 Next Deadline: 7th June 2021 YP 3.4 M1 build Next Team Meetings: * Bug Triage meeting Thursday June 10th at 7:30am PDT ( https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)

Re: [OE-core][dunfell 0/1] Pull request (cover letter only)

Steve, Em ter., 8 de jun. de 2021 às 11:37, Steve Sakoman escreveu: > > This reverts commit e990a9ec5d6eaf2c328d61c4de73ea6c270cfa15. > > Patch not in master, erroneously applied > > The following changes since commit b48cfe9148e8f9bbc942899455215e8f9c8e2728: > > linux-firmware: upgrade

[OE-core][dunfell 0/1] Pull request (cover letter only)

This reverts commit e990a9ec5d6eaf2c328d61c4de73ea6c270cfa15. Patch not in master, erroneously applied The following changes since commit b48cfe9148e8f9bbc942899455215e8f9c8e2728: linux-firmware: upgrade 20210315 -> 20210511 (2021-05-31 05:30:56 -1000) are available in the Git repository at:

Re: [OE-core] [PATCH] lib: oe: utils: always append host gcc version to NATIVELSBSTRING

On Mon, 2021-06-07 at 18:49 -0400, Kyle Russell wrote: > On Mon, Jun 7, 2021 at 5:43 PM Richard Purdie > wrote: > > > > https://bugzilla.yoctoproject.org/show_bug.cgi?id=10441 > > > > This doesn't look quite right? > > > > > Yes, that's the one.  I assumed this was what you meant by,

Re: [OE-core] [PATCH] lib: oe: utils: always append host gcc version to NATIVELSBSTRING

On Tue, Jun 8, 2021 at 11:48 AM Richard Purdie wrote: > > On Tue, 2021-06-08 at 11:20 +0200, Andrea Adami wrote: > > On Tue, Jun 8, 2021 at 12:02 AM Phil Blundell via > > lists.openembedded.org wrote: > > > > > > Wouldn't it be easier to just force -fPIE on for those users for whom > > > this

Re: [OE-core] [PATCH] lib: oe: utils: always append host gcc version to NATIVELSBSTRING

On Tue, 2021-06-08 at 11:20 +0200, Andrea Adami wrote: > On Tue, Jun 8, 2021 at 12:02 AM Phil Blundell via > lists.openembedded.org wrote: > > > > Wouldn't it be easier to just force -fPIE on for those users for whom this > > is a problem? Or force -fPIE off for native everywhere. I'm not sure

Re: [OE-core] [PATCH] lib: oe: utils: always append host gcc version to NATIVELSBSTRING

On Tue, Jun 8, 2021 at 12:02 AM Phil Blundell via lists.openembedded.org wrote: > > Wouldn't it be easier to just force -fPIE on for those users for whom this is > a problem? Or force -fPIE off for native everywhere. I'm not sure that doing > something based on GCC version is obviously the

[OE-core] [PATCH] valgrind: fix a typo

From: Kai Kang Signed-off-by: Kai Kang --- meta/recipes-devtools/valgrind/valgrind_3.17.0.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-devtools/valgrind/valgrind_3.17.0.bb b/meta/recipes-devtools/valgrind/valgrind_3.17.0.bb index d0c60d0a3d..7fcb086789