Re: [OE-core] [yocto] [RFT] gcc7 and glibc-2.26 recipes

"Burton, Ross" writes: > On 24 April 2017 at 23:00, Nathan Lynch wrote: > >> Does adding this patch to lttng-modules work around it? >> > > Yes, it fixes the build here. I'll throw it at the autobuilder now, can > you send a patch with a commit

Re: [OE-core] [PATCH] lttng-modules: work around GCC 7 changes

On 4/25/17 3:33 PM, Nathan Lynch wrote: > Avoid using LTTng's BUILD_RUNTIME_BUG_ON macro, as it appears to run > into a similar problem as Linux experienced with __builtin_constant_p > and dead code elimination. > Thanks for contributing. this patch looks ok to me. > Signed-off-by: Nathan

Re: [OE-core] [PATCH 1/2] grub: Fix build with gcc7

On Mon, Apr 24, 2017 at 6:38 PM, Khem Raj wrote: > On Mon, Apr 24, 2017 at 3:34 PM, Burton, Ross wrote: >> Clearly there's some build difference between our configurations. Are you >> building grub-git instead of grub_2.00? Should we delete grub_2.00

[OE-core] [PATCH] lttng-modules: work around GCC 7 changes

Avoid using LTTng's BUILD_RUNTIME_BUG_ON macro, as it appears to run into a similar problem as Linux experienced with __builtin_constant_p and dead code elimination. Signed-off-by: Nathan Lynch --- .../BUILD_RUNTIME_BUG_ON-vs-gcc7.patch | 43

Re: [OE-core] [PATCH 0/4] Reproducible binaries

On Tue, Apr 25, 2017 at 2:14 PM, Juro Bystricky wrote: > The variable defaults to "0" (do not > build reproducible binaries) in order to minimize any potential > regressions. (Once the reproducible binaries code is mature enough, > it can be set to "1".) My guess is

[OE-core] [PATCH 0/4] Reproducible binaries

This patch set contains several patches aimed to achieve reproducible binaries. Building reproducible binaries may remove certain intentional randomness intended for increased security. Hence, it is reasonable to expect there will be cases where this is not desirable. The user can select his/her

[OE-core] [PATCH 2/4] base.bbclass: initial support for binary reproducibility

Conditionally set some environment variables in order to achieve improved binary reproducibility. Providing BUILD_REPRODUCIBLE_BINARIES is set to "1", we set the following environment variables: export PYTHONHASHSEED=0 export PERL_HASH_SEED=0 export TZ="UTC" We also export and set

[OE-core] [PATCH 4/4] rootfs-postcommands.bbclass: support binary reproducibility

Conditionally support binary reproducibility of rootfs images. If BUILD_REPRODUCIBLE_BINARIES = 1 then: 1. set /etc/timestamp to a reproducible value 2. set /etc/version to a reproducible value The value for /etc/version is modified in a designated catch-all post-rootfs function

[OE-core] [PATCH 1/4] bitbake.conf: new variable BUILD_REPRODUCIBLE_BINARIES

Building reproducible binaries may remove certain intentional randomness intended for increased security. Hence, it is reasonable to expect there will be cases where this is not desirable. The user can select his/her preferences via the variable BUILD_REPRODUCIBLE_BINARIES. The variable defaults

[OE-core] [PATCH 3/4] image-preling.bbclass: support binary reproducibility

Conditionally support binary reproducibility in built images. If BUILD_REPRODUCIBLE_BINARIES = 1 then: 1. Do not randomize library addresses 2. Set/export PRELINK_TIMESTAMP to a reproducible value. The value is derived from the top git commit. Signed-off-by: Juro Bystricky

Re: [OE-core] ✗ patchtest: failure for bash: CVE-2016-0634

On Thu, 2017-04-20 at 07:01 +, Patchwork wrote: > == Series Details == > > Series: bash: CVE-2016-0634 > Revision: 1 > URL : https://patchwork.openembedded.org/series/6434/ > State : failure > > == Summary == > > > Thank you for submitting this patch series to OpenEmbedded Core. This is

Re: [OE-core] [PATCH 0/4] Reproducible binaries

Is using the last commit really that useful? I would like to be able to compare 2 subsequent builds (ideally performed on 2 different hosts with some small modification in metadata layers) and the binaries not affected by those small metadata modifications should be the same - which is not the

[OE-core] ✗ patchtest: failure for libcap: clean up gperf enabling logic

== Series Details == Series: libcap: clean up gperf enabling logic Revision: 1 URL : https://patchwork.openembedded.org/series/6502/ 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] Partially revert "volatile-binds: correct some errors reported by systemd"

Suppressing default version of etc.conf for systemd-tmpfiles-setup prevents at least the name resolver from working as expected when using systemd-resolved. The missing /etc/resolv.conf symlink breaks application relying on this for name resolution (tested with ping from busybox). This patch

Re: [OE-core] [PATCHv4 4/7] bluez5: add PACKAGECONFIG option for systemd

On Tue, Apr 25, 2017 at 11:13 AM, Martin Jansa wrote: > > On Tue, Apr 25, 2017 at 10:48:37AM -0400, Marc Ferland wrote: > > Signed-off-by: Marc Ferland > > --- > > meta/recipes-connectivity/bluez5/bluez5.inc | 4 ++-- > > 1 file changed, 2

[OE-core] [PATCH] libcap: clean up gperf enabling logic

There's no need to sed the Makefile (especially the wrong Makefile) when there's a variable we can pass. Signed-off-by: Ross Burton --- meta/recipes-support/libcap/libcap_2.25.bb | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git

Re: [OE-core] ✗ patchtest: failure for busybox: fix typo in CVE-2016-2147_2.patch Upstream-Status tag

On Tue, Apr 25, 2017 at 9:06 AM, Leonardo Sandoval wrote: > On Thu, 2017-04-20 at 01:01 +, Patchwork wrote: >> == Series Details == >> >> Series: busybox: fix typo in CVE-2016-2147_2.patch Upstream-Status tag >> Revision: 1 >> URL :

Re: [OE-core] [PATCH 0/4] Reproducible binaries

The idea is that both builds have reproducible timestamps. So there may be different ways to determine the best way to get the stamp. My rationale was that if the builds are from two different commits, the difference should be reflected in the timestamp. But I agree that two different commits

[OE-core] [PATCH v2] libevent: 2.0.22 -> 2.1.8

Update libevent to version 2.1.8 and fix test directory creation License file has been changed due to new MIT license in source code. Signed-off-by: Andrej Valek Signed-off-by: Pascal Bach --- .../libevent/Makefile-missing-test-dir.patch

Re: [OE-core] [PATCH v3 2/2] tcf-agent: enable default target debugging features

On 21.04.2017 18:39, Burton, Ross wrote: > > On 20 April 2017 at 20:08, Gernot Hillier > wrote: > > A number of features were disabled in OE due to historic problems > on ARM. In tcf-agent 1.4, they compile cleanly on all

[OE-core] [PATCH v2] connman: fix race condition with systemd-udev

When a new USB network interface is plugged in systemd fails to rename the new interface (ethX) to a predictable name [1] because connman locks it first. Add a fix to connman that makes it to re-evaluate a known but blacklisted ethernet interface for enabling after it has got renamed. Still a

Re: [OE-core] [yocto] [RFT] gcc7 and glibc-2.26 recipes

On 24 April 2017 at 23:00, Nathan Lynch wrote: > Does adding this patch to lttng-modules work around it? > Yes, it fixes the build here. I'll throw it at the autobuilder now, can you send a patch with a commit message that isn't "someone told me to try this"? :) Ross

Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update

On Mon, 2017-04-24 at 21:06 -0400, Bruce Ashfield wrote: > On Mon, Apr 24, 2017 at 5:27 PM, Richard Purdie > wrote: > > On Mon, 2017-04-24 at 15:56 -0400, Bruce Ashfield wrote: > > > > > > > > > On Mon, Apr 24, 2017 at 9:54 AM, Bruce Ashfield

Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update

On Tue, Apr 25, 2017 at 9:09 AM, Richard Purdie wrote: > On Mon, 2017-04-24 at 21:06 -0400, Bruce Ashfield wrote: > > On Mon, Apr 24, 2017 at 5:27 PM, Richard Purdie > > wrote: > > > On Mon, 2017-04-24 at 15:56 -0400,

Re: [OE-core] [PATCH] gperf: 3.0.4 -> 3.1

On 24 April 2017 at 03:12, Huang Qiyu wrote: > Upgrade gperf from 3.0.4 to 3.1. > This breaks the libcap build: | In file included from :0:0: | ./_caps_output.gperf:71:80: error: unknown type name 'size_t' | gperf_case_strncmp (register const char *s1, register

[OE-core] [PATCHv4 2/7] bluez5: remove libasound-module references

Cleanup references to libasound-module since this code has been completly removed from Bluez. Signed-off-by: Marc Ferland --- meta/conf/distro/include/default-providers.inc | 1 - meta/recipes-connectivity/bluez5/bluez5.inc | 5 +

[OE-core] [PATCHv4 1/7] bluez5: Upgrade 5.43 -> 5.44

New feautures/fixes in this version: * fixes to BLE * a new midi plugin * support for single-mode controllers w/o public address * most of the experimental tools have been promoted and are now part of the official tools * 'experimental' has been renamed to 'testing' (hence the addition of the

[OE-core] [PATCHv4 3/7] bluez5: add PACKAGECONFIG option for midi

Signed-off-by: Marc Ferland --- meta/recipes-connectivity/bluez5/bluez5.inc | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/recipes-connectivity/bluez5/bluez5.inc b/meta/recipes-connectivity/bluez5/bluez5.inc index 4244fc8..687656e 100644 ---

[OE-core] [PATCHv4 4/7] bluez5: add PACKAGECONFIG option for systemd

Signed-off-by: Marc Ferland --- meta/recipes-connectivity/bluez5/bluez5.inc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meta/recipes-connectivity/bluez5/bluez5.inc b/meta/recipes-connectivity/bluez5/bluez5.inc index 687656e..71a5016 100644 ---

[OE-core] [PATCHv4 0/7] bluez: upgrade and refactoring

V4: * dropped the "rename readline 'config' option to 'client'" changes (reported by Ross Burton) * make references to libasound-module-bluez depend on bluez4 only (reported by Ross burton) V3: * shell functions use tabs not spaces (reported by Khem Raj) V2: * upgrades to version 5.44 *

[OE-core] [PATCHv4 5/7] bluez5: add PACKAGECONFIG option for cups

Signed-off-by: Marc Ferland --- meta/recipes-connectivity/bluez5/bluez5.inc | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/meta/recipes-connectivity/bluez5/bluez5.inc b/meta/recipes-connectivity/bluez5/bluez5.inc index 71a5016..c8a240f 100644 ---

[OE-core] [PATCHv4 6/7] bluez5: do not install audio.conf

The audio.conf file has been removed, stop installing it. Signed-off-by: Marc Ferland --- meta/recipes-connectivity/bluez5/bluez5.inc | 3 --- 1 file changed, 3 deletions(-) diff --git a/meta/recipes-connectivity/bluez5/bluez5.inc

[OE-core] [PATCHv4 7/7] bluez5: cleanup tabs and spaces

Signed-off-by: Marc Ferland --- meta/recipes-connectivity/bluez5/bluez5.inc | 30 ++--- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/meta/recipes-connectivity/bluez5/bluez5.inc b/meta/recipes-connectivity/bluez5/bluez5.inc index

Re: [OE-core] [PATCHv4 4/7] bluez5: add PACKAGECONFIG option for systemd

On Tue, Apr 25, 2017 at 10:48:37AM -0400, Marc Ferland wrote: > Signed-off-by: Marc Ferland > --- > meta/recipes-connectivity/bluez5/bluez5.inc | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/meta/recipes-connectivity/bluez5/bluez5.inc >

Re: [OE-core] ✗ patchtest: failure for busybox: fix typo in CVE-2016-2147_2.patch Upstream-Status tag

On Thu, 2017-04-20 at 01:01 +, Patchwork wrote: > == Series Details == > > Series: busybox: fix typo in CVE-2016-2147_2.patch Upstream-Status tag > Revision: 1 > URL : https://patchwork.openembedded.org/series/6429/ > State : failure > > == Summary == > > > Thank you for submitting this