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

2018-02-06 Thread Khem Raj
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 version we were using until
>   now, don't know how it really relates to [s20150815].
>
> * 
> https://github.com/iputils/iputils/commit/f3a461603ef4fb7512ade3bdb73fe1824e294547
>
> * fails with:
>   | In file included from ping_common.c:1:0:
>   | ping.h:39:10: fatal error: idna.h: No such file or directory
>   |  #include 
>   |   ^~~~
>
> * Easiest way to reproduce this failure is to remove libidn from gnutls
>   PACKAGECONFIG or to use gnutls which doesn't have libidn PACKAGECONFIG
>   at all (like the one in meta-gplv2).

I think this should be turned into a PACKAGECONFIG and turned off
by default. It doesnt seem to be working as they have found bug in
libidn which needs to be fixed for it to work here. Prior default was to
disable it so we keep that.

>
> * First it leads to following QA issue:
>   http://errors.yoctoproject.org/Errors/Build/53212/
>   ERROR: iputils-s20161105-r0 do_package_qa: QA Issue: iputils-ping rdepends 
> on libidn, but it isn't a build dependency, missing libidn in DEPENDS or 
> PACKAGECONFIG? [build-deps]
>   ERROR: iputils-s20161105-r0 do_package_qa: QA Issue: iputils-traceroute6 
> rdepends on libidn, but it isn't a build dependency, missing libidn in 
> DEPENDS or PACKAGECONFIG? [build-deps]
>   ERROR: iputils-s20161105-r0 do_package_qa: QA run found fatal errors.
>   Please consider fixing them.
>   ERROR: iputils-s20161105-r0 do_package_qa: Function failed:
>   do_package_qa
>   ERROR: Logfile of failure stored in: 
> /OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/iputils/s20161105-r0/temp/log.do_package_qa.7627
>   ERROR: Task 
> (/OE/build/oe-core/openembedded-core/meta/recipes-extended/iputils/iputils_s20161105.bb:do_package_qa)
>  failed with exit code '1'
>
> * But if you cleansstate iputils as well (after removing libidn from
>   gnutls PACKAGECONFIG) to empty iputils RSS, then you get the error about
>   missing idna.h:
>   http://errors.yoctoproject.org/Errors/Build/53213/
>
> * Adding the libidn dependency explicitly in iputils recipe fixes the
>   issue.
>
> Signed-off-by: Martin Jansa 
> ---
>  meta/recipes-extended/iputils/iputils_s20161105.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-extended/iputils/iputils_s20161105.bb 
> b/meta/recipes-extended/iputils/iputils_s20161105.bb
> index ad7dbc4d4a..0acf2be5d3 100644
> --- a/meta/recipes-extended/iputils/iputils_s20161105.bb
> +++ b/meta/recipes-extended/iputils/iputils_s20161105.bb
> @@ -11,7 +11,7 @@ LIC_FILES_CHKSUM = 
> "file://ping.c;beginline=1;endline=35;md5=f9ceb201733e9a6cf8f
>  
> file://arping.c;beginline=1;endline=11;md5=fe84301b5c2655c950f8b92a057fafa6 \
>  
> file://tftpd.c;beginline=1;endline=32;md5=28834bf8a91a5b8a92755dbee709ef96 "
>
> -DEPENDS = "gnutls libcap libgcrypt"
> +DEPENDS = "gnutls libcap libgcrypt libidn"
>
>  SRC_URI = "git://github.com/iputils/iputils \
> file://0001-Fix-build-on-MUSL.patch \
> --
> 2.15.1
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Wold, Saul
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!


> Signed-off-by: Avinash Reddy Palleti  >
Acked-by: Saul Wold 
> ---
>  meta/recipes-kernel/linux-firmware/linux-firmware_git.bb | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb 
> b/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb
> index ff60d30..3a2148d 100644
> --- a/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb
> +++ b/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb
> @@ -247,7 +247,7 @@ PACKAGES =+ "${PN}-ralink-license ${PN}-ralink \
>   ${PN}-iwlwifi-6050-4 ${PN}-iwlwifi-6050-5 \
>   ${PN}-iwlwifi-7260 \
>   ${PN}-iwlwifi-7265 \
> - ${PN}-iwlwifi-7265d ${PN}-iwlwifi-8265 \
> + ${PN}-iwlwifi-7265d ${PN}-iwlwifi-8000c ${PN}-iwlwifi-
> 8265 \
>   ${PN}-iwlwifi-misc \
>   ${PN}-ibt-license ${PN}-ibt ${PN}-ibt-misc \
>   ${PN}-ibt-11-5 ${PN}-ibt-12-16 ${PN}-ibt-hw-37-7 ${PN}-
> ibt-hw-37-8 \
> @@ -619,6 +619,7 @@ FILES_${PN}-iwlwifi-6050-5 =
> "${nonarch_base_libdir}/firmware/iwlwifi-6050-5.uco
>  FILES_${PN}-iwlwifi-7260   =
> "${nonarch_base_libdir}/firmware/iwlwifi-7260-*.ucode"
>  FILES_${PN}-iwlwifi-7265   =
> "${nonarch_base_libdir}/firmware/iwlwifi-7265-*.ucode"
>  FILES_${PN}-iwlwifi-7265d   =
> "${nonarch_base_libdir}/firmware/iwlwifi-7265D-*.ucode"
> +FILES_${PN}-iwlwifi-8000c   =
> "${nonarch_base_libdir}/firmware/iwlwifi-8000C-*.ucode"
>  FILES_${PN}-iwlwifi-8265   =
> "${nonarch_base_libdir}/firmware/iwlwifi-8265-*.ucode"
>  FILES_${PN}-iwlwifi-misc   =
> "${nonarch_base_libdir}/firmware/iwlwifi-*.ucode"
>  
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread avinash . reddy . palleti
From: Avinash Reddy Palleti 

Adding reference to iwlwifi-8000c firmware which was removed erroneously in
commit  3e4b382c0c687a76f824cd84b478c4f778e15e3e

Signed-off-by: Avinash Reddy Palleti 
---
 meta/recipes-kernel/linux-firmware/linux-firmware_git.bb | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb 
b/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb
index ff60d30..3a2148d 100644
--- a/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb
+++ b/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb
@@ -247,7 +247,7 @@ PACKAGES =+ "${PN}-ralink-license ${PN}-ralink \
  ${PN}-iwlwifi-6050-4 ${PN}-iwlwifi-6050-5 \
  ${PN}-iwlwifi-7260 \
  ${PN}-iwlwifi-7265 \
- ${PN}-iwlwifi-7265d ${PN}-iwlwifi-8265 \
+ ${PN}-iwlwifi-7265d ${PN}-iwlwifi-8000c ${PN}-iwlwifi-8265 \
  ${PN}-iwlwifi-misc \
  ${PN}-ibt-license ${PN}-ibt ${PN}-ibt-misc \
  ${PN}-ibt-11-5 ${PN}-ibt-12-16 ${PN}-ibt-hw-37-7 
${PN}-ibt-hw-37-8 \
@@ -619,6 +619,7 @@ FILES_${PN}-iwlwifi-6050-5 = 
"${nonarch_base_libdir}/firmware/iwlwifi-6050-5.uco
 FILES_${PN}-iwlwifi-7260   = 
"${nonarch_base_libdir}/firmware/iwlwifi-7260-*.ucode"
 FILES_${PN}-iwlwifi-7265   = 
"${nonarch_base_libdir}/firmware/iwlwifi-7265-*.ucode"
 FILES_${PN}-iwlwifi-7265d   = 
"${nonarch_base_libdir}/firmware/iwlwifi-7265D-*.ucode"
+FILES_${PN}-iwlwifi-8000c   = 
"${nonarch_base_libdir}/firmware/iwlwifi-8000C-*.ucode"
 FILES_${PN}-iwlwifi-8265   = 
"${nonarch_base_libdir}/firmware/iwlwifi-8265-*.ucode"
 FILES_${PN}-iwlwifi-misc   = "${nonarch_base_libdir}/firmware/iwlwifi-*.ucode"
 
-- 
2.7.4

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Joshua Watt
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:
> 
> - Generate meson.cross toolchain file at SDK extraction time.
> - Wrap meson with a shell script that dynamically generates a
> toolchain 

FWIW, I *just* pushed up a patch to add support for this to so that I
could have Icecream distributed compiling support in the SDK. I called
them post-relocation scripts, see http://lists.openembedded.org/piperma
il/openembedded-core/2018-February/147282.html

This patch show how you install a post-relocation script from a recipe:
http://lists.openembedded.org/pipermail/openembedded-core/2018-February
/147283.html (look at icecc-setup.sh). It's pretty easy and modeled
after the environment setup scripts. The issue that meson is having
sounds similar to what I encountered with Icecream: something needed in
the SDK can only really be generated by host system when the SDK is
installed. There isn't enough information or the ability to generate it
beforehand when the SDK is constructed by Yocto.

Granted, this patch has not yet gone through the rigors of code review
so it will likely change, but I think that it is safe to say that such
a feature would be useful for more that just meson.

> file and then runs meson pointing to it.
> - Change meson to support pulling in env vars in meson.cross, and use
> a
> fixed meson.cross file that references the env vars.
> 
> On 01/17/2018 09:47 AM, Martin Kelly wrote:
> > Paul, any opinion?
> > 
> > On 01/12/2018 04:35 AM, Alexander Kanavin wrote:
> > > On 01/11/2018 09:22 PM, Martin Kelly wrote:
> > > > Khem and Alexander, could you comment on which solution is
> > > > preferable 
> > > > from an SDK standpoint? Otherwise, could you nominate someone
> > > > else to 
> > > > do so in your place? :)
> > > 
> > > I'm not sure who is the resident SDK expert, perhaps Paul
> > > Eggleton?
> > > 
> > > Alex
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Juro Bystricky
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 obtained from mtime of "autoconf.texi", unfortunately we patch this
file and change the mtime as a consequence.
The date serves as a document version identifier, so preserving the original 
mtime of
"autoconf.texi" would be misleading, as we actually did modify the document on 
purpose.
The fix is to set the mtime of "autoconf.texi" based on SOURCE_DATE_EPOCH.

[YOCTO #12524]

Signed-off-by: Juro Bystricky 
---
 meta/recipes-devtools/autoconf/autoconf.inc | 9 +
 1 file changed, 9 insertions(+)

diff --git a/meta/recipes-devtools/autoconf/autoconf.inc 
b/meta/recipes-devtools/autoconf/autoconf.inc
index df81bc6..f5156f7 100644
--- a/meta/recipes-devtools/autoconf/autoconf.inc
+++ b/meta/recipes-devtools/autoconf/autoconf.inc
@@ -48,6 +48,15 @@ do_configure() {
oe_runconf
 }
 
+do_compile_prepend_class-target() {
+   # mtime of autoconf.texi will end up as embedded date in autoconf.info.
+   # We patch autoconf.texi, so that modifies mtime each time.
+   # To ensure reproducibility, set the mtime to SOURCE_DATE_EPOCH
+   if [ -n "${SOURCE_DATE_EPOCH}" ]; then
+   touch -d @${SOURCE_DATE_EPOCH} ${S}/doc/autoconf.texi
+   fi
+}
+
 do_install_append() {
 rm -rf ${D}${datadir}/emacs
 }
-- 
2.7.4

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Martin Kelly

(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.
- Wrap meson with a shell script that dynamically generates a toolchain 
file and then runs meson pointing to it.

- Change meson to support pulling in env vars in meson.cross, and use a
fixed meson.cross file that references the env vars.

On 01/17/2018 09:47 AM, Martin Kelly wrote:

Paul, any opinion?

On 01/12/2018 04:35 AM, Alexander Kanavin wrote:

On 01/11/2018 09:22 PM, Martin Kelly wrote:
Khem and Alexander, could you comment on which solution is preferable 
from an SDK standpoint? Otherwise, could you nominate someone else to 
do so in your place? :)


I'm not sure who is the resident SDK expert, perhaps Paul Eggleton?

Alex

--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Martin Jansa
* 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].

* 
https://github.com/iputils/iputils/commit/f3a461603ef4fb7512ade3bdb73fe1824e294547

* fails with:
  | In file included from ping_common.c:1:0:
  | ping.h:39:10: fatal error: idna.h: No such file or directory
  |  #include 
  |   ^~~~

* Easiest way to reproduce this failure is to remove libidn from gnutls
  PACKAGECONFIG or to use gnutls which doesn't have libidn PACKAGECONFIG
  at all (like the one in meta-gplv2).

* First it leads to following QA issue:
  http://errors.yoctoproject.org/Errors/Build/53212/
  ERROR: iputils-s20161105-r0 do_package_qa: QA Issue: iputils-ping rdepends on 
libidn, but it isn't a build dependency, missing libidn in DEPENDS or 
PACKAGECONFIG? [build-deps]
  ERROR: iputils-s20161105-r0 do_package_qa: QA Issue: iputils-traceroute6 
rdepends on libidn, but it isn't a build dependency, missing libidn in DEPENDS 
or PACKAGECONFIG? [build-deps]
  ERROR: iputils-s20161105-r0 do_package_qa: QA run found fatal errors.
  Please consider fixing them.
  ERROR: iputils-s20161105-r0 do_package_qa: Function failed:
  do_package_qa
  ERROR: Logfile of failure stored in: 
/OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/iputils/s20161105-r0/temp/log.do_package_qa.7627
  ERROR: Task 
(/OE/build/oe-core/openembedded-core/meta/recipes-extended/iputils/iputils_s20161105.bb:do_package_qa)
 failed with exit code '1'

* But if you cleansstate iputils as well (after removing libidn from
  gnutls PACKAGECONFIG) to empty iputils RSS, then you get the error about
  missing idna.h:
  http://errors.yoctoproject.org/Errors/Build/53213/

* Adding the libidn dependency explicitly in iputils recipe fixes the
  issue.

Signed-off-by: Martin Jansa 
---
 meta/recipes-extended/iputils/iputils_s20161105.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-extended/iputils/iputils_s20161105.bb 
b/meta/recipes-extended/iputils/iputils_s20161105.bb
index ad7dbc4d4a..0acf2be5d3 100644
--- a/meta/recipes-extended/iputils/iputils_s20161105.bb
+++ b/meta/recipes-extended/iputils/iputils_s20161105.bb
@@ -11,7 +11,7 @@ LIC_FILES_CHKSUM = 
"file://ping.c;beginline=1;endline=35;md5=f9ceb201733e9a6cf8f
 
file://arping.c;beginline=1;endline=11;md5=fe84301b5c2655c950f8b92a057fafa6 \
 
file://tftpd.c;beginline=1;endline=32;md5=28834bf8a91a5b8a92755dbee709ef96 "
 
-DEPENDS = "gnutls libcap libgcrypt"
+DEPENDS = "gnutls libcap libgcrypt libidn"
 
 SRC_URI = "git://github.com/iputils/iputils \
file://0001-Fix-build-on-MUSL.patch \
-- 
2.15.1

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Martin Jansa
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].

https://github.com/iputils/iputils/commit/f3a461603ef4fb7512ade3bdb73fe1824e294547

Easiest way to reproduce this failure is to remove libidn from gnutls
PACKAGECONFIG or to use gnutls which doesn't have libidn PACKAGECONFIG at
all (like the one in meta-gplv2).

First it leads to following QA issue:
http://errors.yoctoproject.org/Errors/Build/53212/
ERROR: iputils-s20161105-r0 do_package_qa: QA Issue: iputils-ping rdepends
on libidn, but it isn't a build dependency, missing libidn in DEPENDS or
PACKAGECONFIG? [build-deps]
ERROR: iputils-s20161105-r0 do_package_qa: QA Issue: iputils-traceroute6
rdepends on libidn, but it isn't a build dependency, missing libidn in
DEPENDS or PACKAGECONFIG? [build-deps]
ERROR: iputils-s20161105-r0 do_package_qa: QA run found fatal errors.
Please consider fixing them.
ERROR: iputils-s20161105-r0 do_package_qa: Function failed: do_package_qa
ERROR: Logfile of failure stored in:
/OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/iputils/s20161105-r0/temp/log.do_package_qa.7627
ERROR: Task
(/OE/build/oe-core/openembedded-core/meta/recipes-extended/iputils/iputils_s20161105.bb:do_package_qa)
failed with exit code '1'

But if you cleansstate iputils as well (after removing libidn from gnutls
PACKAGECONFIG) to empty iputils RSS, then you get the error about missing
idna.h:
http://errors.yoctoproject.org/Errors/Build/53213/

Adding the libidn dependency explicitly in iputils recipe fixes the issue.

Regards,

On Tue, Feb 6, 2018 at 11:03 PM, Martin Jansa 
wrote:

> 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 just oe-core and nodistro to check if it
> fails the same there as well.
>
> Regards,
>
> On Tue, Feb 6, 2018 at 12:07 PM,  wrote:
>
>> This is an automated email from the git hooks/post-receive script.
>>
>> rpurdie pushed a commit to branch master
>> in repository openembedded-core.
>>
>> commit 5997981fa2c22609a88b8cbb595dbf7758b2f7c2
>> Author: Alexander Kanavin 
>> AuthorDate: Thu Feb 1 20:02:08 2018 +0200
>>
>> iputils: update to 20161105
>>
>> We've been using obsolete upstream URI for quite a while; meanwhile
>> a lot of development has happened
>>
>> Drop all the patches: they are either changing the code that has been
>> refactored,
>> or are backports.
>>
>> Add a new musl fix patch from gentoo.
>>
>> ping6 and tracepath6 variants have been folded into standard versions.
>>
>> Signed-off-by: Alexander Kanavin 
>> Signed-off-by: Ross Burton 
>> ---
>>  .../iputils/files/0001-Fix-build-on-MUSL.patch | 93
>> ++
>>  .../files/0001-Fix-header-inclusion-for-musl.patch | 92
>> -
>>  .../0001-Intialize-struct-elements-by-name.patch   | 52 
>>  ...ing-fix-arping-hang-if-SIGALRM-is-blocked.patch | 44 --
>>  .../iputils/files/debian/targets.diff  | 15 
>>  .../iputils/files/debian/use_gethostbyname2.diff   | 31 
>>  .../iputils/files/nsgmls-path-fix.patch| 27 ---
>>  .../{iputils_s20151218.bb => iputils_s20161105.bb} | 33 +++-
>>  8 files changed, 103 insertions(+), 284 deletions(-)
>>
>> diff --git a/meta/recipes-extended/iputils/files/0001-Fix-build-on-MUSL.patch
>> b/meta/recipes-extended/iputils/files/0001-Fix-build-on-MUSL.patch
>> new file mode 100644
>> index 000..c86dafc
>> --- /dev/null
>> +++ b/meta/recipes-extended/iputils/files/0001-Fix-build-on-MUSL.patch
>> @@ -0,0 +1,93 @@
>> +From c6c5966d9fae27bc2f0a34ab59b999555111bd2d Mon Sep 17 00:00:00 2001
>> +From: Aric Belsito 
>> +Date: Sun, 29 Oct 2017 23:17:03 +0100
>> +Subject: [PATCH] Fix build on MUSL
>> +
>> +Add missing AI_IDN and NI_IDN declarations.
>> +
>> +Bug: https://bugs.gentoo.org/503914
>> +Signed-off-by: Alexander Kanavin 
>> +---
>> + arping.c  |  7 +++
>> + ping.h| 11 +++
>> + tracepath.c   |  8 
>> + traceroute6.c |  4 
>> + 4 files changed, 30 insertions(+)
>> +
>> +diff --git a/arping.c b/arping.c
>> +index 1a3f40b..531d29d 100644
>> +--- a/arping.c
>>  b/arping.c
>> +@@ -45,6 +45,13 @@ struct sysfs_devattr_values;
>> + #ifdef USE_IDN
>> + #include 
>> + #include 
>> ++
>> ++#ifndef AI_IDN
>> ++#define AI_IDN 0x0040
>> ++#endif
>> ++#ifndef AI_CANONIDN
>> ++#define AI_CANONIDN 0x0080
>> ++#endif
>> + #endif
>> +
>> + #include "SNAPSHOT.h"
>> +diff --git a/ping.h b/ping.h
>> +index 749f3ff..227315f 100644
>> +--- a/ping.h
>>  b/ping.h
>> +@@ -38,6 +38,17 @@
>> + 

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

2018-02-06 Thread Patchwork
== 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 proposed
series by patchtest resulting in the following failures:



* Issue SUMMARY is missing in newly added recipe 
[test_summary_presence] 
  Suggested fixSpecify the variable SUMMARY in nativesdk-icecc-toolchain



If you believe any of these test results are incorrect, please reply to the
mailing list (openembedded-core@lists.openembedded.org) raising your concerns.
Otherwise we would appreciate you correcting the issues and submitting a new
version of the patchset if applicable. Please ensure you add/increment the
version number when sending the new version (i.e. [PATCH] -> [PATCH v2] ->
[PATCH v3] -> ...).

---
Guidelines: 
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Joshua Watt
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 
---
 .../icecc-create-env/icecc-create-env  | 110 ++---
 1 file changed, 54 insertions(+), 56 deletions(-)

diff --git 
a/meta/recipes-devtools/icecc-create-env/icecc-create-env/icecc-create-env 
b/meta/recipes-devtools/icecc-create-env/icecc-create-env/icecc-create-env
index 90d249df9f3..537e38a9ba0 100755
--- a/meta/recipes-devtools/icecc-create-env/icecc-create-env/icecc-create-env
+++ b/meta/recipes-devtools/icecc-create-env/icecc-create-env/icecc-create-env
@@ -4,7 +4,8 @@
 # Copyright (C) 2004 by the Icecream Authors
 # GPL
 
-target_files=
+target_paths=
+target_aliases=
 
 is_dynamic_elf ()
 {
@@ -32,15 +33,33 @@ fix_rpath ()
 fi
 }
 
-is_contained ()
+add_path ()
 {
-case " $target_files " in
-*" $1 "* ) return 0 ;;
-*"=$1 "* ) return 0;;
-* ) return 1 ;;
+case " $target_paths " in
+*" $1 "*)
+return 1
+;;
+*)
+target_paths="$target_paths $1"
+return 0
+;;
 esac
 }
 
+add_alias ()
+{
+if test "$1" != "$2"; then
+local alias="$1=$2"
+case " $target_aliases " in
+*" $alias "*)
+;;
+*)
+target_aliases="$target_aliases $alias"
+;;
+esac
+fi
+}
+
 normalize_path ()
 {
 # Normalizes the path to a file or directory, removing all "." and ".."
@@ -61,20 +80,17 @@ normalize_path ()
 
 add_file ()
 {
-local path=`normalize_path $1`
-local name="$path"
-if test -n "$2"; then
-name="$2"
-fi
-test -z "$name" && return
+local p=`normalize_path $1`
 # readlink is required for Yocto, so we can use it
-path=`readlink -f "$path"`
-toadd="$name=$path"
-is_contained "$toadd" && return
-if test -z "$silent"; then
-echo "adding file $toadd"
+local path=`readlink -f "$p"`
+
+add_alias "$path" "$p"
+if test -n "$2"; then
+add_alias "$path" "$2"
 fi
-target_files="$target_files $toadd"
+
+add_path "$path" || return
+
 if test -x "$path"; then
 # Only call ldd when it makes sense
 if is_dynamic_elf "$path"; then
@@ -208,52 +224,34 @@ link_rel ()
 }
 
 tempdir=`mktemp -d /tmp/iceccenvXX`
-new_target_files=
-for i in $target_files; do
-case $i in
-*=/*)
-target=`echo $i | cut -d= -f1`
-path=`echo $i | cut -d= -f2`
-;;
-*)
-path=$i
-target=$i
-;;
-esac
-if test "$target" == "$path"; then
-mkdir -p $tempdir/`dirname $target`
-cp -pH $target $tempdir/$target
-
-if test -f $tempdir/$target -a -x $tempdir/$target; then
-strip -s $tempdir/$target 2>/dev/null
-fi
-
-fix_rpath $tempdir/$target `dirname $target`
-else
-mkdir -p $tempdir/`dirname $path`
-cp -pH $path $tempdir/$path
+target_files=
+for path in $target_paths; do
+mkdir -p $tempdir/`dirname $path`
+cp -pH $path $tempdir/$path
 
-mkdir -p $tempdir/`dirname $target`
-# Relative links are used because the files are checked for being
-# executable outside the chroot
-link_rel $path $target $tempdir
+if test -f $tempdir/$path -a -x $tempdir/$path; then
+strip -s $tempdir/$path 2>/dev/null
+fi
 
-if test -f $tempdir/$path -a -x $tempdir/$path; then
-strip -s $tempdir/$path 2>/dev/null
-fi
+fix_rpath $tempdir/$path `dirname $path`
+target_files="$target_files $path"
+done
 
-fix_rpath $tempdir/$path `dirname $path`
+for i in $target_aliases; do
+target=`echo $i | cut -d= -f1`
+link_name=`echo $i | cut -d= -f2`
 
-path=`echo $path | cut -b2-`
-new_target_files="$new_target_files $path"
-fi
+mkdir -p $tempdir/`dirname $link_name`
+# Relative links are used because the files are checked for being
+# executable outside the chroot
+link_rel $target $link_name $tempdir
 
-target=`echo $target | cut -b2-`
-new_target_files="$new_target_files $target"
+link_name=`echo $link_name | cut -b2-`
+target_files="$target_files $link_name"
 done
 
 #sort the files
-target_files=`for i in $new_target_files; do echo $i; done | sort`
+target_files=`for i in $target_files; do echo $i; done | sort`
 
 #test if an archive name was supplied
 #if not use the md5 of all files as the archive name
-- 
2.14.3

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Joshua Watt
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 a/meta/classes/icecc.bbclass b/meta/classes/icecc.bbclass
index 9d5eaed57ce..8492ece60c3 100644
--- a/meta/classes/icecc.bbclass
+++ b/meta/classes/icecc.bbclass
@@ -346,3 +346,10 @@ do_compile_kernelmodules_prepend() {
 do_install_prepend() {
 set_icecc_env
 }
+
+# IceCream is not (currently) supported in the extensible SDK
+ICECC_SDK_HOST_TASK = "nativesdk-icecc-toolchain"
+ICECC_SDK_HOST_TASK_task-populate-sdk-ext = ""
+
+# Add the toolchain scripts to the SDK
+TOOLCHAIN_HOST_TASK_append = " ${ICECC_SDK_HOST_TASK}"
-- 
2.14.3

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Joshua Watt
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 
---
 .../icecc-toolchain/icecc-toolchain/icecc-env.sh   | 37 +++
 .../icecc-toolchain/icecc-toolchain/icecc-setup.sh | 43 ++
 .../nativesdk-icecc-toolchain_0.1.bb   | 38 +++
 3 files changed, 118 insertions(+)
 create mode 100644 
meta/recipes-devtools/icecc-toolchain/icecc-toolchain/icecc-env.sh
 create mode 100644 
meta/recipes-devtools/icecc-toolchain/icecc-toolchain/icecc-setup.sh
 create mode 100644 
meta/recipes-devtools/icecc-toolchain/nativesdk-icecc-toolchain_0.1.bb

diff --git a/meta/recipes-devtools/icecc-toolchain/icecc-toolchain/icecc-env.sh 
b/meta/recipes-devtools/icecc-toolchain/icecc-toolchain/icecc-env.sh
new file mode 100644
index 000..4c34edbbc5d
--- /dev/null
+++ b/meta/recipes-devtools/icecc-toolchain/icecc-toolchain/icecc-env.sh
@@ -0,0 +1,37 @@
+#! /bin/sh
+# Copyright 2018 Garmin Ltd. or its subsidiaries
+#
+# Permission is hereby granted, free of charge, to any person obtaining a copy
+# of this software and associated documentation files (the "Software"), to deal
+# in the Software without restriction, including without limitation the rights
+# to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+# copies of the Software, and to permit persons to whom the Software is
+# furnished to do so, subject to the following conditions:
+#
+# The above copyright notice and this permission notice shall be included in
+# all copies or substantial portions of the Software.
+#
+# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+# AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+# LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+# OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+# SOFTWARE.
+#
+
+if [ -z "$ICECC_PATH" ]; then
+ICECC_PATH=$(which icecc 2> /dev/null)
+fi
+
+if [ -n "$ICECC_PATH" ]; then
+export ICECC_PATH
+export 
ICECC_VERSION="$OECORE_NATIVE_SYSROOT/usr/share/icecream/@TOOLCHAIN_ENV@"
+export ICECC="$(which ${CROSS_COMPILE}gcc)"
+export ICECXX="$(which ${CROSS_COMPILE}g++)"
+export ICEAS="$(which ${CROSS_COMPILE}as)"
+export PATH="$OECORE_NATIVE_SYSROOT/usr/share/icecream/bin:$PATH"
+else
+echo "Icecc not found. Disabling distributed compiling"
+fi
+
diff --git 
a/meta/recipes-devtools/icecc-toolchain/icecc-toolchain/icecc-setup.sh 
b/meta/recipes-devtools/icecc-toolchain/icecc-toolchain/icecc-setup.sh
new file mode 100644
index 000..a433e55b029
--- /dev/null
+++ b/meta/recipes-devtools/icecc-toolchain/icecc-toolchain/icecc-setup.sh
@@ -0,0 +1,43 @@
+#! /bin/sh
+# Copyright 2018 Garmin Ltd. or its subsidiaries
+#
+# Permission is hereby granted, free of charge, to any person obtaining a copy
+# of this software and associated documentation files (the "Software"), to deal
+# in the Software without restriction, including without limitation the rights
+# to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+# copies of the Software, and to permit persons to whom the Software is
+# furnished to do so, subject to the following conditions:
+#
+# The above copyright notice and this permission notice shall be included in
+# all copies or substantial portions of the Software.
+#
+# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+# AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+# LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+# OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+# SOFTWARE.
+#
+
+# Setup environment
+for env_setup_script in `ls $1/environment-setup-*`; do
+   . $env_setup_script
+done
+
+# ICECC_PATH will have been found icecc-env.sh
+if [ -z "$ICECC_PATH" ]; then
+exit 0
+fi
+
+echo "Setting up IceCream distributed compiling..."
+
+# Create the environment
+mkdir -p "`dirname $ICECC_VERSION`"
+icecc-create-env $ICECC $ICECXX $ICEAS $ICECC_VERSION || exit $?
+
+# Create symbolic links
+d="$OECORE_NATIVE_SYSROOT/usr/share/icecream/bin"
+mkdir -p "$d"
+ln -s "$ICECC_PATH" "$d/${CROSS_COMPILE}gcc"
+ln -s "$ICECC_PATH" "$d/${CROSS_COMPILE}g++"
diff --git 
a/meta/recipes-devtools/icecc-toolchain/nativesdk-icecc-toolchain_0.1.bb 
b/meta/recipes-devtools/icecc-toolchain/nativesdk-icecc-toolchain_0.1.bb
new file mode 100644
index 00

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

2018-02-06 Thread Joshua Watt
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(-)
 rename meta/recipes-devtools/icecc-create-env/{icecc-create-env-native_0.1.bb 
=> icecc-create-env_0.1.bb} (98%)

diff --git 
a/meta/recipes-devtools/icecc-create-env/icecc-create-env-native_0.1.bb 
b/meta/recipes-devtools/icecc-create-env/icecc-create-env_0.1.bb
similarity index 98%
rename from 
meta/recipes-devtools/icecc-create-env/icecc-create-env-native_0.1.bb
rename to meta/recipes-devtools/icecc-create-env/icecc-create-env_0.1.bb
index f8f4aef3923..053945ebbc6 100644
--- a/meta/recipes-devtools/icecc-create-env/icecc-create-env-native_0.1.bb
+++ b/meta/recipes-devtools/icecc-create-env/icecc-create-env_0.1.bb
@@ -12,8 +12,6 @@ PR = "r2"
 DEPENDS = ""
 INHIBIT_DEFAULT_DEPS = "1"
 
-inherit native
-
 # This is needed, because otherwise there is dependency loop from quilt-native
 # Dependency loop #1 found:
 #  Task 10907 (meta/recipes-devtools/quilt/quilt-native_0.60.bb, do_install) 
(dependent Tasks ['quilt-native, do_compile'])
@@ -34,3 +32,5 @@ do_install() {
 install -d ${D}/${bindir}
 install -m 0755 ${WORKDIR}/icecc-create-env ${D}/${bindir}
 }
+
+BBCLASSEXTEND = "native nativesdk"
-- 
2.14.3

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Joshua Watt
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 
 meta/recipes-core/meta/meta-environment.bb |  2 ++
 3 files changed, 25 insertions(+)

diff --git a/meta/classes/toolchain-scripts.bbclass 
b/meta/classes/toolchain-scripts.bbclass
index 9bcfe708c7c..eeb320d15a8 100644
--- a/meta/classes/toolchain-scripts.bbclass
+++ b/meta/classes/toolchain-scripts.bbclass
@@ -116,6 +116,21 @@ fi
 EOF
 }
 
+toolchain_create_post_relocate_script() {
+   script=$1
+   rm -f $script
+   touch $script
+
+cat >> $script 

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

2018-02-06 Thread Joshua Watt
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 dependencies.

Signed-off-by: Joshua Watt 
---
 .../icecc-create-env/icecc-create-env| 20 +---
 1 file changed, 17 insertions(+), 3 deletions(-)

diff --git 
a/meta/recipes-devtools/icecc-create-env/icecc-create-env/icecc-create-env 
b/meta/recipes-devtools/icecc-create-env/icecc-create-env/icecc-create-env
index c838256f748..7636d090a48 100755
--- a/meta/recipes-devtools/icecc-create-env/icecc-create-env/icecc-create-env
+++ b/meta/recipes-devtools/icecc-create-env/icecc-create-env/icecc-create-env
@@ -6,6 +6,12 @@
 
 target_files=
 
+is_dynamic_elf ()
+{
+# Is the file an dynamically linked ELF executable?
+(file -L "$1" | grep 'ELF' > /dev/null 2>&1) && (! file -L "$1" | grep 
'static' > /dev/null 2>&1)
+}
+
 is_contained ()
 {
 case " $target_files " in
@@ -34,8 +40,16 @@ add_file ()
 target_files="$target_files $toadd"
 if test -x "$path"; then
 # Only call ldd when it makes sense
-if file -L "$path" | grep 'ELF' > /dev/null 2>&1; then
-if ! file -L "$path" | grep 'static' > /dev/null 2>&1; then
+if is_dynamic_elf "$path"; then
+# Request the program interpeter (dynamic loader)
+interp=`readelf -w -l "$path" | grep "Requesting program 
interpreter:" | sed "s/\s*\[Requesting program interpreter:\s*\(.*\)\]/\1/g"`
+
+if test -n "$interp" && test -x "$interp"; then
+# Use the dynamic loaders --list argument to list the
+# depenencies. The program may have a a different program
+# interpeter (typical when using uninative tarballs), which is
+# why we can't just call ldd.
+#
 # ldd now outputs ld as /lib/ld-linux.so.xx on current nptl 
based glibc
 # this regexp parse the outputs like:
 # ldd /usr/bin/gcc
@@ -43,7 +57,7 @@ add_file ()
 # libc.so.6 => /lib/tls/libc.so.6 (0xb7e81000)
 # /lib/ld-linux.so.2 (0xb7fe8000)
 # covering both situations ( with => and without )
-for lib in `ldd "$path" | sed -n 's,^[^/]*\(/[^ ]*\).*,\1,p'`; 
do
+for lib in `$interp --list "$path" | sed -n 's,^[^/]*\(/[^ 
]*\).*,\1,p'`; do
 test -f "$lib" || continue
 # Check wether the same library also exists in the parent 
directory,
 # and prefer that on the assumption that it is a more 
generic one.
-- 
2.14.3

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Joshua Watt
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 to what was previously generated.

In addition, symbolic links are no longer dereferenced when creating the
archive, as they are purposely included to provide alternate names for
files

Signed-off-by: Joshua Watt 
---
 .../icecc-create-env/icecc-create-env/icecc-create-env  | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git 
a/meta/recipes-devtools/icecc-create-env/icecc-create-env/icecc-create-env 
b/meta/recipes-devtools/icecc-create-env/icecc-create-env/icecc-create-env
index 0791bd54b27..426b093d91c 100755
--- a/meta/recipes-devtools/icecc-create-env/icecc-create-env/icecc-create-env
+++ b/meta/recipes-devtools/icecc-create-env/icecc-create-env/icecc-create-env
@@ -256,7 +256,11 @@ if test -z "$silent"; then
 fi
 
 cd $tempdir
-tar -czhf "$mydir/$archive_name" $target_files || {
+# Add everything in the temp directory. Tar doesn't like to be given files with
+# ".." in them, which frequently happens in $target_files, and will strip off
+# the path prefix past the offending "..". This makes the archive generate
+# incorrectly
+tar -czf "$mydir/$archive_name" . || {
 if test -z "$silent"; then
 echo "Couldn't create archive"
 fi
-- 
2.14.3

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Joshua Watt
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 unable to resolve $ORIGIN resulting in a failure
to find dynamic libraries.

The fix is to replace $ORIGIN in executable RPATH entries with the known
chroot executable path.  In order for this to work, the actual real path
to the executable must be resolved to remove any symlinks, otherwise the
calculate $ORIGIN replacement will be wrong. This is done by using
"readlink -f", which is an acceptable dependency because Yocto already
requires it.

Signed-off-by: Joshua Watt 
---
 .../icecc-create-env/icecc-create-env  | 40 --
 1 file changed, 37 insertions(+), 3 deletions(-)

diff --git 
a/meta/recipes-devtools/icecc-create-env/icecc-create-env/icecc-create-env 
b/meta/recipes-devtools/icecc-create-env/icecc-create-env/icecc-create-env
index 426b093d91c..90d249df9f3 100755
--- a/meta/recipes-devtools/icecc-create-env/icecc-create-env/icecc-create-env
+++ b/meta/recipes-devtools/icecc-create-env/icecc-create-env/icecc-create-env
@@ -12,6 +12,26 @@ is_dynamic_elf ()
 (file -L "$1" | grep 'ELF' > /dev/null 2>&1) && (! file -L "$1" | grep 
'static' > /dev/null 2>&1)
 }
 
+fix_rpath ()
+{
+# Patches the RPATH for a file. When the program is executed in the chroot
+# be iceccd, /proc is not mounted. As such, $ORIGIN can't be resolved. To
+# work around this, replace all instances of $ORIGIN in RPATH with the
+# known chroot path to the executables directory
+local path="$1"
+local origin="$2"
+if ! is_dynamic_elf "$path"; then
+return
+fi
+local new_rpath="`readelf -w -d "$path" | grep RPATH | \
+sed 's/.*\[\(.*\)\]/\1/g' | \
+sed "s,\\\$ORIGIN,/$origin,g"`"
+
+if test -n "$new_rpath"; then
+$PATCHELF --set-rpath "$new_rpath" "$path"
+fi
+}
+
 is_contained ()
 {
 case " $target_files " in
@@ -47,9 +67,8 @@ add_file ()
 name="$2"
 fi
 test -z "$name" && return
-# ls -H isn't really the same as readlink, but
-# readlink is not portable enough.
-path=`ls -H $path`
+# readlink is required for Yocto, so we can use it
+path=`readlink -f "$path"`
 toadd="$name=$path"
 is_contained "$toadd" && return
 if test -z "$silent"; then
@@ -108,6 +127,17 @@ added_as=$1
 shift
 archive_name=$1
 
+if test -z "$PATCHELF"; then
+PATCHELF=`which patchelf 2> /dev/null`
+fi
+if test -z "$PATCHELF"; then
+PATCHELF=`which patchelf-uninative 2> /dev/null`
+fi
+if test -z "$PATCHELF"; then
+echo "patchelf is required"
+exit 1
+fi
+
 if test -z "$added_gcc" || test -z "$added_gxx" ; then
 echo "usage: $0  "
 exit 1
@@ -197,6 +227,8 @@ for i in $target_files; do
 if test -f $tempdir/$target -a -x $tempdir/$target; then
 strip -s $tempdir/$target 2>/dev/null
 fi
+
+fix_rpath $tempdir/$target `dirname $target`
 else
 mkdir -p $tempdir/`dirname $path`
 cp -pH $path $tempdir/$path
@@ -210,6 +242,8 @@ for i in $target_files; do
 strip -s $tempdir/$path 2>/dev/null
 fi
 
+fix_rpath $tempdir/$path `dirname $path`
+
 path=`echo $path | cut -b2-`
 new_target_files="$new_target_files $path"
 fi
-- 
2.14.3

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Joshua Watt
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 +++---
 1 file changed, 57 insertions(+), 7 deletions(-)

diff --git 
a/meta/recipes-devtools/icecc-create-env/icecc-create-env/icecc-create-env 
b/meta/recipes-devtools/icecc-create-env/icecc-create-env/icecc-create-env
index 7636d090a48..0791bd54b27 100755
--- a/meta/recipes-devtools/icecc-create-env/icecc-create-env/icecc-create-env
+++ b/meta/recipes-devtools/icecc-create-env/icecc-create-env/icecc-create-env
@@ -21,10 +21,28 @@ is_contained ()
 esac
 }
 
+normalize_path ()
+{
+# Normalizes the path to a file or directory, removing all "." and ".."
+# entries. Use pwd -L to explicitly prevent symlink expansion
+local path=$1
+if test -f "$path"; then
+pushd $(dirname $path) > /dev/null 2>&1
+dir_path=$(pwd -L)
+path=$dir_path/$(basename $path)
+popd > /dev/null 2>&1
+elif test -d "$path"; then
+pushd $path > /dev/null 2>&1
+path=$(pwd -L)
+popd > /dev/null 2>&1
+fi
+echo $path
+}
+
 add_file ()
 {
-local name="$1"
-local path="$1";
+local path=`normalize_path $1`
+local name="$path"
 if test -n "$2"; then
 name="$2"
 fi
@@ -129,7 +147,7 @@ if test -n "$specfile" && test -e "$specfile"; then
 fi
 
 ltofile=`$added_gcc -print-prog-name=lto1`
-pluginfile="${ltofile%lto1}liblto_plugin.so"
+pluginfile=`normalize_path "${ltofile%lto1}liblto_plugin.so"`
 if test -r "$pluginfile"
 then
 add_file $pluginfile  ${pluginfile#*usr}
@@ -146,6 +164,19 @@ else
 exit 1
 fi
 
+link_rel ()
+{
+local target="$1"
+local name="$2"
+local base="$3"
+
+local prefix=`dirname $name`
+
+prefix=`echo $prefix | sed 's,[^/]\+,..,g' | sed 's,^/*,,g'`
+
+ln -s $prefix/$target $base/$name
+}
+
 tempdir=`mktemp -d /tmp/iceccenvXX`
 new_target_files=
 for i in $target_files; do
@@ -159,11 +190,30 @@ for i in $target_files; do
 target=$i
 ;;
 esac
-mkdir -p $tempdir/`dirname $target`
-cp -p $path $tempdir/$target
-if test -f $tempdir/$target -a -x $tempdir/$target; then
-strip -s $tempdir/$target 2>/dev/null
+if test "$target" == "$path"; then
+mkdir -p $tempdir/`dirname $target`
+cp -pH $target $tempdir/$target
+
+if test -f $tempdir/$target -a -x $tempdir/$target; then
+strip -s $tempdir/$target 2>/dev/null
+fi
+else
+mkdir -p $tempdir/`dirname $path`
+cp -pH $path $tempdir/$path
+
+mkdir -p $tempdir/`dirname $target`
+# Relative links are used because the files are checked for being
+# executable outside the chroot
+link_rel $path $target $tempdir
+
+if test -f $tempdir/$path -a -x $tempdir/$path; then
+strip -s $tempdir/$path 2>/dev/null
+fi
+
+path=`echo $path | cut -b2-`
+new_target_files="$new_target_files $path"
 fi
+
 target=`echo $target | cut -b2-`
 new_target_files="$new_target_files $target"
 done
-- 
2.14.3

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Joshua Watt
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 insertions(+)

diff --git 
a/meta/recipes-devtools/icecc-create-env/icecc-create-env/icecc-create-env 
b/meta/recipes-devtools/icecc-create-env/icecc-create-env/icecc-create-env
index 723f1f9bd90..c838256f748 100755
--- a/meta/recipes-devtools/icecc-create-env/icecc-create-env/icecc-create-env
+++ b/meta/recipes-devtools/icecc-create-env/icecc-create-env/icecc-create-env
@@ -122,6 +122,16 @@ then
 add_file $pluginfile  /usr${pluginfile#*usr}
 fi
 
+# for testing the environment is usable at all
+if test -x /bin/true; then
+add_file /bin/true
+elif test -x /usr/bin/true; then
+add_file /usr/bin/true /bin/true
+else
+echo "'true' not found"
+exit 1
+fi
+
 tempdir=`mktemp -d /tmp/iceccenvXX`
 new_target_files=
 for i in $target_files; do
-- 
2.14.3

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Joshua Watt
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: Joshua Watt 
---
 .../icecc-create-env/icecc-create-env  | 208 ++---
 1 file changed, 104 insertions(+), 104 deletions(-)

diff --git 
a/meta/recipes-devtools/icecc-create-env/icecc-create-env/icecc-create-env 
b/meta/recipes-devtools/icecc-create-env/icecc-create-env/icecc-create-env
index 7e4dbc414e7..723f1f9bd90 100755
--- a/meta/recipes-devtools/icecc-create-env/icecc-create-env/icecc-create-env
+++ b/meta/recipes-devtools/icecc-create-env/icecc-create-env/icecc-create-env
@@ -8,63 +8,63 @@ target_files=
 
 is_contained ()
 {
-  case " $target_files " in
-*" $1 "* ) return 0 ;;
-*"=$1 "* ) return 0;;
-* ) return 1 ;;
-  esac
+case " $target_files " in
+*" $1 "* ) return 0 ;;
+*"=$1 "* ) return 0;;
+* ) return 1 ;;
+esac
 }
 
 add_file ()
 {
-  local name="$1"
-  local path="$1";
-  if test -n "$2"; then
-name="$2"
-  fi
-  test -z "$name" && return
-  # ls -H isn't really the same as readlink, but
-  # readlink is not portable enough.
-  path=`ls -H $path`
-  toadd="$name=$path"
-  is_contained "$toadd" && return
-  if test -z "$silent"; then
-  echo "adding file $toadd"
-  fi
-  target_files="$target_files $toadd"
-  if test -x "$path"; then
-# Only call ldd when it makes sense
-if file -L "$path" | grep 'ELF' > /dev/null 2>&1; then
-   if ! file -L "$path" | grep 'static' > /dev/null 2>&1; then
-  # ldd now outputs ld as /lib/ld-linux.so.xx on current nptl based 
glibc
-   # this regexp parse the outputs like:
-   # ldd /usr/bin/gcc
-   # linux-gate.so.1 =>  (0xe000)
-   # libc.so.6 => /lib/tls/libc.so.6 (0xb7e81000)
-   # /lib/ld-linux.so.2 (0xb7fe8000)
-   # covering both situations ( with => and without )
-  for lib in `ldd "$path" | sed -n 's,^[^/]*\(/[^ ]*\).*,\1,p'`; do
-   test -f "$lib" || continue
-   # Check wether the same library also exists in the parent directory,
-   # and prefer that on the assumption that it is a more generic one.
-   local baselib=`echo "$lib" | sed 's,\(/[^/]*\)/.*\(/[^/]*\)$,\1\2,'`
-   test -f "$baselib" && lib=$baselib
- add_file "$lib"
-done
-  fi
+local name="$1"
+local path="$1";
+if test -n "$2"; then
+name="$2"
+fi
+test -z "$name" && return
+# ls -H isn't really the same as readlink, but
+# readlink is not portable enough.
+path=`ls -H $path`
+toadd="$name=$path"
+is_contained "$toadd" && return
+if test -z "$silent"; then
+echo "adding file $toadd"
+fi
+target_files="$target_files $toadd"
+if test -x "$path"; then
+# Only call ldd when it makes sense
+if file -L "$path" | grep 'ELF' > /dev/null 2>&1; then
+if ! file -L "$path" | grep 'static' > /dev/null 2>&1; then
+# ldd now outputs ld as /lib/ld-linux.so.xx on current nptl 
based glibc
+# this regexp parse the outputs like:
+# ldd /usr/bin/gcc
+# linux-gate.so.1 =>  (0xe000)
+# libc.so.6 => /lib/tls/libc.so.6 (0xb7e81000)
+# /lib/ld-linux.so.2 (0xb7fe8000)
+# covering both situations ( with => and without )
+for lib in `ldd "$path" | sed -n 's,^[^/]*\(/[^ ]*\).*,\1,p'`; 
do
+test -f "$lib" || continue
+# Check wether the same library also exists in the parent 
directory,
+# and prefer that on the assumption that it is a more 
generic one.
+local baselib=`echo "$lib" | sed 
's,\(/[^/]*\)/.*\(/[^/]*\)$,\1\2,'`
+test -f "$baselib" && lib=$baselib
+add_file "$lib"
+done
+fi
+fi
 fi
-  fi
 }
 
 # backward compat
 if test "$1" = "--respect-path"; then
-  shift
+shift
 fi
 
 #add a --silent switch to avoid "broken pipe" errors when calling this scipt 
from within OE
 if test "$1" = "--silent"; then
- silent=1
- shift
+silent=1
+shift
 fi
 
 
@@ -77,18 +77,18 @@ shift
 archive_name=$1
 
 if test -z "$added_gcc" || test -z "$added_gxx" ; then
-   echo "usage: $0  "
-   exit 1
+echo "usage: $0  "
+exit 1
 fi
 
 if ! test -x "$added_gcc" ; then
-  echo "'$added_gcc' is no executable."
-  exit 1
+echo "'$added_gcc' is no executable."
+exit 1
 fi
 
 if ! test -x "$added_gxx" ; then
-  echo "'$added_gcc' is no executable."
-  exit 1
+echo "'$added_gcc' is no executable."
+exit 1
 fi
 
 
@@ -97,51 +97,51 @@ add_file 

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

2018-02-06 Thread Joshua Watt
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 insertions(+), 9 deletions(-)

diff --git a/meta/classes/icecc.bbclass b/meta/classes/icecc.bbclass
index e8725b582b3..35a1aaef86f 100644
--- a/meta/classes/icecc.bbclass
+++ b/meta/classes/icecc.bbclass
@@ -210,15 +210,14 @@ def icecc_get_tool(bb, d, tool):
 else:
 ice_dir = d.expand('${STAGING_BINDIR_TOOLCHAIN}')
 target_sys = d.expand('${TARGET_SYS}')
-tool_bin = os.path.join(ice_dir, "%s-%s" % (target_sys, tool))
-if os.path.isfile(tool_bin):
-return tool_bin
-else:
-external_tool_bin = icecc_get_external_tool(bb, d, tool)
-if os.path.isfile(external_tool_bin):
-return external_tool_bin
-else:
-return ""
+for p in ice_dir.split(':'):
+tool_bin = os.path.join(p, "%s-%s" % (target_sys, tool))
+if os.path.isfile(tool_bin):
+return tool_bin
+external_tool_bin = icecc_get_external_tool(bb, d, tool)
+if os.path.isfile(external_tool_bin):
+return external_tool_bin
+return ""
 
 def icecc_get_and_check_tool(bb, d, tool):
 # Check that g++ or gcc is not a symbolic link to icecc binary in
-- 
2.14.3

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Joshua Watt
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 is probably not worth maintaining.

Signed-off-by: Joshua Watt 
---
 meta/classes/icecc.bbclass | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/meta/classes/icecc.bbclass b/meta/classes/icecc.bbclass
index 35a1aaef86f..9d5eaed57ce 100644
--- a/meta/classes/icecc.bbclass
+++ b/meta/classes/icecc.bbclass
@@ -101,6 +101,9 @@ def use_icecc(bb,d):
 if icecc_is_allarch(bb, d):
 return "no"
 
+if icecc_is_cross_canadian(bb, d):
+return "no"
+
 pn = d.getVar('PN')
 
 system_class_blacklist = []
@@ -151,6 +154,9 @@ def icecc_is_native(bb, d):
 bb.data.inherits_class("cross", d) or \
 bb.data.inherits_class("native", d);
 
+def icecc_is_cross_canadian(bb, d):
+return bb.data.inherits_class("cross-canadian", d)
+
 def icecc_dir(bb, d):
 return d.expand('${TMPDIR}/work-shared/ice')
 
-- 
2.14.3

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Joshua Watt
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 sense for each recipe to generate a toolchain,
only to find it has already generated an uploaded to the compile server
by another recipe.

Signed-off-by: Joshua Watt 
---
 meta/classes/icecc.bbclass | 7 +--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/meta/classes/icecc.bbclass b/meta/classes/icecc.bbclass
index 1cc1c4ddb0f..e8725b582b3 100644
--- a/meta/classes/icecc.bbclass
+++ b/meta/classes/icecc.bbclass
@@ -151,6 +151,9 @@ def icecc_is_native(bb, d):
 bb.data.inherits_class("cross", d) or \
 bb.data.inherits_class("native", d);
 
+def icecc_dir(bb, d):
+return d.expand('${TMPDIR}/work-shared/ice')
+
 # Don't pollute allarch signatures with TARGET_FPU
 icecc_version[vardepsexclude] += "TARGET_FPU"
 def icecc_version(bb, d):
@@ -175,8 +178,8 @@ def icecc_version(bb, d):
 archive_name += "-kernel"
 
 import socket
-ice_dir = d.expand('${STAGING_DIR_NATIVE}${prefix_native}')
-tar_file = os.path.join(ice_dir, 'ice', archive_name + "-@VERSION@-" + 
socket.gethostname() + '.tar.gz')
+ice_dir = icecc_dir(bb, d)
+tar_file = os.path.join(ice_dir, archive_name + "-@VERSION@-" + 
socket.gethostname() + '.tar.gz')
 
 return tar_file
 
-- 
2.14.3

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Martin Jansa
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 just oe-core and nodistro to check if it
fails the same there as well.

Regards,

On Tue, Feb 6, 2018 at 12:07 PM,  wrote:

> This is an automated email from the git hooks/post-receive script.
>
> rpurdie pushed a commit to branch master
> in repository openembedded-core.
>
> commit 5997981fa2c22609a88b8cbb595dbf7758b2f7c2
> Author: Alexander Kanavin 
> AuthorDate: Thu Feb 1 20:02:08 2018 +0200
>
> iputils: update to 20161105
>
> We've been using obsolete upstream URI for quite a while; meanwhile
> a lot of development has happened
>
> Drop all the patches: they are either changing the code that has been
> refactored,
> or are backports.
>
> Add a new musl fix patch from gentoo.
>
> ping6 and tracepath6 variants have been folded into standard versions.
>
> Signed-off-by: Alexander Kanavin 
> Signed-off-by: Ross Burton 
> ---
>  .../iputils/files/0001-Fix-build-on-MUSL.patch | 93
> ++
>  .../files/0001-Fix-header-inclusion-for-musl.patch | 92
> -
>  .../0001-Intialize-struct-elements-by-name.patch   | 52 
>  ...ing-fix-arping-hang-if-SIGALRM-is-blocked.patch | 44 --
>  .../iputils/files/debian/targets.diff  | 15 
>  .../iputils/files/debian/use_gethostbyname2.diff   | 31 
>  .../iputils/files/nsgmls-path-fix.patch| 27 ---
>  .../{iputils_s20151218.bb => iputils_s20161105.bb} | 33 +++-
>  8 files changed, 103 insertions(+), 284 deletions(-)
>
> diff --git a/meta/recipes-extended/iputils/files/0001-Fix-build-on-MUSL.patch
> b/meta/recipes-extended/iputils/files/0001-Fix-build-on-MUSL.patch
> new file mode 100644
> index 000..c86dafc
> --- /dev/null
> +++ b/meta/recipes-extended/iputils/files/0001-Fix-build-on-MUSL.patch
> @@ -0,0 +1,93 @@
> +From c6c5966d9fae27bc2f0a34ab59b999555111bd2d Mon Sep 17 00:00:00 2001
> +From: Aric Belsito 
> +Date: Sun, 29 Oct 2017 23:17:03 +0100
> +Subject: [PATCH] Fix build on MUSL
> +
> +Add missing AI_IDN and NI_IDN declarations.
> +
> +Bug: https://bugs.gentoo.org/503914
> +Signed-off-by: Alexander Kanavin 
> +---
> + arping.c  |  7 +++
> + ping.h| 11 +++
> + tracepath.c   |  8 
> + traceroute6.c |  4 
> + 4 files changed, 30 insertions(+)
> +
> +diff --git a/arping.c b/arping.c
> +index 1a3f40b..531d29d 100644
> +--- a/arping.c
>  b/arping.c
> +@@ -45,6 +45,13 @@ struct sysfs_devattr_values;
> + #ifdef USE_IDN
> + #include 
> + #include 
> ++
> ++#ifndef AI_IDN
> ++#define AI_IDN 0x0040
> ++#endif
> ++#ifndef AI_CANONIDN
> ++#define AI_CANONIDN 0x0080
> ++#endif
> + #endif
> +
> + #include "SNAPSHOT.h"
> +diff --git a/ping.h b/ping.h
> +index 749f3ff..227315f 100644
> +--- a/ping.h
>  b/ping.h
> +@@ -38,6 +38,17 @@
> + #include 
> + #include 
> + #include 
> ++
> ++#ifndef AI_IDN
> ++#define AI_IDN 0x0040
> ++#endif
> ++#ifndef AI_CANONIDN
> ++#define AI_CANONIDN 0x0080
> ++#endif
> ++#ifndef NI_IDN
> ++#define NI_IDN 32
> ++#endif
> ++
> + #define getaddrinfo_flags (AI_CANONNAME | AI_IDN | AI_CANONIDN)
> + #define getnameinfo_flags NI_IDN
> + #else
> +diff --git a/tracepath.c b/tracepath.c
> +index 74a829d..dcec5b9 100644
> +--- a/tracepath.c
>  b/tracepath.c
> +@@ -30,6 +30,14 @@
> + #ifdef USE_IDN
> + #include 
> + #include 
> ++
> ++#ifndef AI_IDN
> ++#define AI_IDN 0x0040
> ++#endif
> ++#ifndef NI_IDN
> ++#define NI_IDN 32
> ++#endif
> ++
> + #define getnameinfo_flags NI_IDN
> + #else
> + #define getnameinfo_flags 0
> +diff --git a/traceroute6.c b/traceroute6.c
> +index 48fc5c5..8d1eebf 100644
> +--- a/traceroute6.c
>  b/traceroute6.c
> +@@ -251,6 +251,10 @@
> + #include 
> + #include 
> +
> ++#ifndef NI_IDN
> ++#define NI_IDN 32
> ++#endif
> ++
> + #define getnameinfo_flags NI_IDN
> + #else
> + #define getnameinfo_flags 0
> +--
> +2.15.1
> +
> diff --git 
> a/meta/recipes-extended/iputils/files/0001-Fix-header-inclusion-for-musl.patch
> b/meta/recipes-extended/iputils/files/0001-Fix-header-
> inclusion-for-musl.patch
> deleted file mode 100644
> index 20ef07e..000
> --- a/meta/recipes-extended/iputils/files/0001-Fix-header-
> inclusion-for-musl.patch
> +++ /dev/null
> @@ -1,92 +0,0 @@
> -From be0bb81d72fea4d20da74f4f2236aa145684f332 Mon Sep 17 00:00:00 2001
> -From: Khem Raj 
> -Date: Wed, 6 Jan 2016 14:14:22 -0800
> -Subject: [PATCH] Fix header inclusion for musl
> -
> -Fix errors e.g.
> -
> -In file included from tracepath.c:17:0:
> -/usr/include/linux/errqueue.h:33:18:
> -error: array type has incomplete element type 'struct timespec'
> -  struct timespec ts[3];
> -  ^
> -tracepath.c: In function 'main':
> -tracepath.c:329:16: error: 'INT_MAX

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

2018-02-06 Thread Joshua Watt
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 tarball and use it when
compiling.

Most of the changes should be straightforward. icecc-create-env has
been almost completely re-written but the changes were broken up into
hopefully logical chunks.

The following changes since commit 385944254d0ef88bd6450a221a54cbcb40020b42:

  tcmode-default.inc: drop preferred version of gzip-native (2018-01-31 
17:01:20 +)

are available in the Git repository at:

  git://push.yoctoproject.org/poky-contrib jpew/icecream

Joshua Watt (14):
  icecc.bbclass: Move to shared work directory
  icecc.bbclass: Fix STAGING_BINDIR_TOOLCHAIN usage
  icecc.bbclass: Skip canadian-cross compiles
  icecc-create-env: Reformat
  icecc-create-env: Add /bin/true to environment
  icecc-create-env: Use program interpreter for deps
  icecc-create-env: Symlink alternate names
  icecc-create-env: Archive directory
  icecc-create-env: Fix executable rpaths
  icecc-create-env: Add support for nativesdk
  icecc-create-env: Allow multiple tool aliases
  toolchain-shar-extract: Add post-relocate scripts
  icecc-toolchain: Add SDK icecream setup
  icecc.bbclass: Add IceCream support to SDK

 meta/classes/icecc.bbclass |  37 ++-
 meta/classes/toolchain-scripts.bbclass |  15 +
 meta/files/toolchain-shar-extract.sh   |   8 +
 meta/recipes-core/meta/meta-environment.bb |   2 +
 .../icecc-create-env/icecc-create-env  | 328 ++---
 ...e-env-native_0.1.bb => icecc-create-env_0.1.bb} |   4 +-
 .../icecc-toolchain/icecc-toolchain/icecc-env.sh   |  37 +++
 .../icecc-toolchain/icecc-toolchain/icecc-setup.sh |  43 +++
 .../nativesdk-icecc-toolchain_0.1.bb   |  38 +++
 9 files changed, 390 insertions(+), 122 deletions(-)
 rename meta/recipes-devtools/icecc-create-env/{icecc-create-env-native_0.1.bb 
=> icecc-create-env_0.1.bb} (98%)
 create mode 100644 
meta/recipes-devtools/icecc-toolchain/icecc-toolchain/icecc-env.sh
 create mode 100644 
meta/recipes-devtools/icecc-toolchain/icecc-toolchain/icecc-setup.sh
 create mode 100644 
meta/recipes-devtools/icecc-toolchain/nativesdk-icecc-toolchain_0.1.bb

-- 
2.14.3

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Martin Kelly
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:
https://packages.debian.org/jessie/all/python3-nose/filelist

Also, other packages like python3-setuptools are already doing the same with
their binaries.

Signed-off-by: Denys Dmytriyenko 
Signed-off-by: Ross Burton 
Signed-off-by: Martin Kelly 
---
 meta/recipes-devtools/python/python3-nose_1.3.7.bb | 4 
 1 file changed, 4 insertions(+)

diff --git a/meta/recipes-devtools/python/python3-nose_1.3.7.bb 
b/meta/recipes-devtools/python/python3-nose_1.3.7.bb
index 99bba4403f..1e2ff74f57 100644
--- a/meta/recipes-devtools/python/python3-nose_1.3.7.bb
+++ b/meta/recipes-devtools/python/python3-nose_1.3.7.bb
@@ -17,6 +17,10 @@ S = "${WORKDIR}/nose-${PV}"
 
 inherit setuptools3
 
+do_install_append() {
+mv ${D}${bindir}/nosetests ${D}${bindir}/nosetests3
+}
+
 RDEPENDS_${PN}_class-target = "\
   python3-unittest \
   "
-- 
2.11.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Martin Kelly
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.

| 
/mnt/a/oe/build/tmp/work/cortexa7t2hf-neon-vfpv4-bec-linux-musleabi/python-pygpgme/0.3-r0/recipe-sysroot/usr/l
ib/Scrt1.o: In function `_start_c':
| /usr/src/debug/musl/1.1.16+gitAUTOINC+179766aa2e-r0/git/crt/crt1.c:17: 
undefined reference to `main'
| collect2: error: ld returned 1 exit status

This error while cryptic is due to the fact that we are
building a shared library but also pass -pie flag to the link
step after specify LDHSARED ( which is -shared linker flags )

we can not use -pie when doing shared libs. This is true for all the python
modules inheriting setup tools

Disable the pie flags thusly for all modules using setuptools since
this setting is done in setuptools makefiles which are then used
during module compiles

Backport notes:
In master, this commit is reverted in master in favor of using GCCPIE =
"--enable-default-pie" in security_flags.inc. However, backporting that change
introduces many merge conflicts and will be a serious maintenance issue, so I
think it's safest to just backport this small change, which fixes build failures
in python-cffi and likely other recipes.

For completeness, this is the list of commits in OE-core master that will
supersede this change:

- 1c7e195c94764d680a12a49b870f04cd58860f81
  "gcc: Introduce a knob to configure gcc to default to PIE"
- e93765ffb5718b0fce84f0b8123963176dea95e4
  "security_flags.inc: Delete pinnings for SECURITY_NO_PIE_CFLAGS"
- fcfe6d4ab4460f8358e13023022a5e909941ca93
  distutils,setuptools: Delete use of SECURITY_NO_PIE_CFLAGS

Signed-off-by: Khem Raj 
Signed-off-by: Ross Burton 
Signed-off-by: Martin Kelly 
---
 meta/classes/distutils-common-base.bbclass | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/classes/distutils-common-base.bbclass 
b/meta/classes/distutils-common-base.bbclass
index 824a1b68b1..fa733c672c 100644
--- a/meta/classes/distutils-common-base.bbclass
+++ b/meta/classes/distutils-common-base.bbclass
@@ -11,3 +11,5 @@ FILES_${PN}-dev += "\
   ${libdir}/pkgconfig \
   ${PYTHON_SITEPACKAGES_DIR}/*.la \
 "
+
+SECURITY_CFLAGS = "${SECURITY_NO_PIE_CFLAGS}"
-- 
2.11.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Cal Sullivan
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 wrote:



On 02/05/2018 04:47 PM, Khem Raj wrote:


On Mon, Feb 5, 2018 at 4:15 PM Cal Sullivan 
> wrote:


Looking at the test and the output, its expecting /dev/sda3 to be
mounted as /media and /dev/sda4 to be mounted as /mnt. With this
test result, there is no /media, and instead /dev/sda3 is mounted
to /mnt.

That seems odd to me unless that partition either wasn't created
or went entirely undetected.

I'll take a closer look, I think there's more going on here.


Udev trigger sometimes get ignored have seem that in past
Thanks for the info Khem! I think its an intermittent issue unrelated 
to this patch.


I ran the following with my patch applied on top of master and only 
SANITY_TESTED_DISTROS changed in local.conf:


MACHINE=qemux86-64 oe-selftest -r wic.Wic.test_qemu

And it didn't fail.

I'm going to run this test a few hundred times overnight without my 
patch and see if I can hit it.


Thanks,
Cal




---
Cal

On 02/05/2018 03:34 PM, Burton, Ross wrote:

This is causing the qemu boot wic test to fail in oe-selftest:

2018-02-05 15:08:41,786 - oe-selftest - INFO - FAIL [64.639s]:
test_qemu (wic.Wic)
2018-02-05 15:08:41,786 - oe-selftest - INFO -
--
2018-02-05 15:08:41,786 - oe-selftest - INFO - Traceback (most
recent call last):
  File

"/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oe-selftest/build/meta/lib/oeqa/core/decorator/__init__.py",
line 32, in wrapped_f
    return func(*args, **kwargs)
  File

"/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oe-selftest/build/meta/lib/oeqa/selftest/cases/wic.py",
line 58, in wrapped_f
    return func(*args, **kwargs)
  File

"/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oe-selftest/build/meta/lib/oeqa/selftest/cases/wic.py",
line 637, in test_qemu
    self.assertEqual(output, '/dev/root /\r\n/dev/sda1
/boot\r\n/dev/sda3 /mnt')
AssertionError: '/dev/root /\r\n/dev/sda1 /boot\r\n/dev/sda3
/media\r\n/dev/sda4 /mnt' != '/dev/root /\r\n/dev/sda1
/boot\r\n/dev/sda3 /mnt'
  /dev/root /
  /dev/sda1 /boot
- /dev/sda3 /media
- /dev/sda4 /mnt?         ^
+ /dev/sda3 /mnt?         ^

Presumably this is the initramfs mounting more stuff
automatically?  I don't have an opinion right now as to whether
this is a problem with the initramfs or the test case being too
strict...

Ross


On 1 February 2018 at 14:03, Burton, Ross mailto:ross.bur...@intel.com>> wrote:

Sorry, missed this.  I'll pull it into MUT and throw it at
the autobuilder...

Ross

On 31 January 2018 at 22:53, Cal Sullivan
mailto:california.l.sulli...@intel.com>> wrote:

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
28fc6ba761ed4a47efa7c43e7f7dff5e2fe72b5e
"core-image-minimal-initramfs: use
initramfs-framework by default" but
reverted due to the selftests
runqemu.RunqemuTests.test_boot_machine_iso
and runqemu.RunqemuTests.test_boot_deploy_hddimg
failing. Since then,
the kinks have been worked out, and missing
functionality that had been
missed (non-EFI installation module) has been added.

Since the PACKAGE_INSTALL variable was getting
so long with all these
individual modules getting added, I also
introduced a new
INITRAMFS_SCRIPTS variable to the
core-image-minimal-initramfs recipe.
This variable makes the recipe look much
cleaner, and also allows easier
replacement or additions to the scripts.

Fixes [YOCTO #10987].

Signed-off-by: California Sullivan
mailto:california.l.sulli...@intel.com>>
---
 
meta/recipes-core/images/core-image-minimal-initramfs.bb
 

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

2018-02-06 Thread Bystricky, Juro

> 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 elephant lion wolf fox " | xargs -n1 | sort -u
elephant
fox
lion
wolf
zebra


-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Matthijs Vader
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
> >
> > Thanks! The second patch you sent in with that actually solved some other
> problems I was having as well. Still one left to fix:
> >
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=12534
> >
> > See also the comment I added to that bugreport just now.
> 
> Cool! Can we have a joint effort in the merged patches?

Yes I will. I'll contact you off list.
 
> Also, can you please look into this fix I made against bitbake?
> At least one node module (cli-color) has cyclic dependencies, making the
> npm fetcher looping infinitely.
> http://lists.openembedded.org/pipermail/bitbake-devel/2018-
> February/009199.html

I'll look at that & test that.

> >
> > Best regards, Matthijs
> >
> >
> >> 2018-02-04 23:23 keltezéssel, mpvader írta:
> >>> npm now requires --force to clean the cache, see [1]. Also, use
> >>> clean instead of clear since the latter is an alias.
> >>>
> >>> [1]
> >>>
> >>
> https://github.com/npm/npm/commit/34f24c8381235790945208d25ac193bc
> >> 97a2
> >>> 1b79
> >>>
> >>> Signed-off-by: mpvader 
> >>> ---
> >>>meta/classes/npm.bbclass | 2 +-
> >>>1 file changed, 1 insertion(+), 1 deletion(-)
> >>>
> >>> diff --git a/meta/classes/npm.bbclass b/meta/classes/npm.bbclass
> >>> index
> >>> a69bedb..43aed36 100644
> >>> --- a/meta/classes/npm.bbclass
> >>> +++ b/meta/classes/npm.bbclass
> >>> @@ -31,7 +31,7 @@ npm_do_compile() {
> >>>   fi
> >>>   npm set cache ${WORKDIR}/npm_cache
> >>>   # clear cache before every build
> >>> - npm cache clear
> >>> + npm cache clean --force
> >>>   # Install pkg into ${S} without going to the registry
> >>>   if [  "${NPM_INSTALL_DEV}" = "1" ]; then
> >>>   npm --arch=${NPM_ARCH} --target_arch=${NPM_ARCH} --
> >> no-registry
> >>> install
> >>>
> >
> >

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Patchwork
== 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 been executed on the proposed
series by patchtest resulting in the following failures:



* Issue Series sent to the wrong mailing list or some patches from 
the series correspond to different mailing lists [test_target_mailing_list] 
  Suggested fixSend the series again to the correct mailing list (ML)
  Suggested ML p...@yoctoproject.org 
[http://git.yoctoproject.org/cgit/cgit.cgi/poky/]
  Patch's path:meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.10.bbappend

* Issue Series does not apply on top of target branch 
[test_series_merge_on_head] 
  Suggested fixRebase your series on top of targeted branch
  Targeted branch  master (currently at 4a4eff9b9e)



If you believe any of these test results are incorrect, please reply to the
mailing list (openembedded-core@lists.openembedded.org) raising your concerns.
Otherwise we would appreciate you correcting the issues and submitting a new
version of the patchset if applicable. Please ensure you add/increment the
version number when sending the new version (i.e. [PATCH] -> [PATCH v2] ->
[PATCH v3] -> ...).

---
Guidelines: 
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Bruce Ashfield
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 --
 .../recipes-kernel/linux/linux-yocto_4.4.bbappend  | 27 --
 .../recipes-kernel/linux/linux-yocto_4.9.bbappend  | 27 --
 3 files changed, 81 deletions(-)
 delete mode 100644 
meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.10.bbappend
 delete mode 100644 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend
 delete mode 100644 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.9.bbappend

diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.10.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.10.bbappend
deleted file mode 100644
index 346a1c79354b..
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.10.bbappend
+++ /dev/null
@@ -1,27 +0,0 @@
-KBRANCH_genericx86  = "standard/base"
-KBRANCH_genericx86-64  = "standard/base"
-
-KMACHINE_genericx86 ?= "common-pc"
-KMACHINE_genericx86-64 ?= "common-pc-64"
-KBRANCH_edgerouter = "standard/edgerouter"
-KBRANCH_beaglebone-yocto = "standard/beaglebone"
-KMACHINE_beaglebone-yocto = "beaglebone"
-KBRANCH_mpc8315e-rdb = "standard/fsl-mpc8315e-rdb"
-
-SRCREV_machine_genericx86?= "c1d8c4408b8aedd88eeb6ccc89ce834dd41b3f09"
-SRCREV_machine_genericx86-64 ?= "c1d8c4408b8aedd88eeb6ccc89ce834dd41b3f09"
-SRCREV_machine_edgerouter ?= "c1d8c4408b8aedd88eeb6ccc89ce834dd41b3f09"
-SRCREV_machine_beaglebone-yocto ?= "c1d8c4408b8aedd88eeb6ccc89ce834dd41b3f09"
-SRCREV_machine_mpc8315e-rdb ?= "c388fdfc9a1e06b22ca3533a023f4d67a6fc1e9b"
-
-COMPATIBLE_MACHINE_genericx86 = "genericx86"
-COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
-COMPATIBLE_MACHINE_edgerouter = "edgerouter"
-COMPATIBLE_MACHINE_beaglebone-yocto = "beaglebone-yocto"
-COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
-
-LINUX_VERSION_genericx86 = "4.10.17"
-LINUX_VERSION_genericx86-64 = "4.10.17"
-LINUX_VERSION_edgerouter = "4.10.17"
-LINUX_VERSION_beaglebone-yocto = "4.10.17"
-LINUX_VERSION_mpc8315e-rdb = "4.10.17"
diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend
deleted file mode 100644
index fa271e3e6d89..
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend
+++ /dev/null
@@ -1,27 +0,0 @@
-KBRANCH_genericx86  = "standard/base"
-KBRANCH_genericx86-64  = "standard/base"
-
-KMACHINE_genericx86 ?= "common-pc"
-KMACHINE_genericx86-64 ?= "common-pc-64"
-KBRANCH_edgerouter = "standard/edgerouter"
-KBRANCH_beaglebone-yocto = "standard/beaglebone"
-KMACHINE_beaglebone-yocto = "beaglebone"
-KBRANCH_mpc8315e-rdb = "standard/fsl-mpc8315e-rdb"
-
-SRCREV_machine_genericx86?= "4d31a8b7661509ff1044abcf9050750cc2478e20"
-SRCREV_machine_genericx86-64 ?= "4d31a8b7661509ff1044abcf9050750cc2478e20"
-SRCREV_machine_edgerouter ?= "f070447fb60b5b939c94583d7c05f55ec2b37acd"
-SRCREV_machine_beaglebone-yocto ?= "f070447fb60b5b939c94583d7c05f55ec2b37acd"
-SRCREV_machine_mpc8315e-rdb ?= "df06daf8e6de559934d16e88129bbba0237d0292"
-
-COMPATIBLE_MACHINE_genericx86 = "genericx86"
-COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
-COMPATIBLE_MACHINE_edgerouter = "edgerouter"
-COMPATIBLE_MACHINE_beaglebone-yocto = "beaglebone-yocto"
-COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
-
-LINUX_VERSION_genericx86 = "4.4.113"
-LINUX_VERSION_genericx86-64 = "4.4.113"
-LINUX_VERSION_edgerouter = "4.4.93"
-LINUX_VERSION_beaglebone-yocto = "4.4.93"
-LINUX_VERSION_mpc8315e-rdb = "4.4.93"
diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.9.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.9.bbappend
deleted file mode 100644
index c0f8a4d1f7dd..
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.9.bbappend
+++ /dev/null
@@ -1,27 +0,0 @@
-KBRANCH_genericx86  = "standard/base"
-KBRANCH_genericx86-64  = "standard/base"
-
-KMACHINE_genericx86 ?= "common-pc"
-KMACHINE_genericx86-64 ?= "common-pc-64"
-KBRANCH_edgerouter = "standard/edgerouter"
-KBRANCH_beaglebone-yocto = "standard/beaglebone"
-KMACHINE_beaglebone-yocto = "beaglebone"
-KBRANCH_mpc8315e-rdb = "standard/fsl-mpc8315e-rdb"
-
-SRCREV_machine_genericx86?= "f7a6d45fff853173bfbf61706aeffcd1d1e99467"
-SRCREV_machine_genericx86-64 ?= "f7a6d45fff853173bfbf61706aeffcd1d1e99467"
-SRCREV_machine_edgerouter ?= "5174e51fa08d0942ddcf8b19540e90ec10eeb621"
-SRCREV_machine_beaglebone-yocto ?= "5174e51fa08d0942ddcf8b19540e90ec10eeb621"
-SRCREV_machine_mpc8315e-rdb ?= "98afa8ec2086fb2262d43040094e6c786d3847ba"
-
-COMPATIBLE_MACHINE_genericx86 = "genericx86"
-COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
-COMPATIBLE_MACHINE_edgerouter = "edgerouter"
-COMPATIBLE_MACHINE_beaglebone-yocto = "beaglebone-yocto"
-COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
-
-LINUX_VERSION_genericx86

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

2018-02-06 Thread Bruce Ashfield
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 --git a/meta/conf/machine/include/x86-base.inc 
b/meta/conf/machine/include/x86-base.inc
index 023eb5ecca71..f8aacea64ccb 100644
--- a/meta/conf/machine/include/x86-base.inc
+++ b/meta/conf/machine/include/x86-base.inc
@@ -21,7 +21,7 @@ SERIAL_CONSOLE ?= "115200 ttyS0"
 # kernel-related variables
 #
 PREFERRED_PROVIDER_virtual/kernel ??= "linux-yocto"
-PREFERRED_VERSION_linux-yocto ??= "4.12%"
+PREFERRED_VERSION_linux-yocto ??= "4.15%"
 
 #
 # XSERVER subcomponents, used to build the XSERVER variable
diff --git a/meta/conf/machine/qemuarm.conf b/meta/conf/machine/qemuarm.conf
index aa112f51401a..9403b1e7e3b6 100644
--- a/meta/conf/machine/qemuarm.conf
+++ b/meta/conf/machine/qemuarm.conf
@@ -16,5 +16,5 @@ QB_MACHINE = "-machine versatilepb"
 QB_KERNEL_CMDLINE_APPEND = "console=ttyAMA0,115200 console=tty"
 # Add the 'virtio-rng-pci' device otherwise the guest may run out of entropy
 QB_OPT_APPEND = "-show-cursor -usb -device usb-tablet -device virtio-rng-pci"
-PREFERRED_VERSION_linux-yocto ??= "4.12%"
+PREFERRED_VERSION_linux-yocto ??= "4.15%"
 QB_DTB = "${@oe.utils.version_less_or_equal('PREFERRED_VERSION_linux-yocto', 
'4.7', '', 'zImage-versatile-pb.dtb', d)}"
-- 
2.5.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Bruce Ashfield
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) is not
justified in new releases.

Signed-off-by: Bruce Ashfield 
---
 meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb   | 38 
 meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb | 25 -
 meta/recipes-kernel/linux/linux-yocto_4.9.bb  | 44 ---
 3 files changed, 107 deletions(-)
 delete mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb
 delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb
 delete mode 100644 meta/recipes-kernel/linux/linux-yocto_4.9.bb

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb
deleted file mode 100644
index 0519bb9acced..
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb
+++ /dev/null
@@ -1,38 +0,0 @@
-KBRANCH ?= "standard/preempt-rt/base"
-
-require recipes-kernel/linux/linux-yocto.inc
-
-# Skip processing of this recipe if it is not explicitly specified as the
-# PREFERRED_PROVIDER for virtual/kernel. This avoids errors when trying
-# to build multiple virtual/kernel providers, e.g. as dependency of
-# core-image-rt-sdk, core-image-rt.
-python () {
-if d.getVar("KERNEL_PACKAGE_NAME") == "kernel" and 
d.getVar("PREFERRED_PROVIDER_virtual/kernel") != "linux-yocto-rt":
-raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to 
linux-yocto-rt to enable it")
-}
-
-SRCREV_machine ?= "7b2a74f272ef0a6e292b259872d47e891d7b2a20"
-SRCREV_meta ?= "ef2f5d9a0ac1c5ac60e76b18b0bb3393be450336"
-
-SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.9.git;branch=${KBRANCH};name=machine \
-   
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.9;destsuffix=${KMETA}"
-
-LINUX_VERSION ?= "4.9.78"
-
-PV = "${LINUX_VERSION}+git${SRCPV}"
-
-KMETA = "kernel-meta"
-KCONF_BSP_AUDIT_LEVEL = "2"
-
-LINUX_KERNEL_TYPE = "preempt-rt"
-
-COMPATIBLE_MACHINE = "(qemux86|qemux86-64|qemuarm|qemuppc|qemumips)"
-
-KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
-
-# Functionality flags
-KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc 
features/taskstats/taskstats.scc"
-KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
-KERNEL_FEATURES_append_qemuall=" cfg/virtio.scc"
-KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
-KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb
deleted file mode 100644
index 5c9a26098863..
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb
+++ /dev/null
@@ -1,25 +0,0 @@
-KBRANCH ?= "standard/tiny/common-pc"
-LINUX_KERNEL_TYPE = "tiny"
-KCONFIG_MODE = "--allnoconfig"
-
-require recipes-kernel/linux/linux-yocto.inc
-
-LINUX_VERSION ?= "4.9.78"
-
-KMETA = "kernel-meta"
-KCONF_BSP_AUDIT_LEVEL = "2"
-
-SRCREV_machine ?= "f7a6d45fff853173bfbf61706aeffcd1d1e99467"
-SRCREV_meta ?= "ef2f5d9a0ac1c5ac60e76b18b0bb3393be450336"
-
-PV = "${LINUX_VERSION}+git${SRCPV}"
-
-SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.9.git;branch=${KBRANCH};name=machine \
-   
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.9;destsuffix=${KMETA}"
-
-COMPATIBLE_MACHINE = "qemux86|qemux86-64"
-
-# Functionality flags
-KERNEL_FEATURES = ""
-
-KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.9.bb 
b/meta/recipes-kernel/linux/linux-yocto_4.9.bb
deleted file mode 100644
index 871d87000373..
--- a/meta/recipes-kernel/linux/linux-yocto_4.9.bb
+++ /dev/null
@@ -1,44 +0,0 @@
-KBRANCH ?= "standard/base"
-
-require recipes-kernel/linux/linux-yocto.inc
-
-# board specific branches
-KBRANCH_qemuarm  ?= "standard/arm-versatile-926ejs"
-KBRANCH_qemuarm64 ?= "standard/qemuarm64"
-KBRANCH_qemumips ?= "standard/mti-malta32"
-KBRANCH_qemuppc  ?= "standard/qemuppc"
-KBRANCH_qemux86  ?= "standard/base"
-KBRANCH_qemux86-64 ?= "standard/base"
-KBRANCH_qemumips64 ?= "standard/mti-malta64"
-
-SRCREV_machine_qemuarm ?= "801a684d5e769ca18e6ad9758806a528eccdcb73"
-SRCREV_machine_qemuarm64 ?= "f7a6d45fff853173bfbf61706aeffcd1d1e99467"
-SRCREV_machine_qemumips ?= "8235c7fda39963abbf6347390fd460e18a7e47b5"
-SRCREV_machine_qemuppc ?= "f7a6d45fff853173bfbf61706aeffcd1d1e99467"
-SRCREV_machine_qemux86 ?= "f7a6d45fff853173bfbf61706aeffcd1d1e99467"
-SRCREV_machine_qemux86-64 ?= "f7a6d45fff853173bfbf61706aeffcd1d1e99467"
-SRCREV_machine_qemumips64 ?= "bd9d169cd29aa5f2397ff383cd29f84a1043a693"
-SRCREV_machine ?= "f7a6d45fff853173bfbf61706aeffcd1d1e99467"
-SRCREV_meta ?= "ef2f5d9a0ac1c5ac60e76b18b0bb3393be450336"
-
-SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.9.git;name=machine

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

2018-02-06 Thread Bruce Ashfield
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) is not
justified in new releases.

Signed-off-by: Bruce Ashfield 
---
 meta/recipes-kernel/linux/linux-yocto-rt_4.10.bb   | 38 ---
 meta/recipes-kernel/linux/linux-yocto-tiny_4.10.bb | 25 
 meta/recipes-kernel/linux/linux-yocto_4.10.bb  | 44 --
 3 files changed, 107 deletions(-)
 delete mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_4.10.bb
 delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_4.10.bb
 delete mode 100644 meta/recipes-kernel/linux/linux-yocto_4.10.bb

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.10.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.10.bb
deleted file mode 100644
index 8b9888549740..
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.10.bb
+++ /dev/null
@@ -1,38 +0,0 @@
-KBRANCH ?= "standard/preempt-rt/base"
-
-require recipes-kernel/linux/linux-yocto.inc
-
-# Skip processing of this recipe if it is not explicitly specified as the
-# PREFERRED_PROVIDER for virtual/kernel. This avoids errors when trying
-# to build multiple virtual/kernel providers, e.g. as dependency of
-# core-image-rt-sdk, core-image-rt.
-python () {
-if d.getVar("KERNEL_PACKAGE_NAME") == "kernel" and 
d.getVar("PREFERRED_PROVIDER_virtual/kernel") != "linux-yocto-rt":
-raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to 
linux-yocto-rt to enable it")
-}
-
-SRCREV_machine ?= "c1d8c4408b8aedd88eeb6ccc89ce834dd41b3f09"
-SRCREV_meta ?= "1d9a8200184af22f8981fa24b0e82af49c7988dd"
-
-SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.10.git;branch=${KBRANCH};name=machine 
\
-   
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.10;destsuffix=${KMETA}"
-
-LINUX_VERSION ?= "4.10.17"
-
-PV = "${LINUX_VERSION}+git${SRCPV}"
-
-KMETA = "kernel-meta"
-KCONF_BSP_AUDIT_LEVEL = "2"
-
-LINUX_KERNEL_TYPE = "preempt-rt"
-
-COMPATIBLE_MACHINE = "(qemux86|qemux86-64|qemuarm|qemuppc|qemumips)"
-
-KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
-
-# Functionality flags
-KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc 
features/taskstats/taskstats.scc"
-KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
-KERNEL_FEATURES_append_qemuall=" cfg/virtio.scc"
-KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
-KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.10.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_4.10.bb
deleted file mode 100644
index b223497693cd..
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.10.bb
+++ /dev/null
@@ -1,25 +0,0 @@
-KBRANCH ?= "standard/tiny/common-pc"
-LINUX_KERNEL_TYPE = "tiny"
-KCONFIG_MODE = "--allnoconfig"
-
-require recipes-kernel/linux/linux-yocto.inc
-
-LINUX_VERSION ?= "4.10.17"
-
-KMETA = "kernel-meta"
-KCONF_BSP_AUDIT_LEVEL = "2"
-
-SRCREV_machine ?= "c1d8c4408b8aedd88eeb6ccc89ce834dd41b3f09"
-SRCREV_meta ?= "1d9a8200184af22f8981fa24b0e82af49c7988dd"
-
-PV = "${LINUX_VERSION}+git${SRCPV}"
-
-SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.10.git;branch=${KBRANCH};name=machine 
\
-   
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.10;destsuffix=${KMETA}"
-
-COMPATIBLE_MACHINE = "qemux86|qemux86-64"
-
-# Functionality flags
-KERNEL_FEATURES = ""
-
-KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.10.bb 
b/meta/recipes-kernel/linux/linux-yocto_4.10.bb
deleted file mode 100644
index 1fe3cca2ab42..
--- a/meta/recipes-kernel/linux/linux-yocto_4.10.bb
+++ /dev/null
@@ -1,44 +0,0 @@
-KBRANCH ?= "standard/base"
-
-require recipes-kernel/linux/linux-yocto.inc
-
-# board specific branches
-KBRANCH_qemuarm  ?= "standard/arm-versatile-926ejs"
-KBRANCH_qemuarm64 ?= "standard/qemuarm64"
-KBRANCH_qemumips ?= "standard/mti-malta32"
-KBRANCH_qemuppc  ?= "standard/qemuppc"
-KBRANCH_qemux86  ?= "standard/base"
-KBRANCH_qemux86-64 ?= "standard/base"
-KBRANCH_qemumips64 ?= "standard/mti-malta64"
-
-SRCREV_machine_qemuarm ?= "ae12e19cecc19af66f64a50538909cb1cad185f9"
-SRCREV_machine_qemuarm64 ?= "c1d8c4408b8aedd88eeb6ccc89ce834dd41b3f09"
-SRCREV_machine_qemumips ?= "b71b80fd679a17dfb4f73b352263c49273f721d4"
-SRCREV_machine_qemuppc ?= "c1d8c4408b8aedd88eeb6ccc89ce834dd41b3f09"
-SRCREV_machine_qemux86 ?= "c1d8c4408b8aedd88eeb6ccc89ce834dd41b3f09"
-SRCREV_machine_qemux86-64 ?= "c1d8c4408b8aedd88eeb6ccc89ce834dd41b3f09"
-SRCREV_machine_qemumips64 ?= "8bb135e71037c46175bbcc7acf387309b2e17133"
-SRCREV_machine ?= "c1d8c4408b8aedd88eeb6ccc89ce834dd41b3f09"
-SRCREV_meta ?= "1d9a8200184af22f8981fa24b0e82af49c7988dd"
-
-SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-

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

2018-02-06 Thread Bruce Ashfield
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) is not
justified in new releases.

Signed-off-by: Bruce Ashfield 
---
 meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb   | 36 ---
 meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb | 23 -
 meta/recipes-kernel/linux/linux-yocto_4.4.bb  | 42 ---
 3 files changed, 101 deletions(-)
 delete mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb
 delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb
 delete mode 100644 meta/recipes-kernel/linux/linux-yocto_4.4.bb

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb
deleted file mode 100644
index 5fd13f13c90b..
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb
+++ /dev/null
@@ -1,36 +0,0 @@
-KBRANCH ?= "standard/preempt-rt/base"
-
-require recipes-kernel/linux/linux-yocto.inc
-
-# Skip processing of this recipe if it is not explicitly specified as the
-# PREFERRED_PROVIDER for virtual/kernel. This avoids errors when trying
-# to build multiple virtual/kernel providers, e.g. as dependency of
-# core-image-rt-sdk, core-image-rt.
-python () {
-if d.getVar("KERNEL_PACKAGE_NAME") == "kernel" and 
d.getVar("PREFERRED_PROVIDER_virtual/kernel") != "linux-yocto-rt":
-raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to 
linux-yocto-rt to enable it")
-}
-
-SRCREV_machine ?= "d5efeeeb928a0111fc187fd1e8d03d2e4e35d4a0"
-SRCREV_meta ?= "b149d14ccae8349ab33e101f6af233a12f4b17ba"
-
-SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.4.git;branch=${KBRANCH};name=machine \
-   
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.4;destsuffix=${KMETA}"
-
-LINUX_VERSION ?= "4.4.113"
-
-PV = "${LINUX_VERSION}+git${SRCPV}"
-
-KMETA = "kernel-meta"
-KCONF_BSP_AUDIT_LEVEL = "2"
-
-LINUX_KERNEL_TYPE = "preempt-rt"
-
-COMPATIBLE_MACHINE = "(qemux86|qemux86-64|qemuarm|qemuppc|qemumips)"
-
-# Functionality flags
-KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc 
features/taskstats/taskstats.scc"
-KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
-KERNEL_FEATURES_append_qemuall=" cfg/virtio.scc"
-KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
-KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb
deleted file mode 100644
index 8a98189d4c74..
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb
+++ /dev/null
@@ -1,23 +0,0 @@
-KBRANCH ?= "standard/tiny/common-pc"
-LINUX_KERNEL_TYPE = "tiny"
-KCONFIG_MODE = "--allnoconfig"
-
-require recipes-kernel/linux/linux-yocto.inc
-
-LINUX_VERSION ?= "4.4.113"
-
-KMETA = "kernel-meta"
-KCONF_BSP_AUDIT_LEVEL = "2"
-
-SRCREV_machine ?= "4d31a8b7661509ff1044abcf9050750cc2478e20"
-SRCREV_meta ?= "b149d14ccae8349ab33e101f6af233a12f4b17ba"
-
-PV = "${LINUX_VERSION}+git${SRCPV}"
-
-SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.4.git;branch=${KBRANCH};name=machine \
-   
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.4;destsuffix=${KMETA}"
-
-COMPATIBLE_MACHINE = "qemux86|qemux86-64"
-
-# Functionality flags
-KERNEL_FEATURES = ""
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.4.bb 
b/meta/recipes-kernel/linux/linux-yocto_4.4.bb
deleted file mode 100644
index 97c16d59dd18..
--- a/meta/recipes-kernel/linux/linux-yocto_4.4.bb
+++ /dev/null
@@ -1,42 +0,0 @@
-KBRANCH ?= "standard/base"
-
-require recipes-kernel/linux/linux-yocto.inc
-
-# board specific branches
-KBRANCH_qemuarm  ?= "standard/arm-versatile-926ejs"
-KBRANCH_qemuarm64 ?= "standard/qemuarm64"
-KBRANCH_qemumips ?= "standard/mti-malta32"
-KBRANCH_qemuppc  ?= "standard/qemuppc"
-KBRANCH_qemux86  ?= "standard/base"
-KBRANCH_qemux86-64 ?= "standard/base"
-KBRANCH_qemumips64 ?= "standard/mti-malta64"
-
-SRCREV_machine_qemuarm ?= "400c0f39b954cd8fffdf53e6ec97852b73fea7af"
-SRCREV_machine_qemuarm64 ?= "4d31a8b7661509ff1044abcf9050750cc2478e20"
-SRCREV_machine_qemumips ?= "fb03a9472367b6c177729ac631326aafd5d17c92"
-SRCREV_machine_qemuppc ?= "4d31a8b7661509ff1044abcf9050750cc2478e20"
-SRCREV_machine_qemux86 ?= "4d31a8b7661509ff1044abcf9050750cc2478e20"
-SRCREV_machine_qemux86-64 ?= "4d31a8b7661509ff1044abcf9050750cc2478e20"
-SRCREV_machine_qemumips64 ?= "26b8ba186a6d39728fc1510bd2264110c75842f5"
-SRCREV_machine ?= "4d31a8b7661509ff1044abcf9050750cc2478e20"
-SRCREV_meta ?= "b149d14ccae8349ab33e101f6af233a12f4b17ba"
-
-SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.4.git;name=machine;branch=${KBRANCH}; 
\
-   
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=m

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

2018-02-06 Thread Bruce Ashfield
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 --git a/meta/recipes-kernel/lttng/lttng-modules_2.10.4.bb 
b/meta/recipes-kernel/lttng/lttng-modules_2.10.5.bb
similarity index 90%
rename from meta/recipes-kernel/lttng/lttng-modules_2.10.4.bb
rename to meta/recipes-kernel/lttng/lttng-modules_2.10.5.bb
index dd695f835d12..370b78aae146 100644
--- a/meta/recipes-kernel/lttng/lttng-modules_2.10.4.bb
+++ b/meta/recipes-kernel/lttng/lttng-modules_2.10.5.bb
@@ -16,8 +16,8 @@ SRC_URI = 
"https://lttng.org/files/${BPN}/${BPN}-${PV}.tar.bz2 \
file://BUILD_RUNTIME_BUG_ON-vs-gcc7.patch \
 "
 
-SRC_URI[md5sum] = "832452b321a4df6836549e72d05b2ce9"
-SRC_URI[sha256sum] = 
"f918e3b890f378f47a9ba8710ff52590e9b1d9c63b12a0e64d138e2e2e1b3c8a"
+SRC_URI[md5sum] = "4aaabaafd15d9455c83972e26ccfbca7"
+SRC_URI[sha256sum] = 
"b8dbbbee45a673c381f51b99c555e36655c3c2c7a5477aab927591cc7f003a1f"
 
 export INSTALL_MOD_DIR="kernel/lttng-modules"
 
-- 
2.5.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Bruce Ashfield
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 to specify mode per pin in a 
group
  55b9053b5a5a pinctrl: intel: Add support for variable size pad groups

Signed-off-by: Bruce Ashfield 
---
 meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb   |  4 ++--
 meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb |  4 ++--
 meta/recipes-kernel/linux/linux-yocto_4.12.bb  | 18 +-
 3 files changed, 13 insertions(+), 13 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb
index 11ff3cfecd12..f54bf8f2e903 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb
@@ -11,8 +11,8 @@ python () {
 raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to 
linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "f095b0588b491bb81854fbc168479cf5ff8a03ff"
-SRCREV_meta ?= "44a22d45cbcd7e14ea635d36949e14135f540fe0"
+SRCREV_machine ?= "21541338928449e6131e73bfd529f5214027d918"
+SRCREV_meta ?= "7986844d9de597218a23f82e68b01e5bf060d576"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.12.git;branch=${KBRANCH};name=machine 
\

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.12;destsuffix=${KMETA}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb
index c516d5de69af..5ac407c4dce3 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb
@@ -9,8 +9,8 @@ LINUX_VERSION ?= "4.12.19"
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine ?= "257f843ea367744620f1d92910afd2f454e31483"
-SRCREV_meta ?= "44a22d45cbcd7e14ea635d36949e14135f540fe0"
+SRCREV_machine ?= "4b7a5c1b4ec5536806942340755bcfbf6f3584d9"
+SRCREV_meta ?= "7986844d9de597218a23f82e68b01e5bf060d576"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.12.bb 
b/meta/recipes-kernel/linux/linux-yocto_4.12.bb
index d7b6e2750d50..f2db5174ac86 100644
--- a/meta/recipes-kernel/linux/linux-yocto_4.12.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_4.12.bb
@@ -11,15 +11,15 @@ KBRANCH_qemux86  ?= "standard/base"
 KBRANCH_qemux86-64 ?= "standard/base"
 KBRANCH_qemumips64 ?= "standard/mti-malta64"
 
-SRCREV_machine_qemuarm ?= "dafca619b2bd44966042bba76aa00edb0ca002df"
-SRCREV_machine_qemuarm64 ?= "257f843ea367744620f1d92910afd2f454e31483"
-SRCREV_machine_qemumips ?= "99c30bfd13f4cc364e55b67138705976bab193c9"
-SRCREV_machine_qemuppc ?= "257f843ea367744620f1d92910afd2f454e31483"
-SRCREV_machine_qemux86 ?= "257f843ea367744620f1d92910afd2f454e31483"
-SRCREV_machine_qemux86-64 ?= "257f843ea367744620f1d92910afd2f454e31483"
-SRCREV_machine_qemumips64 ?= "135d85c1f8cded6b68d533a0018b2897230b880c"
-SRCREV_machine ?= "257f843ea367744620f1d92910afd2f454e31483"
-SRCREV_meta ?= "44a22d45cbcd7e14ea635d36949e14135f540fe0"
+SRCREV_machine_qemuarm ?= "77d25f21501511f01eb3df3c58dd8cf10a90adce"
+SRCREV_machine_qemuarm64 ?= "4b7a5c1b4ec5536806942340755bcfbf6f3584d9"
+SRCREV_machine_qemumips ?= "567ea03f6c5844bed62957b20747b4315851e3c3"
+SRCREV_machine_qemuppc ?= "4b7a5c1b4ec5536806942340755bcfbf6f3584d9"
+SRCREV_machine_qemux86 ?= "4b7a5c1b4ec5536806942340755bcfbf6f3584d9"
+SRCREV_machine_qemux86-64 ?= "4b7a5c1b4ec5536806942340755bcfbf6f3584d9"
+SRCREV_machine_qemumips64 ?= "4796b8299a405d1428f000cc4a2e8800a3670541"
+SRCREV_machine ?= "4b7a5c1b4ec5536806942340755bcfbf6f3584d9"
+SRCREV_meta ?= "7986844d9de597218a23f82e68b01e5bf060d576"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.12.git;name=machine;branch=${KBRANCH};
 \

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.12;destsuffix=${KMETA}"
-- 
2.5.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Bruce Ashfield
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 +++---
 ...aders_4.14.13.bb => linux-libc-headers_4.15.bb} |  4 +--
 4 files changed, 23 insertions(+), 48 deletions(-)
 rename meta/recipes-kernel/linux-libc-headers/{linux-libc-headers_4.14.13.bb 
=> linux-libc-headers_4.15.bb} (71%)

diff --git a/meta/conf/distro/include/tcmode-default.inc 
b/meta/conf/distro/include/tcmode-default.inc
index 64ffeb5ef74c..2e7243f32c2c 100644
--- a/meta/conf/distro/include/tcmode-default.inc
+++ b/meta/conf/distro/include/tcmode-default.inc
@@ -27,7 +27,7 @@ SDKGCCVERSION ?= "${GCCVERSION}"
 BINUVERSION ?= "2.29%"
 GDBVERSION ?= "8.0%"
 GLIBCVERSION ?= "2.26%"
-LINUXLIBCVERSION ?= "4.14%"
+LINUXLIBCVERSION ?= "4.15%"
 
 PREFERRED_VERSION_gcc ?= "${GCCVERSION}"
 PREFERRED_VERSION_gcc-cross-${TARGET_ARCH} ?= "${GCCVERSION}"
diff --git 
a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers/0001-libc-compat.h-fix-some-issues-arising-from-in6.h.patch
 
b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers/0001-libc-compat.h-fix-some-issues-arising-from-in6.h.patch
index 8bb775ccf74a..a3fa59001d2d 100644
--- 
a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers/0001-libc-compat.h-fix-some-issues-arising-from-in6.h.patch
+++ 
b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers/0001-libc-compat.h-fix-some-issues-arising-from-in6.h.patch
@@ -11,11 +11,11 @@ Upstream-Status: Submitted
  include/uapi/linux/libc-compat.h | 25 -
  1 file changed, 8 insertions(+), 17 deletions(-)
 
-Index: linux-4.8-rc4/include/uapi/linux/libc-compat.h
+Index: linux-4.15/include/uapi/linux/libc-compat.h
 ===
 linux-4.8-rc4.orig/include/uapi/linux/libc-compat.h
-+++ linux-4.8-rc4/include/uapi/linux/libc-compat.h
-@@ -48,13 +48,12 @@
+--- linux-4.15.orig/include/uapi/linux/libc-compat.h   2018-02-05 
17:37:44.724314379 -0500
 linux-4.15/include/uapi/linux/libc-compat.h2018-02-05 
17:38:02.148913820 -0500
+@@ -49,13 +49,12 @@
  #ifndef _UAPI_LIBC_COMPAT_H
  #define _UAPI_LIBC_COMPAT_H
  
@@ -33,7 +33,7 @@ Index: linux-4.8-rc4/include/uapi/linux/libc-compat.h
   * that would already be defined. */
  
  #define __UAPI_DEF_IF_IFCONF 0
-@@ -98,15 +97,7 @@
+@@ -99,15 +98,7 @@
  #define __UAPI_DEF_IN_CLASS   0
  
  #define __UAPI_DEF_IN6_ADDR   0
@@ -49,7 +49,7 @@ Index: linux-4.8-rc4/include/uapi/linux/libc-compat.h
  #define __UAPI_DEF_SOCKADDR_IN6   0
  #define __UAPI_DEF_IPV6_MREQ  0
  #define __UAPI_DEF_IPPROTO_V6 0
-@@ -114,10 +105,10 @@
+@@ -115,10 +106,10 @@
  #define __UAPI_DEF_IN6_PKTINFO0
  #define __UAPI_DEF_IP6_MTUINFO0
  
@@ -62,7 +62,7 @@ Index: linux-4.8-rc4/include/uapi/linux/libc-compat.h
   * __UAPI_DEF_* defines and adjust appropriately. */
  #define __UAPI_DEF_IN_ADDR1
  #define __UAPI_DEF_IN_IPPROTO 1
-@@ -127,7 +118,7 @@
+@@ -128,7 +119,7 @@
  #define __UAPI_DEF_IN_CLASS   1
  
  #define __UAPI_DEF_IN6_ADDR   1
@@ -71,20 +71,21 @@ Index: linux-4.8-rc4/include/uapi/linux/libc-compat.h
   * coordinate. */
  #define __UAPI_DEF_IN6_ADDR_ALT   1
  #define __UAPI_DEF_SOCKADDR_IN6   1
-@@ -149,7 +140,7 @@
- /* If we did not see any headers from any supported C libraries,
+@@ -170,7 +161,7 @@
   * or we are being included in the kernel, then define everything
-  * that we need. */
+  * that we need. Check for previous __UAPI_* definitions to give
+  * unsupported C libraries a way to opt out of any kernel definition. */
 -#else /* !defined(__GLIBC__) */
 +#else /* __KERNEL__ */
  
  /* Definitions for if.h */
- #define __UAPI_DEF_IF_IFCONF 1
-@@ -182,6 +173,6 @@
- /* Definitions for xattr.h */
+ #ifndef __UAPI_DEF_IF_IFCONF
+@@ -262,7 +253,7 @@
  #define __UAPI_DEF_XATTR  1
+ #endif
  
 -#endif /* __GLIBC__ */
 +#endif /* __KERNEL__ */
  
- #endif /* _UAPI_LIBC_COMPAT_H */
+ /* Definitions for if_ether.h */
+ /* allow libcs like musl to deactivate this, glibc does not implement this. */
diff --git 
a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers/0002-libc-compat.h-prevent-redefinition-of-struct-ethhdr.patch
 
b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers/0002-libc-compat.h-prevent-redefinition-of-struct-ethhdr.patch
index 8dc1edc33be5..fb7e1de17a6e 100644
--- 
a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers/0002-libc-compat.h-prevent-redefinition-of-struct-ethhdr.patch
+++ 
b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers/0002-libc-compat.h-prevent-redefinition-of-struct-ethhdr.patch
@@ -11,37 +11,11 @@ Upstream-Status: Submitted
  include/uapi/linux/libc-compat.h | 6 ++
  2 files changed, 9 insertions(+), 1 deletion(-)
 
-Index: l

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

2018-02-06 Thread Bruce Ashfield
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 commits.

Signed-off-by: Bruce Ashfield 
---
 meta/recipes-kernel/linux/linux-yocto-rt_4.15.bb   | 38 +
 meta/recipes-kernel/linux/linux-yocto-tiny_4.15.b  | 25 
 meta/recipes-kernel/linux/linux-yocto-tiny_4.15.bb | 47 ++
 meta/recipes-kernel/linux/linux-yocto_4.15.bb  | 47 ++
 4 files changed, 157 insertions(+)
 create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_4.15.bb
 create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_4.15.b
 create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_4.15.bb
 create mode 100644 meta/recipes-kernel/linux/linux-yocto_4.15.bb

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.15.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.15.bb
new file mode 100644
index ..31f8c23cef52
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.15.bb
@@ -0,0 +1,38 @@
+KBRANCH ?= "v4.15/standard/preempt-rt/base"
+
+require recipes-kernel/linux/linux-yocto.inc
+
+# Skip processing of this recipe if it is not explicitly specified as the
+# PREFERRED_PROVIDER for virtual/kernel. This avoids errors when trying
+# to build multiple virtual/kernel providers, e.g. as dependency of
+# core-image-rt-sdk, core-image-rt.
+python () {
+if d.getVar("KERNEL_PACKAGE_NAME") == "kernel" and 
d.getVar("PREFERRED_PROVIDER_virtual/kernel") != "linux-yocto-rt":
+raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to 
linux-yocto-rt to enable it")
+}
+
+SRCREV_machine ?= "9c2e6c0fc71526c45fc7ddf3ec91e2e2f27e3da0"
+SRCREV_meta ?= "64ad69e5b4a38e678500d7a70791ac5154c6c154"
+
+SRC_URI = 
"git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
+   
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.15;destsuffix=${KMETA}"
+
+LINUX_VERSION ?= "4.15"
+
+PV = "${LINUX_VERSION}+git${SRCPV}"
+
+KMETA = "kernel-meta"
+KCONF_BSP_AUDIT_LEVEL = "2"
+
+LINUX_KERNEL_TYPE = "preempt-rt"
+
+COMPATIBLE_MACHINE = "(qemux86|qemux86-64|qemuarm|qemuppc|qemumips)"
+
+KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
+
+# Functionality flags
+KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc 
features/taskstats/taskstats.scc"
+KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
+KERNEL_FEATURES_append_qemuall=" cfg/virtio.scc"
+KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
+KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.15.b 
b/meta/recipes-kernel/linux/linux-yocto-tiny_4.15.b
new file mode 100644
index ..7a6696c71a68
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.15.b
@@ -0,0 +1,25 @@
+KBRANCH ?= "v4.15/standard/tiny/common-pc"
+LINUX_KERNEL_TYPE = "tiny"
+KCONFIG_MODE = "--allnoconfig"
+
+require recipes-kernel/linux/linux-yocto.inc
+
+LINUX_VERSION ?= "4.15"
+
+KMETA = "kernel-meta"
+KCONF_BSP_AUDIT_LEVEL = "2"
+
+SRCREV_machine ?= "f7a6d45fff853173bfbf61706aeffcd1d1e99467"
+SRCREV_meta ?= "ef2f5d9a0ac1c5ac60e76b18b0bb3393be450336"
+
+PV = "${LINUX_VERSION}+git${SRCPV}"
+
+SRC_URI = 
"git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
+   
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.15;destsuffix=${KMETA}"
+
+COMPATIBLE_MACHINE = "qemux86|qemux86-64"
+
+# Functionality flags
+KERNEL_FEATURES = ""
+
+KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.15.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_4.15.bb
new file mode 100644
index ..60b7e600d24d
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.15.bb
@@ -0,0 +1,47 @@
+KBRANCH ?= "v4.15/standard/base"
+
+require recipes-kernel/linux/linux-yocto.inc
+
+# board specific branches
+KBRANCH_qemuarm  ?= "v4.15/standard/arm-versatile-926ejs"
+KBRANCH_qemuarm64 ?= "v4.15/standard/qemuarm64"
+KBRANCH_qemumips ?= "v4.15/standard/mti-malta32"
+KBRANCH_qemuppc  ?= "v4.15/standard/qemuppc"
+KBRANCH_qemux86  ?= "v4.15/standard/base"
+KBRANCH_qemux86-64 ?= "v4.15/standard/base"
+KBRANCH_qemumips64 ?= "v4.15/standard/mti-malta64"
+
+SRCREV_machine_qemuarm ?= "5fdc3d579c5f50fbaaa5faecae79e20b73810346"
+SRCREV_machine_qemuarm64 ?= "9c2e6c0fc71526c45fc7ddf3ec91e2e2f27e3da0"
+SRCREV_machine_qemumips ?= "5afbe5a7e271f1c115a7c77bea4a71356c6f2792"
+SRCREV_machine_qemuppc ?= "9c2e6c0fc71526c45fc7ddf3ec91e2e2f27e3da0"
+SRCREV_machine_qemux86 ?= "9c2e6c0fc71526c45fc7ddf3ec91e2e2f27e3da0"
+SRCREV_machine_qemux86-64 ?= "9c2e6c0fc71526c45fc7ddf3ec91e2e2f27e3da0"
+SRCREV_machine_qemumips64 ?= "f9a3a72209bde080e4ecb4fbe7a0f99954643131"
+SRCREV_m

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

2018-02-06 Thread Bruce Ashfield
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 commits.

Signed-off-by: Bruce Ashfield 
---
 meta/recipes-kernel/linux/linux-yocto-rt_4.14.bb   | 38 +++
 meta/recipes-kernel/linux/linux-yocto-tiny_4.14.bb | 25 
 meta/recipes-kernel/linux/linux-yocto_4.14.bb  | 44 ++
 3 files changed, 107 insertions(+)
 create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_4.14.bb
 create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_4.14.bb
 create mode 100644 meta/recipes-kernel/linux/linux-yocto_4.14.bb

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.14.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.14.bb
new file mode 100644
index ..669a2606aed8
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.14.bb
@@ -0,0 +1,38 @@
+KBRANCH ?= "v4.14/standard/preempt-rt/base"
+
+require recipes-kernel/linux/linux-yocto.inc
+
+# Skip processing of this recipe if it is not explicitly specified as the
+# PREFERRED_PROVIDER for virtual/kernel. This avoids errors when trying
+# to build multiple virtual/kernel providers, e.g. as dependency of
+# core-image-rt-sdk, core-image-rt.
+python () {
+if d.getVar("KERNEL_PACKAGE_NAME") == "kernel" and 
d.getVar("PREFERRED_PROVIDER_virtual/kernel") != "linux-yocto-rt":
+raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to 
linux-yocto-rt to enable it")
+}
+
+SRCREV_machine ?= "ae0fb21fdde3df106d7dad76620bdf39721425e2"
+SRCREV_meta ?= "0e964663a7978bdb459c28f3777e1b6dfe97d93d"
+
+SRC_URI = 
"git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
+   
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.14;destsuffix=${KMETA}"
+
+LINUX_VERSION ?= "4.14.16"
+
+PV = "${LINUX_VERSION}+git${SRCPV}"
+
+KMETA = "kernel-meta"
+KCONF_BSP_AUDIT_LEVEL = "2"
+
+LINUX_KERNEL_TYPE = "preempt-rt"
+
+COMPATIBLE_MACHINE = "(qemux86|qemux86-64|qemuarm|qemuppc|qemumips)"
+
+KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
+
+# Functionality flags
+KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc 
features/taskstats/taskstats.scc"
+KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
+KERNEL_FEATURES_append_qemuall=" cfg/virtio.scc"
+KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
+KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.14.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_4.14.bb
new file mode 100644
index ..bf4b0ac4f6c3
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.14.bb
@@ -0,0 +1,25 @@
+KBRANCH ?= "v4.14/standard/tiny/common-pc"
+LINUX_KERNEL_TYPE = "tiny"
+KCONFIG_MODE = "--allnoconfig"
+
+require recipes-kernel/linux/linux-yocto.inc
+
+LINUX_VERSION ?= "4.14.16"
+
+KMETA = "kernel-meta"
+KCONF_BSP_AUDIT_LEVEL = "2"
+
+SRCREV_machine ?= "ae0fb21fdde3df106d7dad76620bdf39721425e2"
+SRCREV_meta ?= "0e964663a7978bdb459c28f3777e1b6dfe97d93d"
+
+PV = "${LINUX_VERSION}+git${SRCPV}"
+
+SRC_URI = 
"git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
+   
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.14;destsuffix=${KMETA}"
+
+COMPATIBLE_MACHINE = "qemux86|qemux86-64"
+
+# Functionality flags
+KERNEL_FEATURES = ""
+
+KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.14.bb 
b/meta/recipes-kernel/linux/linux-yocto_4.14.bb
new file mode 100644
index ..e71046ee0c74
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto_4.14.bb
@@ -0,0 +1,44 @@
+KBRANCH ?= "v4.14/standard/base"
+
+require recipes-kernel/linux/linux-yocto.inc
+
+# board specific branches
+KBRANCH_qemuarm  ?= "v4.14/standard/arm-versatile-926ejs"
+KBRANCH_qemuarm64 ?= "v4.14/standard/qemuarm64"
+KBRANCH_qemumips ?= "v4.14/standard/mti-malta32"
+KBRANCH_qemuppc  ?= "v4.14/standard/qemuppc"
+KBRANCH_qemux86  ?= "v4.14/standard/base"
+KBRANCH_qemux86-64 ?= "v4.14/standard/base"
+KBRANCH_qemumips64 ?= "v4.14/standard/mti-malta64"
+
+SRCREV_machine_qemuarm ?= "52cbbd4d3e216cbf0c12ae66f012103b20777884"
+SRCREV_machine_qemuarm64 ?= "ae0fb21fdde3df106d7dad76620bdf39721425e2"
+SRCREV_machine_qemumips ?= "900ca1bbd59fe4bf28a767e816d1883d173d7397"
+SRCREV_machine_qemuppc ?= "ae0fb21fdde3df106d7dad76620bdf39721425e2"
+SRCREV_machine_qemux86 ?= "ae0fb21fdde3df106d7dad76620bdf39721425e2"
+SRCREV_machine_qemux86-64 ?= "ae0fb21fdde3df106d7dad76620bdf39721425e2"
+SRCREV_machine_qemumips64 ?= "c6c6244d216a6c2f87c807d8e2e4bc42baa7c480"
+SRCREV_machine ?= "ae0fb21fdde3df106d7dad76620bdf39721425e2"
+SRCREV_meta ?= "0e964663a7978bdb459c28f3777e1b6dfe97d93d"
+
+SRC_URI = 
"git://git.yoctoproject.org/linux

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

2018-02-06 Thread Bruce Ashfield
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 repository and adjusted the recipes to use it.

   Other than a few more branches to wade through, it won't change any workflows
   and will save download space for this update and for the future.

 - On that note, I'm moving master to v4.14 as the LTS/LTSI kernel, with
   v4.15 available as the "latest" kernel. I'm also keeping 4.12 around for a
   bit longer to move the reference BSPs to v4.14+.

   I'll send a second series for meta-yocto that updates the default versions to
   match the v4.14+ kernel revisions.

   Note: This doesn't mean that I'm no longer maintaining the other kernels for
 CVEs/stable updates, it just means that they won't get SRCREV bumps in
 master. Anything older than 4.14 is a big maintenance concern for
 fixes/security due to the recent CVEs, etc. It was a mistake to allow
 as many kernels to be active in master as there currently is, so taking
 both factors into account, I'm correcting to v4.14/v4.15 + yocto-dev
 for the release.

 - linux-libc-headers is updated to the latest kernel, and I've refreshed the
   mulsc patches as part of that update.

 - I uprev'd lttng to v2.10.5 to build against v4.15+

 - I've built qemu* core-image-sato/core-image-kernel-dev for both v4.14 and
   v4.15 and performed boot tests. I've also built poky-lsb for v4.14 and also
   done boot tests. I've also built mulsc based systems and done the same boot
   tests.

So I've done my best to cover all the possible build combinations, but it is
a rather large matrix, so I'll be watching this go through the autobuilders
and other tests (and failures).

Cheers,

Bruce

The following changes since commit 385944254d0ef88bd6450a221a54cbcb40020b42:

  tcmode-default.inc: drop preferred version of gzip-native (2018-01-31 
17:01:20 +)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib zedd/kernel
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (9):
  linux-yocto: introduce 4.14 recipes
  linux-yocto: introduce 4.15 recipes
  linux-libc-headers: update to v4.15
  linux-yocto/4.12: pinctrl backports
  lttng-modules: update to v2.10.5 for kernel 4.15
  linux-yocto/4.10: drop recipe
  linux-yocto/4.4: drop recipe
  linux-yocto/4.9: drop recipe
  machines: bump default linux-yocto to v4.15

 meta/conf/distro/include/tcmode-default.inc|  2 +-
 meta/conf/machine/include/x86-base.inc |  2 +-
 meta/conf/machine/qemuarm.conf |  2 +-
 ...mpat.h-fix-some-issues-arising-from-in6.h.patch | 29 ++---
 ...t.h-prevent-redefinition-of-struct-ethhdr.patch | 36 +++--
 ...aders_4.14.13.bb => linux-libc-headers_4.15.bb} |  4 +-
 meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb   |  4 +-
 ...nux-yocto-rt_4.10.bb => linux-yocto-rt_4.14.bb} | 12 +++---
 ...inux-yocto-rt_4.9.bb => linux-yocto-rt_4.15.bb} | 12 +++---
 meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb| 36 -
 meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb |  4 +-
 ...yocto-tiny_4.10.bb => linux-yocto-tiny_4.14.bb} | 12 +++---
 ...x-yocto-tiny_4.9.bb => linux-yocto-tiny_4.15.b} |  8 ++--
 meta/recipes-kernel/linux/linux-yocto-tiny_4.15.bb | 47 ++
 meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb  | 23 ---
 meta/recipes-kernel/linux/linux-yocto_4.12.bb  | 18 -
 .../{linux-yocto_4.10.bb => linux-yocto_4.14.bb}   | 46 ++---
 meta/recipes-kernel/linux/linux-yocto_4.15.bb  | 47 ++
 meta/recipes-kernel/linux/linux-yocto_4.4.bb   | 42 ---
 meta/recipes-kernel/linux/linux-yocto_4.9.bb   | 44 
 ...g-modules_2.10.4.bb => lttng-modules_2.10.5.bb} |  4 +-
 21 files changed, 179 insertions(+), 255 deletions(-)
 rename meta/recipes-kernel/linux-libc-headers/{linux-libc-headers_4.14.13.bb 
=> linux-libc-headers_4.15.bb} (71%)
 rename meta/recipes-kernel/linux/{linux-yocto-rt_4.10.bb => 
linux-yocto-rt_4.14.bb} (78%)
 rename meta/recipes-kernel/linux/{linux-yocto-rt_4.9.bb => 
linux-yocto-rt_4.15.bb} (78%)
 delete mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb
 rename meta/recipes-kernel/linux/{linux-yocto-tiny_4.10.bb => 
linux-yocto-tiny_4.14.bb} (54%)
 rename meta/recipes-kernel/linux/{linux-yocto-tiny_4.9.bb => 
linux-yocto-tiny_4.15.b} (71%)
 create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_4.15.bb
 delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb
 rename meta/recipes-kernel/linux/{linux-yocto_4.10.bb => linux-yocto_4.14.bb} 
(40%)
 create mode 100644 meta/recipes-kernel/linux/linux-yocto_4.15.bb
 delete mode 100644 meta/recipes

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

2018-02-06 Thread Alexander Kanavin
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 
b/meta/recipes-extended/iputils/files/0001-Fix-build-on-MUSL.patch
index c86dafc0380..ce8cfebbb03 100644
--- a/meta/recipes-extended/iputils/files/0001-Fix-build-on-MUSL.patch
+++ b/meta/recipes-extended/iputils/files/0001-Fix-build-on-MUSL.patch
@@ -6,6 +6,8 @@ Subject: [PATCH] Fix build on MUSL
 Add missing AI_IDN and NI_IDN declarations.
 
 Bug: https://bugs.gentoo.org/503914
+
+Upstream-Status: Pending
 Signed-off-by: Alexander Kanavin 
 ---
  arping.c  |  7 +++
-- 
2.15.1

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Alexander Kanavin
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 Kanavin 
---
 .../recipes-test/postinst/postinst_1.0.bb  | 14 +++-
 meta/lib/oeqa/selftest/cases/runtime_test.py   | 37 ++
 2 files changed, 50 insertions(+), 1 deletion(-)

diff --git a/meta-selftest/recipes-test/postinst/postinst_1.0.bb 
b/meta-selftest/recipes-test/postinst/postinst_1.0.bb
index d4bab6dcc22..913bfabf89e 100644
--- a/meta-selftest/recipes-test/postinst/postinst_1.0.bb
+++ b/meta-selftest/recipes-test/postinst/postinst_1.0.bb
@@ -3,11 +3,12 @@ LICENSE = "MIT"
 
 inherit allarch
 
-PACKAGES = "${PN}-rootfs ${PN}-delayed-a ${PN}-delayed-b"
+PACKAGES = "${PN}-rootfs ${PN}-delayed-a ${PN}-delayed-b ${PN}-rootfs-failing"
 
 ALLOW_EMPTY_${PN}-rootfs = "1"
 ALLOW_EMPTY_${PN}-delayed-a = "1"
 ALLOW_EMPTY_${PN}-delayed-b = "1"
+ALLOW_EMPTY_${PN}-rootfs-failing = "1"
 
 RDEPENDS_${PN}-delayed-a = "${PN}-rootfs"
 RDEPENDS_${PN}-delayed-b = "${PN}-delayed-a"
@@ -58,3 +59,14 @@ pkg_postinst_ontarget_${PN}-delayed-b () {
 
 touch ${TESTDIR}/delayed-b
 }
+
+# This scriptlet intentionally includes a bogus command in the middle to test 
+# that we catch and report such errors properly.
+pkg_postinst_${PN}-rootfs-failing () {
+mkdir -p $D${TESTDIR}
+touch $D${TESTDIR}/rootfs-before-failure
+run_a_really_broken_command
+# Scriptlet execution should stop here; the following commands are NOT 
supposed to run.
+# (oe-selftest checks for it).
+touch $D${TESTDIR}/rootfs-after-failure
+}
diff --git a/meta/lib/oeqa/selftest/cases/runtime_test.py 
b/meta/lib/oeqa/selftest/cases/runtime_test.py
index 1c69255b568..9c9b4b34111 100644
--- a/meta/lib/oeqa/selftest/cases/runtime_test.py
+++ b/meta/lib/oeqa/selftest/cases/runtime_test.py
@@ -221,3 +221,40 @@ class Postinst(OESelftestTestCase):
 for filename in ("rootfs", "delayed-a", "delayed-b"):
 status, output = qemu.run_serial("test -f %s && 
echo found" % os.path.join(targettestdir, filename))
 self.assertEqual(output, "found", "%s was not 
present on boot" % filename)
+
+
+
+def test_failing_postinst(self):
+"""
+Summary:The purpose of this test case is to verify that 
post-installation
+scripts that contain errors are properly reported.
+Expected:   The scriptlet failure is properly reported.
+The file that is created after the error in the 
scriptlet is not present.
+Product: oe-core
+Author: Alexander Kanavin 
+"""
+
+import oe.path
+
+vars = get_bb_vars(("IMAGE_ROOTFS", "sysconfdir"), 
"core-image-minimal")
+rootfs = vars["IMAGE_ROOTFS"]
+self.assertIsNotNone(rootfs)
+sysconfdir = vars["sysconfdir"]
+self.assertIsNotNone(sysconfdir)
+# Need to use oe.path here as sysconfdir starts with /
+hosttestdir = oe.path.join(rootfs, sysconfdir, "postinst-test")
+
+for classes in ("package_rpm", "package_deb", "package_ipk"):
+with self.subTest(package_class=classes):
+features = 'CORE_IMAGE_EXTRA_INSTALL = 
"postinst-rootfs-failing"\n'
+features += 'PACKAGE_CLASSES = "%s"\n' % classes
+self.write_config(features)
+bb_result = bitbake('core-image-minimal')
+self.assertGreaterEqual(bb_result.output.find("Intentionally 
failing postinstall scriptlets of ['postinst-rootfs-failing'] to defer them to 
first boot is deprecated."), 0,
+"Warning about a failed scriptlet not found in bitbake 
output: %s" %(bb_result.output))
+
+self.assertTrue(os.path.isfile(os.path.join(hosttestdir, 
"rootfs-before-failure")),
+"rootfs-before-failure file was not 
created")
+self.assertFalse(os.path.isfile(os.path.join(hosttestdir, 
"rootfs-after-failure")),
+"rootfs-after-failure file was created")
+
-- 
2.15.1

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Alexander Kanavin
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 one that works for all package types.

Signed-off-by: Alexander Kanavin 
---
 meta/classes/package.bbclass | 12 
 meta/classes/package_rpm.bbclass |  8 
 2 files changed, 16 insertions(+), 4 deletions(-)

diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass
index 6a7f35a3e78..607b548d08d 100644
--- a/meta/classes/package.bbclass
+++ b/meta/classes/package.bbclass
@@ -1339,6 +1339,17 @@ fi
 postinst += postinst_ontarget
 d.setVar('pkg_postinst_%s' % pkg, postinst)
 
+def add_set_e_to_scriptlets(pkg):
+for scriptlet_name in ('pkg_preinst', 'pkg_postinst', 'pkg_prerm', 
'pkg_postrm'):
+scriptlet = d.getVar('%s_%s' % (scriptlet_name, pkg))
+if scriptlet:
+scriptlet_split = scriptlet.split('\n')
+if scriptlet_split[0].startswith("#!"):
+scriptlet = scriptlet_split[0] + "\nset -e\n" + 
"\n".join(scriptlet_split[1:])
+else:
+scriptlet = "set -e\n" + "\n".join(scriptlet_split[0:])
+d.setVar('%s_%s' % (scriptlet_name, pkg), scriptlet)
+
 def write_if_exists(f, pkg, var):
 def encode(str):
 import codecs
@@ -1435,6 +1446,7 @@ fi
 write_if_exists(sf, pkg, 'FILES')
 write_if_exists(sf, pkg, 'CONFFILES')
 process_postinst_on_target(pkg, d.getVar("MLPREFIX"))
+add_set_e_to_scriptlets(pkg)
 write_if_exists(sf, pkg, 'pkg_postinst')
 write_if_exists(sf, pkg, 'pkg_postrm')
 write_if_exists(sf, pkg, 'pkg_preinst')
diff --git a/meta/classes/package_rpm.bbclass b/meta/classes/package_rpm.bbclass
index e26b2ad6625..af64ef62c58 100644
--- a/meta/classes/package_rpm.bbclass
+++ b/meta/classes/package_rpm.bbclass
@@ -470,12 +470,12 @@ python write_specfile () {
 
 # Now process scriptlets
 if splitrpreinst:
-spec_scriptlets_bottom.append('%%pre -n %s -p "/bin/sh -e"' % 
splitname)
+spec_scriptlets_bottom.append('%%pre -n %s' % splitname)
 spec_scriptlets_bottom.append('# %s - preinst' % splitname)
 spec_scriptlets_bottom.append(splitrpreinst)
 spec_scriptlets_bottom.append('')
 if splitrpostinst:
-spec_scriptlets_bottom.append('%%post -n %s -p "/bin/sh -e"' % 
splitname)
+spec_scriptlets_bottom.append('%%post -n %s' % splitname)
 spec_scriptlets_bottom.append('# %s - postinst' % splitname)
 spec_scriptlets_bottom.append(splitrpostinst)
 spec_scriptlets_bottom.append('')
@@ -564,12 +564,12 @@ python write_specfile () {
 spec_preamble_top.append('')
 
 if srcrpreinst:
-spec_scriptlets_top.append('%pre -p "/bin/sh -e"')
+spec_scriptlets_top.append('%pre')
 spec_scriptlets_top.append('# %s - preinst' % srcname)
 spec_scriptlets_top.append(srcrpreinst)
 spec_scriptlets_top.append('')
 if srcrpostinst:
-spec_scriptlets_top.append('%post -p "/bin/sh -e"')
+spec_scriptlets_top.append('%post')
 spec_scriptlets_top.append('# %s - postinst' % srcname)
 spec_scriptlets_top.append(srcrpostinst)
 spec_scriptlets_top.append('')
-- 
2.15.1

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Alexander Kanavin
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: Alexander Kanavin 
---
 meta/lib/oe/package_manager.py | 18 +++---
 1 file changed, 15 insertions(+), 3 deletions(-)

diff --git a/meta/lib/oe/package_manager.py b/meta/lib/oe/package_manager.py
index f7e013437c9..1ae31f8e744 100644
--- a/meta/lib/oe/package_manager.py
+++ b/meta/lib/oe/package_manager.py
@@ -83,6 +83,11 @@ def opkg_query(cmd_output):
 
 return output
 
+# Note: this should be bb.fatal in the future.
+def failed_postinsts_warn(pkgs, log_path):
+bb.warn("""Intentionally failing postinstall scriptlets of %s to defer 
them to first boot is deprecated. Please place them into 
pkg_postinst_ontarget_${PN} ().
+If deferring to first boot wasn't the intent, then scriptlet failure may mean 
an issue in the recipe, or a regression elsewhere.
+Details of the failure are in %s.""" %(pkgs, log_path))
 
 class Indexer(object, metaclass=ABCMeta):
 def __init__(self, d, deploy_dir):
@@ -605,8 +610,7 @@ class RpmPM(PackageManager):
 failed_scriptlets_pkgnames[line.split()[-1]] = True
 
 if len(failed_scriptlets_pkgnames) > 0:
-bb.warn("Intentionally failing postinstall scriptlets of %s to 
defer them to first boot is deprecated. Please place them into 
pkg_postinst_ontarget_${PN} ()." %(list(failed_scriptlets_pkgnames.keys(
-bb.warn("If deferring to first boot wasn't the intent, then 
scriptlet failure may mean an issue in the recipe, or a regression elsewhere.")
+failed_postinsts_warn(list(failed_scriptlets_pkgnames.keys()), 
self.d.expand("${T}/log.do_rootfs"))
 for pkg in failed_scriptlets_pkgnames.keys():
 self.save_rpmpostinst(pkg)
 
@@ -1068,6 +1072,13 @@ class OpkgPM(OpkgDpkgPM):
 bb.note(cmd)
 output = subprocess.check_output(cmd.split(), 
stderr=subprocess.STDOUT).decode("utf-8")
 bb.note(output)
+failed_pkgs = []
+for line in output.split('\n'):
+if line.endswith("configuration required on target."):
+bb.warn(line)
+failed_pkgs.append(line.split(".")[0])
+if failed_pkgs:
+failed_postinsts_warn(failed_pkgs, 
self.d.expand("${T}/log.do_rootfs"))
 except subprocess.CalledProcessError as e:
 (bb.fatal, bb.note)[attempt_only]("Unable to install packages. "
   "Command '%s' returned %d:\n%s" %
@@ -1331,9 +1342,10 @@ class DpkgPM(OpkgDpkgPM):
 stderr=subprocess.STDOUT).decode("utf-8")
 bb.note(output)
 except subprocess.CalledProcessError as e:
-bb.note("%s for package %s failed with %d:\n%s" %
+bb.warn("%s for package %s failed with %d:\n%s" %
 (control_script.name, pkg_name, e.returncode,
 e.output.decode("utf-8")))
+failed_postinsts_warn([pkg_name], 
self.d.expand("${T}/log.do_rootfs"))
 failed_pkgs.append(pkg_name)
 break
 
-- 
2.15.1

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Martin Jansa
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 DISTRO_FEATURES.
2) include libpam and pam-plugin-wheel in packagegroup-core-lbs
(and RDEPENDS_packagegroup-core-lsb-runtime-add) only when pam is in
DISTRO_FEATURES?

The warning says that libpam is broken without pam in DISTRO_FEATURES, I'm
not sure how much LSB tests exercise it, but if the warning is correct,
then it was broken in poky-lsb builds runtime already.

Regards,

On Mon, Feb 5, 2018 at 12:54 PM, Burton, Ross  wrote:

> This breaks world builds on the autobuilder with poky-lsb:
>
> https://autobuilder.yocto.io/builders/nightly-world/builds/
> 736/steps/BuildImages/logs/stdio
>
> Ross
>
> On 1 February 2018 at 14:34, Martin Jansa  wrote:
>
>> * replace do_pam_sanity function with distro_features_check inherit
>> * fixes:
>>   WARNING: libpam-1.3.0-r5 do_pam_sanity: Building libpam but 'pam' isn't
>> in DISTRO_FEATURES, PAM won't work correctly
>>   in world builds and prevents user to build libpam at all without pam
>>   in DISTRO_FEATURES, I don't see any users of this which wouldn't respect
>>   pam in DISTRO_FEATURES
>> * only libuser is depending on libpam without respecting DISTRO_FEATURES
>> * there are few recipes in meta-oe layers depending on libpam without
>>   respecting DISTRO_FEATURES, I've sent patch for them:
>>   samba, openwsman, pam-ssh-agent-auth, sblim-sfcb, passwdqc, python-pam,
>> smbnetfs
>>   and omxplayer in meta-raspberrypi, I've sent PR for that one:
>>   https://github.com/agherzan/meta-raspberrypi/pull/192
>>
>> Signed-off-by: Martin Jansa 
>> ---
>>  meta/recipes-extended/libuser/libuser_0.62.bb | 3 +++
>>  meta/recipes-extended/pam/libpam_1.3.0.bb | 7 ++-
>>  2 files changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/meta/recipes-extended/libuser/libuser_0.62.bb
>> b/meta/recipes-extended/libuser/libuser_0.62.bb
>> index 1765346646..7ec54eb16e 100644
>> --- a/meta/recipes-extended/libuser/libuser_0.62.bb
>> +++ b/meta/recipes-extended/libuser/libuser_0.62.bb
>> @@ -22,6 +22,9 @@ SRC_URI[sha256sum] = "a58ff4fabb01a25043b142185a33e
>> eea961109dd60d4b40b6a9df4fa3c
>>
>>  DEPENDS = "popt libpam glib-2.0 python3"
>>
>> +inherit distro_features_check
>> +REQUIRED_DISTRO_FEATURES = "pam"
>> +
>>  inherit autotools gettext python3native python3-dir pkgconfig gtk-doc
>>
>>  EXTRA_OEMAKE = "PYTHON_CPPFLAGS=-I${STAGING_I
>> NCDIR}/${PYTHON_DIR}${PYTHON_ABI}"
>> diff --git a/meta/recipes-extended/pam/libpam_1.3.0.bb
>> b/meta/recipes-extended/pam/libpam_1.3.0.bb
>> index 8f7753d001..92ab72a42f 100644
>> --- a/meta/recipes-extended/pam/libpam_1.3.0.bb
>> +++ b/meta/recipes-extended/pam/libpam_1.3.0.bb
>> @@ -151,11 +151,8 @@ do_install() {
>> fi
>>  }
>>
>> -python do_pam_sanity () {
>> -if not bb.utils.contains('DISTRO_FEATURES', 'pam', True, False, d):
>> -bb.warn("Building libpam but 'pam' isn't in DISTRO_FEATURES, PAM
>> won't work correctly")
>> -}
>> -addtask pam_sanity before do_configure
>> +inherit distro_features_check
>> +REQUIRED_DISTRO_FEATURES = "pam"
>>
>>  BBCLASSEXTEND = "nativesdk native"
>>
>> --
>> 2.15.1
>>
>> --
>> ___
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>
>
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Ross Burton
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.

[1] oe-core 0ff62b0462f3f64672bd4704de9a192eb1a730d1

Signed-off-by: Ross Burton 
---
 meta/recipes-core/expat/expat_2.2.5.bb | 5 -
 1 file changed, 5 deletions(-)

diff --git a/meta/recipes-core/expat/expat_2.2.5.bb 
b/meta/recipes-core/expat/expat_2.2.5.bb
index f7a5b36ac74..bce59298e5b 100644
--- a/meta/recipes-core/expat/expat_2.2.5.bb
+++ b/meta/recipes-core/expat/expat_2.2.5.bb
@@ -18,11 +18,6 @@ SRC_URI[sha256sum] = 
"d9dc32efba7e74f788fcc4f212a43216fc37cf5f23f4c2339664d47335
 
 inherit autotools lib_package
 
-# This package uses an archive format known to have issue with some
-# versions of gzip
-DEPENDS += "pigz-native"
-do_unpack[depends] += "pigz-native:do_populate_sysroot"
-
 do_configure_prepend () {
rm -f ${S}/conftools/libtool.m4
 }
-- 
2.11.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Ross Burton
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
--- a/meta/recipes-extended/pigz/pigz_2.4.bb
+++ b/meta/recipes-extended/pigz/pigz_2.4.bb
@@ -8,10 +8,10 @@ SECTION = "console/utils"
 LICENSE = "Zlib & Apache-2.0"
 LIC_FILES_CHKSUM = 
"file://pigz.c;md5=9ae6dee8ceba9610596ed0ada493d142;beginline=7;endline=21"
 
-SRC_URI = 
"https://github.com/madler/pigz/archive/v${PV}.tar.gz;downloadfilename=${BP}.tar.gz";
-SRC_URI[md5sum] = "3c8a601db141d3013ef9fe5f2daaf73f"
-SRC_URI[sha256sum] = 
"e228e7d18b34c4ece8d596eb6eee97bde533c6beedbb728d07d3abe90b4b1b52"
-
+SRC_URI = "http://zlib.net/${BPN}/fossils/${BP}.tar.gz";
+SRC_URI[md5sum] = "def2f6e19d9d8231445adc1349d346df"
+SRC_URI[sha256sum] = 
"a4f816222a7b4269bd232680590b579ccc72591f1bb5adafcd7208ca77e14f73"
+# Point this at the homepage in case /fossils/ isn't updated
 UPSTREAM_CHECK_URI = "http://zlib.net/${BPN}/";
 UPSTREAM_CHECK_REGEX = "pigz-(?P.*)\.tar"
 
-- 
2.11.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Ross Burton
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 -
 meta/recipes-extended/pigz/pigz_2.4.bb | 21 +
 2 files changed, 1 insertion(+), 21 deletions(-)

diff --git a/meta/conf/distro/include/default-providers.inc 
b/meta/conf/distro/include/default-providers.inc
index c1cc97fccc7..e65c1ed323d 100644
--- a/meta/conf/distro/include/default-providers.inc
+++ b/meta/conf/distro/include/default-providers.inc
@@ -42,7 +42,6 @@ PREFERRED_PROVIDER_opkg ?= "opkg"
 PREFERRED_PROVIDER_opkg-native ?= "opkg-native"
 PREFERRED_PROVIDER_nativesdk-opkg ?= "nativesdk-opkg"
 PREFERRED_PROVIDER_console-tools ?= "kbd"
-PREFERRED_PROVIDER_gzip-native ?= "pigz-native"
 PREFERRED_PROVIDER_udev ?= 
"${@bb.utils.contains('DISTRO_FEATURES','systemd','systemd','eudev',d)}"
 PREFERRED_RPROVIDER_bluez-hcidump ?= 
"${@bb.utils.contains('DISTRO_FEATURES','bluetooth 
bluez5','bluez5','bluez-hcidump',d)}"
 # Alternative is ltp-ddt in meta-oe: 
meta-oe/recipes-devtools/ltp-ddt/ltp-ddt_0.0.4.bb
diff --git a/meta/recipes-extended/pigz/pigz_2.4.bb 
b/meta/recipes-extended/pigz/pigz_2.4.bb
index cb41154dafe..20e4154434f 100644
--- a/meta/recipes-extended/pigz/pigz_2.4.bb
+++ b/meta/recipes-extended/pigz/pigz_2.4.bb
@@ -8,8 +8,6 @@ SECTION = "console/utils"
 LICENSE = "Zlib & Apache-2.0"
 LIC_FILES_CHKSUM = 
"file://pigz.c;md5=9ae6dee8ceba9610596ed0ada493d142;beginline=7;endline=21"
 
-PROVIDES_class-native += "gzip-native"
-
 SRC_URI = 
"https://github.com/madler/pigz/archive/v${PV}.tar.gz;downloadfilename=${BP}.tar.gz";
 SRC_URI[md5sum] = "3c8a601db141d3013ef9fe5f2daaf73f"
 SRC_URI[sha256sum] = 
"e228e7d18b34c4ece8d596eb6eee97bde533c6beedbb728d07d3abe90b4b1b52"
@@ -21,9 +19,7 @@ DEPENDS = "zlib"
 
 EXTRA_OEMAKE = "-e MAKEFLAGS="
 
-inherit update-alternatives
-
-do_install_class-target() {
+do_install() {
# Install files into /bin (FHS), which is typical place for gzip
install -d ${D}${base_bindir}
install ${B}/pigz ${D}${base_bindir}/pigz
@@ -31,19 +27,4 @@ do_install_class-target() {
ln -nsf pigz ${D}${base_bindir}/pigzcat
 }
 
-do_install() {
-   install -d ${D}${bindir}
-   install ${B}/pigz ${D}${bindir}/gzip
-   ln -nsf gzip ${D}${bindir}/gunzip
-   ln -nsf gzip ${D}${bindir}/zcat
-}
-
-ALTERNATIVE_PRIORITY = "80"
-ALTERNATIVE_${PN} = "gunzip gzip zcat"
-ALTERNATIVE_${PN}_class-nativesdk = ""
-ALTERNATIVE_LINK_NAME[gunzip] = "${base_bindir}/gunzip"
-ALTERNATIVE_LINK_NAME[gzip] = "${base_bindir}/gzip"
-ALTERNATIVE_LINK_NAME[zcat] = "${base_bindir}/zcat"
-ALTERNATIVE_TARGET = "${base_bindir}/pigz"
-
 BBCLASSEXTEND = "native nativesdk"
-- 
2.11.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Ross Burton
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 meta/recipes-core/expat/expat.inc

diff --git a/meta/recipes-core/expat/expat.inc 
b/meta/recipes-core/expat/expat.inc
deleted file mode 100644
index 0ee6c276d99..000
--- a/meta/recipes-core/expat/expat.inc
+++ /dev/null
@@ -1,25 +0,0 @@
-SUMMARY = "A stream-oriented XML parser library"
-DESCRIPTION = "Expat is an XML parser library written in C. It is a 
stream-oriented parser in which an application registers handlers for things 
the parser might find in the XML document (like start tags)"
-HOMEPAGE = "http://expat.sourceforge.net/";
-SECTION = "libs"
-LICENSE = "MIT"
-
-SRC_URI = "${SOURCEFORGE_MIRROR}/expat/expat-${PV}.tar.bz2 \
-   file://autotools.patch \
-   file://libtool-tag.patch \
- "
-
-SRC_URI_append_class-native = " file://no_getrandom.patch"
-
-inherit autotools lib_package
-
-# This package uses an archive format known to have issue with some
-# versions of gzip
-DEPENDS += "pigz-native"
-do_unpack[depends] += "pigz-native:do_populate_sysroot"
-
-do_configure_prepend () {
-   rm -f ${S}/conftools/libtool.m4
-}
-
-BBCLASSEXTEND = "native nativesdk"
diff --git a/meta/recipes-core/expat/expat_2.2.5.bb 
b/meta/recipes-core/expat/expat_2.2.5.bb
index 337287b93bc..f7a5b36ac74 100644
--- a/meta/recipes-core/expat/expat_2.2.5.bb
+++ b/meta/recipes-core/expat/expat_2.2.5.bb
@@ -1,4 +1,30 @@
-require expat.inc
+SUMMARY = "A stream-oriented XML parser library"
+DESCRIPTION = "Expat is an XML parser library written in C. It is a 
stream-oriented parser in which an application registers handlers for things 
the parser might find in the XML document (like start tags)"
+HOMEPAGE = "http://expat.sourceforge.net/";
+SECTION = "libs"
+LICENSE = "MIT"
+
 LIC_FILES_CHKSUM = "file://COPYING;md5=5b8620d98e49772d95fc1d291c26aa79"
+
+SRC_URI = "${SOURCEFORGE_MIRROR}/expat/expat-${PV}.tar.bz2 \
+   file://autotools.patch \
+   file://libtool-tag.patch \
+ "
+
+SRC_URI_append_class-native = " file://no_getrandom.patch"
+
 SRC_URI[md5sum] = "789e297f547980fc9ecc036f9a070d49"
 SRC_URI[sha256sum] = 
"d9dc32efba7e74f788fcc4f212a43216fc37cf5f23f4c2339664d473353aedf6"
+
+inherit autotools lib_package
+
+# This package uses an archive format known to have issue with some
+# versions of gzip
+DEPENDS += "pigz-native"
+do_unpack[depends] += "pigz-native:do_populate_sysroot"
+
+do_configure_prepend () {
+   rm -f ${S}/conftools/libtool.m4
+}
+
+BBCLASSEXTEND = "native nativesdk"
-- 
2.11.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Böszörményi Zoltán

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 actually solved some other 
problems I was having as well. Still one left to fix:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=12534

See also the comment I added to that bugreport just now.


Cool! Can we have a joint effort in the merged patches?

Also, can you please look into this fix I made against bitbake?
At least one node module (cli-color) has cyclic dependencies,
making the npm fetcher looping infinitely.
http://lists.openembedded.org/pipermail/bitbake-devel/2018-February/009199.html



Best regards, Matthijs



2018-02-04 23:23 keltezéssel, mpvader írta:

npm now requires --force to clean the cache, see [1]. Also, use clean
instead of clear since the latter is an alias.

[1]


https://github.com/npm/npm/commit/34f24c8381235790945208d25ac193bc
97a2

1b79

Signed-off-by: mpvader 
---
   meta/classes/npm.bbclass | 2 +-
   1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/npm.bbclass b/meta/classes/npm.bbclass index
a69bedb..43aed36 100644
--- a/meta/classes/npm.bbclass
+++ b/meta/classes/npm.bbclass
@@ -31,7 +31,7 @@ npm_do_compile() {
fi
npm set cache ${WORKDIR}/npm_cache
# clear cache before every build
-   npm cache clear
+   npm cache clean --force
# Install pkg into ${S} without going to the registry
if [  "${NPM_INSTALL_DEV}" = "1" ]; then
npm --arch=${NPM_ARCH} --target_arch=${NPM_ARCH} --

no-registry

install






--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Burton, Ross
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 merging.

Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Stefan Stanacar
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
> do_unpack if
> there are type=kmeta or file:// entries in the SRC_URI value of the kernel
> recipe.
> (which is the case for linux-yocto).
>
> Make this a separate task so that it actually gets run for kernel recipes
> with
> no file:// or type=kmeta in SRC_URI.
>
> Signed-off-by: Stefan Stanacar 
> ---
>  meta/classes/kernel.bbclass | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
> index 2f6eca3..6a8d6e8 100644
> --- a/meta/classes/kernel.bbclass
> +++ b/meta/classes/kernel.bbclass
> @@ -125,7 +125,7 @@ inherit ${KERNEL_CLASSES}
>  # the symlink.
>  do_unpack[cleandirs] += " ${S} ${STAGING_KERNEL_DIR} ${B}
> ${STAGING_KERNEL_BUILDDIR}"
>  do_clean[cleandirs] += " ${S} ${STAGING_KERNEL_DIR} ${B}
> ${STAGING_KERNEL_BUILDDIR}"
> -base_do_unpack_append () {
> +python do_symlink_staging_dir () {
>  s = d.getVar("S")
>  if s[-1] == '/':
>  # drop trailing slash, so that os.symlink(kernsrc, s) doesn't use
> s as directory name and fail
> @@ -142,6 +142,7 @@ base_do_unpack_append () {
>  shutil.move(s, kernsrc)
>  os.symlink(kernsrc, s)
>  }
> +addtask do_symlink_staging_dir after do_unpack before do_patch
> do_configure
>
>  inherit kernel-arch deploy
>
> --
> 2.7.4
>
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2018-02-06 Thread Paul Eggleton
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:
> > >
> > > > Am I supposed to see bunch of these warnings (3 during parsing and 20
> > more
> > > > during build):
> > > >
> > > > WARNING: Variable key RDEPENDS_${KERNEL_PACKAGE_NAME}-base
> > > > (${KERNEL_PACKAGE_NAME}-image) replaces original key
> > RDEPENDS_kernel-base
> > > > (kernel-devicetree).
> > > >
> > > >
> > > > From kernel.bbclass:
> > > >
> > > > # Allow machines to override this dependency if kernel image files are
> > > > # not wanted in images as standard
> > > > RDEPENDS_${KERNEL_PACKAGE_NAME}-base ?= "${KERNEL_PACKAGE_NAME}-image"
> > > >
> > >
> > > That's your kernel recipe not liking the new multiple-name kernel
> > classes,
> > > and if your problem is the same as oe-core's qemu* machines then this is
> > > the fix:
> > >
> > > -RDEPENDS_kernel-base = ""
> > > +RDEPENDS_${KERNEL_PACKAGE_NAME}-base = ""
> >
> > Ah, I see, thanks! I assume all other operations with that variable (like
> > appends) would have to be changed similarly?
> >
> 
> Yes.
> 
> CCing Paul, master of release notes, to ensure this gets into the migration
> guide. :)

I've added this to:

  https://wiki.yoctoproject.org/wiki/FutureMigrationGuide

There must be a load missing from there for 2.5 so if you can think of 
anything that needs adding, in whatever raw form you can, go for it.

Cheers,
Paul

-- 
Paul Eggleton
Intel Open Source Technology Centre
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core