[yocto] [meta-security][PATCH] sssd: disable build secrets

From: Kai Kang It requires http_parser.h to build secrets: | configure: error: | You must have the header file http_parser.h installed to build sssd | with secrets responder. If you want to build sssd without secret responder | then specify --without-secrets when running configure. The header

Re: [yocto][meta-virtualization][zeus][PATCH] kubernetes: CVE-2020-8555

Can you confirm that the k8s versions in master/dunfell don't have this CVE ? Bruce In message: [yocto][meta-virtualization][zeus][PATCH] kubernetes: CVE-2020-8555 on 15/06/2020 Zhixiong Chi wrote: > Backport the CVE patch from the upstream: > https://github.com/kubernetes/kubernetes.git > >

Re: [yocto] Go toolchain in SDK

On 16/06/2020 23:55, Robert Berger via lists.yoctoproject.org wrote: bitbake core-image-sato-sdk -c populate_sdk and currently also for: bitbake core-image-sato-sdk -c populate_sdk_ext ... and no arm-resy-linux-gnueabi-go on the target, only on the host SDK I don't think that's the way it

Re: [yocto] [meta-mingw]: Static libraries

I see. Now, I can tell that you can add manually curl-staticdev to the target. Or it also gets deployed with the SDKIMAGE_FEATURES. But not for libgcc, because libgcc-staticdev package does not exist, and that's why SDKIMAGE_FEATURES couldn't deploy it. I know this now. The way meta-mingw manage

[yocto] Go toolchain in SDK

Hi, What is the "proper" way to add the Go toolchain to an SDK nowadays (dunfell)? I saw there is in poky: ./meta/recipes-core/meta/meta-go-toolchain.bb but I am not quite sure how to build an SDK with meta-go-toolchain included. so I added something like that to local.conf which seems to

Re: [yocto] [meta-mingw]: Static libraries

Please "Reply-All" to keep the discussion on the mailing list On 6/16/20 1:05 PM, Edgar Chaves wrote: Hi, do you have thoughts about this? My concern is that *-staticdev part of nativesdk-* providers is not deployed correctly. nativesdk-*-staticdev packages shouldn't be included in the

[yocto] easiest way to enumerate DEPENDS/RDEPENDS for new python3 recipes?

apparently, i and a couple other people are responsible for whipping up a bunch of python3 recipes that currently do not exist; we're going to standardize on what seems to be the most popular format -- recipes that inherit both "pypi" and "setuptools3", which make the recipes pretty

Re: [linux-yocto] kernel-debuginfo

On Tue, Jun 16, 2020 at 10:02 AM Michael wrote: > > Thank you for a quick respond Bruce. > > > __ > > On Mon, Jun 15, 2020 at 5:37 PM Michael wrote: > >> > >> Hello all. > >> > >> I'm creating a yocto Warrior branch project to a fakeroot for powerpc > >> embedded system to

[yocto] Yocto Project Status WW24'20

Current Dev Position: YP 3.2 M1 Next Deadline: YP 3.2 M1 build date 2020/6/16 Next Team Meetings: * Bug Triage meeting Thursday June 18th at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday July 7th at 8am PDT (

Re: [linux-yocto] kernel-debuginfo

On Mon, Jun 15, 2020 at 5:37 PM Michael wrote: > > Hello all. > > I'm creating a yocto Warrior branch project to a fakeroot for powerpc > embedded system to replace my old non yocto project. I setup the yocto > project to use kernel 4.19.x. My old build used kernel 3.10.xx and hd >

Re: [yocto] [PATCH yocto-autobuilder-helper] config.json: generate the buildtools tarballs for aarch64

On Mon, 15 Jun 2020 at 17:46, Alexander Kanavin wrote: > > On Mon, 15 Jun 2020 at 15:50, Ross Burton wrote: >> >> From: Ross Burton > > > > >> >> "SDKMACHINE" : "aarch64", >> -"BBTARGETS" : "uninative-tarball" >> +