Re: [OE-core] [PATCH 1/5] mesa: Enable gallium-llvm on x86 and x86_64

[Andreas Müller]

On Tue, Aug 28, 2018 at 12:55 AM, Khem Raj  wrote:
> On Mon, Aug 27, 2018 at 2:15 PM Andreas Müller  
> wrote:
>>
>> On Mon, Aug 20, 2018 at 8:59 PM, Khem Raj  wrote:
>> > Signed-off-by: Khem Raj 
>> > ---
>> >  meta/recipes-graphics/cairo/cairo.inc | 3 ++-
>> >  meta/recipes-graphics/mesa/mesa.inc   | 3 +++
>> >  2 files changed, 5 insertions(+), 1 deletion(-)
>> >
>> > diff --git a/meta/recipes-graphics/cairo/cairo.inc 
>> > b/meta/recipes-graphics/cairo/cairo.inc
>> > index 20e0d2c92a..7347f223ff 100644
>> > --- a/meta/recipes-graphics/cairo/cairo.inc
>> > +++ b/meta/recipes-graphics/cairo/cairo.inc
>> > @@ -22,7 +22,8 @@ X11DEPENDS = "virtual/libx11 libsm libxrender libxext"
>> >  DEPENDS = "libpng fontconfig pixman glib-2.0 zlib"
>> >
>> >  PACKAGECONFIG ??= "${@bb.utils.contains('DISTRO_FEATURES', 'x11', 'x11 
>> > xcb', '', d)} \
>> > -   ${@bb.utils.filter('DISTRO_FEATURES', 'directfb', d)}"
>> > +   ${@bb.utils.filter('DISTRO_FEATURES', 'directfb', d)} \
>> > +   ${@bb.utils.contains('DISTRO_FEATURES', 'x11 opengl', 
>> > 'opengl', '', d)}"
>> >
>> >  PACKAGECONFIG[x11] = "--with-x=yes -enable-xlib,--with-x=no 
>> > --disable-xlib,${X11DEPENDS}"
>> >  PACKAGECONFIG[xcb] = "--enable-xcb,--disable-xcb,libxcb"
>> > diff --git a/meta/recipes-graphics/mesa/mesa.inc 
>> > b/meta/recipes-graphics/mesa/mesa.inc
>> > index 5afd0db4b7..dd626d9f00 100644
>> ^ I think this came in accidentaly and it breaks builds when adding
>> packageconfig glesv2:
>>
>> | configure: error: use either --enable-gl=yes or --enable-glesv2=yes.
>> Not both at the same time.
>
> do you remove opengl from DISTRO_FEATURES when enabling glesv2 ?
> try that out.
>
>>
Yes of course I can. But this patch is wrong - we don't have gles as
distro feature - and it is not even mentioned in commit message why
this is done.

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

[OE-core] [PATCH] libid3tag: patch for CVE-2004-2779

[changqing.li]

From: Changqing Li 

Signed-off-by: Changqing Li 
---
 .../libid3tag/libid3tag/10_utf16.dpatch| 33 ++
 .../libid3tag/libid3tag_0.15.1b.bb |  1 +
 2 files changed, 34 insertions(+)
 create mode 100644 meta/recipes-multimedia/libid3tag/libid3tag/10_utf16.dpatch

diff --git a/meta/recipes-multimedia/libid3tag/libid3tag/10_utf16.dpatch 
b/meta/recipes-multimedia/libid3tag/libid3tag/10_utf16.dpatch
new file mode 100644
index 000..8d09ce7
--- /dev/null
+++ b/meta/recipes-multimedia/libid3tag/libid3tag/10_utf16.dpatch
@@ -0,0 +1,33 @@
+libid3tag: patch for CVE-2004-2779
+
+The patch comes from
+https://sources.debian.org/patches/libid3tag/0.15.1b-13/10_utf16.dpatch
+
+Upstream-Status: Pending
+
+CVE: CVE-2004-2779
+
+Signed-off-by: Changqing Li 
+
+diff -urNad libid3tag-0.15.1b/utf16.c 
/tmp/dpep.tKvO7a/libid3tag-0.15.1b/utf16.c
+--- libid3tag-0.15.1b/utf16.c  2006-01-13 15:26:29.0 +0100
 /tmp/dpep.tKvO7a/libid3tag-0.15.1b/utf16.c 2006-01-13 15:27:19.0 
+0100
+@@ -282,5 +282,18 @@
+ 
+   free(utf16);
+ 
++  if (end == *ptr && length % 2 != 0)
++  {
++ /* We were called with a bogus length.  It should always
++  * be an even number.  We can deal with this in a few ways:
++  * - Always give an error.
++  * - Try and parse as much as we can and
++  *   - return an error if we're called again when we
++  * already tried to parse everything we can.
++  *   - tell that we parsed it, which is what we do here.
++  */
++ (*ptr)++;
++  }
++
+   return ucs4;
+ }
diff --git a/meta/recipes-multimedia/libid3tag/libid3tag_0.15.1b.bb 
b/meta/recipes-multimedia/libid3tag/libid3tag_0.15.1b.bb
index f6139d6..fe31646 100644
--- a/meta/recipes-multimedia/libid3tag/libid3tag_0.15.1b.bb
+++ b/meta/recipes-multimedia/libid3tag/libid3tag_0.15.1b.bb
@@ -13,6 +13,7 @@ SRC_URI = "${SOURCEFORGE_MIRROR}/mad/libid3tag-${PV}.tar.gz \
file://addpkgconfig.patch \
file://obsolete_automake_macros.patch \
file://0001-Fix-gperf-3.1-incompatibility.patch \
+   file://10_utf16.dpatch \
"
 UPSTREAM_CHECK_URI = "https://sourceforge.net/projects/mad/files/libid3tag/";
 UPSTREAM_CHECK_REGEX = "/projects/mad/files/libid3tag/(?P.*)/$"
-- 
2.7.4

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

[OE-core] Troubleshooting sstate cache

[Nick Winters]

Often when I use an sstate cache from another build, I run into problems
where builds fail. Usually the failure is a result of not being able to
find a shared library. If I delete the sstate cache, the build succeeds,
although it is 8 hours later. I switched to using sstate mirrors and had
similar problems.

Questions:

* Are there any tools or bitbake commands to use for troubleshooting
failures like this?

* I am creating one sstate cache per architecture being built. Should this
really be necessary?

* Any other advice to help troubleshoot sstate cache issues?

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

[OE-core] [PATCH] libjpeg-turbo: Upgrade 1.5.3 -> 2.0.0

[changqing.li]

From: Changqing Li 

License-Update: Copyright Year Update

1. Upgrade from 1.5.3 -> 2.0.0, change from autools to cmake
2. Add a patch for fix package qa error
3. remove --with-build-date since 2.0.0 not support config build date

Signed-off-by: Changqing Li 
---
 .../0001-libjpeg-turbo-fix-package_qa-error.patch  | 32 ++
 ...bjpeg-turbo_1.5.3.bb => libjpeg-turbo_2.0.0.bb} | 29 
 2 files changed, 43 insertions(+), 18 deletions(-)
 create mode 100644 
meta/recipes-graphics/jpeg/files/0001-libjpeg-turbo-fix-package_qa-error.patch
 rename meta/recipes-graphics/jpeg/{libjpeg-turbo_1.5.3.bb => 
libjpeg-turbo_2.0.0.bb} (61%)

diff --git 
a/meta/recipes-graphics/jpeg/files/0001-libjpeg-turbo-fix-package_qa-error.patch
 
b/meta/recipes-graphics/jpeg/files/0001-libjpeg-turbo-fix-package_qa-error.patch
new file mode 100644
index 000..44c2c76
--- /dev/null
+++ 
b/meta/recipes-graphics/jpeg/files/0001-libjpeg-turbo-fix-package_qa-error.patch
@@ -0,0 +1,32 @@
+From 0a24f03a67425a7b58b3fd40d965c0c9801ae7a1 Mon Sep 17 00:00:00 2001
+From: Changqing Li 
+Date: Mon, 27 Aug 2018 16:10:55 +0800
+Subject: [PATCH] libjpeg-turbo: fix package_qa error
+
+Fix package qa errors like below:
+libjpeg.so.62.3.0 contains probably-redundant RPATH /usr/lib [useless-rpaths]
+usr/bin/cjpeg contains probably-redundant RPATH /usr/lib
+
+Upstream-Status: Inappropriate[oe-specific]
+
+Signed-off-by: Changqing Li 
+---
+ CMakeLists.txt | 2 --
+ 1 file changed, 2 deletions(-)
+
+diff --git a/CMakeLists.txt b/CMakeLists.txt
+index 1719522..682cef1 100644
+--- a/CMakeLists.txt
 b/CMakeLists.txt
+@@ -109,8 +109,6 @@ endif()
+ 
+ include(cmakescripts/GNUInstallDirs.cmake)
+ 
+-set(CMAKE_INSTALL_RPATH ${CMAKE_INSTALL_FULL_LIBDIR})
+-
+ macro(report_directory var)
+   if(CMAKE_INSTALL_${var} STREQUAL CMAKE_INSTALL_FULL_${var})
+ message(STATUS "CMAKE_INSTALL_${var} = ${CMAKE_INSTALL_${var}}")
+-- 
+2.7.4
+
diff --git a/meta/recipes-graphics/jpeg/libjpeg-turbo_1.5.3.bb 
b/meta/recipes-graphics/jpeg/libjpeg-turbo_2.0.0.bb
similarity index 61%
rename from meta/recipes-graphics/jpeg/libjpeg-turbo_1.5.3.bb
rename to meta/recipes-graphics/jpeg/libjpeg-turbo_2.0.0.bb
index 6be6aa5..7737a59 100644
--- a/meta/recipes-graphics/jpeg/libjpeg-turbo_1.5.3.bb
+++ b/meta/recipes-graphics/jpeg/libjpeg-turbo_2.0.0.bb
@@ -4,16 +4,17 @@ HOMEPAGE = "http://libjpeg-turbo.org/";
 
 LICENSE = "BSD-3-Clause"
 LIC_FILES_CHKSUM = 
"file://cdjpeg.h;endline=13;md5=8184bcc7c4ac7b9edc6a7bc00f231d0b \
-
file://jpeglib.h;endline=16;md5=f67d70e547a2662c079781c72f877f72 \
+
file://jpeglib.h;endline=16;md5=7ea97dc83b0f59052ee837e61ef0e08f \
 
file://djpeg.c;endline=11;md5=c59e19811c006cb38f82d6477134d314 \
 "
 DEPENDS_append_x86-64_class-target = " nasm-native"
 DEPENDS_append_x86_class-target= " nasm-native"
 
-SRC_URI = "${SOURCEFORGE_MIRROR}/${BPN}/${BPN}-${PV}.tar.gz"
+SRC_URI = "${SOURCEFORGE_MIRROR}/${BPN}/${BPN}-${PV}.tar.gz \
+   file://0001-libjpeg-turbo-fix-package_qa-error.patch"
 
-SRC_URI[md5sum] = "7c82f0f6a3130ec06b8a4d0b321cbca3"
-SRC_URI[sha256sum] = 
"b24890e2bb46e12e72a79f7e965f409f4e16466d00e1dd15d93d73ee6b592523"
+SRC_URI[md5sum] = "b12a3fcf1d078db38410f27718a91b83"
+SRC_URI[sha256sum] = 
"778876105d0d316203c928fd2a0374c8c01f755d0a00b12a1c8934aeccff8868"
 UPSTREAM_CHECK_URI = "http://sourceforge.net/projects/libjpeg-turbo/files/";
 UPSTREAM_CHECK_REGEX = "/libjpeg-turbo/files/(?P(\d+[\.\-_]*)+)/"
 
@@ -25,32 +26,24 @@ RPROVIDES_${PN} += "jpeg"
 RREPLACES_${PN} += "jpeg"
 RCONFLICTS_${PN} += "jpeg"
 
-inherit autotools pkgconfig
+inherit cmake pkgconfig
 
 # Add nasm-native dependency consistently for all build arches is hard
-EXTRA_OECONF_append_class-native = " --without-simd"
+EXTRA_OECMAKE_append_class-native = " -DWITH_SIMD=False"
 
 # Work around missing x32 ABI support
-EXTRA_OECONF_append_class-target = " ${@bb.utils.contains("TUNE_FEATURES", 
"mx32", "--without-simd", "", d)}"
+EXTRA_OECMAKE_append_class-target = " ${@bb.utils.contains("TUNE_FEATURES", 
"mx32", "-DWITH_SIMD=False", "", d)}"
 
 # Work around missing non-floating point ABI support in MIPS
-EXTRA_OECONF_append_class-target = " ${@bb.utils.contains("MIPSPKGSFX_FPU", 
"-nf", "--without-simd", "", d)}"
+EXTRA_OECMAKE_append_class-target = " ${@bb.utils.contains("MIPSPKGSFX_FPU", 
"-nf", "-DWITH_SIMD=False", "", d)}"
 
 # Provide a workaround if Altivec unit is not present in PPC
-EXTRA_OECONF_append_class-target_powerpc = " 
${@bb.utils.contains("TUNE_FEATURES", "altivec", "", "--without-simd", d)}"
-EXTRA_OECONF_append_class-target_powerpc64 = " 
${@bb.utils.contains("TUNE_FEATURES", "altivec", "", "--without-simd", d)}"
+EXTRA_OECMAKE_append_class-target_powerpc = " 
${@bb.utils.contains("TUNE_FEATURES", "altivec", "", "-DWITH_SIMD=False", d)}"
+EXTRA_OECMAKE_append_class-target_powerpc64 = " 
${@bb.utils.contains("TUNE_FEATURES", "altivec", "", "-DWITH_SIMD=False", d)}"

Re: [OE-core] [PATCH] boost: add ptest support

[Randy MacLeod]

On 08/27/2018 06:17 PM, Yang Wang wrote:
Not sure if it's worth to run the Ptest on QEMU though, I also run Ptest 
on SIMICS simulators, thousands of tests didn't get run, looks like the 
result was not good as well.


Now my nightly Ptest runs on x86 device and gets consistent result every 
day:


     2018-08-27T06:26 -- 2018-08-27T09:52
     Passed:  40518
     Failed:  289
     Skipped: 1876


Consistent results are good and > 90% pass rate is very good.
What are the stats using qemux86-64 and/or simics?

I don't expect that qemu results would be as close to real hardware
as Simics but it is quite good and freely available.



Thanks,
Yang Wang



--
# Randy MacLeod
# Wind River Linux
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 3/3] image_types_wic: Add variable WIC_EXTENSION

[Richard Purdie]

On Mon, 2018-08-27 at 17:31 +0300, Alexandru Vasiu wrote:
> Used to specify what extention will have the image file which
> is created using wic. The default value is wic. For creating an
> ISO image, WIC_EXTENSION will be iso.
> 
> Signed-off-by: Alexandru Vasiu 
> ---
>  meta/classes/image.bbclass   | 2 ++
>  meta/classes/image_types_wic.bbclass | 3 ++-
>  2 files changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
> index 024d2d4c96..c6833a6770 100644
> --- a/meta/classes/image.bbclass
> +++ b/meta/classes/image.bbclass
> @@ -607,6 +607,8 @@ python create_symlinks() {
>  if not link_name:
>  return
>  for type in subimages:
> +if type == 'wic':
> +type = d.getVar('WIC_EXTENSION')
>  dst = os.path.join(deploy_dir, link_name + "." + type)
>  src = img_name + imgsuffix + type
>  if os.path.exists(os.path.join(deploy_dir, src)):

This is hardcoding an image type specific issue into common code. I
really want to avoid doing that.

In the past I started the process of trying to untangle the spaghetti
we had in image.bbclass and abstract it into common building blocks.
The hope was to eventually have proper APIs around this.

I never really got back to do further rounds of cleanup/improvement to
get to that goal but the more image type specific pieces we add back
in, the harder it will make those goals and the less maintainable the
coed will become.

So is there some other way we can handle this. It looks like we don't
even use this iso mode in OE-Core which is bad from a testing
perspective too? I don't see WIC_EXTENSION being set to iso anywhere?

Cheers,

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

Re: [OE-core] [PATCH 1/5] mesa: Enable gallium-llvm on x86 and x86_64

[Khem Raj]

On Mon, Aug 27, 2018 at 2:15 PM Andreas Müller  wrote:
>
> On Mon, Aug 20, 2018 at 8:59 PM, Khem Raj  wrote:
> > Signed-off-by: Khem Raj 
> > ---
> >  meta/recipes-graphics/cairo/cairo.inc | 3 ++-
> >  meta/recipes-graphics/mesa/mesa.inc   | 3 +++
> >  2 files changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/meta/recipes-graphics/cairo/cairo.inc 
> > b/meta/recipes-graphics/cairo/cairo.inc
> > index 20e0d2c92a..7347f223ff 100644
> > --- a/meta/recipes-graphics/cairo/cairo.inc
> > +++ b/meta/recipes-graphics/cairo/cairo.inc
> > @@ -22,7 +22,8 @@ X11DEPENDS = "virtual/libx11 libsm libxrender libxext"
> >  DEPENDS = "libpng fontconfig pixman glib-2.0 zlib"
> >
> >  PACKAGECONFIG ??= "${@bb.utils.contains('DISTRO_FEATURES', 'x11', 'x11 
> > xcb', '', d)} \
> > -   ${@bb.utils.filter('DISTRO_FEATURES', 'directfb', d)}"
> > +   ${@bb.utils.filter('DISTRO_FEATURES', 'directfb', d)} \
> > +   ${@bb.utils.contains('DISTRO_FEATURES', 'x11 opengl', 'opengl', 
> > '', d)}"
> >
> >  PACKAGECONFIG[x11] = "--with-x=yes -enable-xlib,--with-x=no 
> > --disable-xlib,${X11DEPENDS}"
> >  PACKAGECONFIG[xcb] = "--enable-xcb,--disable-xcb,libxcb"
> > diff --git a/meta/recipes-graphics/mesa/mesa.inc 
> > b/meta/recipes-graphics/mesa/mesa.inc
> > index 5afd0db4b7..dd626d9f00 100644
> ^ I think this came in accidentaly and it breaks builds when adding
> packageconfig glesv2:
>
> | configure: error: use either --enable-gl=yes or --enable-glesv2=yes.
> Not both at the same time.

do you remove opengl from DISTRO_FEATURES when enabling glesv2 ?
try that out.

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

Re: [OE-core] [PATCH] sstate: Add sstate usage summary to the build

[Richard Purdie]

On Mon, 2018-08-27 at 23:47 +0100, richard.pur...@linuxfoundation.org
wrote:
> On Fri, 2018-08-24 at 23:24 +0200, Martin Jansa wrote:
> > This is nice addition, but maybe it would be worth explaining
> > somewhere what these numbers actually mean.
> > 
> > e.g. my current build shows:
> > Sstate summary: Wanted 181 Found 39 Missed 142 Current 279 (21%
> > match, 69% complete)

I should add that with a bit of experience you can learnt to interpret
these.

A build with a ~20% match often means the do_populate_lic sstate
matched and nothing else did. That means there is a fair amount of work
to be done.

On the other hand, the 69% is fairly positive as a large chunk of the
build is already complete.

I'm basing this just on having watched a few builds on the
autobuilder...

Cheers,

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

Re: [OE-core] [PATCH] sstate: Add sstate usage summary to the build

[richard . purdie]

On Fri, 2018-08-24 at 23:24 +0200, Martin Jansa wrote:
> This is nice addition, but maybe it would be worth explaining
> somewhere what these numbers actually mean.
> 
> e.g. my current build shows:
> Sstate summary: Wanted 181 Found 39 Missed 142 Current 279 (21%
> match, 69% complete)
> 
> From quick look at the code my understanding is that:
> 1) Wanted = Found + Missed
> 2) Wanted is number of sstate covered tasks needed for current build,
> Found is how many of them will be covered by existing sstate (fetched
> from SSTATE_MIRROR or local) and match is just Found/Wanted
> 3) Current is most confusing for me as it is a sum of tasks covered
> either by normal stamps or setscene and complete is then percentage
> of the tasks which either doesn't need to be executed at all or will
> be covered by sstate

Wanted is the number of artefacts the build ideally wants from sstate

Found is the number of artefacts present in sstate locally or it thinks
are fetchable from any mirrors

Missed = Wanted - Found

Current is the number of stamps which bitbake viewed as "current", i.e.
it needed to do nothing. Since they're current, it wouldn't bother
querying sstate or considering them any further.

"% match" tells you how much of the sstate queried, matched

"% complete" tells you how much of the build is already current or
completed

The reason the current/complete numbers are there are because a build
directory where a build has already partly completed could show a "0%
match" against sstate but its not immediately clear that things which
have already run are never checked for in sstate. A build which was 90%
complete would likely have a high "% match" for a fresh tmpdir so this
was added to try and give people a real idea of how much work remains
in a given build "up front" when you start the build.

Does that help explain it? I'm open to better terminology but its hard
to find something short and simple which conveys this...

> 4) Neither of these is about not-sstate-covered tasks which for this
> build was 1983 and 1574 were already covered by stamp files (as shown
> at the end of the build shown bellow)

The % current is close. 1574/1983 = 79% which is approx equal (but
greater than) 69%. The difference is that 69% is before any sstate was
fetched, there was a 21% sstate match which meant X tasks were then
covered. Therefore after setscene ran, the number of completed tasks
would be higher and at 1574. We couldn't easily compute 1574 in
advance.

>Am I close?
> 
> I'm used to meta/classes/buildstats-summary.bbclass output
> (unfortunately after the build) which just shows 3 numbers per sstate
> covered task and this new summary is a bit confusing for me.

People wanted to know about coverage in advance of the build running
and we have a different set of numbers to work with unfortunately.
Statistics afterwards are much easier! :)

I'm open to better ways of presenting it to make it clearer what it
means but we don't really want to print too much either. It really is
meant so you can tell at a glance roughly how much work a build will
need to do.

Cheers,

Richard


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

Re: [OE-core] [RFC] Yocto Project Bug 12372 - Automate the execution of pTest with LAVA

[Yang Wang]

On 08/26/2018 10:04 PM, Otavio Salvador wrote:

On Fri, Aug 24, 2018 at 11:23 AM Wang, Yang (Young)
 wrote:

I see some good feedback from people mentioned they are working on similar 
solutions and should come out soon. We will continuously work on this ticket.

Did you consider using labgrid? It has a lot in common in current
infra we use in OEQA (ptest and like) and has nice capabilities to be
used locally and remotely.

Quickly had a look at labgrid, looks like it is using similar method to 
control devices with using configuration files, in this case, target 
controller is common, with using different type of YAML config files, it 
can control different devices. (Please correct me if I'm wrong.)


I think the key point of this ticket is to run Ptest on hardware devices 
automatically and make it as common as possible for Yocto. So, no matter 
using LAVA or labgrid, the devices being controlled need to be publicly 
accessible and maintained well.


Do you have examples similar to this ticket can share with us?

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

Re: [OE-core] [PATCH 1/5] mesa: Enable gallium-llvm on x86 and x86_64

[Andreas Müller]

On Mon, Aug 20, 2018 at 8:59 PM, Khem Raj  wrote:
> Signed-off-by: Khem Raj 
> ---
>  meta/recipes-graphics/cairo/cairo.inc | 3 ++-
>  meta/recipes-graphics/mesa/mesa.inc   | 3 +++
>  2 files changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/meta/recipes-graphics/cairo/cairo.inc 
> b/meta/recipes-graphics/cairo/cairo.inc
> index 20e0d2c92a..7347f223ff 100644
> --- a/meta/recipes-graphics/cairo/cairo.inc
> +++ b/meta/recipes-graphics/cairo/cairo.inc
> @@ -22,7 +22,8 @@ X11DEPENDS = "virtual/libx11 libsm libxrender libxext"
>  DEPENDS = "libpng fontconfig pixman glib-2.0 zlib"
>
>  PACKAGECONFIG ??= "${@bb.utils.contains('DISTRO_FEATURES', 'x11', 'x11 xcb', 
> '', d)} \
> -   ${@bb.utils.filter('DISTRO_FEATURES', 'directfb', d)}"
> +   ${@bb.utils.filter('DISTRO_FEATURES', 'directfb', d)} \
> +   ${@bb.utils.contains('DISTRO_FEATURES', 'x11 opengl', 'opengl', 
> '', d)}"
>
>  PACKAGECONFIG[x11] = "--with-x=yes -enable-xlib,--with-x=no 
> --disable-xlib,${X11DEPENDS}"
>  PACKAGECONFIG[xcb] = "--enable-xcb,--disable-xcb,libxcb"
> diff --git a/meta/recipes-graphics/mesa/mesa.inc 
> b/meta/recipes-graphics/mesa/mesa.inc
> index 5afd0db4b7..dd626d9f00 100644
^ I think this came in accidentaly and it breaks builds when adding
packageconfig glesv2:

| configure: error: use either --enable-gl=yes or --enable-glesv2=yes.
Not both at the same time.

Please check

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

Re: [OE-core] [oe-core][rocko][sumo][master][PATCH 2/2] base-files: respect PERSISTENT_LOG_DIR

[Ankur Tyagi]

On Sat, Aug 25, 2018 at 12:17 PM Khem Raj  wrote:
>
> On Fri, Aug 17, 2018 at 6:00 PM Ankur Tyagi  wrote:
> >
> > Respect PERSISTENT_LOG_DIR variable. In this way, if the user overrides
> > this variable to be e.g "/home/root/log", /var/log on the final image would
> > be a link pointing to /home/root/log on persistent storage.
> >
>
> I would suggest to stick with VOLATILE_BINDS

But this won't help with VOLATILE_LOG_DIR set as "no".
I think it is a common requirement to have persistent logging mounted
in a separate partition.
This patch makes it easy (hopefully) for the user to achieve the above
without any additional recipe.

>
> > Signed-off-by: Ankur Tyagi 
> > ---
> >  meta/recipes-core/base-files/base-files_3.0.14.bb | 6 +-
> >  1 file changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/meta/recipes-core/base-files/base-files_3.0.14.bb 
> > b/meta/recipes-core/base-files/base-files_3.0.14.bb
> > index 1c0863b..597fdaa 100644
> > --- a/meta/recipes-core/base-files/base-files_3.0.14.bb
> > +++ b/meta/recipes-core/base-files/base-files_3.0.14.bb
> > @@ -42,7 +42,7 @@ dirs755 = "/boot /dev ${base_bindir} ${base_sbindir} 
> > ${base_libdir} \
> > ${localstatedir}/backups ${localstatedir}/lib \
> > /sys ${localstatedir}/lib/misc ${localstatedir}/spool \
> > ${localstatedir}/volatile \
> > -   ${localstatedir}/${@'volatile/' if 
> > oe.types.boolean('${VOLATILE_LOG_DIR}') else ''}log \
> > +   ${@'${localstatedir}/volatile/log' if 
> > oe.types.boolean('${VOLATILE_LOG_DIR}') else '${PERSISTENT_LOG_DIR}' if 
> > d.getVar('PERSISTENT_LOG_DIR') else '${localstatedir}/log' } \
> > /home ${prefix}/src ${localstatedir}/local \
> > /media"
> >
> > @@ -106,6 +106,10 @@ do_install () {
> > ln -sf volatile/$d ${D}${localstatedir}/$d
> > done
> >
> > +   if [ ${@ oe.types.boolean('${VOLATILE_LOG_DIR}') } = False -a ! -z 
> > ${PERSISTENT_LOG_DIR} ]; then
> > +   ln -sf ${PERSISTENT_LOG_DIR} ${D}/${localstatedir}/log
> > +   fi
> > +
> > ln -snf ../run ${D}${localstatedir}/run
> > ln -snf ../run/lock ${D}${localstatedir}/lock
> >
> > --
> > 2.7.4
> >
> > --
> > ___
> > 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] pulseaudio: 11.1 -> 12.2

[Tanu Kaskinen]

Release notes for 12.0:
https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/12.0/

12.1 contains a few regression fixes:
https://lists.freedesktop.org/archives/pulseaudio-discuss/2018-July/030259.html

12.2 is just a fixup for the configure script brokenness in the 12.1 tarball.

qpaeq changed license from AGPL to LGPL, so now there's no AGPL licensed
code any more. This removes the excuse to not enable fftw support (i.e.
module-equalizer-sink and qpaeq). I'll enable fftw in a separate patch.

There's a new gsettings module that should be enabled, but I'll do
that in a separate patch. It's not particularly important, because the
module is only used by the paprefs GUI application that doesn't seem to
be packaged for OE at the moment.

Removed upstreamed patches:
0001-padsp-Make-it-compile-on-musl.patch
0001-memfd-wrappers-only-define-memfd_create-if-not-alrea.patch

License-Update: qpaeq changed license from AGPL to LGPL:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/commit/61217528a1cb5043ca3fa1051a73ad3268cfb3d8

Signed-off-by: Tanu Kaskinen 
---

According to the Yocto project status emails, YP 2.6 M3 Build Target is
today. If I recall correctly, that's the cutoff point for version
upgrades, so this patch may be late. If so, I apologize for dropping the
ball as a recipe maintainer. I can resend after 2.6 is out.

 .../pulseaudio/pulseaudio.inc | 15 ++--
 ...nly-define-memfd_create-if-not-alrea.patch | 66 -
 .../0001-padsp-Make-it-compile-on-musl.patch  | 70 ---
 ...{pulseaudio_11.1.bb => pulseaudio_12.2.bb} |  6 +-
 4 files changed, 7 insertions(+), 150 deletions(-)
 delete mode 100644 
meta/recipes-multimedia/pulseaudio/pulseaudio/0001-memfd-wrappers-only-define-memfd_create-if-not-alrea.patch
 delete mode 100644 
meta/recipes-multimedia/pulseaudio/pulseaudio/0001-padsp-Make-it-compile-on-musl.patch
 rename meta/recipes-multimedia/pulseaudio/{pulseaudio_11.1.bb => 
pulseaudio_12.2.bb} (53%)

diff --git a/meta/recipes-multimedia/pulseaudio/pulseaudio.inc 
b/meta/recipes-multimedia/pulseaudio/pulseaudio.inc
index 8189a569e1..f526690390 100644
--- a/meta/recipes-multimedia/pulseaudio/pulseaudio.inc
+++ b/meta/recipes-multimedia/pulseaudio/pulseaudio.inc
@@ -16,9 +16,6 @@ SECTION = "libs/multimedia"
 # The src/pulsecore/filter/ directory contains code under the 3-clause BSD
 # license.
 #
-# src/utils/qpaeq is licensed under AGPL. qpaeq is not installed by this
-# recipe, however, which is why AGPL is not mentioned in LICENSE.
-#
 # People who distribute PulseAudio binaries need to also consider that there
 # are some dependencies to GPL libraries. LGPL code that depends on GPL
 # libraries probably becomes effectively GPL-licensed (at compile-time? or at
@@ -47,16 +44,14 @@ SECTION = "libs/multimedia"
 # section 3, and therefore libdbus's GPL license doesn't affect PulseAudio.
 LICENSE = "LGPLv2.1+ & MIT & BSD-3-Clause"
 
-LIC_FILES_CHKSUM = "file://LICENSE;md5=a848e8d03f04976778eab2348b59ed2b \
+LIC_FILES_CHKSUM = "file://LICENSE;md5=0e5cd938de1a7a53ea5adac38cc10c39 \
 file://GPL;md5=4325afd396febcb659c36b49533135d4 \
 file://LGPL;md5=2d5025d4aa3495befef8f17206a5b0a1 \
-file://AGPL;md5=73f1eb20517c55bf9493b7dd6e480788 \
 
file://src/modules/echo-cancel/adrian-license.txt;md5=abbab006a561fbffccedf1c3531f34ab
 \
 
file://src/pulsecore/filter/LICENSE.WEBKIT;md5=49defbaffddf8c51faf606ff7fc3b1f7 
\
 
file://src/pulsecore/resampler.h;beginline=4;endline=21;md5=09794012ae16912c0270f3280cc8ff84
 \
 
file://src/modules/reserve.h;beginline=6;endline=28;md5=0e23094760367d51b6609750e9b31fbb
 \
 
file://src/pulsecore/rtkit.h;beginline=6;endline=29;md5=3f00ff966716ae0817c31576d1473528
 \
-
file://src/utils/qpaeq;beginline=2;endline=16;md5=7f62515a4762f0c3fc3d4201858bb964
 \
 
file://src/modules/echo-cancel/adrian-aec.h;beginline=3;endline=12;md5=d3ed4fad1c073f8b06f37495dc5d1026
 \
 
file://src/pulsecore/filter/biquad.h;beginline=1;endline=4;md5=6d46d1365206528a20137355924233c1
 \
 "
@@ -93,10 +88,6 @@ EXTRA_OECONF += "--without-soxr"
 # ddbd713293 without explaining why it was not made a PACKAGECONFIG item
 # instead. Oh well, let's keep it disabled until someone expresses some
 # interest in having it enabled.
-#
-# One nice thing about disabling this is that it also prevents qpaeq from
-# being installed, so we avoid adding AGPL to the list of licenses (nothing
-# else in PulseAudio is licensed under AGPL).
 EXTRA_OECONF += "--without-fftw"
 
 # The "adrian" echo canceller implementation has a non-standard license
@@ -106,6 +97,10 @@ EXTRA_OECONF += "--without-fftw"
 # very good anyway, better alternatives exist (such as the webrtc canceller).
 EXTRA_OECONF += "--disable-adrian-aec"
 
+# FIXME: The gsettings module is temporarily disabled, 

[OE-core] [PATCH resend 1/2] libarchive: CVE-2017-14501

[Jagadeesh Krishnanjanappa]

iso9660: validate directory record length

Affects libarchive <= 3.3.2

Signed-off-by: Jagadeesh Krishnanjanappa 
---
 .../libarchive/libarchive/CVE-2017-14501.patch | 79 ++
 .../libarchive/libarchive_3.3.2.bb |  1 +
 2 files changed, 80 insertions(+)
 create mode 100644 
meta/recipes-extended/libarchive/libarchive/CVE-2017-14501.patch

diff --git a/meta/recipes-extended/libarchive/libarchive/CVE-2017-14501.patch 
b/meta/recipes-extended/libarchive/libarchive/CVE-2017-14501.patch
new file mode 100644
index 000..1038102
--- /dev/null
+++ b/meta/recipes-extended/libarchive/libarchive/CVE-2017-14501.patch
@@ -0,0 +1,79 @@
+From f9569c086ff29259c73790db9cbf39fe8fb9d862 Mon Sep 17 00:00:00 2001
+From: John Starks 
+Date: Wed, 25 Jul 2018 12:16:34 -0700
+Subject: [PATCH] iso9660: validate directory record length
+
+CVE: CVE-2017-14501
+Upstream-Status: Backport 
[https://github.com/mmatuska/libarchive/commit/13e87dcd9c37b533127cceb9f3e1e5a38d95e784]
+
+Signed-off-by: Jagadeesh Krishnanjanappa 
+---
+ libarchive/archive_read_support_format_iso9660.c | 17 +++--
+ 1 file changed, 11 insertions(+), 6 deletions(-)
+
+diff --git a/libarchive/archive_read_support_format_iso9660.c 
b/libarchive/archive_read_support_format_iso9660.c
+index f01d37bf..089bb723 100644
+--- a/libarchive/archive_read_support_format_iso9660.c
 b/libarchive/archive_read_support_format_iso9660.c
+@@ -409,7 +409,8 @@ static int next_entry_seek(struct archive_read *, struct 
iso9660 *,
+   struct file_info **);
+ static struct file_info *
+   parse_file_info(struct archive_read *a,
+-  struct file_info *parent, const unsigned char *isodirrec);
++  struct file_info *parent, const unsigned char *isodirrec,
++  size_t reclen);
+ static intparse_rockridge(struct archive_read *a,
+   struct file_info *file, const unsigned char *start,
+   const unsigned char *end);
+@@ -1022,7 +1023,7 @@ read_children(struct archive_read *a, struct file_info 
*parent)
+   if (*(p + DR_name_len_offset) == 1
+   && *(p + DR_name_offset) == '\001')
+   continue;
+-  child = parse_file_info(a, parent, p);
++  child = parse_file_info(a, parent, p, b - p);
+   if (child == NULL) {
+   __archive_read_consume(a, skip_size);
+   return (ARCHIVE_FATAL);
+@@ -1112,7 +1113,7 @@ choose_volume(struct archive_read *a, struct iso9660 
*iso9660)
+*/
+   seenJoliet = iso9660->seenJoliet;/* Save flag. */
+   iso9660->seenJoliet = 0;
+-  file = parse_file_info(a, NULL, block);
++  file = parse_file_info(a, NULL, block, vd->size);
+   if (file == NULL)
+   return (ARCHIVE_FATAL);
+   iso9660->seenJoliet = seenJoliet;
+@@ -1144,7 +1145,7 @@ choose_volume(struct archive_read *a, struct iso9660 
*iso9660)
+   return (ARCHIVE_FATAL);
+   }
+   iso9660->seenJoliet = 0;
+-  file = parse_file_info(a, NULL, block);
++  file = parse_file_info(a, NULL, block, vd->size);
+   if (file == NULL)
+   return (ARCHIVE_FATAL);
+   iso9660->seenJoliet = seenJoliet;
+@@ -1749,7 +1750,7 @@ archive_read_format_iso9660_cleanup(struct archive_read 
*a)
+  */
+ static struct file_info *
+ parse_file_info(struct archive_read *a, struct file_info *parent,
+-const unsigned char *isodirrec)
++const unsigned char *isodirrec, size_t reclen)
+ {
+   struct iso9660 *iso9660;
+   struct file_info *file, *filep;
+@@ -1763,7 +1764,11 @@ parse_file_info(struct archive_read *a, struct 
file_info *parent,
+ 
+   iso9660 = (struct iso9660 *)(a->format->data);
+ 
+-  dr_len = (size_t)isodirrec[DR_length_offset];
++  if (reclen == 0 || reclen < (dr_len = 
(size_t)isodirrec[DR_length_offset])) {
++  archive_set_error(&a->archive, ARCHIVE_ERRNO_MISC,
++  "Invalid directory record length");
++  return (NULL);
++  }
+   name_len = (size_t)isodirrec[DR_name_len_offset];
+   location = archive_le32dec(isodirrec + DR_extent_offset);
+   fsize = toi(isodirrec + DR_size_offset, DR_size_size);
+-- 
+2.13.3
+
diff --git a/meta/recipes-extended/libarchive/libarchive_3.3.2.bb 
b/meta/recipes-extended/libarchive/libarchive_3.3.2.bb
index 3269716..e3d90b2 100644
--- a/meta/recipes-extended/libarchive/libarchive_3.3.2.bb
+++ b/meta/recipes-extended/libarchive/libarchive_3.3.2.bb
@@ -37,6 +37,7 @@ SRC_URI = 
"http://libarchive.org/downloads/libarchive-${PV}.tar.gz \
file://CVE-2017-14502.patch \
file://non-recursive-extract-and-list.patch \
file://CVE-2017-14503.patch \
+   file://CVE-2017-14501.patch \

[OE-core] [PATCH resend 2/2] libcgroup: CVE-2018-14348

[Jagadeesh Krishnanjanappa]

Affects libcgroup <= 0.41

Signed-off-by: Jagadeesh Krishnanjanappa 
---
 .../libcgroup/libcgroup/CVE-2018-14348.patch   | 37 ++
 meta/recipes-core/libcgroup/libcgroup_0.41.bb  |  3 +-
 2 files changed, 39 insertions(+), 1 deletion(-)
 create mode 100644 meta/recipes-core/libcgroup/libcgroup/CVE-2018-14348.patch

diff --git a/meta/recipes-core/libcgroup/libcgroup/CVE-2018-14348.patch 
b/meta/recipes-core/libcgroup/libcgroup/CVE-2018-14348.patch
new file mode 100644
index 000..d133703
--- /dev/null
+++ b/meta/recipes-core/libcgroup/libcgroup/CVE-2018-14348.patch
@@ -0,0 +1,37 @@
+From 0d88b73d189ea3440ccaab00418d6469f76fa590 Mon Sep 17 00:00:00 2001
+From: Michal Hocko 
+Date: Wed, 18 Jul 2018 11:24:29 +0200
+Subject: [PATCH] cgrulesengd: remove umask(0)
+
+One of our partners has noticed that cgred daemon is creating a log file
+(/var/log/cgred) with too wide permissions (0666) and that is seen as
+a security bug because an untrusted user can write to otherwise
+restricted area. CVE-2018-14348 has been assigned to this issue.
+
+CVE: CVE-2018-14348
+Upstream-Status: Backport 
[https://sourceforge.net/p/libcg/libcg/ci/0d88b73d189ea3440ccaab00418d6469f76fa590]
+
+Signed-off-by: Michal Hocko 
+Acked-by: Balbir Singh 
+Signed-off-by: Jagadeesh Krishnanjanappa 
+---
+ src/daemon/cgrulesengd.c | 3 ---
+ 1 file changed, 3 deletions(-)
+
+diff --git a/src/daemon/cgrulesengd.c b/src/daemon/cgrulesengd.c
+index ea51f11..0d288f3 100644
+--- a/src/daemon/cgrulesengd.c
 b/src/daemon/cgrulesengd.c
+@@ -889,9 +889,6 @@ int cgre_start_daemon(const char *logp, const int logf,
+   } else if (pid > 0) {
+   exit(EXIT_SUCCESS);
+   }
+-
+-  /* Change the file mode mask. */
+-  umask(0);
+   } else {
+   flog(LOG_DEBUG, "Not using daemon mode\n");
+   pid = getpid();
+-- 
+2.13.3
+
diff --git a/meta/recipes-core/libcgroup/libcgroup_0.41.bb 
b/meta/recipes-core/libcgroup/libcgroup_0.41.bb
index 7ddc81e..92d7261 100644
--- a/meta/recipes-core/libcgroup/libcgroup_0.41.bb
+++ b/meta/recipes-core/libcgroup/libcgroup_0.41.bb
@@ -11,7 +11,8 @@ inherit autotools pkgconfig
 
 DEPENDS = "bison-native flex-native"
 
-SRC_URI = 
"${SOURCEFORGE_MIRROR}/project/libcg/${BPN}/v0.41/${BPN}-${PV}.tar.bz2"
+SRC_URI = 
"${SOURCEFORGE_MIRROR}/project/libcg/${BPN}/v0.41/${BPN}-${PV}.tar.bz2 \
+   file://CVE-2018-14348.patch"
 SRC_URI_append_libc-musl = " file://musl-decls-compat.patch"
 
 SRC_URI[md5sum] = "3dea9d50b8a5b73ff0bf1cdcb210f63f"
-- 
2.7.4

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

Re: [OE-core] [Q&A] "http://sources.openembedded.org" is unavailable

[Tomohiro Komagata]

Thanks!
Today, I could confirm that the server is available.

On 2018/08/25 18:15, Martin Jansa wrote:

The server which is hosting this is I believe in transit and should be back 
online in couple days.

On Sat, Aug 25, 2018 at 10:50 AM Tomohiro Komagata mailto:tomohiro.komagata...@gmail.com>> wrote:

Hi all,

In this week, I have failed to bitbake,
because "http://sources.openembedded.org"; is unavailable and it occurs the 
fetch error.

Does anyone have any information ?
When will its server be available ?

Best regards,
　T.Komagata

-- 
___

Openembedded-core mailing list
Openembedded-core@lists.openembedded.org 

http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

Re: [OE-core] [PATCH] distutils3.bbclass: improve error messages

[Hongxu Jia]

1. There are other tasks have the similar bbfatal_log invoking, such as
distutils3_stage_all/distutils3_do_install, why not update them all.

2. Would you please update python2's in distutils.bbclass also?

//Hongxu

On 2018年08月27日 17:54, Jens Rehsack wrote:

For non-python developers it's difficult to identify where start
searching in case of errors. Fixing and marking the string to
grep for might help finding some root causes of issues slightly
quicker.

Signed-off-by: Jens Rehsack 
---
  meta/classes/distutils3.bbclass | 4 ++--
  1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/classes/distutils3.bbclass b/meta/classes/distutils3.bbclass
index 1d0c54a513..9e31505f0c 100644
--- a/meta/classes/distutils3.bbclass
+++ b/meta/classes/distutils3.bbclass
@@ -23,14 +23,14 @@ distutils3_do_compile() {
  STAGING_LIBDIR=${STAGING_LIBDIR} \
  ${STAGING_BINDIR_NATIVE}/${PYTHON_PN}-native/${PYTHON_PN} setup.py \
  build ${DISTUTILS_BUILD_ARGS} || \
-bbfatal_log "${PYTHON_PN} setup.py build_ext execution failed."
+bbfatal_log "'${PYTHON_PN} setup.py build ${DISTUTILS_BUILD_ARGS}' 
execution failed."
  }
  distutils3_do_compile[vardepsexclude] = "MACHINE"
  
  distutils3_stage_headers() {

  install -d ${STAGING_DIR_HOST}${PYTHON_SITEPACKAGES_DIR}
  ${STAGING_BINDIR_NATIVE}/${PYTHON_PN}-native/${PYTHON_PN} setup.py 
install_headers ${DISTUTILS_STAGE_HEADERS_ARGS} || \
-bbfatal_log "${PYTHON_PN} setup.py install_headers execution failed."
+bbfatal_log "'${PYTHON_PN} setup.py install_headers' execution failed."
  }
  distutils3_stage_headers[vardepsexclude] = "MACHINE"
  



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

[OE-core] Yocto Project Unassigned Bugs - Help Needed

[Jolley, Stephen K]

All,



The triage team meets weekly and does its best to handle the bugs reported into 
the bugzilla. The number of people attending that meeting has fallen, as have 
the number of people available to help fix bugs. One of the things we hear 
users report is they don't know how to help. We (the triage team) are therefore 
going to start reporting out the currently 313 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out 
with these.



Bugs are split into two types, "true bugs" where things don't work as they 
should and "enhancements" which are features we'd want to add to the system.



There are also roughly three different "priority" classes right now, "2.6", 
"2.99" and "Future", the more pressing/urgent issues being in "2.6".



Please review this link and if a bug is something you would be able to help 
with either take ownership of the bug, or send me (stephen.k.jol...@intel.com) 
an e-mail with the bug number you would like and I will assign it to you 
(please make sure you have a bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*Cell:(208) 244-4460
* Email: stephen.k.jol...@intel.com

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

Re: [OE-core] [PATCH] cmake: add CMAKE_SYSROOT to generated toolchain file

[Khem Raj]

since it was staged in oe-core/master-next, it got into my
testing queue and is causing several recipes FTBFS

see

http://errors.yoctoproject.org/Errors/Build/66877/
On Fri, Aug 24, 2018 at 5:34 AM Pascal Bach  wrote:
>
> This already got fixed in the toolchain file that is used during development
> in 
> https://github.com/openembedded/openembedded-core/commit/cb42802f2fe1760f894a435b07286bca3a220364
>
> The toolchain file generated by the cmake.bbclass however does not set
> CMAKE_SYSROOT. Under certain circumstances this also leads to the error:
> `"stdlib.h: No such file or directory #include_next "`
> during the build of a recipe.
>
> An example where this accured was during the upgrade of the Apache Thrift
> recipe in meta-openembedded to 0.11.0. With this change the build works out of
> the box.
>
> CMAKE_SYSROOT must only be set when crosscompiling, otherwise it will 
> interfere
> with the native compiler headers.
>
> Signed-off-by: Pascal Bach 
> ---
>  meta/classes/cmake.bbclass | 5 +
>  1 file changed, 5 insertions(+)
>
> diff --git a/meta/classes/cmake.bbclass b/meta/classes/cmake.bbclass
> index fd40a9863e..251ddd9afe 100644
> --- a/meta/classes/cmake.bbclass
> +++ b/meta/classes/cmake.bbclass
> @@ -64,9 +64,12 @@ def map_target_arch_to_uname_arch(target_arch):
>  return "ppc64"
>  return target_arch
>
> +
>  cmake_do_generate_toolchain_file() {
> if [ "${BUILD_SYS}" = "${HOST_SYS}" ]; then
> cmake_crosscompiling="set( CMAKE_CROSSCOMPILING FALSE )"
> +   else
> +   cmake_sysroot="set( CMAKE_SYSROOT \"${RECIPE_SYSROOT}\" )"
> fi
> cat > ${WORKDIR}/toolchain.cmake <  # CMake system name must be something like "Linux".
> @@ -95,6 +98,8 @@ set( CMAKE_FIND_ROOT_PATH_MODE_PROGRAM 
> ${OECMAKE_FIND_ROOT_PATH_MODE_PROGRAM} )
>  set( CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY )
>  set( CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY )
>
> +$cmake_sysroot
> +
>  # Use qt.conf settings
>  set( ENV{QT_CONF_PATH} ${WORKDIR}/qt.conf )
>
> --
> 2.11.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

[OE-core] [PATCH 3/3] image_types_wic: Add variable WIC_EXTENSION

[Alexandru Vasiu]

Used to specify what extention will have the image file which
is created using wic. The default value is wic. For creating an
ISO image, WIC_EXTENSION will be iso.

Signed-off-by: Alexandru Vasiu 
---
 meta/classes/image.bbclass   | 2 ++
 meta/classes/image_types_wic.bbclass | 3 ++-
 2 files changed, 4 insertions(+), 1 deletion(-)

diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
index 024d2d4c96..c6833a6770 100644
--- a/meta/classes/image.bbclass
+++ b/meta/classes/image.bbclass
@@ -607,6 +607,8 @@ python create_symlinks() {
 if not link_name:
 return
 for type in subimages:
+if type == 'wic':
+type = d.getVar('WIC_EXTENSION')
 dst = os.path.join(deploy_dir, link_name + "." + type)
 src = img_name + imgsuffix + type
 if os.path.exists(os.path.join(deploy_dir, src)):
diff --git a/meta/classes/image_types_wic.bbclass 
b/meta/classes/image_types_wic.bbclass
index 5b40a9e919..77cde5763c 100644
--- a/meta/classes/image_types_wic.bbclass
+++ b/meta/classes/image_types_wic.bbclass
@@ -9,6 +9,7 @@ WKS_FILE ??= "${IMAGE_BASENAME}.${MACHINE}.wks"
 WKS_FILES ?= "${WKS_FILE} ${IMAGE_BASENAME}.wks"
 WKS_SEARCH_PATH ?= "${THISDIR}:${@':'.join('%s/wic' % p for p in 
'${BBPATH}'.split(':'))}:${@':'.join('%s/scripts/lib/wic/canned-wks' % l for l 
in '${BBPATH}:${COREBASE}'.split(':'))}"
 WKS_FULL_PATH = "${@wks_search(d.getVar('WKS_FILES').split(), 
d.getVar('WKS_SEARCH_PATH')) or ''}"
+WIC_EXTENSION ??= "wic"
 
 def wks_search(files, search_path):
 for f in files:
@@ -30,7 +31,7 @@ IMAGE_CMD_wic () {
fi
 
BUILDDIR="${TOPDIR}" wic create "$wks" --vars 
"${STAGING_DIR}/${MACHINE}/imgdata/" -e "${IMAGE_BASENAME}" -o "$out/" 
${WIC_CREATE_EXTRA_ARGS}
-   mv "$out/$(basename "${wks%.wks}")"*.direct 
"$out${IMAGE_NAME_SUFFIX}.wic"
+   mv "$out/$(basename "${wks%.wks}")"*.direct 
"$out${IMAGE_NAME_SUFFIX}.${WIC_EXTENSION}"
rm -rf "$out/"
 }
 IMAGE_CMD_wic[vardepsexclude] = "WKS_FULL_PATH WKS_FILES TOPDIR"
-- 
2.18.0

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

[OE-core] [PATCH 2/3] bind: improve reproducibility

[Hongxu Jia]

- Tweak var-DST_OPENSSL_LIBS assignment in configure.in, it is
  helpful to fix build path issue in isc-config.sh

- `named/lwresd -V' and start log hide build options which expose
  build path directories.

Signed-off-by: Hongxu Jia 
---
 ...igure.in-remove-useless-L-use_openssl-lib.patch | 32 
 ...lwresd-V-and-start-log-hide-build-options.patch | 34 ++
 meta/recipes-connectivity/bind/bind_9.11.4.bb  |  2 ++
 3 files changed, 68 insertions(+)
 create mode 100644 
meta/recipes-connectivity/bind/bind/0001-configure.in-remove-useless-L-use_openssl-lib.patch
 create mode 100644 
meta/recipes-connectivity/bind/bind/0001-named-lwresd-V-and-start-log-hide-build-options.patch

diff --git 
a/meta/recipes-connectivity/bind/bind/0001-configure.in-remove-useless-L-use_openssl-lib.patch
 
b/meta/recipes-connectivity/bind/bind/0001-configure.in-remove-useless-L-use_openssl-lib.patch
new file mode 100644
index 000..871bb2a
--- /dev/null
+++ 
b/meta/recipes-connectivity/bind/bind/0001-configure.in-remove-useless-L-use_openssl-lib.patch
@@ -0,0 +1,32 @@
+From 950867d9fd3f690e271c8c807b6eed144b2935b2 Mon Sep 17 00:00:00 2001
+From: Hongxu Jia 
+Date: Mon, 27 Aug 2018 15:00:51 +0800
+Subject: [PATCH] configure.in: remove useless `-L$use_openssl/lib'
+
+Since `--with-openssl=${STAGING_DIR_HOST}${prefix}' is used in bind recipe,
+the `-L$use_openssl/lib' has a hardcoded suffix, removing it is harmless
+and helpful for clean up host build path in isc-config.sh
+
+Upstream-Status: Inappropriate [oe-core specific]
+
+Signed-off-by: Hongxu Jia 
+---
+ configure.in | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/configure.in b/configure.in
+index 54efc55..76ac0eb 100644
+--- a/configure.in
 b/configure.in
+@@ -1691,7 +1691,7 @@ If you don't want OpenSSL, use --without-openssl])
+   fi
+   ;;
+   *)
+-  DST_OPENSSL_LIBS="-L$use_openssl/lib -lcrypto"
++  DST_OPENSSL_LIBS="-lcrypto"
+   ;;
+   esac
+   fi
+-- 
+2.7.4
+
diff --git 
a/meta/recipes-connectivity/bind/bind/0001-named-lwresd-V-and-start-log-hide-build-options.patch
 
b/meta/recipes-connectivity/bind/bind/0001-named-lwresd-V-and-start-log-hide-build-options.patch
new file mode 100644
index 000..75908aa
--- /dev/null
+++ 
b/meta/recipes-connectivity/bind/bind/0001-named-lwresd-V-and-start-log-hide-build-options.patch
@@ -0,0 +1,34 @@
+From a3af4a405baf5ff582e82aaba392dd9667d94bdc Mon Sep 17 00:00:00 2001
+From: Hongxu Jia 
+Date: Mon, 27 Aug 2018 21:24:20 +0800
+Subject: [PATCH] `named/lwresd -V' and start log hide build options
+
+The build options expose build path directories, so hide them.
+[snip]
+$ named -V
+|built by make with *** (options are hidden)
+[snip]
+
+Upstream-Status: Inappropriate [oe-core specific]
+
+Signed-off-by: Hongxu Jia 
+---
+ bin/named/include/named/globals.h | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/bin/named/include/named/globals.h 
b/bin/named/include/named/globals.h
+index ba3457e..7741da7 100644
+--- a/bin/named/include/named/globals.h
 b/bin/named/include/named/globals.h
+@@ -68,7 +68,7 @@ EXTERN const char *  ns_g_version
INIT(VERSION);
+ EXTERN const char *   ns_g_productINIT(PRODUCT);
+ EXTERN const char *   ns_g_descriptionINIT(DESCRIPTION);
+ EXTERN const char *   ns_g_srcid  INIT(SRCID);
+-EXTERN const char *   ns_g_configargs INIT(CONFIGARGS);
++EXTERN const char *   ns_g_configargs INIT("*** (options are 
hidden)");
+ EXTERN const char *   ns_g_builderINIT(BUILDER);
+ EXTERN in_port_t  ns_g_port   INIT(0);
+ EXTERN isc_dscp_t ns_g_dscp   INIT(-1);
+-- 
+2.7.4
+
diff --git a/meta/recipes-connectivity/bind/bind_9.11.4.bb 
b/meta/recipes-connectivity/bind/bind_9.11.4.bb
index 7522fdb..d27068c 100644
--- a/meta/recipes-connectivity/bind/bind_9.11.4.bb
+++ b/meta/recipes-connectivity/bind/bind_9.11.4.bb
@@ -17,6 +17,8 @@ SRC_URI = 
"https://ftp.isc.org/isc/bind9/${PV}/${BPN}-${PV}.tar.gz \
file://bind-ensure-searching-for-json-headers-searches-sysr.patch \
file://0001-gen.c-extend-DIRNAMESIZE-from-256-to-512.patch \
file://0001-lib-dns-gen.c-fix-too-long-error.patch \
+   file://0001-configure.in-remove-useless-L-use_openssl-lib.patch \
+   file://0001-named-lwresd-V-and-start-log-hide-build-options.patch \
 "
 
 SRC_URI[md5sum] = "9b4834d78f30cdb796ce437262272a36"
-- 
2.7.4

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

[OE-core] [PATCH 1/3] isoimage-isohybrid: Fix creating initrd.cpio

[Alexandru Vasiu]

Only bsdcpio works with numbers for option -R to specify user:group,
while GNU cpio doesn't. Debian use GNU cpio so without this change,
you cannot create ISO images without installing bsdcpio.

Signed-off-by: Alexandru Vasiu 
---
 scripts/lib/wic/plugins/source/isoimage-isohybrid.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/lib/wic/plugins/source/isoimage-isohybrid.py 
b/scripts/lib/wic/plugins/source/isoimage-isohybrid.py
index 0d4f50d1f7..4a0a57ef9e 100644
--- a/scripts/lib/wic/plugins/source/isoimage-isohybrid.py
+++ b/scripts/lib/wic/plugins/source/isoimage-isohybrid.py
@@ -191,7 +191,7 @@ class IsoImagePlugin(SourcePlugin):
 else:
 raise WicError("Couldn't find or build initrd, exiting.")
 
-exec_cmd("cd %s && find . | cpio -o -H newc -R +0:+0 
>./initrd.cpio " \
+exec_cmd("cd %s && find . | cpio -o -H newc -R root:root 
>./initrd.cpio " \
 % initrd_dir, as_shell=True)
 exec_cmd("gzip -f -9 -c %s/initrd.cpio > %s" \
 % (cr_workdir, initrd), as_shell=True)
-- 
2.18.0

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

[OE-core] [PATCH 3/3] ruby: improve reproducibility

[Hongxu Jia]

Find out rbconfig.rb and created.rid from ${B}/.installed.list
and remove build host directories

- For rbconfig.rb, parse it like python's _sysconfigdata.py
[snip rbconfig.rb]
 26   CONFIG["INSTALL"] = 'install -c'
[snip rbconfig.rb]

- For created.rid, it records file created time, just strip ${WORKDIR} prefix.
[snip created.rid]
840 /ruby-2.5.1/doc/maintainers.rdocFri, 22 Dec 2017 23:08:05 +
[snip created.rid]

Signed-off-by: Hongxu Jia 
---
 meta/recipes-devtools/ruby/ruby_2.5.1.bb | 20 
 1 file changed, 20 insertions(+)

diff --git a/meta/recipes-devtools/ruby/ruby_2.5.1.bb 
b/meta/recipes-devtools/ruby/ruby_2.5.1.bb
index af2739a..1197323 100644
--- a/meta/recipes-devtools/ruby/ruby_2.5.1.bb
+++ b/meta/recipes-devtools/ruby/ruby_2.5.1.bb
@@ -35,6 +35,26 @@ do_install() {
 oe_runmake 'DESTDIR=${D}' install
 }
 
+do_install_append_class-target () {
+# Find out rbconfig.rb from .installed.list
+rbconfig_rb=`grep rbconfig.rb ${B}/.installed.list`
+# Remove build host directories
+sed -i -e 's:--sysroot=${STAGING_DIR_TARGET}::g' \
+   -e s:'--with-libtool-sysroot=${STAGING_DIR_TARGET}'::g \
+   -e 's|${DEBUG_PREFIX_MAP}||g' \
+   -e 's:${HOSTTOOLS_DIR}/::g' \
+   -e 's:${RECIPE_SYSROOT_NATIVE}::g' \
+   -e 's:${RECIPE_SYSROOT}::g' \
+   -e 's:${BASE_WORKDIR}/${MULTIMACH_TARGET_SYS}::g' \
+${D}$rbconfig_rb
+
+# Find out created.rid from .installed.list
+created_rid=`grep created.rid ${B}/.installed.list`
+# Remove build host directories
+sed -i -e 's:${WORKDIR}::g' ${D}$created_rid
+
+}
+
 PACKAGES =+ "${PN}-ri-docs ${PN}-rdoc"
 
 SUMMARY_${PN}-ri-docs = "ri (Ruby Interactive) documentation for the Ruby 
standard library"
-- 
2.7.4

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

[OE-core] [PATCH 1/3] nss :improve reproducibility

[Hongxu Jia]

- Explicitly requests the newer database `sql:' rather than
  retrieved from NSS_DEFAULT_DB_TYPE

- Removes build path prefix from pkcs11.txt

Refers certutil manual:
[certutil manual]
-d [prefix]directory
 Specify the database directory containing the certificate and key database 
files.
 certutil supports two types of databases: the legacy security databases 
(cert8.db,
  key3.db, and secmod.db) and new SQLite databases (cert9.db, key4.db, and 
pkcs11.txt).

 NSS recognizes the following prefixes:
  sql: requests the newer database
  dbm: requests the legacy database
 If no prefix is specified the default type is retrieved from 
NSS_DEFAULT_DB_TYPE.
 If NSS_DEFAULT_DB_TYPE is not set then dbm: is the default.
[certutil manual]

Signed-off-by: Hongxu Jia 
---
 meta/recipes-support/nss/nss_3.38.bb | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-support/nss/nss_3.38.bb 
b/meta/recipes-support/nss/nss_3.38.bb
index f3e5170..904b621 100644
--- a/meta/recipes-support/nss/nss_3.38.bb
+++ b/meta/recipes-support/nss/nss_3.38.bb
@@ -215,9 +215,11 @@ do_install_append_class-target() {
 # Create a blank certificate
 mkdir -p ${D}${sysconfdir}/pki/nssdb/
 touch ./empty_password
-certutil -N -d ${D}${sysconfdir}/pki/nssdb/ -f ./empty_password
+certutil -N -d sql:${D}${sysconfdir}/pki/nssdb/ -f ./empty_password
 chmod 644 ${D}${sysconfdir}/pki/nssdb/*.db
 rm ./empty_password
+# Remove build path prefix
+sed -i "s:${D}::g"  ${D}${sysconfdir}/pki/nssdb/pkcs11.txt
 }
 
 PACKAGE_WRITE_DEPS += "nss-native"
-- 
2.7.4

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

[OE-core] [PATCH 2/3] isoimage-isohybrid: Fix variable names

[Alexandru Vasiu]

initrd.cpio is created in initrd_dir, not in cr_workdir. Gzip will
let initrd.cpio uncompressed if the path is not found.

Also, grub_image variable doesn't exist, grub_src_image should
be used instead.

Signed-off-by: Alexandru Vasiu 
---
 scripts/lib/wic/plugins/source/isoimage-isohybrid.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/scripts/lib/wic/plugins/source/isoimage-isohybrid.py 
b/scripts/lib/wic/plugins/source/isoimage-isohybrid.py
index 4a0a57ef9e..25a695da17 100644
--- a/scripts/lib/wic/plugins/source/isoimage-isohybrid.py
+++ b/scripts/lib/wic/plugins/source/isoimage-isohybrid.py
@@ -194,7 +194,7 @@ class IsoImagePlugin(SourcePlugin):
 exec_cmd("cd %s && find . | cpio -o -H newc -R root:root 
>./initrd.cpio " \
 % initrd_dir, as_shell=True)
 exec_cmd("gzip -f -9 -c %s/initrd.cpio > %s" \
-% (cr_workdir, initrd), as_shell=True)
+% (initrd_dir, initrd), as_shell=True)
 shutil.rmtree(initrd_dir)
 
 return initrd
@@ -317,7 +317,7 @@ class IsoImagePlugin(SourcePlugin):
 grub_src = os.path.join(deploy_dir, grub_src_image)
 if not os.path.exists(grub_src):
 raise WicError("Grub loader %s is not found in %s. "
-   "Please build grub-efi first" % 
(grub_image, deploy_dir))
+   "Please build grub-efi first" % 
(grub_src_image, deploy_dir))
 shutil.copy(grub_src, grub_target)
 
 if not os.path.isfile(os.path.join(target_dir, "boot.cfg")):
-- 
2.18.0

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

Re: [OE-core] [PATCH 10/12] linux-yocto: introduce 4.18 recipes

[Khem Raj]

On Mon, Aug 27, 2018 at 7:43 AM Bruce Ashfield
 wrote:
>
> Sweet. I just saw mine break as well.
>
> Were you going to do the uprev to meta-oe, or did you want me to
> send a patch ?
>

I have a local patch already.

> Bruce
>
> On 2018-08-27 10:20 AM, Khem Raj wrote:
> > uprev fixes it even on mips
> > On Mon, Aug 27, 2018 at 5:59 AM Bruce Ashfield
> >  wrote:
> >>
> >> On 2018-08-27 2:58 AM, Khem Raj wrote:
> >>> There is one failure on meta-openembedded seen
> >>
> >> Not bad!
> >>
> >> I'll fire off a build and see what happens here. I'm guessing that
> >> an uprev is the answer .. but you never know with mips :D
> >>
> >> Bruce
> >>
> >>>
> >>> http://errors.yoctoproject.org/Errors/Details/187942/
> >>> On Fri, Aug 24, 2018 at 8:01 AM Bruce Ashfield
> >>>  wrote:
> 
>  Introducing the 4.18 kernel as the 'newest' kernel for the oe core
>  release.
> 
>  This update includes tweaked configs, carried forward BSPs, features
>  (aufs, yaffs2, preempt-rt) and has been tested on all arches for boot
>  and performance sanity.
> 
>  Signed-off-by: Bruce Ashfield 
>  ---
> meta/recipes-kernel/linux/linux-yocto-rt_4.18.bb   | 43 
>  +++
> meta/recipes-kernel/linux/linux-yocto-tiny_4.18.bb | 29 +
> meta/recipes-kernel/linux/linux-yocto_4.18.bb  | 48 
>  ++
> 3 files changed, 120 insertions(+)
> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_4.18.bb
> create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_4.18.bb
> create mode 100644 meta/recipes-kernel/linux/linux-yocto_4.18.bb
> 
>  diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.18.bb 
>  b/meta/recipes-kernel/linux/linux-yocto-rt_4.18.bb
>  new file mode 100644
>  index ..f740b1dcd892
>  --- /dev/null
>  +++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.18.bb
>  @@ -0,0 +1,43 @@
>  +KBRANCH ?= "v4.18/standard/preempt-rt/base"
>  +
>  +require recipes-kernel/linux/linux-yocto.inc
>  +
>  +# Skip processing of this recipe if it is not explicitly specified as 
>  the
>  +# PREFERRED_PROVIDER for virtual/kernel. This avoids errors when trying
>  +# to build multiple virtual/kernel providers, e.g. as dependency of
>  +# core-image-rt-sdk, core-image-rt.
>  +python () {
>  +if d.getVar("KERNEL_PACKAGE_NAME") == "kernel" and 
>  d.getVar("PREFERRED_PROVIDER_virtual/kernel") != "linux-yocto-rt":
>  +raise bb.parse.SkipRecipe("Set 
>  PREFERRED_PROVIDER_virtual/kernel to linux-yocto-rt to enable it")
>  +}
>  +
>  +SRCREV_machine ?= "8a990322beb7b3aa5a06d7bd630f819b70911587"
>  +SRCREV_meta ?= "1f78e20cc98dd46637c0beb6007214fb3650992c"
>  +
>  +SRC_URI = 
>  "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine
>   \
>  +   
>  git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.18;destsuffix=${KMETA}"
>  +
>  +LINUX_VERSION ?= "4.18.3"
>  +
>  +LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
>  +
>  +DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', 
>  d)}"
>  +DEPENDS += "openssl-native util-linux-native"
>  +
>  +PV = "${LINUX_VERSION}+git${SRCPV}"
>  +
>  +KMETA = "kernel-meta"
>  +KCONF_BSP_AUDIT_LEVEL = "2"
>  +
>  +LINUX_KERNEL_TYPE = "preempt-rt"
>  +
>  +COMPATIBLE_MACHINE = "(qemux86|qemux86-64|qemuarm|qemuppc|qemumips)"
>  +
>  +KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
>  +
>  +# Functionality flags
>  +KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc 
>  features/taskstats/taskstats.scc"
>  +KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
>  +KERNEL_FEATURES_append_qemuall=" cfg/virtio.scc"
>  +KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
>  +KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc"
>  diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.18.bb 
>  b/meta/recipes-kernel/linux/linux-yocto-tiny_4.18.bb
>  new file mode 100644
>  index ..1f0b35ec25ec
>  --- /dev/null
>  +++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.18.bb
>  @@ -0,0 +1,29 @@
>  +KBRANCH ?= "v4.18/standard/tiny/common-pc"
>  +LINUX_KERNEL_TYPE = "tiny"
>  +KCONFIG_MODE = "--allnoconfig"
>  +
>  +require recipes-kernel/linux/linux-yocto.inc
>  +
>  +LINUX_VERSION ?= "4.18.3"
>  +LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
>  +
>  +DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', 
>  d)}"
>  +DEPENDS += "openssl-native util-linux-native"
>  +
>  +KMETA = "kernel-meta"
>  +KCONF_BSP_AUDIT_LEVEL = "2"
>  +
>  +SRCREV_machine ?= "eba03655e8e43

Re: [OE-core] [PATCH 10/12] linux-yocto: introduce 4.18 recipes

[Bruce Ashfield]

Sweet. I just saw mine break as well.

Were you going to do the uprev to meta-oe, or did you want me to
send a patch ?

Bruce

On 2018-08-27 10:20 AM, Khem Raj wrote:

uprev fixes it even on mips
On Mon, Aug 27, 2018 at 5:59 AM Bruce Ashfield
 wrote:


On 2018-08-27 2:58 AM, Khem Raj wrote:

There is one failure on meta-openembedded seen


Not bad!

I'll fire off a build and see what happens here. I'm guessing that
an uprev is the answer .. but you never know with mips :D

Bruce



http://errors.yoctoproject.org/Errors/Details/187942/
On Fri, Aug 24, 2018 at 8:01 AM Bruce Ashfield
 wrote:


Introducing the 4.18 kernel as the 'newest' kernel for the oe core
release.

This update includes tweaked configs, carried forward BSPs, features
(aufs, yaffs2, preempt-rt) and has been tested on all arches for boot
and performance sanity.

Signed-off-by: Bruce Ashfield 
---
   meta/recipes-kernel/linux/linux-yocto-rt_4.18.bb   | 43 +++
   meta/recipes-kernel/linux/linux-yocto-tiny_4.18.bb | 29 +
   meta/recipes-kernel/linux/linux-yocto_4.18.bb  | 48 
++
   3 files changed, 120 insertions(+)
   create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_4.18.bb
   create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_4.18.bb
   create mode 100644 meta/recipes-kernel/linux/linux-yocto_4.18.bb

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.18.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.18.bb
new file mode 100644
index ..f740b1dcd892
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.18.bb
@@ -0,0 +1,43 @@
+KBRANCH ?= "v4.18/standard/preempt-rt/base"
+
+require recipes-kernel/linux/linux-yocto.inc
+
+# Skip processing of this recipe if it is not explicitly specified as the
+# PREFERRED_PROVIDER for virtual/kernel. This avoids errors when trying
+# to build multiple virtual/kernel providers, e.g. as dependency of
+# core-image-rt-sdk, core-image-rt.
+python () {
+if d.getVar("KERNEL_PACKAGE_NAME") == "kernel" and 
d.getVar("PREFERRED_PROVIDER_virtual/kernel") != "linux-yocto-rt":
+raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to 
linux-yocto-rt to enable it")
+}
+
+SRCREV_machine ?= "8a990322beb7b3aa5a06d7bd630f819b70911587"
+SRCREV_meta ?= "1f78e20cc98dd46637c0beb6007214fb3650992c"
+
+SRC_URI = 
"git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
+   
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.18;destsuffix=${KMETA}"
+
+LINUX_VERSION ?= "4.18.3"
+
+LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
+
+DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
+DEPENDS += "openssl-native util-linux-native"
+
+PV = "${LINUX_VERSION}+git${SRCPV}"
+
+KMETA = "kernel-meta"
+KCONF_BSP_AUDIT_LEVEL = "2"
+
+LINUX_KERNEL_TYPE = "preempt-rt"
+
+COMPATIBLE_MACHINE = "(qemux86|qemux86-64|qemuarm|qemuppc|qemumips)"
+
+KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
+
+# Functionality flags
+KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc 
features/taskstats/taskstats.scc"
+KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
+KERNEL_FEATURES_append_qemuall=" cfg/virtio.scc"
+KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
+KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.18.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_4.18.bb
new file mode 100644
index ..1f0b35ec25ec
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.18.bb
@@ -0,0 +1,29 @@
+KBRANCH ?= "v4.18/standard/tiny/common-pc"
+LINUX_KERNEL_TYPE = "tiny"
+KCONFIG_MODE = "--allnoconfig"
+
+require recipes-kernel/linux/linux-yocto.inc
+
+LINUX_VERSION ?= "4.18.3"
+LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
+
+DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
+DEPENDS += "openssl-native util-linux-native"
+
+KMETA = "kernel-meta"
+KCONF_BSP_AUDIT_LEVEL = "2"
+
+SRCREV_machine ?= "eba03655e8e436ef6090100423bcea43e4911478"
+SRCREV_meta ?= "1f78e20cc98dd46637c0beb6007214fb3650992c"
+
+PV = "${LINUX_VERSION}+git${SRCPV}"
+
+SRC_URI = 
"git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
+   
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.18;destsuffix=${KMETA}"
+
+COMPATIBLE_MACHINE = "qemux86|qemux86-64"
+
+# Functionality flags
+KERNEL_FEATURES = ""
+
+KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.18.bb 
b/meta/recipes-kernel/linux/linux-yocto_4.18.bb
new file mode 100644
index ..b42c124c87da
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto_4.18.bb
@@ -0,0 +1,48 @@
+KBRANCH ?= "v4.18/standard/base"
+
+require recipes-kernel/linux/linux-yocto.inc
+
+# board specific branches
+KBRANCH_qemuarm  ?= "v4.18/standard/arm-versatile-926ejs"
+K

Re: [OE-core] [PATCH 10/12] linux-yocto: introduce 4.18 recipes

[Khem Raj]

uprev fixes it even on mips
On Mon, Aug 27, 2018 at 5:59 AM Bruce Ashfield
 wrote:
>
> On 2018-08-27 2:58 AM, Khem Raj wrote:
> > There is one failure on meta-openembedded seen
>
> Not bad!
>
> I'll fire off a build and see what happens here. I'm guessing that
> an uprev is the answer .. but you never know with mips :D
>
> Bruce
>
> >
> > http://errors.yoctoproject.org/Errors/Details/187942/
> > On Fri, Aug 24, 2018 at 8:01 AM Bruce Ashfield
> >  wrote:
> >>
> >> Introducing the 4.18 kernel as the 'newest' kernel for the oe core
> >> release.
> >>
> >> This update includes tweaked configs, carried forward BSPs, features
> >> (aufs, yaffs2, preempt-rt) and has been tested on all arches for boot
> >> and performance sanity.
> >>
> >> Signed-off-by: Bruce Ashfield 
> >> ---
> >>   meta/recipes-kernel/linux/linux-yocto-rt_4.18.bb   | 43 
> >> +++
> >>   meta/recipes-kernel/linux/linux-yocto-tiny_4.18.bb | 29 +
> >>   meta/recipes-kernel/linux/linux-yocto_4.18.bb  | 48 
> >> ++
> >>   3 files changed, 120 insertions(+)
> >>   create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_4.18.bb
> >>   create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_4.18.bb
> >>   create mode 100644 meta/recipes-kernel/linux/linux-yocto_4.18.bb
> >>
> >> diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.18.bb 
> >> b/meta/recipes-kernel/linux/linux-yocto-rt_4.18.bb
> >> new file mode 100644
> >> index ..f740b1dcd892
> >> --- /dev/null
> >> +++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.18.bb
> >> @@ -0,0 +1,43 @@
> >> +KBRANCH ?= "v4.18/standard/preempt-rt/base"
> >> +
> >> +require recipes-kernel/linux/linux-yocto.inc
> >> +
> >> +# Skip processing of this recipe if it is not explicitly specified as the
> >> +# PREFERRED_PROVIDER for virtual/kernel. This avoids errors when trying
> >> +# to build multiple virtual/kernel providers, e.g. as dependency of
> >> +# core-image-rt-sdk, core-image-rt.
> >> +python () {
> >> +if d.getVar("KERNEL_PACKAGE_NAME") == "kernel" and 
> >> d.getVar("PREFERRED_PROVIDER_virtual/kernel") != "linux-yocto-rt":
> >> +raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel 
> >> to linux-yocto-rt to enable it")
> >> +}
> >> +
> >> +SRCREV_machine ?= "8a990322beb7b3aa5a06d7bd630f819b70911587"
> >> +SRCREV_meta ?= "1f78e20cc98dd46637c0beb6007214fb3650992c"
> >> +
> >> +SRC_URI = 
> >> "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine 
> >> \
> >> +   
> >> git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.18;destsuffix=${KMETA}"
> >> +
> >> +LINUX_VERSION ?= "4.18.3"
> >> +
> >> +LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
> >> +
> >> +DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', 
> >> d)}"
> >> +DEPENDS += "openssl-native util-linux-native"
> >> +
> >> +PV = "${LINUX_VERSION}+git${SRCPV}"
> >> +
> >> +KMETA = "kernel-meta"
> >> +KCONF_BSP_AUDIT_LEVEL = "2"
> >> +
> >> +LINUX_KERNEL_TYPE = "preempt-rt"
> >> +
> >> +COMPATIBLE_MACHINE = "(qemux86|qemux86-64|qemuarm|qemuppc|qemumips)"
> >> +
> >> +KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
> >> +
> >> +# Functionality flags
> >> +KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc 
> >> features/taskstats/taskstats.scc"
> >> +KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
> >> +KERNEL_FEATURES_append_qemuall=" cfg/virtio.scc"
> >> +KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
> >> +KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc"
> >> diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.18.bb 
> >> b/meta/recipes-kernel/linux/linux-yocto-tiny_4.18.bb
> >> new file mode 100644
> >> index ..1f0b35ec25ec
> >> --- /dev/null
> >> +++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.18.bb
> >> @@ -0,0 +1,29 @@
> >> +KBRANCH ?= "v4.18/standard/tiny/common-pc"
> >> +LINUX_KERNEL_TYPE = "tiny"
> >> +KCONFIG_MODE = "--allnoconfig"
> >> +
> >> +require recipes-kernel/linux/linux-yocto.inc
> >> +
> >> +LINUX_VERSION ?= "4.18.3"
> >> +LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
> >> +
> >> +DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', 
> >> d)}"
> >> +DEPENDS += "openssl-native util-linux-native"
> >> +
> >> +KMETA = "kernel-meta"
> >> +KCONF_BSP_AUDIT_LEVEL = "2"
> >> +
> >> +SRCREV_machine ?= "eba03655e8e436ef6090100423bcea43e4911478"
> >> +SRCREV_meta ?= "1f78e20cc98dd46637c0beb6007214fb3650992c"
> >> +
> >> +PV = "${LINUX_VERSION}+git${SRCPV}"
> >> +
> >> +SRC_URI = 
> >> "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine 
> >> \
> >> +   
> >> git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.18;destsuffix=${KMETA}"
> >> +
> >> +COMPATIBLE_MACHINE = "qemux86|qemux86-64"
> >> +
> >> +# Functionality flags
> >> +KERNEL_FEATURES = ""
> >> +
> >> +KERNEL_DEVICETREE_qemuarm

[OE-core] [PATCH] cpan.bbclass: make RPATH fix more general

[Jens Rehsack]

Extract a general version of RPATH fix for libxml-parser-perl_2.44.bb
from
  292471701 libxml-parser-perl: fix "...contains bad RPATH"
into cpan.bbclass to catch most errors reported by Khem Raj via
  http://errors.yoctoproject.org/Errors/Build/66538/

Genrally, Perl 5 toolchain deals with cross-compile sysroots
as if a dependency is installed at an exostic place on a server.
This issue needs to be addressed wider into the community.

Signed-off-by: Jens Rehsack 
---
 meta/classes/cpan.bbclass | 10 ++
 meta/recipes-devtools/perl/libxml-parser-perl_2.44.bb |  7 ---
 2 files changed, 10 insertions(+), 7 deletions(-)

diff --git a/meta/classes/cpan.bbclass b/meta/classes/cpan.bbclass
index 926c6358a6..a5bc301898 100644
--- a/meta/classes/cpan.bbclass
+++ b/meta/classes/cpan.bbclass
@@ -40,6 +40,16 @@ cpan_do_configure () {
fi
 }
 
+do_configure_append_class-target() {
+   find . -name Makefile | xargs sed -E -i \
+   -e 's:LD_RUN_PATH ?= ?"?[^"]*"?::g'
+}
+
+do_configure_append_class-nativesdk() {
+   find . -name Makefile | xargs sed -E -i \
+   -e 's:LD_RUN_PATH ?= ?"?[^"]*"?::g'
+}
+
 cpan_do_compile () {
oe_runmake PASTHRU_INC="${CFLAGS}" LD="${CCLD}"
 }
diff --git a/meta/recipes-devtools/perl/libxml-parser-perl_2.44.bb 
b/meta/recipes-devtools/perl/libxml-parser-perl_2.44.bb
index 194ed6ac48..95af4d1de6 100644
--- a/meta/recipes-devtools/perl/libxml-parser-perl_2.44.bb
+++ b/meta/recipes-devtools/perl/libxml-parser-perl_2.44.bb
@@ -21,13 +21,6 @@ inherit cpan ptest-perl
 do_configure_append_class-target() {
sed -E \
-e 's:-L${STAGING_LIBDIR}::g' -e 's:-I${STAGING_INCDIR}::g' \
-   -e 's:LD_RUN_PATH ?= ?"?[^"]*"?::g' \
-   -i Makefile Expat/Makefile
-}
-
-do_configure_append_class-nativesdk() {
-   sed -E \
-   -e 's:LD_RUN_PATH ?= ?"?[^"]*"?::g' \
-i Makefile Expat/Makefile
 }
 
-- 
2.17.1

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

Re: [OE-core] [PATCH 10/12] linux-yocto: introduce 4.18 recipes

[Bruce Ashfield]

On 2018-08-27 2:58 AM, Khem Raj wrote:

There is one failure on meta-openembedded seen


Not bad!

I'll fire off a build and see what happens here. I'm guessing that
an uprev is the answer .. but you never know with mips :D

Bruce



http://errors.yoctoproject.org/Errors/Details/187942/
On Fri, Aug 24, 2018 at 8:01 AM Bruce Ashfield
 wrote:


Introducing the 4.18 kernel as the 'newest' kernel for the oe core
release.

This update includes tweaked configs, carried forward BSPs, features
(aufs, yaffs2, preempt-rt) and has been tested on all arches for boot
and performance sanity.

Signed-off-by: Bruce Ashfield 
---
  meta/recipes-kernel/linux/linux-yocto-rt_4.18.bb   | 43 +++
  meta/recipes-kernel/linux/linux-yocto-tiny_4.18.bb | 29 +
  meta/recipes-kernel/linux/linux-yocto_4.18.bb  | 48 ++
  3 files changed, 120 insertions(+)
  create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_4.18.bb
  create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_4.18.bb
  create mode 100644 meta/recipes-kernel/linux/linux-yocto_4.18.bb

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.18.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.18.bb
new file mode 100644
index ..f740b1dcd892
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.18.bb
@@ -0,0 +1,43 @@
+KBRANCH ?= "v4.18/standard/preempt-rt/base"
+
+require recipes-kernel/linux/linux-yocto.inc
+
+# Skip processing of this recipe if it is not explicitly specified as the
+# PREFERRED_PROVIDER for virtual/kernel. This avoids errors when trying
+# to build multiple virtual/kernel providers, e.g. as dependency of
+# core-image-rt-sdk, core-image-rt.
+python () {
+if d.getVar("KERNEL_PACKAGE_NAME") == "kernel" and 
d.getVar("PREFERRED_PROVIDER_virtual/kernel") != "linux-yocto-rt":
+raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to 
linux-yocto-rt to enable it")
+}
+
+SRCREV_machine ?= "8a990322beb7b3aa5a06d7bd630f819b70911587"
+SRCREV_meta ?= "1f78e20cc98dd46637c0beb6007214fb3650992c"
+
+SRC_URI = 
"git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
+   
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.18;destsuffix=${KMETA}"
+
+LINUX_VERSION ?= "4.18.3"
+
+LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
+
+DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
+DEPENDS += "openssl-native util-linux-native"
+
+PV = "${LINUX_VERSION}+git${SRCPV}"
+
+KMETA = "kernel-meta"
+KCONF_BSP_AUDIT_LEVEL = "2"
+
+LINUX_KERNEL_TYPE = "preempt-rt"
+
+COMPATIBLE_MACHINE = "(qemux86|qemux86-64|qemuarm|qemuppc|qemumips)"
+
+KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
+
+# Functionality flags
+KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc 
features/taskstats/taskstats.scc"
+KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
+KERNEL_FEATURES_append_qemuall=" cfg/virtio.scc"
+KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
+KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.18.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_4.18.bb
new file mode 100644
index ..1f0b35ec25ec
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.18.bb
@@ -0,0 +1,29 @@
+KBRANCH ?= "v4.18/standard/tiny/common-pc"
+LINUX_KERNEL_TYPE = "tiny"
+KCONFIG_MODE = "--allnoconfig"
+
+require recipes-kernel/linux/linux-yocto.inc
+
+LINUX_VERSION ?= "4.18.3"
+LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
+
+DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
+DEPENDS += "openssl-native util-linux-native"
+
+KMETA = "kernel-meta"
+KCONF_BSP_AUDIT_LEVEL = "2"
+
+SRCREV_machine ?= "eba03655e8e436ef6090100423bcea43e4911478"
+SRCREV_meta ?= "1f78e20cc98dd46637c0beb6007214fb3650992c"
+
+PV = "${LINUX_VERSION}+git${SRCPV}"
+
+SRC_URI = 
"git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
+   
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.18;destsuffix=${KMETA}"
+
+COMPATIBLE_MACHINE = "qemux86|qemux86-64"
+
+# Functionality flags
+KERNEL_FEATURES = ""
+
+KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.18.bb 
b/meta/recipes-kernel/linux/linux-yocto_4.18.bb
new file mode 100644
index ..b42c124c87da
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto_4.18.bb
@@ -0,0 +1,48 @@
+KBRANCH ?= "v4.18/standard/base"
+
+require recipes-kernel/linux/linux-yocto.inc
+
+# board specific branches
+KBRANCH_qemuarm  ?= "v4.18/standard/arm-versatile-926ejs"
+KBRANCH_qemuarm64 ?= "v4.18/standard/qemuarm64"
+KBRANCH_qemumips ?= "v4.18/standard/mti-malta32"
+KBRANCH_qemuppc  ?= "v4.18/standard/qemuppc"
+KBRANCH_qemux86  ?= "v4.18/standard/base"
+KBRANCH_qemux86-64 ?= "v4.18/standard/base"
+KBRANCH_qemumips64 ?= "v4.18/

Re: [OE-core] [meta-oe][for-sumo][PATCH] ltrace_git: Update SRC_URI due to inaccessible problem

[Martin Jansa]

On Mon, Aug 27, 2018 at 10:38:40AM +0200, vincent.prince...@gmail.com wrote:
> From: Junil Kim 
> 
> Existing URI service was closed and fetch error occurred.
> Change existing repository to another mirrored SRC URI.
> 
> Signed-off-by: Junil Kim 
> Signed-off-by: Khem Raj 

changes fro meta-oe need to go through openembedded-devel ML as
explained in README file.

> ---
>  meta-oe/recipes-devtools/ltrace/ltrace_git.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta-oe/recipes-devtools/ltrace/ltrace_git.bb 
> b/meta-oe/recipes-devtools/ltrace/ltrace_git.bb
> index abe015d..f4033f7 100644
> --- a/meta-oe/recipes-devtools/ltrace/ltrace_git.bb
> +++ b/meta-oe/recipes-devtools/ltrace/ltrace_git.bb
> @@ -15,7 +15,7 @@ SRCREV = "c22d359433b333937ee3d803450dc41998115685"
>  
>  DEPENDS = "elfutils"
>  RDEPENDS_${PN} = "elfutils"
> -SRC_URI = "git://anonscm.debian.org/collab-maint/ltrace.git;branch=master \
> +SRC_URI = 
> "git://github.com/sparkleholic/ltrace.git;branch=master;protocol=http \
> file://configure-allow-to-disable-selinux-support.patch \
> file://0001-replace-readdir_r-with-readdir.patch \
> file://0001-Use-correct-enum-type.patch \
> -- 
> 2.7.4
> 
> -- 
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

-- 
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com


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

[OE-core] [PATCH] distutils3.bbclass: improve error messages

[Jens Rehsack]

For non-python developers it's difficult to identify where start
searching in case of errors. Fixing and marking the string to
grep for might help finding some root causes of issues slightly
quicker.

Signed-off-by: Jens Rehsack 
---
 meta/classes/distutils3.bbclass | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/classes/distutils3.bbclass b/meta/classes/distutils3.bbclass
index 1d0c54a513..9e31505f0c 100644
--- a/meta/classes/distutils3.bbclass
+++ b/meta/classes/distutils3.bbclass
@@ -23,14 +23,14 @@ distutils3_do_compile() {
 STAGING_LIBDIR=${STAGING_LIBDIR} \
 ${STAGING_BINDIR_NATIVE}/${PYTHON_PN}-native/${PYTHON_PN} setup.py \
 build ${DISTUTILS_BUILD_ARGS} || \
-bbfatal_log "${PYTHON_PN} setup.py build_ext execution failed."
+bbfatal_log "'${PYTHON_PN} setup.py build ${DISTUTILS_BUILD_ARGS}' 
execution failed."
 }
 distutils3_do_compile[vardepsexclude] = "MACHINE"
 
 distutils3_stage_headers() {
 install -d ${STAGING_DIR_HOST}${PYTHON_SITEPACKAGES_DIR}
 ${STAGING_BINDIR_NATIVE}/${PYTHON_PN}-native/${PYTHON_PN} setup.py 
install_headers ${DISTUTILS_STAGE_HEADERS_ARGS} || \
-bbfatal_log "${PYTHON_PN} setup.py install_headers execution failed."
+bbfatal_log "'${PYTHON_PN} setup.py install_headers' execution failed."
 }
 distutils3_stage_headers[vardepsexclude] = "MACHINE"
 
-- 
2.17.1

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

[OE-core] ✗ patchtest: failure for ltrace_git: Update SRC_URI due to inaccessible problem (rev3)

[Patchwork]

== Series Details ==

Series: ltrace_git: Update SRC_URI due to inaccessible problem (rev3)
Revision: 3
URL   : https://patchwork.openembedded.org/series/13629/
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:



* Patch[meta-oe, for-sumo] ltrace_git: Update SRC_URI due to 
inaccessible problem
 Issue Series sent to the wrong mailing list 
[test_target_mailing_list] 
  Suggested fixCheck the project's README (meta-oe, for-sumo) and send the 
patch to the indicated list

* 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 0791c4d39e)



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

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

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

[OE-core] ✗ patchtest: failure for libsodium: Update SRC_URI due to inaccessible problem

[Patchwork]

== Series Details ==

Series: libsodium: Update SRC_URI due to inaccessible problem
Revision: 1
URL   : https://patchwork.openembedded.org/series/13746/
State : failure

== Summary ==


Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on the proposed
series by patchtest resulting in the following failures:



* Issue Series sent to the wrong mailing list or some patches from 
the series correspond to different mailing lists [test_target_mailing_list] 
  Suggested fixSend the series again to the correct mailing list (ML)
  Suggested ML openembedded-de...@lists.openembedded.org 
[http://git.openembedded.org/meta-openembedded/]
  Patch's path:meta-oe/recipes-crypto/libsodium/libsodium_1.0.11.bb

* 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 0791c4d39e)



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

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

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

[OE-core] [for-sumo][PATCH] libsodium: Update SRC_URI due to inaccessible problem

[vincent . prince . fr]

From: Vincent Prince 

Signed-off-by: Vincent Prince 
---
 meta-oe/recipes-crypto/libsodium/libsodium_1.0.11.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-oe/recipes-crypto/libsodium/libsodium_1.0.11.bb 
b/meta-oe/recipes-crypto/libsodium/libsodium_1.0.11.bb
index cbcbe96..00fa7aa 100644
--- a/meta-oe/recipes-crypto/libsodium/libsodium_1.0.11.bb
+++ b/meta-oe/recipes-crypto/libsodium/libsodium_1.0.11.bb
@@ -3,7 +3,7 @@ HOMEPAGE = "http://libsodium.org/";
 LICENSE = "ISC"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=c9f00492f01f5610253fde01c3d2e866"
 
-SRC_URI = 
"https://download.libsodium.org/libsodium/releases/${BPN}-${PV}.tar.gz";
+SRC_URI = 
"https://download.libsodium.org/libsodium/releases/old/unsupported/${BPN}-${PV}.tar.gz";
 SRC_URI[md5sum] = "b58928d035064b2a46fb564937b83540"
 SRC_URI[sha256sum] = 
"a14549db3c49f6ae2170cbbf4664bd48ace50681045e8dbea7c8d9fb96f9c765"
 
-- 
2.7.4

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

[OE-core] [PATCH 0/1] nativesdk.bbclass: set consistent staging dirs regardless of multilib

[Chen Qi]

*** BLURB HERE ***
The following changes since commit 87d3a9685dd9613e4f6718031d4ebd9344b01c47:

  bitbake: parse/ast: ensure saved event handlers really do get restored 
(2018-08-24 07:53:14 +0100)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib ChenQi/nativesdk-recipe-sysroot
  
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=ChenQi/nativesdk-recipe-sysroot

Chen Qi (1):
  nativesdk.bbclass: set consistent staging dirs regardless of multilib

 meta/classes/nativesdk.bbclass | 5 +
 1 file changed, 5 insertions(+)

-- 
1.9.1

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

[OE-core] [PATCH 1/1] nativesdk.bbclass: set consistent staging dirs regardless of multilib

[Chen Qi]

For now, the RECIPE_SYSROOT of nativesdk recipes is ${WORKDIR}/recipe-sysroot
if multilib is disabled and ${WORKDIR}/nativesdk-recipe-sysroot if multilib
is enabled. And it's causing chaos. Problems I've met include:
1) 'File Exists' error when doing extend_recipe_sysroot
2) Rebuilding failure about cmake based nativesdk recipes if toggling multilib

In nativesdk.bbclass, We've set MULTILIBS to be "", and we've changed MLPREFIX
to be 'nativesdk-', I think we should also set consistent RECIPE_SYSROOT to be
${WORKDIR}/nativesdk-recipe-sysroot.

Signed-off-by: Chen Qi 
---
 meta/classes/nativesdk.bbclass | 5 +
 1 file changed, 5 insertions(+)

diff --git a/meta/classes/nativesdk.bbclass b/meta/classes/nativesdk.bbclass
index ab566e9..f3336e5 100644
--- a/meta/classes/nativesdk.bbclass
+++ b/meta/classes/nativesdk.bbclass
@@ -12,6 +12,11 @@ MACHINEOVERRIDES = ""
 
 MULTILIBS = ""
 
+# we need consistent staging dir whether or not multilib is enabled
+STAGING_DIR_HOST = "${WORKDIR}/nativesdk-recipe-sysroot"
+STAGING_DIR_TARGET = "${WORKDIR}/nativesdk-recipe-sysroot"
+RECIPE_SYSROOT = "${WORKDIR}/nativesdk-recipe-sysroot"
+
 #
 # Update PACKAGE_ARCH and PACKAGE_ARCHS
 #
-- 
1.9.1

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

[OE-core] [PATCH 1/1] staging.bbclass: avoid staging native components for target sysroot

[Chen Qi]

In the staging_populate_sysroot_dir function, components are staged
by pkgarch matching. In case of x86-64 targets, it's possible that
the native components are also matched, and thus are expectedly installed.

The negative effect is at least unnecessary installation, and in some
cases is compilation error. For example, when using eSDK and we are trying
to cross compile some project in lib32 environment, the compilation will
fail.

Signed-off-by: Chen Qi 
---
 meta/classes/staging.bbclass | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/classes/staging.bbclass b/meta/classes/staging.bbclass
index 27b012e..1b9803a 100644
--- a/meta/classes/staging.bbclass
+++ b/meta/classes/staging.bbclass
@@ -198,6 +198,9 @@ def staging_populate_sysroot_dir(targetsysroot, 
nativesysroot, native, d):
 if manifest.endswith("-initial.populate_sysroot"):
 # skip glibc-initial and libgcc-initial due to file overlap
 continue
+if not native and manifest.endswith("-native.populate_sysroot"):
+# avoid native components to be installed into target sysroot
+continue
 tmanifest = targetdir + "/" + os.path.basename(manifest)
 if os.path.exists(tmanifest):
 continue
-- 
1.9.1

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

[OE-core] [PATCH 0/1] staging.bbclass: avoid staging native components for target sysroot

[Chen Qi]

*** BLURB HERE ***
The following changes since commit 87d3a9685dd9613e4f6718031d4ebd9344b01c47:

  bitbake: parse/ast: ensure saved event handlers really do get restored 
(2018-08-24 07:53:14 +0100)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib ChenQi/staging-native
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=ChenQi/staging-native

Chen Qi (1):
  staging.bbclass: avoid staging native components for target sysroot

 meta/classes/staging.bbclass | 3 +++
 1 file changed, 3 insertions(+)

-- 
1.9.1

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

[OE-core] [meta-oe][for-sumo][PATCH] ltrace_git: Update SRC_URI due to inaccessible problem

[vincent . prince . fr]

From: Junil Kim 

Existing URI service was closed and fetch error occurred.
Change existing repository to another mirrored SRC URI.

Signed-off-by: Junil Kim 
Signed-off-by: Khem Raj 
---
 meta-oe/recipes-devtools/ltrace/ltrace_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-oe/recipes-devtools/ltrace/ltrace_git.bb 
b/meta-oe/recipes-devtools/ltrace/ltrace_git.bb
index abe015d..f4033f7 100644
--- a/meta-oe/recipes-devtools/ltrace/ltrace_git.bb
+++ b/meta-oe/recipes-devtools/ltrace/ltrace_git.bb
@@ -15,7 +15,7 @@ SRCREV = "c22d359433b333937ee3d803450dc41998115685"
 
 DEPENDS = "elfutils"
 RDEPENDS_${PN} = "elfutils"
-SRC_URI = "git://anonscm.debian.org/collab-maint/ltrace.git;branch=master \
+SRC_URI = 
"git://github.com/sparkleholic/ltrace.git;branch=master;protocol=http \
file://configure-allow-to-disable-selinux-support.patch \
file://0001-replace-readdir_r-with-readdir.patch \
file://0001-Use-correct-enum-type.patch \
-- 
2.7.4

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

Re: [OE-core] [PATCH 10/12] linux-yocto: introduce 4.18 recipes

[Khem Raj]

There is one failure on meta-openembedded seen

http://errors.yoctoproject.org/Errors/Details/187942/
On Fri, Aug 24, 2018 at 8:01 AM Bruce Ashfield
 wrote:
>
> Introducing the 4.18 kernel as the 'newest' kernel for the oe core
> release.
>
> This update includes tweaked configs, carried forward BSPs, features
> (aufs, yaffs2, preempt-rt) and has been tested on all arches for boot
> and performance sanity.
>
> Signed-off-by: Bruce Ashfield 
> ---
>  meta/recipes-kernel/linux/linux-yocto-rt_4.18.bb   | 43 +++
>  meta/recipes-kernel/linux/linux-yocto-tiny_4.18.bb | 29 +
>  meta/recipes-kernel/linux/linux-yocto_4.18.bb  | 48 
> ++
>  3 files changed, 120 insertions(+)
>  create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_4.18.bb
>  create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_4.18.bb
>  create mode 100644 meta/recipes-kernel/linux/linux-yocto_4.18.bb
>
> diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.18.bb 
> b/meta/recipes-kernel/linux/linux-yocto-rt_4.18.bb
> new file mode 100644
> index ..f740b1dcd892
> --- /dev/null
> +++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.18.bb
> @@ -0,0 +1,43 @@
> +KBRANCH ?= "v4.18/standard/preempt-rt/base"
> +
> +require recipes-kernel/linux/linux-yocto.inc
> +
> +# Skip processing of this recipe if it is not explicitly specified as the
> +# PREFERRED_PROVIDER for virtual/kernel. This avoids errors when trying
> +# to build multiple virtual/kernel providers, e.g. as dependency of
> +# core-image-rt-sdk, core-image-rt.
> +python () {
> +if d.getVar("KERNEL_PACKAGE_NAME") == "kernel" and 
> d.getVar("PREFERRED_PROVIDER_virtual/kernel") != "linux-yocto-rt":
> +raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to 
> linux-yocto-rt to enable it")
> +}
> +
> +SRCREV_machine ?= "8a990322beb7b3aa5a06d7bd630f819b70911587"
> +SRCREV_meta ?= "1f78e20cc98dd46637c0beb6007214fb3650992c"
> +
> +SRC_URI = 
> "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
> +   
> git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.18;destsuffix=${KMETA}"
> +
> +LINUX_VERSION ?= "4.18.3"
> +
> +LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
> +
> +DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
> +DEPENDS += "openssl-native util-linux-native"
> +
> +PV = "${LINUX_VERSION}+git${SRCPV}"
> +
> +KMETA = "kernel-meta"
> +KCONF_BSP_AUDIT_LEVEL = "2"
> +
> +LINUX_KERNEL_TYPE = "preempt-rt"
> +
> +COMPATIBLE_MACHINE = "(qemux86|qemux86-64|qemuarm|qemuppc|qemumips)"
> +
> +KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
> +
> +# Functionality flags
> +KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc 
> features/taskstats/taskstats.scc"
> +KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
> +KERNEL_FEATURES_append_qemuall=" cfg/virtio.scc"
> +KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
> +KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc"
> diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.18.bb 
> b/meta/recipes-kernel/linux/linux-yocto-tiny_4.18.bb
> new file mode 100644
> index ..1f0b35ec25ec
> --- /dev/null
> +++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.18.bb
> @@ -0,0 +1,29 @@
> +KBRANCH ?= "v4.18/standard/tiny/common-pc"
> +LINUX_KERNEL_TYPE = "tiny"
> +KCONFIG_MODE = "--allnoconfig"
> +
> +require recipes-kernel/linux/linux-yocto.inc
> +
> +LINUX_VERSION ?= "4.18.3"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
> +
> +DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
> +DEPENDS += "openssl-native util-linux-native"
> +
> +KMETA = "kernel-meta"
> +KCONF_BSP_AUDIT_LEVEL = "2"
> +
> +SRCREV_machine ?= "eba03655e8e436ef6090100423bcea43e4911478"
> +SRCREV_meta ?= "1f78e20cc98dd46637c0beb6007214fb3650992c"
> +
> +PV = "${LINUX_VERSION}+git${SRCPV}"
> +
> +SRC_URI = 
> "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
> +   
> git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.18;destsuffix=${KMETA}"
> +
> +COMPATIBLE_MACHINE = "qemux86|qemux86-64"
> +
> +# Functionality flags
> +KERNEL_FEATURES = ""
> +
> +KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
> diff --git a/meta/recipes-kernel/linux/linux-yocto_4.18.bb 
> b/meta/recipes-kernel/linux/linux-yocto_4.18.bb
> new file mode 100644
> index ..b42c124c87da
> --- /dev/null
> +++ b/meta/recipes-kernel/linux/linux-yocto_4.18.bb
> @@ -0,0 +1,48 @@
> +KBRANCH ?= "v4.18/standard/base"
> +
> +require recipes-kernel/linux/linux-yocto.inc
> +
> +# board specific branches
> +KBRANCH_qemuarm  ?= "v4.18/standard/arm-versatile-926ejs"
> +KBRANCH_qemuarm64 ?= "v4.18/standard/qemuarm64"
> +KBRANCH_qemumips ?= "v4.18/standard/mti-malta32"
> +KBRANCH_qemuppc  ?= "v4.18/standard/qemuppc"
> +KBRANCH_qemux86  ?= "v4.18/standard/base"
> +KBRANCH_qemu