[OE-core] [PATCH] iproute2: Upgrade 4.10.0 -> 4.11.0

[Changhyeok Bae]

Signed-off-by: Changhyeok Bae 
---
 .../iproute2/{iproute2_4.10.0.bb => iproute2_4.11.0.bb}   | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-connectivity/iproute2/{iproute2_4.10.0.bb => 
iproute2_4.11.0.bb} (75%)

diff --git a/meta/recipes-connectivity/iproute2/iproute2_4.10.0.bb 
b/meta/recipes-connectivity/iproute2/iproute2_4.11.0.bb
similarity index 75%
rename from meta/recipes-connectivity/iproute2/iproute2_4.10.0.bb
rename to meta/recipes-connectivity/iproute2/iproute2_4.11.0.bb
index 063d467..0ee0f21 100644
--- a/meta/recipes-connectivity/iproute2/iproute2_4.10.0.bb
+++ b/meta/recipes-connectivity/iproute2/iproute2_4.11.0.bb
@@ -7,8 +7,8 @@ SRC_URI = 
"${KERNELORG_MIRROR}/linux/utils/net/${BPN}/${BP}.tar.xz \
file://0001-include-stdint.h-explicitly-for-UINT16_MAX.patch \
   "
 
-SRC_URI[md5sum] = "b94a2b0edefaeac124dc8f5d006931b9"
-SRC_URI[sha256sum] = 
"22b1e1c1fc704ad35837e5a66103739727b8b48ac90b48c13f79b7367ff0a9a8"
+SRC_URI[md5sum] = "7a9498de88bcca95c305df6108ae197e"
+SRC_URI[sha256sum] = 
"72671028bda696d0cb8f48ec8e702581c3a501caeed33eec3a81d7041cbc8026"
 
 # CFLAGS are computed in Makefile and reference CCOPTS
 #
-- 
2.7.4

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

Re: [OE-core] [PATCH v2 1/1] multilib.bbclass: fix faulty redefinition of STAGING_KERNEL_DIR

[Petter Mabäcker]

 

Hi, 

Just realized this change was never merged into master, so see
this as a friendly reminder about this change-set (might have been lost
in the flood of changes in this time-frame). Not the most common use
case I guess, but would be good to finally get rid of the problem. If
you have any concerns about the change, please let me know. The solution
was briefly discussed with Richard on irc a couple of month ago, but if
someone thinks this should be solved in some other way, please initiate
a discussion :) 

BR Petter 

2017-05-15 06:17 skrev Petter Mabäcker:


> Due to the problem fixed in
> '56c677a multilib: Move redefinition
of STAGING_DIR_KERNEL'
> STAGING_KERNEL_DIR must be redefined for lib32
in multilib.bbclass.
> However this redefinition expanded
STAGING_KERNEL_DIR to an absolute
> path. This unconsciously added the
TMPDIR path in the sstate object,
> causing packages depended on
STAGING_KERNEL_DIR being rebuild if the
> TMPDIR was changed.
> 
> Solve
this by forcing the unexpanded TMPDIR variable to remain in the
>
beginning of STAGING_DIR_KERNEL (as default). Since TMPDIR is included
in
> BB_HASHBASE_WHITELIST, the sstate object will not be depended on
the
> expanded path anymore.
> 
> Signed-off-by: Petter Mabäcker

> ---
> meta/classes/multilib.bbclass | 4 +++-
> 1
file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git
a/meta/classes/multilib.bbclass b/meta/classes/multilib.bbclass
> index
ab04597..816f54e 100644
> --- a/meta/classes/multilib.bbclass
> +++
b/meta/classes/multilib.bbclass
> @@ -4,7 +4,9 @@ python
multilib_virtclass_handler () {
> if cls != "multilib" or not variant:
>
return
> 
> - e.data.setVar('STAGING_KERNEL_DIR',
e.data.getVar('STAGING_KERNEL_DIR'))
> + localdata =
bb.data.createCopy(e.data)
> + localdata.delVar('TMPDIR')
> +
e.data.setVar('STAGING_KERNEL_DIR',
localdata.getVar('STAGING_KERNEL_DIR'))
> 
> # There should only be one
kernel in multilib configs
> # We also skip multilib setup for module
packages.
> -- 
> 1.9.1
 -- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [morty][PATCH] elfutils: fix building elfutils-native with GCC7

[Cody P Schafer]

This is heavily based on the oe-core master commit with the same
subject, but includes a backport of upstream's fix for the fallthrough
warnings rebased to 0.166 (the oe-core patch which targeted 0.168 did
not apply), a rebase of the format-truncation patch, and a backport of
the upstream format-length patch.

Info from OE-Core master patch follows:

From OE-Core rev: aaf4c4f3d09ac3897205417eb15e19d54e0c0d05
From: Joshua Lock 

Backport a fix from upstream for a -Wformat-truncation=2 warning
and implement a simple fix for a -Wimplicit-fallthrough warning.

Signed-off-by: Joshua Lock 
Signed-off-by: Richard Purdie 

Signed-off-by: Cody P Schafer 
---
 ...-GCC7-Wimplicit-fallthrough-support-fixes.patch | 318 +
 .../0001-ar-Fix-GCC7-Wformat-length-issues.patch   | 125 
 .../elfutils-0.166/Fix_one_GCC7_warning.patch  |  45 +++
 .../elfutils/elfutils-0.166/fallthrough.patch  |  36 +++
 meta/recipes-devtools/elfutils/elfutils_0.166.bb   |   5 +
 5 files changed, 529 insertions(+)
 create mode 100644 
meta/recipes-devtools/elfutils/elfutils-0.166/0001-Add-GCC7-Wimplicit-fallthrough-support-fixes.patch
 create mode 100644 
meta/recipes-devtools/elfutils/elfutils-0.166/0001-ar-Fix-GCC7-Wformat-length-issues.patch
 create mode 100644 
meta/recipes-devtools/elfutils/elfutils-0.166/Fix_one_GCC7_warning.patch
 create mode 100644 
meta/recipes-devtools/elfutils/elfutils-0.166/fallthrough.patch

diff --git 
a/meta/recipes-devtools/elfutils/elfutils-0.166/0001-Add-GCC7-Wimplicit-fallthrough-support-fixes.patch
 
b/meta/recipes-devtools/elfutils/elfutils-0.166/0001-Add-GCC7-Wimplicit-fallthrough-support-fixes.patch
new file mode 100644
index 00..a240323f33
--- /dev/null
+++ 
b/meta/recipes-devtools/elfutils/elfutils-0.166/0001-Add-GCC7-Wimplicit-fallthrough-support-fixes.patch
@@ -0,0 +1,318 @@
+From 09949994e76eea3c1230a5c88ffa8fdf588b120f Mon Sep 17 00:00:00 2001
+From: Mark Wielaard 
+Date: Wed, 2 Nov 2016 13:29:26 +0100
+Subject: [PATCH] Add GCC7 -Wimplicit-fallthrough support/fixes.
+
+GCC7 will have a new -Wimplicit-fallthrough warning. It did catch one
+small buglet in elflint option procession. So it seems useful to enable
+to make sure all swatch case fallthroughs are deliberate.
+
+Add configure check to detect whether gcc support -Wimplicit-fallthrough
+and enable it. Add fixes and explicit fallthrough comments where necessary.
+
+Signed-off-by: Mark Wielaard 
+
+Upstream-Status: Backport
+Upstream-Commit: a3cc8182b2ae05290b0eafa74b70746d7befc0e4
+---
+ backends/alpha_retval.c|  4 +---
+ backends/i386_regs.c   |  1 +
+ backends/i386_retval.c |  3 +--
+ backends/linux-core-note.c |  4 ++--
+ backends/ppc_regs.c|  2 +-
+ backends/x86_64_regs.c |  1 +
+ config/eu.am   |  8 +++-
+ configure.ac   | 10 ++
+ libcpu/i386_disasm.c   |  2 +-
+ libdw/cfi.c|  2 ++
+ libdw/encoded-value.h  |  1 +
+ libdwfl/dwfl_report_elf.c  |  2 +-
+ src/addr2line.c|  1 +
+ src/elfcompress.c  |  3 ++-
+ src/elflint.c  |  4 +++-
+ src/objdump.c  |  4 +++-
+ tests/backtrace-data.c |  1 +
+ tests/backtrace.c  |  2 +-
+ 18 files changed, 40 insertions(+), 15 deletions(-)
+
+diff --git a/backends/alpha_retval.c b/backends/alpha_retval.c
+index 53dbfa45..7232b462 100644
+--- a/backends/alpha_retval.c
 b/backends/alpha_retval.c
+@@ -130,9 +130,7 @@ alpha_return_value_location (Dwarf_Die *functypedie, const 
Dwarf_Op **locp)
+   return nloc_intreg;
+ }
+   }
+-
+-  /* Else fall through.  */
+-
++  /* Fallthrough */
+ case DW_TAG_structure_type:
+ case DW_TAG_class_type:
+ case DW_TAG_union_type:
+diff --git a/backends/i386_regs.c b/backends/i386_regs.c
+index fb8ded33..fd963a62 100644
+--- a/backends/i386_regs.c
 b/backends/i386_regs.c
+@@ -92,6 +92,7 @@ i386_register_info (Ebl *ebl __attribute__ ((unused)),
+ case 5:
+ case 8:
+   *type = DW_ATE_address;
++  /* Fallthrough */
+ case 0 ... 3:
+ case 6 ... 7:
+   name[0] = 'e';
+diff --git a/backends/i386_retval.c b/backends/i386_retval.c
+index 9da797d5..4aa646fe 100644
+--- a/backends/i386_retval.c
 b/backends/i386_retval.c
+@@ -122,9 +122,8 @@ i386_return_value_location (Dwarf_Die *functypedie, const 
Dwarf_Op **locp)
+ return nloc_intreg;
+   if (size <= 8)
+ return nloc_intregpair;
+-
+-  /* Else fall through.  */
+   }
++/* Fallthrough */
+ 
+ case DW_TAG_structure_type:
+ case DW_TAG_class_type:
+diff --git a/backends/linux-core-note.c b/backends/linux-core-note.c
+index ff2b226f..321721f3 100644
+--- a/backends/linux-core-note.c
 b/backends/linux-core-note.c
+@@ -219,8 +219,8 @@ EBLHOOK(core_note) (const 

Re: [OE-core] Fun with npm shrinkwrap

[Davis, Michael]

> In fact, meta-nodejs is already in use here, and I've been told to give
> "inherit npm-base" a try. Is that what you mean?

Yes inherit npm-base should give you what you need. With the before mentioned 
limitations.

> How "unreproducible" will builds become? The license checks are not that
> critical as I wouldn't trust them right now anyway. Offline builds
> correlate with reproduciblilty - we need to archive the artifacts and
> generate images with changes later on, independent of what happened
> outside meanwhile. Not a killer right now, but not an option on the long
> run.

Mostly it just means you may get slightly different versions of dependencies 
over time.
Depending mostly on how locked down your package.json and those of your deps 
are.
https://docs.npmjs.com/misc/semver


> PS: Top-posting is considered evil.
The sad shame of having to use Outlook.  No IMAP / POP and davmail hates me.
Bottom-posting is dying a slow death these days.  Only see it in Linux mailing 
lists for the most part.

--
Mike

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

Re: [OE-core] [morty][PATCH] gcc-6.2: backport fix of check for empty string in ubsan.c

[Khem Raj]

On Wed, Jun 7, 2017 at 11:46 AM, Cody P Schafer  wrote:
> From: Joshua Lock 
>
> Building gcc-cross-initial with GCC7 on the host fails due to the
> comparison of a pointer to an integer in ubsan_use_new_style_p, which
> is forbidden by ISO C++:
>
> ubsan.c:1474:23: error: ISO C++ forbids comparison between pointer and
> integer [-fpermissive]
>|| xloc.file == '\0' || xloc.file[0] == '\xff'
>
> Backport the fix from upstream GCC to enable the build with GCC 7
>

this is fine


> (From OE-Core rev: 7a7fcbab0365b9501c737dbc02715be14dda72a3)
>
> Signed-off-by: Joshua Lock 
> Signed-off-by: Richard Purdie 
> Signed-off-by: Cody P Schafer 
> ---
>  meta/recipes-devtools/gcc/gcc-6.2.inc  |  5 ++--
>  .../gcc/gcc-6.2/ubsan-fix-check-empty-string.patch | 28 
> ++
>  2 files changed, 31 insertions(+), 2 deletions(-)
>  create mode 100644 
> meta/recipes-devtools/gcc/gcc-6.2/ubsan-fix-check-empty-string.patch
>
> diff --git a/meta/recipes-devtools/gcc/gcc-6.2.inc 
> b/meta/recipes-devtools/gcc/gcc-6.2.inc
> index b118995e1d..39ae653805 100644
> --- a/meta/recipes-devtools/gcc/gcc-6.2.inc
> +++ b/meta/recipes-devtools/gcc/gcc-6.2.inc
> @@ -80,8 +80,9 @@ SRC_URI = "\
> 
> file://0047-libgcc_s-Use-alias-for-__cpu_indicator_init-instead-.patch \
> ${BACKPORTS} \
>  "
> -BACKPORTS = ""
> -
> +BACKPORTS = "\
> +   file://ubsan-fix-check-empty-string.patch \
> +"
>  SRC_URI[md5sum] = "9768625159663b300ae4de2f4745fcc4"
>  SRC_URI[sha256sum] = 
> "9944589fc722d3e66308c0ce5257788ebd7872982a718aa2516123940671b7c5"
>
> diff --git 
> a/meta/recipes-devtools/gcc/gcc-6.2/ubsan-fix-check-empty-string.patch 
> b/meta/recipes-devtools/gcc/gcc-6.2/ubsan-fix-check-empty-string.patch
> new file mode 100644
> index 00..c0127198e0
> --- /dev/null
> +++ b/meta/recipes-devtools/gcc/gcc-6.2/ubsan-fix-check-empty-string.patch
> @@ -0,0 +1,28 @@
> +From 8db2cf6353c13f2a84cbe49b689654897906c499 Mon Sep 17 00:00:00 2001
> +From: kyukhin 
> +Date: Sat, 3 Sep 2016 10:57:05 +
> +Subject: [PATCH] gcc/  * ubsan.c (ubsan_use_new_style_p): Fix check for empty
> + string.
> +
> +git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@239971 
> 138bc75d-0d04-0410-961f-82ee72b054a4
> +
> +Upstream-Status: Backport
> +Signed-off-by: Joshua Lock 
> +
> +---
> + gcc/ubsan.c   | 2 +-
> + 2 files changed, 5 insertions(+), 1 deletion(-)
> +
> +Index: gcc-6.3.0/gcc/ubsan.c
> +===
> +--- gcc-6.3.0.orig/gcc/ubsan.c
>  gcc-6.3.0/gcc/ubsan.c
> +@@ -1471,7 +1471,7 @@ ubsan_use_new_style_p (location_t loc)
> +
> +   expanded_location xloc = expand_location (loc);
> +   if (xloc.file == NULL || strncmp (xloc.file, "\1", 2) == 0
> +-  || xloc.file == '\0' || xloc.file[0] == '\xff'
> ++  || xloc.file[0] == '\0' || xloc.file[0] == '\xff'
> +   || xloc.file[1] == '\xff')
> + return false;
> +
> --
> 2.13.0
>
> --
> ___
> 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] [morty][PATCH] gcc-6.2: backport fix of check for empty string in ubsan.c

[Cody P Schafer]

On Wed, Jun 7, 2017 at 2:46 PM, Cody P Schafer  wrote:
> From: Joshua Lock 
>
> Building gcc-cross-initial with GCC7 on the host fails due to the
> comparison of a pointer to an integer in ubsan_use_new_style_p, which
> is forbidden by ISO C++:

The patch to oe-core master was for gcc 6.3, I've modified it to apply
to gcc 6.2 (which is in morty).

We probably also need to backport the CVE patch, and examine the
6.2..6.3 log to see if there are any other critical patches. Or just
put gcc 6.3 into morty.

This at just gets gcc building for me again.
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] tcf-agent: Fix daemon termination

[Burton, Ross]

On 7 June 2017 at 17:33, Martin Kelly  wrote:

> Which patch are you referring to? I used git send-email for the systemd
> patch, and it applies just fine for me on OE-core master (using patch -p1).
>

Sorry, forgot to trim recipients.  Yes, it was Jan's patch.

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

[OE-core] [morty][PATCH] gcc-6.2: backport fix of check for empty string in ubsan.c

[Cody P Schafer]

From: Joshua Lock 

Building gcc-cross-initial with GCC7 on the host fails due to the
comparison of a pointer to an integer in ubsan_use_new_style_p, which
is forbidden by ISO C++:

ubsan.c:1474:23: error: ISO C++ forbids comparison between pointer and
integer [-fpermissive]
   || xloc.file == '\0' || xloc.file[0] == '\xff'

Backport the fix from upstream GCC to enable the build with GCC 7

(From OE-Core rev: 7a7fcbab0365b9501c737dbc02715be14dda72a3)

Signed-off-by: Joshua Lock 
Signed-off-by: Richard Purdie 
Signed-off-by: Cody P Schafer 
---
 meta/recipes-devtools/gcc/gcc-6.2.inc  |  5 ++--
 .../gcc/gcc-6.2/ubsan-fix-check-empty-string.patch | 28 ++
 2 files changed, 31 insertions(+), 2 deletions(-)
 create mode 100644 
meta/recipes-devtools/gcc/gcc-6.2/ubsan-fix-check-empty-string.patch

diff --git a/meta/recipes-devtools/gcc/gcc-6.2.inc 
b/meta/recipes-devtools/gcc/gcc-6.2.inc
index b118995e1d..39ae653805 100644
--- a/meta/recipes-devtools/gcc/gcc-6.2.inc
+++ b/meta/recipes-devtools/gcc/gcc-6.2.inc
@@ -80,8 +80,9 @@ SRC_URI = "\

file://0047-libgcc_s-Use-alias-for-__cpu_indicator_init-instead-.patch \
${BACKPORTS} \
 "
-BACKPORTS = ""
-
+BACKPORTS = "\
+   file://ubsan-fix-check-empty-string.patch \
+"
 SRC_URI[md5sum] = "9768625159663b300ae4de2f4745fcc4"
 SRC_URI[sha256sum] = 
"9944589fc722d3e66308c0ce5257788ebd7872982a718aa2516123940671b7c5"
 
diff --git 
a/meta/recipes-devtools/gcc/gcc-6.2/ubsan-fix-check-empty-string.patch 
b/meta/recipes-devtools/gcc/gcc-6.2/ubsan-fix-check-empty-string.patch
new file mode 100644
index 00..c0127198e0
--- /dev/null
+++ b/meta/recipes-devtools/gcc/gcc-6.2/ubsan-fix-check-empty-string.patch
@@ -0,0 +1,28 @@
+From 8db2cf6353c13f2a84cbe49b689654897906c499 Mon Sep 17 00:00:00 2001
+From: kyukhin 
+Date: Sat, 3 Sep 2016 10:57:05 +
+Subject: [PATCH] gcc/  * ubsan.c (ubsan_use_new_style_p): Fix check for empty
+ string.
+
+git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@239971 
138bc75d-0d04-0410-961f-82ee72b054a4
+
+Upstream-Status: Backport
+Signed-off-by: Joshua Lock 
+
+---
+ gcc/ubsan.c   | 2 +-
+ 2 files changed, 5 insertions(+), 1 deletion(-)
+
+Index: gcc-6.3.0/gcc/ubsan.c
+===
+--- gcc-6.3.0.orig/gcc/ubsan.c
 gcc-6.3.0/gcc/ubsan.c
+@@ -1471,7 +1471,7 @@ ubsan_use_new_style_p (location_t loc)
+ 
+   expanded_location xloc = expand_location (loc);
+   if (xloc.file == NULL || strncmp (xloc.file, "\1", 2) == 0
+-  || xloc.file == '\0' || xloc.file[0] == '\xff'
++  || xloc.file[0] == '\0' || xloc.file[0] == '\xff'
+   || xloc.file[1] == '\xff')
+ return false;
+ 
-- 
2.13.0

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

Re: [OE-core] Fun with npm shrinkwrap

[Jan Kiszka]

On 2017-06-07 16:09, Davis, Michael wrote:
> If offline builds, license checking, or stable dependency versions are not 
> important to you then you can use the meta-nodejs layer.  It just uses the 
> yarn tool directly https://github.com/imyller/meta-nodejs.
> 

In fact, meta-nodejs is already in use here, and I've been told to give
"inherit npm-base" a try. Is that what you mean?

How "unreproducible" will builds become? The license checks are not that
critical as I wouldn't trust them right now anyway. Offline builds
correlate with reproduciblilty - we need to archive the artifacts and
generate images with changes later on, independent of what happened
outside meanwhile. Not a killer right now, but not an option on the long
run.

> 
> On a hijacked side note has yarn been considered as a solution to some of our 
> npm issues?
> It seems to be npm with built in licnese checking and better version 
> determination.
> Might not cover 100% of our use cases, but then npm only seems to work 50% of 
> the time without tweaking something anyways.
> 

Can't comment on yarn, but another colleague pointed out that the
machinery of arch-linux may also be worth a look, not only for the
nodejs/npm galaxy.

Thanks,
Jan

PS: Top-posting is considered evil.

-- 
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH v3] runtime/dnf: Add new dnf test cases

[Jose Perez Carranza]

When I tried this test image was built without using states hence 
"busybox*.rpm" and "curl*.rpm"where present under 
"tmp/deploy/rpm/core2_64" hence the repo i taking tha packages form 
there to add them to repo and used on the image, but when using sstates 
those packages are not being built so are not present on local build 
directory. is there any way to force those packages to be built to have 
them available on tmp/deploy/rpm/core2_64?


On 06/07/2017 05:21 AM, Burton, Ross wrote:


On 15 May 2017 at 14:50, > wrote:


Add test cases to test “exclude” and “installroot“ options, also
modify
the logic of filtering packages on the feed to have all the packages
needed by the tests.


Fails all over the autobuilder, for example:

http://errors.yoctoproject.org/Errors/Details/143886/

Ross


--
Saludos
José

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

Re: [OE-core] [PATCH] meta*: Add LAYERSERIES_COMPAT and LAYERSERIES_CORENAMES markup to layer.conf

[Peter Kjellerstedt]

> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
> Leonardo Sandoval
> Sent: den 7 juni 2017 18:51
> To: Richard Purdie 
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH] meta*: Add LAYERSERIES_COMPAT and
> LAYERSERIES_CORENAMES markup to layer.conf
> 
> On Wed, 2017-06-07 at 13:39 +0100, Richard Purdie wrote:
> > This means mismatched layers are more clearly identified to the user
> in
> > cases where compatibility has not been tested. This is perhaps not as
> > needed for the core repository (other than CORENAMES) but lets lead
> by
> > example.
> >
> > Signed-off-by: Richard Purdie 
> > ---
> >  meta-selftest/conf/layer.conf | 2 ++
> >  meta-skeleton/conf/layer.conf | 2 ++
> >  meta/conf/layer.conf  | 2 ++
> >  3 files changed, 6 insertions(+)
> >
> > diff --git a/meta-selftest/conf/layer.conf b/meta-
> selftest/conf/layer.conf
> > index a847b78..2a71895 100644
> > --- a/meta-selftest/conf/layer.conf
> > +++ b/meta-selftest/conf/layer.conf
> > @@ -8,3 +8,5 @@ BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
> >  BBFILE_COLLECTIONS += "selftest"
> >  BBFILE_PATTERN_selftest = "^${LAYERDIR}/"
> >  BBFILE_PRIORITY_selftest = "5"
> > +
> > +LAYERSERIES_COMPAT_selftest = "rocko"
> > diff --git a/meta-skeleton/conf/layer.conf b/meta-
> skeleton/conf/layer.conf
> > index aca1633..a15516a 100644
> > --- a/meta-skeleton/conf/layer.conf
> > +++ b/meta-skeleton/conf/layer.conf
> > @@ -13,3 +13,5 @@ BBFILE_PRIORITY_skeleton = "1"
> >  LAYERVERSION_skeleton = "1"
> >
> >  LAYERDEPENDS_skeleton = "core"
> > +
> > +LAYERSERIES_COMPAT_skeleton = "rocko"
> > diff --git a/meta/conf/layer.conf b/meta/conf/layer.conf
> > index fc16502..6d36aa1 100644
> > --- a/meta/conf/layer.conf
> > +++ b/meta/conf/layer.conf
> > @@ -11,6 +11,8 @@ BBFILE_PRIORITY_core = "5"
> >  # cause compatibility issues with other layers
> >  LAYERVERSION_core = "10"
> >
> > +LAYERSERIES_CORENAMES = "rocko"
> > +
> >  BBLAYERS_LAYERINDEX_NAME_core = "openembedded-core"
> 
> at oe-core, Is there a reason not to set all LAYERSERIES_COMPAT_* =
> "${LAYERSERIES_CORENAMES}"? this would make it easier to bump the
> COMPAT set of variables.

That is probably a bad idea, especially if the aim here is to lead 
by example, since otherwise you risk other layers to just blindly 
copying that and then we have gained nothing...

> >  # Set a variable to get to the top of the metadata location
> > --
> > 2.7.4

//Peter

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

Re: [OE-core] [PATCH v2 01/25] bitbake.conf: support for merged usr with DISTRO_FEATURE usrmerge

[Peter Kjellerstedt]

> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
> Patrick Ohly
> Sent: den 7 juni 2017 16:32
> To: Richard Purdie 
> Cc: Joshua Lock ; openembedded-
> c...@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH v2 01/25] bitbake.conf: support for
> merged usr with DISTRO_FEATURE usrmerge
> 
> On Wed, 2017-06-07 at 12:52 +0100, Richard Purdie wrote:
> > On Wed, 2017-02-22 at 10:26 +0200, Amarnath Valluri wrote:
> > > From: Joshua Lock 
> > >
> > > Modify bindir, libdir and sbindir to be exec_prefix/$d, rather than
> > > base_prefix/$d, when the usrmerge DISTRO_FEATURE is enabled.
> > >
> > > Signed-off-by: Joshua Lock 
> > > ---
> > >  meta/conf/bitbake.conf | 12 
> > >  1 file changed, 8 insertions(+), 4 deletions(-)
> >
> > I was asked to clarify the status of this series. We've taken many of
> > the changes but the core changes to bitbake.conf haven't been merged.
> >
> > Ross/I discussed it and we both feel that the bitbake.conf make the
> > file pretty unreadable. We'd therefore like to see this implemented
> > as a .inc file which gets included when the relevant DISTRO_FEATURE 
> > is set (or could just be included by the appropriate distro configs). 
> > This .inc file would then simply override the paths. I believe this 
> > would be a lot more readable than the current approach which is a 
> > key concern in the core config.

I actually suggested an alternative change to bitbake.conf in the GitHub 
review that changes bitbake.conf to take usrmerge into account:

https://github.com/avalluri/openembedded-core/commit/1655a93238902a883052a55d88ae14dd02243530

I will include my suggested solution here since I will refer to it 
below:

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 0f27e92e96..305eaff583 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -17,11 +17,13 @@ export base_prefix = ""
 export prefix = "/usr"
 export exec_prefix = "${prefix}"
 
+root_prefix = "${@bb.utils.contains('DISTRO_FEATURES', 'usrmerge', 
'${exec_prefix}', '${base_prefix}', d)}"
+
 # Base paths
-export base_bindir = "${base_prefix}/bin"
-export base_sbindir = "${base_prefix}/sbin"
-export base_libdir = "${base_prefix}/${baselib}"
-export nonarch_base_libdir = "${base_prefix}/lib"
+export base_bindir = "${root_prefix}/bin"
+export base_sbindir = "${root_prefix}/sbin"
+export base_libdir = "${root_prefix}/${baselib}"
+export nonarch_base_libdir = "${root_prefix}/lib"
 
 # Architecture independent paths
 export sysconfdir = "${base_prefix}/etc"

I think that better maintains the readability of the bitbake.conf file, 
while making the $root_prefix variable available as it can be useful in 
its own (e.g., in the systemd recipe).

> > The merge of the rest of this feature is therefore pending on the
> > development of such a patch, or a discussion convincing Ross/I why we
> > shouldn't take that approach for some reason.
> 
> Such a .inc file would have to be included after the "Include the rest
> of the config files." section, because DISTRO_FEATURES only has its
> final value (?) at that point. One also needs the patch that I
> coincidentally just sent today to the bitbake list which allows
> including such a file only when "usrmerge" is in DISTRO_FEATURES.
> 
> Would that be okay?
> 
> One downside is that code using the variables earlier will just see the
> non-usrmerge version, with no indication in "bitbake -e" that the value
> might have been different in the middle of parsing. The if check in the
> proposed patch has the same effect on the actual values, but at least
> it shows up in "bitbake -e". This is not a particularly strong argument
> either way, I just wanted to mention it.

Based on your concerns about when the path variables affected by 
usrmerge would have what values, maybe my suggested change above 
should be changed to define root_prefix like this instead:

root_prefix ?= "${base_prefix}"

and then we create a usrmerge.inc file with the following contents:

DISTRO_FEATURES_append = " usrmerge"

root_prefix = "${exec_prefix}"

This file should then be required by a layer.conf file so that 
root_prefix is set before bitbake.conf is read. That should make sure 
that there never is any risk of the paths being defined differently 
based on whether usrmerge has been added to DISTRO_FEATURES yet or not.
And it should be clear in bitbake -e how such a variable got its value.

The only minor drawback I see is that the usrmerge.inc file needs to 
be required from a layer.conf file rather than just adding usrmerge 
to DISTRO_FEATURES in ${DISTRO}.conf, but at least I could live with 
that. One could of course add an appropriate comment before the 
definition of the root_prefix variable, to clarify its use and maybe 
even point at the usrmerge.inc 

Re: [OE-core] [PATCH] tcf-agent: Fix daemon termination

[Martin Kelly]

On 06/07/2017 09:08 AM, Burton, Ross wrote:


On 6 June 2017 at 18:28, Martin Kelly > wrote:

I sent a separate patch for fixing the systemd issue, so I think we
can merge the two patches separately (they're both needed):

https://patchwork.openembedded.org/patch/140355/


Neither of our patches have been merged yet.


Sorry, somehow slipped through the net.

This patch doesn't apply as it's been corrupted by the mailer.  Please
use git-send-email instead of copy/pasting (I've managed to apply it
manually as it's a simple patch this time).

Ross



Which patch are you referring to? I used git send-email for the systemd 
patch, and it applies just fine for me on OE-core master (using patch -p1).

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

Re: [OE-core] [PATCH] meta*: Add LAYERSERIES_COMPAT and LAYERSERIES_CORENAMES markup to layer.conf

[Leonardo Sandoval]

On Wed, 2017-06-07 at 13:39 +0100, Richard Purdie wrote:
> This means mismatched layers are more clearly identified to the user in
> cases where compatibility has not been tested. This is perhaps not as
> needed for the core repository (other than CORENAMES) but lets lead by
> example.
> 
> Signed-off-by: Richard Purdie 
> ---
>  meta-selftest/conf/layer.conf | 2 ++
>  meta-skeleton/conf/layer.conf | 2 ++
>  meta/conf/layer.conf  | 2 ++
>  3 files changed, 6 insertions(+)
> 
> diff --git a/meta-selftest/conf/layer.conf b/meta-selftest/conf/layer.conf
> index a847b78..2a71895 100644
> --- a/meta-selftest/conf/layer.conf
> +++ b/meta-selftest/conf/layer.conf
> @@ -8,3 +8,5 @@ BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
>  BBFILE_COLLECTIONS += "selftest"
>  BBFILE_PATTERN_selftest = "^${LAYERDIR}/"
>  BBFILE_PRIORITY_selftest = "5"
> +
> +LAYERSERIES_COMPAT_selftest = "rocko"
> diff --git a/meta-skeleton/conf/layer.conf b/meta-skeleton/conf/layer.conf
> index aca1633..a15516a 100644
> --- a/meta-skeleton/conf/layer.conf
> +++ b/meta-skeleton/conf/layer.conf
> @@ -13,3 +13,5 @@ BBFILE_PRIORITY_skeleton = "1"
>  LAYERVERSION_skeleton = "1"
>  
>  LAYERDEPENDS_skeleton = "core"
> +
> +LAYERSERIES_COMPAT_skeleton = "rocko"
> diff --git a/meta/conf/layer.conf b/meta/conf/layer.conf
> index fc16502..6d36aa1 100644
> --- a/meta/conf/layer.conf
> +++ b/meta/conf/layer.conf
> @@ -11,6 +11,8 @@ BBFILE_PRIORITY_core = "5"
>  # cause compatibility issues with other layers
>  LAYERVERSION_core = "10"
>  
> +LAYERSERIES_CORENAMES = "rocko"
> +
>  BBLAYERS_LAYERINDEX_NAME_core = "openembedded-core"

at oe-core, Is there a reason not to set all LAYERSERIES_COMPAT_* =
"${LAYERSERIES_CORENAMES}"? this would make it easier to bump the COMPAT
set of variables.

>  
>  # Set a variable to get to the top of the metadata location
> -- 
> 2.7.4
> 


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

[OE-core] [PATCH] oeqa: Change the order to logDetails and logSummary

[Aníbal Limón]

Is better to log the summary at end to see in an easy way
the actual result of the test run.

[YOCTO #11622]

Signed-off-by: Aníbal Limón 
---
 meta/classes/testimage.bbclass| 2 +-
 meta/classes/testsdk.bbclass  | 4 ++--
 meta/lib/oeqa/core/context.py | 2 +-
 meta/lib/oeqa/selftest/context.py | 2 +-
 4 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/meta/classes/testimage.bbclass b/meta/classes/testimage.bbclass
index 1185593..6c33e16 100644
--- a/meta/classes/testimage.bbclass
+++ b/meta/classes/testimage.bbclass
@@ -292,8 +292,8 @@ def testimage_main(d):
 # Show results (if we have them)
 if not results:
 bb.fatal('%s - FAILED - tests were interrupted during execution' % pn)
-results.logSummary(pn)
 results.logDetails()
+results.logSummary(pn)
 if not results.wasSuccessful():
 bb.fatal('%s - FAILED - check the task log and the ssh log' % pn)
 
diff --git a/meta/classes/testsdk.bbclass b/meta/classes/testsdk.bbclass
index 8a9e680..6b51a33 100644
--- a/meta/classes/testsdk.bbclass
+++ b/meta/classes/testsdk.bbclass
@@ -72,8 +72,8 @@ def testsdk_main(d):
 component = "%s %s" % (pn, OESDKTestContextExecutor.name)
 context_msg = "%s:%s" % (os.path.basename(tcname), 
os.path.basename(sdk_env))
 
-result.logSummary(component, context_msg)
 result.logDetails()
+result.logSummary(component, context_msg)
 
 if not result.wasSuccessful():
 fail = True
@@ -176,8 +176,8 @@ def testsdkext_main(d):
 component = "%s %s" % (pn, OESDKExtTestContextExecutor.name)
 context_msg = "%s:%s" % (os.path.basename(tcname), 
os.path.basename(sdk_env))
 
-result.logSummary(component, context_msg)
 result.logDetails()
+result.logSummary(component, context_msg)
 
 if not result.wasSuccessful():
 fail = True
diff --git a/meta/lib/oeqa/core/context.py b/meta/lib/oeqa/core/context.py
index 0dbf5c3..2d543ff 100644
--- a/meta/lib/oeqa/core/context.py
+++ b/meta/lib/oeqa/core/context.py
@@ -158,8 +158,8 @@ class OETestContextExecutor(object):
 else:
 self._pre_run()
 rc = self.tc.runTests(**self.tc_kwargs['run'])
-rc.logSummary(self.name)
 rc.logDetails()
+rc.logSummary(self.name)
 
 output_link = os.path.join(os.path.dirname(args.output_log),
 "%s-results.log" % self.name)
diff --git a/meta/lib/oeqa/selftest/context.py 
b/meta/lib/oeqa/selftest/context.py
index ca73070..8c8439b 100644
--- a/meta/lib/oeqa/selftest/context.py
+++ b/meta/lib/oeqa/selftest/context.py
@@ -179,8 +179,8 @@ class OESelftestTestContextExecutor(OETestContextExecutor):
 else:
 self._pre_run()
 rc = self.tc.runTests(**self.tc_kwargs['run'])
-rc.logSummary(self.name)
 rc.logDetails()
+rc.logSummary(self.name)
 
 return rc
 
-- 
2.1.4

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

Re: [OE-core] [PATCH] tcf-agent: Fix daemon termination

[Jan Kiszka]

On 2017-06-07 18:33, Martin Kelly wrote:
> On 06/07/2017 09:08 AM, Burton, Ross wrote:
>>
>> On 6 June 2017 at 18:28, Martin Kelly > > wrote:
>>
>> I sent a separate patch for fixing the systemd issue, so I think we
>> can merge the two patches separately (they're both needed):
>>
>> https://patchwork.openembedded.org/patch/140355/
>> 
>>
>> Neither of our patches have been merged yet.
>>
>>
>> Sorry, somehow slipped through the net.
>>
>> This patch doesn't apply as it's been corrupted by the mailer.  Please
>> use git-send-email instead of copy/pasting (I've managed to apply it
>> manually as it's a simple patch this time).
>>
>> Ross
>>
> 
> Which patch are you referring to? I used git send-email for the systemd
> patch, and it applies just fine for me on OE-core master (using patch -p1).

Wasn't you, was mine. :)

Jan

-- 
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] tcf-agent: Fix daemon termination

[Jan Kiszka]

On 2017-06-07 18:08, Burton, Ross wrote:
> 
> On 6 June 2017 at 18:28, Martin Kelly  > wrote:
> 
> I sent a separate patch for fixing the systemd issue, so I think we
> can merge the two patches separately (they're both needed):
> 
> https://patchwork.openembedded.org/patch/140355/
> 
> 
> Neither of our patches have been merged yet.
> 
> 
> Sorry, somehow slipped through the net.
> 
> This patch doesn't apply as it's been corrupted by the mailer.  Please
> use git-send-email instead of copy/pasting (I've managed to apply it
> manually as it's a simple patch this time).

GnuPG signatures cause troubles... I added to my blacklist.

Sorry,
Jan

-- 
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH v2 4/4] cve-check-tool: fix crash on exceptions

[Marko, Peter]

> the commit shortlog does not match what the patch is doing, unless the new 
> replaced function is the one avoiding exceptions..

The fixed issue is tracked under 
https://github.com/ikeydoherty/cve-check-tool/issues/60
It says "crash on bad pointer free".
It fixes crash when freeing invalid pointer, which happened on sqlite 
exceptions.

If necessary, I can update the commit message with longer explanation.

On Wed, 2017-06-07 at 08:04 +0200, Peter Marko wrote:
> This fixes cve-check-tool crashes on exceptions.
> 
> Signed-off-by: Peter Marko 
> ---
>  .../cve-check-tool/cve-check-tool_5.6.4.bb |  1 +
>  ...01-Fix-freeing-memory-allocated-by-sqlite.patch | 50 
> ++
>  2 files changed, 51 insertions(+)
>  create mode 100644 
> meta/recipes-devtools/cve-check-tool/files/0001-Fix-freeing-memory-all
> ocated-by-sqlite.patch
> 
> diff --git 
> a/meta/recipes-devtools/cve-check-tool/cve-check-tool_5.6.4.bb 
> b/meta/recipes-devtools/cve-check-tool/cve-check-tool_5.6.4.bb
> index 1f906ee..4829b11 100644
> --- a/meta/recipes-devtools/cve-check-tool/cve-check-tool_5.6.4.bb
> +++ b/meta/recipes-devtools/cve-check-tool/cve-check-tool_5.6.4.bb
> @@ -11,6 +11,7 @@ SRC_URI = 
> "https://github.com/ikeydoherty/${BPN}/releases/download/v${PV}/${BP}.
> 
> file://0001-print-progress-in-percent-when-downloading-CVE-db.patch \
> 
> file://0001-curl-allow-overriding-default-CA-certificate-file.patch \
> 
> file://0001-update-Compare-computed-vs-expected-sha256-digit-str.patch 
> \
> +   file://0001-Fix-freeing-memory-allocated-by-sqlite.patch \
>"
>  
>  SRC_URI[md5sum] = "c5f4247140fc9be3bf41491d31a34155"
> diff --git 
> a/meta/recipes-devtools/cve-check-tool/files/0001-Fix-freeing-memory-a
> llocated-by-sqlite.patch 
> b/meta/recipes-devtools/cve-check-tool/files/0001-Fix-freeing-memory-a
> llocated-by-sqlite.patch
> new file mode 100644
> index 000..4a82cf2
> --- /dev/null
> +++ b/meta/recipes-devtools/cve-check-tool/files/0001-Fix-freeing-memo
> +++ ry-allocated-by-sqlite.patch
> @@ -0,0 +1,50 @@
> +From a3353429652f83bb8b0316500faa88fa242d Mon Sep 17 00:00:00 
> +2001
> +From: Peter Marko 
> +Date: Thu, 13 Apr 2017 23:09:52 +0200
> +Subject: [PATCH] Fix freeing memory allocated by sqlite
> +
> +Upstream-Status: Backport
> +Signed-off-by: Peter Marko 
> +---
> + src/core.c | 8 
> + 1 file changed, 4 insertions(+), 4 deletions(-)
> +
> +diff --git a/src/core.c b/src/core.c
> +index 6263031..6788f16 100644
> +--- a/src/core.c
>  b/src/core.c
> +@@ -82,7 +82,7 @@ static bool ensure_table(CveDB *self)
> + rc = sqlite3_exec(self->db, query, NULL, NULL, );
> + if (rc != SQLITE_OK) {
> + fprintf(stderr, "ensure_table(): %s\n", err);
> +-free(err);
> ++sqlite3_free(err);
> + return false;
> + }
> + 
> +@@ -91,7 +91,7 @@ static bool ensure_table(CveDB *self)
> + rc = sqlite3_exec(self->db, query, NULL, NULL, );
> + if (rc != SQLITE_OK) {
> + fprintf(stderr, "ensure_table(): %s\n", err);
> +-free(err);
> ++sqlite3_free(err);
> + return false;
> + }
> + 
> +@@ -99,11 +99,11 @@ static bool ensure_table(CveDB *self)
> + rc = sqlite3_exec(self->db, query, NULL, NULL, );
> + if (rc != SQLITE_OK) {
> + fprintf(stderr, "ensure_table(): %s\n", err);
> +-free(err);
> ++sqlite3_free(err);
> + return false;
> + }
> + if (err) {
> +-free(err);
> ++sqlite3_free(err);
> + }
> + 
> + return true;
> +--
> +2.1.4
> +
> --
> 2.1.4
> 


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

Re: [OE-core] [oe-core][PATCH 1/1] ghostscript: move to version 9.21

[Burton, Ross]

On 6 June 2017 at 20:00, Slater, Joseph W (Wind River) <
joe.sla...@windriver.com> wrote:

> A couple of patches have been submitted moving ghostscript from 9.20 to
> 9.21.  Should I submit a new one fixing the CUPSCONFIG issue, or is the one
> from Fan Xin being considered instead?
>
>
The patches are functionally the same from what I can tell (although I
haven't tested that), so the cups problem is still a thing.

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

Re: [OE-core] [oe-core] DISK_SIGNATURE no longer functional

[Davis, Michael]

I tried using  ROOT_VM = "root=PARTUUID=${DISK_SIGNATURE}-02"
The resulting PARTUUID in syslinux append line still doesn’t match the one on 
the actual disk.


From: Jonathan Liu [mailto:net...@gmail.com]
Sent: Tuesday, June 06, 2017 5:01 PM
To: Davis, Michael
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [oe-core] DISK_SIGNATURE no longer functional

Hi Michael,

See https://patchwork.openembedded.org/patch/128565/. SYSLINUX_ROOT was renamed 
to ROOT_VM in Krogoth.

Regards,
Jonathan

On Tue., 6 Jun. 2017 at 11:29 pm, Davis, Michael 
> wrote:
Pyro.

Guessing something with all the new wic additions killed it.


-Original Message-
From: Jonathan Liu [mailto:net...@gmail.com]
Sent: Monday, June 05, 2017 7:17 PM
To: Davis, Michael
Cc: 
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [oe-core] DISK_SIGNATURE no longer functional

Hi Michael,

On 21 May 2017 at 03:16, Davis, Michael 
> wrote:
> I am trying to create a generic MSDOS PC_BIOS hdddirect image with a root
> partition set by the DISK_SIGNATURE.
>
> SYSLINUX_ROOT = "root=PARTUUID=${DISK_SIGNATURE}-02"
>
>
>
> However the signature generated in syslinux.cfg and the one on the disk
> don’t match.
>
> I tried defining my own signature and the one in syslinux changes, but the
> one on the disk doesn’t match.
>
>
>
> root=PARTUUID=22aaf83b-02
>
>
>
> NAME   PARTUUID
>
> sdd
>
> ├─sdd2 341e84a7-02
>
> ├─sdd3 341e84a7-03
>
> └─sdd1 341e84a7-01

Which release did DISK_SIGNATURE stop working?

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

Re: [OE-core] [PATCH 1/2] bitbake.conf: DISTRO_FEATURES as overrides

[Peter Kjellerstedt]

> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
> Patrick Ohly
> Sent: den 7 juni 2017 17:32
> To: openembedded-core@lists.openembedded.org
> Subject: [OE-core] [PATCH 1/2] bitbake.conf: DISTRO_FEATURES as
> overrides
> 
> As discussed in "[Openembedded-architecture] Yocto Compatible 2.0 +
> signature changes", changes in .bbappend must depend on some explicit
> configuration change, typically selecting a distro feature.
> 
> For _append and _remove, adding an override that is set only when the
> corresponding entry is in DISTRO_FEATURES achieves that:
> 
>   DISTRO_FEATURES = " ... my-distro-feature ... "
> 
>   do_install_append_my-distro-feature () {
>...
>   }
> 
> Signed-off-by: Patrick Ohly 
> ---
>  meta/conf/bitbake.conf | 17 -
>  1 file changed, 16 insertions(+), 1 deletion(-)
> 
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index 3ad905c..ca6501e 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -713,7 +713,7 @@ DISTRO_NAME ??= "OpenEmbedded"
>  #
>  # This works for  functions as well, they are really just environment
> variables.
>  # Default OVERRIDES to make compilation fail fast in case of build
> system misconfiguration.
> -OVERRIDES = "${TARGET_OS}:${TRANSLATED_TARGET_ARCH}:build-
> ${BUILD_OS}:pn-
> ${PN}:${MACHINEOVERRIDES}:${DISTROOVERRIDES}:${CLASSOVERRIDE}:forcevari
> able"
> +OVERRIDES = "${TARGET_OS}:${TRANSLATED_TARGET_ARCH}:build-
> ${BUILD_OS}:pn-
> ${PN}:${MACHINEOVERRIDES}:${DISTROOVERRIDES}${DISTROFEATURESOVERRIDES}:
> ${CLASSOVERRIDE}:forcevariable"
>  OVERRIDES[vardepsexclude] = "MACHINEOVERRIDES"
>  CLASSOVERRIDE ?= "class-target"
>  DISTROOVERRIDES ?= "${@d.getVar('DISTRO') or ''}"
> @@ -722,6 +722,21 @@ MACHINEOVERRIDES[vardepsexclude] = "MACHINE"
> 
>  FILESOVERRIDES =
> "${TRANSLATED_TARGET_ARCH}:${MACHINEOVERRIDES}:${DISTROOVERRIDES}"
> 
> +# Turns certain DISTRO_FEATURES into overrides of the same name
> +# or (optionally) some other name. Ensures that these special
> +# distro features remain set also for native and nativesdk
> +# recipes, so that these overrides can also be used there.
> +#
> +# Beware that this part of OVERRIDES changes during parsing, so usage
> +# of these overrides should be limited to .bb and .bbappend files,
> +# because then DISTRO_FEATURES is final.
> +DISTRO_FEATURES_OVERRIDES ??= ""
> +DISTRO_FEATURES_OVERRIDES[doc] = "A space-separated list of 
> entries. \
> +Each entry is added to OVERRIDES with the  name if 
> is in DISTRO_FEATURES."
> +DISTRO_FEATURES_FILTER_NATIVE_append = " ${DISTRO_FEATURES_OVERRIDES}"
> +DISTRO_FEATURES_FILTER_NATIVESDK_append = "
> ${DISTRO_FEATURES_OVERRIDES}"
> +DISTROFEATURESOVERRIDES = "${@ ''.join([':' + x for x in
> (set(d.getVar('DISTRO_FEATURES_OVERRIDES').split()) &
> set((d.getVar('DISTRO_FEATURES') or '').split()))]) }"
> +
>  ##
>  # Include the rest of the config files.
>  ##
> --
> git-series 0.9.1

Rather than requiring that the wanted DISTRO_FEATURES that should be 
available as overrides are defined in DISTRO_FEATURES_OVERRIDES (which 
should not be confused with the similarly named DISTROFEATURESOVERRIDES 
variable that you also add...), why not add them all but with a prefix. 
I.e., similar to how package names are available as overrides prefixed 
with "pn-", how about all distro features are made available as 
overrides with a "df-" prefix?

//Peter

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

Re: [OE-core] [PATCH] tcf-agent: Fix daemon termination

[Burton, Ross]

On 6 June 2017 at 18:28, Martin Kelly  wrote:

> I sent a separate patch for fixing the systemd issue, so I think we can
> merge the two patches separately (they're both needed):
>
> https://patchwork.openembedded.org/patch/140355/
>
> Neither of our patches have been merged yet.
>

Sorry, somehow slipped through the net.

This patch doesn't apply as it's been corrupted by the mailer.  Please use
git-send-email instead of copy/pasting (I've managed to apply it manually
as it's a simple patch this time).

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

[OE-core] ✗ patchtest: failure for automake: Backport perl 5.22 fix (rev2)

[Patchwork]

== Series Details ==

Series: automake: Backport perl 5.22 fix (rev2)
Revision: 2
URL   : https://patchwork.openembedded.org/series/6623/
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 A patch file has been added, but does not have a 
Signed-off-by tag [test_signed_off_by_presence] 
  Suggested fixSign off the added patch file 
(meta/recipes-devtools/automake/automake/0001-automake-port-to-Perl-5.22-and-later.patch)



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] -> ...).

---
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

Re: [OE-core] [PATCH v2 4/4] cve-check-tool: fix crash on exceptions

[Leonardo Sandoval]

the commit shortlog does not match what the patch is doing, unless the
new replaced function is the one avoiding exceptions..




On Wed, 2017-06-07 at 08:04 +0200, Peter Marko wrote:
> This fixes cve-check-tool crashes on exceptions.
> 
> Signed-off-by: Peter Marko 
> ---
>  .../cve-check-tool/cve-check-tool_5.6.4.bb |  1 +
>  ...01-Fix-freeing-memory-allocated-by-sqlite.patch | 50 
> ++
>  2 files changed, 51 insertions(+)
>  create mode 100644 
> meta/recipes-devtools/cve-check-tool/files/0001-Fix-freeing-memory-allocated-by-sqlite.patch
> 
> diff --git a/meta/recipes-devtools/cve-check-tool/cve-check-tool_5.6.4.bb 
> b/meta/recipes-devtools/cve-check-tool/cve-check-tool_5.6.4.bb
> index 1f906ee..4829b11 100644
> --- a/meta/recipes-devtools/cve-check-tool/cve-check-tool_5.6.4.bb
> +++ b/meta/recipes-devtools/cve-check-tool/cve-check-tool_5.6.4.bb
> @@ -11,6 +11,7 @@ SRC_URI = 
> "https://github.com/ikeydoherty/${BPN}/releases/download/v${PV}/${BP}.
> 
> file://0001-print-progress-in-percent-when-downloading-CVE-db.patch \
> 
> file://0001-curl-allow-overriding-default-CA-certificate-file.patch \
> 
> file://0001-update-Compare-computed-vs-expected-sha256-digit-str.patch \
> +   file://0001-Fix-freeing-memory-allocated-by-sqlite.patch \
>"
>  
>  SRC_URI[md5sum] = "c5f4247140fc9be3bf41491d31a34155"
> diff --git 
> a/meta/recipes-devtools/cve-check-tool/files/0001-Fix-freeing-memory-allocated-by-sqlite.patch
>  
> b/meta/recipes-devtools/cve-check-tool/files/0001-Fix-freeing-memory-allocated-by-sqlite.patch
> new file mode 100644
> index 000..4a82cf2
> --- /dev/null
> +++ 
> b/meta/recipes-devtools/cve-check-tool/files/0001-Fix-freeing-memory-allocated-by-sqlite.patch
> @@ -0,0 +1,50 @@
> +From a3353429652f83bb8b0316500faa88fa242d Mon Sep 17 00:00:00 2001
> +From: Peter Marko 
> +Date: Thu, 13 Apr 2017 23:09:52 +0200
> +Subject: [PATCH] Fix freeing memory allocated by sqlite
> +
> +Upstream-Status: Backport
> +Signed-off-by: Peter Marko 
> +---
> + src/core.c | 8 
> + 1 file changed, 4 insertions(+), 4 deletions(-)
> +
> +diff --git a/src/core.c b/src/core.c
> +index 6263031..6788f16 100644
> +--- a/src/core.c
>  b/src/core.c
> +@@ -82,7 +82,7 @@ static bool ensure_table(CveDB *self)
> + rc = sqlite3_exec(self->db, query, NULL, NULL, );
> + if (rc != SQLITE_OK) {
> + fprintf(stderr, "ensure_table(): %s\n", err);
> +-free(err);
> ++sqlite3_free(err);
> + return false;
> + }
> + 
> +@@ -91,7 +91,7 @@ static bool ensure_table(CveDB *self)
> + rc = sqlite3_exec(self->db, query, NULL, NULL, );
> + if (rc != SQLITE_OK) {
> + fprintf(stderr, "ensure_table(): %s\n", err);
> +-free(err);
> ++sqlite3_free(err);
> + return false;
> + }
> + 
> +@@ -99,11 +99,11 @@ static bool ensure_table(CveDB *self)
> + rc = sqlite3_exec(self->db, query, NULL, NULL, );
> + if (rc != SQLITE_OK) {
> + fprintf(stderr, "ensure_table(): %s\n", err);
> +-free(err);
> ++sqlite3_free(err);
> + return false;
> + }
> + if (err) {
> +-free(err);
> ++sqlite3_free(err);
> + }
> + 
> + return true;
> +-- 
> +2.1.4
> +
> -- 
> 2.1.4
> 


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

Re: [OE-core] [PATCH 0/2] Yocto Compatible 2.0 support code

[Joshua Watt]

On Wed, 2017-06-07 at 17:31 +0200, Patrick Ohly wrote:
> As discussed in the "[Openembedded-architecture] Yocto Compatible 2.0
> + signature changes" mail thread, changes in a .bbappend cannot be
> done unconditionally. Making _append and _remove depend on overrides
> which get set based on DISTRO_FEATURES is one way of achieving this.
> 
> The oe.utils.optional_includes() helper function has not been
> discussed before. It's an attempt to address concerns by developers
> that having to write code for (potentially complex) condition
> checking
> is error prone and hard to read.

I promise I'm not trying to start a flame war here, and perhaps there
is history behind this that I'm not aware of but...

Why doesn't bitbake support some sort of "if" statement? It seems like
most of what we are trying to do could be accomplished with much less
fuss if one could simply do this in the bb file:

 if bb.utils.contains('DISTRO_FEATURES', 'my-feature', d):
include foo.inc

One could even eliminate the separate inc file and simply put its
contents under the conditional (as much fun as it seems to have to open
a new file just to see what a recipe is doing with a distro feature...)

It would also appear that this could make a lot of other things simpler
as well (and may even negate the need to backfill DISTRO_FEATURES into
overrides?)


> 
> It depends on the bitbake enhancement that allows including multiple
> files at once.
> 
> Patrick Ohly (2):
>   bitbake.conf: DISTRO_FEATURES as overrides
>   utils.py: helper function for optional include files
> 
>  meta/conf/bitbake.conf | 17 -
>  meta/lib/oe/utils.py   | 29 +
>  2 files changed, 45 insertions(+), 1 deletion(-)
> 
> base-commit: 49c255494c1d0704a1c8c428281c81541b05dc3e
> -- 
> git-series 0.9.1

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

[OE-core] [morty][PATCH] automake: Backport perl 5.22 fix

[Cody P Schafer]

From: Marek Vasut 

Backport 13f00eb4493c "automake: port to Perl 5.22 and later"
from automake upstream to fix build with perl 5.22 .

(From OE-Core rev: 7fa044e799db651d45e4732e2527acfc2bc7cd47)

Signed-off-by: Marek Vasut 
Cc: Ross Burton 
Cc: Richard Purdie 
Signed-off-by: Ross Burton 
Signed-off-by: Cody P Schafer 
---
 ...0001-automake-port-to-Perl-5.22-and-later.patch | 32 ++
 meta/recipes-devtools/automake/automake_1.15.bb|  4 ++-
 2 files changed, 35 insertions(+), 1 deletion(-)
 create mode 100644 
meta/recipes-devtools/automake/automake/0001-automake-port-to-Perl-5.22-and-later.patch

diff --git 
a/meta/recipes-devtools/automake/automake/0001-automake-port-to-Perl-5.22-and-later.patch
 
b/meta/recipes-devtools/automake/automake/0001-automake-port-to-Perl-5.22-and-later.patch
new file mode 100644
index 00..0e6895fb4b
--- /dev/null
+++ 
b/meta/recipes-devtools/automake/automake/0001-automake-port-to-Perl-5.22-and-later.patch
@@ -0,0 +1,32 @@
+From 13f00eb4493c217269b76614759e452d8302955e Mon Sep 17 00:00:00 2001
+From: Paul Eggert 
+Date: Thu, 31 Mar 2016 16:35:29 -0700
+Subject: [PATCH] automake: port to Perl 5.22 and later
+
+Without this change, Perl 5.22 complains "Unescaped left brace in
+regex is deprecated" and this is planned to become a hard error in
+Perl 5.26.  See:
+http://search.cpan.org/dist/perl-5.22.0/pod/perldelta.pod#A_literal_%22{%22_should_now_be_escaped_in_a_pattern
+* bin/automake.in (substitute_ac_subst_variables): Escape left brace.
+
+Upstream-Status: Backport [13f00eb4493c217269b76614759e452d8302955e]
+---
+ bin/automake.in | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/bin/automake.in b/bin/automake.in
+index a3a0aa318..2c8f31e14 100644
+--- a/bin/automake.in
 b/bin/automake.in
+@@ -3878,7 +3878,7 @@ sub substitute_ac_subst_variables_worker
+ sub substitute_ac_subst_variables
+ {
+   my ($text) = @_;
+-  $text =~ s/\${([^ \t=:+{}]+)}/substitute_ac_subst_variables_worker ($1)/ge;
++  $text =~ s/\$[{]([^ \t=:+{}]+)}/substitute_ac_subst_variables_worker 
($1)/ge;
+   return $text;
+ }
+ 
+-- 
+2.11.0
+
diff --git a/meta/recipes-devtools/automake/automake_1.15.bb 
b/meta/recipes-devtools/automake/automake_1.15.bb
index a3c72fd334..61ae3ba3e3 100644
--- a/meta/recipes-devtools/automake/automake_1.15.bb
+++ b/meta/recipes-devtools/automake/automake_1.15.bb
@@ -21,7 +21,9 @@ RDEPENDS_${PN}_class-native = "autoconf-native 
hostperl-runtime-native"
 SRC_URI += " file://python-libdir.patch \
 file://buildtest.patch \
 file://performance.patch \
-file://new_rt_path_for_test-driver.patch"
+file://new_rt_path_for_test-driver.patch \
+file://0001-automake-port-to-Perl-5.22-and-later.patch \
+"
 
 SRC_URI[md5sum] = "716946a105ca228ab545fc37a70df3a3"
 SRC_URI[sha256sum] = 
"7946e945a96e28152ba5a6beb0625ca715c6e32ac55f2e353ef54def0c8ed924"
-- 
2.13.0

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

[OE-core] [PATCH 2/2] utils.py: helper function for optional include files

[Patrick Ohly]

By using oe.utils.optional_includes(), developers can simplify the
code which selects which additional include files need to be included
in a .bbappend.

In the simple case (one distro feature and one include file) the code
is not shorter, but the intent is clearer than corresponding code
using bb.utils.contains():

   require ${@ oe.utils.optional_includes(d, 'foo-feature:bar.inc') }

More complex cases are also supported, in particular include files
that are required for one of several distro features or multiple
different include files.

To keep the common use case simple, DISTRO_FEATURES are checked by
default. Checking IMAGE_FEATURES might also be useful.

The DISTRO_FEATURES default and the intended usage make this more
suitable for OE-core than bitbake.

Signed-off-by: Patrick Ohly 
---
 meta/lib/oe/utils.py | 29 +
 1 file changed, 29 insertions(+)

diff --git a/meta/lib/oe/utils.py b/meta/lib/oe/utils.py
index 330a5ff..a6c6199 100644
--- a/meta/lib/oe/utils.py
+++ b/meta/lib/oe/utils.py
@@ -126,6 +126,35 @@ def features_backfill(var,d):
 if addfeatures:
 d.appendVar(var, " " + " ".join(addfeatures))
 
+def optional_includes(d, mapping, key_var="DISTRO_FEATURES"):
+"""
+This can be used to generate a list of files to include depending on
+the distro features that are selected. key_var contains the features
+that are set, mapping_var a space-separated set of :
+entries. Features and files are separated by comma. Each file on the
+right-hand side is included in the result once if any of the features one
+the left-hand side is set.
+
+Example:
+   require ${@ oe.utils.optional_includes(d, "foo,bar:foo-or-bar.inc 
xyz:x.inc,y.inc,z.inc")}
+
+For DISTRO_FEATURES = "foo xyz" that will include four .inc files in the
+order in which they are listed.
+"""
+key = set((d.getVar(key_var) or "").split())
+mapping = mapping.split()
+includes = []
+for entry in mapping:
+parts = entry.split(":", 1)
+if len(parts) != 2:
+bb.fatal("%s must contain entries of the form 
:, not %s" % (mapping_var, entry))
+features, files = parts
+for feature in features.split(","):
+if feature in key:
+for file in files.split(","):
+if file not in includes:
+includes.append(file)
+return " ".join(includes)
 
 def packages_filter_out_system(d):
 """
-- 
git-series 0.9.1
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 1/2] bitbake.conf: DISTRO_FEATURES as overrides

[Patrick Ohly]

As discussed in "[Openembedded-architecture] Yocto Compatible 2.0 +
signature changes", changes in .bbappend must depend on some explicit
configuration change, typically selecting a distro feature.

For _append and _remove, adding an override that is set only when the
corresponding entry is in DISTRO_FEATURES achieves that:

  DISTRO_FEATURES = " ... my-distro-feature ... "

  do_install_append_my-distro-feature () {
   ...
  }

Signed-off-by: Patrick Ohly 
---
 meta/conf/bitbake.conf | 17 -
 1 file changed, 16 insertions(+), 1 deletion(-)

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 3ad905c..ca6501e 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -713,7 +713,7 @@ DISTRO_NAME ??= "OpenEmbedded"
 #
 # This works for  functions as well, they are really just environment 
variables.
 # Default OVERRIDES to make compilation fail fast in case of build system 
misconfiguration.
-OVERRIDES = 
"${TARGET_OS}:${TRANSLATED_TARGET_ARCH}:build-${BUILD_OS}:pn-${PN}:${MACHINEOVERRIDES}:${DISTROOVERRIDES}:${CLASSOVERRIDE}:forcevariable"
+OVERRIDES = 
"${TARGET_OS}:${TRANSLATED_TARGET_ARCH}:build-${BUILD_OS}:pn-${PN}:${MACHINEOVERRIDES}:${DISTROOVERRIDES}${DISTROFEATURESOVERRIDES}:${CLASSOVERRIDE}:forcevariable"
 OVERRIDES[vardepsexclude] = "MACHINEOVERRIDES"
 CLASSOVERRIDE ?= "class-target"
 DISTROOVERRIDES ?= "${@d.getVar('DISTRO') or ''}"
@@ -722,6 +722,21 @@ MACHINEOVERRIDES[vardepsexclude] = "MACHINE"
 
 FILESOVERRIDES = 
"${TRANSLATED_TARGET_ARCH}:${MACHINEOVERRIDES}:${DISTROOVERRIDES}"
 
+# Turns certain DISTRO_FEATURES into overrides of the same name
+# or (optionally) some other name. Ensures that these special
+# distro features remain set also for native and nativesdk
+# recipes, so that these overrides can also be used there.
+#
+# Beware that this part of OVERRIDES changes during parsing, so usage
+# of these overrides should be limited to .bb and .bbappend files,
+# because then DISTRO_FEATURES is final.
+DISTRO_FEATURES_OVERRIDES ??= ""
+DISTRO_FEATURES_OVERRIDES[doc] = "A space-separated list of  entries. 
\
+Each entry is added to OVERRIDES with the  name if  is in 
DISTRO_FEATURES."
+DISTRO_FEATURES_FILTER_NATIVE_append = " ${DISTRO_FEATURES_OVERRIDES}"
+DISTRO_FEATURES_FILTER_NATIVESDK_append = " ${DISTRO_FEATURES_OVERRIDES}"
+DISTROFEATURESOVERRIDES = "${@ ''.join([':' + x for x in 
(set(d.getVar('DISTRO_FEATURES_OVERRIDES').split()) & 
set((d.getVar('DISTRO_FEATURES') or '').split()))]) }"
+
 ##
 # Include the rest of the config files.
 ##
-- 
git-series 0.9.1
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 0/2] Yocto Compatible 2.0 support code

[Patrick Ohly]

As discussed in the "[Openembedded-architecture] Yocto Compatible 2.0
+ signature changes" mail thread, changes in a .bbappend cannot be
done unconditionally. Making _append and _remove depend on overrides
which get set based on DISTRO_FEATURES is one way of achieving this.

The oe.utils.optional_includes() helper function has not been
discussed before. It's an attempt to address concerns by developers
that having to write code for (potentially complex) condition checking
is error prone and hard to read.

It depends on the bitbake enhancement that allows including multiple
files at once.

Patrick Ohly (2):
  bitbake.conf: DISTRO_FEATURES as overrides
  utils.py: helper function for optional include files

 meta/conf/bitbake.conf | 17 -
 meta/lib/oe/utils.py   | 29 +
 2 files changed, 45 insertions(+), 1 deletion(-)

base-commit: 49c255494c1d0704a1c8c428281c81541b05dc3e
-- 
git-series 0.9.1
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 2/3 v2][pyro] piglit: add patch for lack of gbm_bo_map

[Daniel Díaz]

[Backported from master.]

[Piglit Bug #100978] -- https://bugs.freedesktop.org/show_bug.cgi?id=100978

When linking against Mali 450 r6, errors like the following
can be seen:
  ../../../../lib/libpiglitutil_gl.so.0: undefined reference to `gbm_bo_unmap'
  ../../../../lib/libpiglitutil_gl.so.0: undefined reference to `gbm_bo_map'
  collect2: error: ld returned 1 exit status
  make[2]: *** [bin/point-sprite] Error 1

This is due to gbm_bo_map() and gbm_bo_unmap() being recently
added but not yet implemented by all graphics drivers.

Instead of relying on GBM's version, actually try to link
against those symbols.

Signed-off-by: Daniel Díaz 
---
v2: Embed upstream status into patch; add patch into recipe.

 ...fine-GBM_BO_MAP-only-when-symbol-is-found.patch | 51 ++
 meta/recipes-graphics/piglit/piglit_git.bb |  1 +
 2 files changed, 52 insertions(+)
 create mode 100644 
meta/recipes-graphics/piglit/piglit/0001-CMake-define-GBM_BO_MAP-only-when-symbol-is-found.patch

diff --git 
a/meta/recipes-graphics/piglit/piglit/0001-CMake-define-GBM_BO_MAP-only-when-symbol-is-found.patch
 
b/meta/recipes-graphics/piglit/piglit/0001-CMake-define-GBM_BO_MAP-only-when-symbol-is-found.patch
new file mode 100644
index 000..8b63424
--- /dev/null
+++ 
b/meta/recipes-graphics/piglit/piglit/0001-CMake-define-GBM_BO_MAP-only-when-symbol-is-found.patch
@@ -0,0 +1,51 @@
+From 47697aee05a112422acf203982085e7b3e6c05b2 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Daniel=20D=C3=ADaz?= 
+Date: Thu, 4 May 2017 00:57:39 -0500
+Subject: [PATCH 1/4] CMake: define GBM_BO_MAP only when symbol is found
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+gbm_bo_map() and _unmap() have been added recently to Mesa,
+and this update may not have reached all implementations of
+GBM, such as the one provided by Mali r6, where said
+definitions can be found in the header file but not in the
+library itself. This leads to errors like the following when
+linking:
+  ../../../../lib/libpiglitutil_gl.so.0: undefined reference to `gbm_bo_unmap'
+  ../../../../lib/libpiglitutil_gl.so.0: undefined reference to `gbm_bo_map'
+  collect2: error: ld returned 1 exit status
+  make[2]: *** [bin/point-sprite] Error 1
+
+Instead of relying on the header file, actually try to link
+using that symbol to determine if PIGLIT_HAS_GBM_BO_MAP
+should be defined.
+
+Upstream-Status: Submitted [pig...@lists.freedesktop.org]
+
+Signed-off-by: Daniel Díaz 
+Reviewed-by: Jan Vesely 
+Reviewed-by: Dylan Baker 
+---
+ CMakeLists.txt | 5 +++--
+ 1 file changed, 3 insertions(+), 2 deletions(-)
+
+diff --git a/CMakeLists.txt b/CMakeLists.txt
+index a4ff99e..cc26fa8 100644
+--- a/CMakeLists.txt
 b/CMakeLists.txt
+@@ -141,8 +141,9 @@ IF(${CMAKE_SYSTEM_NAME} MATCHES "Linux")
+   if(GBM_FOUND)
+   set(PIGLIT_HAS_GBM True)
+   add_definitions(-DPIGLIT_HAS_GBM)
+-  if (GBM_VERSION VERSION_EQUAL "12.1" OR GBM_VERSION 
VERSION_GREATER "12.1")
+-  set(PIGLIT_HAS_GBM_BO_MAP True)
++  set(CMAKE_REQUIRED_LIBRARIES ${CMAKE_REQUIRED_LIBRARIES} 
${GBM_LIBRARIES})
++  CHECK_FUNCTION_EXISTS(gbm_bo_map PIGLIT_HAS_GBM_BO_MAP)
++  if (PIGLIT_HAS_GBM_BO_MAP)
+   add_definitions(-DPIGLIT_HAS_GBM_BO_MAP)
+   endif()
+   endif(GBM_FOUND)
+-- 
+1.9.1
+
diff --git a/meta/recipes-graphics/piglit/piglit_git.bb 
b/meta/recipes-graphics/piglit/piglit_git.bb
index eae3eed..19db86c 100644
--- a/meta/recipes-graphics/piglit/piglit_git.bb
+++ b/meta/recipes-graphics/piglit/piglit_git.bb
@@ -5,6 +5,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=b2beded7103a3d8a442a2a0391d607b0"
 SRC_URI = "git://anongit.freedesktop.org/piglit \
file://0001-cmake-install-bash-completions-in-the-right-place.patch 
\
file://0001-tests-Use-FE_UPWARD-only-if-its-defined-in-fenv.h.patch 
\
+   file://0001-CMake-define-GBM_BO_MAP-only-when-symbol-is-found.patch 
\
"
 
 # From 2017-02-06
-- 
1.9.1

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

[OE-core] [PATCH 3/3 v2][pyro] piglit: add patches for unbuildable surfaceless Mesa test

[Daniel Díaz]

[Backported from master.]

Some EGL implementations do not actually ship all Khronos-
extensions. As it turns out, the Mali 450 driver does not
include any of the following symbols, used by the
egl_mesa_platform_surfaceless.c spec test:
* eglGetPlatformDisplay
* eglCreatePlatformPixmapSurface
* eglCreatePlatformWindowSurface

The Right Thing To Do was to obtain the implementation of
these functions (via eglGetProcAddress), as is provided
by their EXT counterparts. These are guaranteed to exist
since they are required by EGL_EXT_platform_base.

Signed-off-by: Daniel Díaz 
---
v2: Embed upstream status into patches; add patch into recipe.

 ...nour-Surfaceless-MESA-in-get_default_disp.patch | 54 +++
 ...atform_surfaceless-Don-t-use-eglGetPlatfo.patch | 36 ++
 ...atform_surfaceless-Use-EXT-functions-for-.patch | 78 ++
 meta/recipes-graphics/piglit/piglit_git.bb |  3 +
 4 files changed, 171 insertions(+)
 create mode 100644 
meta/recipes-graphics/piglit/piglit/0002-util-egl-Honour-Surfaceless-MESA-in-get_default_disp.patch
 create mode 100644 
meta/recipes-graphics/piglit/piglit/0003-egl_mesa_platform_surfaceless-Don-t-use-eglGetPlatfo.patch
 create mode 100644 
meta/recipes-graphics/piglit/piglit/0004-egl_mesa_platform_surfaceless-Use-EXT-functions-for-.patch

diff --git 
a/meta/recipes-graphics/piglit/piglit/0002-util-egl-Honour-Surfaceless-MESA-in-get_default_disp.patch
 
b/meta/recipes-graphics/piglit/piglit/0002-util-egl-Honour-Surfaceless-MESA-in-get_default_disp.patch
new file mode 100644
index 000..f3aa1ba
--- /dev/null
+++ 
b/meta/recipes-graphics/piglit/piglit/0002-util-egl-Honour-Surfaceless-MESA-in-get_default_disp.patch
@@ -0,0 +1,54 @@
+From a6608f218b5023cef36b3de5ec3c5f00b0211d1c Mon Sep 17 00:00:00 2001
+From: Daniel Diaz 
+Date: Wed, 17 May 2017 18:00:15 -0500
+Subject: [PATCH 2/4] util/egl: Honour Surfaceless MESA in get_default_display
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+The EGL_MESA_platform_surfaceless extension was introduced not too long
+ago. Add support for it our helper.
+
+Upstream-Status: Accepted, since git 7b74602.
+
+Signed-off-by: Daniel Díaz 
+Reviewed-by: Emil Velikov 
+---
+ tests/util/piglit-util-egl.c | 7 +++
+ 1 file changed, 7 insertions(+)
+
+diff --git a/tests/util/piglit-util-egl.c b/tests/util/piglit-util-egl.c
+index 106c735..389fe12 100644
+--- a/tests/util/piglit-util-egl.c
 b/tests/util/piglit-util-egl.c
+@@ -85,6 +85,7 @@ piglit_egl_get_default_display(EGLenum platform)
+   static bool has_x11 = false;
+   static bool has_wayland = false;
+   static bool has_gbm = false;
++  static bool has_surfaceless_mesa = false;
+ 
+   static EGLDisplay (*peglGetPlatformDisplayEXT)(EGLenum platform, void 
*native_display, const EGLint *attrib_list);
+ 
+@@ -99,6 +100,7 @@ piglit_egl_get_default_display(EGLenum platform)
+   has_x11 = piglit_is_egl_extension_supported(EGL_NO_DISPLAY, 
"EGL_EXT_platform_x11");
+   has_wayland = piglit_is_egl_extension_supported(EGL_NO_DISPLAY, 
"EGL_EXT_platform_wayland");
+   has_gbm = piglit_is_egl_extension_supported(EGL_NO_DISPLAY, 
"EGL_EXT_platform_gbm");
++  has_surfaceless_mesa = 
piglit_is_egl_extension_supported(EGL_NO_DISPLAY, 
"EGL_MESA_platform_surfaceless");
+ 
+   peglGetPlatformDisplayEXT = (void*) 
eglGetProcAddress("eglGetPlatformDisplayEXT");
+   }
+@@ -123,6 +125,11 @@ piglit_egl_get_default_display(EGLenum platform)
+   return EGL_NO_DISPLAY;
+   }
+   break;
++  case EGL_PLATFORM_SURFACELESS_MESA:
++  if (!has_surfaceless_mesa) {
++  return EGL_NO_DISPLAY;
++  }
++  break;
+   default:
+   fprintf(stderr, "%s: unrecognized platform %#x\n", __func__, 
platform);
+   return EGL_NO_DISPLAY;
+-- 
+1.9.1
+
diff --git 
a/meta/recipes-graphics/piglit/piglit/0003-egl_mesa_platform_surfaceless-Don-t-use-eglGetPlatfo.patch
 
b/meta/recipes-graphics/piglit/piglit/0003-egl_mesa_platform_surfaceless-Don-t-use-eglGetPlatfo.patch
new file mode 100644
index 000..0f24dc1
--- /dev/null
+++ 
b/meta/recipes-graphics/piglit/piglit/0003-egl_mesa_platform_surfaceless-Don-t-use-eglGetPlatfo.patch
@@ -0,0 +1,36 @@
+From c0dc430b8f5deeacdb11cd188195e16f512af233 Mon Sep 17 00:00:00 2001
+From: Daniel Diaz 
+Date: Wed, 17 May 2017 18:00:16 -0500
+Subject: [PATCH 3/4] egl_mesa_platform_surfaceless: Don't use
+ eglGetPlatformDisplay directly
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+The entry point is not guaranteed to exist, so use the
+piglit_egl_get_default_display() helper which does the correct thing.
+
+Upstream-Status: Accepted, since 

[OE-core] [PATCH 1/3 v2][pyro] piglit: depend on virtual/egl

[Daniel Díaz]

[Backported from master.]

While building for Hikey using Mali 450 driver (r6p0), an
error like the following appears while linking:

  [  1%] Linking C shared library ../../../../lib/libpiglitutil.so
  [...]
  [...]/aarch64-linaro-linux/gcc/aarch64-linaro-linux/6.3.1/ld: cannot find 
-lEGL
  collect2: error: ld returned 1 exit status
  make[2]: *** [lib/libpiglitutil.so.0] Error 1

Mesa generally provides virtual/egl (along with virtual/libgl,
which satisfies Piglit's current DEPENDS) but that is not the
implementation to use with Mali.

Signed-off-by: Daniel Díaz 
---
v2: No change, just resending.
 
 meta/recipes-graphics/piglit/piglit_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-graphics/piglit/piglit_git.bb 
b/meta/recipes-graphics/piglit/piglit_git.bb
index d6bfb14..eae3eed 100644
--- a/meta/recipes-graphics/piglit/piglit_git.bb
+++ b/meta/recipes-graphics/piglit/piglit_git.bb
@@ -14,7 +14,7 @@ PV = "1.0+gitr${SRCPV}"
 
 S = "${WORKDIR}/git"
 
-DEPENDS = "libpng virtual/libx11 libxkbcommon libxrender waffle virtual/libgl 
libglu python3-mako-native python3-numpy-native python3-six-native"
+DEPENDS = "libpng virtual/libx11 libxkbcommon libxrender waffle virtual/libgl 
libglu python3-mako-native python3-numpy-native python3-six-native virtual/egl"
 
 inherit cmake python3native distro_features_check bash-completion
 # depends on virtual/libx11
-- 
1.9.1

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

[OE-core] [PATCH] buildhistory: skip tests if GitPython module is missing

[leonardo . sandoval . gonzalez]

From: Leonardo Sandoval 

Catching a possible exception when importing the git module,
allows us to skip test if the latter is missing on the host.
Also, import oe.buildhistory_analysis inside fuctions
because this module also needs git to work correctly.

[YOCTO #11620]

Signed-off-by: Leonardo Sandoval 
---
 meta/lib/oeqa/selftest/cases/oelib/buildhistory.py | 13 ++---
 1 file changed, 10 insertions(+), 3 deletions(-)

diff --git a/meta/lib/oeqa/selftest/cases/oelib/buildhistory.py 
b/meta/lib/oeqa/selftest/cases/oelib/buildhistory.py
index 4e877517c1..f9bec53d4a 100644
--- a/meta/lib/oeqa/selftest/cases/oelib/buildhistory.py
+++ b/meta/lib/oeqa/selftest/cases/oelib/buildhistory.py
@@ -1,9 +1,7 @@
 import os
 from oeqa.selftest.case import OESelftestTestCase
 import tempfile
-from git import Repo
 from oeqa.utils.commands import get_bb_var
-from oe.buildhistory_analysis import blob_to_dict, compare_dict_blobs
 
 class TestBlobParsing(OESelftestTestCase):
 
@@ -12,7 +10,12 @@ class TestBlobParsing(OESelftestTestCase):
 self.repo_path = tempfile.mkdtemp(prefix='selftest-buildhistory',
 dir=get_bb_var('TOPDIR'))
 
-self.repo = Repo.init(self.repo_path)
+try:
+from git import Repo
+self.repo = Repo.init(self.repo_path)
+except ImportError:
+self.skipTest('Python module GitPython is not present')
+
 self.test_file = "test"
 self.var_map = {}
 
@@ -40,6 +43,7 @@ class TestBlobParsing(OESelftestTestCase):
 """
 Test convertion of git blobs to dictionary
 """
+from oe.buildhistory_analysis import blob_to_dict
 valuesmap = { "foo" : "1", "bar" : "2" }
 self.commit_vars(to_add = valuesmap)
 
@@ -51,6 +55,8 @@ class TestBlobParsing(OESelftestTestCase):
 """
 Test comparisson of dictionaries extracted from git blobs
 """
+from oe.buildhistory_analysis import compare_dict_blobs
+
 changesmap = { "foo-2" : ("2", "8"), "bar" : ("","4"), "bar-2" : 
("","5")}
 
 self.commit_vars(to_add = { "foo" : "1", "foo-2" : "2", "foo-3" : "3" 
})
@@ -69,6 +75,7 @@ class TestBlobParsing(OESelftestTestCase):
 """
 Test default values for comparisson of git blob dictionaries
 """
+from oe.buildhistory_analysis import compare_dict_blobs
 defaultmap = { x : ("default", "1")  for x in ["PKG", "PKGE", "PKGV", 
"PKGR"]}
 
 self.commit_vars(to_add = { "foo" : "1" })
-- 
2.12.0

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

[OE-core] [PATCH] libunwind: don't mess around with ARM atomic detection

[Ross Burton]

This recipe explictly sets -DAO_USE_PTHREAD_DEFS on ARM, but with libunwind 1.2
this causes the linker to fail:

  hidden symbol `__sync_synchronize' in libgcc.a(linux-atomic.o) is referenced 
by DSO

Removing these defines lets configure do the right thing and build libunwind.

Signed-off-by: Ross Burton 
---
 meta/recipes-support/libunwind/libunwind.inc | 5 -
 1 file changed, 5 deletions(-)

diff --git a/meta/recipes-support/libunwind/libunwind.inc 
b/meta/recipes-support/libunwind/libunwind.inc
index 4f64ad7..fc33786 100644
--- a/meta/recipes-support/libunwind/libunwind.inc
+++ b/meta/recipes-support/libunwind/libunwind.inc
@@ -13,11 +13,6 @@ PACKAGECONFIG[lzma] = 
"--enable-minidebuginfo,--disable-minidebuginfo,xz"
 EXTRA_OECONF_arm = "--enable-debug-frame"
 EXTRA_OECONF_aarch64 = "--enable-debug-frame"
 
-CFLAGS += "${ATOMICOPS}"
-ATOMICOPS_armv5 = "-DAO_USE_PTHREAD_DEFS=1"
-ATOMICOPS_armv4 = "-DAO_USE_PTHREAD_DEFS=1"
-ATOMICOPS ?= ""
-
 SECURITY_LDFLAGS_append_libc-musl = " -lssp_nonshared -lssp"
 
 BBCLASSEXTEND = "native"
-- 
2.8.1

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

Re: [OE-core] [PATCH v2 01/25] bitbake.conf: support for merged usr with DISTRO_FEATURE usrmerge

[Patrick Ohly]

On Wed, 2017-06-07 at 12:52 +0100, Richard Purdie wrote:
> On Wed, 2017-02-22 at 10:26 +0200, Amarnath Valluri wrote:
> > From: Joshua Lock 
> > 
> > Modify bindir, libdir and sbindir to be exec_prefix/$d, rather than
> > base_prefix/$d, when the usrmerge DISTRO_FEATURE is enabled.
> > 
> > Signed-off-by: Joshua Lock 
> > ---
> >  meta/conf/bitbake.conf | 12 
> >  1 file changed, 8 insertions(+), 4 deletions(-)
> 
> I was asked to clarify the status of this series. We've taken many of
> the changes but the core changes to bitbake.conf haven't been merged.
> 
> Ross/I discussed it and we both feel that the bitbake.conf make the
> file pretty unreadable. We'd therefore like to see this implemented as
> a .inc file which gets included when the relevant DISTRO_FEATURE is set
> (or could just be included by the appropriate distro configs). This
> .inc file would then simply override the paths. I believe this would be
> a lot more readable than the current approach which is a key concern in
> the core config.
> 
> The merge of the rest of this feature is therefore pending on the
> development of such a patch, or a discussion convincing Ross/I why we
> shouldn't take that approach for some reason.

Such a .inc file would have to be included after the "Include the rest
of the config files." section, because DISTRO_FEATURES only has its
final value (?) at that point. One also needs the patch that I
coincidentally just sent today to the bitbake list which allows
including such a file only when "usrmerge" is in DISTRO_FEATURES.

Would that be okay?

One downside is that code using the variables earlier will just see the
non-usrmerge version, with no indication in "bitbake -e" that the value
might have been different in the middle of parsing. The if check in the
proposed patch has the same effect on the actual values, but at least it
shows up in "bitbake -e". This is not a particularly strong argument
either way, I just wanted to mention it.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.



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

[OE-core] [PATCH][krogoth] oeqa/selftest/recipetool: actually fix create_github test

[Ross Burton]

The Meson revision was locked down but the license list change wasn't actually
committed...

Also specify the exact path for recipetool to write to, for clarity.

Signed-off-by: Ross Burton 
---
 meta/lib/oeqa/selftest/recipetool.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/lib/oeqa/selftest/recipetool.py 
b/meta/lib/oeqa/selftest/recipetool.py
index 312684b..0ec8381 100644
--- a/meta/lib/oeqa/selftest/recipetool.py
+++ b/meta/lib/oeqa/selftest/recipetool.py
@@ -448,10 +448,10 @@ class RecipetoolTests(RecipetoolBase):
 os.makedirs(temprecipe)
 recipefile = os.path.join(temprecipe, 'meson_git.bb')
 srcuri = 'https://github.com/mesonbuild/meson;rev=0.32.0'
-result = runCmd(['recipetool', 'create', '-o', temprecipe, srcuri])
+result = runCmd(['recipetool', 'create', '-o', recipefile, srcuri])
 self.assertTrue(os.path.isfile(recipefile))
 checkvars = {}
-checkvars['LICENSE'] = set(['Apache-2.0', 'Unknown'])
+checkvars['LICENSE'] = set(['Apache-2.0'])
 checkvars['SRC_URI'] = 
'git://github.com/mesonbuild/meson;protocol=https'
 inherits = ['setuptools']
 self._test_recipe_contents(recipefile, checkvars, inherits)
-- 
2.8.1

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

Re: [OE-core] [PATCH v2] python3: make readline, gdbm, and db support conditional.

[Burton, Ross]

On 7 June 2017 at 14:49, Ismo Puustinen  wrote:

> +RRECOMMENDS_${PN}-core = "${@bb.utils.contains('PACKAGECONFIG',
> 'readline', '${PN}-readline', '', d)}"
>

Recommends can not exists, so I wouldn't bother with this complication.

+RDEPENDS_${PN}-modules_remove += "${@bb.utils.contains('PACKAGECONFIG',
> 'readline', '', '${PN}-readline', d)}"

(etc)

Don't use _remove and += as it's confusing.

But if for example readline is disabled, why would the package be created
in the first place?

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

Re: [OE-core] Fun with npm shrinkwrap

[Davis, Michael]

If offline builds, license checking, or stable dependency versions are not 
important to you then you can use the meta-nodejs layer.  It just uses the yarn 
tool directly https://github.com/imyller/meta-nodejs.


On a hijacked side note has yarn been considered as a solution to some of our 
npm issues?
It seems to be npm with built in licnese checking and better version 
determination.
Might not cover 100% of our use cases, but then npm only seems to work 50% of 
the time without tweaking something anyways.



-Original Message-
From: openembedded-core-boun...@lists.openembedded.org 
[mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of Jan 
Kiszka
Sent: Wednesday, June 07, 2017 7:04 AM
To: Alexander Kanavin; openembedded-core@lists.openembedded.org
Cc: Paul Eggleton
Subject: Re: [OE-core] Fun with npm shrinkwrap

On 2017-06-07 13:43, Alexander Kanavin wrote:
> On 06/06/2017 06:14 PM, Jan Kiszka wrote:
> 
>> Yeah, good points. Probably this problem is also related to OE
>> reimplementing parts of the npm logic.
>>
>> But I suppose those concepts won't materialize very soon, will they? I'm
>> also looking for a short-term solution, at least some reasonable tactic
>> to generate such recipes in the meantime. Is there something in that
>> thread I should dig into?
> 
> What I am getting at is that it would be awesome if you convince your
> management that npm support in Yocto is a problem that needs a better
> solution and work on it. Yes, this means you can't work on product
> development for quite some time; this is the price for using open source
> projects without a commercial support contract :)

We are such a instance support :) - but we also need to get paid / pay
our contractors.

> 
> My apologies if this is not the answer you were seeking.
> 

I'm getting your point, even more now as I ran into a package that does
not even install at all (node-red-contrib-opcua). Can't promise anything
at this point, but I will carry this forward, in all directions.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux
-- 
___
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 v2] python3: make readline, gdbm, and db support conditional.

[Ismo Puustinen]

The three libraries' (readline, gdbm, and db) licenses belong to the
GPLv3 family. Add them to to PACKAGECONFIG so they can be switched off
if the licensing doesn't allow using them. Python build system
autodetects the dependencies but doesn't allow them to be explicitly
disabled, so just deal with the dependencies.

The defaults in PACKAGECONFIG are the same as before, so there should be
no change to current users.

Signed-off-by: Ismo Puustinen 
---
 meta/recipes-devtools/python/python3_3.5.3.bb | 23 +--
 1 file changed, 21 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-devtools/python/python3_3.5.3.bb 
b/meta/recipes-devtools/python/python3_3.5.3.bb
index d7c29f2..e9a1e6b 100644
--- a/meta/recipes-devtools/python/python3_3.5.3.bb
+++ b/meta/recipes-devtools/python/python3_3.5.3.bb
@@ -1,6 +1,6 @@
 require recipes-devtools/python/python.inc
 
-DEPENDS = "python3-native libffi bzip2 db gdbm openssl readline sqlite3 zlib 
virtual/libintl xz"
+DEPENDS = "python3-native libffi bzip2 openssl sqlite3 zlib virtual/libintl xz"
 PR = "${INC_PR}.0"
 PYTHON_MAJMIN = "3.5"
 PYTHON_BINABI= "${PYTHON_MAJMIN}m"
@@ -76,6 +76,11 @@ export CROSSPYTHONPATH = 
"${STAGING_LIBDIR_NATIVE}/python${PYTHON_MAJMIN}/lib-dy
 # No ctypes option for python 3
 PYTHONLSBOPTS = ""
 
+PACKAGECONFIG ??= "readline gdbm db"
+PACKAGECONFIG[readline] = ",,readline"
+PACKAGECONFIG[gdbm] = ",,gdbm"
+PACKAGECONFIG[db] = ",,db"
+
 do_configure_append() {
rm -f ${S}/Makefile.orig
autoreconf -Wcross --verbose --install --force --exclude=autopoint 
../Python-${PV}/Modules/_ctypes/libffi
@@ -194,7 +199,7 @@ require python-${PYTHON_MAJMIN}-manifest.inc
 
 # manual dependency additions
 RPROVIDES_${PN}-modules = "${PN}"
-RRECOMMENDS_${PN}-core = "${PN}-readline"
+RRECOMMENDS_${PN}-core = "${@bb.utils.contains('PACKAGECONFIG', 'readline', 
'${PN}-readline', '', d)}"
 RRECOMMENDS_${PN}-crypt = "openssl"
 RRECOMMENDS_${PN}-crypt_class-nativesdk = "nativesdk-openssl"
 
@@ -222,3 +227,17 @@ PACKAGES += "${PN}-man"
 FILES_${PN}-man = "${datadir}/man"
 
 BBCLASSEXTEND = "nativesdk"
+
+# If readline is not there, don't create python3-readline package. Same
+# for gdbm and db.
+PACKAGES_remove += "${@bb.utils.contains('PACKAGECONFIG', 'readline', '', 
'${PN}-readline', d)}"
+PROVIDES_remove += "${@bb.utils.contains('PACKAGECONFIG', 'readline', '', 
'${PN}-readline', d)}"
+RDEPENDS_${PN}-modules_remove += "${@bb.utils.contains('PACKAGECONFIG', 
'readline', '', '${PN}-readline', d)}"
+
+PACKAGES_remove += "${@bb.utils.contains('PACKAGECONFIG', 'gdbm', '', 
'${PN}-gdbm', d)}"
+PROVIDES_remove += "${@bb.utils.contains('PACKAGECONFIG', 'gdbm', '', 
'${PN}-gdbm', d)}"
+RDEPENDS_${PN}-modules_remove += "${@bb.utils.contains('PACKAGECONFIG', 
'gdbm', '', '${PN}-gdbm', d)}"
+
+PACKAGES_remove += "${@bb.utils.contains('PACKAGECONFIG', 'db', '', 
'${PN}-db', d)}"
+PROVIDES_remove += "${@bb.utils.contains('PACKAGECONFIG', 'db', '', 
'${PN}-db', d)}"
+RDEPENDS_${PN}-modules_remove += "${@bb.utils.contains('PACKAGECONFIG', 'db', 
'', '${PN}-db', d)}"
-- 
2.9.4

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

[OE-core] [PATCH v4] u-boot: enable dhcp for MPC8315 board

[Ed Bartosh]

Getting ip address from DHCP server is much more convenient
than setting static ip. It allows to configure u-boot in
more generic way and to avoid hardcoding static ip in
u-boot configuration.

Enabled dhcp client functionality for Yocto reference
hardware MPC8315E-RDB.

Signed-off-by: Ed Bartosh 
---
 .../u-boot/files/MPC8315ERDB-enable-DHCP.patch| 19 +++
 meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc |  4 +++-
 2 files changed, 22 insertions(+), 1 deletion(-)
 create mode 100644 meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch

diff --git a/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch 
b/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
new file mode 100644
index 000..cea52b7
--- /dev/null
+++ b/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
@@ -0,0 +1,19 @@
+Enabled dhcp client functionality for Yocto reference
+hardware MPC8315E-RDB.
+
+Upstream-Status: Pending
+
+Signed-off-by: Ed Bartosh 
+
+diff --git a/configs/MPC8315ERDB_defconfig b/configs/MPC8315ERDB_defconfig
+index 4e2b705..b02ab1f 100644
+--- a/configs/MPC8315ERDB_defconfig
 b/configs/MPC8315ERDB_defconfig
+@@ -9,6 +9,7 @@ CONFIG_HUSH_PARSER=y
+ CONFIG_CMD_I2C=y
+ CONFIG_CMD_USB=y
+ # CONFIG_CMD_SETEXPR is not set
++CONFIG_CMD_DHCP=y
+ CONFIG_CMD_MII=y
+ CONFIG_CMD_PING=y
+ CONFIG_CMD_EXT2=y
diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc 
b/meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc
index df24c85..8ee1c32 100644
--- a/meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc
+++ b/meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc
@@ -9,6 +9,8 @@ PE = "1"
 # repo during parse
 SRCREV = "a705ebc81b7f91bbd0ef7c634284208342901149"
 
-SRC_URI = "git://git.denx.de/u-boot.git"
+SRC_URI = "git://git.denx.de/u-boot.git \
+file://MPC8315ERDB-enable-DHCP.patch \
+"
 
 S = "${WORKDIR}/git"
-- 
2.1.4

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

[OE-core] [PATCH v3] u-boot: enable dhcp for MPC8315 board

[Ed Bartosh]

Getting ip address from DHCP server is much more convenient
than setting static ip. It allows to configure u-boot in
more generic way and to avoid hardcoding static ip in
u-boot configuration.

Enabled dhcp client functionality for Yocto reference
hardware MPC8315E-RDB.

Signed-off-by: Ed Bartosh 
---
 .../u-boot/files/MPC8315ERDB-enable-DHCP.patch| 19 +++
 meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc |  4 +++-
 2 files changed, 22 insertions(+), 1 deletion(-)
 create mode 100644 meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch

diff --git a/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch 
b/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
new file mode 100644
index 000..5a41108
--- /dev/null
+++ b/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
@@ -0,0 +1,19 @@
+Enabled dhcp client functionality for Yocto reference
+hardware MPC8315E-RDB.
+
+Upstream-Status: Submitted
+
+Signed-off-by: Ed Bartosh 
+
+diff --git a/configs/MPC8315ERDB_defconfig b/configs/MPC8315ERDB_defconfig
+index 4e2b705..b02ab1f 100644
+--- a/configs/MPC8315ERDB_defconfig
 b/configs/MPC8315ERDB_defconfig
+@@ -9,6 +9,7 @@ CONFIG_HUSH_PARSER=y
+ CONFIG_CMD_I2C=y
+ CONFIG_CMD_USB=y
+ # CONFIG_CMD_SETEXPR is not set
++CONFIG_CMD_DHCP=y
+ CONFIG_CMD_MII=y
+ CONFIG_CMD_PING=y
+ CONFIG_CMD_EXT2=y
diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc 
b/meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc
index df24c85..8ee1c32 100644
--- a/meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc
+++ b/meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc
@@ -9,6 +9,8 @@ PE = "1"
 # repo during parse
 SRCREV = "a705ebc81b7f91bbd0ef7c634284208342901149"
 
-SRC_URI = "git://git.denx.de/u-boot.git"
+SRC_URI = "git://git.denx.de/u-boot.git \
+file://MPC8315ERDB-enable-DHCP.patch \
+"
 
 S = "${WORKDIR}/git"
-- 
2.1.4

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

[OE-core] [PATCH] meta*: Add LAYERSERIES_COMPAT and LAYERSERIES_CORENAMES markup to layer.conf

[Richard Purdie]

This means mismatched layers are more clearly identified to the user in
cases where compatibility has not been tested. This is perhaps not as
needed for the core repository (other than CORENAMES) but lets lead by
example.

Signed-off-by: Richard Purdie 
---
 meta-selftest/conf/layer.conf | 2 ++
 meta-skeleton/conf/layer.conf | 2 ++
 meta/conf/layer.conf  | 2 ++
 3 files changed, 6 insertions(+)

diff --git a/meta-selftest/conf/layer.conf b/meta-selftest/conf/layer.conf
index a847b78..2a71895 100644
--- a/meta-selftest/conf/layer.conf
+++ b/meta-selftest/conf/layer.conf
@@ -8,3 +8,5 @@ BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
 BBFILE_COLLECTIONS += "selftest"
 BBFILE_PATTERN_selftest = "^${LAYERDIR}/"
 BBFILE_PRIORITY_selftest = "5"
+
+LAYERSERIES_COMPAT_selftest = "rocko"
diff --git a/meta-skeleton/conf/layer.conf b/meta-skeleton/conf/layer.conf
index aca1633..a15516a 100644
--- a/meta-skeleton/conf/layer.conf
+++ b/meta-skeleton/conf/layer.conf
@@ -13,3 +13,5 @@ BBFILE_PRIORITY_skeleton = "1"
 LAYERVERSION_skeleton = "1"
 
 LAYERDEPENDS_skeleton = "core"
+
+LAYERSERIES_COMPAT_skeleton = "rocko"
diff --git a/meta/conf/layer.conf b/meta/conf/layer.conf
index fc16502..6d36aa1 100644
--- a/meta/conf/layer.conf
+++ b/meta/conf/layer.conf
@@ -11,6 +11,8 @@ BBFILE_PRIORITY_core = "5"
 # cause compatibility issues with other layers
 LAYERVERSION_core = "10"
 
+LAYERSERIES_CORENAMES = "rocko"
+
 BBLAYERS_LAYERINDEX_NAME_core = "openembedded-core"
 
 # Set a variable to get to the top of the metadata location
-- 
2.7.4

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

[OE-core] ✗ patchtest: failure for u-boot: enable dhcp for MPC8315 board (rev2)

[Patchwork]

== Series Details ==

Series: u-boot: enable dhcp for MPC8315 board (rev2)
Revision: 2
URL   : https://patchwork.openembedded.org/series/7108/
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 Added patch file is missing Upstream-Status in the header 
[test_upstream_status_presence] 
  Suggested fixAdd Upstream-Status:  to the header of 
meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch (possible values: 
Pending, Submitted, Accepted, Backport, Denied, Inappropriate)

* Issue A patch file has been added, but does not have a 
Signed-off-by tag [test_signed_off_by_presence] 
  Suggested fixSign off the added patch file 
(meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch)



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] -> ...).

---
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 v2] u-boot: enable dhcp for MPC8315 board

[Ed Bartosh]

Getting ip address from DHCP server is much more convenient
than setting static ip. It allows to configure u-boot in
more generic way and to avoid hardcoding static ip in
u-boot configuration.

Enabled dhcp client functionality for Yocto reference
hardware MPC8315E-RDB.

Signed-off-by: Ed Bartosh 
---
 meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch | 12 
 meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc   |  4 +++-
 2 files changed, 15 insertions(+), 1 deletion(-)
 create mode 100644 meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch

diff --git a/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch 
b/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
new file mode 100644
index 000..df89e05
--- /dev/null
+++ b/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
@@ -0,0 +1,12 @@
+diff --git a/configs/MPC8315ERDB_defconfig b/configs/MPC8315ERDB_defconfig
+index 4e2b705..b02ab1f 100644
+--- a/configs/MPC8315ERDB_defconfig
 b/configs/MPC8315ERDB_defconfig
+@@ -9,6 +9,7 @@ CONFIG_HUSH_PARSER=y
+ CONFIG_CMD_I2C=y
+ CONFIG_CMD_USB=y
+ # CONFIG_CMD_SETEXPR is not set
++CONFIG_CMD_DHCP=y
+ CONFIG_CMD_MII=y
+ CONFIG_CMD_PING=y
+ CONFIG_CMD_EXT2=y
diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc 
b/meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc
index df24c85..8ee1c32 100644
--- a/meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc
+++ b/meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc
@@ -9,6 +9,8 @@ PE = "1"
 # repo during parse
 SRCREV = "a705ebc81b7f91bbd0ef7c634284208342901149"
 
-SRC_URI = "git://git.denx.de/u-boot.git"
+SRC_URI = "git://git.denx.de/u-boot.git \
+file://MPC8315ERDB-enable-DHCP.patch \
+"
 
 S = "${WORKDIR}/git"
-- 
2.1.4

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

Re: [OE-core] [PATCH] u-boot: enable dhcp for MPC8315 board

[Burton, Ross]

On 7 June 2017 at 13:05, Ed Bartosh  wrote:

> +file://MPC8315ERDB-enable-DHCP.patch \
>

This file isn't in the patch.

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

[OE-core] [PATCH] u-boot: enable dhcp for MPC8315 board

[Ed Bartosh]

Getting ip address from DHCP server is much more convenient
than setting static ip. It allows to configure u-boot in
more generic way and to avoid hardcoding static ip in
u-boot configuration.

Enabled dhcp client functionality for Yocto reference
hardware MPC8315E-RDB.

Signed-off-by: Ed Bartosh 
---
 meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc 
b/meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc
index df24c85..8ee1c32 100644
--- a/meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc
+++ b/meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc
@@ -9,6 +9,8 @@ PE = "1"
 # repo during parse
 SRCREV = "a705ebc81b7f91bbd0ef7c634284208342901149"
 
-SRC_URI = "git://git.denx.de/u-boot.git"
+SRC_URI = "git://git.denx.de/u-boot.git \
+file://MPC8315ERDB-enable-DHCP.patch \
+"
 
 S = "${WORKDIR}/git"
-- 
2.1.4

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

Re: [OE-core] Fun with npm shrinkwrap

[Jan Kiszka]

On 2017-06-07 13:43, Alexander Kanavin wrote:
> On 06/06/2017 06:14 PM, Jan Kiszka wrote:
> 
>> Yeah, good points. Probably this problem is also related to OE
>> reimplementing parts of the npm logic.
>>
>> But I suppose those concepts won't materialize very soon, will they? I'm
>> also looking for a short-term solution, at least some reasonable tactic
>> to generate such recipes in the meantime. Is there something in that
>> thread I should dig into?
> 
> What I am getting at is that it would be awesome if you convince your
> management that npm support in Yocto is a problem that needs a better
> solution and work on it. Yes, this means you can't work on product
> development for quite some time; this is the price for using open source
> projects without a commercial support contract :)

We are such a instance support :) - but we also need to get paid / pay
our contractors.

> 
> My apologies if this is not the answer you were seeking.
> 

I'm getting your point, even more now as I ran into a package that does
not even install at all (node-red-contrib-opcua). Can't promise anything
at this point, but I will carry this forward, in all directions.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH v2 01/25] bitbake.conf: support for merged usr with DISTRO_FEATURE usrmerge

[Richard Purdie]

On Wed, 2017-02-22 at 10:26 +0200, Amarnath Valluri wrote:
> From: Joshua Lock 
> 
> Modify bindir, libdir and sbindir to be exec_prefix/$d, rather than
> base_prefix/$d, when the usrmerge DISTRO_FEATURE is enabled.
> 
> Signed-off-by: Joshua Lock 
> ---
>  meta/conf/bitbake.conf | 12 
>  1 file changed, 8 insertions(+), 4 deletions(-)

I was asked to clarify the status of this series. We've taken many of
the changes but the core changes to bitbake.conf haven't been merged.

Ross/I discussed it and we both feel that the bitbake.conf make the
file pretty unreadable. We'd therefore like to see this implemented as
a .inc file which gets included when the relevant DISTRO_FEATURE is set
(or could just be included by the appropriate distro configs). This
.inc file would then simply override the paths. I believe this would be
a lot more readable than the current approach which is a key concern in
the core config.

The merge of the rest of this feature is therefore pending on the
development of such a patch, or a discussion convincing Ross/I why we
shouldn't take that approach for some reason.

Cheers,

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

Re: [OE-core] Fun with npm shrinkwrap

[Alexander Kanavin]

On 06/06/2017 06:14 PM, Jan Kiszka wrote:


Yeah, good points. Probably this problem is also related to OE
reimplementing parts of the npm logic.

But I suppose those concepts won't materialize very soon, will they? I'm
also looking for a short-term solution, at least some reasonable tactic
to generate such recipes in the meantime. Is there something in that
thread I should dig into?


What I am getting at is that it would be awesome if you convince your 
management that npm support in Yocto is a problem that needs a better 
solution and work on it. Yes, this means you can't work on product 
development for quite some time; this is the price for using open source 
projects without a commercial support contract :)


My apologies if this is not the answer you were seeking.

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

[OE-core] ✗ patchtest: failure for #11283: wic rm (rev2)

[Patchwork]

== Series Details ==

Series: #11283: wic rm (rev2)
Revision: 2
URL   : https://patchwork.openembedded.org/series/7046/
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 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 49c255494c)



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] -> ...).

---
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 v2 3/6] wic: add 'wic rm' command

[Ed Bartosh]

Added empty 'wic rm' command that does nothing.
The functionality will be added by the next commits.

[YOCTO #11283]

Signed-off-by: Ed Bartosh 
---
 scripts/lib/wic/engine.py |  7 +++
 scripts/wic   | 14 ++
 2 files changed, 21 insertions(+)

diff --git a/scripts/lib/wic/engine.py b/scripts/lib/wic/engine.py
index a48c4adafb..9a8055c05c 100644
--- a/scripts/lib/wic/engine.py
+++ b/scripts/lib/wic/engine.py
@@ -340,6 +340,13 @@ def wic_cp(args, native_sysroot):
 disk = Disk(args.dest.image, native_sysroot)
 disk.copy(args.src, args.dest.part, args.dest.path)
 
+def wic_rm(args, native_sysroot):
+"""
+Remove files or directories from the vfat partition of
+partitioned image.
+"""
+pass
+
 def find_canned(scripts_path, file_name):
 """
 Find a file either by its path or by name in the canned files dir.
diff --git a/scripts/wic b/scripts/wic
index fc192ec852..da14f4714a 100755
--- a/scripts/wic
+++ b/scripts/wic
@@ -248,6 +248,13 @@ def wic_cp_subcommand(args, usage_str):
 """
 engine.wic_cp(args, args.native_sysroot)
 
+def wic_rm_subcommand(args, usage_str):
+"""
+Command-line handling for removing files/dirs from images.
+The real work is done by engine.wic_rm()
+"""
+engine.wic_rm(args, args.native_sysroot)
+
 def wic_help_subcommand(args, usage_str):
 """
 Command-line handling for help subcommand to keep the current
@@ -286,6 +293,9 @@ helptopics = {
 "cp":[wic_help_topic_subcommand,
   wic_help_topic_usage,
   hlp.wic_cp_help],
+"rm":[wic_help_topic_subcommand,
+  wic_help_topic_usage,
+  hlp.wic_rm_help],
 "list":  [wic_help_topic_subcommand,
   wic_help_topic_usage,
   hlp.wic_list_help]
@@ -409,6 +419,10 @@ subcommands = {
   hlp.wic_cp_usage,
   hlp.wic_cp_help,
   wic_init_parser_cp],
+"rm":[wic_rm_subcommand,
+  hlp.wic_rm_usage,
+  hlp.wic_rm_help,
+  wic_init_parser_rm],
 "help":  [wic_help_subcommand,
   wic_help_topic_usage,
   hlp.wic_help_help,
-- 
2.12.0

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

[OE-core] [PATCH v2 5/6] wic: implement removing directories

[Ed Bartosh]

Added support for removing directories using mdeltree
utility to Disk.del method

[YOCTO #11283]

Signed-off-by: Ed Bartosh 
---
 scripts/lib/wic/engine.py | 22 ++
 1 file changed, 18 insertions(+), 4 deletions(-)

diff --git a/scripts/lib/wic/engine.py b/scripts/lib/wic/engine.py
index 6fc8bb72c3..2c899dd386 100644
--- a/scripts/lib/wic/engine.py
+++ b/scripts/lib/wic/engine.py
@@ -239,6 +239,7 @@ class Disk:
 self._mdir = None
 self._mcopy = None
 self._mdel = None
+self._mdeltree = None
 self._partimages = {}
 
 # find parted
@@ -290,6 +291,10 @@ class Disk:
 def mdel(self):
 return self._prop("mdel")
 
+@property
+def mdeltree(self):
+return self._prop("mdeltree")
+
 def _get_part_image(self, pnum):
 if pnum not in self.partitions:
 raise WicError("Partition %s is not in the image")
@@ -325,10 +330,19 @@ class Disk:
 
 def remove(self, pnum, path):
 """Remove files/dirs from the partition."""
-cmd = "{} -i {} ::{}".format(self.mdel,
- self._get_part_image(pnum),
- path)
-exec_cmd(cmd)
+partimg = self._get_part_image(pnum)
+cmd = "{} -i {} ::{}".format(self.mdel, partimg, path)
+try:
+exec_cmd(cmd)
+except WicError as err:
+if "not found" in str(err) or "non empty" in str(err):
+# mdel outputs 'File ... not found' or 'directory .. non empty"
+# try to use mdeltree as path could be a directory
+cmd = "{} -i {} ::{}".format(self.mdeltree,
+ partimg, path)
+exec_cmd(cmd)
+else:
+raise err
 self._put_part_image(pnum)
 
 def wic_ls(args, native_sysroot):
-- 
2.12.0

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

[OE-core] [PATCH v2 6/6] selftest: add test_wic_rm test case

[Ed Bartosh]

Added test case for "wic rm" functionality.
- remove file from vfat partition
- remove directory from vfat partition

Signed-off-by: Ed Bartosh 
---
 meta/lib/oeqa/selftest/cases/wic.py | 30 ++
 1 file changed, 30 insertions(+)

diff --git a/meta/lib/oeqa/selftest/cases/wic.py 
b/meta/lib/oeqa/selftest/cases/wic.py
index fa1a71c957..0e58a40ffc 100644
--- a/meta/lib/oeqa/selftest/cases/wic.py
+++ b/meta/lib/oeqa/selftest/cases/wic.py
@@ -891,3 +891,33 @@ part /etc --source rootfs --ondisk mmcblk0 --fstype=ext4 
--exclude-path bin/ --r
 self.assertEqual(0, result.status)
 self.assertEqual(8, len(result.output.split('\n')))
 self.assertTrue(os.path.basename(testdir) in result.output)
+
+def test_wic_rm(self):
+"""Test removing files and directories from the the wic image."""
+self.assertEqual(0, runCmd("wic create mkefidisk "
+   "--image-name=core-image-minimal "
+   "-D -o %s" % self.resultdir).status)
+images = glob(self.resultdir + "mkefidisk-*.direct")
+self.assertEqual(1, len(images))
+
+sysroot = get_bb_var('RECIPE_SYSROOT_NATIVE', 'wic-tools')
+
+# list directory content of the first partition
+result = runCmd("wic ls %s:1 -n %s" % (images[0], sysroot))
+self.assertEqual(0, result.status)
+self.assertTrue('\nbzimage' in result.output)
+self.assertTrue('\nefi   ' in result.output)
+
+# remove file
+result = runCmd("wic rm %s:1/bzimage -n %s" % (images[0], sysroot))
+self.assertEqual(0, result.status)
+
+# remove directory
+result = runCmd("wic rm %s:1/efi -n %s" % (images[0], sysroot))
+self.assertEqual(0, result.status)
+
+# check if they're removed
+result = runCmd("wic ls %s:1 -n %s" % (images[0], sysroot))
+self.assertEqual(0, result.status)
+self.assertFalse('\nbzimage' in result.output)
+self.assertFalse('\nefi   ' in result.output)
-- 
2.12.0

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

[OE-core] [PATCH v2 4/6] wic: implement removing files

[Ed Bartosh]

Added implementation of Disk.del method and wic_r
function that removes files from the vfat partition
using mdel utility.

[YOCTO #11283]

Signed-off-by: Ed Bartosh 
---
 scripts/lib/wic/engine.py | 16 +++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/scripts/lib/wic/engine.py b/scripts/lib/wic/engine.py
index 9a8055c05c..6fc8bb72c3 100644
--- a/scripts/lib/wic/engine.py
+++ b/scripts/lib/wic/engine.py
@@ -238,6 +238,7 @@ class Disk:
 self._partitions = None
 self._mdir = None
 self._mcopy = None
+self._mdel = None
 self._partimages = {}
 
 # find parted
@@ -285,6 +286,10 @@ class Disk:
 def mcopy(self):
 return self._prop("mcopy")
 
+@property
+def mdel(self):
+return self._prop("mdel")
+
 def _get_part_image(self, pnum):
 if pnum not in self.partitions:
 raise WicError("Partition %s is not in the image")
@@ -318,6 +323,14 @@ class Disk:
 exec_cmd(cmd)
 self._put_part_image(pnum)
 
+def remove(self, pnum, path):
+"""Remove files/dirs from the partition."""
+cmd = "{} -i {} ::{}".format(self.mdel,
+ self._get_part_image(pnum),
+ path)
+exec_cmd(cmd)
+self._put_part_image(pnum)
+
 def wic_ls(args, native_sysroot):
 """List contents of partitioned image or vfat partition."""
 disk = Disk(args.path.image, native_sysroot)
@@ -345,7 +358,8 @@ def wic_rm(args, native_sysroot):
 Remove files or directories from the vfat partition of
 partitioned image.
 """
-pass
+disk = Disk(args.path.image, native_sysroot)
+disk.remove(args.path.part, args.path.path)
 
 def find_canned(scripts_path, file_name):
 """
-- 
2.12.0

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

[OE-core] [PATCH v2 2/6] wic: add help and usage content for 'wic rm'

[Ed Bartosh]

Added wic_rm_help and wic_rm_usage variables to help.py.
These variables contain help content that will be used in
'wic rm help' and 'wic rm --help' output.

Signed-off-by: Ed Bartosh 
---
 scripts/lib/wic/help.py | 59 -
 1 file changed, 58 insertions(+), 1 deletion(-)

diff --git a/scripts/lib/wic/help.py b/scripts/lib/wic/help.py
index e93ac4b74c..23d943cc4c 100644
--- a/scripts/lib/wic/help.py
+++ b/scripts/lib/wic/help.py
@@ -395,7 +395,7 @@ DESCRIPTION
 The second form of the command copies file or directory to the specified 
directory
 on the vfat partition:
$ wic cp test 
tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.wic:1/efi/
-   $ wic ls 
tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.wic:1/eti/
+   $ wic ls 
tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.wic:1/efi/
Volume in drive : is boot
 Volume Serial Number is DB4C-FD4C
Directory for ::/efi
@@ -411,6 +411,63 @@ DESCRIPTION
 containing the tools(parted and mtools) to use.
 """
 
+wic_rm_usage = """
+
+ Remove files or directories from the vfat partitions
+
+ usage: wic rm : [--native-sysroot ]
+
+ This command  removes files or directories from the vfat partitions of 
partitioned
+ image.
+
+ See 'wic help rm' for more detailed instructions.
+
+"""
+
+wic_rm_help = """
+
+NAME
+wic rm - remove files or directories from the vfat partitions
+
+SYNOPSIS
+wic rm  :
+wic rm  : --native-sysroot 
+
+DESCRIPTION
+This command removes files or directories from the vfat partition of the
+wic image:
+
+$ wic ls 
./tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.wic:1
+Volume in drive : is boot
+ Volume Serial Number is 11D0-DE21
+Directory for ::/
+
+libcom32 c32186500 2017-06-02  15:15
+libutil  c32 24148 2017-06-02  15:15
+syslinux cfg   209 2017-06-02  15:15
+vesamenu c32 27104 2017-06-02  15:15
+vmlinuz6926384 2017-06-02  15:15
+5 files   7 164 345 bytes
+ 16 582 656 bytes free
+
+$ wic rm 
./tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.wic:1/libutil.c32
+
+$ wic ls 
./tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.wic:1
+Volume in drive : is boot
+ Volume Serial Number is 11D0-DE21
+Directory for ::/
+
+libcom32 c32186500 2017-06-02  15:15
+syslinux cfg   209 2017-06-02  15:15
+vesamenu c32 27104 2017-06-02  15:15
+vmlinuz6926384 2017-06-02  15:15
+4 files   7 140 197 bytes
+ 16 607 232 bytes free
+
+The -n option is used to specify the path to the native sysroot
+containing the tools(parted and mtools) to use.
+"""
+
 wic_plugins_help = """
 
 NAME
-- 
2.12.0

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

[OE-core] [PATCH v2 0/6] #11283: wic rm

[Ed Bartosh]

Hi,

This is an implementation of new wic subcommand 'wic rm'.

It removes files or directories from vfat partitions:

$ wic ls ./tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.wic:1
Volume in drive : is boot
 Volume Serial Number is 11D0-DE21
Directory for ::/

libcom32 c32186500 2017-06-02  15:15
libutil  c32 24148 2017-06-02  15:15
syslinux cfg   209 2017-06-02  15:15
vesamenu c32 27104 2017-06-02  15:15
vmlinuz6926384 2017-06-02  15:15
5 files   7 164 345 bytes
 16 582 656 bytes free

$ wic rm 
./tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.wic:1/libutil.c32

$ wic ls ./tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.wic:1
Volume in drive : is boot
 Volume Serial Number is 11D0-DE21
Directory for ::/

libcom32 c32186500 2017-06-02  15:15
syslinux cfg   209 2017-06-02  15:15
vesamenu c32 27104 2017-06-02  15:15
vmlinuz6926384 2017-06-02  15:15
4 files   7 140 197 bytes
 16 607 232 bytes free

The patchset also contains test case for 'wic rm' functionality.

Changes in v2: Modified test_wic_rm to fix test failure on Yocto autobuilder.

The following changes since commit 4a114a5ab10fc467c6c270b20af25b852250c78c:

  image_types_wic: schedule prepare_wic_build correctly (2017-06-07 10:42:20 
+0300)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib ed/wic/wip
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=ed/wic/wip

Ed Bartosh (6):
  wic: add wic_init_parser_rm
  wic: add help and usage content for 'wic rm'
  wic: add 'wic rm' command
  wic: implement removing files
  wic: implement removing directories
  selftest: add test_wic_rm test case

 meta/lib/oeqa/selftest/cases/wic.py | 30 +++
 scripts/lib/wic/engine.py   | 35 ++
 scripts/lib/wic/help.py | 59 -
 scripts/wic | 20 +
 4 files changed, 143 insertions(+), 1 deletion(-)

-- 
2.12.0

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

[OE-core] [PATCH v2 1/6] wic: add wic_init_parser_rm

[Ed Bartosh]

Add parser for 'wic rm' subcommand.

Signed-off-by: Ed Bartosh 
---
 scripts/wic | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/scripts/wic b/scripts/wic
index 5e81fad726..fc192ec852 100755
--- a/scripts/wic
+++ b/scripts/wic
@@ -379,6 +379,12 @@ def wic_init_parser_cp(subparser):
 subparser.add_argument("-n", "--native-sysroot",
 help="path to the native sysroot containing the tools")
 
+def wic_init_parser_rm(subparser):
+subparser.add_argument("path", type=imgpathtype,
+help="path: :")
+subparser.add_argument("-n", "--native-sysroot",
+help="path to the native sysroot containing the tools")
+
 def wic_init_parser_help(subparser):
 helpparsers = subparser.add_subparsers(dest='help_topic', 
help=hlp.wic_usage)
 for helptopic in helptopics:
-- 
2.12.0

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

Re: [OE-core] [PATCH v3] runtime/dnf: Add new dnf test cases

[Burton, Ross]

On 15 May 2017 at 14:50,  wrote:

> Add test cases to test “exclude” and “installroot“ options, also modify
> the logic of filtering packages on the feed to have all the packages
> needed by the tests.
>

Fails all over the autobuilder, for example:

http://errors.yoctoproject.org/Errors/Details/143886/

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

Re: [OE-core] [PATCH] libunwind: fix build failure on MIPS

[Burton, Ross]

On 7 June 2017 at 02:39, akuster808  wrote:

> under what conditions is this failing? or what is the build failure
> message. The subject makes it sound like your host is a Mips system.
>

Yeah good point.  I'll sent a v2.

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

[OE-core] [PATCH] libxml2: Fix CVE-2017-8872

[Fan Xin]

CVE: CVE-2017-8872
The htmlParseTryOrFinish function in HTMLparser.c in libxml2 2.9.4 allows 
attackers
to cause a denial of service (buffer over-read) or information disclosure.

External References:
https://bugzilla.gnome.org/show_bug.cgi?id=77520

Signed-off-by: Fan Xin 
---
 .../libxml/libxml2/libxml2-CVE-2017-8872.patch | 23 ++
 meta/recipes-core/libxml/libxml2_2.9.4.bb  |  1 +
 2 files changed, 24 insertions(+)
 create mode 100644 meta/recipes-core/libxml/libxml2/libxml2-CVE-2017-8872.patch

diff --git a/meta/recipes-core/libxml/libxml2/libxml2-CVE-2017-8872.patch 
b/meta/recipes-core/libxml/libxml2/libxml2-CVE-2017-8872.patch
new file mode 100644
index 000..df05e06
--- /dev/null
+++ b/meta/recipes-core/libxml/libxml2/libxml2-CVE-2017-8872.patch
@@ -0,0 +1,23 @@
+libxml2-2.9.4: Fix CVE-2017-8872
+
+Bug 775200 - (CVE-2017-8872) global-buffer-overflow in htmlParseTryOrFinish 
(HTMLparser.c:5403) 
+ - [https://bugzilla.gnome.org/show_bug.cgi?id=775200]
+
+CVE: CVE-2017-8872
+Upstream-Status: Submitted
+
+Signed-off-by: Fan Xin 
+
+Index: libxml2-2.9.4/HTMLparser.c
+===
+--- libxml2-2.9.4.orig/HTMLparser.c
 libxml2-2.9.4/HTMLparser.c
+@@ -5396,6 +5396,8 @@ htmlParseTryOrFinish(htmlParserCtxtPtr c
+   ctxt->instate = XML_PARSER_EOF;
+   if ((ctxt->sax) && (ctxt->sax->endDocument != NULL))
+   ctxt->sax->endDocument(ctxt->userData);
++
++  goto done;
+   }
+   }
+ if (avail < 1)
diff --git a/meta/recipes-core/libxml/libxml2_2.9.4.bb 
b/meta/recipes-core/libxml/libxml2_2.9.4.bb
index ea0d3b8..0b4cbca 100644
--- a/meta/recipes-core/libxml/libxml2_2.9.4.bb
+++ b/meta/recipes-core/libxml/libxml2_2.9.4.bb
@@ -24,6 +24,7 @@ SRC_URI = 
"ftp://xmlsoft.org/libxml2/libxml2-${PV}.tar.gz;name=libtar \
file://libxml2-CVE-2016-4658.patch \
file://libxml2-fix_NULL_pointer_derefs.patch \
file://CVE-2016-9318.patch \
+  file://libxml2-CVE-2017-8872.patch \
   "
 
 SRC_URI[libtar.md5sum] = "ae249165c173b1ff386ee8ad676815f5"
-- 
1.9.1

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

[OE-core] [PATCH] libtirpc: Fix CVE-2017-8779

[Fan Xin]

This vulnerability is also called "rpcbomb".
Backport upstream patch to fix this vulnerability.
CVE: CVE-2017-8779

Signed-off-by: Fan Xin
---
 .../libtirpc/0001-Fix-for-CVE-2017-8779.patch  | 276 +
 meta/recipes-extended/libtirpc/libtirpc_1.0.1.bb   |   1 +
 2 files changed, 277 insertions(+)
 create mode 100644 
meta/recipes-extended/libtirpc/libtirpc/0001-Fix-for-CVE-2017-8779.patch

diff --git 
a/meta/recipes-extended/libtirpc/libtirpc/0001-Fix-for-CVE-2017-8779.patch 
b/meta/recipes-extended/libtirpc/libtirpc/0001-Fix-for-CVE-2017-8779.patch
new file mode 100644
index 000..b3bae67
--- /dev/null
+++ b/meta/recipes-extended/libtirpc/libtirpc/0001-Fix-for-CVE-2017-8779.patch
@@ -0,0 +1,276 @@
+From dd9c7cf4f8f375c6d641b760d124650c418c2ce3 Mon Sep 17 00:00:00 2001
+From: Guido Vranken 
+Date: Mon, 15 May 2017 11:12:21 -0400
+Subject: [PATCH] Fix for CVE-2017-8779
+
+Signed-off-by: Steve Dickson 
+---
+ src/rpc_generic.c |  8 
+ src/rpcb_prot.c   | 22 ++
+ src/rpcb_st_xdr.c |  9 +
+ src/xdr.c | 30 +-
+ 4 files changed, 52 insertions(+), 17 deletions(-)
+
+CVE: CVE-2017-8779
+Upstream-Status: Backport
+
+Signed-off-by: Fan Xin 
+
+diff --git a/src/rpc_generic.c b/src/rpc_generic.c
+index 2f09a8f..589cbd5 100644
+--- a/src/rpc_generic.c
 b/src/rpc_generic.c
+@@ -615,6 +615,9 @@ __rpc_taddr2uaddr_af(int af, const struct netbuf *nbuf)
+ 
+   switch (af) {
+   case AF_INET:
++  if (nbuf->len < sizeof(*sin)) {
++  return NULL;
++  }
+   sin = nbuf->buf;
+   if (inet_ntop(af, >sin_addr, namebuf, sizeof namebuf)
+   == NULL)
+@@ -626,6 +629,9 @@ __rpc_taddr2uaddr_af(int af, const struct netbuf *nbuf)
+   break;
+ #ifdef INET6
+   case AF_INET6:
++  if (nbuf->len < sizeof(*sin6)) {
++  return NULL;
++  }
+   sin6 = nbuf->buf;
+   if (inet_ntop(af, >sin6_addr, namebuf6, sizeof namebuf6)
+   == NULL)
+@@ -667,6 +673,8 @@ __rpc_uaddr2taddr_af(int af, const char *uaddr)
+ 
+   port = 0;
+   sin = NULL;
++  if (uaddr == NULL)
++  return NULL;
+   addrstr = strdup(uaddr);
+   if (addrstr == NULL)
+   return NULL;
+diff --git a/src/rpcb_prot.c b/src/rpcb_prot.c
+index 43fd385..a923c8e 100644
+--- a/src/rpcb_prot.c
 b/src/rpcb_prot.c
+@@ -41,6 +41,7 @@
+ #include 
+ #include 
+ #include 
++#include "rpc_com.h"
+ 
+ bool_t
+ xdr_rpcb(xdrs, objp)
+@@ -53,13 +54,13 @@ xdr_rpcb(xdrs, objp)
+   if (!xdr_u_int32_t(xdrs, >r_vers)) {
+   return (FALSE);
+   }
+-  if (!xdr_string(xdrs, >r_netid, (u_int)~0)) {
++  if (!xdr_string(xdrs, >r_netid, RPC_MAXDATASIZE)) {
+   return (FALSE);
+   }
+-  if (!xdr_string(xdrs, >r_addr, (u_int)~0)) {
++  if (!xdr_string(xdrs, >r_addr, RPC_MAXDATASIZE)) {
+   return (FALSE);
+   }
+-  if (!xdr_string(xdrs, >r_owner, (u_int)~0)) {
++  if (!xdr_string(xdrs, >r_owner, RPC_MAXDATASIZE)) {
+   return (FALSE);
+   }
+   return (TRUE);
+@@ -159,19 +160,19 @@ xdr_rpcb_entry(xdrs, objp)
+   XDR *xdrs;
+   rpcb_entry *objp;
+ {
+-  if (!xdr_string(xdrs, >r_maddr, (u_int)~0)) {
++  if (!xdr_string(xdrs, >r_maddr, RPC_MAXDATASIZE)) {
+   return (FALSE);
+   }
+-  if (!xdr_string(xdrs, >r_nc_netid, (u_int)~0)) {
++  if (!xdr_string(xdrs, >r_nc_netid, RPC_MAXDATASIZE)) {
+   return (FALSE);
+   }
+   if (!xdr_u_int32_t(xdrs, >r_nc_semantics)) {
+   return (FALSE);
+   }
+-  if (!xdr_string(xdrs, >r_nc_protofmly, (u_int)~0)) {
++  if (!xdr_string(xdrs, >r_nc_protofmly, RPC_MAXDATASIZE)) {
+   return (FALSE);
+   }
+-  if (!xdr_string(xdrs, >r_nc_proto, (u_int)~0)) {
++  if (!xdr_string(xdrs, >r_nc_proto, RPC_MAXDATASIZE)) {
+   return (FALSE);
+   }
+   return (TRUE);
+@@ -292,7 +293,7 @@ xdr_rpcb_rmtcallres(xdrs, p)
+   bool_t dummy;
+   struct r_rpcb_rmtcallres *objp = (struct r_rpcb_rmtcallres *)(void *)p;
+ 
+-  if (!xdr_string(xdrs, >addr, (u_int)~0)) {
++  if (!xdr_string(xdrs, >addr, RPC_MAXDATASIZE)) {
+   return (FALSE);
+   }
+   if (!xdr_u_int(xdrs, >results.results_len)) {
+@@ -312,6 +313,11 @@ xdr_netbuf(xdrs, objp)
+   if (!xdr_u_int32_t(xdrs, (u_int32_t *) >maxlen)) {
+   return (FALSE);
+   }
++
++  if (objp->maxlen > RPC_MAXDATASIZE) {
++  return (FALSE);
++  }
++
+   dummy = xdr_bytes(xdrs, (char **)&(objp->buf),
+   (u_int *)&(objp->len), objp->maxlen);
+   return (dummy);
+diff --git a/src/rpcb_st_xdr.c b/src/rpcb_st_xdr.c
+index 

[OE-core] [PATCH] libtiff: Upgrade to 4.0.8

[Fan Xin]

1. Upgrade libtiff from 4.0.7 to 4.0.8

2. Delete the following patch file due to CVE-2017-5225 has been fixed in 4.0.8
 libtiff-CVE-2017-5225.patch

Signed-off-by: Fan Xin 
---
 .../libtiff/files/libtiff-CVE-2017-5225.patch  | 92 --
 .../libtiff/{tiff_4.0.7.bb => tiff_4.0.8.bb}   |  5 +-
 2 files changed, 2 insertions(+), 95 deletions(-)
 delete mode 100644 
meta/recipes-multimedia/libtiff/files/libtiff-CVE-2017-5225.patch
 rename meta/recipes-multimedia/libtiff/{tiff_4.0.7.bb => tiff_4.0.8.bb} (90%)

diff --git a/meta/recipes-multimedia/libtiff/files/libtiff-CVE-2017-5225.patch 
b/meta/recipes-multimedia/libtiff/files/libtiff-CVE-2017-5225.patch
deleted file mode 100644
index 3263353..000
--- a/meta/recipes-multimedia/libtiff/files/libtiff-CVE-2017-5225.patch
+++ /dev/null
@@ -1,92 +0,0 @@
-From a24df1e93833dfeaa69bf4d510518dc4684db64d Mon Sep 17 00:00:00 2001
-From: Li Zhou 
-Date: Wed, 25 Jan 2017 17:07:21 +0800
-Subject: [PATCH] libtiff: fix CVE-2017-5225
-
-tools/tiffcp.c: error out cleanly in cpContig2SeparateByRow
-and cpSeparate2ContigByRow if BitsPerSample != 8 to avoid heap based
-overflow. Fixes http://bugzilla.maptools.org/show_bug.cgi?id=2656 and
-http://bugzilla.maptools.org/show_bug.cgi?id=2657
-
-Upstream-Status: Backport
-CVE: CVE-2017-5225
-Signed-off-by: Li Zhou 

- ChangeLog  |  7 +++
- tools/tiffcp.c | 24 ++--
- 2 files changed, 29 insertions(+), 2 deletions(-)
-
-diff --git a/ChangeLog b/ChangeLog
-index 9b9d397..7e82795 100644
 a/ChangeLog
-+++ b/ChangeLog
-@@ -1,3 +1,10 @@
-+2017-01-11 Even Rouault 
-+
-+  * tools/tiffcp.c: error out cleanly in cpContig2SeparateByRow and
-+  cpSeparate2ContigByRow if BitsPerSample != 8 to avoid heap based 
overflow.
-+  Fixes http://bugzilla.maptools.org/show_bug.cgi?id=2656 and
-+  http://bugzilla.maptools.org/show_bug.cgi?id=2657
-+
- 2016-11-19  Bob Friesenhahn  
- 
-   * libtiff 4.0.7 released.
-diff --git a/tools/tiffcp.c b/tools/tiffcp.c
-index 338a3d1..2e84577 100644
 a/tools/tiffcp.c
-+++ b/tools/tiffcp.c
-@@ -592,7 +592,7 @@ static copyFunc pickCopyFunc(TIFF*, TIFF*, uint16, 
uint16);
- static int
- tiffcp(TIFF* in, TIFF* out)
- {
--  uint16 bitspersample, samplesperpixel = 1;
-+  uint16 bitspersample = 1, samplesperpixel = 1;
-   uint16 input_compression, input_photometric = PHOTOMETRIC_MINISBLACK;
-   copyFunc cf;
-   uint32 width, length;
-@@ -1068,6 +1068,16 @@ DECLAREcpFunc(cpContig2SeparateByRow)
-   register uint32 n;
-   uint32 row;
-   tsample_t s;
-+uint16 bps = 0;
-+
-+(void) TIFFGetField(in, TIFFTAG_BITSPERSAMPLE, );
-+if( bps != 8 )
-+{
-+TIFFError(TIFFFileName(in),
-+  "Error, can only handle BitsPerSample=8 in %s",
-+  "cpContig2SeparateByRow");
-+return 0;
-+}
- 
-   inbuf = _TIFFmalloc(scanlinesizein);
-   outbuf = _TIFFmalloc(scanlinesizeout);
-@@ -1121,6 +1131,16 @@ DECLAREcpFunc(cpSeparate2ContigByRow)
-   register uint32 n;
-   uint32 row;
-   tsample_t s;
-+uint16 bps = 0;
-+
-+(void) TIFFGetField(in, TIFFTAG_BITSPERSAMPLE, );
-+if( bps != 8 )
-+{
-+TIFFError(TIFFFileName(in),
-+  "Error, can only handle BitsPerSample=8 in %s",
-+  "cpSeparate2ContigByRow");
-+return 0;
-+}
- 
-   inbuf = _TIFFmalloc(scanlinesizein);
-   outbuf = _TIFFmalloc(scanlinesizeout);
-@@ -1763,7 +1783,7 @@ pickCopyFunc(TIFF* in, TIFF* out, uint16 bitspersample, 
uint16 samplesperpixel)
-   uint32 w, l, tw, tl;
-   int bychunk;
- 
--  (void) TIFFGetField(in, TIFFTAG_PLANARCONFIG, );
-+  (void) TIFFGetFieldDefaulted(in, TIFFTAG_PLANARCONFIG, );
-   if (shortv != config && bitspersample != 8 && samplesperpixel > 1) {
-   fprintf(stderr,
-   "%s: Cannot handle different planar configuration w/ 
bits/sample != 8\n",
--- 
-1.9.1
-
diff --git a/meta/recipes-multimedia/libtiff/tiff_4.0.7.bb 
b/meta/recipes-multimedia/libtiff/tiff_4.0.8.bb
similarity index 90%
rename from meta/recipes-multimedia/libtiff/tiff_4.0.7.bb
rename to meta/recipes-multimedia/libtiff/tiff_4.0.8.bb
index e581736..4a7aecc 100644
--- a/meta/recipes-multimedia/libtiff/tiff_4.0.7.bb
+++ b/meta/recipes-multimedia/libtiff/tiff_4.0.8.bb
@@ -6,11 +6,10 @@ CVE_PRODUCT = "libtiff"
 
 SRC_URI = "http://download.osgeo.org/libtiff/tiff-${PV}.tar.gz \
file://libtool2.patch \
-   file://libtiff-CVE-2017-5225.patch \
   "
 
-SRC_URI[md5sum] = "77ae928d2c6b7fb46a21c3a29325157b"
-SRC_URI[sha256sum] = 
"9f43a2cfb9589e5cecaa66e16bf87f814c945f22df7ba600d63aac4632c4f019"
+SRC_URI[md5sum] = "2a7d1c1318416ddf36d5f6fa4600069b"
+SRC_URI[sha256sum] = 

[OE-core] [PATCH V2] gdb: Upgrade to 8.0 release

[Khem Raj]

For details on changes see
http://lists.gnu.org/archive/html/info-gnu/2017-06/msg2.html

in tcmode-default.inc Pin gdb to 8.0

Signed-off-by: Khem Raj 
---
 meta/conf/distro/include/tcmode-default.inc|  2 +-
 .../gdb/{gdb-7.12.1.inc => gdb-8.0.inc}|  4 +-
 ...anadian_7.12.1.bb => gdb-cross-canadian_8.0.bb} |  0
 .../gdb/{gdb-cross_7.12.1.bb => gdb-cross_8.0.bb}  |  0
 .../gdb/0001-include-sys-types.h-for-mode_t.patch  |  6 +--
 ...0002-make-man-install-relative-to-DESTDIR.patch |  6 +--
 ...s-linux-nat-Define-_ABIO32-if-not-defined.patch |  8 +--
 ...Define-pt_regs-uapi_pt_regs-on-GLIBC-syst.patch | 10 ++--
 ...d-support-for-Renesas-SH-sh4-architecture.patch | 57 +++---
 ...e-libreadline.a-when-using-disable-static.patch | 12 ++---
 .../gdb/gdb/0007-use-asm-sgidefs.h.patch   |  8 +--
 .../0008-Use-exorted-definitions-of-SIGRTMIN.patch | 14 +++---
 .../gdb/gdb/0009-Change-order-of-CFLAGS.patch  | 24 -
 .../0010-resolve-restrict-keyword-conflict.patch   |  8 +--
 .../gdb/{gdb_7.12.1.bb => gdb_8.0.bb}  |  0
 15 files changed, 78 insertions(+), 81 deletions(-)
 rename meta/recipes-devtools/gdb/{gdb-7.12.1.inc => gdb-8.0.inc} (88%)
 rename meta/recipes-devtools/gdb/{gdb-cross-canadian_7.12.1.bb => 
gdb-cross-canadian_8.0.bb} (100%)
 rename meta/recipes-devtools/gdb/{gdb-cross_7.12.1.bb => gdb-cross_8.0.bb} 
(100%)
 rename meta/recipes-devtools/gdb/{gdb_7.12.1.bb => gdb_8.0.bb} (100%)

diff --git a/meta/conf/distro/include/tcmode-default.inc 
b/meta/conf/distro/include/tcmode-default.inc
index bdc70cfbb1..fe217c0392 100644
--- a/meta/conf/distro/include/tcmode-default.inc
+++ b/meta/conf/distro/include/tcmode-default.inc
@@ -25,7 +25,7 @@ PREFERRED_PROVIDER_virtual/gettext ??= "gettext"
 GCCVERSION ?= "6.3%"
 SDKGCCVERSION ?= "${GCCVERSION}"
 BINUVERSION ?= "2.28%"
-GDBVERSION ?= "7.12%"
+GDBVERSION ?= "8.0%"
 GLIBCVERSION ?= "2.25"
 UCLIBCVERSION ?= "1.0%"
 LINUXLIBCVERSION ?= "4.10%"
diff --git a/meta/recipes-devtools/gdb/gdb-7.12.1.inc 
b/meta/recipes-devtools/gdb/gdb-8.0.inc
similarity index 88%
rename from meta/recipes-devtools/gdb/gdb-7.12.1.inc
rename to meta/recipes-devtools/gdb/gdb-8.0.inc
index b15a2b5832..91f2ebfa4b 100644
--- a/meta/recipes-devtools/gdb/gdb-7.12.1.inc
+++ b/meta/recipes-devtools/gdb/gdb-8.0.inc
@@ -16,6 +16,6 @@ SRC_URI = "http://ftp.gnu.org/gnu/gdb/gdb-${PV}.tar.xz \
file://0009-Change-order-of-CFLAGS.patch \
file://0010-resolve-restrict-keyword-conflict.patch \
 "
-SRC_URI[md5sum] = "193453347ddced7acb6b1cd2ee8f2e4b"
-SRC_URI[sha256sum] = 
"4607680b973d3ec92c30ad029f1b7dbde3876869e6b3a117d8a7e90081113186"
+SRC_URI[md5sum] = "c3d35cd949084be53b92cc1e03485f88"
+SRC_URI[sha256sum] = 
"f6a24ffe4917e67014ef9273eb8b547cb96a13e5ca74895b06d683b391f3f4ee"
 
diff --git a/meta/recipes-devtools/gdb/gdb-cross-canadian_7.12.1.bb 
b/meta/recipes-devtools/gdb/gdb-cross-canadian_8.0.bb
similarity index 100%
rename from meta/recipes-devtools/gdb/gdb-cross-canadian_7.12.1.bb
rename to meta/recipes-devtools/gdb/gdb-cross-canadian_8.0.bb
diff --git a/meta/recipes-devtools/gdb/gdb-cross_7.12.1.bb 
b/meta/recipes-devtools/gdb/gdb-cross_8.0.bb
similarity index 100%
rename from meta/recipes-devtools/gdb/gdb-cross_7.12.1.bb
rename to meta/recipes-devtools/gdb/gdb-cross_8.0.bb
diff --git 
a/meta/recipes-devtools/gdb/gdb/0001-include-sys-types.h-for-mode_t.patch 
b/meta/recipes-devtools/gdb/gdb/0001-include-sys-types.h-for-mode_t.patch
index fc6c92f186..4f06d46d70 100644
--- a/meta/recipes-devtools/gdb/gdb/0001-include-sys-types.h-for-mode_t.patch
+++ b/meta/recipes-devtools/gdb/gdb/0001-include-sys-types.h-for-mode_t.patch
@@ -1,4 +1,4 @@
-From 2c81e17216b4e471a1ce0bddb50f374b0722a2ce Mon Sep 17 00:00:00 2001
+From 91da0458b333249eb9c2f4c1f1e53fa4bc085cc9 Mon Sep 17 00:00:00 2001
 From: Khem Raj 
 Date: Tue, 19 Jan 2016 18:18:52 -0800
 Subject: [PATCH 01/10] include sys/types.h for mode_t
@@ -14,7 +14,7 @@ Upstream-Status: Pending
  1 file changed, 1 insertion(+)
 
 diff --git a/gdb/gdbserver/target.h b/gdb/gdbserver/target.h
-index 4c14c204bb..bdab18f7f7 100644
+index 3cc2bc4bab..e6b19b06b9 100644
 --- a/gdb/gdbserver/target.h
 +++ b/gdb/gdbserver/target.h
 @@ -28,6 +28,7 @@
@@ -26,5 +26,5 @@ index 4c14c204bb..bdab18f7f7 100644
  struct emit_ops;
  struct buffer;
 -- 
-2.11.0
+2.13.1
 
diff --git 
a/meta/recipes-devtools/gdb/gdb/0002-make-man-install-relative-to-DESTDIR.patch 
b/meta/recipes-devtools/gdb/gdb/0002-make-man-install-relative-to-DESTDIR.patch
index 9a9201b39c..83c4dded3b 100644
--- 
a/meta/recipes-devtools/gdb/gdb/0002-make-man-install-relative-to-DESTDIR.patch
+++ 
b/meta/recipes-devtools/gdb/gdb/0002-make-man-install-relative-to-DESTDIR.patch
@@ -1,4 +1,4 @@
-From f316d604b312bead78594f02e1355633eda9507b Mon Sep 17 00:00:00 2001
+From 9ce61f97b7758794f06894e934fbb256ff62163e Mon Sep 17 00:00:00 2001
 From: Khem Raj 
 Date: Mon, 2 Mar 2015 

[OE-core] [PATCH v2 1/4] cve-check: add do_rootfs dependency on cve-check

[Peter Marko]

Since do_rootfs depends on cve-check results of all recipes,
we need to recursively depend on recipe do_cve_check.

Signed-off-by: Peter Marko 
---
 meta/classes/cve-check.bbclass | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/classes/cve-check.bbclass b/meta/classes/cve-check.bbclass
index 3a9e227..660fe7a 100644
--- a/meta/classes/cve-check.bbclass
+++ b/meta/classes/cve-check.bbclass
@@ -102,6 +102,7 @@ python cve_check_write_rootfs_manifest () {
 }
 
 ROOTFS_POSTPROCESS_COMMAND_prepend = "${@'cve_check_write_rootfs_manifest; ' 
if d.getVar('CVE_CHECK_CREATE_MANIFEST') == '1' else ''}"
+do_rootfs[recrdeptask] += "${@'do_cve_check' if 
d.getVar('CVE_CHECK_CREATE_MANIFEST') == '1' else ''}"
 
 def get_patches_cves(d):
 """
-- 
2.1.4

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

[OE-core] [PATCH v2 4/4] cve-check-tool: fix crash on exceptions

[Peter Marko]

This fixes cve-check-tool crashes on exceptions.

Signed-off-by: Peter Marko 
---
 .../cve-check-tool/cve-check-tool_5.6.4.bb |  1 +
 ...01-Fix-freeing-memory-allocated-by-sqlite.patch | 50 ++
 2 files changed, 51 insertions(+)
 create mode 100644 
meta/recipes-devtools/cve-check-tool/files/0001-Fix-freeing-memory-allocated-by-sqlite.patch

diff --git a/meta/recipes-devtools/cve-check-tool/cve-check-tool_5.6.4.bb 
b/meta/recipes-devtools/cve-check-tool/cve-check-tool_5.6.4.bb
index 1f906ee..4829b11 100644
--- a/meta/recipes-devtools/cve-check-tool/cve-check-tool_5.6.4.bb
+++ b/meta/recipes-devtools/cve-check-tool/cve-check-tool_5.6.4.bb
@@ -11,6 +11,7 @@ SRC_URI = 
"https://github.com/ikeydoherty/${BPN}/releases/download/v${PV}/${BP}.
file://0001-print-progress-in-percent-when-downloading-CVE-db.patch 
\
file://0001-curl-allow-overriding-default-CA-certificate-file.patch 
\

file://0001-update-Compare-computed-vs-expected-sha256-digit-str.patch \
+   file://0001-Fix-freeing-memory-allocated-by-sqlite.patch \
   "
 
 SRC_URI[md5sum] = "c5f4247140fc9be3bf41491d31a34155"
diff --git 
a/meta/recipes-devtools/cve-check-tool/files/0001-Fix-freeing-memory-allocated-by-sqlite.patch
 
b/meta/recipes-devtools/cve-check-tool/files/0001-Fix-freeing-memory-allocated-by-sqlite.patch
new file mode 100644
index 000..4a82cf2
--- /dev/null
+++ 
b/meta/recipes-devtools/cve-check-tool/files/0001-Fix-freeing-memory-allocated-by-sqlite.patch
@@ -0,0 +1,50 @@
+From a3353429652f83bb8b0316500faa88fa242d Mon Sep 17 00:00:00 2001
+From: Peter Marko 
+Date: Thu, 13 Apr 2017 23:09:52 +0200
+Subject: [PATCH] Fix freeing memory allocated by sqlite
+
+Upstream-Status: Backport
+Signed-off-by: Peter Marko 
+---
+ src/core.c | 8 
+ 1 file changed, 4 insertions(+), 4 deletions(-)
+
+diff --git a/src/core.c b/src/core.c
+index 6263031..6788f16 100644
+--- a/src/core.c
 b/src/core.c
+@@ -82,7 +82,7 @@ static bool ensure_table(CveDB *self)
+ rc = sqlite3_exec(self->db, query, NULL, NULL, );
+ if (rc != SQLITE_OK) {
+ fprintf(stderr, "ensure_table(): %s\n", err);
+-free(err);
++sqlite3_free(err);
+ return false;
+ }
+ 
+@@ -91,7 +91,7 @@ static bool ensure_table(CveDB *self)
+ rc = sqlite3_exec(self->db, query, NULL, NULL, );
+ if (rc != SQLITE_OK) {
+ fprintf(stderr, "ensure_table(): %s\n", err);
+-free(err);
++sqlite3_free(err);
+ return false;
+ }
+ 
+@@ -99,11 +99,11 @@ static bool ensure_table(CveDB *self)
+ rc = sqlite3_exec(self->db, query, NULL, NULL, );
+ if (rc != SQLITE_OK) {
+ fprintf(stderr, "ensure_table(): %s\n", err);
+-free(err);
++sqlite3_free(err);
+ return false;
+ }
+ if (err) {
+-free(err);
++sqlite3_free(err);
+ }
+ 
+ return true;
+-- 
+2.1.4
+
-- 
2.1.4

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

[OE-core] [PATCH v2 3/4] cve-check: clean cve-check recipe result before re-building

[Peter Marko]

If there is cve report for a recipe in previous build and there
is no result for current one, old cves are kept in CVE_CHECK_DIR.
This happens on version upgrade or when cve/recipe is whitelisted.

Signed-off-by: Peter Marko 
---
 meta/classes/cve-check.bbclass | 5 +
 1 file changed, 5 insertions(+)

diff --git a/meta/classes/cve-check.bbclass b/meta/classes/cve-check.bbclass
index 1f0b691..6f5b0f5 100644
--- a/meta/classes/cve-check.bbclass
+++ b/meta/classes/cve-check.bbclass
@@ -83,6 +83,11 @@ python cve_check_write_rootfs_manifest () {
 
 import shutil
 
+if d.getVar("CVE_CHECK_COPY_FILES") == "1":
+deploy_file = os.path.join(d.getVar("CVE_CHECK_DIR"), d.getVar("PN"))
+if os.path.exists(deploy_file):
+bb.utils.remove(deploy_file)
+
 if os.path.exists(d.getVar("CVE_CHECK_TMP_FILE")):
 bb.note("Writing rootfs CVE manifest")
 deploy_dir = d.getVar("DEPLOY_DIR_IMAGE")
-- 
2.1.4

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

[OE-core] [PATCH v2 0/4] cve-check improvements

[Peter Marko]

Hi,

this series of patches fixes some issues with cve-check functionality.

v2: drop patch for RM_OLD_IMAGE handling

Peter Marko (4):
  cve-check: add do_rootfs dependency on cve-check
  cve-check: do not parse error output
  cve-check: clean cve-check recipe result before re-building
  cve-check-tool: fix crash on exceptions

 meta/classes/cve-check.bbclass |  8 +++-
 .../cve-check-tool/cve-check-tool_5.6.4.bb |  1 +
 ...01-Fix-freeing-memory-allocated-by-sqlite.patch | 50 ++
 3 files changed, 58 insertions(+), 1 deletion(-)
 create mode 100644 
meta/recipes-devtools/cve-check-tool/files/0001-Fix-freeing-memory-allocated-by-sqlite.patch

-- 
2.1.4

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

[OE-core] [PATCH v2 2/4] cve-check: do not parse error output

[Peter Marko]

Sometimes there are control messages in cve-check-tool printed to
stderr. These lead to parsing error and thus failed build.
This can happen for instance when cve database needs to be
refreshed during build.

Signed-off-by: Peter Marko 
---
 meta/classes/cve-check.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/cve-check.bbclass b/meta/classes/cve-check.bbclass
index 660fe7a..1f0b691 100644
--- a/meta/classes/cve-check.bbclass
+++ b/meta/classes/cve-check.bbclass
@@ -172,7 +172,7 @@ def check_cves(d, patched_cves):
 f.write("%s,%s,%s," % (bpn, pv, cves))
 cmd.append(faux)
 
-output = subprocess.check_output(cmd, 
stderr=subprocess.STDOUT).decode("utf-8")
+output = subprocess.check_output(cmd).decode("utf-8")
 bb.debug(2, "Output of command %s:\n%s" % ("\n".join(cmd), output))
 except subprocess.CalledProcessError as e:
 bb.warn("Couldn't check for CVEs: %s (output %s)" % (e, e.output))
-- 
2.1.4

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