[OE-core] [PATCH] linux-firmware: package all ibt-17-x-x.sfi/ddc firmware

All ibt-17-x-x.sfi/ddc firmware are use to support Intel Bluetooth 9560 they are needed in different version of Bluetooth driver since 4.14 kernel version. commit b77bb7afe513 ("linux-firmware: package ibt-17-16-1 firmware") only package one of the ibt-17 series firmware. As the Bluetooth

[OE-core] [PATCH V3] pigz: 2.3.4 -> 2.4

License-checksum-change: license is no change, only version bump up. https://github.com/madler/pigz/commit/fe822cb435622c43f491013da77b127e9fe851a9 Signed-off-by: Hongxu Jia --- meta/recipes-extended/pigz/{pigz_2.3.4.bb => pigz_2.4.bb} | 6 +++--- 1 file changed, 3

[OE-core] [PATCH V2] gpgme: 1.9.0 -> 1.10.0

1. Disable test at build time to workaround corss-compile Add 0007 to add option to disable python test and submit it to upstream 2. Rework patch 0002, since the following commit of upstream.

Re: [OE-core] [PATCH 2/7] pigz: 2.3.4 -> 2.4

On 2018-01-31 03:27 AM, Alexander Kanavin wrote: You need to mention this in the commit message. Also explain why the md5sum for LIC_FILES_CHKSUM changed in the commit log. ../Randy I still wonder why patchtest won't tell that anymore; we changed it to look for a tag, and somehow that

Re: [OE-core] [PATCH 4/7] gpgme: 1.9.0 -> 1.10.0

On 2018年01月31日 21:27, Alexander Kanavin wrote: On 01/31/2018 02:28 PM, Burton, Ross wrote: On 31 January 2018 at 07:48, Hongxu Jia > wrote:     1. Disable test at build time to workaround corss-compile Looks like more tests need to

Re: [OE-core] [PATCH] core-image-minimal-initramfs: use initramfs-framework for initialization

Ping. --- Cal On 01/09/2018 05:00 PM, Cal Sullivan wrote: Anything wrong with this? Haven't seen it hit any mut branches. Thanks, Cal On 12/19/2017 02:12 PM, California Sullivan wrote: initramfs-framework is more modular and expandable. This change was proposed in commit

[OE-core] [oe-core][PATCH v2] waf.bbclass: cd to ${S} before checking version

waf requires that the current working directory be the project root (in this case ${S} when it is invoked. The check to get the waf version was being executed as a prefunc for do_configure, which meant it was executed before the current working directory was switched to ${S}, and thus would fail

[OE-core] [PATCH 1/1] devtool: set up git repos so that singletask.lock is ignored

singletask.lock is written out while certain tasks execute for recipes that have externalsrc.bbclass enabled - this includes recipes in devtool's workspace. It appears that there's a race where singletask.lock will be there one minute and then when we try to get the file checksum of it (since we

[OE-core] [PATCH 0/1] devtool: set up git repos so that singletask.lock is ignored

The following changes since commit a0988c3374e964170d1d24fc230306b887432d31: tcmode-default.inc: drop preferred version of gzip-native (2018-01-31 17:01:12 +) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib paule/devtool-singletask-lock-fix

Re: [OE-core] [PATCH] ninja: Upgrade from 1.7.2 to major release 1.8.2

Sure, sorry for some reason I sent it to oe-core-bounce or something last week. Interestingly I just rebased it on master cleanly... On 01/31/2018 03:57 AM, Burton, Ross wrote: Patch doesn't apply, can you rebase and resend please. Ross On 30 January 2018 at 21:09, Alejandro Enedino

[OE-core] [morty][PATCH] buildstats.bbclass: Avoid index exception in /proc/PID/io parsing

From: Pavel Modilaynen There is some probability (depends on system load) to get empty or line containing "0" as the last line while reading /proc/PID/io. Avoid build failure by checking if line contains separator ":" before split. Backport from pyro commit

Re: [OE-core] [PATCHv2] security_flags.inc: Use SECURITY_X_LDFLAGS for all xf86 modules

On Wed, Jan 31, 2018 at 9:47 AM, Tom Rini wrote: > We need to ensure that all xorg modules are linked with > SECURITY_X_LDFLAGS to ensure that they will be able to resolve their run > time dependencies. Update the current list of recipes and add a comment > for future

[OE-core] [PATCHv2] security_flags.inc: Use SECURITY_X_LDFLAGS for all xf86 modules

We need to ensure that all xorg modules are linked with SECURITY_X_LDFLAGS to ensure that they will be able to resolve their run time dependencies. Update the current list of recipes and add a comment for future reference. Cc: Khem Raj Signed-off-by: Tom Rini

Re: [OE-core] [PATCH] security_flags.inc: Use SECURITY_X_LDFLAGS

On Wed, Jan 31, 2018 at 12:37:57PM -0500, Tom Rini wrote: > We need to ensure that all xorg modules are linked with > SECURITY_X_LDFLAGS to ensure that they will be able to resolve their run > time dependencies. Replace the incomplete list here with globs for both > video and input modules. > >

[OE-core] [PATCH] security_flags.inc: Use SECURITY_X_LDFLAGS

We need to ensure that all xorg modules are linked with SECURITY_X_LDFLAGS to ensure that they will be able to resolve their run time dependencies. Replace the incomplete list here with globs for both video and input modules. Cc: Khem Raj Signed-off-by: Tom Rini

Re: [OE-core] [PATCH] waf.bbclass: check that waf exists before trying to execute it

On 31 January 2018 at 17:19, Martin Jansa wrote: > But shouldn't it at least show different error message in case when > ${S}/waf doesn't exist and when it fails to execute it for whatever reason? > Sure, first thing should be to check if S/waf exists and if not, abort.

Re: [OE-core] [PATCH] waf.bbclass: check that waf exists before trying to execute it

But shouldn't it at least show different error message in case when ${S}/waf doesn't exist and when it fails to execute it for whatever reason? On Wed, Jan 31, 2018 at 6:16 PM, Burton, Ross wrote: > On 31 January 2018 at 17:07, Martin Jansa wrote:

Re: [OE-core] [PATCH] waf.bbclass: cd to ${S} before checking version

On 31 January 2018 at 17:02, Joshua Watt wrote: > waf requires that the current working directory be the project root (in > this case ${S} when it is invoked. The check to get the waf version was > being executed as a prefunc for do_configure, which meant it was > executed

Re: [OE-core] [PATCH] waf.bbclass: check that waf exists before trying to execute it

On 31 January 2018 at 17:07, Martin Jansa wrote: > What about the recipes which don't have ${S}/waf at all (and might inherit > waf from possibly wrong reasons), like all those waf-samba recipes > mentioned before? > If a recipe inherits waf but doesn't use waf I'm

Re: [OE-core] [PATCH] waf.bbclass: check that waf exists before trying to execute it

On Wed, 2018-01-31 at 18:07 +0100, Martin Jansa wrote: > What about the recipes which don't have ${S}/waf at all (and might > inherit waf from possibly wrong reasons), like all those waf-samba > recipes mentioned before? Ya, sorry I should have clarified: This should fix it for recipes that only

Re: [OE-core] [PATCH] waf.bbclass: check that waf exists before trying to execute it

What about the recipes which don't have ${S}/waf at all (and might inherit waf from possibly wrong reasons), like all those waf-samba recipes mentioned before? On Wed, Jan 31, 2018 at 6:04 PM, Joshua Watt wrote: > Sorry, I wasn't sure if I should make my patch in-reply-to

Re: [OE-core] [PATCH] waf.bbclass: check that waf exists before trying to execute it

Sorry, I wasn't sure if I should make my patch in-reply-to this thread I think I fixed this correctly in http://lists.openembedded.org/piperma il/openembedded-core/2018-January/147041.html Thanks,Joshua Watt On Wed, 2018-01-31 at 00:39 +0100, Martin Jansa wrote: > +Stefan > > On Wed, Jan 31,

[OE-core] [PATCH] waf.bbclass: cd to ${S} before checking version

waf requires that the current working directory be the project root (in this case ${S} when it is invoked. The check to get the waf version was being executed as a prefunc for do_configure, which meant it was executed before the current working directory was switched to ${S}, and thus would fail

[OE-core] [PATCH] bitbake.conf: Add xattr to DISTRO_FEATURES_NATIVE

Commit db1f1adace58763c35774e3fdfeaac5c3ca646fd disabled 'xattr' from DISTRO_FEATURES when native packages are built, whereas for target packages it was retained. This changed eg. mtd-utils-native to build without extended attributes (capabilities) support from there on. Thus even setcap was

[OE-core] [PATCH 3/3] vulkan: upgrade to version 1.0.65.2

1.0.61.1 -> 1.0.65.2 Signed-off-by: Maxin B. John --- .../vulkan/{vulkan_1.0.61.1.bb => vulkan_1.0.65.2.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-graphics/vulkan/{vulkan_1.0.61.1.bb => vulkan_1.0.65.2.bb} (95%)

[OE-core] [PATCH 2/3] assimp: upgrade to version 4.1.0

4.0.1 -> 4.1.0 Signed-off-by: Maxin B. John --- meta/recipes-graphics/vulkan/{assimp_4.0.1.bb => assimp_4.1.0.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-graphics/vulkan/{assimp_4.0.1.bb => assimp_4.1.0.bb} (91%) diff --git

[OE-core] [PATCH 1/3] libinput: upgrade to version 1.9.4

1.8.4 -> 1.9.4 Signed-off-by: Maxin B. John --- .../wayland/{libinput_1.8.4.bb => libinput_1.9.4.bb} | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) rename meta/recipes-graphics/wayland/{libinput_1.8.4.bb => libinput_1.9.4.bb} (85%) diff --git

Re: [OE-core] [PATCH 4/7] gpgme: 1.9.0 -> 1.10.0

On 01/31/2018 02:28 PM, Burton, Ross wrote: On 31 January 2018 at 07:48, Hongxu Jia > wrote: 1. Disable test at build time to workaround corss-compile Looks like more tests need to be disabled: | Making all in tests | make[4]:

Re: [OE-core] [PATCH 4/7] gpgme: 1.9.0 -> 1.10.0

On 31 January 2018 at 07:48, Hongxu Jia wrote: > 1. Disable test at build time to workaround corss-compile > Looks like more tests need to be disabled: | Making all in tests | make[4]: Entering directory

Re: [OE-core] [PATCH] ninja: Upgrade from 1.7.2 to major release 1.8.2

Patch doesn't apply, can you rebase and resend please. Ross On 30 January 2018 at 21:09, Alejandro Enedino Hernandez Samaniego < alejandro.enedino.hernandez-samani...@xilinx.com> wrote: > Signed-off-by: Alejandro Enedino Hernandez Samaniego > > --- >

[OE-core] [PATCH] module-base: use modules_prepare build target in do_make_scripts()

The kernel Makefile's 'modules_prepare' target must be called for fully setting up a module build environment. Unlike calling 'scripts' target, this also calls 'prepare' target which compiles 'objtool' for example. Otherwise, when having CONFIG_STACK_VALIDATION in kernel config enabled, module

Re: [OE-core] [PATCH 7/7] apr: 1.6.2 -> 1.6.3

We're carrying a lot of patches here, and I'm not convinced that they are all inappropriate. Would you be willing to see what of those are upstreamable? Ross On 31 January 2018 at 07:48, Hongxu Jia wrote: > - Rebase patches 0001 ~ 0008 > > - Fix build path issue to

[OE-core] [PATCH] i2c-tools: rewrite packaging

For unknowable reasons this recipe inherits autotools-brokensep despite not in fact using autotools. Remove the inherit, add a do_install() that calls the makefile directly. Extend EXTRA_OEMAKE to pass bindir/sbindir/incdir/libdir/mandir so the files are all packaged in the correct location (and

Re: [OE-core] [PATCH 1/1] i2c-tools: fix libdir for multilib

On 31 January 2018 at 09:44, wrote: > inherit autotools-brokensep > > +EXTRA_OEMAKE = "libdir=${libdir}" > + > do_compile_prepend() { > sed -i 's#/usr/local#/usr#' ${S}/Makefile > echo "include eeprog/Module.mk" >> ${S}/Makefile > The context of

[OE-core] [PATCH 1/1] i2c-tools: fix libdir for multilib

From: Kai Kang It set variable libdir with $(prefix)/lib in makefile which is not right when multilib is enabled. Correct it with ${libdir}. Signed-off-by: Kai Kang --- meta/recipes-devtools/i2c-tools/i2c-tools_4.0.bb | 2 ++ 1 file changed, 2

[OE-core] [PATCH 0/1] i2c-tools: fix libdir for multilib

From: Kai Kang The following changes since commit e5e89cfb7bc2231ac4fcc16f4cb4f74d806136c4: pulseaudio: improve glibc 2.27 patch (2018-01-30 12:53:16 +) are available in the git repository at: git://git.pokylinux.org/poky-contrib kangkai/i2c

Re: [OE-core] [PATCH] base.bbclass: fix do_unpack[cleandirs] varflag handling

Hey, any comments on that? Not using this patch currently disturbs our companies Yocto kernel workflow. Thus I wonder if no one else have had issues when building kernels from fully custom 'defconfig' files, too. Regards, Enrico On 01/21/2018 12:44 AM, Enrico Jorns wrote: As introduced by

Re: [OE-core] [PATCH 1/2] scripts/runqemu: qemumips support up to 2GiB RAM

On 2017年12月20日 09:53, Hongxu Jia wrote: Ping Ross Ping //Hongxu //Hongxu On 2017年12月06日 10:46, Hongxu Jia wrote: OE uses qemumips to simulate a Malta board by default. As upstream qemu introduced: https://git.qemu.org/?p=qemu.git;a=commit;h=94c2b6aff43cdfcfdfb552773a6b6b973a72ef0b

Re: [OE-core] [PATCH 0/6] improve reproducibility of 6 recipes

Ping //Hongxu On 2018年01月12日 16:11, Hongxu Jia wrote: Fix build path issue of these recipes to improve reproducibility Build success on qemux86-64 with multilib enabled. //Hongxu The following changes since commit 364f8bcfcbd04e722490f363ad36a15fb7066ba7: linux-firmware: Bump revision

[OE-core] [PATCH] tar: 1.29 -> 1.30

1.Upgrade tar from 1.29 to 1.30. 2.Modify musl_dirent.patch, since the data has been changed. 3.Delete CVE-2016-6321.patch, since it is integrated upstream. Signed-off-by: Huang Qiyu --- meta/recipes-extended/tar/tar/CVE-2016-6321.patch | 66 --

Re: [OE-core] [PATCH 2/7] pigz: 2.3.4 -> 2.4

On 01/31/2018 10:29 AM, Hongxu Jia wrote: On 2018年01月31日 16:14, Alexander Kanavin wrote: On 01/31/2018 09:48 AM, Hongxu Jia wrote: -LIC_FILES_CHKSUM = "file://pigz.c;beginline=7;endline=21;md5=a21d4075cb00ab4ca17fce5e7534ca95" +LIC_FILES_CHKSUM =

[OE-core] [PATCH v2] pigz: 2.3.4 -> 2.4

- Update the checksum of LIC_FILES_CHKSUM, license is no change, only version bump up. https://github.com/madler/pigz/commit/fe822cb435622c43f491013da77b127e9fe851a9 Signed-off-by: Hongxu Jia --- meta/recipes-extended/pigz/{pigz_2.3.4.bb => pigz_2.4.bb} | 6 +++---

Re: [OE-core] [PATCH 2/7] pigz: 2.3.4 -> 2.4

On 2018年01月31日 16:14, Alexander Kanavin wrote: On 01/31/2018 09:48 AM, Hongxu Jia wrote: -LIC_FILES_CHKSUM = "file://pigz.c;beginline=7;endline=21;md5=a21d4075cb00ab4ca17fce5e7534ca95" +LIC_FILES_CHKSUM = "file://pigz.c;md5=9ae6dee8ceba9610596ed0ada493d142;beginline=7;endline=21" Please

Re: [OE-core] [PATCH 2/7] pigz: 2.3.4 -> 2.4

On 01/31/2018 09:48 AM, Hongxu Jia wrote: -LIC_FILES_CHKSUM = "file://pigz.c;beginline=7;endline=21;md5=a21d4075cb00ab4ca17fce5e7534ca95" +LIC_FILES_CHKSUM = "file://pigz.c;md5=9ae6dee8ceba9610596ed0ada493d142;beginline=7;endline=21" Please explain what changed here? Alex --