[OE-core] [PATCH 1/3] linux-yocto: introduce 5.4 recipes

From: Bruce Ashfield This creates recipes for the v5.4/* branches of the linux-yocto reference kernel. preempt-rt, yaffs2, aufs5 and reference board specific patches are part of these branches. All major architectures: x86,x86-64,ARM, ARM64,ppc,mips and mips64 have been feature tested against

[OE-core] [PATCH 2/3] kern-tools: update Kconfiglib to latest (for 5.4+ kernel)

From: Bruce Ashfield When a symbol doesn't make it into the final analysis is run using Kconfiglib to show dependencies. v5.4 has introduced Kconfig elements that Kconfiglib can't parse (hence we get no analysis). Updating the Kconfiglib snapshot solves our problem. Signed-off-by: Bruce

[OE-core] [PATCH 0/3][RFT]: kernel-yocto: v5.4 LTS kernel

From: Bruce Ashfield Hi all, I just wanted to send these to the list, so everyone could see the reference kernel that we are planning for the upcoming release. I have other patches to drop 4.19, 5.2 and make this the default kernel for the various reference platforms as well, but I'm not

[OE-core] [PATCH 3/3] kernel-devsrc: update to v5.4+

From: Bruce Ashfield To support on-target module building, we need to include syscall.tbl for ARM64 (just like we do for other architectures). We also copy .config with -a to ensure that we don't trigger extra processing and regen configs. Signed-off-by: Bruce Ashfield Signed-off-by: Bruce

[OE-core] [PATCH] systemd: Refresh the patches

Fixes WARNING: systemd-1_243.4+gitAUTOINC+70e8c1978a-r0 do_patch: Fuzz detected: Applying patch 0001-do-not-disable-buffer-in-writing-files.patch ... QA Issue: Patch log indicates that patches do not apply cleanly. [patch-fuzz] Signed-off-by: Khem Raj ---

Re: [OE-core] [OE-Core][PATCH] libxcrypt: Enable static builds

On Tue, Jan 28, 2020 at 4:48 AM Alex Kiernan wrote: > > Let me have a look at that - what got me here was trying to get a > static busybox so I could OSTree's tests to pass, which all turned out > to be way harder than I expected; this was just one of the things I > tripped over. Busybox

[OE-core] ✗ patchtest: failure for socklog: Disable the chkshsgr tests

== Series Details == Series: socklog: Disable the chkshsgr tests Revision: 1 URL : https://patchwork.openembedded.org/series/22332/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed

[OE-core] [PATCH] socklog: Disable the chkshsgr tests

Running the chkhsgr test during cross compile fails ./chkshsgr || ( cat warn-shsgr; exit 1 ) Oops. Your getgroups() returned 0, and setgroups() failed; this means that I can't reliably do my shsgr test. Please either ``make'' as root or ``make'' while you're in one or more supplementary groups.

Re: [OE-core] [PATCH 06/13] glibc: Update to final 2.31 release

On Tue, Jan 28, 2020 at 11:00 AM Alexander Kanavin wrote: > > Sure, and testing prior to actual releases is very beneficial and > appreciated. I only wanted to make sure we don't tag something as 2.31 final > when it's still a pre-release. > yes we wont :) > Alex > > On Tue, 28 Jan 2020 at

Re: [OE-core] [PATCH 06/13] glibc: Update to final 2.31 release

Sure, and testing prior to actual releases is very beneficial and appreciated. I only wanted to make sure we don't tag something as 2.31 final when it's still a pre-release. Alex On Tue, 28 Jan 2020 at 19:45, Khem Raj wrote: > On Tue, Jan 28, 2020 at 9:48 AM Alexander Kanavin > wrote: > > > >

Re: [OE-core] [PATCH 06/13] glibc: Update to final 2.31 release

On Tue, Jan 28, 2020 at 9:48 AM Alexander Kanavin wrote: > > But 2.31 hasn't yet been released or tagged? > No, it will be released first week of February, given how much work is required for upgrading some of these core pieces, getting some early testing and reporting any regressions and

[OE-core] [PATCH] gcc-cross-canadian: A missing space in an append caused an invalid option

When configuring the cross-candian toolchain for a non-linux target system, the resulting gcc configuration included: --enable-initfini-array--without-headers these should have been two separate options. Signed-off-by: Mark Hatle --- meta/recipes-devtools/gcc/gcc-cross-canadian.inc | 4 ++--

Re: [OE-core] [PATCH 2/2] libgcc.inc: Fix an issue w/ a recursive symlink

On 1/22/20 12:48 AM, Khem Raj wrote: > On Tue, Jan 21, 2020 at 4:43 PM Mark Hatle > wrote: >> >> From: Mark Hatle >> >> If the OS is not Linux, the code could end up generating a recursive symlink. >> This can happen because the same symlink can be created twice in a row. If >> this >>

Re: [OE-core] [PATCH 1/2] toaster.bbclass: Fix error when toaster is used to monitor a build

Ping. On 1/21/20 6:27 PM, Mark Hatle wrote: > The error being corrected looks like: > > File: > '/home/jenkins/workspace/OEBuild/build-32/oe-core/meta/classes/toaster.bbclass', > lineno: 130, function: toaster_package_dumpdata > 0126:lpkgdata = {} > 0127:datadir =

Re: [OE-core] [PATCH 06/13] glibc: Update to final 2.31 release

But 2.31 hasn't yet been released or tagged? http://sourceware.org/git/?p=glibc.git Alex On Tue, 28 Jan 2020 at 17:06, Khem Raj wrote: > > > On Tue, Jan 28, 2020 at 3:02 AM Martin Jansa > wrote: > >> On Sun, Jan 26, 2020 at 11:27:43AM -0800, Khem Raj wrote: >> > Drop ppc 8xx clear cache

Re: [OE-core] [PATCH 1/5] bc: Use texinfo class

On Tue, 2020-01-28 at 16:58 +0100, Jacob Kroon wrote: > On 1/28/20 4:16 PM, Richard Purdie wrote: > > This recipe uses makeinfo so inherit the class which can provide > > it. > > > > Signed-off-by: Richard Purdie > > --- > > meta/recipes-extended/bc/bc_1.07.1.bb | 2 +- > > 1 file changed, 1

Re: [OE-core] [PATCH v2] valgrind: Fix ptest builds on musl

On Tue, Jan 28, 2020 at 2:07 AM Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > On Tue, 2020-01-28 at 09:09 +0100, Alexander Kanavin wrote: > > The reason I dropped the previous version of this is that with the > > patch the test failed, without the patch it passed. If you can > >

Re: [OE-core] [PATCH 06/13] glibc: Update to final 2.31 release

On Tue, Jan 28, 2020 at 3:02 AM Martin Jansa wrote: > On Sun, Jan 26, 2020 at 11:27:43AM -0800, Khem Raj wrote: > > Drop ppc 8xx clear cache optimization, which we have been carrying > > through eglibc days, it has been redone in glibc now > > > > Signed-off-by: Khem Raj > > --- > >

[OE-core] Yocto Project Status WW04'20

Current Dev Position: YP 3.1 M3 Next Deadline: YP 3.1 M2 in QA - release 1/31/20 Next Team Meetings: * Bug Triage meeting Thursday Jan. 30th at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday Feb. 4th at 8am PDT (

Re: [OE-core] [PATCH 1/5] bc: Use texinfo class

On 1/28/20 4:16 PM, Richard Purdie wrote: This recipe uses makeinfo so inherit the class which can provide it. Signed-off-by: Richard Purdie --- meta/recipes-extended/bc/bc_1.07.1.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-extended/bc/bc_1.07.1.bb

[OE-core] [PATCH 4/5] texinfo: Only build texinfo when api-docs enabled

Also fix the crosssdk and cross-canadian cases. Signed-off-by: Richard Purdie --- meta/classes/texinfo.bbclass | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/meta/classes/texinfo.bbclass b/meta/classes/texinfo.bbclass index 72091c733e5..ba1dd4994e1 100644 ---

[OE-core] [PATCH 1/5] bc: Use texinfo class

This recipe uses makeinfo so inherit the class which can provide it. Signed-off-by: Richard Purdie --- meta/recipes-extended/bc/bc_1.07.1.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-extended/bc/bc_1.07.1.bb b/meta/recipes-extended/bc/bc_1.07.1.bb index

[OE-core] [PATCH 3/5] texinfo/texinfo-dummy-native: Drop native path prefix

Now we have recipe specific sysroots we don't need this native path prefix. It was breaking the crosssdk/cross-canadian cases and causing bugs, removing it is the simplest solution. Signed-off-by: Richard Purdie --- meta/classes/texinfo.bbclass | 4 +---

[OE-core] [PATCH 2/5] glibc-package.inc: Remove warnings about unpacked directories

If documemtation generation is disabled, the recipe throws warnings about unpackaged files. Avoid this. Signed-off-by: Richard Purdie --- meta/recipes-core/glibc/glibc-package.inc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-core/glibc/glibc-package.inc

[OE-core] [PATCH 5/5] bitbake.conf/sanity: Drop makeinfo as being required on buildhost

This is a long standing 'odd' dependency which we've meant to resolve. We shouldn't need it and it introduces reproducability issues. We already have texinfo-dummy-native and texinfo-native which can provide it but the work to remove the hosttool was never completed. After cleaning up

Re: [OE-core] [OE-Core][PATCH] libxcrypt: Enable static builds

On Tue, Jan 28, 2020 at 12:02 PM Richard Purdie wrote: > > On Wed, 2020-01-22 at 07:19 +, Alex Kiernan wrote: > > Whilst glibc builds static binaries libxcrypt doesn't, without which > > we > > can't build, for example, a static busybox. Enable static libraries > > here > > so that anyone who

Re: [OE-core] [OE-Core][PATCH] libxcrypt: Enable static builds

On Wed, 2020-01-22 at 07:19 +, Alex Kiernan wrote: > Whilst glibc builds static binaries libxcrypt doesn't, without which > we > can't build, for example, a static busybox. Enable static libraries > here > so that anyone who needs a static binary using just basic libraries > has > one fewer

Re: [OE-core] Could oe-core be infected by virus?

On Tue, 2020-01-28 at 21:56 +1100, JH wrote: > I don't have Bluetooth, I don't need RPC, etc., yet the kernel > initialized all those processes I have never defined and I don't > need. > Where those things defined to let the kernel to initialize them in > boot process? > > It is a small resource

Re: [OE-core] [PATCH 06/13] glibc: Update to final 2.31 release

On Sun, Jan 26, 2020 at 11:27:43AM -0800, Khem Raj wrote: > Drop ppc 8xx clear cache optimization, which we have been carrying > through eglibc days, it has been redone in glibc now > > Signed-off-by: Khem Raj > --- > .../glibc/cross-localedef-native_2.31.bb | 9 +- >

Re: [OE-core] Could oe-core be infected by virus?

Hi, I don't have Bluetooth, I don't need RPC, etc., yet the kernel initialized all those processes I have never defined and I don't need. Where those things defined to let the kernel to initialize them in boot process? It is a small resource device, how can I get rid of those things I don't

Re: [OE-core] [PATCH v2] valgrind: Fix ptest builds on musl

On Tue, 2020-01-28 at 09:09 +0100, Alexander Kanavin wrote: > The reason I dropped the previous version of this is that with the > patch the test failed, without the patch it passed. If you can > confirm that the new version doesn’t regress the test I would > appreciate. You can edit run-ptest

Re: [OE-core] [PATCH v2] valgrind: Fix ptest builds on musl

The reason I dropped the previous version of this is that with the patch the test failed, without the patch it passed. If you can confirm that the new version doesn’t regress the test I would appreciate. You can edit run-ptest prior to running it to include only the test suite with this test to