Re: [OE-core] [PATCH] iputils: add libidn dependency

On Tue, Feb 6, 2018 at 2:44 PM, Martin Jansa wrote: > * https://github.com/iputils/iputils/blob/master/RELNOTES.old > mentiones that IDN was enabled by default in: > [s20160308] and surprisingly the same in [s20150815] > but there are no release notes for s20151218

Re: [OE-core] [PATCH][PYRO] linux-firmware: Add reference to iwlwifi-8000C firmware

On Wed, 2018-02-07 at 10:53 +0530, avinash.reddy.pall...@intel.com wrote: > From: Avinash Reddy Palleti > > Adding reference to iwlwifi-8000c firmware which was removed > erroneously in > commit 3e4b382c0c687a76f824cd84b478c4f778e15e3e > Blame me! >

[OE-core] [PATCH][PYRO] linux-firmware: Add reference to iwlwifi-8000C firmware

From: Avinash Reddy Palleti Adding reference to iwlwifi-8000c firmware which was removed erroneously in commit 3e4b382c0c687a76f824cd84b478c4f778e15e3e Signed-off-by: Avinash Reddy Palleti ---

Re: [OE-core] Issues with meson in SDK with cross-file

On Tue, 2018-02-06 at 15:39 -0800, Martin Kelly wrote: > (ping) > > Paul, what do you about the options we have here for making meson > work > properly in the SDK? > > To recap, here are the available options. I'm wondering if you could > give your opinion on the best fit for how OE SDKs work:

[OE-core] [PATCH] autoconf-doc: improve reproducibility

autoconf-doc package contains autoconf.info. This file contains date when this file was created, i.e: "This manual (31 January 2018) .." Therefore, two builds done on two different days will show different dates for otherwise identical files, hence breaking reproducibility. The date is

Re: [OE-core] Issues with meson in SDK with cross-file

(ping) Paul, what do you about the options we have here for making meson work properly in the SDK? To recap, here are the available options. I'm wondering if you could give your opinion on the best fit for how OE SDKs work: - Generate meson.cross toolchain file at SDK extraction time. -

[OE-core] [PATCH] iputils: add libidn dependency

* https://github.com/iputils/iputils/blob/master/RELNOTES.old mentiones that IDN was enabled by default in: [s20160308] and surprisingly the same in [s20150815] but there are no release notes for s20151218 version we were using until now, don't know how it really relates to [s20150815]. *

Re: [OE-core] [oe-commits] [openembedded-core] 57/62: iputils: update to 20161105

https://github.com/iputils/iputils/blob/master/RELNOTES.old mentiones that IDN was enabled by default in: [s20160308] and surprisingly the same in [s20150815] but there are no release notes for s20151218 version we were using until now, don't know how it really relates to [s20150815].

[OE-core] ✗ patchtest: failure for Fix support for Icecream

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

[OE-core] [PATCH 11/14] icecc-create-env: Allow multiple tool aliases

When files are added to the environment, multiple aliases can be given for the file (by calling add_path multiple times with a second argument). All of these names will end up with a symlink to the original file. Signed-off-by: Joshua Watt ---

[OE-core] [PATCH 14/14] icecc.bbclass: Add IceCream support to SDK

If icecc is inherited, generated SDKs will automatically have optional support for compiling using the IceCream distributed compiler Signed-off-by: Joshua Watt --- meta/classes/icecc.bbclass | 7 +++ 1 file changed, 7 insertions(+) diff --git

[OE-core] [PATCH 13/14] icecc-toolchain: Add SDK icecream setup

IceCream can now be optionally included in the generated SDK by including nativesdk-icecc-toolchain to TOOLCHAIN_HOST_TASK. When the SDK is installed, it will check if icecc exists, and if so will generate the toolchain environment. Signed-off-by: Joshua Watt ---

[OE-core] [PATCH 10/14] icecc-create-env: Add support for nativesdk

icecc-create-env can now be built as a nativesdk recipe, allowing the script to be included as part of an SDK Signed-off-by: Joshua Watt --- .../{icecc-create-env-native_0.1.bb => icecc-create-env_0.1.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)

[OE-core] [PATCH 12/14] toolchain-shar-extract: Add post-relocate scripts

Recipes can now install post-relocation scripts which will be run when the SDK is installed. Signed-off-by: Joshua Watt --- meta/classes/toolchain-scripts.bbclass | 15 +++ meta/files/toolchain-shar-extract.sh | 8

[OE-core] [PATCH 06/14] icecc-create-env: Use program interpreter for deps

ldd cannot always be used to determine a programs dependencies correctly, particularly when the program specifies an alternate program interpreter (dynamic loader). This commonly happens when using a uninative tarball. Instead, determine the program's requested interpreter, and ask it to list the

[OE-core] [PATCH 08/14] icecc-create-env: Archive directory

Taring up the toolchain is now done by adding the entire working directory, instead of listing all the files individually. This is done because the list of files may contain ".." entries, which tar does not like and strips out, resulting in bad archives. This should result in an identical archive

[OE-core] [PATCH 09/14] icecc-create-env: Fix executable rpaths

Executables in the toolchain archive occasionally contain runtime library search paths (RPATH) that use the $ORIGIN placeholder. However, in order for that placeholder to work, /proc must be mounted. When iceccd executes the toolchain in the chroot environment, it doesn't mount /proc, so it is

[OE-core] [PATCH 07/14] icecc-create-env: Symlink alternate names

Instead of renaming files to a new path in the toolchain archive, keep the files with their original paths and create a relative symbolic link from the new path to the original file. Signed-off-by: Joshua Watt --- .../icecc-create-env/icecc-create-env | 64

[OE-core] [PATCH 05/14] icecc-create-env: Add /bin/true to environment

icecream daemons execute /bin/true from the environment as a check to determine if the environment is valid at all, so it needs to be included. Signed-off-by: Joshua Watt --- .../icecc-create-env/icecc-create-env/icecc-create-env | 10 ++ 1 file changed, 10

[OE-core] [PATCH 04/14] icecc-create-env: Reformat

The environment script used an annoying mix of tabs and spaces, and no mapping of tabs to spaces would produce pleasant indentation. Reformat to eliminate tab characters and settle on 4 spaces for indentation (which matches the upstream icecream script from which this is derived) Signed-off-by:

[OE-core] [PATCH 02/14] icecc.bbclass: Fix STAGING_BINDIR_TOOLCHAIN usage

STAGING_BINDIR_TOOLCHAIN is actually a path list, not a single path. Fix icecc.bbclass to try all the paths in the variable instead of treating it as a single path. Signed-off-by: Joshua Watt --- meta/classes/icecc.bbclass | 17 - 1 file changed, 8

[OE-core] [PATCH 03/14] icecc.bbclass: Skip canadian-cross compiles

icecc.bbclass will no longer attempt to distribute cross-canadian compiles. While technically possible to generate a toolchain that runs on the build system and generates executables for the host system, this is not the normal way that icecc operates and there are so few of these recipes that it

[OE-core] [PATCH 01/14] icecc.bbclass: Move to shared work directory

Generate the icecc toolchains in a shared work directory. This class was already setup to correctly synchronize creating the toolchains in a shared location before the RSS changes, so return to that behavior instead of generated the toolchains in each recipe's sysroot. Additionally, it makes no

Re: [OE-core] [oe-commits] [openembedded-core] 57/62: iputils: update to 20161105

Doesn't this new version depend on libidn? Maybe it should be new PACKAGECONFIG or something, but here all builds fail with: | In file included from ping_common.c:1:0: | ping.h:39:10: fatal error: idna.h: No such file or directory | #include | ^~~~ I'm running another build with

[OE-core] [PATCH 00/14] Fix support for Icecream

Fix up support for using Icecream to do distributed builds, which appears to have been broken for some time. In addition, Icecream support can now be enabled in the SDK. When enabled, the SDK install process will check if the host supports icecc and if so will construct a proper environment

[OE-core] [pyro][PATCH] python3-nose: rename ${bindir}/nosetests into ${bindir}/nosetests3

From: Denys Dmytriyenko This resolves a conflict when both python-nose and python3-nose are pulled into an image and try to install ${bindir}/nosetests binary. This matches with how other distros are solving this problem, e.g. Debian:

[OE-core] [pyro][PATCH] distutils-base.bbclass: Do not use -pie with hardening

From: Khem Raj Fix build when PIE is turned on. It tries to build .so file using -pie and -shared flags together because its doing compile and link in same step CFLAGS and LDFLAGS are combined and does not work, ending in errors e.g. |

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

Shortly after leaving work last night I realized that this error should have nothing to do with the initrd/initramfs, as this wic image is not using one. Also, in 300 runs of this test the error didn't occur once, so it appears to be very rare. --- Cal On 02/05/2018 05:52 PM, Cal Sullivan

Re: [OE-core] [PATCH] glibc: improve reproducibility with multilib

> This “| xargs” at the end seems redundant. xargs what? xargs is used to run a > command on each word of > the input.. It forces the words into one line: $ echo "zebra fox elephant elephant lion wolf fox " | xargs -n1 | sort -u | xargs elephant fox lion wolf zebra $echo "zebra fox elephant

Re: [OE-core] [PATCH] classes/npm: replace cache clear with cache clean --force

Hi, You wrote: > 2018-02-05 16:55 keltezéssel, Matthijs Vader írta: > > Hi, > > > > 2018-02-05 15:07, zboszor wrote: > >> I have already sent this patch (although a little extended) last week: > >> http://lists.openembedded.org/pipermail/openembedded-core/2018- > >> February/147071.html > > > >

[OE-core] ✗ patchtest: failure for yocto-bsp: delete bbappends for removed kernels

== Series Details == Series: yocto-bsp: delete bbappends for removed kernels Revision: 1 URL : https://patchwork.openembedded.org/series/10862/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have

[OE-core] [PATCH] yocto-bsp: delete bbappends for removed kernels

4.4/4.9/4.10 are gone from oe-core master, so we can drop our bbappends. 4.12 will be removed in the future and 4.14/4.15 added, but all default versions should be 4.12+ now. Signed-off-by: Bruce Ashfield --- .../recipes-kernel/linux/linux-yocto_4.10.bbappend | 27

[OE-core] [PATCH 9/9] machines: bump default linux-yocto to v4.15

Ensure that the qemu* machines are building the latest available kernel in master. Signed-off-by: Bruce Ashfield --- meta/conf/machine/include/x86-base.inc | 2 +- meta/conf/machine/qemuarm.conf | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff

[OE-core] [PATCH 8/9] linux-yocto/4.9: drop recipe

As was previously announced, anything older than 4.14 is being dropped in the master/release branches to better support newer processors and to ensure that safe/secure kernels are the defaults for all builds. The time required to update the older kernels with constant updates (more than just CVEs)

[OE-core] [PATCH 6/9] linux-yocto/4.10: drop recipe

As was previously announced, anything older than 4.14 is being dropped in the master/release branches to better support newer processors and to ensure that safe/secure kernels are the defaults for all builds. The time required to update the older kernels with constant updates (more than just CVEs)

[OE-core] [PATCH 7/9] linux-yocto/4.4: drop recipe

As was previously announced, anything older than 4.14 is being dropped in the master/release branches to better support newer processors and to ensure that safe/secure kernels are the defaults for all builds. The time required to update the older kernels with constant updates (more than just CVEs)

[OE-core] [PATCH 5/9] lttng-modules: update to v2.10.5 for kernel 4.15

Signed-off-by: Bruce Ashfield --- .../lttng/{lttng-modules_2.10.4.bb => lttng-modules_2.10.5.bb}| 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-kernel/lttng/{lttng-modules_2.10.4.bb => lttng-modules_2.10.5.bb} (90%) diff

[OE-core] [PATCH 4/9] linux-yocto/4.12: pinctrl backports

Backporting the following pinctrl commits to enable controllers on Intel Cannon Lake: 4b7a5c1b4ec5 pinctrl: intel: Add Intel Cannon Lake PCH-H pin controller support 044631ce1937 pinctrl: intel: Add Intel Cannon Lake PCH pin controller support 2054b0ea59a7 pinctrl: intel: Make it possible

[OE-core] [PATCH 3/9] linux-libc-headers: update to v4.15

Signed-off-by: Bruce Ashfield --- meta/conf/distro/include/tcmode-default.inc| 2 +- ...mpat.h-fix-some-issues-arising-from-in6.h.patch | 29 - ...t.h-prevent-redefinition-of-struct-ethhdr.patch | 36 +++---

[OE-core] [PATCH 2/9] linux-yocto: introduce 4.15 recipes

This commit makes the 4.15 kernel available for use with the Yocto configuration fragments and qemu* BSPs. It has been tested for x86,arm,mips and powerpc against the lsb, core* and glibc/mulsc test matrix. This will serve as the "latest" kernel in master, with others being removed in subsequent

[OE-core] [PATCH 1/9] linux-yocto: introduce 4.14 recipes

This commit makes the 4.14 kernel available for use with the Yocto configuration fragments and qemu* BSPs. It has been tested for x86,arm,mips and powerpc against the lsb, core* and glibc/mulsc test matrix. This will serve as the LTS kernel in master, with others being removed in subsequent

[OE-core] [PATCH 0/9] kernel-yocto: kernel updates/drops/refreshes

Hi all, Here is my first proposed set of kernel updates for the April release. Some elements that I'd like to point out: - I've moved to a single/branch versioned linux-yocto repository that I first proposed in the 4.8 kernel cycle, no one objected, so I've moved v4.14 and v4.15 into that

[OE-core] [PATCH] iputils: add missing Upstream-Status to patch

Signed-off-by: Alexander Kanavin --- meta/recipes-extended/iputils/files/0001-Fix-build-on-MUSL.patch | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-extended/iputils/files/0001-Fix-build-on-MUSL.patch

[OE-core] [PATCH 3/3] oe-selftest: add a test for failing package post-installation scriptlets

The test runs a scriptlet that has an intentionally failing command in the middle and checks for two things: 1) that bitbake does warn the user about the failure 2) that scriptlet execution stops at that point. The test is run for all three package types: rpm, deb, ipk. Signed-off-by: Alexander

[OE-core] [PATCH 1/3] package.bbclass: run pre/post installation/removal scriptlets using sh -e

This allows catching errors in the scriptlets which would otherwise go unnoticed, e.g. this sequence: bogus_command proper_command would work just fine without any visible warnings or errors. This was previously done only for rpm packages; this patch replaces the rpm-specific tweak with

[OE-core] [PATCH 2/3] meta/lib/oe/package_manager.py: warn about failing scriptlets for all package types

Previously this was done only for rpm packages; now also ipk/deb scriptlet failures are reported. In the future this will become a hard error, but it can't yet happen due to the legacy 'exit 1' way of deferring scriptlet execution to first boot which needs a deprecation period. Signed-off-by:

Re: [OE-core] [PATCHv2] libpam: be more strict about user's sanity

I'm sorry, I haven't seen this one, because I have packagegroup-core-lsb blacklisted for long time. What is preferred fix? 1) add the same restriction to packagegroup-core-lsb and core-image-lsb and someone will fix poky-lsb build (it doesn't seem like separate distro), to include pam in

[OE-core] [PATCH 2/4] expat: remove old workaround for expat tarball

Back in 2010 the expat 2.0.1 tarball wouldn't unpack correctly with old gzip releases (prior to 1.4). The fix was to explicitly depend on gzip-native to use our binary instead of the host[1]. We don't ship expat 2.0.1 anymore, and even Centos 7 ships gzip 1.5, so this workaround can be removed.

[OE-core] [PATCH 4/4] pigz: use maintainer-built tarballs

Signed-off-by: Ross Burton --- meta/recipes-extended/pigz/pigz_2.4.bb | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/meta/recipes-extended/pigz/pigz_2.4.bb b/meta/recipes-extended/pigz/pigz_2.4.bb index 20e4154434f..6e6da9c3c56 100644 ---

[OE-core] [PATCH 3/4] pigz: pigz is not gzip

Whilst pigz is effectively a parallel gzip, the command line arguments are not the same so pigz isn't a drop-in replacement for gzip. [ YOCTO #12139 ] [ YOCTO #12410 ] Signed-off-by: Ross Burton --- meta/conf/distro/include/default-providers.inc | 1 -

[OE-core] [PATCH 1/4] expat: merge bb and inc

Signed-off-by: Ross Burton --- meta/recipes-core/expat/expat.inc | 25 - meta/recipes-core/expat/expat_2.2.5.bb | 28 +++- 2 files changed, 27 insertions(+), 26 deletions(-) delete mode 100644

Re: [OE-core] [PATCH] classes/npm: replace cache clear with cache clean --force

2018-02-05 16:55 keltezéssel, Matthijs Vader írta: Hi, 2018-02-05 15:07, zboszor wrote: I have already sent this patch (although a little extended) last week: http://lists.openembedded.org/pipermail/openembedded-core/2018- February/147071.html Thanks! The second patch you sent in with that

Re: [OE-core] [PATCH v2 2/3] libva: upgrade to 2.0.0

On 6 February 2018 at 02:03, Anuj Mittal wrote: > +SRC_URI = "https://github.com/intel/${BPN}/releases/download/${PV}/$ > {BPN}-${PV}.tar.bz2" > For convenience bitbake.conf defines BP: BP = "${BPN}-${PV}" Don't bother sending a V3 as I'll just make this change when

Re: [OE-core] [PATCH] kernel.bbclass: Fix symlink creation when using externalsrc

Ping? On Mon, Jan 29, 2018 at 4:38 PM, Stefan Stanacar wrote: > do_unpack is by default in SRCTREECOVEREDTASKS so this append can't run, > since > do_unpack gets removed by when externalsrc is enabled. > > This was hidden because externalsrc does actually run do_fetch and >

Re: [OE-core] WARNING: Variable key %s (%s) replaces original key %s (%s).

On Tuesday, 6 February 2018 11:25:08 AM NZDT Burton, Ross wrote: > On 5 February 2018 at 22:13, Denys Dmytriyenko wrote: > > > On Mon, Feb 05, 2018 at 09:53:44PM +, Burton, Ross wrote: > > > On 5 February 2018 at 18:21, Denys Dmytriyenko wrote: > > > > > >