[OE-core] [PATCH] curl:upgrade 7.64.1 -> 7.65.1

2019-06-18 Thread Zang Ruochen
-Upgrade from curl_7.64.1.bb to curl_7.65.1.bb.

Signed-off-by: Zang Ruochen 
---
 meta/recipes-support/curl/{curl_7.64.1.bb => curl_7.65.1.bb} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-support/curl/{curl_7.64.1.bb => curl_7.65.1.bb} (95%)

diff --git a/meta/recipes-support/curl/curl_7.64.1.bb 
b/meta/recipes-support/curl/curl_7.65.1.bb
similarity index 95%
rename from meta/recipes-support/curl/curl_7.64.1.bb
rename to meta/recipes-support/curl/curl_7.65.1.bb
index 47c28beff6..e7bfe6cc0b 100644
--- a/meta/recipes-support/curl/curl_7.64.1.bb
+++ b/meta/recipes-support/curl/curl_7.65.1.bb
@@ -9,8 +9,8 @@ SRC_URI = "http://curl.haxx.se/download/curl-${PV}.tar.bz2 \
file://0001-replace-krb5-config-with-pkg-config.patch \
 "
 
-SRC_URI[md5sum] = "790c101927845208a9d7e8c429ddd1b2"
-SRC_URI[sha256sum] = 
"4cc7c738b35250d0680f29e93e0820c4cb40035f43514ea3ec8d60322d41a45d"
+SRC_URI[md5sum] = "03ca3fa53ac4d791be66e30ba75b56ea"
+SRC_URI[sha256sum] = 
"cbd36df60c49e461011b4f3064cff1184bdc9969a55e9608bf5cadec4686e3f7"
 
 CVE_PRODUCT = "curl libcurl"
 inherit autotools pkgconfig binconfig multilib_header
-- 
2.20.1



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


[OE-core] [PATCH] gnupg:upgrade 2.2.15 -> 2.2.16

2019-06-18 Thread Zang Ruochen
-Upgrade from gnupg_2.2.15.bb to gnupg_2.2.16.bb.

Signed-off-by: Zang Ruochen 
---
 .../gnupg/{gnupg_2.2.15.bb => gnupg_2.2.16.bb}| 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-support/gnupg/{gnupg_2.2.15.bb => gnupg_2.2.16.bb} (93%)

diff --git a/meta/recipes-support/gnupg/gnupg_2.2.15.bb 
b/meta/recipes-support/gnupg/gnupg_2.2.16.bb
similarity index 93%
rename from meta/recipes-support/gnupg/gnupg_2.2.15.bb
rename to meta/recipes-support/gnupg/gnupg_2.2.16.bb
index 06a257333d..cb7c6c5c62 100644
--- a/meta/recipes-support/gnupg/gnupg_2.2.15.bb
+++ b/meta/recipes-support/gnupg/gnupg_2.2.16.bb
@@ -20,8 +20,8 @@ SRC_URI_append_class-native = " 
file://0001-configure.ac-use-a-custom-value-for-
 file://relocate.patch"
 
 
-SRC_URI[md5sum] = "3ab87e377aa0af2f463649515bf66508"
-SRC_URI[sha256sum] = 
"cb8ce298d7b36558ffc48aec961b14c830ff1783eef7a623411188b5e0f5d454"
+SRC_URI[md5sum] = "d90e186df1c06845880ea58a318f070b"
+SRC_URI[sha256sum] = 
"6cbe8d454bf5dc204621eed3016d721b66298fa95363395bb8eeceb1d2fd14cb"
 
 EXTRA_OECONF = "--disable-ldap \
--disable-ccid-driver \
-- 
2.20.1



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


[OE-core] [PATCH] gnutls:upgrade 3.6.7 -> 3.6.8

2019-06-18 Thread Zang Ruochen
-Upgrade from gnutls_3.6.7.bb to gnutls_3.6.8.bb.

Signed-off-by: Zang Ruochen 
---
 .../gnutls/{gnutls_3.6.7.bb => gnutls_3.6.8.bb}   | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-support/gnutls/{gnutls_3.6.7.bb => gnutls_3.6.8.bb} (93%)

diff --git a/meta/recipes-support/gnutls/gnutls_3.6.7.bb 
b/meta/recipes-support/gnutls/gnutls_3.6.8.bb
similarity index 93%
rename from meta/recipes-support/gnutls/gnutls_3.6.7.bb
rename to meta/recipes-support/gnutls/gnutls_3.6.8.bb
index b27526a64e..6c6c520e8c 100644
--- a/meta/recipes-support/gnutls/gnutls_3.6.7.bb
+++ b/meta/recipes-support/gnutls/gnutls_3.6.8.bb
@@ -21,8 +21,8 @@ SRC_URI = 
"https://www.gnupg.org/ftp/gcrypt/gnutls/v${SHRT_VER}/gnutls-${PV}.tar
file://arm_eabi.patch \
 "
 
-SRC_URI[md5sum] = "c4ac669c500df939d4fbfea722367929"
-SRC_URI[sha256sum] = 
"5b3409ad5aaf239808730d1ee12fdcd148c0be00262c7edf157af655a8a188e2"
+SRC_URI[md5sum] = "9dcf0aa45d1a42e1b3ca5d39ec7c61a8"
+SRC_URI[sha256sum] = 
"aa81944e5635de981171772857e72be231a7e0f559ae0292d2737de475383e83"
 
 inherit autotools texinfo pkgconfig gettext lib_package gtk-doc
 
-- 
2.20.1



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


[OE-core] [PATCH 1/1] target-sdk-provides-dummy: add libperl.so.5 to DUMMY_PROVIDES

2019-06-18 Thread Chen Qi
Add libperl.so.5 to DUMMY_PROVIDES to avoid do_rootfs failure like
below.

Error:
Problem: package postgresql-11.3-r0.core2_32 requires libperl.so.5, but none of 
the providers can be installed

package target-sdk-provides-dummy-1.0-r0.sdk_provides_dummy_target 
conflicts with perl provided by perl-5.30.0-r0.core2_32
package target-sdk-provides-dummy-1.0-r0.sdk_provides_dummy_target 
conflicts with perl-module-strict provided by perl-5.30.0-r0.core2_32

This problem could be reproduced by add 'postgresql' to IMAGE_INSTALL
and then `bitbake core-image-minimal -c populate_sdk'.

Signed-off-by: Chen Qi 
---
 meta/recipes-core/meta/target-sdk-provides-dummy.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-core/meta/target-sdk-provides-dummy.bb 
b/meta/recipes-core/meta/target-sdk-provides-dummy.bb
index 50182de..b5e8c0f 100644
--- a/meta/recipes-core/meta/target-sdk-provides-dummy.bb
+++ b/meta/recipes-core/meta/target-sdk-provides-dummy.bb
@@ -46,6 +46,7 @@ DUMMYPROVIDES = "\
 /bin/bash \
 /usr/bin/env \
 /usr/bin/perl \
+libperl.so.5 \
 pkgconfig \
 pkgconfig-dev \
 pkgconfig-src \
-- 
1.9.1

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


[OE-core] [PATCH 0/1] target-sdk-provides-dummy: add libperl.so.5 to DUMMY_PROVIDES

2019-06-18 Thread Chen Qi
*** BLURB HERE ***
The following changes since commit 111b7173fee69fe8b01ec2fa6999713841326537:

  dev-manual: Fixed grammar issue. (2019-06-18 11:29:23 +0100)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib ChenQi/target-sdk-perl
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=ChenQi/target-sdk-perl

Chen Qi (1):
  target-sdk-provides-dummy: add libperl.so.5 to DUMMY_PROVIDES

 meta/recipes-core/meta/target-sdk-provides-dummy.bb | 1 +
 1 file changed, 1 insertion(+)

-- 
1.9.1

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


[OE-core] [PATCH] libevdev:upgrade 1.6.0 -> 1.7.0

2019-06-18 Thread Zang Ruochen
-Upgrade from libevdev_1.6.0.bb to libevdev_1.7.0.bb.

Signed-off-by: Zang Ruochen 
---
 .../libevdev/{libevdev_1.6.0.bb => libevdev_1.7.0.bb} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-support/libevdev/{libevdev_1.6.0.bb => libevdev_1.7.0.bb} 
(74%)

diff --git a/meta/recipes-support/libevdev/libevdev_1.6.0.bb 
b/meta/recipes-support/libevdev/libevdev_1.7.0.bb
similarity index 74%
rename from meta/recipes-support/libevdev/libevdev_1.6.0.bb
rename to meta/recipes-support/libevdev/libevdev_1.7.0.bb
index 12cf5192fc..abd6f386b8 100644
--- a/meta/recipes-support/libevdev/libevdev_1.6.0.bb
+++ b/meta/recipes-support/libevdev/libevdev_1.7.0.bb
@@ -8,7 +8,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=75aae0d38feea6fda97ca381cb9132eb \
 
 SRC_URI = "http://www.freedesktop.org/software/libevdev/${BP}.tar.xz";
 
-SRC_URI[md5sum] = "154b24f01425c4c82fdc3e11f2c13af6"
-SRC_URI[sha256sum] = 
"f5005c865987d980cc1279b9ec6131b06a89fd9892f649f2a68262b8786ef814"
+SRC_URI[md5sum] = "fabe87d8d7d7f7cdb4a26e5dc99fc517"
+SRC_URI[sha256sum] = 
"11dbe1f2b1d03a51f3e9a196757a75c3a999042ce34cf1fdc00a2363e5a2e369"
 
 inherit autotools pkgconfig
-- 
2.20.1



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


[OE-core] [PATCH] libevent:upgrade 2.1.8 -> 2.1.10

2019-06-18 Thread Zang Ruochen
-Upgrade from libevent_2.1.8.bb to libevent_2.1.10.bb.

-libevent/0001-test-fix-32bit-linux-regress.patch
Removed since this is included in 2.1.10.

Signed-off-by: Zang Ruochen 
---
 .../0001-test-fix-32bit-linux-regress.patch   | 48 ---
 .../{libevent_2.1.8.bb => libevent_2.1.10.bb} |  5 +-
 2 files changed, 2 insertions(+), 51 deletions(-)
 delete mode 100644 
meta/recipes-support/libevent/libevent/0001-test-fix-32bit-linux-regress.patch
 rename meta/recipes-support/libevent/{libevent_2.1.8.bb => libevent_2.1.10.bb} 
(84%)

diff --git 
a/meta/recipes-support/libevent/libevent/0001-test-fix-32bit-linux-regress.patch
 
b/meta/recipes-support/libevent/libevent/0001-test-fix-32bit-linux-regress.patch
deleted file mode 100644
index 36d08204f7..00
--- 
a/meta/recipes-support/libevent/libevent/0001-test-fix-32bit-linux-regress.patch
+++ /dev/null
@@ -1,48 +0,0 @@
-From 69a3813c513c84e02212250c3d5b8a02ecefa698 Mon Sep 17 00:00:00 2001
-From: Mingli Yu 
-Date: Mon, 15 Jan 2018 08:00:33 +
-Subject: [PATCH] test: fix 32bit linux regress
-
-This patch comes from https://github.com/libevent/libevent.git,
-the commit is 63c4bf78d6af3c6ff46d2e8e4b53dd9f577a9ca9
-
-Upstream-Status: Backport
-
-Signed-off-by: Mingli Yu 

- configure.ac| 1 +
- test/regress_util.c | 2 ++
- 2 files changed, 3 insertions(+)
-
-diff --git a/configure.ac b/configure.ac
-index 7528d37..e64cb1f 100644
 a/configure.ac
-+++ b/configure.ac
-@@ -663,6 +663,7 @@ AC_CHECK_SIZEOF(short)
- AC_CHECK_SIZEOF(size_t)
- AC_CHECK_SIZEOF(void *)
- AC_CHECK_SIZEOF(off_t)
-+AC_CHECK_SIZEOF(time_t)
- 
- AC_CHECK_TYPES([struct in6_addr, struct sockaddr_in6, sa_family_t, struct 
addrinfo, struct sockaddr_storage], , ,
- [#define _GNU_SOURCE
-diff --git a/test/regress_util.c b/test/regress_util.c
-index ef6a148..0c7eafb 100644
 a/test/regress_util.c
-+++ b/test/regress_util.c
-@@ -1412,10 +1412,12 @@ static struct date_rfc1123_case {
-   {  1289433600, "Thu, 11 Nov 2010 00:00:00 GMT"},
-   {  1323648000, "Mon, 12 Dec 2011 00:00:00 GMT"},
- #ifndef _WIN32
-+#if EVENT__SIZEOF_TIME_T > 4
-   /** In win32 case we have max   "23:59:59 January 18, 2038, UTC" for 
time32 */
-   {  4294967296, "Sun, 07 Feb 2106 06:28:16 GMT"} /* 2^32 */,
-   /** In win32 case we have max "23:59:59, December 31, 3000, UTC" for 
time64 */
-   {253402300799, "Fri, 31 Dec  23:59:59 GMT"} /* long long future no 
one can imagine */,
-+#endif /* time_t != 32bit */
-   {  1456704000, "Mon, 29 Feb 2016 00:00:00 GMT"} /* leap year */,
- #endif
-   {  1435708800, "Wed, 01 Jul 2015 00:00:00 GMT"} /* leap second */,
--- 
-2.13.3
-
diff --git a/meta/recipes-support/libevent/libevent_2.1.8.bb 
b/meta/recipes-support/libevent/libevent_2.1.10.bb
similarity index 84%
rename from meta/recipes-support/libevent/libevent_2.1.8.bb
rename to meta/recipes-support/libevent/libevent_2.1.10.bb
index 0f91e05a6c..81ceb1cd91 100644
--- a/meta/recipes-support/libevent/libevent_2.1.8.bb
+++ b/meta/recipes-support/libevent/libevent_2.1.10.bb
@@ -9,12 +9,11 @@ LIC_FILES_CHKSUM = 
"file://LICENSE;md5=17f20574c0b154d12236d5fbe964f549"
 SRC_URI = " \
 
https://github.com/libevent/libevent/releases/download/release-${PV}-stable/${BP}-stable.tar.gz
 \
 file://Makefile-missing-test-dir.patch \
-file://0001-test-fix-32bit-linux-regress.patch \
 file://run-ptest \
 "
 
-SRC_URI[md5sum] = "f3eeaed018542963b7d2416ef1135ecc"
-SRC_URI[sha256sum] = 
"965cc5a8bb46ce4199a47e9b2c9e1cae3b137e8356ffdad6d94d3b9069b71dc2"
+SRC_URI[md5sum] = "999caf86f52943af2363bc8077f00167"
+SRC_URI[sha256sum] = 
"e864af41a336bb11dab1a23f32993afe963c1f69618bd9292b89ecf6904845b0"
 
 UPSTREAM_CHECK_URI = "http://libevent.org/";
 
-- 
2.20.1



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


[OE-core] [PATCH] runtime/cases/logrotate: make test more reliable

2019-06-18 Thread Anuj Mittal
By default logrotate uses 'dateext' in logrotate.conf which results in a
date string being appended at the end of log name. In cases when a test
that installs configuration in logrotate.d is executed first (dnf for
example), it might result in errors when logrotate test is executed:

error: destination /var/log/dnf.librepo.log-20190528 already exists, skipping 
rotation
error: destination /var/log/dnf.rpm.log-20190528 already exists, skipping 
rotation
error: destination /var/log/hawkey.log-20190528 already exists, skipping 
rotation

Tweak the test to use it's own temporary configuration that doesn't
enable dateext.

Fixes [YOCTO #13363]

Signed-off-by: Anuj Mittal 
---
 meta/lib/oeqa/runtime/cases/logrotate.py | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/lib/oeqa/runtime/cases/logrotate.py 
b/meta/lib/oeqa/runtime/cases/logrotate.py
index 8358793a24..bfa57c534a 100644
--- a/meta/lib/oeqa/runtime/cases/logrotate.py
+++ b/meta/lib/oeqa/runtime/cases/logrotate.py
@@ -35,7 +35,9 @@ class LogrotateTest(OERuntimeTestCase):
 
 @OETestDepends(['logrotate.LogrotateTest.test_1_logrotate_setup'])
 def test_2_logrotate(self):
-status, output = self.target.run('logrotate -f /etc/logrotate.conf')
+status, output = self.target.run('echo "create \n include 
/etc/logrotate.d" > /tmp/logrotate-test.conf')
+status, output = self.target.run('logrotate -f 
/tmp/logrotate-test.conf')
+
 msg = ('logrotate service could not be reloaded. Status and output: '
 '%s and %s' % (status, output))
 self.assertEqual(status, 0, msg = msg)
-- 
2.20.1

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


Re: [OE-core] [PATCH V3] gcc-runtime: fix C++ header mapping for n32/x32 tune

2019-06-18 Thread Changqing Li



On 6/18/19 11:59 PM, Khem Raj wrote:

On Tue, Jun 18, 2019 at 12:47 AM  wrote:

From: Changqing Li 

The SDK was unable to find the C++ header pieces correctly since it's
using a generic compiler, not one specifically targeting the multilib
vendor prefix and default tune.  This adds the right mapping to ensure
SDKs work as expected. And fix problem in below configurations:

multilib configuration 1:
MACHINE="qemumips64"
MULTILIBS ?= "multilib:lib32 multilib:libn32"
DEFAULTTUNE_virtclass-multilib-lib32 ?= "mips"
DEFAULTTUNE_virtclass-multilib-libn32 ?= "mips64-n32"
MULTILIB_GLOBAL_VARIANTS_append = " libn32"
require conf/multilib.conf

ignoring nonexistent directory 
"/sysroots/mips64-poky-linux/usr/include/c++/8.2.0/mips64-poky-linux/32

multilib configuration 2:
MACHINE="qemumips64"
MULTILIBS = 'multilib:lib64 multilib:lib32'

machine is already 64bit so default lib config will be 64bit, what is
multilib:lib64 for here ?


This config is get from autobuilder.

machine is set to qemumips64, but DEFAULTTUNE is set to mips64-n32,

so this should be why use multilib:lib64.




DEFAULTTUNE = 'mips64-n32'
DEFAULTTUNE_virtclass-multilib-lib64 = 'mips64'
DEFAULTTUNE_virtclass-multilib-lib32 = 'mips32r2'
require conf/multilib.conf

For this configuration:
for target gcc-runtime, need to create symlink like mips64-poly-linux --> 
mips64-poky-linux-gnu32
for target lib64-gcc-runtime, need to create symlink like mips64-poly-linux/32 
--> mips64-pokymllib64-linux
in order to avoid conflict during populate_sdk, create symlink for subfoler 
bits/ext for target gcc-runtime,
this is ugly, but seems no better way to cover all kinds of configuration.

single lib configuration:
MACHINE="qemumips64"
DEFAULTTUNE = "mips64-n32"

Signed-off-by: Changqing Li 
---
  meta/recipes-devtools/gcc/gcc-runtime.inc | 29 +
  1 file changed, 17 insertions(+), 12 deletions(-)

diff --git a/meta/recipes-devtools/gcc/gcc-runtime.inc 
b/meta/recipes-devtools/gcc/gcc-runtime.inc
index 3d03d8e..ba767e1 100644
--- a/meta/recipes-devtools/gcc/gcc-runtime.inc
+++ b/meta/recipes-devtools/gcc/gcc-runtime.inc
@@ -86,10 +86,6 @@ do_install () {
 if [ -d ${D}${infodir} ]; then
 rmdir --ignore-fail-on-non-empty -p ${D}${infodir}
 fi
-   if [ "${TARGET_VENDOR_MULTILIB_ORIGINAL}" != "" -a "${TARGET_VENDOR}" != 
"${TARGET_VENDOR_MULTILIB_ORIGINAL}" ]; then
-   ln -s ${TARGET_SYS} 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR_MULTILIB_ORIGINAL}-${TARGET_OS}
-   fi
-
  }

  do_install_append_class-target () {
@@ -98,20 +94,29 @@ do_install_append_class-target () {
 fi

 if [ "${TARGET_OS}" = "linux-gnun32" ]; then
-   if [ "${MULTILIBS}" != "" ]; then
-   mkdir 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}-pokymllib64-linux
-   ln -s ../${TARGET_SYS} 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}-pokymllib64-linux/32
+   if [ "${TARGET_VENDOR_MULTILIB_ORIGINAL}" != "" -a "${TARGET_VENDOR}" != 
"${TARGET_VENDOR_MULTILIB_ORIGINAL}" ]; then
+   mkdir 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR_MULTILIB_ORIGINAL}-linux
+   ln -s ../${TARGET_SYS} 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR_MULTILIB_ORIGINAL}-linux/32
+   elif [ "${MULTILIB_VARIANTS}" != "" ]; then
+   mkdir 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR}-linux
+   ln -s ../${TARGET_SYS} 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR}-linux/32
 else
 ln -s ${TARGET_SYS} 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR}-linux
 fi
-   fi
-   if [ "${TARGET_OS}" = "linux-gnux32" ]; then
-   if [ "${MULTILIBS}" != "" ]; then
-   mkdir 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}-poky-linux
-   ln -s ../${TARGET_SYS} 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}-poky-linux/x32
+   elif [ "${TARGET_OS}" = "linux-gnux32" ]; then
+   if [ "${TARGET_VENDOR_MULTILIB_ORIGINAL}" != "" -a "${TARGET_VENDOR}" != 
"${TARGET_VENDOR_MULTILIB_ORIGINAL}" ]; then
+   mkdir 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR_MULTILIB_ORIGINAL}-linux
+   ln -s ../${TARGET_SYS} 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR_MULTILIB_ORIGINAL}-linux/x32
+   elif [ "${MULTILIB_VARIANTS}" != "" ]; then
+   mkdir 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR}-linux
+   ln -s ../${TARGET_SYS} 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR}-linux/32
 else
 ln -s ${TARGET_SYS} 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR}-linux
 fi
+   elif [ "${T

Re: [OE-core] [PATCH v3] openssl: Fix a build bug on aarch64BE.

2019-06-18 Thread Lei, Maohui
Hi Alex

> Seems like a contributor agreement is needed for this patch?
> https://www.openssl.org/policies/cla.html

Thank you for your reminder. It seems necessary to do Contributor Agreements. I 
sent my CLA just now.
Lei



From: Alexander Kanavin [mailto:alex.kana...@gmail.com]
Sent: Tuesday, June 18, 2019 7:24 PM
To: Lei, Maohui
Cc: OE-core
Subject: Re: [OE-core] [PATCH v3] openssl: Fix a build bug on aarch64BE.

On Tue, 18 Jun 2019 at 09:54, Lei Maohui 
mailto:leimao...@cn.fujitsu.com>> wrote:
+Upstream-Status: Submitted [https://github.com/openssl/openssl/pull/9151

Seems like a contributor agreement is needed for this patch?
https://www.openssl.org/policies/cla.html

Are you going to do tihs?

Alex


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


Re: [OE-core] [PATCH v2 3/4] linux-yocto: Mark qemuriscv64 as compatible

2019-06-18 Thread Bruce Ashfield
Looks good. Thanks for the v2, that clarifies things!

RP: I'll pull this into my queue, but not a big deal if it gets merged
otherwise. I'll have a new pull request out in a day or so.

Bruce

On Tue, Jun 18, 2019 at 8:58 PM Alistair Francis
 wrote:
>
> Signed-off-by: Alistair Francis 
> ---
>  meta/recipes-kernel/linux/linux-yocto_5.0.bb | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/meta/recipes-kernel/linux/linux-yocto_5.0.bb 
> b/meta/recipes-kernel/linux/linux-yocto_5.0.bb
> index 8aec315084..a8ced4866f 100644
> --- a/meta/recipes-kernel/linux/linux-yocto_5.0.bb
> +++ b/meta/recipes-kernel/linux/linux-yocto_5.0.bb
> @@ -7,6 +7,7 @@ KBRANCH_qemuarm  ?= "v5.0/standard/arm-versatile-926ejs"
>  KBRANCH_qemuarm64 ?= "v5.0/standard/qemuarm64"
>  KBRANCH_qemumips ?= "v5.0/standard/mti-malta32"
>  KBRANCH_qemuppc  ?= "v5.0/standard/qemuppc"
> +KBRANCH_qemuriscv64  ?= "v5.0/standard/base"
>  KBRANCH_qemux86  ?= "v5.0/standard/base"
>  KBRANCH_qemux86-64 ?= "v5.0/standard/base"
>  KBRANCH_qemumips64 ?= "v5.0/standard/mti-malta64"
> @@ -15,6 +16,7 @@ SRCREV_machine_qemuarm ?= 
> "9161b2fa2f1cec0ba02976c389c788445858e0de"
>  SRCREV_machine_qemuarm64 ?= "00638cdd8f92869a0f89ebe3289fdbd856ba9458"
>  SRCREV_machine_qemumips ?= "7de9b8f0db98e51a666477c8e2b64f1964b45410"
>  SRCREV_machine_qemuppc ?= "00638cdd8f92869a0f89ebe3289fdbd856ba9458"
> +SRCREV_machine_qemuriscv64 ?= "00638cdd8f92869a0f89ebe3289fdbd856ba9458"
>  SRCREV_machine_qemux86 ?= "00638cdd8f92869a0f89ebe3289fdbd856ba9458"
>  SRCREV_machine_qemux86-64 ?= "00638cdd8f92869a0f89ebe3289fdbd856ba9458"
>  SRCREV_machine_qemumips64 ?= "5a8b27bcc0b16077ab8edfcd3fb25c80dc2c652e"
> @@ -41,7 +43,7 @@ KCONF_BSP_AUDIT_LEVEL = "2"
>  KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
>  KERNEL_DEVICETREE_qemuarmv5 = "versatile-pb.dtb"
>
> -COMPATIBLE_MACHINE = 
> "qemuarm|qemuarmv5|qemuarm64|qemux86|qemuppc|qemumips|qemumips64|qemux86-64"
> +COMPATIBLE_MACHINE = 
> "qemuarm|qemuarmv5|qemuarm64|qemux86|qemuppc|qemumips|qemumips64|qemux86-64|qemuriscv64"
>
>  # Functionality flags
>  KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc"
> --
> 2.22.0
>
> --
> ___
> 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
- "Use the force Harry" - Gandalf, Star Trek II
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH] systemd-conf: not configure network for nfs root

2019-06-18 Thread kai.kang
From: Kai Kang 

It fails to boot nfs root with systemd that systemd-networkd
re-configures wired network and breaks the connection with nfs root.

Signed-off-by: Kai Kang 
---
 meta/recipes-core/systemd/systemd-conf/wired.network | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-core/systemd/systemd-conf/wired.network 
b/meta/recipes-core/systemd/systemd-conf/wired.network
index 253aee9382..ff807ba31f 100644
--- a/meta/recipes-core/systemd/systemd-conf/wired.network
+++ b/meta/recipes-core/systemd/systemd-conf/wired.network
@@ -1,5 +1,6 @@
 [Match]
 Name=en* eth*
+KernelCommandLine=!nfsroot
 
 [Network]
 DHCP=yes
-- 
2.20.0

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


[OE-core] [PATCH v2 3/4] linux-yocto: Mark qemuriscv64 as compatible

2019-06-18 Thread Alistair Francis
Signed-off-by: Alistair Francis 
---
 meta/recipes-kernel/linux/linux-yocto_5.0.bb | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto_5.0.bb 
b/meta/recipes-kernel/linux/linux-yocto_5.0.bb
index 8aec315084..a8ced4866f 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.0.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.0.bb
@@ -7,6 +7,7 @@ KBRANCH_qemuarm  ?= "v5.0/standard/arm-versatile-926ejs"
 KBRANCH_qemuarm64 ?= "v5.0/standard/qemuarm64"
 KBRANCH_qemumips ?= "v5.0/standard/mti-malta32"
 KBRANCH_qemuppc  ?= "v5.0/standard/qemuppc"
+KBRANCH_qemuriscv64  ?= "v5.0/standard/base"
 KBRANCH_qemux86  ?= "v5.0/standard/base"
 KBRANCH_qemux86-64 ?= "v5.0/standard/base"
 KBRANCH_qemumips64 ?= "v5.0/standard/mti-malta64"
@@ -15,6 +16,7 @@ SRCREV_machine_qemuarm ?= 
"9161b2fa2f1cec0ba02976c389c788445858e0de"
 SRCREV_machine_qemuarm64 ?= "00638cdd8f92869a0f89ebe3289fdbd856ba9458"
 SRCREV_machine_qemumips ?= "7de9b8f0db98e51a666477c8e2b64f1964b45410"
 SRCREV_machine_qemuppc ?= "00638cdd8f92869a0f89ebe3289fdbd856ba9458"
+SRCREV_machine_qemuriscv64 ?= "00638cdd8f92869a0f89ebe3289fdbd856ba9458"
 SRCREV_machine_qemux86 ?= "00638cdd8f92869a0f89ebe3289fdbd856ba9458"
 SRCREV_machine_qemux86-64 ?= "00638cdd8f92869a0f89ebe3289fdbd856ba9458"
 SRCREV_machine_qemumips64 ?= "5a8b27bcc0b16077ab8edfcd3fb25c80dc2c652e"
@@ -41,7 +43,7 @@ KCONF_BSP_AUDIT_LEVEL = "2"
 KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
 KERNEL_DEVICETREE_qemuarmv5 = "versatile-pb.dtb"
 
-COMPATIBLE_MACHINE = 
"qemuarm|qemuarmv5|qemuarm64|qemux86|qemuppc|qemumips|qemumips64|qemux86-64"
+COMPATIBLE_MACHINE = 
"qemuarm|qemuarmv5|qemuarm64|qemux86|qemuppc|qemumips|qemumips64|qemux86-64|qemuriscv64"
 
 # Functionality flags
 KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc"
-- 
2.22.0

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


[OE-core] [PATCH v2 2/4] opensbi: Initial commit of OpenSBI

2019-06-18 Thread Alistair Francis
This is used as a bootloader for RISC-V QEMU machines.

Signed-off-by: Alistair Francis 
---
 ...Makefile-Don-t-specify-mabi-or-march.patch |  38 ++
 ...-lib-Create-a-sbi_ipi_data-structure.patch | 128 ++
 meta/recipes-bsp/opensbi/opensbi-payloads.inc |  37 +
 meta/recipes-bsp/opensbi/opensbi_0.3.bb   |  49 +++
 4 files changed, 252 insertions(+)
 create mode 100644 
meta/recipes-bsp/opensbi/files/0001-Makefile-Don-t-specify-mabi-or-march.patch
 create mode 100644 
meta/recipes-bsp/opensbi/files/0002-lib-Create-a-sbi_ipi_data-structure.patch
 create mode 100644 meta/recipes-bsp/opensbi/opensbi-payloads.inc
 create mode 100644 meta/recipes-bsp/opensbi/opensbi_0.3.bb

diff --git 
a/meta/recipes-bsp/opensbi/files/0001-Makefile-Don-t-specify-mabi-or-march.patch
 
b/meta/recipes-bsp/opensbi/files/0001-Makefile-Don-t-specify-mabi-or-march.patch
new file mode 100644
index 00..9c2d0eb479
--- /dev/null
+++ 
b/meta/recipes-bsp/opensbi/files/0001-Makefile-Don-t-specify-mabi-or-march.patch
@@ -0,0 +1,38 @@
+From f5871e1f3650d6c8a032928cb5d8ca00c275c377 Mon Sep 17 00:00:00 2001
+From: Alistair Francis 
+Date: Fri, 15 Feb 2019 14:57:41 -0800
+Subject: [PATCH] Makefile: Don't specify mabi or march
+
+To avoid
+can't link double-float modules with soft-float modules
+errors when building 32-bit openSBI don't specify mabi or march.
+
+Upstream-Status: Inappropriate [Fixes a 32-bit Yocto flow bug]
+Signed-off-by: Alistair Francis 
+---
+ Makefile | 2 --
+ 1 file changed, 2 deletions(-)
+
+diff --git a/Makefile b/Makefile
+index ae68f55..10851fc 100644
+--- a/Makefile
 b/Makefile
+@@ -145,7 +145,6 @@ GENFLAGS   +=  $(firmware-genflags-y)
+ CFLAGS=   -g -Wall -Werror -nostdlib -fno-strict-aliasing 
-O2
+ CFLAGS+=  -fno-omit-frame-pointer 
-fno-optimize-sibling-calls
+ CFLAGS+=  -mno-save-restore -mstrict-align
+-CFLAGS+=  -mabi=$(PLATFORM_RISCV_ABI) 
-march=$(PLATFORM_RISCV_ISA)
+ CFLAGS+=  -mcmodel=$(PLATFORM_RISCV_CODE_MODEL)
+ CFLAGS+=  $(GENFLAGS)
+ CFLAGS+=  $(platform-cflags-y)
+@@ -158,7 +157,6 @@ CPPFLAGS   +=  $(firmware-cppflags-y)
+ ASFLAGS   =   -g -Wall -nostdlib -D__ASSEMBLY__
+ ASFLAGS   +=  -fno-omit-frame-pointer 
-fno-optimize-sibling-calls
+ ASFLAGS   +=  -mno-save-restore -mstrict-align
+-ASFLAGS   +=  -mabi=$(PLATFORM_RISCV_ABI) 
-march=$(PLATFORM_RISCV_ISA)
+ ASFLAGS   +=  -mcmodel=$(PLATFORM_RISCV_CODE_MODEL)
+ ASFLAGS   +=  $(GENFLAGS)
+ ASFLAGS   +=  $(platform-asflags-y)
+-- 
+2.20.1
+
diff --git 
a/meta/recipes-bsp/opensbi/files/0002-lib-Create-a-sbi_ipi_data-structure.patch 
b/meta/recipes-bsp/opensbi/files/0002-lib-Create-a-sbi_ipi_data-structure.patch
new file mode 100644
index 00..3c846bde62
--- /dev/null
+++ 
b/meta/recipes-bsp/opensbi/files/0002-lib-Create-a-sbi_ipi_data-structure.patch
@@ -0,0 +1,128 @@
+From 508a27204cbbca0a9430236e56681e5e0d343fb9 Mon Sep 17 00:00:00 2001
+From: Alistair Francis 
+Date: Fri, 8 Mar 2019 11:22:22 -0800
+Subject: [PATCH] lib: Create a sbi_ipi_data structure
+
+Create a sbi_ipi_data structure that holds unpacked IPI information. At
+the same time remove ipi_type from the sbi_scratch struct and use a
+fixed offset to access it.
+
+This structure fits in behind the sbi_scratch structure.
+
+This fixes https://github.com/riscv/opensbi/issues/81
+
+Upstream-Status: Backport 
[https://github.com/riscv/opensbi/commit/508a27204cbbca0a9430236e56681e5e0d343fb9]
+Signed-off-by: Alistair Francis 
+---
+ firmware/fw_base.S|  1 -
+ include/sbi/sbi_scratch.h | 23 ---
+ lib/sbi_ipi.c |  8 +---
+ 3 files changed, 21 insertions(+), 11 deletions(-)
+
+diff --git a/firmware/fw_base.S b/firmware/fw_base.S
+index cf2c6a0..69cfc90 100644
+--- a/firmware/fw_base.S
 b/firmware/fw_base.S
+@@ -183,7 +183,6 @@ _start_warm:
+   REG_S   a4, SBI_SCRATCH_PLATFORM_ADDR_OFFSET(tp)
+   la  a4, _hartid_to_scratch
+   REG_S   a4, SBI_SCRATCH_HARTID_TO_SCRATCH_OFFSET(tp)
+-  REG_S   zero, SBI_SCRATCH_IPI_TYPE_OFFSET(tp)
+   REG_S   zero, SBI_SCRATCH_TMP0_OFFSET(tp)
+ 
+   /* Setup stack */
+diff --git a/include/sbi/sbi_scratch.h b/include/sbi/sbi_scratch.h
+index 8389ef3..70ab384 100644
+--- a/include/sbi/sbi_scratch.h
 b/include/sbi/sbi_scratch.h
+@@ -28,17 +28,24 @@
+ #define SBI_SCRATCH_PLATFORM_ADDR_OFFSET  (6 * __SIZEOF_POINTER__)
+ /** Offset of hartid_to_scratch member in sbi_scratch */
+ #define SBI_SCRATCH_HARTID_TO_SCRATCH_OFFSET  (7 * __SIZEOF_POINTER__)
+-/** Offset of ipi_type member in sbi_scratch */
+-#define SBI_SCRATCH_IPI_TYPE_OFFSET   (8 * __SIZEOF_POINTER__)
+ /** Offset of tmp0 member in sbi_scratch */
+-#define SBI_SCRATCH_TMP0_OFFSET   (9 * __SIZEOF_POINT

[OE-core] [PATCH v2 4/4] qemuriscv64: Add the QEMU RISC-V 64-bit machine

2019-06-18 Thread Alistair Francis
The include is split ready to add the 32-bit RISC-V machine as soon as
glibc supports 32-bit RISC-V.

This is based on the work in the meta-riscv layer, thanks to Khem for
starting this.

Signed-off-by: Alistair Francis 
---
 .../conf/machine/include/riscv/arch-riscv.inc | 10 +
 meta/conf/machine/include/riscv/qemuriscv.inc | 45 +++
 .../conf/machine/include/riscv/tune-riscv.inc | 19 
 meta/conf/machine/qemuriscv64.conf| 11 +
 4 files changed, 85 insertions(+)
 create mode 100644 meta/conf/machine/include/riscv/arch-riscv.inc
 create mode 100644 meta/conf/machine/include/riscv/qemuriscv.inc
 create mode 100644 meta/conf/machine/include/riscv/tune-riscv.inc
 create mode 100644 meta/conf/machine/qemuriscv64.conf

diff --git a/meta/conf/machine/include/riscv/arch-riscv.inc 
b/meta/conf/machine/include/riscv/arch-riscv.inc
new file mode 100644
index 00..19f8f3e211
--- /dev/null
+++ b/meta/conf/machine/include/riscv/arch-riscv.inc
@@ -0,0 +1,10 @@
+# RISCV Architecture definition
+
+DEFAULTTUNE ?= "riscv64"
+
+TUNE_ARCH = "${TUNE_ARCH_tune-${DEFAULTTUNE}}"
+TUNE_PKGARCH = "${TUNE_PKGARCH_tune-${DEFAULTTUNE}}"
+TUNE_CCARGS .= ""
+
+# QEMU usermode fails with invalid instruction error (For riscv32)
+MACHINE_FEATURES_BACKFILL_CONSIDERED_append = 
"${@bb.utils.contains('TUNE_FEATURES', 'riscv32', ' qemu-usermode', '', d)}"
diff --git a/meta/conf/machine/include/riscv/qemuriscv.inc 
b/meta/conf/machine/include/riscv/qemuriscv.inc
new file mode 100644
index 00..aa1eba77da
--- /dev/null
+++ b/meta/conf/machine/include/riscv/qemuriscv.inc
@@ -0,0 +1,45 @@
+PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot"
+
+require conf/machine/include/qemu.inc
+require conf/machine/include/riscv/tune-riscv.inc
+
+MACHINE_FEATURES = "screen keyboard ext2 ext3 serial"
+
+KERNEL_IMAGETYPE = "Image"
+
+SERIAL_CONSOLES ?= "115200;ttyS0 115200;hvc0"
+
+IMAGE_FSTYPES_append = " ext4"
+
+MACHINE_EXTRA_RRECOMMENDS += " kernel-modules"
+
+EXTRA_IMAGEDEPENDS += "opensbi"
+RISCV_SBI_PLAT ?= "qemu/virt"
+RISCV_SBI_PAYLOAD ?= "${KERNEL_IMAGETYPE}-${MACHINE}.bin"
+
+# qemuboot options
+QB_KERNEL_CMDLINE_APPEND = "earlycon=sbi"
+QB_MEM = "-m 512"
+QB_MACHINE = "-machine virt"
+QB_DEFAULT_KERNEL = "fw_jump.elf"
+QB_TAP_OPT = "-netdev tap,id=net0,ifname=@TAP@,script=no,downscript=no"
+QB_NETWORK_DEVICE = "-device virtio-net-device,netdev=net0,mac=@MAC@"
+QB_ROOTFS_OPT = "-drive id=disk0,file=@ROOTFS@,if=none,format=raw -device 
virtio-blk-device,drive=disk0"
+QB_SERIAL_OPT = "-device virtio-serial-device -chardev null,id=virtcon -device 
virtconsole,chardev=virtcon"
+QB_TCPSERIAL_OPT = " -device virtio-serial-device -chardev 
socket,id=virtcon,port=@PORT@,host=127.0.0.1 -device 
virtconsole,chardev=virtcon"
+# Add the 'virtio-rng-pci' device otherwise the guest may run out of entropy
+QB_OPT_APPEND = " -object rng-random,filename=/dev/urandom,id=rng0 -device 
virtio-rng-device,rng=rng0"
+
+BAD_RECOMMENDATIONS += "\
+libcxx-dev \
+libcxx-staticdev \
+compiler-rt-dev \
+compiler-rt-staticdev \
+"
+
+ASSUME_PROVIDED += "\
+libcxx-dev \
+libcxx-staticdev \
+compiler-rt-dev \
+compiler-rt-staticdev \
+"
diff --git a/meta/conf/machine/include/riscv/tune-riscv.inc 
b/meta/conf/machine/include/riscv/tune-riscv.inc
new file mode 100644
index 00..1e3a1081e0
--- /dev/null
+++ b/meta/conf/machine/include/riscv/tune-riscv.inc
@@ -0,0 +1,19 @@
+require conf/machine/include/riscv/arch-riscv.inc
+
+TUNEVALID[riscv64] = "Enable 64-bit RISC-V optimizations"
+TUNEVALID[riscv32] = "Enable 32-bit RISC-V optimizations"
+
+TUNEVALID[littleendian] = "Little endian mode"
+
+AVAILTUNES += "riscv64 riscv32"
+
+TUNE_FEATURES_tune-riscv64 = "riscv64 littleendian"
+TUNE_ARCH_tune-riscv64 = "riscv64"
+TUNE_PKGARCH_tune-riscv64 = "riscv64"
+PACKAGE_EXTRA_ARCHS_tune-riscv64 = "riscv64"
+
+TUNE_FEATURES_tune-riscv32 = "riscv32 littleendian"
+TUNE_ARCH_tune-riscv32 = "riscv32"
+TUNE_PKGARCH_tune-riscv32 = "riscv32"
+PACKAGE_EXTRA_ARCHS_tune-riscv32 = "riscv32"
+
diff --git a/meta/conf/machine/qemuriscv64.conf 
b/meta/conf/machine/qemuriscv64.conf
new file mode 100644
index 00..f1be7b8a71
--- /dev/null
+++ b/meta/conf/machine/qemuriscv64.conf
@@ -0,0 +1,11 @@
+#@TYPE: Machine
+#@NAME: generic riscv64 machine
+#@DESCRIPTION: Machine configuration for running a generic riscv64
+
+require conf/machine/include/riscv/qemuriscv.inc
+
+QB_OPT_APPEND = "-show-cursor -monitor null -device 
loader,file=${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE},addr=0x8020"
+
+EXTRA_IMAGEDEPENDS += "u-boot"
+UBOOT_MACHINE = "qemu-riscv64_defconfig"
+UBOOT_ELF = "u-boot"
-- 
2.22.0

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


[OE-core] [PATCH v2 1/4] libffi: Add RISC-V support

2019-06-18 Thread Alistair Francis
Backport a libffi patch to add RISC-V support.

Signed-off-by: Alistair Francis 
---
 .../libffi/0001-New-RISC-V-port-281.patch | 827 ++
 meta/recipes-support/libffi/libffi_3.2.1.bb   |   5 +-
 2 files changed, 830 insertions(+), 2 deletions(-)
 create mode 100644 
meta/recipes-support/libffi/libffi/0001-New-RISC-V-port-281.patch

diff --git a/meta/recipes-support/libffi/libffi/0001-New-RISC-V-port-281.patch 
b/meta/recipes-support/libffi/libffi/0001-New-RISC-V-port-281.patch
new file mode 100644
index 00..589c4d3c44
--- /dev/null
+++ b/meta/recipes-support/libffi/libffi/0001-New-RISC-V-port-281.patch
@@ -0,0 +1,827 @@
+From 8ac73103bf12ce4f776940cb17f3ced15a362f23 Mon Sep 17 00:00:00 2001
+From: Stef O'Rear 
+Date: Sun, 11 Mar 2018 05:55:15 -0700
+Subject: [PATCH] New RISC-V port (#281)
+
+* Add RISC-V support
+
+This patch adds support for the RISC-V architecture (https://riscv.org).
+
+This patch has been tested using QEMU user-mode emulation and GCC 7.2.0
+in the following configurations:
+
+* -march=rv32imac -mabi=ilp32
+* -march=rv32g -mabi=ilp32d
+* -march=rv64imac -mabi=lp64
+* -march=rv64g -mabi=lp64d
+
+The ABI currently can be found at
+https://github.com/riscv/riscv-elf-psabi-doc/blob/master/riscv-elf.md .
+
+* Add RISC-V to README
+
+* RISC-V: fix configure.host
+
+Upstream-Status: Backport 
[https://github.com/libffi/libffi/commit/3840d49aaa831d649b1597518a2903dfed0d57f3]
+Signed-off-by: Alistair Francis 
+---
+ Makefile.am   |   4 +
+ configure.ac  |   5 +
+ src/riscv/ffi.c   | 445 ++
+ src/riscv/ffitarget.h |  68 +++
+ src/riscv/sysv.S  | 214 
+ 5 files changed, 736 insertions(+)
+ create mode 100644 src/riscv/ffi.c
+ create mode 100644 src/riscv/ffitarget.h
+ create mode 100644 src/riscv/sysv.S
+
+diff --git a/Makefile.am b/Makefile.am
+index 0e40451..3837650 100644
+--- a/Makefile.am
 b/Makefile.am
+@@ -32,6 +32,7 @@ EXTRA_DIST = LICENSE ChangeLog.v1 ChangeLog.libgcj   
\
+src/powerpc/asm.h src/powerpc/aix.S src/powerpc/darwin.S   \
+src/powerpc/aix_closure.S src/powerpc/darwin_closure.S \
+src/powerpc/ffi_darwin.c src/powerpc/ffitarget.h   \
++   src/riscv/ffi.c src/riscv/ffitarget.h src/riscv/sysv.S \
+src/s390/ffi.c src/s390/sysv.S src/s390/ffitarget.h\
+src/sh/ffi.c src/sh/sysv.S src/sh/ffitarget.h src/sh64/ffi.c   \
+src/sh64/sysv.S src/sh64/ffitarget.h src/sparc/v8.S\
+@@ -122,6 +123,9 @@ endif
+ if MIPS
+ nodist_libffi_la_SOURCES += src/mips/ffi.c src/mips/o32.S src/mips/n32.S
+ endif
++if RISCV
++nodist_libffi_la_SOURCES += src/riscv/ffi.c src/riscv/sysv.S
++endif
+ if BFIN
+ nodist_libffi_la_SOURCES += src/bfin/ffi.c src/bfin/sysv.S
+ endif
+diff --git a/configure.ac b/configure.ac
+index ce30853..33375aa 100644
+--- a/configure.ac
 b/configure.ac
+@@ -226,6 +226,10 @@ case "$host" in
+   TARGET=MIPS; TARGETDIR=mips
+   ;;
+ 
++  riscv*-*-*)
++  TARGET=RISCV; TARGETDIR=riscv
++  ;;
++
+   nios2*-linux*)
+   TARGET=NIOS2; TARGETDIR=nios2
+   ;;
+@@ -298,6 +302,7 @@ if test $TARGETDIR = unknown; then
+ fi
+ 
+ AM_CONDITIONAL(MIPS, test x$TARGET = xMIPS)
++AM_CONDITIONAL(RISCV, test x$TARGET = xRISCV)
+ AM_CONDITIONAL(BFIN, test x$TARGET = xBFIN)
+ AM_CONDITIONAL(SPARC, test x$TARGET = xSPARC)
+ AM_CONDITIONAL(X86, test x$TARGET = xX86)
+diff --git a/src/riscv/ffi.c b/src/riscv/ffi.c
+new file mode 100644
+index 000..b744fdd
+--- /dev/null
 b/src/riscv/ffi.c
+@@ -0,0 +1,445 @@
++/* ---
++   ffi.c - Copyright (c) 2015 Michael Knyszek 
++ 2015 Andrew Waterman 
++ 2018 Stef O'Rear 
++   Based on MIPS N32/64 port
++
++   RISC-V Foreign Function Interface
++
++   Permission is hereby granted, free of charge, to any person obtaining
++   a copy of this software and associated documentation files (the
++   ``Software''), to deal in the Software without restriction, including
++   without limitation the rights to use, copy, modify, merge, publish,
++   distribute, sublicense, and/or sell copies of the Software, and to
++   permit persons to whom the Software is furnished to do so, subject to
++   the following conditions:
++
++   The above copyright notice and this permission notice shall be included
++   in all copies or substantial portions of the Software.
++
++   THE SOFTWARE IS PROVIDED ``AS IS'', WITHOUT WARRANTY OF ANY KIND,
++   EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
++   MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
++   NONINFRINGEMENT.  IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
++   HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
++   WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
++   OUT OF OR IN CONNECTION WITH THE SOFT

Re: [OE-core] [PATCH 3/4] linux-yocto: Mark qemuriscv64 as compatible

2019-06-18 Thread Alistair Francis
On Tue, Jun 18, 2019 at 11:30 AM Bruce Ashfield
 wrote:
>
> On Tue, Jun 18, 2019 at 12:03 PM Khem Raj  wrote:
> >
> > On Mon, Jun 17, 2019 at 8:44 PM Bruce Ashfield  
> > wrote:
> > >
> > > On Mon, Jun 17, 2019 at 6:04 PM Alistair Francis
> > >  wrote:
> > > >
> > > > Signed-off-by: Alistair Francis 
> > > > ---
> > > >  meta/recipes-kernel/linux/linux-yocto_5.0.bb | 2 +-
> > > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > >
> > > > diff --git a/meta/recipes-kernel/linux/linux-yocto_5.0.bb 
> > > > b/meta/recipes-kernel/linux/linux-yocto_5.0.bb
> > > > index 8aec315084..a79d0b962d 100644
> > > > --- a/meta/recipes-kernel/linux/linux-yocto_5.0.bb
> > > > +++ b/meta/recipes-kernel/linux/linux-yocto_5.0.bb
> > > > @@ -41,7 +41,7 @@ KCONF_BSP_AUDIT_LEVEL = "2"
> > > >  KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
> > > >  KERNEL_DEVICETREE_qemuarmv5 = "versatile-pb.dtb"
> > > >
> > > > -COMPATIBLE_MACHINE = 
> > > > "qemuarm|qemuarmv5|qemuarm64|qemux86|qemuppc|qemumips|qemumips64|qemux86-64"
> > > > +COMPATIBLE_MACHINE = 
> > > > "qemuarm|qemuarmv5|qemuarm64|qemux86|qemuppc|qemumips|qemumips64|qemux86-64|qemuriscv64"
> > >
> > > What KBRANCH / SRCREV would this be building ? Unless it is something
> > > that I'm building and booting, we shouldn't put it in the core recipe
> > > as compatible until the SRCREV and KBRANCH are defined.
> > >
> >
> > it needs to be master branch of repo since it needs no additional
> > patches KBRANCH is not needed I suppose. and SRCREV can be picked from
> > master branch.
>
> Nope. That means /standard/base is the KBRANCH.  master is
> reference only in the tree, and that's where SRCREV comes from as
> well.
> Regardless, it (the branch) should be set explicitly in the recipe if
> we mark it as compatible, since the branch documents the details.

Makes sense, fixed in my v2.

Alistair

>
> Bruce
>
> >
> > > Bruce
> > >
> > >
> > > >
> > > >  # Functionality flags
> > > >  KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc"
> > > > --
> > > > 2.22.0
> > > >
> > > > --
> > > > ___
> > > > 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
> > > - "Use the force Harry" - Gandalf, Star Trek II
> > > --
> > > ___
> > > 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
> - "Use the force Harry" - Gandalf, Star Trek II
> --
> ___
> 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] linux-yocto: Add scsi_debug module when ptest is in DISTRO_FEATURES

2019-06-18 Thread Mariano Lopez


On 6/15/19 8:02 PM, Bruce Ashfield wrote:

On Sat, Jun 15, 2019 at 3:47 PM Mariano Lopez
 wrote:


On 6/15/19 10:15 AM, Richard Purdie wrote:

On Thu, 2019-06-13 at 22:32 -0500, Mariano López wrote:

util-linux ptest requires the scsi_debug module to perform eject/mount
tests. This will conditionally add scsi_debug module when ptest is in
DISTRO_FEATURES.

This doesn't include linux-yocto-tiny because the resulting image will
be too big and do_image would complain about this.

[YOCTO #13301]

Signed-off-by: Mariano López 
---
   meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb | 1 +
   meta/recipes-kernel/linux/linux-yocto-rt_5.0.bb  | 1 +
   meta/recipes-kernel/linux/linux-yocto_4.19.bb| 1 +
   meta/recipes-kernel/linux/linux-yocto_5.0.bb | 1 +
   4 files changed, 4 insertions(+)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb
index 6604bdf90c..0836dc7ea0 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb
@@ -41,3 +41,4 @@ KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
   KERNEL_FEATURES_append_qemuall=" cfg/virtio.scc"
   KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
   KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc cfg/paravirt_kvm.scc"
+KERNEL_FEATURES_append = "${@bb.utils.contains("DISTRO_FEATURES", "ptest", " 
features/scsi/scsi-debug.scc", "" ,d)}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.0.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_5.0.bb
index 1fe28b1bf0..b5e415f935 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.0.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.0.bb
@@ -41,3 +41,4 @@ KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
   KERNEL_FEATURES_append_qemuall=" cfg/virtio.scc"
   KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
   KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc cfg/paravirt_kvm.scc"
+KERNEL_FEATURES_append = "${@bb.utils.contains("DISTRO_FEATURES", "ptest", " 
features/scsi/scsi-debug.scc", "" ,d)}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.19.bb 
b/meta/recipes-kernel/linux/linux-yocto_4.19.bb
index a5fdafe6b2..cda4ecf89e 100644
--- a/meta/recipes-kernel/linux/linux-yocto_4.19.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_4.19.bb
@@ -47,3 +47,4 @@ KERNEL_FEATURES_append_qemuall=" cfg/virtio.scc"
   KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
   KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc cfg/paravirt_kvm.scc"
   KERNEL_FEATURES_append = " ${@bb.utils.contains("TUNE_FEATURES", "mx32", " cfg/x32.scc", 
"" ,d)}"
+KERNEL_FEATURES_append = " ${@bb.utils.contains("DISTRO_FEATURES", "ptest", " 
features/scsi/scsi-debug.scc", "" ,d)}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.0.bb 
b/meta/recipes-kernel/linux/linux-yocto_5.0.bb
index da795d97aa..8aec315084 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.0.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.0.bb
@@ -50,3 +50,4 @@ KERNEL_FEATURES_append_qemuall=" cfg/virtio.scc"
   KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
   KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc cfg/paravirt_kvm.scc"
   KERNEL_FEATURES_append = " ${@bb.utils.contains("TUNE_FEATURES", "mx32", " cfg/x32.scc", 
"" ,d)}"
+KERNEL_FEATURES_append = " ${@bb.utils.contains("DISTRO_FEATURES", "ptest", " 
features/scsi/scsi-debug.scc", "" ,d)}"

I merged this but have just realised its causing warnings:

https://autobuilder.yoctoproject.org/typhoon/#/builders/93/builds/31

which suggest its not quite doing what we hope/need? :/

Cheers,

Richard

Indeed, it seems the configuration is not applied for the qemuarm64
MACHINE:(


It would be applied, but it may be missing some dependency on that
machine and is hence not enabled in the final kernel .config.

Bruce


SCSI support is not enabled by default for ARM architectures, I just 
sent the patch for this:

http://lists.openembedded.org/pipermail/openembedded-core/2019-June/283775.html


Thanks!
Mariano




Let me look into this and send another patch

Thanks,
Mairano




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


[OE-core] [PATCHv2] serf: stop scons trying to create directories in hosts rootfs

2019-06-18 Thread Martin Jansa
* since 1522f09a4d serf: cleanup recipe
  serf.do_install fails in builds with multilib enabled (with
  libdir=/usr/lib64 on host where /usr/lib64 doesn't exist)

DEBUG: Executing shell function do_install
scons: Reading SConscript files ...
PermissionError: [Errno 13] Permission denied: '/usr/lib64':
  File 
"TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/serf-1.3.9/SConstruct", 
line 158:
ENV = os.environ,
  File 
"/TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/recipe-sysroot-native/usr/bin/../../usr/lib/python3.7/site-packages/SCons/Environment.py",
 line 965:
variables.Update(self)
  File 
"/TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/recipe-sysroot-native/usr/bin/../../usr/lib/python3.7/site-packages/SCons/Variables/__init__.py",
 line 227:
option.validator(option.key, env.subst('${%s}'%option.key), env)
  File 
"TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/serf-1.3.9/SConstruct", 
line 60:
return PathVariable.PathIsDirCreate(key, val, env)
  File 
"/TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/recipe-sysroot-native/usr/bin/../../usr/lib/python3.7/site-packages/SCons/Variables/PathVariable.py",
 line 101:
os.makedirs(val)
  File 
"TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/recipe-sysroot-native/usr/lib/python3.7/os.py",
 line 221:
mkdir(name, mode)
ERROR: scons install execution failed.

* I don't know how exactly --install-sandbox is supposed to work but
  in this case it's trying to mkdir /usr/lib64 on the host rootfs
  which is clearly wrong and if I set LIBDIR together with
  --install-sandbox then the install paths are prefixed with $D twice
  in some cases (not for includedir and empty libdir at the end).
  So in the end I think it was an issue caused by the custom path
  validator in serf's SConstruct, removing that stops touching host
  and the installed paths (including the paths inside libserf*.pc)
  look correct

Signed-off-by: Martin Jansa 
---
 ...ories.without.sandbox-install.prefix.patch | 71 +++
 meta/recipes-support/serf/serf_1.3.9.bb   |  1 +
 2 files changed, 72 insertions(+)
 create mode 100644 
meta/recipes-support/serf/serf/SConstruct.stop.creating.directories.without.sandbox-install.prefix.patch

diff --git 
a/meta/recipes-support/serf/serf/SConstruct.stop.creating.directories.without.sandbox-install.prefix.patch
 
b/meta/recipes-support/serf/serf/SConstruct.stop.creating.directories.without.sandbox-install.prefix.patch
new file mode 100644
index 00..91640d6044
--- /dev/null
+++ 
b/meta/recipes-support/serf/serf/SConstruct.stop.creating.directories.without.sandbox-install.prefix.patch
@@ -0,0 +1,71 @@
+stop scons trying to create directories in hosts rootfs
+
+* since 1522f09a4d serf: cleanup recipe
+  serf.do_install fails in builds with multilib enabled (with
+  libdir=/usr/lib64 on host where /usr/lib64 doesn't exist)
+
+DEBUG: Executing shell function do_install
+scons: Reading SConscript files ...
+PermissionError: [Errno 13] Permission denied: '/usr/lib64':
+  File 
"TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/serf-1.3.9/SConstruct", 
line 158:
+ENV = os.environ,
+  File 
"/TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/recipe-sysroot-native/usr/bin/../../usr/lib/python3.7/site-packages/SCons/Environment.py",
 line 965:
+variables.Update(self)
+  File 
"/TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/recipe-sysroot-native/usr/bin/../../usr/lib/python3.7/site-packages/SCons/Variables/__init__.py",
 line 227:
+option.validator(option.key, env.subst('${%s}'%option.key), env)
+  File 
"TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/serf-1.3.9/SConstruct", 
line 60:
+return PathVariable.PathIsDirCreate(key, val, env)
+  File 
"/TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/recipe-sysroot-native/usr/bin/../../usr/lib/python3.7/site-packages/SCons/Variables/PathVariable.py",
 line 101:
+os.makedirs(val)
+  File 
"TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/recipe-sysroot-native/usr/lib/python3.7/os.py",
 line 221:
+mkdir(name, mode)
+ERROR: scons install execution failed.
+
+* I don't know how exactly --install-sandbox is supposed to work but
+  in this case it's trying to mkdir /usr/lib64 on the host rootfs
+  which is clearly wrong and if I set LIBDIR together with
+  --install-sandbox then the install paths are prefixed with $D twice
+  in some cases (not for includedir and empty libdir at the end).
+  So in the end I think it was an issue caused by the custom path
+  validator in serf's SConstruct, removing that stops touching host
+  and the installed paths (including the paths inside libserf*.pc)
+  look correct
+
+Upstream-Status: Pending
+
+Signed-off-by: Martin Jansa 
+
+--- serf-1.3.9/SConstruct  2019-06-18 15:49:19.968961108 +
 serf-1.3.9b/SConstruct 2019-06-18 18:53:21.412337151 +
+@@ -51,17 +51,6 @@
+ """
+ return (key, '%s' % (help), default, None, lambda val: _c

[OE-core] Yocto Project Status WW25'19

2019-06-18 Thread sjolley.yp.pm
Current Dev Position: YP 2.8 M2

Next Deadline: YP 2.8 Milestone 2 Cutoff July 14th, 2019

 

SWAT Team Rotation:

*   SWAT lead is currently: Paul
*   SWAT team rotation: Paul -> Ross on June 21, 2019
*   SWAT team rotation: Ross -> Amanda on June 28, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Next Team Meetings:

*   Bug Triage meeting Thursday June 20th at 7:30am PDT (
 https://zoom.us/j/454367603)
*   Monthly Project Meeting Tuesday July 2nd at 8am PDT (
 https://zoom.us/j/990892712) 
*   Twitch - Next event is Tuesday 9th July at 8am PDT (
 https://www.twitch.tv/yocto_project)

 

Key Status/Updates:

*   2.8 M1 has been through QA and is waiting on responses from YP TSC
members on release readiness. It had more issues that would be ideal but
most were relatively minor and are being worked upon, several with known
causes now with fixes in master. As such its likely to be released.
*   Stephen is recovering from the accident and will now respond to
emails. We're pleased to have him back and wish him a continued speedy
recovery!
*   Mailing lists are proving to be a tricky subject. Some people are
having trouble with emails not making it to the lists which we recognise is
a serious issue. Equally, our groups.io plan isn't proving workable without
major user visible change due to the current domain structure we have. It is
being worked on as a priority to find a way forward.
*   We have a new "newcomer" bug category which are bugs suited to
someone new to the project. These can be seen here:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs
*   We're grateful to Sandy, WindRiver and Michael for helping get
patchtest back into operation. Its tests are looking like they could do with
a little improvement but it is catching some issues and great to see
progress with it again.
*   During M2 Richard plans to look into our options for changing
runqueue to better support more advanced sstate usage. This may have an
impact on how quickly patches merge as the work there is involved and needs
focus.
*   We'd like to remind people that where test suites exist, we'd
appreciate it if people would run them before they send patches, e.g.
"oe-selftest -r devtool" or "oe-selftest -r wic".

 

Planned Releases for YP 2.8:

*   M1 is built and out of QA
*   M2 Cutoff 14th July
*   M2 Release 26th July
*   M3 Cutoff (Feature Freeze) 25th Aug
*   M3 Release 6th Sept
*   M4 Cutoff 30th Sept
*   2.8 (M4) Final Release 25th Oct

 

Planned upcoming dot releases:

*   YP 2.7.1 (Warrior) is planned for build imminently now that 2.8 M1
is done
*   YP 2.6.3 (Thud) is intended for build after 2.7.1 is complete and
before 2.8 M2

 

Tracking Metrics:

*   WDD 2479 (last week 2478) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1511 (last week 1507)
*   Patches in the Pending State: 641 (43%) [last week 641 (43%)]

 

Key Status Links for YP:

 
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Status

 
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedule

 
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Features

 

The Status reports are now stored on the wiki at:

https://wiki.yoctoproject.org/wiki/Weekly_Status

 

[If anyone has suggestions for other information you'd like to see on this
weekly status update, let us know!]

 

Thanks,

 

Stephen K. Jolley

Yocto Project Project Manager

*Cell:(208) 244-4460

* Email:   
sjolley.yp...@gmail.com

 

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


[OE-core] [PATCH 1/1] linux-yocto: Add SCSI support when ptest is in DISTRO_FEATURES

2019-06-18 Thread Mariano López
The scsi_debug module can't be built in some architectures as they have
SCSI support disabled by default. This patch will enable SCSI support as
well as the scsi_debug module when ptest is in DISTRO_FEATURES.

Signed-off-by: Mariano López 
---
 meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb | 5 -
 meta/recipes-kernel/linux/linux-yocto-rt_5.0.bb  | 5 -
 meta/recipes-kernel/linux/linux-yocto_4.19.bb| 5 -
 meta/recipes-kernel/linux/linux-yocto_5.0.bb | 5 -
 4 files changed, 16 insertions(+), 4 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb
index 0836dc7ea0..e6c8ee320c 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb
@@ -41,4 +41,7 @@ KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
 KERNEL_FEATURES_append_qemuall=" cfg/virtio.scc"
 KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
 KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc cfg/paravirt_kvm.scc"
-KERNEL_FEATURES_append = "${@bb.utils.contains("DISTRO_FEATURES", "ptest", " 
features/scsi/scsi-debug.scc", "" ,d)}"
+KERNEL_FEATURES_append = "${@bb.utils.contains("DISTRO_FEATURES", "ptest", "\
+features/scsi/scsi.scc \
+features/scsi/scsi-debug.scc \
+ ","" ,d)}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.0.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_5.0.bb
index b5e415f935..06fd642506 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.0.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.0.bb
@@ -41,4 +41,7 @@ KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
 KERNEL_FEATURES_append_qemuall=" cfg/virtio.scc"
 KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
 KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc cfg/paravirt_kvm.scc"
-KERNEL_FEATURES_append = "${@bb.utils.contains("DISTRO_FEATURES", "ptest", " 
features/scsi/scsi-debug.scc", "" ,d)}"
+KERNEL_FEATURES_append = "${@bb.utils.contains("DISTRO_FEATURES", "ptest", "\
+features/scsi/scsi.scc \
+features/scsi/scsi-debug.scc \
+ ","" ,d)}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.19.bb 
b/meta/recipes-kernel/linux/linux-yocto_4.19.bb
index cda4ecf89e..65b4f68c3d 100644
--- a/meta/recipes-kernel/linux/linux-yocto_4.19.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_4.19.bb
@@ -47,4 +47,7 @@ KERNEL_FEATURES_append_qemuall=" cfg/virtio.scc"
 KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
 KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc cfg/paravirt_kvm.scc"
 KERNEL_FEATURES_append = " ${@bb.utils.contains("TUNE_FEATURES", "mx32", " 
cfg/x32.scc", "" ,d)}"
-KERNEL_FEATURES_append = " ${@bb.utils.contains("DISTRO_FEATURES", "ptest", " 
features/scsi/scsi-debug.scc", "" ,d)}"
+KERNEL_FEATURES_append = "${@bb.utils.contains("DISTRO_FEATURES", "ptest", "\
+features/scsi/scsi.scc \
+features/scsi/scsi-debug.scc \
+ ","" ,d)}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.0.bb 
b/meta/recipes-kernel/linux/linux-yocto_5.0.bb
index 8aec315084..ac813a8663 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.0.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.0.bb
@@ -50,4 +50,7 @@ KERNEL_FEATURES_append_qemuall=" cfg/virtio.scc"
 KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
 KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc cfg/paravirt_kvm.scc"
 KERNEL_FEATURES_append = " ${@bb.utils.contains("TUNE_FEATURES", "mx32", " 
cfg/x32.scc", "" ,d)}"
-KERNEL_FEATURES_append = " ${@bb.utils.contains("DISTRO_FEATURES", "ptest", " 
features/scsi/scsi-debug.scc", "" ,d)}"
+KERNEL_FEATURES_append = "${@bb.utils.contains("DISTRO_FEATURES", "ptest", "\
+features/scsi/scsi.scc \
+features/scsi/scsi-debug.scc \
+ ","" ,d)}"
-- 
2.21.0

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


[OE-core] [PATCH 0/1] linux-yocto: Add SCSI support when ptest is in DISTRO_FEATURES

2019-06-18 Thread Mariano López
Some architectures have SCSI support disabled by default and trying to
build the scsi_debug module will throw a warning, for a missing
dependency, when building the kernel. This patch will enable SCSI
support for all architectures when ptest is listed in the
DISTRO_FEATURES.

The following changes since commit 111b7173fee69fe8b01ec2fa6999713841326537:

  dev-manual: Fixed grammar issue. (2019-06-18 11:29:23 +0100)

are available in the Git repository at:

  git://github.com/justanotherboy/poky bug13301p3
  https://github.com/justanotherboy/poky/tree/bug13301p3

Mariano López (1):
  linux-yocto: Add SCSI support when ptest is in DISTRO_FEATURES

 meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb | 5 -
 meta/recipes-kernel/linux/linux-yocto-rt_5.0.bb  | 5 -
 meta/recipes-kernel/linux/linux-yocto_4.19.bb| 5 -
 meta/recipes-kernel/linux/linux-yocto_5.0.bb | 5 -
 4 files changed, 16 insertions(+), 4 deletions(-)

-- 
2.21.0

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


[OE-core] [PATCH v2] wireless-regdb: Add recipe

2019-06-18 Thread Adrian Bunk
Since wpa-supplicant is provided,
the database of permitted frequencies should also be provided.

wireless-regdb-static should be used with kernel >= 4.15.
wireless-regdb can be used with older kernels and is mostly
irrelevant here, but keeping it in meta-networking would
create needless recipe duplication.

This package was previously in meta-networking.

Signed-off-by: Adrian Bunk 

---
v2: remove empty packages that were generated by default
---
 meta/conf/distro/include/maintainers.inc  |  1 +
 .../packagegroups/packagegroup-base.bb|  1 +
 .../wireless-regdb_2019.06.03.bb  | 44 +++
 3 files changed, 46 insertions(+)
 create mode 100644 
meta/recipes-kernel/wireless-regdb/wireless-regdb_2019.06.03.bb

diff --git a/meta/conf/distro/include/maintainers.inc 
b/meta/conf/distro/include/maintainers.inc
index 0bc7060718..c33bd8e068 100644
--- a/meta/conf/distro/include/maintainers.inc
+++ b/meta/conf/distro/include/maintainers.inc
@@ -728,6 +728,7 @@ RECIPE_MAINTAINER_pn-weston-init = "Denys Dmytriyenko 
"
 RECIPE_MAINTAINER_pn-wget = "Yi Zhao "
 RECIPE_MAINTAINER_pn-which = "Anuj Mittal "
 RECIPE_MAINTAINER_pn-wic-tools = "Anuj Mittal "
+RECIPE_MAINTAINER_pn-wireless-regdb = "Adrian Bunk "
 RECIPE_MAINTAINER_pn-wpa-supplicant = "Changhyeok Bae 
"
 RECIPE_MAINTAINER_pn-x11perf = "Armin Kuster "
 RECIPE_MAINTAINER_pn-x264 = "Anuj Mittal "
diff --git a/meta/recipes-core/packagegroups/packagegroup-base.bb 
b/meta/recipes-core/packagegroups/packagegroup-base.bb
index cae704aa24..d05403635c 100644
--- a/meta/recipes-core/packagegroups/packagegroup-base.bb
+++ b/meta/recipes-core/packagegroups/packagegroup-base.bb
@@ -271,6 +271,7 @@ RRECOMMENDS_packagegroup-base-ipsec = "\
 SUMMARY_packagegroup-base-wifi = "WiFi support"
 RDEPENDS_packagegroup-base-wifi = "\
 iw \
+wireless-regdb-static \
 wpa-supplicant"
 
 RRECOMMENDS_packagegroup-base-wifi = "\
diff --git a/meta/recipes-kernel/wireless-regdb/wireless-regdb_2019.06.03.bb 
b/meta/recipes-kernel/wireless-regdb/wireless-regdb_2019.06.03.bb
new file mode 100644
index 00..9076d94601
--- /dev/null
+++ b/meta/recipes-kernel/wireless-regdb/wireless-regdb_2019.06.03.bb
@@ -0,0 +1,44 @@
+SUMMARY = "Wireless Central Regulatory Domain Database"
+HOMEPAGE = "http://wireless.kernel.org/en/developers/Regulatory/CRDA";
+SECTION = "net"
+LICENSE = "ISC"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=07c4f6dea3845b02a18dc00c8c87699c"
+
+SRC_URI = "https://www.kernel.org/pub/software/network/${BPN}/${BP}.tar.xz";
+SRC_URI[md5sum] = "4b5ba3f089db7fdb7b9daae6a7c1f2cb"
+SRC_URI[sha256sum] = 
"cd917ed86b63ce8d93947979f1f18948f03a4ac0ad89ec25227b36ac00dc54bf"
+
+inherit bin_package allarch
+
+do_install() {
+install -d -m0755 ${D}${nonarch_libdir}/crda
+install -d -m0755 ${D}${sysconfdir}/wireless-regdb/pubkeys
+install -m 0644 regulatory.bin ${D}${nonarch_libdir}/crda/regulatory.bin
+install -m 0644 sforshee.key.pub.pem 
${D}${sysconfdir}/wireless-regdb/pubkeys/sforshee.key.pub.pem
+
+install -m 0644 -D regulatory.db 
${D}${nonarch_base_libdir}/firmware/regulatory.db
+install -m 0644 regulatory.db.p7s 
${D}${nonarch_base_libdir}/firmware/regulatory.db.p7s
+}
+
+# Install static regulatory DB in /lib/firmware for kernel to load.
+# This requires Linux kernel >= v4.15.
+# For kernel <= v4.14, inherit the kernel_wireless_regdb.bbclass
+# (in meta-networking) in kernel's recipe.
+PACKAGES = "${PN}-static ${PN}"
+RCONFLICTS_${PN} = "${PN}-static"
+
+FILES_${PN}-static = " \
+${nonarch_base_libdir}/firmware/regulatory.db \
+${nonarch_base_libdir}/firmware/regulatory.db.p7s \
+"
+
+# Native users might want to use the source of regulatory DB.
+# This is for example used by Linux kernel <= v4.14 and
+# kernel_wireless_regdb.bbclass in meta-networking.
+do_install_append_class-native() {
+install -m 0644 -D db.txt ${D}${libdir}/crda/db.txt
+}
+
+RSUGGESTS_${PN} = "crda"
+
+BBCLASSEXTEND = "native"
-- 
2.17.1

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


Re: [OE-core] [PATCH] wireless-regdb: Add recipe

2019-06-18 Thread Adrian Bunk
On Tue, Jun 18, 2019 at 02:22:31PM +0100, Richard Purdie wrote:
> On Tue, 2019-06-18 at 13:34 +0100, Richard Purdie wrote:
> > On Tue, 2019-06-18 at 09:11 +0300, Adrian Bunk wrote:
> > > Since wpa-supplicant is provided,
> > > the database of permitted frequencies should also be provided.
> > > 
> > > wireless-regdb-static should be used with kernel >= 4.15.
> > > wireless-regdb can be used with older kernels and is mostly
> > > irrelevant here, but keeping it in meta-networking would
> > > create needless recipe duplication.
> > > 
> > > This package was previously in meta-networking.
> > > 
> > > Signed-off-by: Adrian Bunk 
> > > ---
> > >  meta/conf/distro/include/maintainers.inc  |  1 +
> > >  .../packagegroups/packagegroup-base.bb|  1 +
> > >  .../wireless-regdb_2019.06.03.bb  | 44
> > > +++
> > >  3 files changed, 46 insertions(+)
> > >  create mode 100644 meta/recipes-kernel/wireless-regdb/wireless-
> > > regdb_2019.06.03.bb
> > 
> > This seems to break deb rootfs construction:
> > 
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/50/builds/712
> 
> opkg as well:
> 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/76/builds/716
> 
> basically nothing provides wireless-regdb but wireless-regdb depends on
> it.

The root problem is that the empty wireless-regdb-dev exists at all,
I'll send a v2 removing it.

> Cheers,
> 
> Richard

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

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


[OE-core] ✗ patchtest: failure for serf: cleanup recipe (rev2)

2019-06-18 Thread Patchwork
== Series Details ==

Series: serf: cleanup recipe (rev2)
Revision: 2
URL   : https://patchwork.openembedded.org/series/18127/
State : failure

== Summary ==


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



* Issue A patch file has been added, but does not have a 
Signed-off-by tag [test_signed_off_by_presence] 
  Suggested fixSign off the added patch file 
(meta/recipes-support/serf/serf/SConstruct.stop.creating.directories.without.sandbox-install.prefix.patch)

* Issue Added patch file is missing Upstream-Status in the header 
[test_upstream_status_presence_format] 
  Suggested fixAdd Upstream-Status:  to the header of 
meta/recipes-support/serf/serf/SConstruct.stop.creating.directories.without.sandbox-install.prefix.patch
  Standard format  Upstream-Status: 
  Valid status Pending, Accepted, Backport, Denied, Inappropriate [reason], 
Submitted [where]



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

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

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


Re: [OE-core] [PATCH] serf: stop scons trying to create directories in hosts rootfs

2019-06-18 Thread Burton, Ross
No S-o-b in the patch, but more importantly no Upstream-Status.  Have
you reported this upstream?  Or compared what we're doing to what
other distros that package serf do?

Ross

On Tue, 18 Jun 2019 at 20:09, Martin Jansa  wrote:
>
> * since 1522f09a4d serf: cleanup recipe
>   serf.do_install fails in builds with multilib enabled (with
>   libdir=/usr/lib64 on host where /usr/lib64 doesn't exist)
>
> DEBUG: Executing shell function do_install
> scons: Reading SConscript files ...
> PermissionError: [Errno 13] Permission denied: '/usr/lib64':
>   File 
> "TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/serf-1.3.9/SConstruct",
>  line 158:
> ENV = os.environ,
>   File 
> "/TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/recipe-sysroot-native/usr/bin/../../usr/lib/python3.7/site-packages/SCons/Environment.py",
>  line 965:
> variables.Update(self)
>   File 
> "/TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/recipe-sysroot-native/usr/bin/../../usr/lib/python3.7/site-packages/SCons/Variables/__init__.py",
>  line 227:
> option.validator(option.key, env.subst('${%s}'%option.key), env)
>   File 
> "TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/serf-1.3.9/SConstruct",
>  line 60:
> return PathVariable.PathIsDirCreate(key, val, env)
>   File 
> "/TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/recipe-sysroot-native/usr/bin/../../usr/lib/python3.7/site-packages/SCons/Variables/PathVariable.py",
>  line 101:
> os.makedirs(val)
>   File 
> "TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/recipe-sysroot-native/usr/lib/python3.7/os.py",
>  line 221:
> mkdir(name, mode)
> ERROR: scons install execution failed.
>
> * I don't know how exactly --install-sandbox is supposed to work but
>   in this case it's trying to mkdir /usr/lib64 on the host rootfs
>   which is clearly wrong and if I set LIBDIR together with
>   --install-sandbox then the install paths are prefixed with $D twice
>   in some cases (not for includedir and empty libdir at the end).
>   So in the end I think it was an issue caused by the custom path
>   validator in serf's SConstruct, removing that stops touching host
>   and the installed paths (including the paths inside libserf*.pc)
>   look correct
>
> Signed-off-by: Martin Jansa 
> ---
>  ...ories.without.sandbox-install.prefix.patch | 34 +++
>  meta/recipes-support/serf/serf_1.3.9.bb   |  1 +
>  2 files changed, 35 insertions(+)
>  create mode 100644 
> meta/recipes-support/serf/serf/SConstruct.stop.creating.directories.without.sandbox-install.prefix.patch
>
> diff --git 
> a/meta/recipes-support/serf/serf/SConstruct.stop.creating.directories.without.sandbox-install.prefix.patch
>  
> b/meta/recipes-support/serf/serf/SConstruct.stop.creating.directories.without.sandbox-install.prefix.patch
> new file mode 100644
> index 00..bfb2f5a2aa
> --- /dev/null
> +++ 
> b/meta/recipes-support/serf/serf/SConstruct.stop.creating.directories.without.sandbox-install.prefix.patch
> @@ -0,0 +1,34 @@
> +--- ../1.3.9-r0-bad-double/serf-1.3.9/SConstruct   2019-06-18 
> 15:49:19.968961108 +
>  serf-1.3.9/SConstruct  2019-06-18 18:53:21.412337151 +
> +@@ -51,17 +51,6 @@
> + """
> + return (key, '%s' % (help), default, None, lambda val: _converter(val))
> +
> +-# Custom path validator, creates directory when a specified option is set.
> +-# To be used to ensure a PREFIX directory is only created when installing.
> +-def createPathIsDirCreateWithTarget(target):
> +-  def my_validator(key, val, env):
> +-build_targets = (map(str, BUILD_TARGETS))
> +-if target in build_targets:
> +-  return PathVariable.PathIsDirCreate(key, val, env)
> +-else:
> +-  return PathVariable.PathAccept(key, val, env)
> +-  return my_validator
> +-
> + # default directories
> + if sys.platform == 'win32':
> +   default_incdir='..'
> +@@ -77,11 +66,11 @@
> +   PathVariable('PREFIX',
> +'Directory to install under',
> +default_prefix,
> +-   createPathIsDirCreateWithTarget('install')),
> ++   PathVariable.PathAccept),
> +   PathVariable('LIBDIR',
> +'Directory to install architecture dependent libraries 
> under',
> +default_libdir,
> +-   createPathIsDirCreateWithTarget('install')),
> ++   PathVariable.PathAccept),
> +   PathVariable('APR',
> +"Path to apr-1-config, or to APR's install area",
> +default_incdir,
> diff --git a/meta/recipes-support/serf/serf_1.3.9.bb 
> b/meta/recipes-support/serf/serf_1.3.9.bb
> index 92cd5ca061..25ccd79e00 100644
> --- a/meta/recipes-support/serf/serf_1.3.9.bb
> +++ b/meta/recipes-support/serf/serf_1.3.9.bb
> @@ -6,6 +6,7 @@ SRC_URI = "${APACHE_MIRROR}/${BPN}/${BPN}-${PV}.tar.bz2 \
> file://0002-SConstruct-Fix-path-quoting-for-.def-generator.patch \
> file://0003-gen_def.patch \
> 
> file://0004-Follow-up-

Re: [OE-core] [PATCH] serf: stop scons trying to create directories in hosts rootfs

2019-06-18 Thread Martin Jansa
oe-core likes to mix them :)

On Tue, Jun 18, 2019 at 9:14 PM Khem Raj  wrote:

> On Tue, Jun 18, 2019 at 12:09 PM Martin Jansa 
> wrote:
> >
> > * since 1522f09a4d serf: cleanup recipe
> >   serf.do_install fails in builds with multilib enabled (with
> >   libdir=/usr/lib64 on host where /usr/lib64 doesn't exist)
> >
> > DEBUG: Executing shell function do_install
> > scons: Reading SConscript files ...
> > PermissionError: [Errno 13] Permission denied: '/usr/lib64':
> >   File
> "TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/serf-1.3.9/SConstruct",
> line 158:
> > ENV = os.environ,
> >   File
> "/TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/recipe-sysroot-native/usr/bin/../../usr/lib/python3.7/site-packages/SCons/Environment.py",
> line 965:
> > variables.Update(self)
> >   File
> "/TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/recipe-sysroot-native/usr/bin/../../usr/lib/python3.7/site-packages/SCons/Variables/__init__.py",
> line 227:
> > option.validator(option.key, env.subst('${%s}'%option.key), env)
> >   File
> "TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/serf-1.3.9/SConstruct",
> line 60:
> > return PathVariable.PathIsDirCreate(key, val, env)
> >   File
> "/TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/recipe-sysroot-native/usr/bin/../../usr/lib/python3.7/site-packages/SCons/Variables/PathVariable.py",
> line 101:
> > os.makedirs(val)
> >   File
> "TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/recipe-sysroot-native/usr/lib/python3.7/os.py",
> line 221:
> > mkdir(name, mode)
> > ERROR: scons install execution failed.
> >
> > * I don't know how exactly --install-sandbox is supposed to work but
> >   in this case it's trying to mkdir /usr/lib64 on the host rootfs
> >   which is clearly wrong and if I set LIBDIR together with
> >   --install-sandbox then the install paths are prefixed with $D twice
> >   in some cases (not for includedir and empty libdir at the end).
> >   So in the end I think it was an issue caused by the custom path
> >   validator in serf's SConstruct, removing that stops touching host
> >   and the installed paths (including the paths inside libserf*.pc)
> >   look correct
> >
> > Signed-off-by: Martin Jansa 
> > ---
> >  ...ories.without.sandbox-install.prefix.patch | 34 +++
> >  meta/recipes-support/serf/serf_1.3.9.bb   |  1 +
> >  2 files changed, 35 insertions(+)
> >  create mode 100644
> meta/recipes-support/serf/serf/SConstruct.stop.creating.directories.without.sandbox-install.prefix.patch
> >
> > diff --git
> a/meta/recipes-support/serf/serf/SConstruct.stop.creating.directories.without.sandbox-install.prefix.patch
> b/meta/recipes-support/serf/serf/SConstruct.stop.creating.directories.without.sandbox-install.prefix.patch
> > new file mode 100644
> > index 00..bfb2f5a2aa
> > --- /dev/null
> > +++
> b/meta/recipes-support/serf/serf/SConstruct.stop.creating.directories.without.sandbox-install.prefix.patch
> > @@ -0,0 +1,34 @@
> > +--- ../1.3.9-r0-bad-double/serf-1.3.9/SConstruct   2019-06-18
> 15:49:19.968961108 +
> >  serf-1.3.9/SConstruct  2019-06-18 18:53:21.412337151 +
> > +@@ -51,17 +51,6 @@
> > + """
> > + return (key, '%s' % (help), default, None, lambda val:
> _converter(val))
> > +
> > +-# Custom path validator, creates directory when a specified option is
> set.
> > +-# To be used to ensure a PREFIX directory is only created when
> installing.
> > +-def createPathIsDirCreateWithTarget(target):
> > +-  def my_validator(key, val, env):
> > +-build_targets = (map(str, BUILD_TARGETS))
> > +-if target in build_targets:
> > +-  return PathVariable.PathIsDirCreate(key, val, env)
> > +-else:
> > +-  return PathVariable.PathAccept(key, val, env)
> > +-  return my_validator
> > +-
> > + # default directories
> > + if sys.platform == 'win32':
> > +   default_incdir='..'
> > +@@ -77,11 +66,11 @@
> > +   PathVariable('PREFIX',
> > +'Directory to install under',
> > +default_prefix,
> > +-   createPathIsDirCreateWithTarget('install')),
> > ++   PathVariable.PathAccept),
> > +   PathVariable('LIBDIR',
> > +'Directory to install architecture dependent libraries
> under',
> > +default_libdir,
> > +-   createPathIsDirCreateWithTarget('install')),
> > ++   PathVariable.PathAccept),
> > +   PathVariable('APR',
> > +"Path to apr-1-config, or to APR's install area",
> > +default_incdir,
> > diff --git a/meta/recipes-support/serf/serf_1.3.9.bb
> b/meta/recipes-support/serf/serf_1.3.9.bb
> > index 92cd5ca061..25ccd79e00 100644
> > --- a/meta/recipes-support/serf/serf_1.3.9.bb
> > +++ b/meta/recipes-support/serf/serf_1.3.9.bb
> > @@ -6,6 +6,7 @@ SRC_URI = "${APACHE_MIRROR}/${BPN}/${BPN}-${PV}.tar.bz2 \
> >
>  file://0002-SConstruct-Fix-path-quoting-for-.def-generator.patch \
> > file://0003-

Re: [OE-core] [PATCH] serf: stop scons trying to create directories in hosts rootfs

2019-06-18 Thread Khem Raj
On Tue, Jun 18, 2019 at 12:09 PM Martin Jansa  wrote:
>
> * since 1522f09a4d serf: cleanup recipe
>   serf.do_install fails in builds with multilib enabled (with
>   libdir=/usr/lib64 on host where /usr/lib64 doesn't exist)
>
> DEBUG: Executing shell function do_install
> scons: Reading SConscript files ...
> PermissionError: [Errno 13] Permission denied: '/usr/lib64':
>   File 
> "TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/serf-1.3.9/SConstruct",
>  line 158:
> ENV = os.environ,
>   File 
> "/TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/recipe-sysroot-native/usr/bin/../../usr/lib/python3.7/site-packages/SCons/Environment.py",
>  line 965:
> variables.Update(self)
>   File 
> "/TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/recipe-sysroot-native/usr/bin/../../usr/lib/python3.7/site-packages/SCons/Variables/__init__.py",
>  line 227:
> option.validator(option.key, env.subst('${%s}'%option.key), env)
>   File 
> "TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/serf-1.3.9/SConstruct",
>  line 60:
> return PathVariable.PathIsDirCreate(key, val, env)
>   File 
> "/TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/recipe-sysroot-native/usr/bin/../../usr/lib/python3.7/site-packages/SCons/Variables/PathVariable.py",
>  line 101:
> os.makedirs(val)
>   File 
> "TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/recipe-sysroot-native/usr/lib/python3.7/os.py",
>  line 221:
> mkdir(name, mode)
> ERROR: scons install execution failed.
>
> * I don't know how exactly --install-sandbox is supposed to work but
>   in this case it's trying to mkdir /usr/lib64 on the host rootfs
>   which is clearly wrong and if I set LIBDIR together with
>   --install-sandbox then the install paths are prefixed with $D twice
>   in some cases (not for includedir and empty libdir at the end).
>   So in the end I think it was an issue caused by the custom path
>   validator in serf's SConstruct, removing that stops touching host
>   and the installed paths (including the paths inside libserf*.pc)
>   look correct
>
> Signed-off-by: Martin Jansa 
> ---
>  ...ories.without.sandbox-install.prefix.patch | 34 +++
>  meta/recipes-support/serf/serf_1.3.9.bb   |  1 +
>  2 files changed, 35 insertions(+)
>  create mode 100644 
> meta/recipes-support/serf/serf/SConstruct.stop.creating.directories.without.sandbox-install.prefix.patch
>
> diff --git 
> a/meta/recipes-support/serf/serf/SConstruct.stop.creating.directories.without.sandbox-install.prefix.patch
>  
> b/meta/recipes-support/serf/serf/SConstruct.stop.creating.directories.without.sandbox-install.prefix.patch
> new file mode 100644
> index 00..bfb2f5a2aa
> --- /dev/null
> +++ 
> b/meta/recipes-support/serf/serf/SConstruct.stop.creating.directories.without.sandbox-install.prefix.patch
> @@ -0,0 +1,34 @@
> +--- ../1.3.9-r0-bad-double/serf-1.3.9/SConstruct   2019-06-18 
> 15:49:19.968961108 +
>  serf-1.3.9/SConstruct  2019-06-18 18:53:21.412337151 +
> +@@ -51,17 +51,6 @@
> + """
> + return (key, '%s' % (help), default, None, lambda val: _converter(val))
> +
> +-# Custom path validator, creates directory when a specified option is set.
> +-# To be used to ensure a PREFIX directory is only created when installing.
> +-def createPathIsDirCreateWithTarget(target):
> +-  def my_validator(key, val, env):
> +-build_targets = (map(str, BUILD_TARGETS))
> +-if target in build_targets:
> +-  return PathVariable.PathIsDirCreate(key, val, env)
> +-else:
> +-  return PathVariable.PathAccept(key, val, env)
> +-  return my_validator
> +-
> + # default directories
> + if sys.platform == 'win32':
> +   default_incdir='..'
> +@@ -77,11 +66,11 @@
> +   PathVariable('PREFIX',
> +'Directory to install under',
> +default_prefix,
> +-   createPathIsDirCreateWithTarget('install')),
> ++   PathVariable.PathAccept),
> +   PathVariable('LIBDIR',
> +'Directory to install architecture dependent libraries 
> under',
> +default_libdir,
> +-   createPathIsDirCreateWithTarget('install')),
> ++   PathVariable.PathAccept),
> +   PathVariable('APR',
> +"Path to apr-1-config, or to APR's install area",
> +default_incdir,
> diff --git a/meta/recipes-support/serf/serf_1.3.9.bb 
> b/meta/recipes-support/serf/serf_1.3.9.bb
> index 92cd5ca061..25ccd79e00 100644
> --- a/meta/recipes-support/serf/serf_1.3.9.bb
> +++ b/meta/recipes-support/serf/serf_1.3.9.bb
> @@ -6,6 +6,7 @@ SRC_URI = "${APACHE_MIRROR}/${BPN}/${BPN}-${PV}.tar.bz2 \
> file://0002-SConstruct-Fix-path-quoting-for-.def-generator.patch \
> file://0003-gen_def.patch \
> 
> file://0004-Follow-up-to-r1811083-fix-building-with-scons-3.0.0-.patch \
> +
> file://SConstruct.stop.creating.directories.without.sandbox-install.prefix.patch
>  \

tabs or spaces mismatch I gu

[OE-core] [PATCH] serf: stop scons trying to create directories in hosts rootfs

2019-06-18 Thread Martin Jansa
* since 1522f09a4d serf: cleanup recipe
  serf.do_install fails in builds with multilib enabled (with
  libdir=/usr/lib64 on host where /usr/lib64 doesn't exist)

DEBUG: Executing shell function do_install
scons: Reading SConscript files ...
PermissionError: [Errno 13] Permission denied: '/usr/lib64':
  File 
"TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/serf-1.3.9/SConstruct", 
line 158:
ENV = os.environ,
  File 
"/TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/recipe-sysroot-native/usr/bin/../../usr/lib/python3.7/site-packages/SCons/Environment.py",
 line 965:
variables.Update(self)
  File 
"/TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/recipe-sysroot-native/usr/bin/../../usr/lib/python3.7/site-packages/SCons/Variables/__init__.py",
 line 227:
option.validator(option.key, env.subst('${%s}'%option.key), env)
  File 
"TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/serf-1.3.9/SConstruct", 
line 60:
return PathVariable.PathIsDirCreate(key, val, env)
  File 
"/TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/recipe-sysroot-native/usr/bin/../../usr/lib/python3.7/site-packages/SCons/Variables/PathVariable.py",
 line 101:
os.makedirs(val)
  File 
"TOPDIR/BUILD/work/qemux86-signage-linux/serf/1.3.9-r0/recipe-sysroot-native/usr/lib/python3.7/os.py",
 line 221:
mkdir(name, mode)
ERROR: scons install execution failed.

* I don't know how exactly --install-sandbox is supposed to work but
  in this case it's trying to mkdir /usr/lib64 on the host rootfs
  which is clearly wrong and if I set LIBDIR together with
  --install-sandbox then the install paths are prefixed with $D twice
  in some cases (not for includedir and empty libdir at the end).
  So in the end I think it was an issue caused by the custom path
  validator in serf's SConstruct, removing that stops touching host
  and the installed paths (including the paths inside libserf*.pc)
  look correct

Signed-off-by: Martin Jansa 
---
 ...ories.without.sandbox-install.prefix.patch | 34 +++
 meta/recipes-support/serf/serf_1.3.9.bb   |  1 +
 2 files changed, 35 insertions(+)
 create mode 100644 
meta/recipes-support/serf/serf/SConstruct.stop.creating.directories.without.sandbox-install.prefix.patch

diff --git 
a/meta/recipes-support/serf/serf/SConstruct.stop.creating.directories.without.sandbox-install.prefix.patch
 
b/meta/recipes-support/serf/serf/SConstruct.stop.creating.directories.without.sandbox-install.prefix.patch
new file mode 100644
index 00..bfb2f5a2aa
--- /dev/null
+++ 
b/meta/recipes-support/serf/serf/SConstruct.stop.creating.directories.without.sandbox-install.prefix.patch
@@ -0,0 +1,34 @@
+--- ../1.3.9-r0-bad-double/serf-1.3.9/SConstruct   2019-06-18 
15:49:19.968961108 +
 serf-1.3.9/SConstruct  2019-06-18 18:53:21.412337151 +
+@@ -51,17 +51,6 @@
+ """
+ return (key, '%s' % (help), default, None, lambda val: _converter(val))
+ 
+-# Custom path validator, creates directory when a specified option is set.
+-# To be used to ensure a PREFIX directory is only created when installing.
+-def createPathIsDirCreateWithTarget(target):
+-  def my_validator(key, val, env):
+-build_targets = (map(str, BUILD_TARGETS))
+-if target in build_targets:
+-  return PathVariable.PathIsDirCreate(key, val, env)
+-else:
+-  return PathVariable.PathAccept(key, val, env)
+-  return my_validator
+-
+ # default directories
+ if sys.platform == 'win32':
+   default_incdir='..'
+@@ -77,11 +66,11 @@
+   PathVariable('PREFIX',
+'Directory to install under',
+default_prefix,
+-   createPathIsDirCreateWithTarget('install')),
++   PathVariable.PathAccept),
+   PathVariable('LIBDIR',
+'Directory to install architecture dependent libraries under',
+default_libdir,
+-   createPathIsDirCreateWithTarget('install')),
++   PathVariable.PathAccept),
+   PathVariable('APR',
+"Path to apr-1-config, or to APR's install area",
+default_incdir,
diff --git a/meta/recipes-support/serf/serf_1.3.9.bb 
b/meta/recipes-support/serf/serf_1.3.9.bb
index 92cd5ca061..25ccd79e00 100644
--- a/meta/recipes-support/serf/serf_1.3.9.bb
+++ b/meta/recipes-support/serf/serf_1.3.9.bb
@@ -6,6 +6,7 @@ SRC_URI = "${APACHE_MIRROR}/${BPN}/${BPN}-${PV}.tar.bz2 \
file://0002-SConstruct-Fix-path-quoting-for-.def-generator.patch \
file://0003-gen_def.patch \

file://0004-Follow-up-to-r1811083-fix-building-with-scons-3.0.0-.patch \
+
file://SConstruct.stop.creating.directories.without.sandbox-install.prefix.patch
 \
"
 
 SRC_URI[md5sum] = "370a6340ff20366ab088012cd13f2b57"
-- 
2.17.1

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


Re: [OE-core] [PATCH 3/4] linux-yocto: Mark qemuriscv64 as compatible

2019-06-18 Thread Bruce Ashfield
On Tue, Jun 18, 2019 at 12:03 PM Khem Raj  wrote:
>
> On Mon, Jun 17, 2019 at 8:44 PM Bruce Ashfield  
> wrote:
> >
> > On Mon, Jun 17, 2019 at 6:04 PM Alistair Francis
> >  wrote:
> > >
> > > Signed-off-by: Alistair Francis 
> > > ---
> > >  meta/recipes-kernel/linux/linux-yocto_5.0.bb | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/meta/recipes-kernel/linux/linux-yocto_5.0.bb 
> > > b/meta/recipes-kernel/linux/linux-yocto_5.0.bb
> > > index 8aec315084..a79d0b962d 100644
> > > --- a/meta/recipes-kernel/linux/linux-yocto_5.0.bb
> > > +++ b/meta/recipes-kernel/linux/linux-yocto_5.0.bb
> > > @@ -41,7 +41,7 @@ KCONF_BSP_AUDIT_LEVEL = "2"
> > >  KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
> > >  KERNEL_DEVICETREE_qemuarmv5 = "versatile-pb.dtb"
> > >
> > > -COMPATIBLE_MACHINE = 
> > > "qemuarm|qemuarmv5|qemuarm64|qemux86|qemuppc|qemumips|qemumips64|qemux86-64"
> > > +COMPATIBLE_MACHINE = 
> > > "qemuarm|qemuarmv5|qemuarm64|qemux86|qemuppc|qemumips|qemumips64|qemux86-64|qemuriscv64"
> >
> > What KBRANCH / SRCREV would this be building ? Unless it is something
> > that I'm building and booting, we shouldn't put it in the core recipe
> > as compatible until the SRCREV and KBRANCH are defined.
> >
>
> it needs to be master branch of repo since it needs no additional
> patches KBRANCH is not needed I suppose. and SRCREV can be picked from
> master branch.

Nope. That means /standard/base is the KBRANCH.  master is
reference only in the tree, and that's where SRCREV comes from as
well.
Regardless, it (the branch) should be set explicitly in the recipe if
we mark it as compatible, since the branch documents the details.

Bruce

>
> > Bruce
> >
> >
> > >
> > >  # Functionality flags
> > >  KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc"
> > > --
> > > 2.22.0
> > >
> > > --
> > > ___
> > > 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
> > - "Use the force Harry" - Gandalf, Star Trek II
> > --
> > ___
> > 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
- "Use the force Harry" - Gandalf, Star Trek II
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [meta-oe,v2] kernel-fitimage: introduce FIT_HASH_ALG

2019-06-18 Thread Richard Purdie
On Tue, 2019-06-18 at 08:53 -0700, Khem Raj wrote:
> On Tue, Jun 18, 2019 at 1:26 AM Luca Boccassi <
> luca.bocca...@gmail.com> wrote:
> > On Thu, 2017-11-02 at 16:48 +0100, Ayoub Zaki wrote:
> > > sanitize fitImage hash algorithm selection with FIT_HASH_ALG
> > > switch default hash algorithm from sha1 to sha256
> > > 
> > > Signed-off-by: Ayoub Zaki <
> > > ayoub.z...@embexus.com
> > > Acked-by: Denys Dmytriyenko <
> > > de...@ti.com
> > > ---
> > >  meta/classes/kernel-fitimage.bbclass | 13 -
> > >  1 file changed, 8 insertions(+), 5 deletions(-)
> > > 
> > > diff --git a/meta/classes/kernel-fitimage.bbclass
> > > b/meta/classes/kernel-fitimage.bbclass
> > > index 179185b..3cc3a33 100644
> > > --- a/meta/classes/kernel-fitimage.bbclass
> > > +++ b/meta/classes/kernel-fitimage.bbclass
> > > @@ -36,6 +36,9 @@ python __anonymous () {
> > >  # Options for the device tree compiler passed to mkimage '-D'
> > > feature:
> > >  UBOOT_MKIMAGE_DTCOPTS ??= ""
> > > 
> > > +# fitImage Hash Algo
> > > +FIT_HASH_ALG ?= "sha256"
> > > +
> > >  #
> > >  # Emit the fitImage ITS header
> > >  #
> > > @@ -95,7 +98,7 @@ EOF
> > >  # $4 ... Compression type
> > >  fitimage_emit_section_kernel() {
> > > 
> > > - kernel_csum="sha1"
> > > + kernel_csum="${FIT_HASH_ALG}"
> > > 
> > >   ENTRYPOINT=${UBOOT_ENTRYPOINT}
> > >   if [ -n "${UBOOT_ENTRYSYMBOL}" ]; then
> > > @@ -128,7 +131,7 @@ EOF
> > >  # $3 ... Path to DTB image
> > >  fitimage_emit_section_dtb() {
> > > 
> > > - dtb_csum="sha1"
> > > + dtb_csum="${FIT_HASH_ALG}"
> > > 
> > >   cat << EOF >> ${1}
> > >  fdt@${2} {
> > > @@ -152,7 +155,7 @@ EOF
> > >  # $3 ... Path to setup image
> > >  fitimage_emit_section_setup() {
> > > 
> > > - setup_csum="sha1"
> > > + setup_csum="${FIT_HASH_ALG}"
> > > 
> > >   cat << EOF >> ${1}
> > >  setup@${2} {
> > > @@ -179,7 +182,7 @@ EOF
> > >  # $3 ... Path to ramdisk image
> > >  fitimage_emit_section_ramdisk() {
> > > 
> > > - ramdisk_csum="sha1"
> > > + ramdisk_csum="${FIT_HASH_ALG}"
> > >   ramdisk_ctype="none"
> > >   ramdisk_loadline=""
> > >   ramdisk_entryline=""
> > > @@ -237,7 +240,7 @@ EOF
> > >  # $6 ... default flag
> > >  fitimage_emit_section_config() {
> > > 
> > > - conf_csum="sha1"
> > > + conf_csum="${FIT_HASH_ALG}"
> > >   if [ -n "${UBOOT_SIGN_ENABLE}" ] ; then
> > >   conf_sign_keyname="${UBOOT_SIGN_KEYNAME}"
> > >   fi
> > 
> > Hi,
> > 
> > Any update on this patch? It was acked almost 2 years ago.
> > 
> > It would be great to have a way to change the hashsum algorithm
> > when
> > building signed images.
> > 
> 
> I agree, but it would be good to resend this patch on top of current
> master

I managed to apply it to master so its in testing now.

My concerns about the lack of tests for this class are the main reason
patches here get held up.

Cheers,

Richard

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


Re: [OE-core] [PATCH 3/4] linux-yocto: Mark qemuriscv64 as compatible

2019-06-18 Thread Khem Raj
On Mon, Jun 17, 2019 at 8:44 PM Bruce Ashfield  wrote:
>
> On Mon, Jun 17, 2019 at 6:04 PM Alistair Francis
>  wrote:
> >
> > Signed-off-by: Alistair Francis 
> > ---
> >  meta/recipes-kernel/linux/linux-yocto_5.0.bb | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta/recipes-kernel/linux/linux-yocto_5.0.bb 
> > b/meta/recipes-kernel/linux/linux-yocto_5.0.bb
> > index 8aec315084..a79d0b962d 100644
> > --- a/meta/recipes-kernel/linux/linux-yocto_5.0.bb
> > +++ b/meta/recipes-kernel/linux/linux-yocto_5.0.bb
> > @@ -41,7 +41,7 @@ KCONF_BSP_AUDIT_LEVEL = "2"
> >  KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
> >  KERNEL_DEVICETREE_qemuarmv5 = "versatile-pb.dtb"
> >
> > -COMPATIBLE_MACHINE = 
> > "qemuarm|qemuarmv5|qemuarm64|qemux86|qemuppc|qemumips|qemumips64|qemux86-64"
> > +COMPATIBLE_MACHINE = 
> > "qemuarm|qemuarmv5|qemuarm64|qemux86|qemuppc|qemumips|qemumips64|qemux86-64|qemuriscv64"
>
> What KBRANCH / SRCREV would this be building ? Unless it is something
> that I'm building and booting, we shouldn't put it in the core recipe
> as compatible until the SRCREV and KBRANCH are defined.
>

it needs to be master branch of repo since it needs no additional
patches KBRANCH is not needed I suppose. and SRCREV can be picked from
master branch.

> Bruce
>
>
> >
> >  # Functionality flags
> >  KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc"
> > --
> > 2.22.0
> >
> > --
> > ___
> > 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
> - "Use the force Harry" - Gandalf, Star Trek II
> --
> ___
> 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] binconfig: don't try to fix up .la files

2019-06-18 Thread Khem Raj
On Tue, Jun 18, 2019 at 8:55 AM Burton, Ross  wrote:
>
> On Tue, 18 Jun 2019 at 16:51, Khem Raj  wrote:
> > while I agree, are there assumptions in the recipes using binconfig on this 
> > ?
> > especially packages outside oe-core ?
>
> I suspect that everyone is using remove-libtool, because that's one of
> the default inherits.
>

I see, that makes sense. So it was just redundant then

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


Re: [OE-core] [PATCH V3] gcc-runtime: fix C++ header mapping for n32/x32 tune

2019-06-18 Thread Khem Raj
On Tue, Jun 18, 2019 at 12:47 AM  wrote:
>
> From: Changqing Li 
>
> The SDK was unable to find the C++ header pieces correctly since it's
> using a generic compiler, not one specifically targeting the multilib
> vendor prefix and default tune.  This adds the right mapping to ensure
> SDKs work as expected. And fix problem in below configurations:
>
> multilib configuration 1:
> MACHINE="qemumips64"
> MULTILIBS ?= "multilib:lib32 multilib:libn32"
> DEFAULTTUNE_virtclass-multilib-lib32 ?= "mips"
> DEFAULTTUNE_virtclass-multilib-libn32 ?= "mips64-n32"
> MULTILIB_GLOBAL_VARIANTS_append = " libn32"
> require conf/multilib.conf
>
> ignoring nonexistent directory 
> "/sysroots/mips64-poky-linux/usr/include/c++/8.2.0/mips64-poky-linux/32
>
> multilib configuration 2:
> MACHINE="qemumips64"
> MULTILIBS = 'multilib:lib64 multilib:lib32'

machine is already 64bit so default lib config will be 64bit, what is
multilib:lib64 for here ?

> DEFAULTTUNE = 'mips64-n32'
> DEFAULTTUNE_virtclass-multilib-lib64 = 'mips64'
> DEFAULTTUNE_virtclass-multilib-lib32 = 'mips32r2'
> require conf/multilib.conf
>
> For this configuration:
> for target gcc-runtime, need to create symlink like mips64-poly-linux --> 
> mips64-poky-linux-gnu32
> for target lib64-gcc-runtime, need to create symlink like 
> mips64-poly-linux/32 --> mips64-pokymllib64-linux
> in order to avoid conflict during populate_sdk, create symlink for subfoler 
> bits/ext for target gcc-runtime,
> this is ugly, but seems no better way to cover all kinds of configuration.
>
> single lib configuration:
> MACHINE="qemumips64"
> DEFAULTTUNE = "mips64-n32"
>
> Signed-off-by: Changqing Li 
> ---
>  meta/recipes-devtools/gcc/gcc-runtime.inc | 29 +
>  1 file changed, 17 insertions(+), 12 deletions(-)
>
> diff --git a/meta/recipes-devtools/gcc/gcc-runtime.inc 
> b/meta/recipes-devtools/gcc/gcc-runtime.inc
> index 3d03d8e..ba767e1 100644
> --- a/meta/recipes-devtools/gcc/gcc-runtime.inc
> +++ b/meta/recipes-devtools/gcc/gcc-runtime.inc
> @@ -86,10 +86,6 @@ do_install () {
> if [ -d ${D}${infodir} ]; then
> rmdir --ignore-fail-on-non-empty -p ${D}${infodir}
> fi
> -   if [ "${TARGET_VENDOR_MULTILIB_ORIGINAL}" != "" -a "${TARGET_VENDOR}" 
> != "${TARGET_VENDOR_MULTILIB_ORIGINAL}" ]; then
> -   ln -s ${TARGET_SYS} 
> ${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR_MULTILIB_ORIGINAL}-${TARGET_OS}
> -   fi
> -
>  }
>
>  do_install_append_class-target () {
> @@ -98,20 +94,29 @@ do_install_append_class-target () {
> fi
>
> if [ "${TARGET_OS}" = "linux-gnun32" ]; then
> -   if [ "${MULTILIBS}" != "" ]; then
> -   mkdir 
> ${D}${includedir}/c++/${BINV}/${TARGET_ARCH}-pokymllib64-linux
> -   ln -s ../${TARGET_SYS} 
> ${D}${includedir}/c++/${BINV}/${TARGET_ARCH}-pokymllib64-linux/32
> +   if [ "${TARGET_VENDOR_MULTILIB_ORIGINAL}" != "" -a 
> "${TARGET_VENDOR}" != "${TARGET_VENDOR_MULTILIB_ORIGINAL}" ]; then
> +   mkdir 
> ${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR_MULTILIB_ORIGINAL}-linux
> +   ln -s ../${TARGET_SYS} 
> ${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR_MULTILIB_ORIGINAL}-linux/32
> +   elif [ "${MULTILIB_VARIANTS}" != "" ]; then
> +   mkdir 
> ${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR}-linux
> +   ln -s ../${TARGET_SYS} 
> ${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR}-linux/32
> else
> ln -s ${TARGET_SYS} 
> ${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR}-linux
> fi
> -   fi
> -   if [ "${TARGET_OS}" = "linux-gnux32" ]; then
> -   if [ "${MULTILIBS}" != "" ]; then
> -   mkdir 
> ${D}${includedir}/c++/${BINV}/${TARGET_ARCH}-poky-linux
> -   ln -s ../${TARGET_SYS} 
> ${D}${includedir}/c++/${BINV}/${TARGET_ARCH}-poky-linux/x32
> +   elif [ "${TARGET_OS}" = "linux-gnux32" ]; then
> +   if [ "${TARGET_VENDOR_MULTILIB_ORIGINAL}" != "" -a 
> "${TARGET_VENDOR}" != "${TARGET_VENDOR_MULTILIB_ORIGINAL}" ]; then
> +   mkdir 
> ${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR_MULTILIB_ORIGINAL}-linux
> +   ln -s ../${TARGET_SYS} 
> ${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR_MULTILIB_ORIGINAL}-linux/x32
> +   elif [ "${MULTILIB_VARIANTS}" != "" ]; then
> +   mkdir 
> ${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR}-linux
> +   ln -s ../${TARGET_SYS} 
> ${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR}-linux/32
> else
> ln -s ${TARGET_SYS} 
> ${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR}-linux
> fi
> +   elif [ "${

[OE-core] [PATCH V2] systat: systemd never enables the service

2019-06-18 Thread Stefano Babic
Even if SYSTEMD_AUTO_ENABLE is set to "enable", the service is never
activated by systemd. The cause is the postinst function in the recipe:

 pkg_postinst_${PN} () {
 if [ -n "$D" ]; then
 exit 0
 fi
 if [ -e /etc/init.d/populate-volatile.sh ]; then
 /etc/init.d/populate-volatile.sh update
 fi
 }

This generates with activated systemd the following postinst script:

set -e
if [ -n "$D" ]; then
exit 0
fi
if [ -e /etc/init.d/populate-volatile.sh ]; then
/etc/init.d/populate-volatile.sh update
fi
OPTS=""

if [ -n "$D" ]; then
OPTS="--root=$D"
fi

if type systemctl >/dev/null 2>/dev/null; then
if [ -z "$D" ]; then
systemctl daemon-reload
fi

systemctl $OPTS enable sysstat.service

if [ -z "$D" -a "enable" = "enable" ]; then
systemctl --no-block restart sysstat.service
fi
fi

Due to the exit statement, systemctl is never called and the service is
never enabled in rootfs.
Invert the logic for the check to let run the rest of postinst script.

Signed-off-by: Stefano Babic 
---

Changes since V1:
- rebase on current master

 meta/recipes-extended/sysstat/sysstat.inc | 11 +--
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/meta/recipes-extended/sysstat/sysstat.inc 
b/meta/recipes-extended/sysstat/sysstat.inc
index 6b21c6b8c1..4e29721666 100644
--- a/meta/recipes-extended/sysstat/sysstat.inc
+++ b/meta/recipes-extended/sysstat/sysstat.inc
@@ -52,12 +52,11 @@ do_install() {
 }
 
 pkg_postinst_${PN} () {
-if [ -n "$D" ]; then
-exit 0
-fi
-if [ -e /etc/init.d/populate-volatile.sh ]; then
-/etc/init.d/populate-volatile.sh update
-fi
+   if [  ! -n "$D" ]; then
+   if [ -e /etc/init.d/populate-volatile.sh ]; then
+   /etc/init.d/populate-volatile.sh update
+   fi
+   fi
 }
 
 FILES_${PN} += "${libdir}/sa ${systemd_system_unitdir}"
-- 
2.17.1

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


Re: [OE-core] [PATCH] binconfig: don't try to fix up .la files

2019-06-18 Thread Burton, Ross
On Tue, 18 Jun 2019 at 16:51, Khem Raj  wrote:
> while I agree, are there assumptions in the recipes using binconfig on this ?
> especially packages outside oe-core ?

I suspect that everyone is using remove-libtool, because that's one of
the default inherits.

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


Re: [OE-core] [meta-oe,v2] kernel-fitimage: introduce FIT_HASH_ALG

2019-06-18 Thread Khem Raj
On Tue, Jun 18, 2019 at 1:26 AM Luca Boccassi  wrote:
>
> On Thu, 2017-11-02 at 16:48 +0100, Ayoub Zaki wrote:
> > sanitize fitImage hash algorithm selection with FIT_HASH_ALG
> > switch default hash algorithm from sha1 to sha256
> >
> > Signed-off-by: Ayoub Zaki <
> > ayoub.z...@embexus.com
> > >
> > Acked-by: Denys Dmytriyenko <
> > de...@ti.com
> > >
> > ---
> >  meta/classes/kernel-fitimage.bbclass | 13 -
> >  1 file changed, 8 insertions(+), 5 deletions(-)
> >
> > diff --git a/meta/classes/kernel-fitimage.bbclass
> > b/meta/classes/kernel-fitimage.bbclass
> > index 179185b..3cc3a33 100644
> > --- a/meta/classes/kernel-fitimage.bbclass
> > +++ b/meta/classes/kernel-fitimage.bbclass
> > @@ -36,6 +36,9 @@ python __anonymous () {
> >  # Options for the device tree compiler passed to mkimage '-D'
> > feature:
> >  UBOOT_MKIMAGE_DTCOPTS ??= ""
> >
> > +# fitImage Hash Algo
> > +FIT_HASH_ALG ?= "sha256"
> > +
> >  #
> >  # Emit the fitImage ITS header
> >  #
> > @@ -95,7 +98,7 @@ EOF
> >  # $4 ... Compression type
> >  fitimage_emit_section_kernel() {
> >
> > - kernel_csum="sha1"
> > + kernel_csum="${FIT_HASH_ALG}"
> >
> >   ENTRYPOINT=${UBOOT_ENTRYPOINT}
> >   if [ -n "${UBOOT_ENTRYSYMBOL}" ]; then
> > @@ -128,7 +131,7 @@ EOF
> >  # $3 ... Path to DTB image
> >  fitimage_emit_section_dtb() {
> >
> > - dtb_csum="sha1"
> > + dtb_csum="${FIT_HASH_ALG}"
> >
> >   cat << EOF >> ${1}
> >  fdt@${2} {
> > @@ -152,7 +155,7 @@ EOF
> >  # $3 ... Path to setup image
> >  fitimage_emit_section_setup() {
> >
> > - setup_csum="sha1"
> > + setup_csum="${FIT_HASH_ALG}"
> >
> >   cat << EOF >> ${1}
> >  setup@${2} {
> > @@ -179,7 +182,7 @@ EOF
> >  # $3 ... Path to ramdisk image
> >  fitimage_emit_section_ramdisk() {
> >
> > - ramdisk_csum="sha1"
> > + ramdisk_csum="${FIT_HASH_ALG}"
> >   ramdisk_ctype="none"
> >   ramdisk_loadline=""
> >   ramdisk_entryline=""
> > @@ -237,7 +240,7 @@ EOF
> >  # $6 ... default flag
> >  fitimage_emit_section_config() {
> >
> > - conf_csum="sha1"
> > + conf_csum="${FIT_HASH_ALG}"
> >   if [ -n "${UBOOT_SIGN_ENABLE}" ] ; then
> >   conf_sign_keyname="${UBOOT_SIGN_KEYNAME}"
> >   fi
>
> Hi,
>
> Any update on this patch? It was acked almost 2 years ago.
>
> It would be great to have a way to change the hashsum algorithm when
> building signed images.
>

I agree, but it would be good to resend this patch on top of current master

> Thanks!
>
> --
> Kind regards,
> Luca Boccassi
>
> --
> ___
> 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] binconfig: don't try to fix up .la files

2019-06-18 Thread Khem Raj
On Tue, Jun 18, 2019 at 3:47 AM Ross Burton  wrote:
>
> If we're going to clean buildpaths from installed .la files then we should do 
> it
> globally, not in a class that only six recipes in oe-core use.
>

while I agree, are there assumptions in the recipes using binconfig on this ?
especially packages outside oe-core ?

> Signed-off-by: Ross Burton 
> ---
>  meta/classes/binconfig.bbclass | 9 -
>  1 file changed, 9 deletions(-)
>
> diff --git a/meta/classes/binconfig.bbclass b/meta/classes/binconfig.bbclass
> index 133b9537cf0..9112ed46085 100644
> --- a/meta/classes/binconfig.bbclass
> +++ b/meta/classes/binconfig.bbclass
> @@ -40,15 +40,6 @@ binconfig_package_preprocess () {
> -e 's:${STAGING_DIR_HOST}${prefix}:${prefix}:' \
>  $config
> done
> -   for lafile in `find ${PKGD} -type f -name "*.la"` ; do
> -   sed -i \
> -   -e 's:${STAGING_BASELIBDIR}:${base_libdir}:g;' \
> -   -e 's:${STAGING_LIBDIR}:${libdir}:g;' \
> -   -e 's:${STAGING_INCDIR}:${includedir}:g;' \
> -   -e 's:${STAGING_DATADIR}:${datadir}:' \
> -   -e 's:${STAGING_DIR_HOST}${prefix}:${prefix}:' \
> -   $lafile
> -   done
>  }
>
>  SYSROOT_PREPROCESS_FUNCS += "binconfig_sysroot_preprocess"
> --
> 2.11.0
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [AUH] lttng-ust: upgrading to 2.10.4 FAILED

2019-06-18 Thread Khem Raj
On Tue, Jun 18, 2019 at 4:10 AM Alexander Kanavin
 wrote:
>
> On Mon, 17 Jun 2019 at 17:26, Richard Purdie  wrote:
>>
>>
>> I think that perhaps:
>>
>> a) we should have a bug for this as devtool shouldn't be giving
>> tracebacks?
>
>
> Bug filed:
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13404
>
>>
>> b) we could add some kind of "reset" command that AUH could run between
>> builds which would clean things up?
>
>
> There is such a command  - 'devtool reset' and AUH does run it, however in 
> this case it does not work because the recipe in devtool workspace is 
> half-complete. (I think devtool reset looks up the recipe to be reset in 
> workspace/appends, which is empty because of the traceback).
>

may be there should be devetool reset --force to override everything
and bring workspace to original state.

> Alex
> --
> ___
> 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] glib-2.0: fix host path appearing in gsocketclient-slow test script

2019-06-18 Thread Ross Burton
Glib's build looks for the 'env' binary and embeds that path into the test
script, but thanks to hosttools this is /path/to/tmpdir/hosttools/env.

Fix this by hardcoding the path to env in the cross file.

Also as the cross file is only used in target builds only add it to SRC_URI for
target builds, so that changes to the cross file don't cause a rebuild of
glib-2.0-native.

Signed-off-by: Ross Burton 
---
 meta/recipes-core/glib-2.0/glib-2.0/glib-meson.cross | 3 +++
 meta/recipes-core/glib-2.0/glib-2.0_2.60.3.bb| 2 +-
 2 files changed, 4 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-core/glib-2.0/glib-2.0/glib-meson.cross 
b/meta/recipes-core/glib-2.0/glib-2.0/glib-meson.cross
index 8420f9874e1..b5df4007275 100644
--- a/meta/recipes-core/glib-2.0/glib-2.0/glib-meson.cross
+++ b/meta/recipes-core/glib-2.0/glib-2.0/glib-meson.cross
@@ -4,3 +4,6 @@ have_c99_snprintf = true
 have_unix98_printf = true
 va_val_copy = true
 growing_stack = false
+
+[binaries]
+env = "/usr/bin/env"
diff --git a/meta/recipes-core/glib-2.0/glib-2.0_2.60.3.bb 
b/meta/recipes-core/glib-2.0/glib-2.0_2.60.3.bb
index f4ade098ef1..bb77294e1e0 100644
--- a/meta/recipes-core/glib-2.0/glib-2.0_2.60.3.bb
+++ b/meta/recipes-core/glib-2.0/glib-2.0_2.60.3.bb
@@ -16,10 +16,10 @@ SRC_URI = 
"${GNOME_MIRROR}/glib/${SHRT_VER}/glib-${PV}.tar.xz \
file://0001-Do-not-write-bindir-into-pkg-config-files.patch \

file://0001-meson.build-do-not-hardcode-linux-as-the-host-system.patch \

file://0001-meson-do-a-build-time-check-for-strlcpy-before-attem.patch \
-   file://glib-meson.cross \
"
 
 SRC_URI_append_class-native = " file://relocate-modules.patch"
+SRC_URI_append_class-target = " file://glib-meson.cross"
 
 SRC_URI[md5sum] = "112a850caa8d2c21e24d4c9844e8b1fe"
 SRC_URI[sha256sum] = 
"04ab0d560d45790d055f50db2d69974eab8b693a77390075462c56e652b760b9"
-- 
2.11.0

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


Re: [OE-core] [PATCH] wireless-regdb: Add recipe

2019-06-18 Thread Richard Purdie
On Tue, 2019-06-18 at 13:34 +0100, Richard Purdie wrote:
> On Tue, 2019-06-18 at 09:11 +0300, Adrian Bunk wrote:
> > Since wpa-supplicant is provided,
> > the database of permitted frequencies should also be provided.
> > 
> > wireless-regdb-static should be used with kernel >= 4.15.
> > wireless-regdb can be used with older kernels and is mostly
> > irrelevant here, but keeping it in meta-networking would
> > create needless recipe duplication.
> > 
> > This package was previously in meta-networking.
> > 
> > Signed-off-by: Adrian Bunk 
> > ---
> >  meta/conf/distro/include/maintainers.inc  |  1 +
> >  .../packagegroups/packagegroup-base.bb|  1 +
> >  .../wireless-regdb_2019.06.03.bb  | 44
> > +++
> >  3 files changed, 46 insertions(+)
> >  create mode 100644 meta/recipes-kernel/wireless-regdb/wireless-
> > regdb_2019.06.03.bb
> 
> This seems to break deb rootfs construction:
> 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/50/builds/712

opkg as well:

https://autobuilder.yoctoproject.org/typhoon/#/builders/76/builds/716

basically nothing provides wireless-regdb but wireless-regdb depends on
it.

Cheers,

Richard

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


Re: [OE-core] [PATCH] kernel: qemuarmv5: Update machine overrides of KERNEL_DEVICETREE

2019-06-18 Thread Bruce Ashfield
On Tue, Jun 18, 2019 at 3:50 AM  wrote:
>
> From: He Zhe 
>
> The original BSP qemuarm has been renamed to qemuarmv5. Update the machine
> overrides accordingly to avoid not generating dtb.

Acked-by: Bruce Ashfield 

I had meant to do this myself, but kept forgetting :D

I can take this into my tree and send it with my next series.

Bruce

>
> Signed-off-by: He Zhe 
> ---
>  meta/recipes-kernel/linux/linux-yocto-dev.bb   | 2 +-
>  meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb   | 2 +-
>  meta/recipes-kernel/linux/linux-yocto-rt_5.0.bb| 2 +-
>  meta/recipes-kernel/linux/linux-yocto-tiny_4.19.bb | 2 +-
>  meta/recipes-kernel/linux/linux-yocto-tiny_5.0.bb  | 2 +-
>  meta/recipes-kernel/linux/linux-yocto_4.19.bb  | 2 +-
>  meta/recipes-kernel/linux/linux-yocto_5.0.bb   | 1 -
>  7 files changed, 6 insertions(+), 7 deletions(-)
>
> diff --git a/meta/recipes-kernel/linux/linux-yocto-dev.bb 
> b/meta/recipes-kernel/linux/linux-yocto-dev.bb
> index 3a055c1..8c83620 100644
> --- a/meta/recipes-kernel/linux/linux-yocto-dev.bb
> +++ b/meta/recipes-kernel/linux/linux-yocto-dev.bb
> @@ -41,7 +41,7 @@ DEPENDS += "openssl-native util-linux-native"
>
>  COMPATIBLE_MACHINE = 
> "(qemuarm|qemux86|qemuppc|qemumips|qemumips64|qemux86-64)"
>
> -KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
> +KERNEL_DEVICETREE_qemuarmv5 = "versatile-pb.dtb"
>
>  # Functionality flags
>  KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc 
> features/taskstats/taskstats.scc"
> diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb 
> b/meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb
> index 0836dc7..a4facfe 100644
> --- a/meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb
> +++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb
> @@ -33,7 +33,7 @@ LINUX_KERNEL_TYPE = "preempt-rt"
>
>  COMPATIBLE_MACHINE = 
> "(qemux86|qemux86-64|qemuarm|qemuarmv5|qemuarm64|qemuppc|qemumips)"
>
> -KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
> +KERNEL_DEVICETREE_qemuarmv5 = "versatile-pb.dtb"
>
>  # Functionality flags
>  KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc 
> features/taskstats/taskstats.scc"
> diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.0.bb 
> b/meta/recipes-kernel/linux/linux-yocto-rt_5.0.bb
> index b5e415f..8bd9d74 100644
> --- a/meta/recipes-kernel/linux/linux-yocto-rt_5.0.bb
> +++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.0.bb
> @@ -33,7 +33,7 @@ LINUX_KERNEL_TYPE = "preempt-rt"
>
>  COMPATIBLE_MACHINE = 
> "(qemux86|qemux86-64|qemuarm|qemuarmv5|qemuarm64|qemuppc|qemumips)"
>
> -KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
> +KERNEL_DEVICETREE_qemuarmv5 = "versatile-pb.dtb"
>
>  # Functionality flags
>  KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc 
> features/taskstats/taskstats.scc"
> diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.19.bb 
> b/meta/recipes-kernel/linux/linux-yocto-tiny_4.19.bb
> index 4ca11d7..e668854 100644
> --- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.19.bb
> +++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.19.bb
> @@ -29,4 +29,4 @@ COMPATIBLE_MACHINE = "qemux86|qemux86-64|qemuarm|qemuarmv5"
>  # Functionality flags
>  KERNEL_FEATURES = ""
>
> -KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
> +KERNEL_DEVICETREE_qemuarmv5 = "versatile-pb.dtb"
> diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.0.bb 
> b/meta/recipes-kernel/linux/linux-yocto-tiny_5.0.bb
> index a9c463c..226a90c 100644
> --- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.0.bb
> +++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.0.bb
> @@ -29,4 +29,4 @@ COMPATIBLE_MACHINE = "qemux86|qemux86-64|qemuarm|qemuarmv5"
>  # Functionality flags
>  KERNEL_FEATURES = ""
>
> -KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
> +KERNEL_DEVICETREE_qemuarmv5 = "versatile-pb.dtb"
> diff --git a/meta/recipes-kernel/linux/linux-yocto_4.19.bb 
> b/meta/recipes-kernel/linux/linux-yocto_4.19.bb
> index cda4ecf..014d689 100644
> --- a/meta/recipes-kernel/linux/linux-yocto_4.19.bb
> +++ b/meta/recipes-kernel/linux/linux-yocto_4.19.bb
> @@ -36,7 +36,7 @@ PV = "${LINUX_VERSION}+git${SRCPV}"
>  KMETA = "kernel-meta"
>  KCONF_BSP_AUDIT_LEVEL = "2"
>
> -KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
> +KERNEL_DEVICETREE_qemuarmv5 = "versatile-pb.dtb"
>
>  COMPATIBLE_MACHINE = 
> "qemuarm|qemuarmv5|qemuarm64|qemux86|qemuppc|qemumips|qemumips64|qemux86-64"
>
> diff --git a/meta/recipes-kernel/linux/linux-yocto_5.0.bb 
> b/meta/recipes-kernel/linux/linux-yocto_5.0.bb
> index 8aec315..bb7ed56 100644
> --- a/meta/recipes-kernel/linux/linux-yocto_5.0.bb
> +++ b/meta/recipes-kernel/linux/linux-yocto_5.0.bb
> @@ -38,7 +38,6 @@ PV = "${LINUX_VERSION}+git${SRCPV}"
>  KMETA = "kernel-meta"
>  KCONF_BSP_AUDIT_LEVEL = "2"
>
> -KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
>  KERNEL_DEVICETREE_qemuarmv5 = "versatile-pb.dtb"
>
>  COMPATIBLE_MACHINE = 
> "qemuarm|qemuarmv5|qemuarm64|qemux86|qemuppc|qemumips|qemumips64|qemux86-64"
> --
> 2.7.4
>


-- 
- Thou shalt not follow the NULL pointer, for chaos an

Re: [OE-core] [PATCH] wireless-regdb: Add recipe

2019-06-18 Thread Richard Purdie
On Tue, 2019-06-18 at 09:11 +0300, Adrian Bunk wrote:
> Since wpa-supplicant is provided,
> the database of permitted frequencies should also be provided.
> 
> wireless-regdb-static should be used with kernel >= 4.15.
> wireless-regdb can be used with older kernels and is mostly
> irrelevant here, but keeping it in meta-networking would
> create needless recipe duplication.
> 
> This package was previously in meta-networking.
> 
> Signed-off-by: Adrian Bunk 
> ---
>  meta/conf/distro/include/maintainers.inc  |  1 +
>  .../packagegroups/packagegroup-base.bb|  1 +
>  .../wireless-regdb_2019.06.03.bb  | 44
> +++
>  3 files changed, 46 insertions(+)
>  create mode 100644 meta/recipes-kernel/wireless-regdb/wireless-
> regdb_2019.06.03.bb

This seems to break deb rootfs construction:

https://autobuilder.yoctoproject.org/typhoon/#/builders/50/builds/712

> diff --git a/meta/conf/distro/include/maintainers.inc
> b/meta/conf/distro/include/maintainers.inc
> index 38fc711f5c..26851d66e0 100644
> --- a/meta/conf/distro/include/maintainers.inc
> +++ b/meta/conf/distro/include/maintainers.inc
> @@ -726,6 +726,7 @@ RECIPE_MAINTAINER_pn-weston-init = "Denys
> Dmytriyenko "
>  RECIPE_MAINTAINER_pn-wget = "Yi Zhao "
>  RECIPE_MAINTAINER_pn-which = "Anuj Mittal "
>  RECIPE_MAINTAINER_pn-wic-tools = "Anuj Mittal  >"
> +RECIPE_MAINTAINER_pn-wireless-regdb = "Adrian Bunk 
> "
>  RECIPE_MAINTAINER_pn-wpa-supplicant = "Changhyeok Bae <
> changhyeok@gmail.com>"
>  RECIPE_MAINTAINER_pn-x11perf = "Armin Kuster "
>  RECIPE_MAINTAINER_pn-x264 = "Anuj Mittal "
> diff --git a/meta/recipes-core/packagegroups/packagegroup-base.bb
> b/meta/recipes-core/packagegroups/packagegroup-base.bb
> index cae704aa24..d05403635c 100644
> --- a/meta/recipes-core/packagegroups/packagegroup-base.bb
> +++ b/meta/recipes-core/packagegroups/packagegroup-base.bb
> @@ -271,6 +271,7 @@ RRECOMMENDS_packagegroup-base-ipsec = "\
>  SUMMARY_packagegroup-base-wifi = "WiFi support"
>  RDEPENDS_packagegroup-base-wifi = "\
>  iw \
> +wireless-regdb-static \
>  wpa-supplicant"
>  
>  RRECOMMENDS_packagegroup-base-wifi = "\
> diff --git a/meta/recipes-kernel/wireless-regdb/wireless-
> regdb_2019.06.03.bb b/meta/recipes-kernel/wireless-regdb/wireless-
> regdb_2019.06.03.bb
> new file mode 100644
> index 00..df50938a1a
> --- /dev/null
> +++ b/meta/recipes-kernel/wireless-regdb/wireless-regdb_2019.06.03.bb
> @@ -0,0 +1,44 @@
> +SUMMARY = "Wireless Central Regulatory Domain Database"
> +HOMEPAGE = "http://wireless.kernel.org/en/developers/Regulatory/CRDA
> "
> +SECTION = "net"
> +LICENSE = "ISC"
> +LIC_FILES_CHKSUM =
> "file://LICENSE;md5=07c4f6dea3845b02a18dc00c8c87699c"
> +
> +SRC_URI = "
> https://www.kernel.org/pub/software/network/${BPN}/${BP}.tar.xz";
> +SRC_URI[md5sum] = "4b5ba3f089db7fdb7b9daae6a7c1f2cb"
> +SRC_URI[sha256sum] =
> "cd917ed86b63ce8d93947979f1f18948f03a4ac0ad89ec25227b36ac00dc54bf"
> +
> +inherit bin_package allarch
> +
> +do_install() {
> +install -d -m0755 ${D}${nonarch_libdir}/crda
> +install -d -m0755 ${D}${sysconfdir}/wireless-regdb/pubkeys
> +install -m 0644 regulatory.bin
> ${D}${nonarch_libdir}/crda/regulatory.bin
> +install -m 0644 sforshee.key.pub.pem ${D}${sysconfdir}/wireless-
> regdb/pubkeys/sforshee.key.pub.pem
> +
> +install -m 0644 -D regulatory.db
> ${D}${nonarch_base_libdir}/firmware/regulatory.db
> +install -m 0644 regulatory.db.p7s
> ${D}${nonarch_base_libdir}/firmware/regulatory.db.p7s
> +}
> +
> +# Install static regulatory DB in /lib/firmware for kernel to load.
> +# This requires Linux kernel >= v4.15.
> +# For kernel <= v4.14, inherit the kernel_wireless_regdb.bbclass
> +# (in meta-networking) in kernel's recipe.
> +PACKAGES =+ "${PN}-static"
> +RCONFLICTS_${PN} = "${PN}-static"

To work with apt/dpkg this may need an RPROVIDES and/or RREPLACES.

Cheers,

Richard


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


Re: [OE-core] [PATCH] wic/bootimg-efi: allow multiple initrd

2019-06-18 Thread Lee, Chee Yang
My bad, I should test it with complete oe-selftest wic module.

On 6/18/19, 4:37 AM, "Richard Purdie"  
wrote:

On Thu, 2019-06-13 at 14:21 +0800, chee.yang@intel.com wrote:
> From: Chee Yang Lee 
> 
> Allow plugin bootimg-efi to configure with multiple initrd
> through source parameter.
> 
> Uses ; to separate each initrd.
> 
> e.g:
> --sourceparams="loader=${EFI_PROVIDER},initrd=initrd1;initrd2"
> 
> Signed-off-by: Chee Yang Lee 
> ---
>  scripts/lib/wic/plugins/source/bootimg-efi.py | 24 -
> ---
>  1 file changed, 16 insertions(+), 8 deletions(-)


How was this tested? It broke the autobuilder build:

| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing shell function do_image_wic
| INFO: Creating image(s)...
| 
| Traceback (most recent call last):
|   File "/home/pokybuild/yocto-worker/genericx86/build/scripts/wic", line 
525, in 
| sys.exit(main(sys.argv[1:]))
|   File "/home/pokybuild/yocto-worker/genericx86/build/scripts/wic", line 
520, in main
| return hlp.invoke_subcommand(args, parser, hlp.wic_help_usage, 
subcommands)
|   File 
"/home/pokybuild/yocto-worker/genericx86/build/scripts/lib/wic/help.py", line 
83, in invoke_subcommand
| subcmd[0](args, usage)
|   File "/home/pokybuild/yocto-worker/genericx86/build/scripts/wic", line 
220, in wic_create_subcommand
| native_sysroot, options)
|   File 
"/home/pokybuild/yocto-worker/genericx86/build/scripts/lib/wic/engine.py", line 
189, in wic_create
| plugin.do_create()
|   File 
"/home/pokybuild/yocto-worker/genericx86/build/scripts/lib/wic/plugins/imager/direct.py",
 line 86, in do_create
| self.create()
|   File 
"/home/pokybuild/yocto-worker/genericx86/build/scripts/lib/wic/plugins/imager/direct.py",
 line 196, in create
| self._image.prepare(self)
|   File 
"/home/pokybuild/yocto-worker/genericx86/build/scripts/lib/wic/plugins/imager/direct.py",
 line 362, in prepare
| imager.kernel_dir, imager.native_sysroot)
|   File 
"/home/pokybuild/yocto-worker/genericx86/build/scripts/lib/wic/partition.py", 
line 167, in prepare
| kernel_dir, native_sysroot)
|   File 
"/home/pokybuild/yocto-worker/genericx86/build/scripts/lib/wic/plugins/source/bootimg-efi.py",
 line 198, in do_configure_partition
| cls.do_configure_grubefi(hdddir, creator, cr_workdir, source_params)
|   File 
"/home/pokybuild/yocto-worker/genericx86/build/scripts/lib/wic/plugins/source/bootimg-efi.py",
 line 88, in do_configure_grubefi
| if initrds:
| UnboundLocalError: local variable 'initrds' referenced before assignment
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_image_wic (log file is located at 
/home/pokybuild/yocto-worker/genericx86/build/build/tmp/work/genericx86-poky-linux/core-image-minimal-initramfs/1.0-r0/temp/log.do_image_wic.23700)


https://autobuilder.yoctoproject.org/typhoon/#/builders/48/builds/712
https://autobuilder.yoctoproject.org/typhoon/#/builders/37/builds/717
https://autobuilder.yoctoproject.org/typhoon/#/builders/43/builds/712
https://autobuilder.yoctoproject.org/typhoon/#/builders/49/builds/711
https://autobuilder.yoctoproject.org/typhoon/#/builders/58/builds/699

wic selftests don't even work:
https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/526


Richard



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


[OE-core] [PATCHv2] base.bbclass: define PACKAGECONFIG_CONFARGS before only sometimes appending to it

2019-06-18 Thread Martin Jansa
* just to make sure it's expaned by bitbake before it gets
  executed in shell
* e.g. with cmake.bbclass and cmake recipe (any recipe without
  PACKAGECONFIG options have this issue) it looks like this:
  bitbake -e cmake | grep EXTRA_OECMAKE=
  EXTRA_OECMAKE=" -DCMAKE_DOC_DIR=share/doc/cmake-3.14
-DCMAKE_USE_SYSTEM_LIBRARIES=1 -DCMAKE_USE_SYSTEM_LIBRARY_JSONCPP=0
-DCMAKE_USE_SYSTEM_LIBRARY_LIBUV=0
-DCMAKE_USE_SYSTEM_LIBRARY_LIBRHASH=0 -DKWSYS_CHAR_IS_SIGNED=1
-DBUILD_CursesDialog=0 -DKWSYS_LFS_WORKS=1
\${PACKAGECONFIG_CONFARGS}"

Signed-off-by: Martin Jansa 
---
 meta/classes/base.bbclass | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
index 90af8ba72b..0c8a4b2862 100644
--- a/meta/classes/base.bbclass
+++ b/meta/classes/base.bbclass
@@ -15,6 +15,8 @@ OE_EXTRA_IMPORTS ?= ""
 OE_IMPORTS += "os sys time oe.path oe.utils oe.types oe.package 
oe.packagegroup oe.sstatesig oe.lsb oe.cachedpath oe.license 
${OE_EXTRA_IMPORTS}"
 OE_IMPORTS[type] = "list"
 
+PACKAGECONFIG_CONFARGS ??= ""
+
 def oe_import(d):
 import sys
 
-- 
2.17.1

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


[OE-core] [PATCH] apt: fix permissions on apt-daily script for systemd

2019-06-18 Thread Matt Madison
The script needs to be executable so the service doesn't
fail.

Signed-off-by: Matt Madison 
---
 meta/recipes-devtools/apt/apt-package.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/apt/apt-package.inc 
b/meta/recipes-devtools/apt/apt-package.inc
index 6a01f99c63..da91451d7f 100644
--- a/meta/recipes-devtools/apt/apt-package.inc
+++ b/meta/recipes-devtools/apt/apt-package.inc
@@ -83,7 +83,7 @@ do_install () {
install -m 0644 include/apt-pkg/*.h ${D}${includedir}/apt-pkg/
 
install -d ${D}${systemd_unitdir}/system/
-   install -m 0644 ${S}/debian/apt.systemd.daily ${D}${libdir}/apt/
+   install -m 0755 ${S}/debian/apt.systemd.daily ${D}${libdir}/apt/
install -m 0644 ${S}/debian/apt-daily.service 
${D}${systemd_unitdir}/system/
sed -i 's#/usr/lib/apt/#${libdir}/apt/#g' 
${D}${systemd_unitdir}/system/apt-daily.service
install -m 0644 ${S}/debian/apt-daily.timer 
${D}${systemd_unitdir}/system/
-- 
2.20.1

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


Re: [OE-core] [PATCH v3] openssl: Fix a build bug on aarch64BE.

2019-06-18 Thread Alexander Kanavin
On Tue, 18 Jun 2019 at 09:54, Lei Maohui  wrote:

> +Upstream-Status: Submitted [https://github.com/openssl/openssl/pull/9151
>

Seems like a contributor agreement is needed for this patch?
https://www.openssl.org/policies/cla.html

Are you going to do tihs?

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


Re: [OE-core] [PATCH] toolchain-scripts: make rpm work in toolchain

2019-06-18 Thread Alexander Kanavin
RPM is taking these things from its config file, not from an environment
variable, so you must be doing some additional custom magic to configure
rpm from environment when SDK is already in use.

Instead, you probably need to write appropriate settings into the file when
the nativesdk-rpm package gets created (or when populate_sdk is executed).

Alex

On Tue, 18 Jun 2019 at 10:03, Lei, Maohui  wrote:

> ping
>
> > -Original Message-
> > From: openembedded-core-boun...@lists.openembedded.org [mailto:
> openembedded-
> > core-boun...@lists.openembedded.org] On Behalf Of Lei, Maohui
> > Sent: Thursday, June 06, 2019 10:39 AM
> > To: richard.pur...@linuxfoundation.org
> > Cc: openembedded-core@lists.openembedded.org
> > Subject: Re: [OE-core] [PATCH] toolchain-scripts: make rpm work in
> toolchain
> >
> > Hi, Richard
> >
> > > Whilst I can guess why, its not obvious at all the dnf needs
> > > MACHINE_ARCH. I'd probably be happier with a better variable name.
> > > Which code exactly is using it?
> >
> > Arch information is necessary for rpm. As what do for dnf-native in
> > _configure_rpm function, nativesdk-dnf has to do the same work.
> > But the environment for nativesdk doesn't supply arch information. I
> think
> > MACHINE_ARCH is suitable to supply arch information for nativesdk.
> > How about your Opinion?
> >
> > Best regards
> > Lei
> >
> >
> >
> > > -Original Message-
> > > From: richard.pur...@linuxfoundation.org
> > > [mailto:richard.pur...@linuxfoundation.org]
> > > Sent: Tuesday, June 04, 2019 6:26 PM
> > > To: Lei, Maohui
> > > Cc: openembedded-core@lists.openembedded.org
> > > Subject: Re: [OE-core] [PATCH] toolchain-scripts: make rpm work in
> toolchain
> > >
> > > On Tue, 2019-06-04 at 08:29 +, Lei, Maohui wrote:
> > > > Hi Richard
> > > >
> > > > This patch is necessary for dnf-nativesdk which has been merged. But
> > > > this patch is still ignored.
> > > > Do you have any comment about this patch?
> > >
> > > Basically I really don't like exporting "random" variables in the SDK,
> > > particularly when the meaning/use of them isn't clear.
> > >
> > > Whilst I can guess why, its not obvious at all the dnf needs
> > > MACHINE_ARCH. I'd probably be happier with a better variable name.
> > > Which code exactly is using it?
> > >
> > > Cheers,
> > >
> > > Richard
> > >
> > >
> >
> >
> >
> > --
> > ___
> > 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
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [AUH] lttng-ust: upgrading to 2.10.4 FAILED

2019-06-18 Thread Alexander Kanavin
On Mon, 17 Jun 2019 at 17:26, Richard Purdie  wrote:

>
> I think that perhaps:
>
> a) we should have a bug for this as devtool shouldn't be giving
> tracebacks?
>

Bug filed:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13404


> b) we could add some kind of "reset" command that AUH could run between
> builds which would clean things up?
>

There is such a command  - 'devtool reset' and AUH does run it, however in
this case it does not work because the recipe in devtool workspace is
half-complete. (I think devtool reset looks up the recipe to be reset in
workspace/appends, which is empty because of the traceback).

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


Re: [OE-core] [PATCH] lighttpd:upgrade 1.4.53 -> 1.4.54

2019-06-18 Thread Adrian Bunk
WARNING: lighttpd-1.4.54-r0 do_patch: Fuzz detected:

Applying patch mod-eke-prio.patch
patching file src/Makefile.am
Hunk #1 succeeded at 419 with fuzz 2 (offset 15 lines).
patching file src/mod_eke_prio.c

The context lines in the patches can be updated with devtool:

devtool modify lighttpd
devtool finish --force-patch-refresh lighttpd 

Don't forget to review changes done by devtool!

WARNING: lighttpd-1.4.54-r0 do_patch: QA Issue: Patch log indicates that 
patches do not apply cleanly. [patch-fuzz]


cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

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


[OE-core] [PATCH] libsdl2: use binconfig-disabled

2019-06-18 Thread Ross Burton
Just like libsdl, we can rip out the sdl2-config script from the sysroot as
pkg-config is preferrable.

Signed-off-by: Ross Burton 
---
 meta/recipes-graphics/libsdl2/libsdl2_2.0.9.bb | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-graphics/libsdl2/libsdl2_2.0.9.bb 
b/meta/recipes-graphics/libsdl2/libsdl2_2.0.9.bb
index bac91d37366..a0a0b1509a2 100644
--- a/meta/recipes-graphics/libsdl2/libsdl2_2.0.9.bb
+++ b/meta/recipes-graphics/libsdl2/libsdl2_2.0.9.bb
@@ -21,7 +21,9 @@ S = "${WORKDIR}/SDL2-${PV}"
 SRC_URI[md5sum] = "f2ecfba915c54f7200f504d8b48a5dfe"
 SRC_URI[sha256sum] = 
"255186dc676ecd0c1dbf10ec8a2cc5d6869b5079d8a38194c2aecdff54b324b1"
 
-inherit autotools lib_package binconfig pkgconfig
+inherit autotools lib_package binconfig-disabled pkgconfig
+
+BINCONFIG = "${bindir}/sdl2-config"
 
 CVE_PRODUCT = "simple_directmedia_layer sdl"
 
-- 
2.11.0

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


[OE-core] [PATCH] binconfig: don't try to fix up .la files

2019-06-18 Thread Ross Burton
If we're going to clean buildpaths from installed .la files then we should do it
globally, not in a class that only six recipes in oe-core use.

Signed-off-by: Ross Burton 
---
 meta/classes/binconfig.bbclass | 9 -
 1 file changed, 9 deletions(-)

diff --git a/meta/classes/binconfig.bbclass b/meta/classes/binconfig.bbclass
index 133b9537cf0..9112ed46085 100644
--- a/meta/classes/binconfig.bbclass
+++ b/meta/classes/binconfig.bbclass
@@ -40,15 +40,6 @@ binconfig_package_preprocess () {
-e 's:${STAGING_DIR_HOST}${prefix}:${prefix}:' \
 $config
done
-   for lafile in `find ${PKGD} -type f -name "*.la"` ; do
-   sed -i \
-   -e 's:${STAGING_BASELIBDIR}:${base_libdir}:g;' \
-   -e 's:${STAGING_LIBDIR}:${libdir}:g;' \
-   -e 's:${STAGING_INCDIR}:${includedir}:g;' \
-   -e 's:${STAGING_DATADIR}:${datadir}:' \
-   -e 's:${STAGING_DIR_HOST}${prefix}:${prefix}:' \
-   $lafile
-   done
 }
 
 SYSROOT_PREPROCESS_FUNCS += "binconfig_sysroot_preprocess"
-- 
2.11.0

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


[OE-core] [PATCH] insane: remove empty test that does nothing

2019-06-18 Thread Ross Burton
Signed-off-by: Ross Burton 
---
 meta/classes/insane.bbclass | 7 ---
 1 file changed, 7 deletions(-)

diff --git a/meta/classes/insane.bbclass b/meta/classes/insane.bbclass
index fdc20c41a52..6e32db00314 100644
--- a/meta/classes/insane.bbclass
+++ b/meta/classes/insane.bbclass
@@ -259,13 +259,6 @@ def package_qa_check_dbg(path, name, d, elf, messages):
 package_qa_add_message(messages, "debug-files", "non debug package 
contains .debug directory: %s path %s" % \
  (name, package_qa_clean_path(path,d)))
 
-QAPATHTEST[perms] = "package_qa_check_perm"
-def package_qa_check_perm(path,name,d, elf, messages):
-"""
-Check the permission of files
-"""
-return
-
 QAPATHTEST[arch] = "package_qa_check_arch"
 def package_qa_check_arch(path,name,d, elf, messages):
 """
-- 
2.11.0

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


[OE-core] [PATCH] insane: improve buildpath warning messages

2019-06-18 Thread Ross Burton
Instead of reporting large chunks of the work directory and not the package
name:

"File 
/work/corei7-64-poky-linux/libidn2/2.2.0-r0/packages-split/libidn2-dev/usr/lib/pkgconfig/libidn2.pc
 in package contained reference to tmpdir"

We can clean up the paths and be more useful:

"File /usr/lib/pkgconfig/libidn2.pc in package libidn2-dev contains reference 
to TMPDIR"

Signed-off-by: Ross Burton 
---
 meta/classes/insane.bbclass | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/classes/insane.bbclass b/meta/classes/insane.bbclass
index 6e32db00314..0695a044387 100644
--- a/meta/classes/insane.bbclass
+++ b/meta/classes/insane.bbclass
@@ -401,7 +401,8 @@ def package_qa_check_buildpaths(path, name, d, elf, 
messages):
 with open(path, 'rb') as f:
 file_content = f.read()
 if tmpdir in file_content:
-package_qa_add_message(messages, "buildpaths", "File %s in package 
contained reference to tmpdir" % package_qa_clean_path(path,d))
+trimmed = path.replace(os.path.join (d.getVar("PKGDEST"), name), 
"")
+package_qa_add_message(messages, "buildpaths", "File %s in package 
%s contains reference to TMPDIR" % (trimmed, name))
 
 
 QAPATHTEST[xorg-driver-abi] = "package_qa_check_xorg_driver_abi"
-- 
2.11.0

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


Re: [OE-core] [PATCH 1/1] manifest.py: fix test_SDK_manifest_entries

2019-06-18 Thread richard . purdie
On Tue, 2019-06-18 at 10:09 +0800, ChenQi wrote:
> On 06/17/2019 11:54 PM, Richard Purdie wrote:
> > On Mon, 2019-06-17 at 17:24 +0800, Chen Qi wrote:
> > > TOOLCHAIN_OUTPUTNAME could be overridden. So use this variable
> > > directly
> > > instead of its default value ${SDK_NAME}-toolchain-
> > > ${SDK_VERSION}.
> > > 
> > > Signed-off-by: Chen Qi 
> > > ---
> > >   meta/lib/oeqa/selftest/cases/manifest.py | 7 ++-
> > >   1 file changed, 2 insertions(+), 5 deletions(-)
> > > 
> > > diff --git a/meta/lib/oeqa/selftest/cases/manifest.py
> > > b/meta/lib/oeqa/selftest/cases/manifest.py
> > > index c0b25ab..5d13f35 100644
> > > --- a/meta/lib/oeqa/selftest/cases/manifest.py
> > > +++ b/meta/lib/oeqa/selftest/cases/manifest.py
> > > @@ -86,11 +86,8 @@ class VerifyManifest(OESelftestTestCase):
> > >   try:
> > >   mdir = self.get_dir_from_bb_var('SDK_DEPLOY',
> > > self.buildtarget)
> > >   for k in d_target.keys():
> > > -bb_vars = get_bb_vars(['SDK_NAME',
> > > 'SDK_VERSION'], self.buildtarget)
> > > -mfilename[k] = "{}-toolchain-
> > > {}.{}.manifest".format(
> > > -bb_vars['SDK_NAME'],
> > > -bb_vars['SDK_VERSION'],
> > > -k)
> > > +toolchain_outputname =
> > > get_bb_var('TOOLCHAIN_OUTPUTNAME', self.buildtarget)
> > > +mfilename[k] =
> > > "{}.{}.manifest".format(toolchain_outputname, k)
> > Whilst I agree there is a problem here, this code is iterating over
> > multiple targets. Isn't TOOLCHAIN_OUTPUTNAME only going to be
> > correct
> > for one of them?
> > 
> > Cheers,
> > 
> > Richard
> > 
> > 
> 
> This code is iterating over d_target.keys(), which is 'target' and 
> 'host'. And the TOOLCHAIN_OUTPUTNAME is for self.buildtarget, which
> is 
> core-image-minimal. Thus, we are basically checking 
> ${TOOLCHAIN_OUTPUTNAME}.target.manifest and 
> ${TOOLCHAIN_OUTPUTNAME}.host.target.
> e.g.
> tmp-glibc/deploy/sdk/poky-glibc-x86_64-core-image-minimal-core2-64-
> qemux86-64-toolchain-2.7+snapshot.host.manifest
> tmp-glibc/deploy/sdk/poky-glibc-x86_64-core-image-minimal-core2-64-
> qemux86-64-toolchain-2.7+snapshot.target.manifest
> 
> So I think things are correct.

You're right, I was going from memory and thought this code was
handling the case where there are two different targets in an SDK (e.g.
a multilib) but that isn't the case. I've queued the patch for testing.

Cheers,

Richard

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


[OE-core] ✗ patchtest: failure for perl: Move perl-sanity -> perl

2019-06-18 Thread Patchwork
== Series Details ==

Series: perl: Move perl-sanity -> perl
Revision: 1
URL   : https://patchwork.openembedded.org/series/18200/
State : failure

== Summary ==


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



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



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

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

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


[OE-core] ✗ patchtest: failure for systat: systemd never enables the service

2019-06-18 Thread Patchwork
== Series Details ==

Series: systat: systemd never enables the service
Revision: 1
URL   : https://patchwork.openembedded.org/series/18199/
State : failure

== Summary ==


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



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



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

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

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


Re: [OE-core] [Patch v3 2/4] libcap-ng: split into libcap-ng/libcap-ng-python

2019-06-18 Thread Richard Purdie
On Sun, 2019-06-16 at 11:48 -0400, Randy MacLeod wrote:
> util-linux's setpriv needs the libcap-ng library but
> not the python package so split the package up to enable
> this without a dependency loop.
> 
> Signed-off-by: Randy MacLeod 
> ---
>  meta/recipes-support/libcap-ng/libcap-ng  |  1 +
>  .../python.patch  |  0
>  .../libcap-ng/libcap-ng-python_0.7.9.bb   | 27
> ++
>  meta/recipes-support/libcap-ng/libcap-ng.inc  | 17 +++
>  .../libcap-ng/libcap-ng_0.7.9.bb  | 28 +++
> 
>  5 files changed, 49 insertions(+), 24 deletions(-)
>  create mode 12 meta/recipes-support/libcap-ng/libcap-ng
>  rename meta/recipes-support/libcap-ng/{libcap-ng => libcap-ng-
> python}/python.patch (100%)
>  create mode 100644 meta/recipes-support/libcap-ng/libcap-ng-
> python_0.7.9.bb
>  create mode 100644 meta/recipes-support/libcap-ng/libcap-ng.inc

Two steps forward, one step back. The maintainers.inc entry went
missing in v3 from v2.

I fixed it.

Cheers,

Richard

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


[OE-core] [PATCH] perl: Move perl-sanity -> perl

2019-06-18 Thread Richard Purdie
This was moved during the perl cleanup, it can/should be moved back now as
its confusing too many people.

Signed-off-by: Richard Purdie 
---
 ...001-ExtUtils-MakeMaker-add-LDFLAGS-when-linking-binary-m.patch | 0
 ...001-Somehow-this-module-breaks-through-the-perl-wrapper-.patch | 0
 ...001-configure_path.sh-do-not-hardcode-prefix-lib-as-libr.patch | 0
 ...001-configure_tool.sh-do-not-quote-the-argument-to-comma.patch | 0
 .../files/0001-perl-cross-add-LDFLAGS-when-linking-libperl.patch  | 0
 meta/recipes-devtools/{perl-sanity => perl}/files/errno_ver.diff  | 0
 .../{perl-sanity => perl}/files/fix-setgroup.patch| 0
 .../{perl-sanity => perl}/files/native-perlinc.patch  | 0
 .../{perl-sanity => perl}/files/perl-configpm-switch.patch| 0
 .../{perl-sanity => perl}/files/perl-dynloader.patch  | 0
 .../{perl-sanity => perl}/files/perl-rdepends.txt | 0
 meta/recipes-devtools/{perl-sanity => perl}/files/run-ptest   | 0
 meta/recipes-devtools/{perl-sanity => perl}/perl-ptest.inc| 0
 meta/recipes-devtools/{perl-sanity => perl}/perl_5.30.0.bb| 0
 14 files changed, 0 insertions(+), 0 deletions(-)
 rename meta/recipes-devtools/{perl-sanity => 
perl}/files/0001-ExtUtils-MakeMaker-add-LDFLAGS-when-linking-binary-m.patch 
(100%)
 rename meta/recipes-devtools/{perl-sanity => 
perl}/files/0001-Somehow-this-module-breaks-through-the-perl-wrapper-.patch 
(100%)
 rename meta/recipes-devtools/{perl-sanity => 
perl}/files/0001-configure_path.sh-do-not-hardcode-prefix-lib-as-libr.patch 
(100%)
 rename meta/recipes-devtools/{perl-sanity => 
perl}/files/0001-configure_tool.sh-do-not-quote-the-argument-to-comma.patch 
(100%)
 rename meta/recipes-devtools/{perl-sanity => 
perl}/files/0001-perl-cross-add-LDFLAGS-when-linking-libperl.patch (100%)
 rename meta/recipes-devtools/{perl-sanity => perl}/files/errno_ver.diff (100%)
 rename meta/recipes-devtools/{perl-sanity => perl}/files/fix-setgroup.patch 
(100%)
 rename meta/recipes-devtools/{perl-sanity => perl}/files/native-perlinc.patch 
(100%)
 rename meta/recipes-devtools/{perl-sanity => 
perl}/files/perl-configpm-switch.patch (100%)
 rename meta/recipes-devtools/{perl-sanity => perl}/files/perl-dynloader.patch 
(100%)
 rename meta/recipes-devtools/{perl-sanity => perl}/files/perl-rdepends.txt 
(100%)
 rename meta/recipes-devtools/{perl-sanity => perl}/files/run-ptest (100%)
 rename meta/recipes-devtools/{perl-sanity => perl}/perl-ptest.inc (100%)
 rename meta/recipes-devtools/{perl-sanity => perl}/perl_5.30.0.bb (100%)

diff --git 
a/meta/recipes-devtools/perl-sanity/files/0001-ExtUtils-MakeMaker-add-LDFLAGS-when-linking-binary-m.patch
 
b/meta/recipes-devtools/perl/files/0001-ExtUtils-MakeMaker-add-LDFLAGS-when-linking-binary-m.patch
similarity index 100%
rename from 
meta/recipes-devtools/perl-sanity/files/0001-ExtUtils-MakeMaker-add-LDFLAGS-when-linking-binary-m.patch
rename to 
meta/recipes-devtools/perl/files/0001-ExtUtils-MakeMaker-add-LDFLAGS-when-linking-binary-m.patch
diff --git 
a/meta/recipes-devtools/perl-sanity/files/0001-Somehow-this-module-breaks-through-the-perl-wrapper-.patch
 
b/meta/recipes-devtools/perl/files/0001-Somehow-this-module-breaks-through-the-perl-wrapper-.patch
similarity index 100%
rename from 
meta/recipes-devtools/perl-sanity/files/0001-Somehow-this-module-breaks-through-the-perl-wrapper-.patch
rename to 
meta/recipes-devtools/perl/files/0001-Somehow-this-module-breaks-through-the-perl-wrapper-.patch
diff --git 
a/meta/recipes-devtools/perl-sanity/files/0001-configure_path.sh-do-not-hardcode-prefix-lib-as-libr.patch
 
b/meta/recipes-devtools/perl/files/0001-configure_path.sh-do-not-hardcode-prefix-lib-as-libr.patch
similarity index 100%
rename from 
meta/recipes-devtools/perl-sanity/files/0001-configure_path.sh-do-not-hardcode-prefix-lib-as-libr.patch
rename to 
meta/recipes-devtools/perl/files/0001-configure_path.sh-do-not-hardcode-prefix-lib-as-libr.patch
diff --git 
a/meta/recipes-devtools/perl-sanity/files/0001-configure_tool.sh-do-not-quote-the-argument-to-comma.patch
 
b/meta/recipes-devtools/perl/files/0001-configure_tool.sh-do-not-quote-the-argument-to-comma.patch
similarity index 100%
rename from 
meta/recipes-devtools/perl-sanity/files/0001-configure_tool.sh-do-not-quote-the-argument-to-comma.patch
rename to 
meta/recipes-devtools/perl/files/0001-configure_tool.sh-do-not-quote-the-argument-to-comma.patch
diff --git 
a/meta/recipes-devtools/perl-sanity/files/0001-perl-cross-add-LDFLAGS-when-linking-libperl.patch
 
b/meta/recipes-devtools/perl/files/0001-perl-cross-add-LDFLAGS-when-linking-libperl.patch
similarity index 100%
rename from 
meta/recipes-devtools/perl-sanity/files/0001-perl-cross-add-LDFLAGS-when-linking-libperl.patch
rename to 
meta/recipes-devtools/perl/files/0001-perl-cross-add-LDFLAGS-when-linking-libperl.patch
diff --git a/meta/recipes-devtools/perl-sanity/files/errno_ver.diff 
b/meta/recipes-devtools/perl/files/errno_ver.diff
similarity ind

[OE-core] [PATCH] systat: systemd never enables the service

2019-06-18 Thread Stefano Babic
Even if SYSTEMD_AUTO_ENABLE is set to "enable", the service is never
activated by systemd. The cause is the postinst function in the recipe:

 pkg_postinst_${PN} () {
 if [ -n "$D" ]; then
 exit 0
 fi
 if [ -e /etc/init.d/populate-volatile.sh ]; then
 /etc/init.d/populate-volatile.sh update
 fi
 }

This generates with activated systemd the following postinst script:

set -e
if [ -n "$D" ]; then
exit 0
fi
if [ -e /etc/init.d/populate-volatile.sh ]; then
/etc/init.d/populate-volatile.sh update
fi
OPTS=""

if [ -n "$D" ]; then
OPTS="--root=$D"
fi

if type systemctl >/dev/null 2>/dev/null; then
if [ -z "$D" ]; then
systemctl daemon-reload
fi

systemctl $OPTS enable sysstat.service

if [ -z "$D" -a "enable" = "enable" ]; then
systemctl --no-block restart sysstat.service
fi
fi

Due to the exit statement, systemctl is never called and the service is
never enabled in rootfs.
Invert the logic for the check to let run the rest of postinst script.

Signed-off-by: Stefano Babic 
---
 meta/recipes-extended/sysstat/sysstat.inc | 11 +--
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/meta/recipes-extended/sysstat/sysstat.inc 
b/meta/recipes-extended/sysstat/sysstat.inc
index 0bc7e14d36..850a6d1465 100644
--- a/meta/recipes-extended/sysstat/sysstat.inc
+++ b/meta/recipes-extended/sysstat/sysstat.inc
@@ -51,12 +51,11 @@ do_install() {
 }
 
 pkg_postinst_${PN} () {
-if [ -n "$D" ]; then
-exit 0
-fi
-if [ -e /etc/init.d/populate-volatile.sh ]; then
-/etc/init.d/populate-volatile.sh update
-fi
+   if [  ! -n "$D" ]; then
+   if [ -e /etc/init.d/populate-volatile.sh ]; then
+   /etc/init.d/populate-volatile.sh update
+   fi
+   fi
 }
 
 
-- 
2.17.1

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


Re: [OE-core] [meta-oe,v2] kernel-fitimage: introduce FIT_HASH_ALG

2019-06-18 Thread Luca Boccassi
On Thu, 2017-11-02 at 16:48 +0100, Ayoub Zaki wrote:
> sanitize fitImage hash algorithm selection with FIT_HASH_ALG
> switch default hash algorithm from sha1 to sha256
> 
> Signed-off-by: Ayoub Zaki <
> ayoub.z...@embexus.com
> >
> Acked-by: Denys Dmytriyenko <
> de...@ti.com
> >
> ---
>  meta/classes/kernel-fitimage.bbclass | 13 -
>  1 file changed, 8 insertions(+), 5 deletions(-)
> 
> diff --git a/meta/classes/kernel-fitimage.bbclass
> b/meta/classes/kernel-fitimage.bbclass
> index 179185b..3cc3a33 100644
> --- a/meta/classes/kernel-fitimage.bbclass
> +++ b/meta/classes/kernel-fitimage.bbclass
> @@ -36,6 +36,9 @@ python __anonymous () {
>  # Options for the device tree compiler passed to mkimage '-D'
> feature:
>  UBOOT_MKIMAGE_DTCOPTS ??= ""
>  
> +# fitImage Hash Algo
> +FIT_HASH_ALG ?= "sha256"
> +
>  #
>  # Emit the fitImage ITS header
>  #
> @@ -95,7 +98,7 @@ EOF
>  # $4 ... Compression type
>  fitimage_emit_section_kernel() {
>  
> - kernel_csum="sha1"
> + kernel_csum="${FIT_HASH_ALG}"
>  
>   ENTRYPOINT=${UBOOT_ENTRYPOINT}
>   if [ -n "${UBOOT_ENTRYSYMBOL}" ]; then
> @@ -128,7 +131,7 @@ EOF
>  # $3 ... Path to DTB image
>  fitimage_emit_section_dtb() {
>  
> - dtb_csum="sha1"
> + dtb_csum="${FIT_HASH_ALG}"
>  
>   cat << EOF >> ${1}
>  fdt@${2} {
> @@ -152,7 +155,7 @@ EOF
>  # $3 ... Path to setup image
>  fitimage_emit_section_setup() {
>  
> - setup_csum="sha1"
> + setup_csum="${FIT_HASH_ALG}"
>  
>   cat << EOF >> ${1}
>  setup@${2} {
> @@ -179,7 +182,7 @@ EOF
>  # $3 ... Path to ramdisk image
>  fitimage_emit_section_ramdisk() {
>  
> - ramdisk_csum="sha1"
> + ramdisk_csum="${FIT_HASH_ALG}"
>   ramdisk_ctype="none"
>   ramdisk_loadline=""
>   ramdisk_entryline=""
> @@ -237,7 +240,7 @@ EOF
>  # $6 ... default flag
>  fitimage_emit_section_config() {
>  
> - conf_csum="sha1"
> + conf_csum="${FIT_HASH_ALG}"
>   if [ -n "${UBOOT_SIGN_ENABLE}" ] ; then
>   conf_sign_keyname="${UBOOT_SIGN_KEYNAME}"
>   fi

Hi,

Any update on this patch? It was acked almost 2 years ago.

It would be great to have a way to change the hashsum algorithm when
building signed images.

Thanks!

-- 
Kind regards,
Luca Boccassi

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


Re: [OE-core] [PATCH] toolchain-scripts: make rpm work in toolchain

2019-06-18 Thread Lei, Maohui
ping

> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org [mailto:openembedded-
> core-boun...@lists.openembedded.org] On Behalf Of Lei, Maohui
> Sent: Thursday, June 06, 2019 10:39 AM
> To: richard.pur...@linuxfoundation.org
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH] toolchain-scripts: make rpm work in toolchain
> 
> Hi, Richard
> 
> > Whilst I can guess why, its not obvious at all the dnf needs
> > MACHINE_ARCH. I'd probably be happier with a better variable name.
> > Which code exactly is using it?
> 
> Arch information is necessary for rpm. As what do for dnf-native in
> _configure_rpm function, nativesdk-dnf has to do the same work.
> But the environment for nativesdk doesn't supply arch information. I think
> MACHINE_ARCH is suitable to supply arch information for nativesdk.
> How about your Opinion?
> 
> Best regards
> Lei
> 
> 
> 
> > -Original Message-
> > From: richard.pur...@linuxfoundation.org
> > [mailto:richard.pur...@linuxfoundation.org]
> > Sent: Tuesday, June 04, 2019 6:26 PM
> > To: Lei, Maohui
> > Cc: openembedded-core@lists.openembedded.org
> > Subject: Re: [OE-core] [PATCH] toolchain-scripts: make rpm work in toolchain
> >
> > On Tue, 2019-06-04 at 08:29 +, Lei, Maohui wrote:
> > > Hi Richard
> > >
> > > This patch is necessary for dnf-nativesdk which has been merged. But
> > > this patch is still ignored.
> > > Do you have any comment about this patch?
> >
> > Basically I really don't like exporting "random" variables in the SDK,
> > particularly when the meaning/use of them isn't clear.
> >
> > Whilst I can guess why, its not obvious at all the dnf needs
> > MACHINE_ARCH. I'd probably be happier with a better variable name.
> > Which code exactly is using it?
> >
> > Cheers,
> >
> > Richard
> >
> >
> 
> 
> 
> --
> ___
> 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 v2] openssl: Fix a build bug on aarch64BE.

2019-06-18 Thread Lei, Maohui
Hi

I'm sorry I misunderstood. I have submitted v3 version. Please have a review.


Best regards
Lei

> -Original Message-
> From: ChenQi [mailto:qi.c...@windriver.com]
> Sent: Monday, June 17, 2019 1:17 PM
> To: Lei, Maohui/雷 茂慧; openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH v2] openssl: Fix a build bug on aarch64BE.
> 
> On 06/06/2019 05:46 AM, Lei Maohui wrote:
> > Fix bug as following on aarch64BE:
> >
> > Error: operand 1 must be an integer register -- `rev v31.16b,v31.16b'
> >
> > https://github.com/openssl/openssl/pull/9151
> >
> > Upstream-Status: Submitted
> >
> > Signed-off-by: Lei Maohui 
> > ---
> >   ...01-Fix-build-error-for-aarch64-big-endian.patch | 41
> ++
> >   .../recipes-connectivity/openssl/openssl_1.1.1c.bb |  1 +
> >   2 files changed, 42 insertions(+)
> >   create mode 100644 meta/recipes-connectivity/openssl/openssl/0001-Fix-
> build-error-for-aarch64-big-endian.patch
> >
> > diff --git a/meta/recipes-connectivity/openssl/openssl/0001-Fix-build-error-
> for-aarch64-big-endian.patch b/meta/recipes-connectivity/openssl/openssl/0001-
> Fix-build-error-for-aarch64-big-endian.patch
> > new file mode 100644
> > index 000..65ca02c
> > --- /dev/null
> > +++ b/meta/recipes-connectivity/openssl/openssl/0001-Fix-build-error-for-
> aarch64-big-endian.patch
> > @@ -0,0 +1,41 @@
> > +From 1f8c0f2feea5cdcae0bcd9dfc78198d9e2c4cf09 Mon Sep 17 00:00:00 2001
> > +From: Lei Maohui 
> > +Date: Thu, 13 Jun 2019 12:17:30 +0900
> > +Subject: [PATCH] Fix build error for aarch64 big endian.
> > +
> > +Modified rev to rev64, because rev only takes integer registers.
> > +https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90827
> > +Otherwise, the following error will occur.
> > +
> > +Error: operand 1 must be an integer register -- `rev v31.16b,v31.16b'
> > +
> 
> Put Upstream-Status here.
> 
> Best Regards,
> Chen Qi
> 
> > +Signed-off-by: Lei Maohui 
> > +---
> > + crypto/sha/asm/keccak1600-armv8.pl | 4 ++--
> > + 1 file changed, 2 insertions(+), 2 deletions(-)
> > +
> > +diff --git a/crypto/sha/asm/keccak1600-armv8.pl 
> > b/crypto/sha/asm/keccak1600-
> armv8.pl
> > +index dc72f18..6620690 100755
> > +--- a/crypto/sha/asm/keccak1600-armv8.pl
> >  b/crypto/sha/asm/keccak1600-armv8.pl
> > +@@ -731,7 +731,7 @@ $code.=<<___;
> > +   blo .Lprocess_block_ce
> > +   ldr d31,[$inp],#8   // *inp++
> > + #ifdef__AARCH64EB__
> > +-  rev v31.16b,v31.16b
> > ++  rev64   v31.16b,v31.16b
> > + #endif
> > +   eor $A[$j/5][$j%5],$A[$j/5][$j%5],v31.16b
> > +   beq .Lprocess_block_ce
> > +@@ -740,7 +740,7 @@ ___
> > + $code.=<<___;
> > +   ldr d31,[$inp],#8   // *inp++
> > + #ifdef__AARCH64EB__
> > +-  rev v31.16b,v31.16b
> > ++  rev64   v31.16b,v31.16b
> > + #endif
> > +   eor $A[4][4],$A[4][4],v31.16b
> > +
> > +--
> > +2.7.4
> > +
> > diff --git a/meta/recipes-connectivity/openssl/openssl_1.1.1c.bb
> b/meta/recipes-connectivity/openssl/openssl_1.1.1c.bb
> > index 669b1a1..ec85ccd 100644
> > --- a/meta/recipes-connectivity/openssl/openssl_1.1.1c.bb
> > +++ b/meta/recipes-connectivity/openssl/openssl_1.1.1c.bb
> > @@ -16,6 +16,7 @@ SRC_URI = "http://www.openssl.org/source/openssl-
> ${PV}.tar.gz \
> >  file://0001-skip-test_symbol_presence.patch \
> >  file://0001-buildinfo-strip-sysroot-and-debug-prefix-map-from-
> co.patch \
> >  file://afalg.patch \
> > +   file://0001-Fix-build-error-for-aarch64-big-endian.patch \
> >  "
> >
> >   SRC_URI_append_class-nativesdk = " \
> 
> 
> 



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


[OE-core] [warrior][PATCH v3] openssl: Fix a build bug on aarch64BE.

2019-06-18 Thread Lei Maohui
Fix bug as following on aarch64BE:

Error: operand 1 must be an integer register -- `rev v31.16b,v31.16b'

Signed-off-by: Lei Maohui 
---
 ...01-Fix-build-error-for-aarch64-big-endian.patch | 43 ++
 .../recipes-connectivity/openssl/openssl_1.1.1b.bb |  1 +
 2 files changed, 44 insertions(+)
 create mode 100644 
meta/recipes-connectivity/openssl/openssl/0001-Fix-build-error-for-aarch64-big-endian.patch

diff --git 
a/meta/recipes-connectivity/openssl/openssl/0001-Fix-build-error-for-aarch64-big-endian.patch
 
b/meta/recipes-connectivity/openssl/openssl/0001-Fix-build-error-for-aarch64-big-endian.patch
new file mode 100644
index 000..9a90a68
--- /dev/null
+++ 
b/meta/recipes-connectivity/openssl/openssl/0001-Fix-build-error-for-aarch64-big-endian.patch
@@ -0,0 +1,43 @@
+From 1f8c0f2feea5cdcae0bcd9dfc78198d9e2c4cf09 Mon Sep 17 00:00:00 2001
+From: Lei Maohui 
+Date: Thu, 13 Jun 2019 12:17:30 +0900
+Subject: [PATCH] Fix build error for aarch64 big endian.
+
+Modified rev to rev64, because rev only takes integer registers.
+https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90827
+Otherwise, the following error will occur.
+
+Error: operand 1 must be an integer register -- `rev v31.16b,v31.16b'
+
+Upstream-Status: Submitted [https://github.com/openssl/openssl/pull/9151]
+
+Signed-off-by: Lei Maohui 
+---
+ crypto/sha/asm/keccak1600-armv8.pl | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/crypto/sha/asm/keccak1600-armv8.pl 
b/crypto/sha/asm/keccak1600-armv8.pl
+index dc72f18..6620690 100755
+--- a/crypto/sha/asm/keccak1600-armv8.pl
 b/crypto/sha/asm/keccak1600-armv8.pl
+@@ -731,7 +731,7 @@ $code.=<<___;
+   blo .Lprocess_block_ce
+   ldr d31,[$inp],#8   // *inp++
+ #ifdef__AARCH64EB__
+-  rev v31.16b,v31.16b
++  rev64   v31.16b,v31.16b
+ #endif
+   eor $A[$j/5][$j%5],$A[$j/5][$j%5],v31.16b
+   beq .Lprocess_block_ce
+@@ -740,7 +740,7 @@ ___
+ $code.=<<___;
+   ldr d31,[$inp],#8   // *inp++
+ #ifdef__AARCH64EB__
+-  rev v31.16b,v31.16b
++  rev64   v31.16b,v31.16b
+ #endif
+   eor $A[4][4],$A[4][4],v31.16b
+ 
+-- 
+2.7.4
+
diff --git a/meta/recipes-connectivity/openssl/openssl_1.1.1b.bb 
b/meta/recipes-connectivity/openssl/openssl_1.1.1b.bb
index d3404d2..46030c3 100644
--- a/meta/recipes-connectivity/openssl/openssl_1.1.1b.bb
+++ b/meta/recipes-connectivity/openssl/openssl_1.1.1b.bb
@@ -17,6 +17,7 @@ SRC_URI = "http://www.openssl.org/source/openssl-${PV}.tar.gz 
\

file://0001-buildinfo-strip-sysroot-and-debug-prefix-map-from-co.patch \
file://afalg.patch \
file://CVE-2019-1543.patch \
+   file://0001-Fix-build-error-for-aarch64-big-endian.patch \
"
 
 SRC_URI_append_class-nativesdk = " \
-- 
2.7.4



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


[OE-core] [PATCH v3] openssl: Fix a build bug on aarch64BE.

2019-06-18 Thread Lei Maohui
Fix bug as following on aarch64BE:

Error: operand 1 must be an integer register -- `rev v31.16b,v31.16b'

Signed-off-by: Lei Maohui 
---
 ...01-Fix-build-error-for-aarch64-big-endian.patch | 43 ++
 .../recipes-connectivity/openssl/openssl_1.1.1c.bb |  1 +
 2 files changed, 44 insertions(+)
 create mode 100644 
meta/recipes-connectivity/openssl/openssl/0001-Fix-build-error-for-aarch64-big-endian.patch

diff --git 
a/meta/recipes-connectivity/openssl/openssl/0001-Fix-build-error-for-aarch64-big-endian.patch
 
b/meta/recipes-connectivity/openssl/openssl/0001-Fix-build-error-for-aarch64-big-endian.patch
new file mode 100644
index 000..9a90a68
--- /dev/null
+++ 
b/meta/recipes-connectivity/openssl/openssl/0001-Fix-build-error-for-aarch64-big-endian.patch
@@ -0,0 +1,43 @@
+From 1f8c0f2feea5cdcae0bcd9dfc78198d9e2c4cf09 Mon Sep 17 00:00:00 2001
+From: Lei Maohui 
+Date: Thu, 13 Jun 2019 12:17:30 +0900
+Subject: [PATCH] Fix build error for aarch64 big endian.
+
+Modified rev to rev64, because rev only takes integer registers.
+https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90827
+Otherwise, the following error will occur.
+
+Error: operand 1 must be an integer register -- `rev v31.16b,v31.16b'
+
+Upstream-Status: Submitted [https://github.com/openssl/openssl/pull/9151]
+
+Signed-off-by: Lei Maohui 
+---
+ crypto/sha/asm/keccak1600-armv8.pl | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/crypto/sha/asm/keccak1600-armv8.pl 
b/crypto/sha/asm/keccak1600-armv8.pl
+index dc72f18..6620690 100755
+--- a/crypto/sha/asm/keccak1600-armv8.pl
 b/crypto/sha/asm/keccak1600-armv8.pl
+@@ -731,7 +731,7 @@ $code.=<<___;
+   blo .Lprocess_block_ce
+   ldr d31,[$inp],#8   // *inp++
+ #ifdef__AARCH64EB__
+-  rev v31.16b,v31.16b
++  rev64   v31.16b,v31.16b
+ #endif
+   eor $A[$j/5][$j%5],$A[$j/5][$j%5],v31.16b
+   beq .Lprocess_block_ce
+@@ -740,7 +740,7 @@ ___
+ $code.=<<___;
+   ldr d31,[$inp],#8   // *inp++
+ #ifdef__AARCH64EB__
+-  rev v31.16b,v31.16b
++  rev64   v31.16b,v31.16b
+ #endif
+   eor $A[4][4],$A[4][4],v31.16b
+ 
+-- 
+2.7.4
+
diff --git a/meta/recipes-connectivity/openssl/openssl_1.1.1c.bb 
b/meta/recipes-connectivity/openssl/openssl_1.1.1c.bb
index 669b1a1..ec85ccd 100644
--- a/meta/recipes-connectivity/openssl/openssl_1.1.1c.bb
+++ b/meta/recipes-connectivity/openssl/openssl_1.1.1c.bb
@@ -16,6 +16,7 @@ SRC_URI = "http://www.openssl.org/source/openssl-${PV}.tar.gz 
\
file://0001-skip-test_symbol_presence.patch \

file://0001-buildinfo-strip-sysroot-and-debug-prefix-map-from-co.patch \
file://afalg.patch \
+   file://0001-Fix-build-error-for-aarch64-big-endian.patch \
"
 
 SRC_URI_append_class-nativesdk = " \
-- 
2.7.4



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


[OE-core] [PATCH] buildhistory: show time spent writting buildhistory

2019-06-18 Thread Martin Jansa
* especially when pushing longer history to slow remote git server or when
  it timeouts during the push, it's useful to see where the time was actually
  spent

Signed-off-by: Martin Jansa 
---
 meta/classes/buildhistory.bbclass | 4 
 1 file changed, 4 insertions(+)

diff --git a/meta/classes/buildhistory.bbclass 
b/meta/classes/buildhistory.bbclass
index 34709f3f88..e4e1897318 100644
--- a/meta/classes/buildhistory.bbclass
+++ b/meta/classes/buildhistory.bbclass
@@ -841,11 +841,15 @@ python buildhistory_eventhandler() {
 if e.data.getVar("BUILDHISTORY_COMMIT") == "1":
 bb.note("Writing buildhistory")
 bb.build.exec_func("buildhistory_write_sigs", d)
+import time
+start=time.time()
 localdata = bb.data.createCopy(e.data)
 localdata.setVar('BUILDHISTORY_BUILD_FAILURES', 
str(e._failures))
 interrupted = getattr(e, '_interrupted', 0)
 localdata.setVar('BUILDHISTORY_BUILD_INTERRUPTED', 
str(interrupted))
 bb.build.exec_func("buildhistory_commit", localdata)
+stop=time.time()
+bb.note("Writing buildhistory took: %s seconds" % 
round(stop-start))
 else:
 bb.note("No commit since BUILDHISTORY_COMMIT != '1'")
 }
-- 
2.17.1

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


[OE-core] [PATCH] kernel: qemuarmv5: Update machine overrides of KERNEL_DEVICETREE

2019-06-18 Thread zhe.he
From: He Zhe 

The original BSP qemuarm has been renamed to qemuarmv5. Update the machine
overrides accordingly to avoid not generating dtb.

Signed-off-by: He Zhe 
---
 meta/recipes-kernel/linux/linux-yocto-dev.bb   | 2 +-
 meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb   | 2 +-
 meta/recipes-kernel/linux/linux-yocto-rt_5.0.bb| 2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.19.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_5.0.bb  | 2 +-
 meta/recipes-kernel/linux/linux-yocto_4.19.bb  | 2 +-
 meta/recipes-kernel/linux/linux-yocto_5.0.bb   | 1 -
 7 files changed, 6 insertions(+), 7 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-dev.bb 
b/meta/recipes-kernel/linux/linux-yocto-dev.bb
index 3a055c1..8c83620 100644
--- a/meta/recipes-kernel/linux/linux-yocto-dev.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-dev.bb
@@ -41,7 +41,7 @@ DEPENDS += "openssl-native util-linux-native"
 
 COMPATIBLE_MACHINE = "(qemuarm|qemux86|qemuppc|qemumips|qemumips64|qemux86-64)"
 
-KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
+KERNEL_DEVICETREE_qemuarmv5 = "versatile-pb.dtb"
 
 # Functionality flags
 KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc 
features/taskstats/taskstats.scc"
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb
index 0836dc7..a4facfe 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb
@@ -33,7 +33,7 @@ LINUX_KERNEL_TYPE = "preempt-rt"
 
 COMPATIBLE_MACHINE = 
"(qemux86|qemux86-64|qemuarm|qemuarmv5|qemuarm64|qemuppc|qemumips)"
 
-KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
+KERNEL_DEVICETREE_qemuarmv5 = "versatile-pb.dtb"
 
 # Functionality flags
 KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc 
features/taskstats/taskstats.scc"
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.0.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_5.0.bb
index b5e415f..8bd9d74 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.0.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.0.bb
@@ -33,7 +33,7 @@ LINUX_KERNEL_TYPE = "preempt-rt"
 
 COMPATIBLE_MACHINE = 
"(qemux86|qemux86-64|qemuarm|qemuarmv5|qemuarm64|qemuppc|qemumips)"
 
-KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
+KERNEL_DEVICETREE_qemuarmv5 = "versatile-pb.dtb"
 
 # Functionality flags
 KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc 
features/taskstats/taskstats.scc"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.19.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_4.19.bb
index 4ca11d7..e668854 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.19.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.19.bb
@@ -29,4 +29,4 @@ COMPATIBLE_MACHINE = "qemux86|qemux86-64|qemuarm|qemuarmv5"
 # Functionality flags
 KERNEL_FEATURES = ""
 
-KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
+KERNEL_DEVICETREE_qemuarmv5 = "versatile-pb.dtb"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.0.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_5.0.bb
index a9c463c..226a90c 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.0.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.0.bb
@@ -29,4 +29,4 @@ COMPATIBLE_MACHINE = "qemux86|qemux86-64|qemuarm|qemuarmv5"
 # Functionality flags
 KERNEL_FEATURES = ""
 
-KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
+KERNEL_DEVICETREE_qemuarmv5 = "versatile-pb.dtb"
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.19.bb 
b/meta/recipes-kernel/linux/linux-yocto_4.19.bb
index cda4ecf..014d689 100644
--- a/meta/recipes-kernel/linux/linux-yocto_4.19.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_4.19.bb
@@ -36,7 +36,7 @@ PV = "${LINUX_VERSION}+git${SRCPV}"
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
+KERNEL_DEVICETREE_qemuarmv5 = "versatile-pb.dtb"
 
 COMPATIBLE_MACHINE = 
"qemuarm|qemuarmv5|qemuarm64|qemux86|qemuppc|qemumips|qemumips64|qemux86-64"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.0.bb 
b/meta/recipes-kernel/linux/linux-yocto_5.0.bb
index 8aec315..bb7ed56 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.0.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.0.bb
@@ -38,7 +38,6 @@ PV = "${LINUX_VERSION}+git${SRCPV}"
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
 KERNEL_DEVICETREE_qemuarmv5 = "versatile-pb.dtb"
 
 COMPATIBLE_MACHINE = 
"qemuarm|qemuarmv5|qemuarm64|qemux86|qemuppc|qemumips|qemumips64|qemux86-64"
-- 
2.7.4

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


[OE-core] [PATCH V3] gcc-runtime: fix C++ header mapping for n32/x32 tune

2019-06-18 Thread changqing.li
From: Changqing Li 

The SDK was unable to find the C++ header pieces correctly since it's
using a generic compiler, not one specifically targeting the multilib
vendor prefix and default tune.  This adds the right mapping to ensure
SDKs work as expected. And fix problem in below configurations:

multilib configuration 1:
MACHINE="qemumips64"
MULTILIBS ?= "multilib:lib32 multilib:libn32"
DEFAULTTUNE_virtclass-multilib-lib32 ?= "mips"
DEFAULTTUNE_virtclass-multilib-libn32 ?= "mips64-n32"
MULTILIB_GLOBAL_VARIANTS_append = " libn32"
require conf/multilib.conf

ignoring nonexistent directory 
"/sysroots/mips64-poky-linux/usr/include/c++/8.2.0/mips64-poky-linux/32

multilib configuration 2:
MACHINE="qemumips64"
MULTILIBS = 'multilib:lib64 multilib:lib32'
DEFAULTTUNE = 'mips64-n32'
DEFAULTTUNE_virtclass-multilib-lib64 = 'mips64'
DEFAULTTUNE_virtclass-multilib-lib32 = 'mips32r2'
require conf/multilib.conf

For this configuration:
for target gcc-runtime, need to create symlink like mips64-poly-linux --> 
mips64-poky-linux-gnu32
for target lib64-gcc-runtime, need to create symlink like mips64-poly-linux/32 
--> mips64-pokymllib64-linux
in order to avoid conflict during populate_sdk, create symlink for subfoler 
bits/ext for target gcc-runtime,
this is ugly, but seems no better way to cover all kinds of configuration.

single lib configuration:
MACHINE="qemumips64"
DEFAULTTUNE = "mips64-n32"

Signed-off-by: Changqing Li 
---
 meta/recipes-devtools/gcc/gcc-runtime.inc | 29 +
 1 file changed, 17 insertions(+), 12 deletions(-)

diff --git a/meta/recipes-devtools/gcc/gcc-runtime.inc 
b/meta/recipes-devtools/gcc/gcc-runtime.inc
index 3d03d8e..ba767e1 100644
--- a/meta/recipes-devtools/gcc/gcc-runtime.inc
+++ b/meta/recipes-devtools/gcc/gcc-runtime.inc
@@ -86,10 +86,6 @@ do_install () {
if [ -d ${D}${infodir} ]; then
rmdir --ignore-fail-on-non-empty -p ${D}${infodir}
fi
-   if [ "${TARGET_VENDOR_MULTILIB_ORIGINAL}" != "" -a "${TARGET_VENDOR}" 
!= "${TARGET_VENDOR_MULTILIB_ORIGINAL}" ]; then
-   ln -s ${TARGET_SYS} 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR_MULTILIB_ORIGINAL}-${TARGET_OS}
-   fi
-
 }
 
 do_install_append_class-target () {
@@ -98,20 +94,29 @@ do_install_append_class-target () {
fi
 
if [ "${TARGET_OS}" = "linux-gnun32" ]; then
-   if [ "${MULTILIBS}" != "" ]; then
-   mkdir 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}-pokymllib64-linux
-   ln -s ../${TARGET_SYS} 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}-pokymllib64-linux/32
+   if [ "${TARGET_VENDOR_MULTILIB_ORIGINAL}" != "" -a 
"${TARGET_VENDOR}" != "${TARGET_VENDOR_MULTILIB_ORIGINAL}" ]; then
+   mkdir 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR_MULTILIB_ORIGINAL}-linux
+   ln -s ../${TARGET_SYS} 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR_MULTILIB_ORIGINAL}-linux/32
+   elif [ "${MULTILIB_VARIANTS}" != "" ]; then
+   mkdir 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR}-linux
+   ln -s ../${TARGET_SYS} 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR}-linux/32
else
ln -s ${TARGET_SYS} 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR}-linux
fi
-   fi
-   if [ "${TARGET_OS}" = "linux-gnux32" ]; then
-   if [ "${MULTILIBS}" != "" ]; then
-   mkdir 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}-poky-linux
-   ln -s ../${TARGET_SYS} 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}-poky-linux/x32
+   elif [ "${TARGET_OS}" = "linux-gnux32" ]; then
+   if [ "${TARGET_VENDOR_MULTILIB_ORIGINAL}" != "" -a 
"${TARGET_VENDOR}" != "${TARGET_VENDOR_MULTILIB_ORIGINAL}" ]; then
+   mkdir 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR_MULTILIB_ORIGINAL}-linux
+   ln -s ../${TARGET_SYS} 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR_MULTILIB_ORIGINAL}-linux/x32
+   elif [ "${MULTILIB_VARIANTS}" != "" ]; then
+   mkdir 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR}-linux
+   ln -s ../${TARGET_SYS} 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR}-linux/32
else
ln -s ${TARGET_SYS} 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR}-linux
fi
+   elif [ "${TARGET_VENDOR_MULTILIB_ORIGINAL}" != "" -a "${TARGET_VENDOR}" 
!= "${TARGET_VENDOR_MULTILIB_ORIGINAL}" ]; then
+   mkdir 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR_MULTILIB_ORIGINAL}-linux
+   ln -s ../${TARGET_SYS}/bits 
${D}${includedir}/c++/${BINV}/${TARGET_ARCH}${TARGET_VENDOR_MULTILIB_ORIGINAL}-${TARG