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

Final set of changes for dunfell 3.1.2 release. The following changes since commit c2ad3af9da9bb3a98c1d5d1b3d21eb8db643c189: coreutils: don't split stdbuf to own package with single-binary (2020-07-13 17:14:28 -1000) are available in the Git repository at: git://git.openembedded.org/openem

Re: [OE-core] [PATCH] qemurunner: Use tempfile.mkstemp to create pidfile name

On Tue, Jul 21, 2020, 4:56 PM Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > We continue to see qemu races where qemu fails to write out a pidfile. The > pidfile name being used was based on the parent process starting the qemus > so in theory, a qemu shutting down could have delete

[OE-core] [PATCH] site: Make sys_siglist default to no

glibc 2.32 has deprecated sys_siglist [1] since no is default for musl as well, therefore elevate it to common site file for all [1] https://sourceware.org/git/?p=glibc.git;a=commit;h=b1ccfc061feee9ce616444ded8e1cd5acf9fa97f Signed-off-by: Khem Raj --- meta/site/common | 7 +++ meta

[OE-core] [PATCH] qemurunner: Use tempfile.mkstemp to create pidfile name

We continue to see qemu races where qemu fails to write out a pidfile. The pidfile name being used was based on the parent process starting the qemus so in theory, a qemu shutting down could have deleted the file into which the new qemu's pid was about to be written. This shouldn't happen as qemu p

Re: [OE-core] "DEPENDS =" versus "DEPENDS +=" in recipe files

On Tue, Jul 21, 2020 at 2:26 PM Robert P. J. Day wrote: > > pursuant to cleaning up some docs and tweaking the style guide, > i just want to clarify that the *proper* assignment to DEPENDS > in recipe files is: > >DEPENDS = "..." > > unless (of course) that assignment is preceded by a "require

[OE-core] "DEPENDS =" versus "DEPENDS +=" in recipe files

pursuant to cleaning up some docs and tweaking the style guide, i just want to clarify that the *proper* assignment to DEPENDS in recipe files is: DEPENDS = "..." unless (of course) that assignment is preceded by a "require" of a .inc file that assigns to that variable, whereupon the "+=" woul

[OE-core] [dunfell][PATCH v2] busybox: make hwclock compatible with glibc 2.31

settimeofday(2) has been deprecated as of glibc 2.31 which hwclock makes use of. This patch makes hwclock compatible with glibc v2.31 See patch for more details: busybox/0001-hwclock-make-glibc-2.31-compatible.patch Fixes [YOCTO #13981] Signed-off-by: Sakib Sajal --- v2 changes: rebased and te

Re: [OE-core] [dunfell][PATCH] busybox: make hwclock compatible with glibc 2.31

On 2020-07-21 3:01 p.m., Khem Raj wrote: On 7/21/20 11:54 AM, Sakib Sajal wrote: On 2020-07-21 2:11 p.m., Randy MacLeod wrote: Hi Sakib, Did you check this busybox fix against musl? I forgot to ask you this when you showed me this patch yesterday. Randy Yes, I built core-image-minimal

Re: [OE-core] [dunfell][PATCH] busybox: make hwclock compatible with glibc 2.31

On 7/21/20 12:01 PM, Khem Raj wrote: On 7/21/20 11:54 AM, Sakib Sajal wrote: On 2020-07-21 2:11 p.m., Randy MacLeod wrote: Hi Sakib, Did you check this busybox fix against musl? I forgot to ask you this when you showed me this patch yesterday. Randy Yes, I built core-image-minimal wi

Re: [OE-core] [dunfell][PATCH] busybox: make hwclock compatible with glibc 2.31

On 7/21/20 11:54 AM, Sakib Sajal wrote: On 2020-07-21 2:11 p.m., Randy MacLeod wrote: Hi Sakib, Did you check this busybox fix against musl? I forgot to ask you this when you showed me this patch yesterday. Randy Yes, I built core-image-minimal with musl and everything was fine. buil

Re: [OE-core] [dunfell][PATCH] busybox: make hwclock compatible with glibc 2.31

On 2020-07-21 2:11 p.m., Randy MacLeod wrote: Hi Sakib, Did you check this busybox fix against musl? I forgot to ask you this when you showed me this patch yesterday. Randy Yes, I built core-image-minimal with musl and everything was fine. Sakib On Tue., Jul. 21, 2020, 14:01 Sakib Sajal,

[OE-core] ✗ patchtest: failure for busybox: make hwclock compatible with glibc 2.31 (rev2)

== Series Details == Series: busybox: make hwclock compatible with glibc 2.31 (rev2) Revision: 2 URL : https://patchwork.openembedded.org/series/25223/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests h

Re: [OE-core] [dunfell][PATCH] busybox: make hwclock compatible with glibc 2.31

Hi Sakib, Did you check this busybox fix against musl? I forgot to ask you this when you showed me this patch yesterday. Randy On Tue., Jul. 21, 2020, 14:01 Sakib Sajal, wrote: > settimeofday(2) has been deprecated as of glibc 2.31 > which hwclock makes use of. This patch makes hwclock > compa

[OE-core] [dunfell][PATCH] busybox: make hwclock compatible with glibc 2.31

settimeofday(2) has been deprecated as of glibc 2.31 which hwclock makes use of. This patch makes hwclock compatible with glibc v2.31 See patch for more details: busybox/0001-hwclock-make-glibc-2.31-compatible.patch Fixes [YOCTO #13981] Signed-off-by: Sakib Sajal --- ...1-hwclock-make-glibc-2

[OE-core] [PATCH] busybox: make hwclock compatible with glibc 2.31

settimeofday(2) has been deprecated as of glibc 2.31 which hwclock makes use of. This patch makes hwclock compatible with glibc v2.31 See patch for more details: busybox/0001-hwclock-make-glibc-2.31-compatible.patch Fixes [YOCTO #13981] Signed-off-by: Sakib Sajal --- ...1-hwclock-make-glibc-2

[OE-core][PATCH] classes/package: Use HOST_OS for runtime dependencies

The code was using TARGET_OS to try and detect what type of OS the packages would be running on, but this is incorrect. TARGET_OS is the OS for which the package will generate output (e.g. GCC output target or GDB debugging target). The OS where the package will run is the HOST_OS. Note that HOST_O

[OE-core][PATCH] classes/cmake: Fix host detection

Fixes the class to use HOST_OS and HOST_ARCH to set the cmake SYSTEM variables. The HOST variables should be used instead of TARGET_OS/TARGET_ARCH because we want to control how cmake compiles for where the package is going to run (the host), not what it will be generating output for (the target).

Re: [OE-core] [PATCH] gcc: mitigate the Straight-line Speculation attack

Retracting this: v2 coming tomorrow. Ross On Tue, 21 Jul 2020 at 16:46, Ross Burton wrote: > > From: Ross Burton > > Straight-line Speculation is a SPECTRE-like attack on Armv8-A, further > details can be found in the white paper here: > > https://developer.arm.com/support/arm-security-updates/

[OE-core] [PATCH] startup-notification: add time_t type mismatch patch from upstream

From: Ross Burton Backport a patch to fix issues where sizeof(time_t) != sizeof(long). Signed-off-by: Ross Burton --- .../startup-notification-0.12/time_t.patch| 108 ++ .../startup-notification_0.12.bb | 1 + 2 files changed, 109 insertions(+) create mode 1

[OE-core] [PATCH] gcc: mitigate the Straight-line Speculation attack

From: Ross Burton Straight-line Speculation is a SPECTRE-like attack on Armv8-A, further details can be found in the white paper here: https://developer.arm.com/support/arm-security-updates/speculative-processor-vulnerability/downloads/straight-line-speculation Backport the GCC patches to mitig

Re: [OE-core] [PATCH] cve-check.bbclass: always save cve report

On 7/21/20 2:54 AM, Adrian Bunk wrote: > This breaks building the SDK in distributions with INHERIT += "cve-check": > > $ bitbake tmp-sdk -c populate_sdk > ... > NOTE: Tasks Summary: Attempted 2785 tasks of which 2785 didn't need to be > rerun and all succeeded. > ERROR: Execution of event handl

[OE-core] Yocto Project Status WW29'20

Current Dev Position: YP 3.2 M2 Next Deadline: YP 3.2 M2 build date 2020/7/27 Next Team Meetings: * Bug Triage meeting Thursday July 23th at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday Aug. 4th at 8am PDT (

Re: [OE-core] [PATCH] python3-numpy: Stop shipping manual config files

Hi Armin, Anuj, Adrian, On 27.10.19 18:36, Adrian Bunk wrote: Automatic generation seems to work fine, and does not become outdated. Signed-off-by: Adrian Bunk Can you confirm this will also work on zeus, or does zeus miss some other patches this depends on? If possible, can you please qu

Re: [OE-core] [PATCH] cve-check.bbclass: always save cve report

This breaks building the SDK in distributions with INHERIT += "cve-check": $ bitbake tmp-sdk -c populate_sdk ... NOTE: Tasks Summary: Attempted 2785 tasks of which 2785 didn't need to be rerun and all succeeded. ERROR: Execution of event handler 'cve_save_summary_handler' failed Traceback (most r

Re: [OE-core] [bitbake-devel] [yocto] Stable Warrior branch

On Tue, 2020-07-14 at 16:56 +0300, Adrian Bunk wrote: > On Thu, Jun 04, 2020 at 09:28:00PM -0700, akuster wrote: > > Hello, > > > > The Warrior branch of Poky has had its last official dot release. > > It > > will be moving to Community support and EOL within 6 weeks if no > > one > > steps up. >