[OE-core] [PATCH] default-distrovars.inc: drop obsolete LGPLv2_WHITELIST_GPL-3.0

2018-05-11 Thread Andre McCurdy
There doesn't seem to be a clear reason to have two separate
variables to hold whitelisted GPLv3 recipes. Both variables are
treated the same, so adding a recipe to LGPLv2_WHITELIST_GPL-3.0 is
already equivalent to adding it to WHITELIST_GPL-3.0.

Anyone needing to whitelist a GPLv3 recipe should now just use
WHITELIST_GPL-3.0.

Signed-off-by: Andre McCurdy 
---
 meta/classes/base.bbclass   | 25 -
 meta/classes/multilib.bbclass   | 12 +---
 meta/conf/distro/include/default-distrovars.inc |  1 -
 3 files changed, 17 insertions(+), 21 deletions(-)

diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
index bd0d6e3..68626d5 100644
--- a/meta/classes/base.bbclass
+++ b/meta/classes/base.bbclass
@@ -529,19 +529,18 @@ python () {
 incompatwl = []
 for lic in bad_licenses:
 spdx_license = return_spdx(d, lic)
-for w in ["LGPLv2_WHITELIST_", "WHITELIST_"]:
-whitelist.extend((d.getVar(w + lic) or "").split())
-if spdx_license:
-whitelist.extend((d.getVar(w + spdx_license) or 
"").split())
-'''
-We need to track what we are whitelisting and why. If pn is
-incompatible we need to be able to note that the image that
-is created may infact contain incompatible licenses despite
-INCOMPATIBLE_LICENSE being set.
-'''
-incompatwl.extend((d.getVar(w + lic) or "").split())
-if spdx_license:
-incompatwl.extend((d.getVar(w + spdx_license) or 
"").split())
+whitelist.extend((d.getVar("WHITELIST_" + lic) or "").split())
+if spdx_license:
+whitelist.extend((d.getVar("WHITELIST_" + spdx_license) or 
"").split())
+'''
+We need to track what we are whitelisting and why. If pn is
+incompatible we need to be able to note that the image that
+is created may infact contain incompatible licenses despite
+INCOMPATIBLE_LICENSE being set.
+'''
+incompatwl.extend((d.getVar("WHITELIST_" + lic) or "").split())
+if spdx_license:
+incompatwl.extend((d.getVar("WHITELIST_" + spdx_license) 
or "").split())
 
 if not pn in whitelist:
 pkgs = d.getVar('PACKAGES').split()
diff --git a/meta/classes/multilib.bbclass b/meta/classes/multilib.bbclass
index 816f54e..4636c20 100644
--- a/meta/classes/multilib.bbclass
+++ b/meta/classes/multilib.bbclass
@@ -49,7 +49,6 @@ python multilib_virtclass_handler () {
 if bb.data.inherits_class('allarch', e.data) and not 
bb.data.inherits_class('packagegroup', e.data):
 raise bb.parse.SkipPackage("Don't extend allarch recipes which are not 
packagegroups")
 
-
 # Expand this since this won't work correctly once we set a multilib into 
place
 e.data.setVar("ALL_MULTILIB_PACKAGE_ARCHS", 
e.data.getVar("ALL_MULTILIB_PACKAGE_ARCHS"))
  
@@ -65,12 +64,11 @@ python multilib_virtclass_handler () {
 e.data.setVar("PN", variant + "-" + e.data.getVar("PN", False))
 e.data.setVar("OVERRIDES", e.data.getVar("OVERRIDES", False) + override)
 
-# Expand the WHITELISTs with multilib prefix
-for whitelist in ["WHITELIST_GPL-3.0", "LGPLv2_WHITELIST_GPL-3.0"]:
-pkgs = e.data.getVar(whitelist)
-for pkg in pkgs.split():
-pkgs += " " + variant + "-" + pkg
-e.data.setVar(whitelist, pkgs)
+# Expand WHITELIST_GPL-3.0 with multilib prefix
+pkgs = e.data.getVar("WHITELIST_GPL-3.0")
+for pkg in pkgs.split():
+pkgs += " " + variant + "-" + pkg
+e.data.setVar("WHITELIST_GPL-3.0", pkgs)
 
 # DEFAULTTUNE can change TARGET_ARCH override so expand this now before 
update_data
 newtune = e.data.getVar("DEFAULTTUNE_" + "virtclass-multilib-" + variant, 
False)
diff --git a/meta/conf/distro/include/default-distrovars.inc 
b/meta/conf/distro/include/default-distrovars.inc
index 76d09af..2f46e13 100644
--- a/meta/conf/distro/include/default-distrovars.inc
+++ b/meta/conf/distro/include/default-distrovars.inc
@@ -24,7 +24,6 @@ DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT} 
${DISTRO_FEATURES_LIBC}"
 IMAGE_FEATURES ?= ""
 
 WHITELIST_GPL-3.0 ?= ""
-LGPLv2_WHITELIST_GPL-3.0 ?= ""
 
 COMMERCIAL_AUDIO_PLUGINS ?= ""
 # COMMERCIAL_AUDIO_PLUGINS ?= "gst-plugins-ugly-mad 
gst-plugins-ugly-mpegaudioparse"
-- 
1.9.1

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


[OE-core] [rocko][PATCH] libnl: fix CVE-2017-0553

2018-05-11 Thread Andre McCurdy
An elevation of privilege vulnerability in libnl could enable a local
malicious application to execute arbitrary code within the context of
the Wi-Fi service. This issue is rated as Moderate because it first
requires compromising a privileged process and is mitigated by
current platform configurations. Product: Android. Versions: 5.0.2,
5.1.1, 6.0, 6.0.1, 7.0, 7.1.1. Android ID: A-32342065. NOTE: this
issue also exists in the upstream libnl before 3.3.0 library.

  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0553

Backport fix from upstream libnl 3.3.0 release:

  
https://github.com/thom311/libnl/commit/3e18948f17148e6a3c4255bdeaaf01ef6081ceeb
  http://lists.infradead.org/pipermail/libnl/2017-May/002313.html

Signed-off-by: Andre McCurdy 
---
 ...eck-for-integer-overflow-in-nlmsg_reserve.patch | 43 ++
 meta/recipes-support/libnl/libnl_3.2.29.bb |  2 +
 2 files changed, 45 insertions(+)
 create mode 100644 
meta/recipes-support/libnl/libnl/lib-check-for-integer-overflow-in-nlmsg_reserve.patch

diff --git 
a/meta/recipes-support/libnl/libnl/lib-check-for-integer-overflow-in-nlmsg_reserve.patch
 
b/meta/recipes-support/libnl/libnl/lib-check-for-integer-overflow-in-nlmsg_reserve.patch
new file mode 100644
index 000..594dd06
--- /dev/null
+++ 
b/meta/recipes-support/libnl/libnl/lib-check-for-integer-overflow-in-nlmsg_reserve.patch
@@ -0,0 +1,43 @@
+From 3e18948f17148e6a3c4255bdeaaf01ef6081ceeb Mon Sep 17 00:00:00 2001
+From: Thomas Haller 
+Date: Mon, 6 Feb 2017 22:23:52 +0100
+Subject: [PATCH] lib: check for integer-overflow in nlmsg_reserve()
+
+In general, libnl functions are not robust against calling with
+invalid arguments. Thus, never call libnl functions with invalid
+arguments. In case of nlmsg_reserve() this means never provide
+a @len argument that causes overflow.
+
+Still, add an additional safeguard to avoid exploiting such bugs.
+
+Assume that @pad is a trusted, small integer.
+Assume that n->nm_size is a valid number of allocated bytes (and thus
+much smaller then SIZE_T_MAX).
+Assume, that @len may be set to an untrusted value. Then the patch
+avoids an integer overflow resulting in reserving too few bytes.
+
+Upstream-Status: Backport 
[https://github.com/thom311/libnl/commit/3e18948f17148e6a3c4255bdeaaf01ef6081ceeb]
+CVE: CVE-2017-0553
+
+Signed-off-by: Andre McCurdy 
+---
+ lib/msg.c | 3 +++
+ 1 file changed, 3 insertions(+)
+
+diff --git a/lib/msg.c b/lib/msg.c
+index 9af3f3a..3e27d4e 100644
+--- a/lib/msg.c
 b/lib/msg.c
+@@ -411,6 +411,9 @@ void *nlmsg_reserve(struct nl_msg *n, size_t len, int pad)
+   size_t nlmsg_len = n->nm_nlh->nlmsg_len;
+   size_t tlen;
+ 
++  if (len > n->nm_size)
++  return NULL;
++
+   tlen = pad ? ((len + (pad - 1)) & ~(pad - 1)) : len;
+ 
+   if ((tlen + nlmsg_len) > n->nm_size)
+-- 
+1.9.1
+
diff --git a/meta/recipes-support/libnl/libnl_3.2.29.bb 
b/meta/recipes-support/libnl/libnl_3.2.29.bb
index 7d4839b..4ce80e8 100644
--- a/meta/recipes-support/libnl/libnl_3.2.29.bb
+++ b/meta/recipes-support/libnl/libnl_3.2.29.bb
@@ -12,7 +12,9 @@ DEPENDS = "flex-native bison-native"
 SRC_URI = 
"https://github.com/thom311/${BPN}/releases/download/${BPN}${@d.getVar('PV').replace('.','_')}/${BP}.tar.gz
 \
file://fix-pktloc_syntax_h-race.patch \
file://fix-pc-file.patch \
+   file://lib-check-for-integer-overflow-in-nlmsg_reserve.patch \
 "
+
 UPSTREAM_CHECK_URI = "https://github.com/thom311/${BPN}/releases;
 
 SRC_URI[md5sum] = "a8ba62a5c4f883f4e493a46d1f3733fe"
-- 
1.9.1

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


Re: [OE-core] [PATCHv2 5/5] qemu: use sdl2 instead of sdl1

2018-05-11 Thread Alistair Francis
On Fri, May 11, 2018 at 12:21 PM, Martin Jansa  wrote:
> * sdl1 since qemu-2.12.0 depends on x11 in DISTRO_FEATURES, switch to sdl2
>
> Signed-off-by: Martin Jansa 

Reviewed-by: Alistair Francis 

Alistair

> ---
>  meta/recipes-devtools/qemu/qemu.inc | 13 -
>  1 file changed, 8 insertions(+), 5 deletions(-)
>
> diff --git a/meta/recipes-devtools/qemu/qemu.inc 
> b/meta/recipes-devtools/qemu/qemu.inc
> index 9010a04792..8169e55e69 100644
> --- a/meta/recipes-devtools/qemu/qemu.inc
> +++ b/meta/recipes-devtools/qemu/qemu.inc
> @@ -74,11 +74,11 @@ do_install_append() {
>  # END of qemu-mips workaround
>
>  PACKAGECONFIG ??= " \
> -   fdt sdl kvm \
> -   ${@bb.utils.filter('DISTRO_FEATURES', 'alsa xen', d)} \
> -   "
> -PACKAGECONFIG_class-native ??= "fdt alsa kvm"
> -PACKAGECONFIG_class-nativesdk ??= "fdt sdl kvm"
> +fdt sdl sdl2 kvm \
> +${@bb.utils.filter('DISTRO_FEATURES', 'alsa xen', d)} \
> +"
> +PACKAGECONFIG_class-native ??= "fdt sdl sdl2 alsa kvm"
> +PACKAGECONFIG_class-nativesdk ??= "fdt sdl sdl2 kvm"
>
>  # Handle distros such as CentOS 5 32-bit that do not have kvm support
>  PACKAGECONFIG_class-native_remove = "${@'kvm' if not 
> os.path.exists('/usr/include/linux/kvm.h') else ''}"
> @@ -87,6 +87,9 @@ PACKAGECONFIG_class-native_remove = "${@'kvm' if not 
> os.path.exists('/usr/includ
>  PACKAGECONFIG_remove_darwin = "kvm"
>  PACKAGECONFIG_remove_mingw32 = "kvm"
>
> +# sdl1 can be used only together with x11 in DISTRO_FEATURES, because since:
> +# 
> https://github.com/qemu/qemu/commit/2ec78706d188df7d3dab43d07b19b05ef7800a44
> +# it explicitly includes X11/Xlib.h for all gtk, sdl1 UI backends
>  PACKAGECONFIG[sdl] = "--enable-sdl,--disable-sdl,libsdl"
>  PACKAGECONFIG[sdl2] = "--with-sdlabi=2.0,--with-sdlabi=1.2,libsdl2"
>  PACKAGECONFIG[virtfs] = "--enable-virtfs 
> --enable-attr,--disable-virtfs,libcap attr,"
> --
> 2.17.0
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCHv2 1/5] libsdl2: allow to build native and nativesdk

2018-05-11 Thread Alistair Francis
On Fri, May 11, 2018 at 12:20 PM, Martin Jansa  wrote:
> * enable x11 in native builds
>
> Signed-off-by: Martin Jansa 

Reviewed-by: Alistair Francis 

Alistair

> ---
>  meta/recipes-graphics/libsdl2/libsdl2_2.0.8.bb | 4 
>  1 file changed, 4 insertions(+)
>
> diff --git a/meta/recipes-graphics/libsdl2/libsdl2_2.0.8.bb 
> b/meta/recipes-graphics/libsdl2/libsdl2_2.0.8.bb
> index c0cf70d7fd..c37f669321 100644
> --- a/meta/recipes-graphics/libsdl2/libsdl2_2.0.8.bb
> +++ b/meta/recipes-graphics/libsdl2/libsdl2_2.0.8.bb
> @@ -37,6 +37,8 @@ EXTRA_OECONF = "--disable-oss --disable-esd --disable-arts \
>  # and BSP layers to pick either (desktop) opengl, gles2, or no GL
>  PACKAGECONFIG_GL ?= "${@bb.utils.filter('DISTRO_FEATURES', 'opengl', d)}"
>
> +PACKAGECONFIG_class-native = "x11"
> +PACKAGECONFIG_class-nativesdk = "${@bb.utils.filter('DISTRO_FEATURES', 
> 'x11', d)}"
>  PACKAGECONFIG ??= " \
>  ${PACKAGECONFIG_GL} \
>  ${@bb.utils.filter('DISTRO_FEATURES', 'alsa directfb pulseaudio x11', 
> d)} \
> @@ -63,3 +65,5 @@ do_configure_prepend() {
>  }
>
>  FILES_${PN}-dev += "${libdir}/cmake"
> +
> +BBCLASSEXTEND = "native nativesdk"
> --
> 2.17.0
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH] recipes-graphics/libsdl2: Add native and nativesdk support

2018-05-11 Thread Alistair Francis
On Fri, May 11, 2018 at 12:44 PM, Martin Jansa  wrote:
> On Thu, May 10, 2018 at 03:06:47PM -0700, Alistair Francis wrote:
>> On Thu, May 10, 2018 at 2:58 PM, Martin Jansa  wrote:
>> > See http://git.openembedded.org/openembedded-core-contrib/log/?h=jansa/qemu
>> > + http://git.openembedded.org/meta-openembedded-contrib/log/?h=jansa/spice
>> > for more qemu related changes.
>> >
>> > More info:
>> > http://lists.openembedded.org/pipermail/openembedded-core/2017-September/142349.html
>> >
>> > and that's basically where I'm still stuck (and why haven't sent most of
>> > these patches yet), because it works fine "natively" but when the
>> > qemu-native is running inside of chroot or docker, I didn't get the
>> > acceleration working (from virt-viewer running "natively" - outside
>> > chroot/docker).
>> >
>> > I plan to separate libsdl2 changes from this and send them with updated 
>> > qemu
>> > upgrade as discussed with Ross.
>>
>> It looks like you beat me to it. Plus your patches look better then mine :)
>>
>> It would be great if you could send the QEMU 2.12 patches seperatly.
>> Can you CC me when you do?
>
> I've forgot to CC you, but the 2 patchsets I've sent today are:
> http://lists.openembedded.org/pipermail/openembedded-core/2018-May/150717.html
> http://lists.openembedded.org/pipermail/openembedded-devel/2018-May/118144.html
>
> that leaves only virglrenderer and glx support in jansa/qemu branch.

Great, Thanks. I have reviewed them, although I'm not sure if that
matters for this project.

Alistair

>
>> >
>> > On Thu, May 10, 2018 at 11:31 PM Alistair Francis 
>> > 
>> > wrote:
>> >>
>> >> Allow building libsdl2 for native and nativesdk. This is required to use
>> >> libsdl2 in QEMU.
>> >>
>> >> Signed-off-by: Alistair Francis 
>> >> ---
>> >>  meta/recipes-graphics/libsdl2/libsdl2_2.0.8.bb | 7 +++
>> >>  1 file changed, 7 insertions(+)
>> >>
>> >> diff --git a/meta/recipes-graphics/libsdl2/libsdl2_2.0.8.bb
>> >> b/meta/recipes-graphics/libsdl2/libsdl2_2.0.8.bb
>> >> index c0cf70d7fd..36508ec349 100644
>> >> --- a/meta/recipes-graphics/libsdl2/libsdl2_2.0.8.bb
>> >> +++ b/meta/recipes-graphics/libsdl2/libsdl2_2.0.8.bb
>> >> @@ -42,6 +42,11 @@ PACKAGECONFIG ??= " \
>> >>  ${@bb.utils.filter('DISTRO_FEATURES', 'alsa directfb pulseaudio x11',
>> >> d)} \
>> >>  ${@bb.utils.contains('DISTRO_FEATURES', 'wayland', 'wayland gles2',
>> >> '', d)} \
>> >>  "
>> >> +PACKAGECONFIG_class-native = "${PACKAGECONFIG_GL} x11"
>> >> +PACKAGECONFIG_class-nativesdk = "${PACKAGECONFIG_GL} \
>> >> + ${@bb.utils.filter('DISTRO_FEATURES',
>> >> 'x11', d)} \
>> >> +"
>> >> +
>> >>  PACKAGECONFIG[alsa]   = "--enable-alsa
>> >> --disable-alsatest,--disable-alsa,alsa-lib,"
>> >>  PACKAGECONFIG[directfb]   =
>> >> "--enable-video-directfb,--disable-video-directfb,directfb"
>> >>  PACKAGECONFIG[gles2]  =
>> >> "--enable-video-opengles,--disable-video-opengles,virtual/libgles2"
>> >> @@ -63,3 +68,5 @@ do_configure_prepend() {
>> >>  }
>> >>
>> >>  FILES_${PN}-dev += "${libdir}/cmake"
>> >> +
>> >> +BBCLASSEXTEND = "native nativesdk"
>> >> --
>> >> 2.17.0
>> >>
>> >
>
> --
> Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCHv2 3/5] qemu: refresh patches with devtool

2018-05-11 Thread Alistair Francis
On Fri, May 11, 2018 at 12:21 PM, Martin Jansa  wrote:
> From: Martin Jansa 
>
> Signed-off-by: Martin Jansa 
> Signed-off-by: Ross Burton 

Reviewed-by: Alistair Francis 

Alistair

> ---
>  .../qemu/qemu/add-ptest-in-makefile-v10.patch | 13 ---
>  .../qemu/apic-fixup-fallthrough-to-PIC.patch  | 15 
>  ...pus.c-qemu_cpu_kick_thread_debugging.patch | 12 +++
>  ...x-libcap-header-issue-on-some-distro.patch | 16 +
>  ...webkitgtk-hangs-on-32-bit-x86-target.patch | 10 +++---
>  .../qemu/qemu/no-valgrind.patch   | 19 --
>  .../qemu/qemu/pathlimit.patch | 35 ---
>  .../qemu/qemu-enlarge-env-entry-size.patch| 18 +-
>  meta/recipes-devtools/qemu/qemu/wacom.patch   | 24 -
>  9 files changed, 100 insertions(+), 62 deletions(-)
>
> diff --git a/meta/recipes-devtools/qemu/qemu/add-ptest-in-makefile-v10.patch 
> b/meta/recipes-devtools/qemu/qemu/add-ptest-in-makefile-v10.patch
> index e9639820be..3337d1c7ba 100644
> --- a/meta/recipes-devtools/qemu/qemu/add-ptest-in-makefile-v10.patch
> +++ b/meta/recipes-devtools/qemu/qemu/add-ptest-in-makefile-v10.patch
> @@ -1,7 +1,8 @@
> -From 4201a5791fc4798a45a9b9f881602d7bacb74ed1 Mon Sep 17 00:00:00 2001
> +From 6c01c969def7adae70d7d59a40b5640454b97bdb Mon Sep 17 00:00:00 2001
>  From: Juro Bystricky 
>  Date: Thu, 31 Aug 2017 11:06:56 -0700
> -Subject: Add subpackage -ptest which runs all unit test cases for qemu.
> +Subject: [PATCH] Add subpackage -ptest which runs all unit test cases for
> + qemu.
>
>  Upstream-Status: Pending
>
> @@ -9,11 +10,15 @@ Signed-off-by: Kai Kang 
>
>  Signed-off-by: Juro Bystricky 
>
> +---
> + tests/Makefile.include | 8 
> + 1 file changed, 8 insertions(+)
> +
>  diff --git a/tests/Makefile.include b/tests/Makefile.include
> -index f08b741..3d1b3e9 100644
> +index 3b9a5e3..dfbcd72 100644
>  --- a/tests/Makefile.include
>  +++ b/tests/Makefile.include
> -@@ -924,4 +924,12 @@ all: $(QEMU_IOTESTS_HELPERS-y)
> +@@ -972,4 +972,12 @@ all: $(QEMU_IOTESTS_HELPERS-y)
>   -include $(wildcard tests/*.d)
>   -include $(wildcard tests/libqos/*.d)
>
> diff --git 
> a/meta/recipes-devtools/qemu/qemu/apic-fixup-fallthrough-to-PIC.patch 
> b/meta/recipes-devtools/qemu/qemu/apic-fixup-fallthrough-to-PIC.patch
> index d6a3522eda..8ba507c9ff 100644
> --- a/meta/recipes-devtools/qemu/qemu/apic-fixup-fallthrough-to-PIC.patch
> +++ b/meta/recipes-devtools/qemu/qemu/apic-fixup-fallthrough-to-PIC.patch
> @@ -1,7 +1,7 @@
> -From bef93bb81588b5323a52d2e1886f2a77b64a976b Mon Sep 17 00:00:00 2001
> +From ca247c6e7ab7a0bd7b94658a726940f10a6b0559 Mon Sep 17 00:00:00 2001
>  From: Mark Asselstine 
>  Date: Tue, 26 Feb 2013 11:43:28 -0500
> -Subject: [PATCH 03/18] apic: fixup fallthrough to PIC
> +Subject: [PATCH] apic: fixup fallthrough to PIC
>
>  Commit 0e21e12bb311c4c1095d0269dc2ef81196ccb60a [Don't route PIC
>  interrupts through the local APIC if the local APIC config says so.]
> @@ -24,15 +24,16 @@ serviced, is -1.
>  Signed-off-by: Mark Asselstine 
>  Upstream-Status: Submitted 
> [https://lists.gnu.org/archive/html/qemu-devel/2013-04/msg00878.html]
>  Signed-off-by: He Zhe 
> +
>  ---
>   hw/intc/apic.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> -Index: qemu-2.11.1/hw/intc/apic.c
> -===
>  qemu-2.11.1.orig/hw/intc/apic.c
> -+++ qemu-2.11.1/hw/intc/apic.c
> -@@ -591,7 +591,7 @@ int apic_accept_pic_intr(DeviceState *de
> +diff --git a/hw/intc/apic.c b/hw/intc/apic.c
> +index 6fda52b..cd72919 100644
> +--- a/hw/intc/apic.c
>  b/hw/intc/apic.c
> +@@ -603,7 +603,7 @@ int apic_accept_pic_intr(DeviceState *dev)
>   APICCommonState *s = APIC(dev);
>   uint32_t lvt0;
>
> diff --git 
> a/meta/recipes-devtools/qemu/qemu/cpus.c-qemu_cpu_kick_thread_debugging.patch 
> b/meta/recipes-devtools/qemu/qemu/cpus.c-qemu_cpu_kick_thread_debugging.patch
> index 6822132541..46c82a4aea 100644
> --- 
> a/meta/recipes-devtools/qemu/qemu/cpus.c-qemu_cpu_kick_thread_debugging.patch
> +++ 
> b/meta/recipes-devtools/qemu/qemu/cpus.c-qemu_cpu_kick_thread_debugging.patch
> @@ -1,4 +1,4 @@
> -From 697a834c35d19447b7dcdb9e1d9434bc6ce17c21 Mon Sep 17 00:00:00 2001
> +From a2e3ad8e3bbdea20a4c53404674dd8ae46bd2528 Mon Sep 17 00:00:00 2001
>  From: =?UTF-8?q?An=C3=ADbal=20Lim=C3=B3n?= 
>  Date: Wed, 12 Aug 2015 15:11:30 -0500
>  Subject: [PATCH] cpus.c: Add error messages when qemi_cpu_kick_thread fails.
> @@ -12,6 +12,7 @@ current cpu information.
>
>  Upstream-Status: Inappropriate
>  Signed-off-by: Aníbal Limón 
> +
>  ---
>   cpus.c |  5 +
>   

Re: [OE-core] [PATCHv2 2/5] qemu: upgrade to 2.12.0

2018-05-11 Thread Alistair Francis
On Fri, May 11, 2018 at 12:21 PM, Martin Jansa  wrote:
> From: Martin Jansa 
>
> * drop patches which are now included upstream
>
> Signed-off-by: Martin Jansa 
> Signed-off-by: Ross Burton 

Reviewed-by: Alistair Francis 

Alistair

> ---
>  meta/conf/distro/include/tcmode-default.inc   |  2 +-
>  ...4-treat-DISAS_UPDATE-as-variant-of-D.patch | 67 ---
>  ...-connect-socket-to-a-spawned-command.patch | 52 +++---
>  ...2Queue-pointers-in-post_load-routine.patch | 63 -
>  .../qemu/qemu/disable-grabs.patch | 43 ++--
>  meta/recipes-devtools/qemu/qemu/memfd.patch   | 57 
>  .../qemu/qemu/qemu-2.5.0-cflags.patch | 15 -
>  .../qemu/{qemu_2.11.1.bb => qemu_2.12.0.bb}   |  7 +-
>  8 files changed, 65 insertions(+), 241 deletions(-)
>  delete mode 100644 
> meta/recipes-devtools/qemu/qemu/0001-arm-translate-a64-treat-DISAS_UPDATE-as-variant-of-D.patch
>  delete mode 100644 
> meta/recipes-devtools/qemu/qemu/check-PS2Queue-pointers-in-post_load-routine.patch
>  delete mode 100644 meta/recipes-devtools/qemu/qemu/memfd.patch
>  rename meta/recipes-devtools/qemu/{qemu_2.11.1.bb => qemu_2.12.0.bb} (84%)
>
> diff --git a/meta/conf/distro/include/tcmode-default.inc 
> b/meta/conf/distro/include/tcmode-default.inc
> index b197819e9e..5271b41860 100644
> --- a/meta/conf/distro/include/tcmode-default.inc
> +++ b/meta/conf/distro/include/tcmode-default.inc
> @@ -28,7 +28,7 @@ BINUVERSION ?= "2.30%"
>  GDBVERSION ?= "8.1%"
>  GLIBCVERSION ?= "2.27%"
>  LINUXLIBCVERSION ?= "4.15%"
> -QEMUVERSION ?= "2.11%"
> +QEMUVERSION ?= "2.12%"
>
>  PREFERRED_VERSION_gcc ?= "${GCCVERSION}"
>  PREFERRED_VERSION_gcc-cross-${TARGET_ARCH} ?= "${GCCVERSION}"
> diff --git 
> a/meta/recipes-devtools/qemu/qemu/0001-arm-translate-a64-treat-DISAS_UPDATE-as-variant-of-D.patch
>  
> b/meta/recipes-devtools/qemu/qemu/0001-arm-translate-a64-treat-DISAS_UPDATE-as-variant-of-D.patch
> deleted file mode 100644
> index f90cae694c..00
> --- 
> a/meta/recipes-devtools/qemu/qemu/0001-arm-translate-a64-treat-DISAS_UPDATE-as-variant-of-D.patch
> +++ /dev/null
> @@ -1,67 +0,0 @@
> -From a75a52d62418dafe462be4fe30485501d1010bb9 Mon Sep 17 00:00:00 2001
> -From: Victor Kamensky 
> -Date: Fri, 23 Mar 2018 18:26:45 +
> -Subject: [PATCH] arm/translate-a64: treat DISAS_UPDATE as variant of
> - DISAS_EXIT
> -MIME-Version: 1.0
> -Content-Type: text/plain; charset=UTF-8
> -Content-Transfer-Encoding: 8bit
> -
> -In OE project 4.15 linux kernel boot hang was observed under
> -single cpu aarch64 qemu. Kernel code was in a loop waiting for
> -vtimer arrival, spinning in TC generated blocks, while interrupt
> -was pending unprocessed. This happened because when qemu tried to
> -handle vtimer interrupt target had interrupts disabled, as
> -result flag indicating TCG exit, cpu->icount_decr.u16.high,
> -was cleared but arm_cpu_exec_interrupt function did not call
> -arm_cpu_do_interrupt to process interrupt. Later when target
> -reenabled interrupts, it happened without exit into main loop, so
> -following code that waited for result of interrupt execution
> -run in infinite loop.
> -
> -To solve the problem instructions that operate on CPU sys state
> -(i.e enable/disable interrupt), and marked as DISAS_UPDATE,
> -should be considered as DISAS_EXIT variant, and should be
> -forced to exit back to main loop so qemu will have a chance
> -processing pending CPU state updates, including pending
> -interrupts.
> -
> -This change brings consistency with how DISAS_UPDATE is treated
> -in aarch32 case.
> -
> -CC: Peter Maydell 
> -CC: Alex Bennée 
> -CC: qemu-sta...@nongnu.org
> -Suggested-by: Peter Maydell 
> -Signed-off-by: Victor Kamensky 
> -Reviewed-by: Richard Henderson 
> -Message-id: 1521526368-1996-1-git-send-email-kamen...@cisco.com
> -Signed-off-by: Peter Maydell 
> -Upstream-Status: Backport
> 
> - target/arm/translate-a64.c | 6 +++---
> - 1 file changed, 3 insertions(+), 3 deletions(-)
> -
> -diff --git a/target/arm/translate-a64.c b/target/arm/translate-a64.c
> -index 31ff047..327513e 100644
>  a/target/arm/translate-a64.c
> -+++ b/target/arm/translate-a64.c
> -@@ -13378,12 +13378,12 @@ static void aarch64_tr_tb_stop(DisasContextBase 
> *dcbase, CPUState *cpu)
> - case DISAS_UPDATE:
> - gen_a64_set_pc_im(dc->pc);
> - /* fall through */
> --case DISAS_JUMP:
> --tcg_gen_lookup_and_goto_ptr();
> --break;
> - case DISAS_EXIT:
> - tcg_gen_exit_tb(0);
> - break;
> -+case DISAS_JUMP:
> -+tcg_gen_lookup_and_goto_ptr();
> -+break;
> - case DISAS_NORETURN:

Re: [OE-core] do_kernel_configme and defconfig

2018-05-11 Thread Bruce Ashfield
On Fri, May 11, 2018 at 6:17 PM,  wrote:

> Hi Bruce,
>
>
>
> Thanks for your insights. The defconfig is coming from
> KBUILD_DEFCONFIG_machinename = “our_defconfig” in our machine conf. I
> understand that the defconfig is just another configuration fragment, but
> given that it has its own variable (KBUILD_DEFCONFIG) I guess I was
> expecting a bit of “magic” out of it; namely, ordering such that the
> fragment called “defconfig” comes first. Otherwise I don’t really see the
> point in supporting in-tree defconfig + .scc/cfg fragments, since the
> former will just wipe out the latter.
>
>
>
> That being said, your explanation of the current behavior makes sense, but
> I think it should be emphasized somewhere in the manual. Care if I submit a
> documentation patch?
>

Absolutely! Feel free to cc' me on the patch and I'll give it a review as
well.

Bruce


>
>
> Thanks,
> Chris
>
>
>
> *From:* Bruce Ashfield [mailto:bruce.ashfi...@gmail.com]
> *Sent:* Friday, May 11, 2018 5:09 PM
> *To:* LAPLANTE,CHRIS (A-Little Falls,ex1) 
> *Cc:* Patches and discussions about the oe-core layer <
> openembedded-core@lists.openembedded.org>; SMITH,JARED (A-Little
> Falls,ex1) 
> *Subject:* Re: [OE-core] do_kernel_configme and defconfig
>
>
>
>
>
>
>
> On Fri, May 11, 2018 at 3:28 PM, Chris Laplante via Openembedded-core <
> openembedded-core@lists.openembedded.org> wrote:
>
> OK, I figured out why this happens. This line in kernel-yocto.bbclass:
>
>
>
> scc --force -o ${S}/${meta_dir}:cfg,merge,meta ${includes}
> ${bsp_definition} ${sccs} ${patches} ${KERNEL_FEATURES}
>
>
>
> … passes the BSP def before the sccs. In my case, the BSP def is
> mymachine.scc, and the sccs is the defconfig. So that’s why the defconfig
> comes after the BSP.
>
>
>
> My takeaway is that a BSP plus a defconfig is not a supported use case. Is
> that correct?
>
>
>
> A defconfig isn't magic, it is just another input to the configuration
> merging. It will be applied as any other fragment. There is some special
> processing only a defconfig is specified, but otherwise, it is the same. So
> in this case, whatever it sets would be applied after the BSP definition
> and would take precedence (last through the gate wins).
>
>
>
> If you have a BSP definition, you normally don't have a defconfig. Where
> is the defconfig coming from in your scenario ? The SRC_URI ? You can just
> include it from the .scc files to control the order, which is what is
> expected when you have a BSP definition.
>
>
>
> Were you seeing none of your options set ? or something else ?
>
>
>
>
>
> If so, I think it’s important to add some sanity checking to
> kernel-yocto.bbclass.
>
>
>
>
>
> There's really nothing that could be checked, since the intent of the
> fragments isn't known, and for the most part, defconfigs are the same as
> any other fragment (from the point of view of the merging).
>
>
>
> Bruce
>
>
>
> Thanks,
>
> Chris
>
>
>
> *From:* openembedded-core-boun...@lists.openembedded.org [mailto:
> openembedded-core-boun...@lists.openembedded.org] *On Behalf Of *Chris
> Laplante via Openembedded-core
> *Sent:* Friday, May 11, 2018 2:51 PM
> *To:* openembedded-core@lists.openembedded.org
> *Cc:* SMITH,JARED (A-Little Falls,ex1) 
> *Subject:* [OE-core] do_kernel_configme and defconfig
>
>
>
> Hi all,
>
>
>
> Is it expected for do_kernel_configme to apply the defconfig last (after
> configuration fragments introduced by sccs)?
>
>
>
> For some reason, in the call to merge_config, 
> “.kernel-meta/configs//./defconfig”
> is passed last whereas I’d expect it would be first (since that should be
> the base config). This is causing problems, because config options that my
> config fragments are setting are getting overridden by the defconfig – it
> should be the other way around.
>
>
>
> For reference, I’m using Rocko and have just updated to the latest commit.
> We have an in-tree defconfig, and we set KBUILD_DEFCONFIG_machinename
> appropriately. We are using the separate kernel-meta repository to store
> kernel metadata. I have KMACHINE_machinename set up so that it finds the
> correct BSP definition .scc file. Still seem to be missing something,
> though.
>
>
>
> Thanks,
>
> Chris
>
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
>
>
>
> --
>
> "Thou shalt not follow the NULL pointer, for chaos and madness await thee
> at its end"
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] do_kernel_configme and defconfig

2018-05-11 Thread Chris Laplante via Openembedded-core
Hi Bruce,

Thanks for your insights. The defconfig is coming from 
KBUILD_DEFCONFIG_machinename = “our_defconfig” in our machine conf. I 
understand that the defconfig is just another configuration fragment, but given 
that it has its own variable (KBUILD_DEFCONFIG) I guess I was expecting a bit 
of “magic” out of it; namely, ordering such that the fragment called 
“defconfig” comes first. Otherwise I don’t really see the point in supporting 
in-tree defconfig + .scc/cfg fragments, since the former will just wipe out the 
latter.

That being said, your explanation of the current behavior makes sense, but I 
think it should be emphasized somewhere in the manual. Care if I submit a 
documentation patch?

Thanks,
Chris

From: Bruce Ashfield [mailto:bruce.ashfi...@gmail.com]
Sent: Friday, May 11, 2018 5:09 PM
To: LAPLANTE,CHRIS (A-Little Falls,ex1) 
Cc: Patches and discussions about the oe-core layer 
; SMITH,JARED (A-Little Falls,ex1) 

Subject: Re: [OE-core] do_kernel_configme and defconfig



On Fri, May 11, 2018 at 3:28 PM, Chris Laplante via Openembedded-core 
>
 wrote:
OK, I figured out why this happens. This line in kernel-yocto.bbclass:

scc --force -o ${S}/${meta_dir}:cfg,merge,meta ${includes} ${bsp_definition} 
${sccs} ${patches} ${KERNEL_FEATURES}

… passes the BSP def before the sccs. In my case, the BSP def is mymachine.scc, 
and the sccs is the defconfig. So that’s why the defconfig comes after the BSP.

My takeaway is that a BSP plus a defconfig is not a supported use case. Is that 
correct?

A defconfig isn't magic, it is just another input to the configuration merging. 
It will be applied as any other fragment. There is some special processing only 
a defconfig is specified, but otherwise, it is the same. So in this case, 
whatever it sets would be applied after the BSP definition and would take 
precedence (last through the gate wins).

If you have a BSP definition, you normally don't have a defconfig. Where is the 
defconfig coming from in your scenario ? The SRC_URI ? You can just include it 
from the .scc files to control the order, which is what is expected when you 
have a BSP definition.

Were you seeing none of your options set ? or something else ?


If so, I think it’s important to add some sanity checking to 
kernel-yocto.bbclass.


There's really nothing that could be checked, since the intent of the fragments 
isn't known, and for the most part, defconfigs are the same as any other 
fragment (from the point of view of the merging).

Bruce

Thanks,
Chris

From: 
openembedded-core-boun...@lists.openembedded.org
 
[mailto:openembedded-core-boun...@lists.openembedded.org]
 On Behalf Of Chris Laplante via Openembedded-core
Sent: Friday, May 11, 2018 2:51 PM
To: 
openembedded-core@lists.openembedded.org
Cc: SMITH,JARED (A-Little Falls,ex1) 
>
Subject: [OE-core] do_kernel_configme and defconfig

Hi all,

Is it expected for do_kernel_configme to apply the defconfig last (after 
configuration fragments introduced by sccs)?

For some reason, in the call to merge_config, 
“.kernel-meta/configs//./defconfig” is passed last whereas I’d expect it would 
be first (since that should be the base config). This is causing problems, 
because config options that my config fragments are setting are getting 
overridden by the defconfig – it should be the other way around.

For reference, I’m using Rocko and have just updated to the latest commit. We 
have an in-tree defconfig, and we set KBUILD_DEFCONFIG_machinename 
appropriately. We are using the separate kernel-meta repository to store kernel 
metadata. I have KMACHINE_machinename set up so that it finds the correct BSP 
definition .scc file. Still seem to be missing something, though.

Thanks,
Chris

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



--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at 
its end"
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH v2 2/2] wic: add ontrack DM6 aux3 support

2018-05-11 Thread Burton, Ross
This one?  
http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=ross/mut=2e9012e6b44b83b3952598b08cd9d5dadd633b69

Ross

On 11 May 2018 at 20:33, Otavio Salvador
 wrote:
> On Fri, May 11, 2018 at 12:41 PM, Burton, Ross  wrote:
>> Somehow, these patches are causing selftest to fail:
>>
>> ERROR: Not supported fstype:
>>
>> https://autobuilder.yocto.io/builders/nightly-oe-selftest/builds/1051/steps/Running%20oe-selftest/logs/stdio
>
> You forgot the parted patch.
>
> --
> Otavio Salvador O.S. Systems
> http://www.ossystems.com.brhttp://code.ossystems.com.br
> Mobile: +55 (53) 9 9981-7854  Mobile: +1 (347) 903-9750
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [RFT] GCC 8.1

2018-05-11 Thread Burton, Ross
I threw the branch at the Yocto Project autobuilder today, produced a
number of failures:

http://errors.yoctoproject.org/Errors/Latest//?filter=b23dba19607412c8cc7d267d95354d65f5631088=commit

Ross

On 5 May 2018 at 01:26, Khem Raj  wrote:
> Hi All
>
> As you might have noticed that gcc 8.1 was released this week, I am
> calling out for some testing help on testing branch so we can weed out
> issues you might see in your setups. so if you have your
> builders idling over weekend, then you know what they can do this weekend :)
>
> Highlighted changes are
>
> https://gcc.gnu.org/gcc-8/changes.html
>
> and porting doc is
>
> https://gcc.gnu.org/gcc-8/porting_to.html
>
> The branch is here
>
> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/gcc-8
>
> Its uptodate on top of current master oe-core
>
> May fourth be with you !!
>
> Cheers!
>
> -Khem
> --
> ___
> 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] qemu: add gettext to DEPENDS

2018-05-11 Thread Chris Patterson
On Fri, May 11, 2018 at 5:32 PM, Martin Jansa  wrote:
> On Fri, May 11, 2018 at 05:21:09PM -0400, Chris Patterson wrote:
>> On Fri, May 11, 2018 at 3:10 PM, Christopher Larson  
>> wrote:
>> > This is not a correct fix. We have a gettext bbclass for a reason.
>> >
>>
>> I did look at that prior to doing this.  It was my initial approach,
>> but inheriting gettext causes qemu build to fail when it modifies the
>> EXTRA_OECONF options with the nls flag (that qemu doesn't process).
>> There are quite a few other recipes using gettext-native in their
>> DEPENDS, and the reason for one over the other isn't quite clear.
>>
>> In the other thread (v2), Khem requested it only be added
>> conditionally if the gtk packageconfig flag is enabled.  Do you think
>> it would be appropriate to check packageconfig flag, then
>> conditionally inherit, then resolve (scrub) the unsupported configure
>> flags? Or modify the class such that modifying the OECONF is prevented
>> to begin with?
>
> Are you using gtk PACKAGECONFIG for qemu-native (or nativesdk-qemu)?
> Last time I've tried I've found that there are many things missing to
> make it usable, see last few commits at:
> http://git.openembedded.org/openembedded-core-contrib/log/?h=jansa/qemu
>
> I haven't tried gtk(3) for target build, it probably works better there.
>

I was looking to use it in my image (non-native).  Thank you for the info!
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH] qemu: add gettext to DEPENDS

2018-05-11 Thread Martin Jansa
On Fri, May 11, 2018 at 05:21:09PM -0400, Chris Patterson wrote:
> On Fri, May 11, 2018 at 3:10 PM, Christopher Larson  wrote:
> > This is not a correct fix. We have a gettext bbclass for a reason.
> >
> 
> I did look at that prior to doing this.  It was my initial approach,
> but inheriting gettext causes qemu build to fail when it modifies the
> EXTRA_OECONF options with the nls flag (that qemu doesn't process).
> There are quite a few other recipes using gettext-native in their
> DEPENDS, and the reason for one over the other isn't quite clear.
> 
> In the other thread (v2), Khem requested it only be added
> conditionally if the gtk packageconfig flag is enabled.  Do you think
> it would be appropriate to check packageconfig flag, then
> conditionally inherit, then resolve (scrub) the unsupported configure
> flags? Or modify the class such that modifying the OECONF is prevented
> to begin with?

Are you using gtk PACKAGECONFIG for qemu-native (or nativesdk-qemu)?
Last time I've tried I've found that there are many things missing to
make it usable, see last few commits at:
http://git.openembedded.org/openembedded-core-contrib/log/?h=jansa/qemu

I haven't tried gtk(3) for target build, it probably works better there.

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


Re: [OE-core] [PATCH] qemu: add gettext to DEPENDS

2018-05-11 Thread Chris Patterson
On Fri, May 11, 2018 at 3:10 PM, Christopher Larson  wrote:
> This is not a correct fix. We have a gettext bbclass for a reason.
>

I did look at that prior to doing this.  It was my initial approach,
but inheriting gettext causes qemu build to fail when it modifies the
EXTRA_OECONF options with the nls flag (that qemu doesn't process).
There are quite a few other recipes using gettext-native in their
DEPENDS, and the reason for one over the other isn't quite clear.

In the other thread (v2), Khem requested it only be added
conditionally if the gtk packageconfig flag is enabled.  Do you think
it would be appropriate to check packageconfig flag, then
conditionally inherit, then resolve (scrub) the unsupported configure
flags? Or modify the class such that modifying the OECONF is prevented
to begin with?

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


Re: [OE-core] do_kernel_configme and defconfig

2018-05-11 Thread Bruce Ashfield
On Fri, May 11, 2018 at 3:28 PM, Chris Laplante via Openembedded-core <
openembedded-core@lists.openembedded.org> wrote:

> OK, I figured out why this happens. This line in kernel-yocto.bbclass:
>
>
>
> scc --force -o ${S}/${meta_dir}:cfg,merge,meta ${includes}
> ${bsp_definition} ${sccs} ${patches} ${KERNEL_FEATURES}
>
>
>
> … passes the BSP def before the sccs. In my case, the BSP def is
> mymachine.scc, and the sccs is the defconfig. So that’s why the defconfig
> comes after the BSP.
>
>
>
> My takeaway is that a BSP plus a defconfig is not a supported use case. Is
> that correct?
>

A defconfig isn't magic, it is just another input to the configuration
merging. It will be applied as any other fragment. There is some special
processing only a defconfig is specified, but otherwise, it is the same. So
in this case, whatever it sets would be applied after the BSP definition
and would take precedence (last through the gate wins).

If you have a BSP definition, you normally don't have a defconfig. Where is
the defconfig coming from in your scenario ? The SRC_URI ? You can just
include it from the .scc files to control the order, which is what is
expected when you have a BSP definition.

Were you seeing none of your options set ? or something else ?


>
>
> If so, I think it’s important to add some sanity checking to
> kernel-yocto.bbclass.
>
>
>

There's really nothing that could be checked, since the intent of the
fragments isn't known, and for the most part, defconfigs are the same as
any other fragment (from the point of view of the merging).

Bruce


> Thanks,
>
> Chris
>
>
>
> *From:* openembedded-core-boun...@lists.openembedded.org [mailto:
> openembedded-core-boun...@lists.openembedded.org] *On Behalf Of *Chris
> Laplante via Openembedded-core
> *Sent:* Friday, May 11, 2018 2:51 PM
> *To:* openembedded-core@lists.openembedded.org
> *Cc:* SMITH,JARED (A-Little Falls,ex1) 
> *Subject:* [OE-core] do_kernel_configme and defconfig
>
>
>
> Hi all,
>
>
>
> Is it expected for do_kernel_configme to apply the defconfig last (after
> configuration fragments introduced by sccs)?
>
>
>
> For some reason, in the call to merge_config, 
> “.kernel-meta/configs//./defconfig”
> is passed last whereas I’d expect it would be first (since that should be
> the base config). This is causing problems, because config options that my
> config fragments are setting are getting overridden by the defconfig – it
> should be the other way around.
>
>
>
> For reference, I’m using Rocko and have just updated to the latest commit.
> We have an in-tree defconfig, and we set KBUILD_DEFCONFIG_machinename
> appropriately. We are using the separate kernel-meta repository to store
> kernel metadata. I have KMACHINE_machinename set up so that it finds the
> correct BSP definition .scc file. Still seem to be missing something,
> though.
>
>
>
> Thanks,
>
> Chris
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>


-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] Running BitBake multiple times without rechecking upstream AUTOREV versions

2018-05-11 Thread Chris Laplante via Openembedded-core
Hi all,

I'm working on using Jenkins to host our Yocto build. One of the things that 
would be nice is to be able to do a "bitbake our-user-image", upload the 
artifacts to our network file storage, and then do a "bitbake our-user-image -c 
populate_sdk_ext". I'd like to do these separately so that developers are not 
waiting around for the eSDK to be generated if all they care about is the 
kernel, for example. My concern is that the second bitbake invocation could end 
up building different stuff if someone were to check in code in between when 
the two "bitbake"s are run. This is primarily a concern with recipes that use 
AUTOREV (as we do for development purposes).

Is there a way to essentially "freeze" the BitBake data store and re-use it 
across multiple bitbake invocations?

I had a few ideas:

1. Use buildhistory-collect-srcrevs to generate the SRCREV_pn- overrides 
necessary to lock the SRCREVs of all the packages.
2. Use BB_SERVER_TIMEOUT = "-1" to force BitBake to remain resident - when 
BitBake is resident is seems to not reparse recipes. As I understand it, the 
recipe parse stage is when upstreams are checked for new revisions. Not sure if 
this would work.
3. Somehow use the locked siggens.


Is anything like this possible?

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


[OE-core] [OE-Core][PATCH 1/3] base-files: change permissions on /sys and /proc

2018-05-11 Thread Dan McGregor
From: Dan McGregor 

Fedora uses permissions of 555 for /proc and /sys. Debian doesn't
seem to explicitly set their permissions. In addition they're mounted
555.  Having them be 755 causes permission issues on upgrades inside a
container when the guest does not have the permission to change their
modes.

So, just bite the bullet and force them to be 555.

Signed-off-by: Dan McGregor 
---
 meta/recipes-core/base-files/base-files_3.0.14.bb | 8 ++--
 1 file changed, 6 insertions(+), 2 deletions(-)

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 1c0863b1c7b..a6963ba24d6 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
@@ -32,15 +32,16 @@ INHIBIT_DEFAULT_DEPS = "1"
 docdir_append = "/${P}"
 dirs1777 = "/tmp ${localstatedir}/volatile/tmp"
 dirs2775 = ""
+dirs555 = "/sys /proc"
 dirs755 = "/boot /dev ${base_bindir} ${base_sbindir} ${base_libdir} \
${sysconfdir} ${sysconfdir}/default \
-   ${sysconfdir}/skel ${nonarch_base_libdir} /mnt /proc ${ROOT_HOME} 
/run \
+   ${sysconfdir}/skel ${nonarch_base_libdir} /mnt ${ROOT_HOME} /run \
${prefix} ${bindir} ${docdir} /usr/games ${includedir} \
${libdir} ${sbindir} ${datadir} \
${datadir}/common-licenses ${datadir}/dict ${infodir} \
${mandir} ${datadir}/misc ${localstatedir} \
${localstatedir}/backups ${localstatedir}/lib \
-   /sys ${localstatedir}/lib/misc ${localstatedir}/spool \
+   ${localstatedir}/lib/misc ${localstatedir}/spool \
${localstatedir}/volatile \
${localstatedir}/${@'volatile/' if 
oe.types.boolean('${VOLATILE_LOG_DIR}') else ''}log \
/home ${prefix}/src ${localstatedir}/local \
@@ -93,6 +94,9 @@ pkg_preinst_${PN} () {
 }
 
 do_install () {
+   for d in ${dirs555}; do
+   install -m 0555 -d ${D}$d
+   done
for d in ${dirs755}; do
install -m 0755 -d ${D}$d
done
-- 
2.18.0-dev

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


[OE-core] [OE-Core][PATCH 2/3] base-files: use /proc/self/mounts for /etc/mtab

2018-05-11 Thread Dan McGregor
From: Dan McGregor 

It should be /proc/self/mounts instead of /proc/mounts. Also switch to
using a relative link in base-files, as seems to be the convention in
other distributions.

Signed-off-by: Dan McGregor 
---
 meta/recipes-core/base-files/base-files_3.0.14.bb | 2 +-
 .../initrdscripts/files/init-install-efi-testfs.sh| 2 +-
 meta/recipes-core/initrdscripts/files/init-install-efi.sh | 4 ++--
 meta/recipes-core/initrdscripts/files/init-install-testfs.sh  | 2 +-
 meta/recipes-core/initrdscripts/files/init-install.sh | 4 ++--
 meta/recipes-core/initscripts/initscripts-1.0/checkroot.sh| 2 +-
 6 files changed, 8 insertions(+), 8 deletions(-)

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 a6963ba24d6..a4c22c51c77 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
@@ -132,7 +132,7 @@ do_install () {
install -m 0644 ${WORKDIR}/host.conf ${D}${sysconfdir}/host.conf
install -m 0644 ${WORKDIR}/motd ${D}${sysconfdir}/motd
 
-   ln -sf /proc/mounts ${D}${sysconfdir}/mtab
+   ln -sf ${@oe.path.relative('${sysconfdir}', '/proc/self/mounts')} 
${D}${sysconfdir}/mtab
 }
 
 DISTRO_VERSION[vardepsexclude] += "DATE"
diff --git a/meta/recipes-core/initrdscripts/files/init-install-efi-testfs.sh 
b/meta/recipes-core/initrdscripts/files/init-install-efi-testfs.sh
index 9c4b263d544..60c290e1052 100644
--- a/meta/recipes-core/initrdscripts/files/init-install-efi-testfs.sh
+++ b/meta/recipes-core/initrdscripts/files/init-install-efi-testfs.sh
@@ -67,7 +67,7 @@ rm -f /etc/udev/scripts/mount*
 umount /dev/${device}* 2> /dev/null || /bin/true
 
 mkdir -p /tmp
-cat /proc/mounts > /etc/mtab
+cat /proc/self/mounts > /etc/mtab
 
 disk_size=$(parted /dev/${device} unit mb print | grep '^Disk .*: .*MB' | cut 
-d" " -f 3 | sed -e "s/MB//")
 
diff --git a/meta/recipes-core/initrdscripts/files/init-install-efi.sh 
b/meta/recipes-core/initrdscripts/files/init-install-efi.sh
index 82b0aa819e3..838bc83fdb8 100644
--- a/meta/recipes-core/initrdscripts/files/init-install-efi.sh
+++ b/meta/recipes-core/initrdscripts/files/init-install-efi.sh
@@ -141,8 +141,8 @@ umount ${device}* 2> /dev/null || /bin/true
 mkdir -p /tmp
 
 # Create /etc/mtab if not present
-if [ ! -e /etc/mtab ] && [ -e /proc/mounts ]; then
-ln -sf /proc/mounts /etc/mtab
+if [ ! -e /etc/mtab ] && [ -e /proc/self/mounts ]; then
+ln -sf /proc/self/mounts /etc/mtab
 fi
 
 disk_size=$(parted ${device} unit mb print | grep '^Disk .*: .*MB' | cut -d" " 
-f 3 | sed -e "s/MB//")
diff --git a/meta/recipes-core/initrdscripts/files/init-install-testfs.sh 
b/meta/recipes-core/initrdscripts/files/init-install-testfs.sh
index ac621605287..c5b435286e7 100644
--- a/meta/recipes-core/initrdscripts/files/init-install-testfs.sh
+++ b/meta/recipes-core/initrdscripts/files/init-install-testfs.sh
@@ -91,7 +91,7 @@ fi
 
 mkdir -p /tmp
 if [ ! -L /etc/mtab ]; then
-   cat /proc/mounts > /etc/mtab
+   cat /proc/self/mounts > /etc/mtab
 fi
 
 disk_size=$(parted /dev/${device} unit mb print | grep Disk | cut -d" " -f 3 | 
sed -e "s/MB//")
diff --git a/meta/recipes-core/initrdscripts/files/init-install.sh 
b/meta/recipes-core/initrdscripts/files/init-install.sh
index 28e8f09d19d..e203caa32f1 100644
--- a/meta/recipes-core/initrdscripts/files/init-install.sh
+++ b/meta/recipes-core/initrdscripts/files/init-install.sh
@@ -137,8 +137,8 @@ if [ ! -b /dev/loop0 ] ; then
 fi
 
 mkdir -p /tmp
-if [ ! -L /etc/mtab ] && [ -e /proc/mounts ]; then
-ln -sf /proc/mounts /etc/mtab
+if [ ! -L /etc/mtab ] && [ -e /proc/self/mounts ]; then
+ln -sf /proc/self/mounts /etc/mtab
 fi
 
 disk_size=$(parted ${device} unit mb print | grep '^Disk .*: .*MB' | cut -d" " 
-f 3 | sed -e "s/MB//")
diff --git a/meta/recipes-core/initscripts/initscripts-1.0/checkroot.sh 
b/meta/recipes-core/initscripts/initscripts-1.0/checkroot.sh
index 02f0351fcb3..db472ac2676 100755
--- a/meta/recipes-core/initscripts/initscripts-1.0/checkroot.sh
+++ b/meta/recipes-core/initscripts/initscripts-1.0/checkroot.sh
@@ -142,7 +142,7 @@ fi
 mount -n -o remount,$rootmode /
 if test "$rootmode" = rw
 then
-   ln -sf /proc/mounts /dev/mtab
+   ln -sf /proc/self/mounts /dev/mtab
 fi
 
 : exit 0
-- 
2.18.0-dev

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


[OE-core] [OE-Core][PATCH 3/3] base-files: make root home mode customisable

2018-05-11 Thread Dan McGregor
From: Dan McGregor 

Signed-off-by: Dan McGregor 
---
 meta/conf/bitbake.conf| 1 +
 meta/files/fs-perms-persistent-log.txt| 4 ++--
 meta/files/fs-perms.txt   | 4 ++--
 meta/recipes-core/base-files/base-files_3.0.14.bb | 4 +++-
 4 files changed, 8 insertions(+), 5 deletions(-)

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index a21b7282fbd..cd07b86a99c 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -84,6 +84,7 @@ USRBINPATH_class-nativesdk = "/usr/bin"
 
 # Root home directory
 ROOT_HOME ??= "/home/root"
+ROOT_HOME_MODE ??= "0700"
 
 # If set to boolean true ('yes', 'y', 'true', 't', '1'), /var/log links to 
/var/volatile/log.
 # If set to boolean false ('no', 'n', 'false', 'f', '0'), /var/log is on 
persistent storage.
diff --git a/meta/files/fs-perms-persistent-log.txt 
b/meta/files/fs-perms-persistent-log.txt
index 3a7cf3ab945..e16c4464843 100644
--- a/meta/files/fs-perms-persistent-log.txt
+++ b/meta/files/fs-perms-persistent-log.txt
@@ -59,8 +59,8 @@ ${localstatedir}/local0755rootroot
false - - -
 /tmp   01777   rootrootfalse - - -
 ${localstatedir}/volatile/tmp  01777   rootrootfalse - - -
 
-# Set 0700
-${ROOT_HOME}   0700rootrootfalse - - -
+# Set ${ROOT_HOME_MODE}, by default 0700.
+${ROOT_HOME}   ${ROOT_HOME_MODE}   rootrootfalse - 
- -
 
 # Set 2775-lsb
 ${localstatedir}/mail  02775   rootmailfalse - - -
diff --git a/meta/files/fs-perms.txt b/meta/files/fs-perms.txt
index c8c3ac5dbed..ad180399105 100644
--- a/meta/files/fs-perms.txt
+++ b/meta/files/fs-perms.txt
@@ -60,8 +60,8 @@ ${localstatedir}/local0755rootroot
false - - -
 /tmp   01777   rootrootfalse - - -
 ${localstatedir}/volatile/tmp  01777   rootrootfalse - - -
 
-# Set 0700
-${ROOT_HOME}   0700rootrootfalse - - -
+# Set ${ROOT_HOME_MODE}, by default 0700.
+${ROOT_HOME}   ${ROOT_HOME_MODE}   rootrootfalse - 
- -
 
 # Set 2775-lsb
 ${localstatedir}/mail  02775   rootmailfalse - - -
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 a4c22c51c77..6267b649465 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
@@ -35,7 +35,7 @@ dirs2775 = ""
 dirs555 = "/sys /proc"
 dirs755 = "/boot /dev ${base_bindir} ${base_sbindir} ${base_libdir} \
${sysconfdir} ${sysconfdir}/default \
-   ${sysconfdir}/skel ${nonarch_base_libdir} /mnt ${ROOT_HOME} /run \
+   ${sysconfdir}/skel ${nonarch_base_libdir} /mnt /run \
${prefix} ${bindir} ${docdir} /usr/games ${includedir} \
${libdir} ${sbindir} ${datadir} \
${datadir}/common-licenses ${datadir}/dict ${infodir} \
@@ -110,6 +110,8 @@ do_install () {
ln -sf volatile/$d ${D}${localstatedir}/$d
done
 
+   install -m ${ROOT_HOME_MODE} -d ${D}${ROOT_HOME}
+
ln -snf ../run ${D}${localstatedir}/run
ln -snf ../run/lock ${D}${localstatedir}/lock
 
-- 
2.18.0-dev

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


Re: [OE-core] [PATCH] recipes-graphics/libsdl2: Add native and nativesdk support

2018-05-11 Thread Martin Jansa
On Thu, May 10, 2018 at 03:06:47PM -0700, Alistair Francis wrote:
> On Thu, May 10, 2018 at 2:58 PM, Martin Jansa  wrote:
> > See http://git.openembedded.org/openembedded-core-contrib/log/?h=jansa/qemu
> > + http://git.openembedded.org/meta-openembedded-contrib/log/?h=jansa/spice
> > for more qemu related changes.
> >
> > More info:
> > http://lists.openembedded.org/pipermail/openembedded-core/2017-September/142349.html
> >
> > and that's basically where I'm still stuck (and why haven't sent most of
> > these patches yet), because it works fine "natively" but when the
> > qemu-native is running inside of chroot or docker, I didn't get the
> > acceleration working (from virt-viewer running "natively" - outside
> > chroot/docker).
> >
> > I plan to separate libsdl2 changes from this and send them with updated qemu
> > upgrade as discussed with Ross.
> 
> It looks like you beat me to it. Plus your patches look better then mine :)
> 
> It would be great if you could send the QEMU 2.12 patches seperatly.
> Can you CC me when you do?

I've forgot to CC you, but the 2 patchsets I've sent today are:
http://lists.openembedded.org/pipermail/openembedded-core/2018-May/150717.html
http://lists.openembedded.org/pipermail/openembedded-devel/2018-May/118144.html

that leaves only virglrenderer and glx support in jansa/qemu branch.

> >
> > On Thu, May 10, 2018 at 11:31 PM Alistair Francis 
> > wrote:
> >>
> >> Allow building libsdl2 for native and nativesdk. This is required to use
> >> libsdl2 in QEMU.
> >>
> >> Signed-off-by: Alistair Francis 
> >> ---
> >>  meta/recipes-graphics/libsdl2/libsdl2_2.0.8.bb | 7 +++
> >>  1 file changed, 7 insertions(+)
> >>
> >> diff --git a/meta/recipes-graphics/libsdl2/libsdl2_2.0.8.bb
> >> b/meta/recipes-graphics/libsdl2/libsdl2_2.0.8.bb
> >> index c0cf70d7fd..36508ec349 100644
> >> --- a/meta/recipes-graphics/libsdl2/libsdl2_2.0.8.bb
> >> +++ b/meta/recipes-graphics/libsdl2/libsdl2_2.0.8.bb
> >> @@ -42,6 +42,11 @@ PACKAGECONFIG ??= " \
> >>  ${@bb.utils.filter('DISTRO_FEATURES', 'alsa directfb pulseaudio x11',
> >> d)} \
> >>  ${@bb.utils.contains('DISTRO_FEATURES', 'wayland', 'wayland gles2',
> >> '', d)} \
> >>  "
> >> +PACKAGECONFIG_class-native = "${PACKAGECONFIG_GL} x11"
> >> +PACKAGECONFIG_class-nativesdk = "${PACKAGECONFIG_GL} \
> >> + ${@bb.utils.filter('DISTRO_FEATURES',
> >> 'x11', d)} \
> >> +"
> >> +
> >>  PACKAGECONFIG[alsa]   = "--enable-alsa
> >> --disable-alsatest,--disable-alsa,alsa-lib,"
> >>  PACKAGECONFIG[directfb]   =
> >> "--enable-video-directfb,--disable-video-directfb,directfb"
> >>  PACKAGECONFIG[gles2]  =
> >> "--enable-video-opengles,--disable-video-opengles,virtual/libgles2"
> >> @@ -63,3 +68,5 @@ do_configure_prepend() {
> >>  }
> >>
> >>  FILES_${PN}-dev += "${libdir}/cmake"
> >> +
> >> +BBCLASSEXTEND = "native nativesdk"
> >> --
> >> 2.17.0
> >>
> >

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


Re: [OE-core] [PATCH v2 2/2] wic: add ontrack DM6 aux3 support

2018-05-11 Thread Otavio Salvador
On Fri, May 11, 2018 at 12:41 PM, Burton, Ross  wrote:
> Somehow, these patches are causing selftest to fail:
>
> ERROR: Not supported fstype:
>
> https://autobuilder.yocto.io/builders/nightly-oe-selftest/builds/1051/steps/Running%20oe-selftest/logs/stdio

You forgot the parted patch.

-- 
Otavio Salvador O.S. Systems
http://www.ossystems.com.brhttp://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854  Mobile: +1 (347) 903-9750
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH] distcc: update to 3.3

2018-05-11 Thread akuster808


On 05/10/2018 05:02 AM, Burton, Ross wrote:
> Hi Jackie,
>
> Did you get to look at the distcc 3.3 upgrade failures?  We're open
> again for updates and moving to 3.3 instead of a forked repository on
> Armin's personal github would be nice!
yes it would.

- armin
>
> Ross
>
> On 22 March 2018 at 01:09, Huang, Jackie (Wind River)
>  wrote:
>> I will take a look and fix, thanks!
>>
>>
>>
>> Thanks,
>>
>> Jackie
>>
>>
>>
>> From: Burton, Ross [mailto:ross.bur...@intel.com]
>> Sent: Wednesday, March 21, 2018 18:44
>> To: Huang, Jie (Jackie)
>> Cc: OE-core
>> Subject: Re: [OE-core] [PATCH] distcc: update to 3.3
>>
>>
>>
>> This fails to start under systemd so caused the QA to fail:
>>
>>
>>
>> https://autobuilder.yocto.io/builders/nightly-qa-extras/builds/882/steps/Running%20Sanity%20Tests_7/logs/stdio
>>
>>
>>
>> Ross
>>
>>
>>
>> On 15 March 2018 at 08:24,  wrote:
>>
>> From: Jackie Huang 
>>
>> * update to version 3.3
>> * Remove 0001-zeroconf-Include-fcntl.h.patch since it's
>>   included in v3.3
>> * Add update-distcc-symlinks into FILES.
>>
>> Signed-off-by: Jackie Huang 
>> ---
>>  .../distcc/{distcc_3.2.bb => distcc_3.3.bb}| 10 +---
>>  .../files/0001-zeroconf-Include-fcntl.h.patch  | 29
>> --
>>  2 files changed, 6 insertions(+), 33 deletions(-)
>>  rename meta/recipes-devtools/distcc/{distcc_3.2.bb => distcc_3.3.bb} (91%)
>>  delete mode 100644
>> meta/recipes-devtools/distcc/files/0001-zeroconf-Include-fcntl.h.patch
>>
>> diff --git a/meta/recipes-devtools/distcc/distcc_3.2.bb
>> b/meta/recipes-devtools/distcc/distcc_3.3.bb
>> similarity index 91%
>> rename from meta/recipes-devtools/distcc/distcc_3.2.bb
>> rename to meta/recipes-devtools/distcc/distcc_3.3.bb
>> index b6da65a582a..a266e7dde9b 100644
>> --- a/meta/recipes-devtools/distcc/distcc_3.2.bb
>> +++ b/meta/recipes-devtools/distcc/distcc_3.3.bb
>> @@ -14,14 +14,15 @@ PACKAGECONFIG[popt] =
>> "--without-included-popt,--with-included-popt,popt"
>>
>>  RRECOMMENDS_${PN} = "avahi-daemon"
>>
>> -SRC_URI = "git://github.com/distcc/distcc.git;branch=${PV} \
>> +SRC_URI = "git://github.com/distcc/distcc.git;branch=master \
>> file://separatebuilddir.patch \
>> -   file://0001-zeroconf-Include-fcntl.h.patch \
>> file://default \
>> file://distccmon-gnome.desktop \
>> file://distcc \
>> file://distcc.service"
>> -SRCREV = "d8b18df3e9dcbe4f092bed565835d3975e99432c"
>> +
>> +SRCREV = "002e68b766ccd7ad05551e67d162b71a7a773d0d"
>> +
>>  S = "${WORKDIR}/git"
>>  UPSTREAM_VERSION_UNKNOWN = "1"
>>
>> @@ -60,9 +61,10 @@ PACKAGES += "distcc-distmon-gnome"
>>
>>  FILES_${PN} = " ${sysconfdir} \
>> ${bindir}/distcc \
>> -${bindir}/lsdistcc \
>> +   ${bindir}/lsdistcc \
>> ${bindir}/distccd \
>> ${bindir}/distccmon-text \
>> +   ${sbindir}/update-distcc-symlinks \
>> ${systemd_unitdir}/system/distcc.service"
>>  FILES_distcc-distmon-gnome = "  ${bindir}/distccmon-gnome \
>> ${datadir}/distcc"
>> diff --git
>> a/meta/recipes-devtools/distcc/files/0001-zeroconf-Include-fcntl.h.patch
>> b/meta/recipes-devtools/distcc/files/0001-zeroconf-Include-fcntl.h.patch
>> deleted file mode 100644
>> index b17ec9c9599..000
>> --- a/meta/recipes-devtools/distcc/files/0001-zeroconf-Include-fcntl.h.patch
>> +++ /dev/null
>> @@ -1,29 +0,0 @@
>> -From 8331fc4759d809512f404e7a27f817ad6d616450 Mon Sep 17 00:00:00 2001
>> -From: Khem Raj 
>> -Date: Mon, 13 Apr 2015 18:00:33 -0700
>> -Subject: [PATCH] zeroconf: Include fcntl.h
>> -
>> -We need it for getting deinitions for O_* e.g. O_CREAT
>> -
>> -Upstream-Status: Pending
>> -
>> -Signed-off-by: Khem Raj 
>> 
>> - src/zeroconf.c | 1 +
>> - 1 file changed, 1 insertion(+)
>> -
>> -diff --git a/src/zeroconf.c b/src/zeroconf.c
>> -index 414ddc4..31bd33f 100644
>>  a/src/zeroconf.c
>> -+++ b/src/zeroconf.c
>> -@@ -33,6 +33,7 @@
>> - #include 
>> - #include 
>> - #include 
>> -+#include 
>> -
>> - #include 
>> - #include 
>> ---
>> -2.1.4
>> -
>> --
>> 2.13.0
>>
>> --
>> ___
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>
>>

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


Re: [OE-core] do_kernel_configme and defconfig

2018-05-11 Thread Chris Laplante via Openembedded-core
OK, I figured out why this happens. This line in kernel-yocto.bbclass:

scc --force -o ${S}/${meta_dir}:cfg,merge,meta ${includes} ${bsp_definition} 
${sccs} ${patches} ${KERNEL_FEATURES}

... passes the BSP def before the sccs. In my case, the BSP def is 
mymachine.scc, and the sccs is the defconfig. So that's why the defconfig comes 
after the BSP.

My takeaway is that a BSP plus a defconfig is not a supported use case. Is that 
correct?

If so, I think it's important to add some sanity checking to 
kernel-yocto.bbclass.

Thanks,
Chris

From: openembedded-core-boun...@lists.openembedded.org 
[mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of Chris 
Laplante via Openembedded-core
Sent: Friday, May 11, 2018 2:51 PM
To: openembedded-core@lists.openembedded.org
Cc: SMITH,JARED (A-Little Falls,ex1) 
Subject: [OE-core] do_kernel_configme and defconfig

Hi all,

Is it expected for do_kernel_configme to apply the defconfig last (after 
configuration fragments introduced by sccs)?

For some reason, in the call to merge_config, 
".kernel-meta/configs//./defconfig" is passed last whereas I'd expect it would 
be first (since that should be the base config). This is causing problems, 
because config options that my config fragments are setting are getting 
overridden by the defconfig - it should be the other way around.

For reference, I'm using Rocko and have just updated to the latest commit. We 
have an in-tree defconfig, and we set KBUILD_DEFCONFIG_machinename 
appropriately. We are using the separate kernel-meta repository to store kernel 
metadata. I have KMACHINE_machinename set up so that it finds the correct BSP 
definition .scc file. Still seem to be missing something, though.

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


[OE-core] [PATCHv2 1/5] libsdl2: allow to build native and nativesdk

2018-05-11 Thread Martin Jansa
* enable x11 in native builds

Signed-off-by: Martin Jansa 
---
 meta/recipes-graphics/libsdl2/libsdl2_2.0.8.bb | 4 
 1 file changed, 4 insertions(+)

diff --git a/meta/recipes-graphics/libsdl2/libsdl2_2.0.8.bb 
b/meta/recipes-graphics/libsdl2/libsdl2_2.0.8.bb
index c0cf70d7fd..c37f669321 100644
--- a/meta/recipes-graphics/libsdl2/libsdl2_2.0.8.bb
+++ b/meta/recipes-graphics/libsdl2/libsdl2_2.0.8.bb
@@ -37,6 +37,8 @@ EXTRA_OECONF = "--disable-oss --disable-esd --disable-arts \
 # and BSP layers to pick either (desktop) opengl, gles2, or no GL
 PACKAGECONFIG_GL ?= "${@bb.utils.filter('DISTRO_FEATURES', 'opengl', d)}"
 
+PACKAGECONFIG_class-native = "x11"
+PACKAGECONFIG_class-nativesdk = "${@bb.utils.filter('DISTRO_FEATURES', 'x11', 
d)}"
 PACKAGECONFIG ??= " \
 ${PACKAGECONFIG_GL} \
 ${@bb.utils.filter('DISTRO_FEATURES', 'alsa directfb pulseaudio x11', d)} \
@@ -63,3 +65,5 @@ do_configure_prepend() {
 }
 
 FILES_${PN}-dev += "${libdir}/cmake"
+
+BBCLASSEXTEND = "native nativesdk"
-- 
2.17.0

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


[OE-core] [PATCHv2 5/5] qemu: use sdl2 instead of sdl1

2018-05-11 Thread Martin Jansa
* sdl1 since qemu-2.12.0 depends on x11 in DISTRO_FEATURES, switch to sdl2

Signed-off-by: Martin Jansa 
---
 meta/recipes-devtools/qemu/qemu.inc | 13 -
 1 file changed, 8 insertions(+), 5 deletions(-)

diff --git a/meta/recipes-devtools/qemu/qemu.inc 
b/meta/recipes-devtools/qemu/qemu.inc
index 9010a04792..8169e55e69 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -74,11 +74,11 @@ do_install_append() {
 # END of qemu-mips workaround
 
 PACKAGECONFIG ??= " \
-   fdt sdl kvm \
-   ${@bb.utils.filter('DISTRO_FEATURES', 'alsa xen', d)} \
-   "
-PACKAGECONFIG_class-native ??= "fdt alsa kvm"
-PACKAGECONFIG_class-nativesdk ??= "fdt sdl kvm"
+fdt sdl sdl2 kvm \
+${@bb.utils.filter('DISTRO_FEATURES', 'alsa xen', d)} \
+"
+PACKAGECONFIG_class-native ??= "fdt sdl sdl2 alsa kvm"
+PACKAGECONFIG_class-nativesdk ??= "fdt sdl sdl2 kvm"
 
 # Handle distros such as CentOS 5 32-bit that do not have kvm support
 PACKAGECONFIG_class-native_remove = "${@'kvm' if not 
os.path.exists('/usr/include/linux/kvm.h') else ''}"
@@ -87,6 +87,9 @@ PACKAGECONFIG_class-native_remove = "${@'kvm' if not 
os.path.exists('/usr/includ
 PACKAGECONFIG_remove_darwin = "kvm"
 PACKAGECONFIG_remove_mingw32 = "kvm"
 
+# sdl1 can be used only together with x11 in DISTRO_FEATURES, because since:
+# https://github.com/qemu/qemu/commit/2ec78706d188df7d3dab43d07b19b05ef7800a44
+# it explicitly includes X11/Xlib.h for all gtk, sdl1 UI backends
 PACKAGECONFIG[sdl] = "--enable-sdl,--disable-sdl,libsdl"
 PACKAGECONFIG[sdl2] = "--with-sdlabi=2.0,--with-sdlabi=1.2,libsdl2"
 PACKAGECONFIG[virtfs] = "--enable-virtfs --enable-attr,--disable-virtfs,libcap 
attr,"
-- 
2.17.0

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


[OE-core] [PATCHv2 4/5] qemu: add PACKAGECONFIG for virglrenderer, sdl2, usb-redir and spice

2018-05-11 Thread Martin Jansa
* drop "fdt sdl" listed twice in PACKAGECONFIG
* sdl2 when selected needs sdl as well and will depend on both libsdl
  and libsdl
* keep all 4 disabled by default
* spice, usbredir recipes will eventually be in meta-networking layer
  (you can use jansa/spice branch from meta-openembedded-contrib repository)
* virglrenderer recipe will eventually be in oe-core layer
  (you can use jansa/qemu branch from openembedded-core-contrib repository)

Signed-off-by: Martin Jansa 
---
 meta/recipes-devtools/qemu/qemu.inc | 7 ++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/qemu/qemu.inc 
b/meta/recipes-devtools/qemu/qemu.inc
index dc73df813a..9010a04792 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -74,7 +74,6 @@ do_install_append() {
 # END of qemu-mips workaround
 
 PACKAGECONFIG ??= " \
-   fdt sdl \
fdt sdl kvm \
${@bb.utils.filter('DISTRO_FEATURES', 'alsa xen', d)} \
"
@@ -89,6 +88,7 @@ PACKAGECONFIG_remove_darwin = "kvm"
 PACKAGECONFIG_remove_mingw32 = "kvm"
 
 PACKAGECONFIG[sdl] = "--enable-sdl,--disable-sdl,libsdl"
+PACKAGECONFIG[sdl2] = "--with-sdlabi=2.0,--with-sdlabi=1.2,libsdl2"
 PACKAGECONFIG[virtfs] = "--enable-virtfs --enable-attr,--disable-virtfs,libcap 
attr,"
 PACKAGECONFIG[aio] = "--enable-linux-aio,--disable-linux-aio,libaio,"
 PACKAGECONFIG[xfs] = "--enable-xfsctl,--disable-xfsctl,xfsprogs,"
@@ -115,5 +115,10 @@ PACKAGECONFIG[bzip2] = 
"--enable-bzip2,--disable-bzip2,bzip2"
 PACKAGECONFIG[bluez] = "--enable-bluez,--disable-bluez,${BLUEZ}"
 PACKAGECONFIG[libiscsi] = "--enable-libiscsi,--disable-libiscsi"
 PACKAGECONFIG[kvm] = "--enable-kvm,--disable-kvm"
+PACKAGECONFIG[virglrenderer] = 
"--enable-virglrenderer,--disable-virglrenderer,virglrenderer"
+# spice will be in meta-networking layer
+PACKAGECONFIG[spice] = "--enable-spice,--disable-spice,spice"
+# usbredir will be in meta-networking layer
+PACKAGECONFIG[usb-redir] = "--enable-usb-redir,--disable-usb-redir,usbredir"
 
 INSANE_SKIP_${PN} = "arch"
-- 
2.17.0

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


[OE-core] [PATCHv2 3/5] qemu: refresh patches with devtool

2018-05-11 Thread Martin Jansa
From: Martin Jansa 

Signed-off-by: Martin Jansa 
Signed-off-by: Ross Burton 
---
 .../qemu/qemu/add-ptest-in-makefile-v10.patch | 13 ---
 .../qemu/apic-fixup-fallthrough-to-PIC.patch  | 15 
 ...pus.c-qemu_cpu_kick_thread_debugging.patch | 12 +++
 ...x-libcap-header-issue-on-some-distro.patch | 16 +
 ...webkitgtk-hangs-on-32-bit-x86-target.patch | 10 +++---
 .../qemu/qemu/no-valgrind.patch   | 19 --
 .../qemu/qemu/pathlimit.patch | 35 ---
 .../qemu/qemu-enlarge-env-entry-size.patch| 18 +-
 meta/recipes-devtools/qemu/qemu/wacom.patch   | 24 -
 9 files changed, 100 insertions(+), 62 deletions(-)

diff --git a/meta/recipes-devtools/qemu/qemu/add-ptest-in-makefile-v10.patch 
b/meta/recipes-devtools/qemu/qemu/add-ptest-in-makefile-v10.patch
index e9639820be..3337d1c7ba 100644
--- a/meta/recipes-devtools/qemu/qemu/add-ptest-in-makefile-v10.patch
+++ b/meta/recipes-devtools/qemu/qemu/add-ptest-in-makefile-v10.patch
@@ -1,7 +1,8 @@
-From 4201a5791fc4798a45a9b9f881602d7bacb74ed1 Mon Sep 17 00:00:00 2001
+From 6c01c969def7adae70d7d59a40b5640454b97bdb Mon Sep 17 00:00:00 2001
 From: Juro Bystricky 
 Date: Thu, 31 Aug 2017 11:06:56 -0700
-Subject: Add subpackage -ptest which runs all unit test cases for qemu.
+Subject: [PATCH] Add subpackage -ptest which runs all unit test cases for
+ qemu.
 
 Upstream-Status: Pending
 
@@ -9,11 +10,15 @@ Signed-off-by: Kai Kang 
 
 Signed-off-by: Juro Bystricky 
 
+---
+ tests/Makefile.include | 8 
+ 1 file changed, 8 insertions(+)
+
 diff --git a/tests/Makefile.include b/tests/Makefile.include
-index f08b741..3d1b3e9 100644
+index 3b9a5e3..dfbcd72 100644
 --- a/tests/Makefile.include
 +++ b/tests/Makefile.include
-@@ -924,4 +924,12 @@ all: $(QEMU_IOTESTS_HELPERS-y)
+@@ -972,4 +972,12 @@ all: $(QEMU_IOTESTS_HELPERS-y)
  -include $(wildcard tests/*.d)
  -include $(wildcard tests/libqos/*.d)
  
diff --git 
a/meta/recipes-devtools/qemu/qemu/apic-fixup-fallthrough-to-PIC.patch 
b/meta/recipes-devtools/qemu/qemu/apic-fixup-fallthrough-to-PIC.patch
index d6a3522eda..8ba507c9ff 100644
--- a/meta/recipes-devtools/qemu/qemu/apic-fixup-fallthrough-to-PIC.patch
+++ b/meta/recipes-devtools/qemu/qemu/apic-fixup-fallthrough-to-PIC.patch
@@ -1,7 +1,7 @@
-From bef93bb81588b5323a52d2e1886f2a77b64a976b Mon Sep 17 00:00:00 2001
+From ca247c6e7ab7a0bd7b94658a726940f10a6b0559 Mon Sep 17 00:00:00 2001
 From: Mark Asselstine 
 Date: Tue, 26 Feb 2013 11:43:28 -0500
-Subject: [PATCH 03/18] apic: fixup fallthrough to PIC
+Subject: [PATCH] apic: fixup fallthrough to PIC
 
 Commit 0e21e12bb311c4c1095d0269dc2ef81196ccb60a [Don't route PIC
 interrupts through the local APIC if the local APIC config says so.]
@@ -24,15 +24,16 @@ serviced, is -1.
 Signed-off-by: Mark Asselstine 
 Upstream-Status: Submitted 
[https://lists.gnu.org/archive/html/qemu-devel/2013-04/msg00878.html]
 Signed-off-by: He Zhe 
+
 ---
  hw/intc/apic.c | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
 
-Index: qemu-2.11.1/hw/intc/apic.c
-===
 qemu-2.11.1.orig/hw/intc/apic.c
-+++ qemu-2.11.1/hw/intc/apic.c
-@@ -591,7 +591,7 @@ int apic_accept_pic_intr(DeviceState *de
+diff --git a/hw/intc/apic.c b/hw/intc/apic.c
+index 6fda52b..cd72919 100644
+--- a/hw/intc/apic.c
 b/hw/intc/apic.c
+@@ -603,7 +603,7 @@ int apic_accept_pic_intr(DeviceState *dev)
  APICCommonState *s = APIC(dev);
  uint32_t lvt0;
  
diff --git 
a/meta/recipes-devtools/qemu/qemu/cpus.c-qemu_cpu_kick_thread_debugging.patch 
b/meta/recipes-devtools/qemu/qemu/cpus.c-qemu_cpu_kick_thread_debugging.patch
index 6822132541..46c82a4aea 100644
--- 
a/meta/recipes-devtools/qemu/qemu/cpus.c-qemu_cpu_kick_thread_debugging.patch
+++ 
b/meta/recipes-devtools/qemu/qemu/cpus.c-qemu_cpu_kick_thread_debugging.patch
@@ -1,4 +1,4 @@
-From 697a834c35d19447b7dcdb9e1d9434bc6ce17c21 Mon Sep 17 00:00:00 2001
+From a2e3ad8e3bbdea20a4c53404674dd8ae46bd2528 Mon Sep 17 00:00:00 2001
 From: =?UTF-8?q?An=C3=ADbal=20Lim=C3=B3n?= 
 Date: Wed, 12 Aug 2015 15:11:30 -0500
 Subject: [PATCH] cpus.c: Add error messages when qemi_cpu_kick_thread fails.
@@ -12,6 +12,7 @@ current cpu information.
 
 Upstream-Status: Inappropriate
 Signed-off-by: Aníbal Limón 
+
 ---
  cpus.c |  5 +
  custom_debug.h | 24 
@@ -19,10 +20,10 @@ Signed-off-by: Aníbal Limón 
  create mode 100644 custom_debug.h
 
 diff --git a/cpus.c b/cpus.c
-index a822ce3..7e4786e 100644
+index 38eba8b..b84a60a 100644
 --- a/cpus.c
 +++ b/cpus.c
-@@ -1080,6 +1080,8 @@ static void *qemu_tcg_cpu_thread_fn(void *arg)
+@@ 

[OE-core] [PATCHv2 2/5] qemu: upgrade to 2.12.0

2018-05-11 Thread Martin Jansa
From: Martin Jansa 

* drop patches which are now included upstream

Signed-off-by: Martin Jansa 
Signed-off-by: Ross Burton 
---
 meta/conf/distro/include/tcmode-default.inc   |  2 +-
 ...4-treat-DISAS_UPDATE-as-variant-of-D.patch | 67 ---
 ...-connect-socket-to-a-spawned-command.patch | 52 +++---
 ...2Queue-pointers-in-post_load-routine.patch | 63 -
 .../qemu/qemu/disable-grabs.patch | 43 ++--
 meta/recipes-devtools/qemu/qemu/memfd.patch   | 57 
 .../qemu/qemu/qemu-2.5.0-cflags.patch | 15 -
 .../qemu/{qemu_2.11.1.bb => qemu_2.12.0.bb}   |  7 +-
 8 files changed, 65 insertions(+), 241 deletions(-)
 delete mode 100644 
meta/recipes-devtools/qemu/qemu/0001-arm-translate-a64-treat-DISAS_UPDATE-as-variant-of-D.patch
 delete mode 100644 
meta/recipes-devtools/qemu/qemu/check-PS2Queue-pointers-in-post_load-routine.patch
 delete mode 100644 meta/recipes-devtools/qemu/qemu/memfd.patch
 rename meta/recipes-devtools/qemu/{qemu_2.11.1.bb => qemu_2.12.0.bb} (84%)

diff --git a/meta/conf/distro/include/tcmode-default.inc 
b/meta/conf/distro/include/tcmode-default.inc
index b197819e9e..5271b41860 100644
--- a/meta/conf/distro/include/tcmode-default.inc
+++ b/meta/conf/distro/include/tcmode-default.inc
@@ -28,7 +28,7 @@ BINUVERSION ?= "2.30%"
 GDBVERSION ?= "8.1%"
 GLIBCVERSION ?= "2.27%"
 LINUXLIBCVERSION ?= "4.15%"
-QEMUVERSION ?= "2.11%"
+QEMUVERSION ?= "2.12%"
 
 PREFERRED_VERSION_gcc ?= "${GCCVERSION}"
 PREFERRED_VERSION_gcc-cross-${TARGET_ARCH} ?= "${GCCVERSION}"
diff --git 
a/meta/recipes-devtools/qemu/qemu/0001-arm-translate-a64-treat-DISAS_UPDATE-as-variant-of-D.patch
 
b/meta/recipes-devtools/qemu/qemu/0001-arm-translate-a64-treat-DISAS_UPDATE-as-variant-of-D.patch
deleted file mode 100644
index f90cae694c..00
--- 
a/meta/recipes-devtools/qemu/qemu/0001-arm-translate-a64-treat-DISAS_UPDATE-as-variant-of-D.patch
+++ /dev/null
@@ -1,67 +0,0 @@
-From a75a52d62418dafe462be4fe30485501d1010bb9 Mon Sep 17 00:00:00 2001
-From: Victor Kamensky 
-Date: Fri, 23 Mar 2018 18:26:45 +
-Subject: [PATCH] arm/translate-a64: treat DISAS_UPDATE as variant of
- DISAS_EXIT
-MIME-Version: 1.0
-Content-Type: text/plain; charset=UTF-8
-Content-Transfer-Encoding: 8bit
-
-In OE project 4.15 linux kernel boot hang was observed under
-single cpu aarch64 qemu. Kernel code was in a loop waiting for
-vtimer arrival, spinning in TC generated blocks, while interrupt
-was pending unprocessed. This happened because when qemu tried to
-handle vtimer interrupt target had interrupts disabled, as
-result flag indicating TCG exit, cpu->icount_decr.u16.high,
-was cleared but arm_cpu_exec_interrupt function did not call
-arm_cpu_do_interrupt to process interrupt. Later when target
-reenabled interrupts, it happened without exit into main loop, so
-following code that waited for result of interrupt execution
-run in infinite loop.
-
-To solve the problem instructions that operate on CPU sys state
-(i.e enable/disable interrupt), and marked as DISAS_UPDATE,
-should be considered as DISAS_EXIT variant, and should be
-forced to exit back to main loop so qemu will have a chance
-processing pending CPU state updates, including pending
-interrupts.
-
-This change brings consistency with how DISAS_UPDATE is treated
-in aarch32 case.
-
-CC: Peter Maydell 
-CC: Alex Bennée 
-CC: qemu-sta...@nongnu.org
-Suggested-by: Peter Maydell 
-Signed-off-by: Victor Kamensky 
-Reviewed-by: Richard Henderson 
-Message-id: 1521526368-1996-1-git-send-email-kamen...@cisco.com
-Signed-off-by: Peter Maydell 
-Upstream-Status: Backport

- target/arm/translate-a64.c | 6 +++---
- 1 file changed, 3 insertions(+), 3 deletions(-)
-
-diff --git a/target/arm/translate-a64.c b/target/arm/translate-a64.c
-index 31ff047..327513e 100644
 a/target/arm/translate-a64.c
-+++ b/target/arm/translate-a64.c
-@@ -13378,12 +13378,12 @@ static void aarch64_tr_tb_stop(DisasContextBase 
*dcbase, CPUState *cpu)
- case DISAS_UPDATE:
- gen_a64_set_pc_im(dc->pc);
- /* fall through */
--case DISAS_JUMP:
--tcg_gen_lookup_and_goto_ptr();
--break;
- case DISAS_EXIT:
- tcg_gen_exit_tb(0);
- break;
-+case DISAS_JUMP:
-+tcg_gen_lookup_and_goto_ptr();
-+break;
- case DISAS_NORETURN:
- case DISAS_SWI:
- break;
--- 
-2.7.4
-
diff --git 
a/meta/recipes-devtools/qemu/qemu/chardev-connect-socket-to-a-spawned-command.patch
 
b/meta/recipes-devtools/qemu/qemu/chardev-connect-socket-to-a-spawned-command.patch
index 6e6bf95c18..f1cf53a8c5 100644
--- 

Re: [OE-core] [PATCH] qemu: add gettext to DEPENDS

2018-05-11 Thread Christopher Larson
This is not a correct fix. We have a gettext bbclass for a reason.

On Fri, May 11, 2018 at 9:35 AM, Chris Patterson  wrote:

> From: Chris Patterson 
>
> Otherwise QEMU build may fail with missing `msgfmt` command.
>
> | make -C po install
> |   GEN bg.mo
> |   GEN tr.mo
> |   GEN de_DE.mo
> | /bin/sh: msgfmt: command not found
> | /bin/sh: msgfmt: command not found
>
> Signed-off-by: Chris Patterson 
> ---
>  meta/recipes-devtools/qemu/qemu.inc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-devtools/qemu/qemu.inc
> b/meta/recipes-devtools/qemu/qemu.inc
> index dc73df8..ba1b9b2 100644
> --- a/meta/recipes-devtools/qemu/qemu.inc
> +++ b/meta/recipes-devtools/qemu/qemu.inc
> @@ -1,7 +1,7 @@
>  SUMMARY = "Fast open source processor emulator"
>  HOMEPAGE = "http://qemu.org;
>  LICENSE = "GPLv2 & LGPLv2.1"
> -DEPENDS = "glib-2.0 zlib pixman"
> +DEPENDS = "glib-2.0 zlib pixman gettext"
>  RDEPENDS_${PN}_class-target += "bash"
>
>  require qemu-targets.inc
> --
> 2.1.4
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>



-- 
Christopher Larson
kergoth at gmail dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Senior Software Engineer, Mentor Graphics
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] do_kernel_configme and defconfig

2018-05-11 Thread Chris Laplante via Openembedded-core
Hi all,

Is it expected for do_kernel_configme to apply the defconfig last (after 
configuration fragments introduced by sccs)?

For some reason, in the call to merge_config, 
".kernel-meta/configs//./defconfig" is passed last whereas I'd expect it would 
be first (since that should be the base config). This is causing problems, 
because config options that my config fragments are setting are getting 
overridden by the defconfig - it should be the other way around.

For reference, I'm using Rocko and have just updated to the latest commit. We 
have an in-tree defconfig, and we set KBUILD_DEFCONFIG_machinename 
appropriately. We are using the separate kernel-meta repository to store kernel 
metadata. I have KMACHINE_machinename set up so that it finds the correct BSP 
definition .scc file. Still seem to be missing something, though.

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


Re: [OE-core] [PATCH v2] qemu: add gettext-native to DEPENDS

2018-05-11 Thread Khem Raj
On Fri, May 11, 2018 at 10:25 AM, Chris Patterson  wrote:
> From: Chris Patterson 
>
> Otherwise QEMU build may fail with missing `msgfmt` command.
>
> | make -C po install
> |   GEN bg.mo
> |   GEN tr.mo
> |   GEN de_DE.mo
> | /bin/sh: msgfmt: command not found
> | /bin/sh: msgfmt: command not found
>

are you enabling gtk+ packageconfig ?
I dont see po files build built otherwise if you are enabling gtk+
then please move the
dependency into that packageconfig.

Adding gettext dependency especially on native recipes can dampen
parallism and increase
build time due to serialization. And qemu-native is quite a
fundamental package we need at early
stages of build.

> Signed-off-by: Chris Patterson 
> ---
>  meta/recipes-devtools/qemu/qemu.inc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-devtools/qemu/qemu.inc 
> b/meta/recipes-devtools/qemu/qemu.inc
> index dc73df8..78fa30c 100644
> --- a/meta/recipes-devtools/qemu/qemu.inc
> +++ b/meta/recipes-devtools/qemu/qemu.inc
> @@ -1,7 +1,7 @@
>  SUMMARY = "Fast open source processor emulator"
>  HOMEPAGE = "http://qemu.org;
>  LICENSE = "GPLv2 & LGPLv2.1"
> -DEPENDS = "glib-2.0 zlib pixman"
> +DEPENDS = "glib-2.0 zlib pixman gettext-native"
>  RDEPENDS_${PN}_class-target += "bash"
>
>  require qemu-targets.inc
> --
> 2.1.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] [meta-oe][PATCH] strongswan: package up sbin debug files

2018-05-11 Thread Chris Patterson
From: Chris Patterson 

Signed-off-by: Chris Patterson 
---
 meta-networking/recipes-support/strongswan/strongswan_5.6.2.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-networking/recipes-support/strongswan/strongswan_5.6.2.bb 
b/meta-networking/recipes-support/strongswan/strongswan_5.6.2.bb
index f2fe1f1..5cae6ac 100644
--- a/meta-networking/recipes-support/strongswan/strongswan_5.6.2.bb
+++ b/meta-networking/recipes-support/strongswan/strongswan_5.6.2.bb
@@ -46,7 +46,7 @@ inherit autotools systemd pkgconfig
 RRECOMMENDS_${PN} = "kernel-module-ipsec"
 
 FILES_${PN} += "${libdir}/ipsec/lib*${SOLIBS}"
-FILES_${PN}-dbg += "${bindir}/.debug ${libdir}/ipsec/.debug 
${libexecdir}/ipsec/.debug"
+FILES_${PN}-dbg += "${bindir}/.debug ${sbindir}/.debug ${libdir}/ipsec/.debug 
${libexecdir}/ipsec/.debug"
 FILES_${PN}-dev += "${libdir}/ipsec/lib*${SOLIBSDEV} ${libdir}/ipsec/*.la"
 FILES_${PN}-staticdev += "${libdir}/ipsec/*.a"
 
-- 
2.1.4

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


[OE-core] [PATCH] perl-ptest: drop runtime dependency on libssp

2018-05-11 Thread Martin Jansa
* We use ssp impl directly from glibc/musl now.

Signed-off-by: Martin Jansa 
---
 meta/recipes-devtools/perl/perl-ptest.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/perl/perl-ptest.inc 
b/meta/recipes-devtools/perl/perl-ptest.inc
index 6a7a2d7cb3..8d46448566 100644
--- a/meta/recipes-devtools/perl/perl-ptest.inc
+++ b/meta/recipes-devtools/perl/perl-ptest.inc
@@ -50,7 +50,7 @@ python populate_packages_prepend() {
 '${PN}-ptest%s', '%s', recursive=True, match_path=True)
 }
 
-RDEPENDS_${PN}-ptest += "${PN}-modules ${PN}-doc ${PN}-misc sed libssp"
+RDEPENDS_${PN}-ptest += "${PN}-modules ${PN}-doc ${PN}-misc sed"
 
 # The perl-ptest package contains Perl internal modules and generating file
 # dependencies for it causes problems.
-- 
2.17.0

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


Re: [OE-core] [pyro][PATCH 2/2] gcc: Remove patch causing ICE on x86_64 valgrind compile (on x86-64 only)

2018-05-11 Thread Khem Raj
On Fri, May 11, 2018 at 1:10 AM, André Draszik  wrote:
> From: André Draszik 
>
> This is similar to commit f76ee525a75d, but instead of disabling
> the patch on all builds, we only remove it for x86-64 builds, as
> the original change's commit message mentined issues with this
> patch applied on that architecture only.
>

this is better thanks

> Signed-off-by: André Draszik 
> ---
>  meta/recipes-devtools/gcc/gcc-6.4.inc | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/meta/recipes-devtools/gcc/gcc-6.4.inc 
> b/meta/recipes-devtools/gcc/gcc-6.4.inc
> index 1803917f01..9a23863022 100644
> --- a/meta/recipes-devtools/gcc/gcc-6.4.inc
> +++ b/meta/recipes-devtools/gcc/gcc-6.4.inc
> @@ -81,9 +81,11 @@ SRC_URI = "\
> file://0048-sync-gcc-stddef.h-with-musl.patch \
> file://0054_all_nopie-all-flags.patch \
> file://0055-unwind_h-glibc26.patch \
> -   
> file://0056-LRA-PR70904-relax-the-restriction-on-subreg-reload-f.patch \
> +   ${LRA_PR70904_PATCH} \
> ${BACKPORTS} \
>  "
> +LRA_PR70904_PATCH = 
> "file://0056-LRA-PR70904-relax-the-restriction-on-subreg-reload-f.patch"
> +LRA_PR70904_PATCH_x86-64 = ""
>  BACKPORTS = "\
> file://CVE-2016-6131.patch \
> 
> file://0057-ARM-PR-82445-suppress-32-bit-aligned-ldrd-strd-peeph.patch \
> --
> 2.16.2
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH v2] qemu: add gettext-native to DEPENDS

2018-05-11 Thread Chris Patterson
From: Chris Patterson 

Otherwise QEMU build may fail with missing `msgfmt` command.

| make -C po install
|   GEN bg.mo
|   GEN tr.mo
|   GEN de_DE.mo
| /bin/sh: msgfmt: command not found
| /bin/sh: msgfmt: command not found

Signed-off-by: Chris Patterson 
---
 meta/recipes-devtools/qemu/qemu.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/qemu/qemu.inc 
b/meta/recipes-devtools/qemu/qemu.inc
index dc73df8..78fa30c 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -1,7 +1,7 @@
 SUMMARY = "Fast open source processor emulator"
 HOMEPAGE = "http://qemu.org;
 LICENSE = "GPLv2 & LGPLv2.1"
-DEPENDS = "glib-2.0 zlib pixman"
+DEPENDS = "glib-2.0 zlib pixman gettext-native"
 RDEPENDS_${PN}_class-target += "bash"
 
 require qemu-targets.inc
-- 
2.1.4

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


[OE-core] [PATCH] qemu: add gettext to DEPENDS

2018-05-11 Thread Chris Patterson
From: Chris Patterson 

Otherwise QEMU build may fail with missing `msgfmt` command.

| make -C po install
|   GEN bg.mo
|   GEN tr.mo
|   GEN de_DE.mo
| /bin/sh: msgfmt: command not found
| /bin/sh: msgfmt: command not found

Signed-off-by: Chris Patterson 
---
 meta/recipes-devtools/qemu/qemu.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/qemu/qemu.inc 
b/meta/recipes-devtools/qemu/qemu.inc
index dc73df8..ba1b9b2 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -1,7 +1,7 @@
 SUMMARY = "Fast open source processor emulator"
 HOMEPAGE = "http://qemu.org;
 LICENSE = "GPLv2 & LGPLv2.1"
-DEPENDS = "glib-2.0 zlib pixman"
+DEPENDS = "glib-2.0 zlib pixman gettext"
 RDEPENDS_${PN}_class-target += "bash"
 
 require qemu-targets.inc
-- 
2.1.4

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


[OE-core] [PATCH] patchreview: don't disable malformed SoB check

2018-05-11 Thread Ross Burton
We cleaned up the metadata so this can be enabled again.

Signed-off-by: Ross Burton 
---
 scripts/contrib/patchreview.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/scripts/contrib/patchreview.py b/scripts/contrib/patchreview.py
index 4e3e73c7a8b..1086c95f67f 100755
--- a/scripts/contrib/patchreview.py
+++ b/scripts/contrib/patchreview.py
@@ -132,8 +132,8 @@ def analyse(results, want_blame=False, verbose=True):
 need_blame = True
 if verbose:
 print("Missing Signed-off-by tag (%s)" % patch)
-# TODO: disable this for now as too much fails
-if False and r.malformed_sob:
+
+if r.malformed_sob:
 need_blame = True
 if verbose:
 print("Malformed Signed-off-by '%s' (%s)" % (r.malformed_sob, 
patch))
-- 
2.11.0

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


[OE-core] [PATCH] uninative-tarball: Add libjis and euc-jp gconv files

2018-05-11 Thread Ross Burton
From: Khem Raj 

packages like fontforge-native fail with mysterious errors like

| ../../git/inc/gwwiconv.h:44:21: error: conflicting types for ‘gww_iconv_close’
|  #define iconv_close gww_iconv_close
|  ^~~
| ../../git/inc/gwwiconv.h:37:13: note: previous declaration of 
‘gww_iconv_close’ was here
|  extern void gww_iconv_close( gww_iconv_t cd);
|  ^~~

The reason behind this is that a check for iconv fails during native
configure run, the check fails because the autoconf test to check for iconv
pokes for these gconv's in test runs before declaring iconv support successful.

Therefore when uninative is active the package fails to build but when
uninative is inactive all works fine. this patch fixes that

Signed-off-by: Khem Raj 
Signed-off-by: Ross Burton 
---
 meta/recipes-core/meta/uninative-tarball.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-core/meta/uninative-tarball.bb 
b/meta/recipes-core/meta/uninative-tarball.bb
index 38c3a314e16..c38c2a445e9 100644
--- a/meta/recipes-core/meta/uninative-tarball.bb
+++ b/meta/recipes-core/meta/uninative-tarball.bb
@@ -12,6 +12,8 @@ TOOLCHAIN_HOST_TASK = "\
 nativesdk-glibc-gconv-iso8859-1 \
 nativesdk-glibc-gconv-utf-16 \
 nativesdk-glibc-gconv-cp1252 \
+nativesdk-glibc-gconv-euc-jp \
+nativesdk-glibc-gconv-libjis \
 nativesdk-patchelf \
 nativesdk-libxcrypt \
 "
-- 
2.11.0

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


[OE-core] [PATCH] patchreview: don't disable malformed SoB check

2018-05-11 Thread Ross Burton
We cleaned up the metadata so this can be enabled again.

Signed-off-by: Ross Burton 
---
 scripts/contrib/patchreview.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/scripts/contrib/patchreview.py b/scripts/contrib/patchreview.py
index 4e3e73c7a8b..1086c95f67f 100755
--- a/scripts/contrib/patchreview.py
+++ b/scripts/contrib/patchreview.py
@@ -132,8 +132,8 @@ def analyse(results, want_blame=False, verbose=True):
 need_blame = True
 if verbose:
 print("Missing Signed-off-by tag (%s)" % patch)
-# TODO: disable this for now as too much fails
-if False and r.malformed_sob:
+
+if r.malformed_sob:
 need_blame = True
 if verbose:
 print("Malformed Signed-off-by '%s' (%s)" % (r.malformed_sob, 
patch))
-- 
2.11.0

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


[OE-core] [PATCH V2] distcc: update to 3.3

2018-05-11 Thread Hongxu Jia
* update to version 3.3
* Remove 0001-zeroconf-Include-fcntl.h.patch since it's
  included in v3.3
* Add update-distcc-symlinks into FILES.

Signed-off-by: Jackie Huang 

* Correct upstream SRC_URI and SRCREV to v3.3
* Correct default to fix starting distccd service failed
  It caused by upstream commit:
  
https://github.com/distcc/distcc/commit/920e8b922addea8c54e68cc29c1416753f532f78
  ...
  commit 920e8b922addea8c54e68cc29c1416753f532f78
  Author: Shawn Landden 
  Date:   Mon Feb 26 11:29:14 2018 -0800

  daemon: warn when masquerade is not setup
  ...
  Add option --make-me-a-botnet to disable the warning.

* Use localhost to replace 192.168.7.0/24 which is inappropriate for runqemu 
slirp.

[YOCTO #12741]

Signed-off-by: Hongxu Jia 
---
 .../distcc/{distcc_3.2.bb => distcc_3.3.bb}|  8 +++---
 .../files/0001-zeroconf-Include-fcntl.h.patch  | 29 --
 meta/recipes-devtools/distcc/files/default |  4 +--
 3 files changed, 6 insertions(+), 35 deletions(-)
 rename meta/recipes-devtools/distcc/{distcc_3.2.bb => distcc_3.3.bb} (91%)
 delete mode 100644 
meta/recipes-devtools/distcc/files/0001-zeroconf-Include-fcntl.h.patch

diff --git a/meta/recipes-devtools/distcc/distcc_3.2.bb 
b/meta/recipes-devtools/distcc/distcc_3.3.bb
similarity index 91%
rename from meta/recipes-devtools/distcc/distcc_3.2.bb
rename to meta/recipes-devtools/distcc/distcc_3.3.bb
index ff0e22f..c4c65e6 100644
--- a/meta/recipes-devtools/distcc/distcc_3.2.bb
+++ b/meta/recipes-devtools/distcc/distcc_3.3.bb
@@ -14,14 +14,13 @@ PACKAGECONFIG[popt] = 
"--without-included-popt,--with-included-popt,popt"
 
 RRECOMMENDS_${PN} = "avahi-daemon"
 
-SRC_URI = "git://github.com/akuster/distcc.git;branch=${PV} \
+SRC_URI = "git://github.com/distcc/distcc.git \
file://separatebuilddir.patch \
-   file://0001-zeroconf-Include-fcntl.h.patch \
file://default \
file://distccmon-gnome.desktop \
file://distcc \
file://distcc.service"
-SRCREV = "d8b18df3e9dcbe4f092bed565835d3975e99432c"
+SRCREV = "002e68b766ccd7ad05551e67d162b71a7a773d0d"
 S = "${WORKDIR}/git"
 
 inherit autotools pkgconfig update-rc.d useradd systemd
@@ -59,9 +58,10 @@ PACKAGES += "distcc-distmon-gnome"
 
 FILES_${PN} = " ${sysconfdir} \
${bindir}/distcc \
-${bindir}/lsdistcc \
+   ${bindir}/lsdistcc \
${bindir}/distccd \
${bindir}/distccmon-text \
+   ${sbindir}/update-distcc-symlinks \
${systemd_unitdir}/system/distcc.service"
 FILES_distcc-distmon-gnome = "  ${bindir}/distccmon-gnome \
${datadir}/distcc"
diff --git 
a/meta/recipes-devtools/distcc/files/0001-zeroconf-Include-fcntl.h.patch 
b/meta/recipes-devtools/distcc/files/0001-zeroconf-Include-fcntl.h.patch
deleted file mode 100644
index b17ec9c..000
--- a/meta/recipes-devtools/distcc/files/0001-zeroconf-Include-fcntl.h.patch
+++ /dev/null
@@ -1,29 +0,0 @@
-From 8331fc4759d809512f404e7a27f817ad6d616450 Mon Sep 17 00:00:00 2001
-From: Khem Raj 
-Date: Mon, 13 Apr 2015 18:00:33 -0700
-Subject: [PATCH] zeroconf: Include fcntl.h
-
-We need it for getting deinitions for O_* e.g. O_CREAT
-
-Upstream-Status: Pending
-
-Signed-off-by: Khem Raj 

- src/zeroconf.c | 1 +
- 1 file changed, 1 insertion(+)
-
-diff --git a/src/zeroconf.c b/src/zeroconf.c
-index 414ddc4..31bd33f 100644
 a/src/zeroconf.c
-+++ b/src/zeroconf.c
-@@ -33,6 +33,7 @@
- #include 
- #include 
- #include 
-+#include 
- 
- #include 
- #include 
--- 
-2.1.4
-
diff --git a/meta/recipes-devtools/distcc/files/default 
b/meta/recipes-devtools/distcc/files/default
index 63c4159..e5ca68b 100644
--- a/meta/recipes-devtools/distcc/files/default
+++ b/meta/recipes-devtools/distcc/files/default
@@ -16,9 +16,9 @@ STARTDISTCC="true"
 #
 # ALLOWEDNETS="127.0.0.1"
 
-ALLOWEDNETS="192.168.7.0/24"
+ALLOWEDNETS="127.0.0.1"
 
 #
 # OPTIONS is used for the systemd service file
 #
-OPTIONS="--allow 192.168.7.0/24"
+OPTIONS="--allow 127.0.0.1 --make-me-a-botnet"
-- 
2.7.4

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


[OE-core] [PATCH 1/2] swig: fix patch headers

2018-05-11 Thread Ross Burton
Signed-off-by: Ross Burton 
---
 ...ig-3.0.12-Coverity-fix-issue-reported-for-SWIG_Python_FixMetho.patch | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/meta/recipes-devtools/swig/swig/swig-3.0.12-Coverity-fix-issue-reported-for-SWIG_Python_FixMetho.patch
 
b/meta/recipes-devtools/swig/swig/swig-3.0.12-Coverity-fix-issue-reported-for-SWIG_Python_FixMetho.patch
index eab50fc7ef7..10e4afd1ba0 100644
--- 
a/meta/recipes-devtools/swig/swig/swig-3.0.12-Coverity-fix-issue-reported-for-SWIG_Python_FixMetho.patch
+++ 
b/meta/recipes-devtools/swig/swig/swig-3.0.12-Coverity-fix-issue-reported-for-SWIG_Python_FixMetho.patch
@@ -13,7 +13,7 @@ The issue is only reported for the "swig_ptr: " line, but for
 consistency we replace both occurrences of strncpy with memcpy.
 ---
 Signed-off-by: Khem Raj 
-Status: Backport [https://github.com/swig/swig/pull/898]
+Upstream-Status: Backport [https://github.com/swig/swig/pull/898]
 
  Lib/python/pyinit.swg | 4 ++--
  1 file changed, 2 insertions(+), 2 deletions(-)
-- 
2.11.0

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


[OE-core] [PATCH 2/2] gtk+: fix patch headers

2018-05-11 Thread Ross Burton
Signed-off-by: Ross Burton 
---
 .../gtk+/0001-Do-not-look-into-HOME-when-looking-for-gtk-modules.patch  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/meta/recipes-gnome/gtk+/gtk+/0001-Do-not-look-into-HOME-when-looking-for-gtk-modules.patch
 
b/meta/recipes-gnome/gtk+/gtk+/0001-Do-not-look-into-HOME-when-looking-for-gtk-modules.patch
index 9201e45c39e..83be39c3bf2 100644
--- 
a/meta/recipes-gnome/gtk+/gtk+/0001-Do-not-look-into-HOME-when-looking-for-gtk-modules.patch
+++ 
b/meta/recipes-gnome/gtk+/gtk+/0001-Do-not-look-into-HOME-when-looking-for-gtk-modules.patch
@@ -6,7 +6,7 @@ Subject: [PATCH] Do not look into $HOME when looking for gtk 
modules
 On the host it causes host contamination, on the target it's a
 potential security issue. Gtk+3 has already removed this.
 
-Upstream-Status: Inapproriate [gtk2 is in maintenance mode]
+Upstream-Status: Inappropriate [gtk2 is in maintenance mode]
 Signed-off-by: Alexander Kanavin 
 ---
  gtk/gtkmodules.c | 4 
-- 
2.11.0

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


Re: [OE-core] [meta-oe][PATCH] wic: Fix partition files UIDs on multi rootfs images

2018-05-11 Thread Tom Rini
On Fri, May 11, 2018 at 04:32:31PM +0200, Ricardo Ribalda Delgado wrote:

> When a wks makes reference to multiple rootfs, libspeudo data is not
> properly chossen. This results in filesystems with invalid UIDs for all
> the files.
> 
> This can be tested with this .wks file:
> part / --source rootfs --fstype=ext4 --rootfs-dir=core-image-base
> part /mnt/data1/ --fstype=ext4 --source rootfs --rootfs-dir=core-image-minimal
> part /mnt/data2/ --fstype=ext4 --source rootfs --rootfs-dir=core-image-minimal
> 
> And this script
> 
> $bitbake core-image-minimal core-image-base syslinux
> $losetup --partscan --find --read-only --show test*direct
> $sudo mount /dev/loop0p1 /mnt
> $ls -lan /mnt
> otal 40
> drwxr-xr-x 18    0    0  1024 May 11 16:11 .
> drwxr-xr-x 25    0    0  4096 May  6 06:31 ..
> drwxr-xr-x  2 1000 1000  3072 May 11 15:51 bin
> drwxr-xr-x  2 1000 1000  1024 May 11 13:59 boot
> drwxr-xr-x  2 1000 1000  1024 May 11 13:59 dev
> drwxr-xr-x 25 1000 1000  3072 May 11 15:51 etc
> drwxr-xr-x  3 1000 1000  1024 May 11 13:59 home
> drwxr-xr-x  6 1000 1000  3072 May 11 15:51 lib
> drwx--  2    0    0 12288 May 11 16:11 lost+found
> drwxr-xr-x  2 1000 1000  1024 May 11 13:59 media
> drwxr-xr-x  3 1000 1000  1024 May 11 15:50 mnt
> drwxr-xr-x  2 1000 1000  1024 May 11 13:59 proc
> drwxr-xr-x  2 1000 1000  1024 May 11 15:51 run
> drwxr-xr-x  2 1000 1000  3072 May 11 15:51 sbin
> drwxr-xr-x  2 1000 1000  1024 May 11 13:59 sys
> drwxr-xr-t  2 1000 1000  1024 May 11 13:59 tmp
> drwxr-xr-x 10 1000 1000  1024 May 11 14:54 usr
> drwxr-xr-x  8 1000 1000  1024 May 11 14:55 var
> $sudo losetup -d /dev/loop0
> 
> Signed-off-by: Ricardo Ribalda Delgado 

Reviewed-by: Tom Rini 

-- 
Tom


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


Re: [OE-core] [PATCH v2 2/2] wic: add ontrack DM6 aux3 support

2018-05-11 Thread Burton, Ross
Somehow, these patches are causing selftest to fail:

ERROR: Not supported fstype:

https://autobuilder.yocto.io/builders/nightly-oe-selftest/builds/1051/steps/Running%20oe-selftest/logs/stdio

Ross

On 4 May 2018 at 18:43, Otavio Salvador  wrote:
> Add ontrack DM6 aux3 partition support to enable creating
> partitions required to boot i.MX MXS based platforms.
>
> This has been removed by OE-Core:21af89a6 (wic: allow only supported
> fstypes). It was unnoticed as most users were still using the
> meta-freecale image generation class instead of wic but we are now
> in process of dropping the class and this is the remaining use-case.
>
> Signed-off-by: Otavio Salvador 
> ---
>
> Changes in v2: None
>
>  scripts/lib/wic/ksparser.py  | 3 ++-
>  scripts/lib/wic/plugins/imager/direct.py | 2 ++
>  2 files changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/scripts/lib/wic/ksparser.py b/scripts/lib/wic/ksparser.py
> index e590b2fe3c..02b267380f 100644
> --- a/scripts/lib/wic/ksparser.py
> +++ b/scripts/lib/wic/ksparser.py
> @@ -138,7 +138,8 @@ class KickStart():
>  part.add_argument('--fsoptions', dest='fsopts')
>  part.add_argument('--fstype', default='vfat',
>choices=('ext2', 'ext3', 'ext4', 'btrfs',
> -   'squashfs', 'vfat', 'msdos', 'swap'))
> +   'squashfs', 'vfat', 'msdos', 'swap',
> +   'ontrackdm6aux3'))
>  part.add_argument('--mkfs-extraopts', default='')
>  part.add_argument('--label')
>  part.add_argument('--no-table', action='store_true')
> diff --git a/scripts/lib/wic/plugins/imager/direct.py 
> b/scripts/lib/wic/plugins/imager/direct.py
> index 1fa6b917e6..594481e6a9 100644
> --- a/scripts/lib/wic/plugins/imager/direct.py
> +++ b/scripts/lib/wic/plugins/imager/direct.py
> @@ -528,6 +528,8 @@ class PartitionedImage():
>  parted_fs_type = "fat16"
>  if not part.system_id:
>  part.system_id = '0x6' # FAT16
> +elif part.fstype == "ontrackdm6aux3":
> +parted_fs_type = "ontrackdm6aux3"
>  else:
>  # Type for ext2/ext3/ext4/btrfs
>  parted_fs_type = "ext2"
> --
> 2.17.0
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH 2/2] rpm: Assume a max limit of 1024 open files

2018-05-11 Thread Alexander Kanavin

On 05/11/2018 01:39 PM, Peter Kjellerstedt wrote:

However, I gave this some more thought, and maybe it would be better to
let bitbake set the soft limit for max open files to, e.g., 1024. That
way we would not need to modify the code in rpm as it would adapt itself
automatically. I tried adding the following to bitbake_main and it worked:

 import resource

 # Set the maximum number of open files as there are performance problems
 # with, e.g., rpm if this is unlimited (which it may be if running inside
 # a Docker container).
 (soft, hard) = resource.getrlimit(resource.RLIMIT_NOFILE)
 soft = int(os.environ.get("BB_LIMIT_NOFILE", "1024"))
 resource.setrlimit(resource.RLIMIT_NOFILE, (min(soft, hard), hard))


That's right, this is the best solution.

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


[OE-core] [meta-oe][PATCH] wic: Fix partition files UIDs on multi rootfs images

2018-05-11 Thread Ricardo Ribalda Delgado
When a wks makes reference to multiple rootfs, libspeudo data is not
properly chossen. This results in filesystems with invalid UIDs for all
the files.

This can be tested with this .wks file:
part / --source rootfs --fstype=ext4 --rootfs-dir=core-image-base
part /mnt/data1/ --fstype=ext4 --source rootfs --rootfs-dir=core-image-minimal
part /mnt/data2/ --fstype=ext4 --source rootfs --rootfs-dir=core-image-minimal

And this script

$bitbake core-image-minimal core-image-base syslinux
$losetup --partscan --find --read-only --show test*direct
$sudo mount /dev/loop0p1 /mnt
$ls -lan /mnt
otal 40
drwxr-xr-x 18    0    0  1024 May 11 16:11 .
drwxr-xr-x 25    0    0  4096 May  6 06:31 ..
drwxr-xr-x  2 1000 1000  3072 May 11 15:51 bin
drwxr-xr-x  2 1000 1000  1024 May 11 13:59 boot
drwxr-xr-x  2 1000 1000  1024 May 11 13:59 dev
drwxr-xr-x 25 1000 1000  3072 May 11 15:51 etc
drwxr-xr-x  3 1000 1000  1024 May 11 13:59 home
drwxr-xr-x  6 1000 1000  3072 May 11 15:51 lib
drwx--  2    0    0 12288 May 11 16:11 lost+found
drwxr-xr-x  2 1000 1000  1024 May 11 13:59 media
drwxr-xr-x  3 1000 1000  1024 May 11 15:50 mnt
drwxr-xr-x  2 1000 1000  1024 May 11 13:59 proc
drwxr-xr-x  2 1000 1000  1024 May 11 15:51 run
drwxr-xr-x  2 1000 1000  3072 May 11 15:51 sbin
drwxr-xr-x  2 1000 1000  1024 May 11 13:59 sys
drwxr-xr-t  2 1000 1000  1024 May 11 13:59 tmp
drwxr-xr-x 10 1000 1000  1024 May 11 14:54 usr
drwxr-xr-x  8 1000 1000  1024 May 11 14:55 var
$sudo losetup -d /dev/loop0

Signed-off-by: Ricardo Ribalda Delgado 
---
 scripts/lib/wic/partition.py | 2 +-
 scripts/lib/wic/plugins/imager/direct.py | 4 
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/scripts/lib/wic/partition.py b/scripts/lib/wic/partition.py
index 3fe5c4e26c..c73af9d427 100644
--- a/scripts/lib/wic/partition.py
+++ b/scripts/lib/wic/partition.py
@@ -211,7 +211,7 @@ class Partition():
 """
 p_prefix = os.environ.get("PSEUDO_PREFIX", "%s/usr" % native_sysroot)
 p_localstatedir = os.environ.get("PSEUDO_LOCALSTATEDIR",
- "%s/../pseudo" %  
get_bitbake_var("IMAGE_ROOTFS"))
+ "%s/../pseudo" %  rootfs_dir)
 p_passwd = os.environ.get("PSEUDO_PASSWD", rootfs_dir)
 p_nosymlinkexp = os.environ.get("PSEUDO_NOSYMLINKEXP", "1")
 pseudo = "export PSEUDO_PREFIX=%s;" % p_prefix
diff --git a/scripts/lib/wic/plugins/imager/direct.py 
b/scripts/lib/wic/plugins/imager/direct.py
index 1fa6b917e6..81583e97b9 100644
--- a/scripts/lib/wic/plugins/imager/direct.py
+++ b/scripts/lib/wic/plugins/imager/direct.py
@@ -122,6 +122,10 @@ class DirectPlugin(ImagerPlugin):
 if self._update_fstab(fstab_lines, self.parts):
 # copy rootfs dir to workdir to update fstab
 # as rootfs can be used by other tasks and can't be modified
+new_pseudo = os.path.realpath(os.path.join(self.workdir, "pseudo"))
+from_dir = os.path.join(os.path.join(image_rootfs, ".."), "pseudo")
+from_dir = os.path.realpath(from_dir)
+copyhardlinktree(from_dir, new_pseudo)
 new_rootfs = os.path.realpath(os.path.join(self.workdir, 
"rootfs_copy"))
 copyhardlinktree(image_rootfs, new_rootfs)
 fstab_path = os.path.join(new_rootfs, 'etc/fstab')
-- 
2.17.0

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


Re: [OE-core] Question about multi rootfs UIDs when using wic

2018-05-11 Thread Ricardo Ribalda Delgado
Hello

So this is what I have tried out:

I have downloaded master from openembedded-core
(f04e6bd144deb0c8fe2742f66b18904b6619a502)
then:
bitbake core-image-minimal core-image-base syslinux

Create a file  test.wks
part / --source rootfs --fstype=ext4 --rootfs-dir=core-image-base
part /mnt/data1/ --fstype=ext4 --source rootfs
--rootfs-dir=core-image-minimal
part /mnt/data2/ --fstype=ext4 --source rootfs
--rootfs-dir=core-image-minimal

bootloader --timeout=0


Then:
losetup --partscan --find --read-only --show test*direct
sudo mount /dev/loop0p1 /mnt
ls -lan /mnt
total 40
drwxr-xr-x 1800  1024 May 11 16:11 .
drwxr-xr-x 2500  4096 May  6 06:31 ..
drwxr-xr-x  2 1000 1000  3072 May 11 15:51 bin
drwxr-xr-x  2 1000 1000  1024 May 11 13:59 boot
drwxr-xr-x  2 1000 1000  1024 May 11 13:59 dev
drwxr-xr-x 25 1000 1000  3072 May 11 15:51 etc
drwxr-xr-x  3 1000 1000  1024 May 11 13:59 home
drwxr-xr-x  6 1000 1000  3072 May 11 15:51 lib
drwx--  200 12288 May 11 16:11 lost+found
drwxr-xr-x  2 1000 1000  1024 May 11 13:59 media
drwxr-xr-x  3 1000 1000  1024 May 11 15:50 mnt
drwxr-xr-x  2 1000 1000  1024 May 11 13:59 proc
drwxr-xr-x  2 1000 1000  1024 May 11 15:51 run
drwxr-xr-x  2 1000 1000  3072 May 11 15:51 sbin
drwxr-xr-x  2 1000 1000  1024 May 11 13:59 sys
drwxr-xr-t  2 1000 1000  1024 May 11 13:59 tmp
drwxr-xr-x 10 1000 1000  1024 May 11 14:54 usr
drwxr-xr-x  8 1000 1000  1024 May 11 14:55 var


With my patch:
ricardo@neopili:/tmp/openembedded-core/build$ ls -lan /mnt
total 40
drwxr-xr-x 18 0 0  1024 May 11 16:18 .
drwxr-xr-x 25 0 0  4096 May  6 06:31 ..
drwxr-xr-x  2 0 0  3072 May 11 15:51 bin
drwxr-xr-x  2 0 0  1024 May 11 13:59 boot
drwxr-xr-x  2 0 0  1024 May 11 13:59 dev
drwxr-xr-x 25 0 0  3072 May 11 15:51 etc
drwxr-xr-x  3 0 0  1024 May 11 13:59 home
drwxr-xr-x  6 0 0  3072 May 11 15:51 lib
drwx--  2 0 0 12288 May 11 16:18 lost+found
drwxr-xr-x  2 0 0  1024 May 11 13:59 media
drwxr-xr-x  3 0 0  1024 May 11 15:50 mnt
drwxr-xr-x  2 0 0  1024 May 11 13:59 proc
drwxr-xr-x  2 0 0  1024 May 11 15:51 run
drwxr-xr-x  2 0 0  3072 May 11 15:51 sbin
drwxr-xr-x  2 0 0  1024 May 11 13:59 sys
drwxrwxrwt  2 0 0  1024 May 11 13:59 tmp
drwxr-xr-x 10 0 0  1024 May 11 14:54 usr
drwxr-xr-x  8 0 0  1024 May 11 14:55 var


I think that I am going to send a formal patch to the mailing list and see
if we get some feedback


Cheers!

On Tue, May 8, 2018 at 3:39 PM Volker Vogelhuber <
v.vogelhu...@digitalendoscopy.de> wrote:

> Hi Ricardo,

> On 07.05.2018 15:22, Ricardo Ribalda Delgado wrote:
> > In my case this patch does the trick
> Unfortunately your patch results in having the recovery image's UID and
> GID settings to be set to my current user instead of root. So no, your
> patch does not seem to work for me.
> I didn't have the time to check in detail what's wrong with your version.

> >
> > commit 269334f2400c6ee0c7b4fec7d9bf0f701e50c329 (HEAD -> europa,
origin/europa)
> > Author: Ricardo Ribalda Delgado 
> > Date:   Mon May 7 13:54:15 2018 +0200
> >
> >  wic: Fix partition files UIDs on multi rootfs images
> >
> > diff --git a/scripts/lib/wic/partition.py b/scripts/lib/wic/partition.py
> > index 84fe85d62b..49921e7494 100644
> > --- a/scripts/lib/wic/partition.py
> > +++ b/scripts/lib/wic/partition.py
> > @@ -206,7 +206,7 @@ class Partition():
> >   """
> >   p_prefix = os.environ.get("PSEUDO_PREFIX", "%s/usr" %
native_sysroot)
> >   p_localstatedir = os.environ.get("PSEUDO_LOCALSTATEDIR",
> > - "%s/../pseudo" %
> > get_bitbake_var("IMAGE_ROOTFS"))
> > + "%s/../pseudo" %  rootfs_dir)
> >   p_passwd = os.environ.get("PSEUDO_PASSWD", rootfs_dir)
> >   p_nosymlinkexp = os.environ.get("PSEUDO_NOSYMLINKEXP", "1")
> >   pseudo = "export PSEUDO_PREFIX=%s;" % p_prefix
> > diff --git a/scripts/lib/wic/plugins/imager/direct.py
> > b/scripts/lib/wic/plugins/imager/direct.py
> > index da1c061063..a90a47c926 100644
> > --- a/scripts/lib/wic/plugins/imager/direct.py
> > +++ b/scripts/lib/wic/plugins/imager/direct.py
> > @@ -121,6 +121,10 @@ class DirectPlugin(ImagerPlugin):
> >   if self._update_fstab(fstab_lines, self.parts):
> >   # copy rootfs dir to workdir to update fstab
> >   # as rootfs can be used by other tasks and can't be
modified
> > +new_pseudo = os.path.realpath(os.path.join(self.workdir,
"pseudo"))
> > +from_dir = os.path.join(os.path.join(image_rootfs, ".."),
"pseudo")
> > +from_dir = os.path.realpath(from_dir)
> > +copyhardlinktree(from_dir, new_pseudo)
> >   new_rootfs = os.path.realpath(os.path.join(self.workdir,
> > "rootfs_copy"))
> >   copyhardlinktree(image_rootfs, new_rootfs)
> >   fstab_path = os.path.join(new_rootfs, 'etc/fstab')
> >
> >
> >
> > Can you try it on your setup? If it also works for you I will 

Re: [OE-core] [PATCH 1/3] gcc-sanitizers: Package new liblsan objects built with gcc8

2018-05-11 Thread Dan McGregor
On 11 May 2018 at 00:52, Khem Raj  wrote:
> Fixes installed-vs-shipped QA errors
>
> Reported-by: Dan McGregor 

The email address I typically use in my git submissions is
dan.mcgre...@usask.ca. The gmail address is what I use only for
mailing lists.

> Signed-off-by: Khem Raj 
> ---
>  meta/recipes-devtools/gcc/gcc-sanitizers.inc | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-devtools/gcc/gcc-sanitizers.inc 
> b/meta/recipes-devtools/gcc/gcc-sanitizers.inc
> index 3b7e0028f2..e5e84526fa 100644
> --- a/meta/recipes-devtools/gcc/gcc-sanitizers.inc
> +++ b/meta/recipes-devtools/gcc/gcc-sanitizers.inc
> @@ -94,6 +94,7 @@ FILES_liblsan += "${libdir}/liblsan.so.*"
>  FILES_liblsan-dev += "\
>  ${libdir}/liblsan.so \
>  ${libdir}/liblsan.la \
> +${libdir}/liblsan_preinit.o \
>  "

This looks good.

>  FILES_liblsan-staticdev += "${libdir}/liblsan.a"
>
> --
> 2.17.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] [pyro][PATCH v2 2/2] gcc: Remove patch causing ICE on x86_64 valgrind compile (on x86-64 only)

2018-05-11 Thread André Draszik
From: André Draszik 

This is similar to commit f76ee525a75d, but instead of disabling
the patch on all builds, we only remove it for x86-64 builds, as
the original change's commit message mentioned issues with this
patch applied on that architecture only.

Signed-off-by: André Draszik 
---
 meta/recipes-devtools/gcc/gcc-6.4.inc | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/gcc/gcc-6.4.inc 
b/meta/recipes-devtools/gcc/gcc-6.4.inc
index 1803917f01..9a23863022 100644
--- a/meta/recipes-devtools/gcc/gcc-6.4.inc
+++ b/meta/recipes-devtools/gcc/gcc-6.4.inc
@@ -81,9 +81,11 @@ SRC_URI = "\
file://0048-sync-gcc-stddef.h-with-musl.patch \
file://0054_all_nopie-all-flags.patch \
file://0055-unwind_h-glibc26.patch \
-   
file://0056-LRA-PR70904-relax-the-restriction-on-subreg-reload-f.patch \
+   ${LRA_PR70904_PATCH} \
${BACKPORTS} \
 "
+LRA_PR70904_PATCH = 
"file://0056-LRA-PR70904-relax-the-restriction-on-subreg-reload-f.patch"
+LRA_PR70904_PATCH_x86-64 = ""
 BACKPORTS = "\
file://CVE-2016-6131.patch \

file://0057-ARM-PR-82445-suppress-32-bit-aligned-ldrd-strd-peeph.patch \
-- 
2.16.2

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


[OE-core] [PATCH 1/2] musl-utils: monitor commits for upstream tracking

2018-05-11 Thread Ross Burton
This repository is infrequently updated and doesn't really release, so just
watch for new commits.

Signed-off-by: Ross Burton 
---
 meta/recipes-core/musl/musl-utils.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-core/musl/musl-utils.bb 
b/meta/recipes-core/musl/musl-utils.bb
index 74b846df595..dd0ce330613 100644
--- a/meta/recipes-core/musl/musl-utils.bb
+++ b/meta/recipes-core/musl/musl-utils.bb
@@ -13,6 +13,8 @@ PV = "20170421"
 SRCREV = "fb5630138ccabbbc14a19d372096a04e42573c7d"
 SRC_URI = "git://github.com/boltlinux/musl-utils"
 
+UPSTREAM_CHECK_COMMITS = "1"
+
 inherit autotools
 
 S = "${WORKDIR}/git"
-- 
2.11.0

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


[OE-core] [PATCH 2/2] distcc: disable upstream checking for now

2018-05-11 Thread Ross Burton
Whilst we're using a fork of the upstream repository, disable upstream checking.
Once we upgrade to 3.3 this can be removed.

Signed-off-by: Ross Burton 
---
 meta/recipes-devtools/distcc/distcc_3.2.bb | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-devtools/distcc/distcc_3.2.bb 
b/meta/recipes-devtools/distcc/distcc_3.2.bb
index ee077495d5f..2b19d69000d 100644
--- a/meta/recipes-devtools/distcc/distcc_3.2.bb
+++ b/meta/recipes-devtools/distcc/distcc_3.2.bb
@@ -17,6 +17,9 @@ SRC_URI = "git://github.com/akuster/distcc.git;branch=${PV} \
 
 SRCREV = "d8b18df3e9dcbe4f092bed565835d3975e99432c"
 
+# Because we're using a fork currently, upstream checks don't work
+UPSTREAM_VERSION_UNKNOWN = "1"
+
 S = "${WORKDIR}/git"
 
 inherit autotools pkgconfig update-rc.d useradd systemd
-- 
2.11.0

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


Re: [OE-core] [pyro][PATCH 2/2] gcc: Remove patch causing ICE on x86_64 valgrind compile (on x86-64 only)

2018-05-11 Thread Peter Kjellerstedt
> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
> André Draszik
> Sent: den 11 maj 2018 10:10
> To: openembedded-core@lists.openembedded.org
> Subject: [OE-core] [pyro][PATCH 2/2] gcc: Remove patch causing ICE on
> x86_64 valgrind compile (on x86-64 only)
> 
> From: André Draszik 
> 
> This is similar to commit f76ee525a75d, but instead of disabling
> the patch on all builds, we only remove it for x86-64 builds, as
> the original change's commit message mentined issues with this

Change "mentined" to "mentioned".

> patch applied on that architecture only.
> 
> Signed-off-by: André Draszik 

//Peter

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


Re: [OE-core] [PATCH 2/2] rpm: Assume a max limit of 1024 open files

2018-05-11 Thread Peter Kjellerstedt
> -Original Message-
> From: Alexander Kanavin [mailto:alexander.kana...@linux.intel.com]
> Sent: den 11 maj 2018 07:44
> To: Peter Kjellerstedt ; openembedded-
> c...@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH 2/2] rpm: Assume a max limit of 1024 open
> files
> 
> On 05/11/2018 01:20 AM, Peter Kjellerstedt wrote:
> > If sysconf(_SC_OPEN_MAX) is much greater than the usual 1024 (for
> > example inside a Docker container), the performance drops sharply.
> 
> Please do not drop the link to the upstream bug when replacing one
> patch with another.

Right, forgot about that.

> You can also simply amend my patch and add your SOB.

Well, I thought it was more clear this way, since your patch removed 
the functionality that closed the files, whereas mine modifies it.

> Also, why assume specifically 1024? We either need to close all the
> open files, or none, and your patch creates a situation where only 
> some of the files may be closed. I'd say we should drop those two 
> code snippets altogether instead of hardcoding 1024 into them.

Well, my expectation was that there is a reason that they want to make 
sure that all open file descriptors have FD_CLOEXEC set so that they 
are closed when forking. At the same time I don't assume rpm to actually 
have more than 1024 files open at one time, so even if using 
sysconf(_SC_OPEN_MAX) is the right thing to do, using 1024 should work 
in practice.

However, I gave this some more thought, and maybe it would be better to 
let bitbake set the soft limit for max open files to, e.g., 1024. That 
way we would not need to modify the code in rpm as it would adapt itself 
automatically. I tried adding the following to bitbake_main and it worked:

import resource

# Set the maximum number of open files as there are performance problems
# with, e.g., rpm if this is unlimited (which it may be if running inside
# a Docker container).
(soft, hard) = resource.getrlimit(resource.RLIMIT_NOFILE)
soft = int(os.environ.get("BB_LIMIT_NOFILE", "1024"))
resource.setrlimit(resource.RLIMIT_NOFILE, (min(soft, hard), hard))

I do not know if bitbake_main is the right place for this, or if there is 
some more appropriate location for it. Richard?

I can send a new patch to add this, once I know where it should be added.

> Oh, and: please do comment in the upstream bug (e.g. with your
> benchmarks from the cover letter), otherwise upstream may do nothing
> because they're not using Docker.

Will do. I think suggesting that rpm should set the limit itself, as per 
my suggestion for bitbake above, might be an appropriate solution that 
they can accept.

> Alex

//Peter

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


Re: [OE-core] [PATCH 5/6] dbus-glib: upgrade to 0.110

2018-05-11 Thread Burton, Ross
If dbus-glib doesn't need --with-introspect-xml anymore then the dbus
recipe can stop installing it.

Ross

On 11 May 2018 at 03:20, Chen Qi  wrote:
> The obsolete '--with-introspect-xml' option is removed.
>
> Signed-off-by: Chen Qi 
> ---
>  meta/recipes-core/dbus/dbus-glib.inc  | 4 +---
>  meta/recipes-core/dbus/dbus-glib_0.108.bb | 4 
>  meta/recipes-core/dbus/dbus-glib_0.110.bb | 4 
>  3 files changed, 5 insertions(+), 7 deletions(-)
>  delete mode 100644 meta/recipes-core/dbus/dbus-glib_0.108.bb
>  create mode 100644 meta/recipes-core/dbus/dbus-glib_0.110.bb
>
> diff --git a/meta/recipes-core/dbus/dbus-glib.inc 
> b/meta/recipes-core/dbus/dbus-glib.inc
> index 55f710f..16dbf4f 100644
> --- a/meta/recipes-core/dbus/dbus-glib.inc
> +++ b/meta/recipes-core/dbus/dbus-glib.inc
> @@ -22,9 +22,7 @@ inherit autotools pkgconfig gettext bash-completion gtk-doc
>  PACKAGECONFIG ??= ""
>  PACKAGECONFIG[tests] = "--enable-tests,,,"
>
> -EXTRA_OECONF = 
> "--with-introspect-xml=${STAGING_DATADIR_NATIVE}/dbus/dbus-bus-introspect.xml 
> \
> -
> --with-dbus-binding-tool=${STAGING_BINDIR_NATIVE}/dbus-binding-tool"
> -EXTRA_OECONF_class-native = 
> "--with-introspect-xml=${STAGING_DATADIR_NATIVE}/dbus/dbus-bus-introspect.xml"
> +EXTRA_OECONF_class-target = 
> "--with-dbus-binding-tool=${STAGING_BINDIR_NATIVE}/dbus-binding-tool"
>
>  PACKAGES += "${PN}-tests"
>
> diff --git a/meta/recipes-core/dbus/dbus-glib_0.108.bb 
> b/meta/recipes-core/dbus/dbus-glib_0.108.bb
> deleted file mode 100644
> index 7a9a69e..000
> --- a/meta/recipes-core/dbus/dbus-glib_0.108.bb
> +++ /dev/null
> @@ -1,4 +0,0 @@
> -require dbus-glib.inc
> -
> -SRC_URI[md5sum] = "a66a613705870752ca9786e0359aea97"
> -SRC_URI[sha256sum] = 
> "9f340c7e2352e9cdf113893ca77ca9075d9f8d5e81476bf2bf361099383c602c"
> diff --git a/meta/recipes-core/dbus/dbus-glib_0.110.bb 
> b/meta/recipes-core/dbus/dbus-glib_0.110.bb
> new file mode 100644
> index 000..8120505
> --- /dev/null
> +++ b/meta/recipes-core/dbus/dbus-glib_0.110.bb
> @@ -0,0 +1,4 @@
> +require dbus-glib.inc
> +
> +SRC_URI[md5sum] = "d7cebf1d69445cbd28b4983392145192"
> +SRC_URI[sha256sum] = 
> "7ce4760cf66c69148f6bd6c92feaabb8812dee30846b24cd0f7395c436d7e825"
> --
> 1.9.1
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [pyro][PATCH 2/2] gcc: Remove patch causing ICE on x86_64 valgrind compile (on x86-64 only)

2018-05-11 Thread André Draszik
From: André Draszik 

This is similar to commit f76ee525a75d, but instead of disabling
the patch on all builds, we only remove it for x86-64 builds, as
the original change's commit message mentined issues with this
patch applied on that architecture only.

Signed-off-by: André Draszik 
---
 meta/recipes-devtools/gcc/gcc-6.4.inc | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/gcc/gcc-6.4.inc 
b/meta/recipes-devtools/gcc/gcc-6.4.inc
index 1803917f01..9a23863022 100644
--- a/meta/recipes-devtools/gcc/gcc-6.4.inc
+++ b/meta/recipes-devtools/gcc/gcc-6.4.inc
@@ -81,9 +81,11 @@ SRC_URI = "\
file://0048-sync-gcc-stddef.h-with-musl.patch \
file://0054_all_nopie-all-flags.patch \
file://0055-unwind_h-glibc26.patch \
-   
file://0056-LRA-PR70904-relax-the-restriction-on-subreg-reload-f.patch \
+   ${LRA_PR70904_PATCH} \
${BACKPORTS} \
 "
+LRA_PR70904_PATCH = 
"file://0056-LRA-PR70904-relax-the-restriction-on-subreg-reload-f.patch"
+LRA_PR70904_PATCH_x86-64 = ""
 BACKPORTS = "\
file://CVE-2016-6131.patch \

file://0057-ARM-PR-82445-suppress-32-bit-aligned-ldrd-strd-peeph.patch \
-- 
2.16.2

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


[OE-core] [pyro][PATCH 1/2] Revert "gcc: Remove patch causing ICE on x86_64 valgrind compile"

2018-05-11 Thread André Draszik
From: André Draszik 

This reverts commit f76ee525a75dd6e443743bf723ad4511707c7f49.

With the patch removed we otherwise get QEMU (mipsel) segfaults:
--- SIGSEGV {si_signo=SIGSEGV, si_code=1, si_addr = 0x000d4e40} ---
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault

Signed-off-by: André Draszik 
---
 meta/recipes-devtools/gcc/gcc-6.4.inc  |  1 +
 ...-relax-the-restriction-on-subreg-reload-f.patch | 51 ++
 2 files changed, 52 insertions(+)
 create mode 100644 
meta/recipes-devtools/gcc/gcc-6.4/0056-LRA-PR70904-relax-the-restriction-on-subreg-reload-f.patch

diff --git a/meta/recipes-devtools/gcc/gcc-6.4.inc 
b/meta/recipes-devtools/gcc/gcc-6.4.inc
index daa9e42af8..1803917f01 100644
--- a/meta/recipes-devtools/gcc/gcc-6.4.inc
+++ b/meta/recipes-devtools/gcc/gcc-6.4.inc
@@ -81,6 +81,7 @@ SRC_URI = "\
file://0048-sync-gcc-stddef.h-with-musl.patch \
file://0054_all_nopie-all-flags.patch \
file://0055-unwind_h-glibc26.patch \
+   
file://0056-LRA-PR70904-relax-the-restriction-on-subreg-reload-f.patch \
${BACKPORTS} \
 "
 BACKPORTS = "\
diff --git 
a/meta/recipes-devtools/gcc/gcc-6.4/0056-LRA-PR70904-relax-the-restriction-on-subreg-reload-f.patch
 
b/meta/recipes-devtools/gcc/gcc-6.4/0056-LRA-PR70904-relax-the-restriction-on-subreg-reload-f.patch
new file mode 100644
index 00..231f147619
--- /dev/null
+++ 
b/meta/recipes-devtools/gcc/gcc-6.4/0056-LRA-PR70904-relax-the-restriction-on-subreg-reload-f.patch
@@ -0,0 +1,51 @@
+From a582b0a53d1dc8604a201348b99ca8de48784e7e Mon Sep 17 00:00:00 2001
+From: jiwang 
+Date: Thu, 12 May 2016 17:00:52 +
+Subject: [PATCH] [LRA] PR70904, relax the restriction on subreg reload for
+ wide mode
+
+2016-05-12  Jiong Wang  
+
+gcc/
+  PR rtl-optimization/70904
+  * lra-constraint.c (process_addr_reg): Relax the restriction on
+  subreg reload for wide mode.
+
+git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@236181 
138bc75d-0d04-0410-961f-82ee72b054a4
+---
+Upstream-Status: Backport
+Signed-off-by: Khem Raj 
+
+ gcc/lra-constraints.c | 16 +++-
+ 1 file changed, 15 insertions(+), 1 deletion(-)
+
+diff --git a/gcc/lra-constraints.c b/gcc/lra-constraints.c
+index f96fd458e23..73fb72a2ea5 100644
+--- a/gcc/lra-constraints.c
 b/gcc/lra-constraints.c
+@@ -1326,7 +1326,21 @@ process_addr_reg (rtx *loc, bool check_only_p, rtx_insn 
**before, rtx_insn **aft
+ 
+   subreg_p = GET_CODE (*loc) == SUBREG;
+   if (subreg_p)
+-loc = _REG (*loc);
++{
++  reg = SUBREG_REG (*loc);
++  mode = GET_MODE (reg);
++
++  /* For mode with size bigger than ptr_mode, there unlikely to be "mov"
++   between two registers with different classes, but there normally will
++   be "mov" which transfers element of vector register into the general
++   register, and this normally will be a subreg which should be reloaded
++   as a whole.  This is particularly likely to be triggered when
++   -fno-split-wide-types specified.  */
++  if (in_class_p (reg, cl, _class)
++|| GET_MODE_SIZE (mode) <= GET_MODE_SIZE (ptr_mode))
++   loc = _REG (*loc);
++}
++
+   reg = *loc;
+   mode = GET_MODE (reg);
+   if (! REG_P (reg))
+-- 
+2.14.2
+
-- 
2.16.2

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


[OE-core] [PATCH 2/3] libxcrypt: Fix build with gcc8

2018-05-11 Thread Khem Raj
Reported-by: Martin Jansa 
Signed-off-by: Khem Raj 
---
 ...format-truncation-warning-with-gcc-8.patch | 36 +++
 .../recipes-core/libxcrypt/libxcrypt_4.0.0.bb |  4 ++-
 2 files changed, 39 insertions(+), 1 deletion(-)
 create mode 100644 
meta/recipes-core/libxcrypt/libxcrypt/0001-disable-format-truncation-warning-with-gcc-8.patch

diff --git 
a/meta/recipes-core/libxcrypt/libxcrypt/0001-disable-format-truncation-warning-with-gcc-8.patch
 
b/meta/recipes-core/libxcrypt/libxcrypt/0001-disable-format-truncation-warning-with-gcc-8.patch
new file mode 100644
index 00..654eae6c6a
--- /dev/null
+++ 
b/meta/recipes-core/libxcrypt/libxcrypt/0001-disable-format-truncation-warning-with-gcc-8.patch
@@ -0,0 +1,36 @@
+From c8c5908611e44a649489e8d217528fedc4864e14 Mon Sep 17 00:00:00 2001
+From: Khem Raj 
+Date: Thu, 10 May 2018 13:32:20 -0700
+Subject: [PATCH] disable format-truncation warning with gcc-8
+
+Upstream-Status: Pending
+
+Signed-off-by: Khem Raj 
+---
+ crypt-sunmd5.c | 6 ++
+ 1 file changed, 6 insertions(+)
+
+diff --git a/crypt-sunmd5.c b/crypt-sunmd5.c
+index 4c85b7f..3e838cd 100644
+--- a/crypt-sunmd5.c
 b/crypt-sunmd5.c
+@@ -151,6 +151,11 @@ getrounds (const char *s)
+   return ((uint32_t)val);
+ }
+ 
++#pragma GCC diagnostic push
++#if defined(__GNUC__) && (__GNUC__ >= 8)
++#pragma GCC diagnostic ignored "-Wformat-truncation"
++#endif
++
+ void
+ gensalt_sunmd5_rn (unsigned long count,
+const uint8_t *rbytes, size_t nrbytes,
+@@ -189,6 +194,7 @@ gensalt_sunmd5_rn (unsigned long count,
+ "$" CRYPT_ALGNAME "," ROUNDS "%u$%s$",
+ (unsigned int)count, rndstr);
+ }
++#pragma GCC diagnostic pop
+ 
+ void
+ crypt_sunmd5_rn (const char *phrase, const char *setting,
diff --git a/meta/recipes-core/libxcrypt/libxcrypt_4.0.0.bb 
b/meta/recipes-core/libxcrypt/libxcrypt_4.0.0.bb
index a1be4be7ef..8cc5edac49 100644
--- a/meta/recipes-core/libxcrypt/libxcrypt_4.0.0.bb
+++ b/meta/recipes-core/libxcrypt/libxcrypt_4.0.0.bb
@@ -12,7 +12,9 @@ inherit autotools
 SRCREV ?= "215b32aa4e0b255c3356a96bd6d257661bad73ca"
 SRCBRANCH ?= "master"
 
-SRC_URI = "git://github.com/besser82/libxcrypt.git;branch=${SRCBRANCH}"
+SRC_URI = "git://github.com/besser82/libxcrypt.git;branch=${SRCBRANCH} \
+   file://0001-disable-format-truncation-warning-with-gcc-8.patch \
+   "
 
 PROVIDES = "virtual/crypt"
 
-- 
2.17.0

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


[OE-core] [PATCH 3/3] uninative-tarball: Add libjis and euc-jp gconv files

2018-05-11 Thread Khem Raj
packages like fontforge-native fail with mysterious errors like

| ../../git/inc/gwwiconv.h:44:21: error: conflicting types for ‘gww_iconv_close’
|  #define iconv_close gww_iconv_close
|  ^~~
| ../../git/inc/gwwiconv.h:37:13: note: previous declaration of 
‘gww_iconv_close’ was here
|  extern void gww_iconv_close( gww_iconv_t cd);
|  ^~~

The reason behind this is that a check for iconv fails during native
configure run, the check fails because the autoconf test to check for iconv
pokes for these gconv's in test runs before declaring iconv support successful.

Therefore when uninative is active the package fails to build but when
uninative is inactive all works fine. this patch fixes that

Signed-off-by: Khem Raj 
---
 meta/recipes-core/meta/uninative-tarball.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-core/meta/uninative-tarball.bb 
b/meta/recipes-core/meta/uninative-tarball.bb
index 38c3a314e1..c38c2a445e 100644
--- a/meta/recipes-core/meta/uninative-tarball.bb
+++ b/meta/recipes-core/meta/uninative-tarball.bb
@@ -12,6 +12,8 @@ TOOLCHAIN_HOST_TASK = "\
 nativesdk-glibc-gconv-iso8859-1 \
 nativesdk-glibc-gconv-utf-16 \
 nativesdk-glibc-gconv-cp1252 \
+nativesdk-glibc-gconv-euc-jp \
+nativesdk-glibc-gconv-libjis \
 nativesdk-patchelf \
 nativesdk-libxcrypt \
 "
-- 
2.17.0

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


[OE-core] [PATCH 1/3] gcc-sanitizers: Package new liblsan objects built with gcc8

2018-05-11 Thread Khem Raj
Fixes installed-vs-shipped QA errors

Reported-by: Dan McGregor 
Signed-off-by: Khem Raj 
---
 meta/recipes-devtools/gcc/gcc-sanitizers.inc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-devtools/gcc/gcc-sanitizers.inc 
b/meta/recipes-devtools/gcc/gcc-sanitizers.inc
index 3b7e0028f2..e5e84526fa 100644
--- a/meta/recipes-devtools/gcc/gcc-sanitizers.inc
+++ b/meta/recipes-devtools/gcc/gcc-sanitizers.inc
@@ -94,6 +94,7 @@ FILES_liblsan += "${libdir}/liblsan.so.*"
 FILES_liblsan-dev += "\
 ${libdir}/liblsan.so \
 ${libdir}/liblsan.la \
+${libdir}/liblsan_preinit.o \
 "
 FILES_liblsan-staticdev += "${libdir}/liblsan.a"
 
-- 
2.17.0

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


[OE-core] [PATCH] boost: add contract lib

2018-05-11 Thread mingli.yu
From: Mingli Yu 

Add the contract lib which implements contract
programming (a.k.a., Design by Contract or DbC) [1]
for the C++ programming language.

Signed-off-by: Mingli Yu 
---
 meta/recipes-support/boost/boost.inc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-support/boost/boost.inc 
b/meta/recipes-support/boost/boost.inc
index b447897a0c..6984bee777 100644
--- a/meta/recipes-support/boost/boost.inc
+++ b/meta/recipes-support/boost/boost.inc
@@ -9,6 +9,7 @@ BOOST_LIBS = "\
atomic \
chrono \
container \
+   contract \
date_time \
exception \
filesystem \
-- 
2.11.0

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


Re: [OE-core] [PATCH] boost: add contract lib

2018-05-11 Thread Yu, Mingli

Please ignore this patch.

Thanks,

On 2018年05月11日 11:34, mingli...@windriver.com wrote:

From: Mingli Yu 

Add the contract lib

Signed-off-by: Mingli Yu 
---
  meta/recipes-support/boost/boost.inc | 1 +
  1 file changed, 1 insertion(+)

diff --git a/meta/recipes-support/boost/boost.inc 
b/meta/recipes-support/boost/boost.inc
index b447897a0c..6984bee777 100644
--- a/meta/recipes-support/boost/boost.inc
+++ b/meta/recipes-support/boost/boost.inc
@@ -9,6 +9,7 @@ BOOST_LIBS = "\
atomic \
chrono \
container \
+   contract \
date_time \
exception \
filesystem \


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