[OE-core] [PATCH V2 1/4] image_types_wic.bbclass: adjust WKS_FILE_DEPENDS_DEFAULT

2017-08-03 Thread liu . ming50
From: Ming Liu 

Let WKS_FILE_DEPENDS_DEFAULT default to include all native recipes
listed in NATIVE_RECIPES of wic, as a temporary solution to avoid
breaking wic image build.

Recommended solution is to use WKS_FILE_DEPENDS in image recipes
together with WKS_FILE to specify dependencies.

Drop do_image_wic depends varflags, it's not needed any more, all
the dependencies will be handled by WKS_FILE_DEPENDS.

Signed-off-by: Ming Liu 
---
 meta/classes/image_types_wic.bbclass | 21 +++--
 1 file changed, 19 insertions(+), 2 deletions(-)

diff --git a/meta/classes/image_types_wic.bbclass 
b/meta/classes/image_types_wic.bbclass
index b825b47..ad578c4 100644
--- a/meta/classes/image_types_wic.bbclass
+++ b/meta/classes/image_types_wic.bbclass
@@ -39,9 +39,26 @@ IMAGE_CMD_wic[vardepsexclude] = "WKS_FULL_PATH WKS_FILES"
 USING_WIC = "${@bb.utils.contains_any('IMAGE_FSTYPES', 'wic ' + ' 
'.join('wic.%s' % c for c in '${CONVERSIONTYPES}'.split()), '1', '', d)}"
 WKS_FILE_CHECKSUM = "${@'${WKS_FULL_PATH}:%s' % 
os.path.exists('${WKS_FULL_PATH}') if '${USING_WIC}' else ''}"
 do_image_wic[file-checksums] += "${WKS_FILE_CHECKSUM}"
-do_image_wic[depends] += "${@' '.join('%s-native:do_populate_sysroot' % r for 
r in ('parted', 'gptfdisk', 'dosfstools', 'mtools'))}"
 
-WKS_FILE_DEPENDS_DEFAULT = "syslinux-native bmap-tools-native cdrtools-native 
btrfs-tools-native squashfs-tools-native e2fsprogs-native"
+# Defaults to include all native recipes listed in NATIVE_RECIPES of
+# wic, as a temporary solution to avoid breaking wic image build.
+# Recommended solution is to use WKS_FILE_DEPENDS in image recipes
+# together with WKS_FILE to specify dependencies.
+WKS_FILE_DEPENDS_DEFAULT = "\
+bmap-tools-native \
+grub-efi-native \
+syslinux-native \
+mtools-native \
+dosfstools-native \
+cdrtools-native \
+btrfs-tools-native \
+e2fsprogs-native \
+squashfs-tools-native \
+util-linux-native \
+parted-native \
+gptfdisk-native \
+"
+
 WKS_FILE_DEPENDS_BOOTLOADERS = ""
 WKS_FILE_DEPENDS_BOOTLOADERS_x86 = "syslinux grub-efi systemd-boot"
 WKS_FILE_DEPENDS_BOOTLOADERS_x86-64 = "syslinux grub-efi systemd-boot"
-- 
2.7.4

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


[OE-core] [PATCH V2 4/4] qemux86.conf: set WKS_FILE_DEPENDS

2017-08-03 Thread liu . ming50
From: Ming Liu 

To involve in a minimal set of dependencies required by directdisk.wks.

Drop do_image_wic depends varflags, it's not needed any more.

Signed-off-by: Ming Liu 
---
 meta/conf/machine/qemux86.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/conf/machine/qemux86.conf b/meta/conf/machine/qemux86.conf
index c26dda2..01490b7 100644
--- a/meta/conf/machine/qemux86.conf
+++ b/meta/conf/machine/qemux86.conf
@@ -29,4 +29,4 @@ MACHINE_FEATURES += "x86"
 MACHINE_ESSENTIAL_EXTRA_RDEPENDS += "v86d"
 
 WKS_FILE ?= "directdisk.wks"
-do_image_wic[depends] += "syslinux:do_populate_sysroot 
syslinux-native:do_populate_sysroot mtools-native:do_populate_sysroot 
dosfstools-native:do_populate_sysroot"
+WKS_FILE_DEPENDS ?= "syslinux syslinux-native mtools-native dosfstools-native 
e2fsprogs-native parted-native"
-- 
2.7.4

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


[OE-core] [PATCH V2 0/4] Set WKS_FILE_DEPENDS/Clean up some do_image_wic depends

2017-08-03 Thread liu . ming50
From: Ming Liu 

Ming Liu (4):
  image_types_wic.bbclass: adjust WKS_FILE_DEPENDS_DEFAULT
  wic-image-minimal.bb: add parted-native e2fsprogs-native to
WKS_FILE_DEPENDS
  qemux86-64.conf: set WKS_FILE_DEPENDS
  qemux86.conf: set WKS_FILE_DEPENDS

 .../recipes-test/images/wic-image-minimal.bb|  2 +-
 meta/classes/image_types_wic.bbclass| 21 +++--
 meta/conf/machine/qemux86-64.conf   |  2 +-
 meta/conf/machine/qemux86.conf  |  2 +-
 4 files changed, 22 insertions(+), 5 deletions(-)

-- 
2.7.4

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


[OE-core] [PATCH V2 3/4] qemux86-64.conf: set WKS_FILE_DEPENDS

2017-08-03 Thread liu . ming50
From: Ming Liu 

To involve in a minimal set of dependencies required by directdisk.wks.

Drop do_image_wic depends varflags, it's not needed any more.

Signed-off-by: Ming Liu 
---
 meta/conf/machine/qemux86-64.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/conf/machine/qemux86-64.conf 
b/meta/conf/machine/qemux86-64.conf
index 10189cb..8fb9fd5 100644
--- a/meta/conf/machine/qemux86-64.conf
+++ b/meta/conf/machine/qemux86-64.conf
@@ -30,4 +30,4 @@ MACHINE_FEATURES += "x86"
 MACHINE_ESSENTIAL_EXTRA_RDEPENDS += "v86d"
 
 WKS_FILE ?= "directdisk.wks"
-do_image_wic[depends] += "syslinux:do_populate_sysroot 
syslinux-native:do_populate_sysroot mtools-native:do_populate_sysroot 
dosfstools-native:do_populate_sysroot"
+WKS_FILE_DEPENDS ?= "syslinux syslinux-native mtools-native dosfstools-native 
e2fsprogs-native parted-native"
-- 
2.7.4

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


[OE-core] [PATCH V2 2/4] wic-image-minimal.bb: add parted-native e2fsprogs-native to WKS_FILE_DEPENDS

2017-08-03 Thread liu . ming50
From: Ming Liu 

They are needed by wic to generate a image based on
wic-image-minimal.wic.

Signed-off-by: Ming Liu 
---
 meta-selftest/recipes-test/images/wic-image-minimal.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-selftest/recipes-test/images/wic-image-minimal.bb 
b/meta-selftest/recipes-test/images/wic-image-minimal.bb
index e1da203..5a83af5 100644
--- a/meta-selftest/recipes-test/images/wic-image-minimal.bb
+++ b/meta-selftest/recipes-test/images/wic-image-minimal.bb
@@ -6,7 +6,7 @@ IMAGE_INSTALL = "packagegroup-core-boot"
 
 IMAGE_FSTYPES = "wic"
 
-WKS_FILE_DEPENDS = "syslinux syslinux-native dosfstools-native mtools-native 
gptfdisk-native"
+WKS_FILE_DEPENDS = "syslinux syslinux-native dosfstools-native mtools-native 
gptfdisk-native parted-native e2fsprogs-native"
 
 LIC_FILES_CHKSUM = 
"file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
 
-- 
2.7.4

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


Re: [OE-core] [PATCH 1/1] expat: upgrade to 2.2.2

2017-08-03 Thread Dengke Du

OK!


On 2017年08月04日 00:48, Khem Raj wrote:

On Thu, Aug 3, 2017 at 9:42 AM, Burton, Ross  wrote:

On 24 July 2017 at 11:23, Burton, Ross  wrote:

I've filed a bug upstream about the failure on Debian 8:
https://github.com/libexpat/libexpat/issues/97


And this bug is now resolved.  expat in git can read /dev/urandom directly
if it doesn't find the syscalls it wants.

Sounds good. Denke, when you refresh patch please include this patch along

http://git.openembedded.org/openembedded-core-contrib/tree/meta/recipes-core/expat/expat/libtool-tag.patch?h=kraj/master&id=01929853a8346ba0fc27090150ebc506d1c5cd1e

which was not there in your v1.


Ross


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


[OE-core] [PATCH] recipes-kernel: linux-dummy: provide dummy vmlinux package

2017-08-03 Thread Ruslan Bilovol
oprofile package depends on kernel-vmlinux package
through RRECOMMENDS dependency. Thus provide it
here to satisfy dependencies.

Signed-off-by: Ruslan Bilovol 
---
 meta/recipes-kernel/linux/linux-dummy.bb | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-kernel/linux/linux-dummy.bb 
b/meta/recipes-kernel/linux/linux-dummy.bb
index 994ac74..e1c7f76 100644
--- a/meta/recipes-kernel/linux/linux-dummy.bb
+++ b/meta/recipes-kernel/linux/linux-dummy.bb
@@ -13,10 +13,14 @@ PACKAGES_DYNAMIC += "^kernel-module-.*"
 PACKAGES_DYNAMIC += "^kernel-image-.*"
 PACKAGES_DYNAMIC += "^kernel-firmware-.*"
 
-PACKAGES += "kernel-modules"
+PACKAGES += "kernel-modules kernel-vmlinux"
 FILES_kernel-modules = ""
 ALLOW_EMPTY_kernel-modules = "1"
 DESCRIPTION_kernel-modules = "Kernel modules meta package"
+FILES_kernel-vmlinux = ""
+ALLOW_EMPTY_kernel-vmlinux = "1"
+DESCRIPTION_kernel-vmlinux = "Kernel vmlinux meta package"
+
 
 INHIBIT_DEFAULT_DEPS = "1"
 
-- 
1.9.1

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


[OE-core] [poky][pyro][PATCH 0/1] backport IFF_LOWER_UP fix for 4.10+musl

2017-08-03 Thread Alejandro Mery
From: Alejandro Mery 

This commit cherry-picks a fix already applied to master and accepted upstream

commit: 868486c238780ce4a11d9ec9a38e40cb6c1cfc01

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

André Draszik (1):
  linux-libc-headers: fix duplicate IFF_LOWER_UP DORMANT ECHO on musl

 h-musl-_does_-define-IFF_LOWER_UP-DORMAN.patch | 46 ++
 .../linux-libc-headers/linux-libc-headers_4.10.bb  |  1 +
 2 files changed, 47 insertions(+)
 create mode 100644 
meta/recipes-kernel/linux-libc-headers/linux-libc-headers/0001-libc-compat.h-musl-_does_-define-IFF_LOWER_UP-DORMAN.patch

-- 
2.13.0


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


[OE-core] [poky][pyro][PATCH 1/1] linux-libc-headers: fix duplicate IFF_LOWER_UP DORMANT ECHO on musl

2017-08-03 Thread Alejandro Mery
From: André Draszik 

musl _does_ define IFF_LOWER_UP DORMANT ECHO so we should
prevent redefinition of these when on musl.

As per the included patch, this can be triggered by
(from connman 6to4.c):
include 
include 
include 
include 
include 
include 
include 
include 
include 
include 
include 
include 
include 
include 

In file included from ../git/src/6to4.c:34:0:
.../usr/include/linux/if.h:97:2: error: expected identifier before numeric 
constant
  IFF_LOWER_UP   = 1<<16, /* __volatile__ */
  ^

This is because at that time, IFF_LOWER_UP has been converted
to 0x1 already:
enum net_device_flags {
 0x1 = 1<<16,
 0x2 = 1<<17,
 0x4 = 1<<18,

};

Backport a patch that addresses this.

(From OE-Core rev: 24dc2200047bae5d32c168d2625d96ac08a93d3d)

Signed-off-by: André Draszik 
Signed-off-by: Ross Burton 
Signed-off-by: Richard Purdie 
---
 h-musl-_does_-define-IFF_LOWER_UP-DORMAN.patch | 46 ++
 .../linux-libc-headers/linux-libc-headers_4.10.bb  |  1 +
 2 files changed, 47 insertions(+)
 create mode 100644 
meta/recipes-kernel/linux-libc-headers/linux-libc-headers/0001-libc-compat.h-musl-_does_-define-IFF_LOWER_UP-DORMAN.patch

diff --git 
a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers/0001-libc-compat.h-musl-_does_-define-IFF_LOWER_UP-DORMAN.patch
 
b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers/0001-libc-compat.h-musl-_does_-define-IFF_LOWER_UP-DORMAN.patch
new file mode 100644
index 00..bde2132ebf
--- /dev/null
+++ 
b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers/0001-libc-compat.h-musl-_does_-define-IFF_LOWER_UP-DORMAN.patch
@@ -0,0 +1,46 @@
+Content-Type: text/plain; charset="utf-8"
+MIME-Version: 1.0
+Content-Transfer-Encoding: 7bit
+Subject: [v2,2/3] uapi glibc compat: fix build if libc defines IFF_ECHO
+From: Hauke Mehrtens 
+X-Patchwork-Id: 9686293
+Message-Id: <20170418210036.26039-3-ha...@hauke-m.de>
+To: da...@davemloft.net, net...@vger.kernel.org
+Cc: linux-ker...@vger.kernel.org, ja...@redhat.com, j...@openwrt.org,
+ david.heidelber...@ixit.cz, maillist-li...@barfooze.de,
+ mikko.rap...@iki.fi, dw...@infradead.org, Hauke Mehrtens 
+Date: Tue, 18 Apr 2017 23:00:35 +0200
+
+musl 1.1.15 defines IFF_ECHO and the other net_device_flags options.
+When a user application includes linux/if.h and net/if.h the compile
+will fail.
+
+Activate __UAPI_DEF_IF_NET_DEVICE_FLAGS_LOWER_UP_DORMANT_ECHO only when
+it is needed. This should also make this work in case glibc will add
+these defines.
+
+Acked-by: Mikko Rapeli 
+Signed-off-by: Hauke Mehrtens 
+---
+Upstream-Status: Submitted [https://patchwork.kernel.org/patch/9686293/]
+Signed-off-by: André Draszik 
+Acked-by: Stephane Ayotte 
+ include/uapi/linux/libc-compat.h | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/include/uapi/linux/libc-compat.h 
b/include/uapi/linux/libc-compat.h
+index 43a81136ea6e..ce2fa8a4ced6 100644
+--- a/include/uapi/linux/libc-compat.h
 b/include/uapi/linux/libc-compat.h
+@@ -64,9 +64,11 @@
+ /* Everything up to IFF_DYNAMIC, matches net/if.h until glibc 2.23 */
+ #define __UAPI_DEF_IF_NET_DEVICE_FLAGS 0
+ /* For the future if glibc adds IFF_LOWER_UP, IFF_DORMANT and IFF_ECHO */
++#ifndef IFF_ECHO
+ #ifndef __UAPI_DEF_IF_NET_DEVICE_FLAGS_LOWER_UP_DORMANT_ECHO
+ #define __UAPI_DEF_IF_NET_DEVICE_FLAGS_LOWER_UP_DORMANT_ECHO 1
+ #endif /* __UAPI_DEF_IF_NET_DEVICE_FLAGS_LOWER_UP_DORMANT_ECHO */
++#endif /* IFF_ECHO */
+ 
+ #else /* _NET_IF_H */
+ 
diff --git a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_4.10.bb 
b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_4.10.bb
index 108446aa34..29262789a8 100644
--- a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_4.10.bb
+++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_4.10.bb
@@ -4,6 +4,7 @@ SRC_URI_append_libc-musl = "\
 file://0001-libc-compat.h-fix-some-issues-arising-from-in6.h.patch \
 file://0002-libc-compat.h-prevent-redefinition-of-struct-ethhdr.patch \
 file://0003-remove-inclusion-of-sysinfo.h-in-kernel.h.patch \
+file://0001-libc-compat.h-musl-_does_-define-IFF_LOWER_UP-DORMAN.patch \
"
 
 SRC_URI[md5sum] = "b5e7f6b9b2fe1b6cc7bc56a3a0bfc090"
-- 
2.13.0


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


Re: [OE-core] [PATCH 1/2] armv8: update to use armv8-a tune

2017-08-03 Thread Denys Dmytriyenko
On Mon, Jul 31, 2017 at 12:31:58PM -0500, Mark Hatle wrote:
> On 7/31/17 12:16 PM, Armin Kuster wrote:
> > Signed-off-by: Armin Kuster 
> > ---
> >  meta/conf/machine/include/arm/arch-armv8.inc | 25 +
> >  1 file changed, 25 insertions(+)
> > 
> > diff --git a/meta/conf/machine/include/arm/arch-armv8.inc 
> > b/meta/conf/machine/include/arm/arch-armv8.inc
> > index 5e832fa..dc1ba5e 100644
> > --- a/meta/conf/machine/include/arm/arch-armv8.inc
> > +++ b/meta/conf/machine/include/arm/arch-armv8.inc
> > @@ -1 +1,26 @@
> > +DEFAULTTUNE ?= "armv8-a"
> 
> do we want the '-a'?  The other arm (7) are of the format armv7a (no '-').

On the other hand, gcc went with armv7-a instead of armv7a...
So, maybe having '-a' is actually more aligned with others?


> > +
> > +TUNEVALID[armv8-a] = "Enable instructions for ARMv8-a"
> > +TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'armv8-a', ' 
> > -march=armv8-a', '', d)}"
> > +
> > +TUNEVALID[crypto] = "Enable crypto instructions for ARMv8-a"
> > +TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'crypto', '+crypto', 
> > '', d)}"
> > +
> > +MACHINEOVERRIDES =. "${@bb.utils.contains('TUNE_FEATURES', 'armv8-a', 
> > 'armv8a:', '' ,d)}"
> > +
> >  require conf/machine/include/arm/arch-arm64.inc
> > +
> > +AVAILTUNES += "armv8-a armv8-a-crypto"
> > +ARMPKGARCH_tune-armv8-a ?= "armv8-a"
> > +
> > +# Enable Crypto extension. This also enables Advanced SIMD and 
> > floating-point instructions
> > +ARMPKGARCH_tune-armv8-a-crypto ?= "armv8-a"
> > +
> > +TUNE_FEATURES_tune-armv8-a = "aarch64 armv8-a"
> > +TUNE_FEATURES_tune-armv8-a-crypto = "${TUNE_FEATURES_tune-armv8-a} crypto"
> > +
> > +PACKAGE_EXTRA_ARCHS_tune-armv8-a = "aarch64 armv8-a"
> > +PACKAGE_EXTRA_ARCHS_tune-armv8-a-crypto = 
> > "${PACKAGE_EXTRA_ARCHS_tune-armv8-a} armv8-a-crypto"
> > +
> > +BASE_LIB_tune-armv8-a = "${BASE_LIB_tune-aarch64}"
> > +BASE_LIB_tune-armv8-a-crypto = "${BASE_LIB_tune-aarch64}"
> > 
> 
> -- 
> ___
> 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 1/1] expat: upgrade to 2.2.2

2017-08-03 Thread Khem Raj
On Thu, Aug 3, 2017 at 9:42 AM, Burton, Ross  wrote:
> On 24 July 2017 at 11:23, Burton, Ross  wrote:
>>
>> I've filed a bug upstream about the failure on Debian 8:
>> https://github.com/libexpat/libexpat/issues/97
>
>
> And this bug is now resolved.  expat in git can read /dev/urandom directly
> if it doesn't find the syscalls it wants.

Sounds good. Denke, when you refresh patch please include this patch along

http://git.openembedded.org/openembedded-core-contrib/tree/meta/recipes-core/expat/expat/libtool-tag.patch?h=kraj/master&id=01929853a8346ba0fc27090150ebc506d1c5cd1e

which was not there in your v1.

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


Re: [OE-core] [PATCH 1/2] armv8: update to use armv8-a tune

2017-08-03 Thread Mark Hatle
On 8/3/17 10:56 AM, akuster808 wrote:
> 
> 
> On 08/01/2017 08:46 AM, Khem Raj wrote:
>> On Tue, Aug 1, 2017 at 8:24 AM, Mark Hatle  wrote:
>>> On 8/1/17 10:20 AM, Khem Raj wrote:
 On Tue, Aug 1, 2017 at 8:17 AM, akuster808  wrote:
>
> On 07/31/2017 12:04 PM, Khem Raj wrote:
>>
>> On 7/31/17 10:51 AM, Mark Hatle wrote:
>>> On 7/31/17 12:40 PM, akuster808 wrote:

 On 07/31/2017 10:31 AM, Mark Hatle wrote:
> On 7/31/17 12:16 PM, Armin Kuster wrote:
>> Signed-off-by: Armin Kuster 
>> ---
>>meta/conf/machine/include/arm/arch-armv8.inc | 25
>> +
>>1 file changed, 25 insertions(+)
>>
>> diff --git a/meta/conf/machine/include/arm/arch-armv8.inc
>> b/meta/conf/machine/include/arm/arch-armv8.inc
>> index 5e832fa..dc1ba5e 100644
>> --- a/meta/conf/machine/include/arm/arch-armv8.inc
>> +++ b/meta/conf/machine/include/arm/arch-armv8.inc
>> @@ -1 +1,26 @@
>> +DEFAULTTUNE ?= "armv8-a"
> do we want the '-a'?  The other arm (7) are of the format armv7a (no
> '-').
 works for me either way.

 While we are at it. How would we want ‘armv8.1-a’, ‘armv8.2-a’,
 ‘armv8.3-a'
 formated as?
>>> My preference is to drop the '-'.  As for the '.', I'm not sure.. not
>>> something
>>> we've run across before.
>>>
>>> We could just drop it (the '.'), but it really depends on if armv81a
>>> would
>>> confuse someone (familiar with arm) or not.
>> I would suggest to also sync  with other distros and ensure that we dont
>> do something different. Its very costly later. Since applications get
>> ported to most common combination
> Sync what part? naming of file? ( sorry lost regarding your comment)
 naming convention for arch e.g.

>>> I'd say Debian/Ubuntu -- Fedora/RH would be the two primary sources I'd 
>>> look at.
>>>   Between debian package names and RPM package names, it should give a clue 
>>> if
>>> there is any community standard forming for those names.
>>>
>>> (May still be too premature for those environments for the armv8.X-a 
>>> naming...
>>> and I've not seen it discussed on any other lists either.)
>> yeah, it will be good to not go through the pain of community doing
>> something else later
>> like *-*-gnueabihf triplet was invented and to date we keep fixing
>> packages for OE
>> to account for gnueabihf can be gnueabi + -mfloat-abi=hard but
>> packages just assume
> 
> I think I now understand the issue. Any interest in having additional 
> tune files warehoused somewhere so folks don't have to reinvent the 
> wheel? Something like "meta-extra-tunes" ?
> 
> I prefer fostering contributions for additional tune files that get 
> vetted by the community rather than the multitude of unseen 
> implementations I have found sitting around.

I wouldn't be against it.  The original thought was that new tunes (and related
configurations) would be housed in the BSP until submitted to the YP.  But I'm
not sure in hindsight that is very robust..

Having a general meta-* layer that can just collect arch settings would be
useful to help coordinate people, but keep out in-progress stuff from the base.
The only issue is someone will have to further coordinate acceptance into the
extra layer, and help push them into the oe-core proper when the tune quality is
at a correct level --or-- the tune becomes prevalent in the world.

(I just don't want it to become a dumping ground and it never ends up in the
core...  Similarly moving older tunes out of the core might some day be useful
as well.)

Key of course is this should include tunes, as well as things like
siteinfo.bbclass and insane.bbclass or other extensions.  (via:
PACKAGEQA_EXTRA_MACHDEFFUNCS and similar.)

While the toolchains, arch recipe patches, etc should be elsewhere...

--Mark

> regards,
> armin
> 
>>
>>
>>> --Mark
> 

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


Re: [OE-core] [PATCH 1/1] expat: upgrade to 2.2.2

2017-08-03 Thread Burton, Ross
On 24 July 2017 at 11:23, Burton, Ross  wrote:

> I've filed a bug upstream about the failure on Debian 8:
> https://github.com/libexpat/libexpat/issues/97
>

And this bug is now resolved.  expat in git can read /dev/urandom directly
if it doesn't find the syscalls it wants.

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


Re: [OE-core] [PATCH v4] kernel: Add support for multiple kernel packages

2017-08-03 Thread Ovidiu-Adrian Vancea
On Thu, 2017-07-27 at 11:01 -0700, Rees, Kevron wrote:
> On Wed, Jul 19, 2017 at 8:56 AM, Wold, Saul 
> wrote:
> > On Tue, 2017-07-18 at 08:34 -0500, Haris Okanovic wrote:
> > > 
> > > On 07/17/2017 03:31 PM, Wold, Saul wrote:
> > > > 
> > > > On Wed, 2017-07-05 at 12:33 -0500, Haris Okanovic wrote:
> > > > > 
> > > > > Some distros may want to provide alternate kernel "flavors"
> > > > > via
> > > > > feeds
> > > > > or
> > > > > within bootable images. For example, readily available builds
> > > > > which
> > > > > provide certain diagnostic features can enable developers and
> > > > > testers
> > > > > to
> > > > > more quickly resolve issues by avoiding lengthy kernel
> > > > > builds.
> > > > > 
> > > > > This change allows for building multiple flavors of the
> > > > > kernel
> > > > > and
> > > > > module packages by templatizing kernel package names via a
> > > > > new
> > > > > KERNEL_PACKAGE_NAME variable in kernel.bbclass. It defaults
> > > > > to
> > > > > the
> > > > > old
> > > > > name of "kernel", but can be overridden by certain recipes
> > > > > providing
> > > > > alternate kernel flavors.
> > > > > 
> > > > > To maintain compatibility, recipes providing alternate kernel
> > > > > flavors
> > > > > cannot be the "preferred provider" for virtual/kernel. This
> > > > > is
> > > > > because
> > > > > OE puts the preferred provider's build and source at
> > > > > "tmp-glibc/work-shared/$MACHINE/kernel-build-artifacts/" and
> > > > > "tmp-glibc/work-shared/$MACHINE/kernel-source/" instead of
> > > > > "tmp-glibc/work/*/$PN/" like other recipes. Therefore,
> > > > > recipes
> > > > > using
> > > > > the
> > > > > default KERNEL_PACKAGE_NAME="kernel" follows the old
> > > > > semantics --
> > > > > build
> > > > > in the old location and may be preferred provider -- while
> > > > > recipes
> > > > > using
> > > > > all other KERNEL_PACKAGE_NAME's build from the normal WORKDIR
> > > > > and
> > > > > don't
> > > > > provide "virtual/kernel".
> > > > > 
> > > > > Testing:
> > > > >   1. Prepended `KERNEL_PACKAGE_NAME = "tiny-linux"` to
> > > > >  linux-yocto-tiny_4.9.bb so that it may build alongside
> > > > >  the main kernel.
> > > > >   2. `bitbake linux-yocto linux-yocto-tiny` to build both
> > > > > kernel
> > > > > flavors.
> > > > >   3. Verified image and modules IPKs exist for both:
> > > > >  tmp-glibc/deploy/ipk/qemux86/kernel-* for linux-yocto
> > > > >  tmp-glibc/deploy/ipk/qemux86/tiny-linux* for linux-
> > > > > yocto-
> > > > > tiny
> > > > >   4. Verified linux-yocto is the "preferred provider", and
> > > > > was
> > > > > built
> > > > > in
> > > > >  shared directory: tmp-glibc/work-shared/qemux86/kernel-*
> > > > >   5. Appended `CORE_IMAGE_BASE_INSTALL += "tiny-linux"` to
> > > > >  core-image-base.bb to include both kernel flavors.
> > > > >   6. `bitbake core-image-base` to build an image.
> > > > >   7. Verified image contains two bzImage's under /boot/, with
> > > > >  "yocto-standard" selected to boot via symlink.
> > > > > 
> > > > > Discussion thread:
> > > > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.ope
> > > > > nembedded.org_pipermail_openembedded-2Dcore_2015-
> > > > > 2DDe&d=DwICAg&c=I_0YwoKy7z5LMTVdyO6YCiE2uzI1jjZZuIPelcSjixA&r
> > > > > =35FLeGKBmrBGMHAhCV37-B4ddgcjLZXUChuxj5DD6Sk&m=-J-
> > > > > ERX3BXdjXgeeIE_ZNE7GozSVtUpP3Wt6FV_jtLtM&s=z_ITagkjX7-
> > > > > q9KHaytBdqTZeJYksmYYjciSiELDYIGE&e= 
> > > > > cemb
> > > > > er/thread.html#114122
> > > > > 
> > > > > Signed-off-by: Ioan-Adrian Ratiu 
> > > > > Signed-off-by: Gratian Crisan 
> > > > > Signed-off-by: Haris Okanovic 
> > > > > Coauthored-by: Gratian Crisan 
> > > > > Coauthored-by: Haris Okanovic 
> > > > > Coauthored-by: Josh Hernstrom 
> > > > > ---
> > > > > [PATCH v2] Change STAGING_KERNEL_DIR and
> > > > > STAGING_KERNEL_BUILDDIR
> > > > > to
> > > > > the
> > > > > "work" directory in alternate kernel builds, instead of
> > > > > "work-
> > > > > shared",
> > > > > so
> > > > > that the two builds don't clobber each other.
> > > > > 
> > > > > [PATCH v3] An updated version of this change rebased onto the
> > > > > current
> > > > > OE-core master. Changes:
> > > > >   * Remove PREFERRED_PROVIDER check in linux-yocto.inc in
> > > > > alternate
> > > > > kernel builds, since alternate kernels aren't the
> > > > > PREFERRED_PROVIDER for virtual/kernel by definition.
> > > > >   * Remove "virtual/kernel" from PROVIDES in alternate kernel
> > > > > builds.
> > > > > 
> > > > > [PATCH v4] Another rebase onto master; no functional change.
> > > > > Improved description and testing steps.
> > > > 
> > > > So I finally had a chance to get back to this and test build
> > > > with
> > > > it, I
> > > > saw the following WARNING, which lead to the ERROR:
> > > > 
> > > > WARNING: Variable key FILES_${PN}-dev (${includedir}
> > > > ${FILES_SOLIBSDEV}
> > > > ${libdir}/*.la ${libdir}/*.o ${libdir}/pkgconfig
> > > > ${datadir}/pkgconfig
> > > > ${datadir}/ac

Re: [OE-core] [PATCH 1/2] armv8: update to use armv8-a tune

2017-08-03 Thread akuster808



On 08/01/2017 08:46 AM, Khem Raj wrote:

On Tue, Aug 1, 2017 at 8:24 AM, Mark Hatle  wrote:

On 8/1/17 10:20 AM, Khem Raj wrote:

On Tue, Aug 1, 2017 at 8:17 AM, akuster808  wrote:


On 07/31/2017 12:04 PM, Khem Raj wrote:


On 7/31/17 10:51 AM, Mark Hatle wrote:

On 7/31/17 12:40 PM, akuster808 wrote:


On 07/31/2017 10:31 AM, Mark Hatle wrote:

On 7/31/17 12:16 PM, Armin Kuster wrote:

Signed-off-by: Armin Kuster 
---
   meta/conf/machine/include/arm/arch-armv8.inc | 25
+
   1 file changed, 25 insertions(+)

diff --git a/meta/conf/machine/include/arm/arch-armv8.inc
b/meta/conf/machine/include/arm/arch-armv8.inc
index 5e832fa..dc1ba5e 100644
--- a/meta/conf/machine/include/arm/arch-armv8.inc
+++ b/meta/conf/machine/include/arm/arch-armv8.inc
@@ -1 +1,26 @@
+DEFAULTTUNE ?= "armv8-a"

do we want the '-a'?  The other arm (7) are of the format armv7a (no
'-').

works for me either way.

While we are at it. How would we want ‘armv8.1-a’, ‘armv8.2-a’,
‘armv8.3-a'
formated as?

My preference is to drop the '-'.  As for the '.', I'm not sure.. not
something
we've run across before.

We could just drop it (the '.'), but it really depends on if armv81a
would
confuse someone (familiar with arm) or not.

I would suggest to also sync  with other distros and ensure that we dont
do something different. Its very costly later. Since applications get
ported to most common combination

Sync what part? naming of file? ( sorry lost regarding your comment)

naming convention for arch e.g.


I'd say Debian/Ubuntu -- Fedora/RH would be the two primary sources I'd look at.
  Between debian package names and RPM package names, it should give a clue if
there is any community standard forming for those names.

(May still be too premature for those environments for the armv8.X-a naming...
and I've not seen it discussed on any other lists either.)

yeah, it will be good to not go through the pain of community doing
something else later
like *-*-gnueabihf triplet was invented and to date we keep fixing
packages for OE
to account for gnueabihf can be gnueabi + -mfloat-abi=hard but
packages just assume


I think I now understand the issue. Any interest in having additional 
tune files warehoused somewhere so folks don't have to reinvent the 
wheel? Something like "meta-extra-tunes" ?


I prefer fostering contributions for additional tune files that get 
vetted by the community rather than the multitude of unseen 
implementations I have found sitting around.


regards,
armin





--Mark


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


Re: [OE-core] [PATCH] glibc: Update to latest on 2.26 pre-release

2017-08-03 Thread Khem Raj
On Thu, Aug 3, 2017 at 4:04 AM, Burton, Ross  wrote:
> On 2 August 2017 at 23:03, Burton, Ross  wrote:
>>
>> Build almost anything because it will need glibc-locale.  Sorry.
>>
>> I can throw it on the AB to see what fails/works.
>
>
> The autobuilder, for once, is on my side.
>
> https://autobuilder.yocto.io/tgrid, the ross/glibc row at 4cb48130d80a.
>

I have sent an update to move to final 2.26 release. Please try that one

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


[OE-core] [PATCH 2/2] glibc: Upgrade to 2.26 final release

2017-08-03 Thread Khem Raj
Signed-off-by: Khem Raj 
---
 meta/conf/distro/include/tcmode-default.inc|  2 +-
 ...e_2.25.90.bb => cross-localedef-native_2.26.bb} |  5 +-
 ...bc-initial_2.25.90.bb => glibc-initial_2.26.bb} |  0
 ...libc-locale_2.25.90.bb => glibc-locale_2.26.bb} |  0
 ...libc-mtrace_2.25.90.bb => glibc-mtrace_2.26.bb} |  0
 ...bc-scripts_2.25.90.bb => glibc-scripts_2.26.bb} |  0
 ...ress-pedantic-warning-caused-by-statement.patch | 90 ++
 .../glibc/{glibc_2.25.90.bb => glibc_2.26.bb}  |  6 +-
 8 files changed, 96 insertions(+), 7 deletions(-)
 rename meta/recipes-core/glibc/{cross-localedef-native_2.25.90.bb => 
cross-localedef-native_2.26.bb} (94%)
 rename meta/recipes-core/glibc/{glibc-initial_2.25.90.bb => 
glibc-initial_2.26.bb} (100%)
 rename meta/recipes-core/glibc/{glibc-locale_2.25.90.bb => 
glibc-locale_2.26.bb} (100%)
 rename meta/recipes-core/glibc/{glibc-mtrace_2.25.90.bb => 
glibc-mtrace_2.26.bb} (100%)
 rename meta/recipes-core/glibc/{glibc-scripts_2.25.90.bb => 
glibc-scripts_2.26.bb} (100%)
 create mode 100644 
meta/recipes-core/glibc/glibc/0026-assert-Suppress-pedantic-warning-caused-by-statement.patch
 rename meta/recipes-core/glibc/{glibc_2.25.90.bb => glibc_2.26.bb} (96%)

diff --git a/meta/conf/distro/include/tcmode-default.inc 
b/meta/conf/distro/include/tcmode-default.inc
index 8ffb8ad046..2754136405 100644
--- a/meta/conf/distro/include/tcmode-default.inc
+++ b/meta/conf/distro/include/tcmode-default.inc
@@ -26,7 +26,7 @@ GCCVERSION ?= "7.%"
 SDKGCCVERSION ?= "${GCCVERSION}"
 BINUVERSION ?= "2.28%"
 GDBVERSION ?= "8.0%"
-GLIBCVERSION ?= "2.25%"
+GLIBCVERSION ?= "2.26%"
 LINUXLIBCVERSION ?= "4.10%"
 
 PREFERRED_VERSION_gcc ?= "${GCCVERSION}"
diff --git a/meta/recipes-core/glibc/cross-localedef-native_2.25.90.bb 
b/meta/recipes-core/glibc/cross-localedef-native_2.26.bb
similarity index 94%
rename from meta/recipes-core/glibc/cross-localedef-native_2.25.90.bb
rename to meta/recipes-core/glibc/cross-localedef-native_2.26.bb
index 5dd0c70400..fc5d70dbb9 100644
--- a/meta/recipes-core/glibc/cross-localedef-native_2.25.90.bb
+++ b/meta/recipes-core/glibc/cross-localedef-native_2.26.bb
@@ -17,12 +17,11 @@ inherit autotools
 
 FILESEXTRAPATHS =. "${FILE_DIRNAME}/${PN}:${FILE_DIRNAME}/glibc:"
 
-#SRCBRANCH ?= "release/${PV}/master"
-SRCBRANCH ?= "master"
+SRCBRANCH ?= "release/${PV}/master"
 GLIBC_GIT_URI ?= "git://sourceware.org/git/glibc.git"
 UPSTREAM_CHECK_GITTAGREGEX = "(?P\d+\.\d+(\.\d+)*)"
 
-SRCREV_glibc ?= "43a9f537fc121a867981ca31ea9d79f33ce0fd24"
+SRCREV_glibc ?= "1c9a5c270d8b66f30dcfaf1cb2d6cf39d3e18369"
 SRCREV_localedef ?= "dfb4afe551c6c6e94f9cc85417bd1f582168c843"
 
 SRC_URI = "${GLIBC_GIT_URI};branch=${SRCBRANCH};name=glibc \
diff --git a/meta/recipes-core/glibc/glibc-initial_2.25.90.bb 
b/meta/recipes-core/glibc/glibc-initial_2.26.bb
similarity index 100%
rename from meta/recipes-core/glibc/glibc-initial_2.25.90.bb
rename to meta/recipes-core/glibc/glibc-initial_2.26.bb
diff --git a/meta/recipes-core/glibc/glibc-locale_2.25.90.bb 
b/meta/recipes-core/glibc/glibc-locale_2.26.bb
similarity index 100%
rename from meta/recipes-core/glibc/glibc-locale_2.25.90.bb
rename to meta/recipes-core/glibc/glibc-locale_2.26.bb
diff --git a/meta/recipes-core/glibc/glibc-mtrace_2.25.90.bb 
b/meta/recipes-core/glibc/glibc-mtrace_2.26.bb
similarity index 100%
rename from meta/recipes-core/glibc/glibc-mtrace_2.25.90.bb
rename to meta/recipes-core/glibc/glibc-mtrace_2.26.bb
diff --git a/meta/recipes-core/glibc/glibc-scripts_2.25.90.bb 
b/meta/recipes-core/glibc/glibc-scripts_2.26.bb
similarity index 100%
rename from meta/recipes-core/glibc/glibc-scripts_2.25.90.bb
rename to meta/recipes-core/glibc/glibc-scripts_2.26.bb
diff --git 
a/meta/recipes-core/glibc/glibc/0026-assert-Suppress-pedantic-warning-caused-by-statement.patch
 
b/meta/recipes-core/glibc/glibc/0026-assert-Suppress-pedantic-warning-caused-by-statement.patch
new file mode 100644
index 00..b2bb96b818
--- /dev/null
+++ 
b/meta/recipes-core/glibc/glibc/0026-assert-Suppress-pedantic-warning-caused-by-statement.patch
@@ -0,0 +1,90 @@
+From 037283cbc74739b72f36dfec827d120faa243406 Mon Sep 17 00:00:00 2001
+From: Florian Weimer 
+Date: Thu, 6 Jul 2017 11:50:55 +0200
+Subject: [PATCH 26/26] assert: Suppress pedantic warning caused by statement
+ expression [BZ# 21242]
+
+On 07/05/2017 10:15 PM, Zack Weinberg wrote:
+> On Wed, Jul 5, 2017 at 11:51 AM, Florian Weimer  wrote:
+>> On 07/05/2017 05:46 PM, Zack Weinberg wrote:
+>>> A problem occurs to me: expressions involving VLAs _are_ evaluated
+>>> inside sizeof.
+>>
+>> The type of the sizeof argument would still be int (due to the
+>> comparison against 0), so this doesn't actually occur.
+>
+> I rechecked what C99 says about sizeof and VLAs, and you're right -
+> the operand of sizeof is only evaluated when sizeof is _directly_
+> applied to a VLA.  So this is indeed safe, but I think this wrinkle
+> should be mentioned in the comment.  Perhaps
+>
+> /* The first o

[OE-core] [PATCH 1/2] llvm: Keep llvm-native dependency with clang toolchain

2017-08-03 Thread Khem Raj
This was needed when we were conflicting with clang-native
but this is solved via append PN to binaries of llvm-native

Signed-off-by: Khem Raj 
---
 meta/recipes-devtools/llvm/llvm_git.bb | 2 --
 1 file changed, 2 deletions(-)

diff --git a/meta/recipes-devtools/llvm/llvm_git.bb 
b/meta/recipes-devtools/llvm/llvm_git.bb
index 722bc53aa1..15152dc1ff 100644
--- a/meta/recipes-devtools/llvm/llvm_git.bb
+++ b/meta/recipes-devtools/llvm/llvm_git.bb
@@ -10,8 +10,6 @@ LIC_FILES_CHKSUM = 
"file://LICENSE.TXT;md5=e825e017edc35cfd58e26116e5251771"
 
 DEPENDS = "libffi libxml2-native zlib ninja-native llvm-native"
 
-DEPENDS_remove_toolchain-clang = "llvm-native"
-
 RDEPENDS_${PN}_append_class-target = " ncurses-terminfo"
 
 inherit perlnative pythonnative cmake pkgconfig
-- 
2.13.3

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


[OE-core] [PATCH] context: Include a command line argument to run all except certain tests

2017-08-03 Thread leonardo . sandoval . gonzalez
From: Leonardo Sandoval 

A new command line argument (-R, which is the oposite of current -r) that allows
to run all test cases except the ones indicated through the command line.

Some command line examples:

* Run all except the distro test case:
$ oe-selftest -R distrodata

* Run all except the archiver test case and a single bblayers unit test
$ oe-selftest -R archiver bblayers.BitbakeLayers.test_bitbakelayers_add_remove

[YOCTO #11847]

Signed-off-by: Leonardo Sandoval 
---
 meta/lib/oeqa/core/context.py | 20 +---
 meta/lib/oeqa/selftest/context.py | 11 ---
 2 files changed, 25 insertions(+), 6 deletions(-)

diff --git a/meta/lib/oeqa/core/context.py b/meta/lib/oeqa/core/context.py
index 422e289992..acd547416f 100644
--- a/meta/lib/oeqa/core/context.py
+++ b/meta/lib/oeqa/core/context.py
@@ -41,6 +41,14 @@ class OETestContext(object):
 
 return modules
 
+def skipTests(self, skips):
+if not skips:
+return
+for test in self.suites:
+for skip in skips:
+if test.id().startswith(skip):
+setattr(test, 'setUp', lambda: test.skipTest('Skip by the 
command line argument "%s"' % skip))
+
 def loadTests(self, module_paths, modules=[], tests=[],
 modules_manifest="", modules_required=[], filters={}):
 if modules_manifest:
@@ -50,9 +58,12 @@ class OETestContext(object):
 modules_required, filters)
 self.suites = self.loader.discover()
 
-def runTests(self):
+def runTests(self, skips=[]):
 self.runner = self.runnerClass(self, descriptions=False, verbosity=2)
 
+# Dinamically skip those tests specified though arguments
+self.skipTests(skips)
+
 self._run_start_time = time.time()
 result = self.runner.run(self.suites)
 self._run_end_time = time.time()
@@ -128,7 +139,8 @@ class OETestContextExecutor(object):
 self.tc_kwargs = {}
 self.tc_kwargs['init'] = {}
 self.tc_kwargs['load'] = {}
-self.tc_kwargs['run'] = {}
+self.tc_kwargs['list'] = {}
+self.tc_kwargs['run']  = {}
 
 self.tc_kwargs['init']['logger'] = self._setup_logger(logger, args)
 if args.test_data_file:
@@ -143,6 +155,8 @@ class OETestContextExecutor(object):
 else:
 self.tc_kwargs['load']['modules'] = []
 
+self.tc_kwargs['run']['skips'] = []
+
 self.module_paths = args.CASES_PATHS
 
 def _pre_run(self):
@@ -159,7 +173,7 @@ class OETestContextExecutor(object):
 sys.exit(1)
 
 if args.list_tests:
-rc = self.tc.listTests(args.list_tests, **self.tc_kwargs['run'])
+rc = self.tc.listTests(args.list_tests, **self.tc_kwargs['list'])
 else:
 self._pre_run()
 rc = self.tc.runTests(**self.tc_kwargs['run'])
diff --git a/meta/lib/oeqa/selftest/context.py 
b/meta/lib/oeqa/selftest/context.py
index 990c761f29..9e90d3c256 100644
--- a/meta/lib/oeqa/selftest/context.py
+++ b/meta/lib/oeqa/selftest/context.py
@@ -25,14 +25,14 @@ class OESelftestTestContext(OETestContext):
 self.custommachine = None
 self.config_paths = config_paths
 
-def runTests(self, machine=None):
+def runTests(self, machine=None, skips=[]):
 if machine:
 self.custommachine = machine
 if machine == 'random':
 self.custommachine = choice(self.machines)
 self.logger.info('Run tests with custom MACHINE set to: %s' % \
 self.custommachine)
-return super(OESelftestTestContext, self).runTests()
+return super(OESelftestTestContext, self).runTests(skips)
 
 def listTests(self, display_type, machine=None):
 return super(OESelftestTestContext, self).listTests(display_type)
@@ -51,6 +51,9 @@ class OESelftestTestContextExecutor(OETestContextExecutor):
 group.add_argument('-a', '--run-all-tests', default=False,
 action="store_true", dest="run_all_tests",
 help='Run all (unhidden) tests')
+group.add_argument('-R', '--skip-tests', required=False, 
action='store',
+nargs='+', dest="skips", default=None,
+help='Run all (unhidden) tests except the ones specified. 
Format should be [.[.]]')
 group.add_argument('-r', '--run-tests', required=False, action='store',
 nargs='+', dest="run_tests", default=None,
 help='Select what tests to run (modules, classes or test 
methods). Format should be: ..')
@@ -133,6 +136,8 @@ class OESelftestTestContextExecutor(OETestContextExecutor):
 copyfile(self.tc_kwargs['init']['config_paths']['bblayers'], 
 self.tc_kwargs['init']['config_paths']['bblayers_backup'])
 
+self.tc_kwargs['run']['skips'] = args.skips
+
 def _pre_run(self):
 def _check_required_env_variables(vars):
 for var in vars:
@@

Re: [OE-core] [PATCH] glibc: Update to latest on 2.26 pre-release

2017-08-03 Thread Burton, Ross
On 2 August 2017 at 23:03, Burton, Ross  wrote:

> Build almost anything because it will need glibc-locale.  Sorry.
>
> I can throw it on the AB to see what fails/works.
>

The autobuilder, for once, is on my side.

https://autobuilder.yocto.io/tgrid, the ross/glibc row at 4cb48130d80a.

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


[OE-core] [PATCH] valgrind: enable on mips soft-float

2017-08-03 Thread André Draszik
From: André Draszik 

Valgrind support for mips soft-float hosts has been fixed
in the 3.12 [1] and 3.13 [2] releases, so let's start
building it on those, too.

[1] 
https://sourceware.org/git/?p=valgrind.git;a=commit;h=8f0070d31daea6f0ed18f8fe69498a67530bfcbb
[2] 
https://sourceware.org/git/?p=valgrind.git;a=commit;h=3172936d63da4b6257099bc05aee5793978269cb

Signed-off-by: André Draszik 
---
 meta/recipes-devtools/valgrind/valgrind_3.13.0.bb | 2 --
 1 file changed, 2 deletions(-)

diff --git a/meta/recipes-devtools/valgrind/valgrind_3.13.0.bb 
b/meta/recipes-devtools/valgrind/valgrind_3.13.0.bb
index e1ff29a312..a5c49431a5 100644
--- a/meta/recipes-devtools/valgrind/valgrind_3.13.0.bb
+++ b/meta/recipes-devtools/valgrind/valgrind_3.13.0.bb
@@ -53,9 +53,7 @@ COMPATIBLE_HOST_armv6 = 'null'
 COMPATIBLE_HOST_linux-gnux32 = 'null'
 
 # Disable for some MIPS variants
-COMPATIBLE_HOST_mipsarcho32 = "${@bb.utils.contains("TARGET_FPU", "soft", 
"null", ".*-linux", d)}"
 COMPATIBLE_HOST_mipsarchn32 = 'null'
-COMPATIBLE_HOST_mipsarchn64 = "${@bb.utils.contains("TARGET_FPU", "soft", 
"null", ".*-linux", d)}"
 COMPATIBLE_HOST_mipsarchr6 = 'null'
 
 inherit autotools ptest
-- 
2.13.2

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