[OE-core] [PATCH] removing PN from BB_HASH_CODEPARSER_VALS

2023-09-14 Thread Matthias Schoepfer via lists.openembedded.org
When using icecc.bbclass for builds, the build will break due to the fact, that during parsing stage, PN is set to no-pn, which leads to the issue that the ICECC_RECIPE_DISABLE recipes (appended or within icecc.bbclass) are no longer parsed / ignored correctly. This will lead to an error. Unfortun

Re: [OE-core] [meta-oe][PATCH 3/4] libgcrypt: made libgcrypt-lic license "GPLv2+ & LGPLv2.1+"

2020-07-08 Thread Matthias Schoepfer via lists.openembedded.org
Hi Richard, thanks, that does help maybe a little. Personally, I find the license / compliance topic one of the most annoying things in embedded development *by far*. I also wonder, why nobody else has stumbled across this, since I guess it is quite common to rule out GPLv3, because most proje

Re: [OE-core] [meta-oe][PATCH 3/4] libgcrypt: made libgcrypt-lic license "GPLv2+ & LGPLv2.1+"

2020-07-06 Thread Matthias Schoepfer via lists.openembedded.org
Hi Richard, On 5/26/20 1:37 PM, Richard Purdie wrote: I think we need to be really clear about what the license of ${PN}-lic means. That leads to a really good question, which license is the license text itself under? I've asked this on our licensing list to see if anyone knows. Cheers, Rich

Re: [OE-core] [meta-oe][PATCH 3/4] libgcrypt: made libgcrypt-lic license "GPLv2+ & LGPLv2.1+"

2020-05-26 Thread Matthias Schoepfer via lists.openembedded.org
Hi Richard, On 5/26/20 10:19 AM, Richard Purdie wrote: On Tue, 2020-05-26 at 10:12 +0200, Matthias Schoepfer via lists.openembedded.org wrote: From: Matthias Schoepfer With the exception of dumpsexp.c, which is GPLv3, all other parts of libgcrypt are GPLv2+ & LGPLv2.1+, BSD or MIT or o

[OE-core] [meta-oe][PATCH 4/4] libksba: made libksba-lic "GPLv2+ | LGPLv3+"

2020-05-26 Thread Matthias Schoepfer via lists.openembedded.org
From: Matthias Schoepfer If not set manually to "GPLv2+ | LGPLv3+", install of non GPLv3 parts (the library in this case) will be prevented in a setup that has INCOMPATIBLE_LICENSE = "GPLv3 LGPLv3 GPLv3+ LGPLv3+ GPL-3.0 LGPL-3.0 AGPL-3.0" COPY_LIC_MANIFEST = "1" COPY_LIC_DIRS = "1" LICENSE_CREAT

[OE-core] [meta-oe][PATCH 3/4] libgcrypt: made libgcrypt-lic license "GPLv2+ & LGPLv2.1+"

2020-05-26 Thread Matthias Schoepfer via lists.openembedded.org
From: Matthias Schoepfer With the exception of dumpsexp.c, which is GPLv3, all other parts of libgcrypt are GPLv2+ & LGPLv2.1+, BSD or MIT or other "permissive" licenses. If libgcrypt-lic is not set to "GPLv2+ & LGPLv2.1+", image creation will fail with settings like INCOMPATIBLE_LICENSE = "GPL

[OE-core] [meta-oe][PATCH 2/4] elfutils: made elfutils-lic "GPLv2 | LGPLv3+"

2020-05-26 Thread Matthias Schoepfer via lists.openembedded.org
From: Matthias Schoepfer If not set manually to "GPLv2 | LGPLv3+", install of non GPLv3 parts of elfutils will be prevented in a setup that has INCOMPATIBLE_LICENSE = "GPLv3 LGPLv3 GPLv3+ LGPLv3+ GPL-3.0 LGPL-3.0 AGPL-3.0" COPY_LIC_MANIFEST = "1" COPY_LIC_DIRS = "1" LICENSE_CREATE_PACKAGE = "1"

[OE-core] [meta-oe][PATCH 1/4] libgcc: made libgcc-lic "GPL-3.0-with-GCC-exception"

2020-05-26 Thread Matthias Schoepfer via lists.openembedded.org
From: Matthias Schoepfer libgcc LICENSE_${PN} is "GPL-3.0-with-GCC-exception". If libgcc-lic is not also set to the same license, creating of image with INCOMPATIBLE_LICENSE = "GPLv3 LGPLv3 GPLv3+ LGPLv3+ GPL-3.0 LGPL-3.0 AGPL-3.0" COPY_LIC_MANIFEST = "1" COPY_LIC_DIRS = "1" LICENSE_CREATE_PACKA

Re: [OE-core] [PATCH v2] python3: fixing bpo-36852 patch for builds on i686 architecture

2020-03-30 Thread Matthias Schoepfer via Lists.Openembedded.Org
added to the recipe (please test the build after you do that). Alex On Mon, 30 Mar 2020 at 11:41, Matthias Schoepfer via Lists.Openembedded.Org <http://Lists.Openembedded.Org> <mailto:googlemail@lists.openembedded.org>> wrote: From: Matthias Schoepfer mailto:

[OE-core] [PATCH v2] python3: fixing bpo-36852 patch for builds on i686 architecture

2020-03-30 Thread Matthias Schoepfer via Lists.Openembedded.Org
From: Matthias Schoepfer The original patch "bpo-36852: proper detection of mips architecture for soft float" uses AC_CANONICAL_TARGET to determine the platform triplet. While AC_CANONICAL_TARGET exports i686 as target_cpu, gcc is using i386 instead. We fall back here to i386, as it is conform to

[OE-core] [PATCH] python3: fixing bpo-36852 patch for builds on i686 architecture

2020-03-27 Thread Matthias Schoepfer via Lists.Openembedded.Org
From: Matthias Schoepfer The original patch "bpo-36852: proper detection of mips architecture for soft float" uses AC_CANONICAL_TARGET to determine the platform triplet. While AC_CANONICAL_TARGET exports i686 as target_cpu, gcc is using i386 instead. We fall back here to i386, as it is conform to