Re: [OE-core] [PATCH] goarch.bbclass: set SECURITY_CFLAGS for mips64

2018-06-13 Thread Kang Kai

On 2018年06月14日 11:33, Khem Raj wrote:



On 6/13/18 8:15 PM, Kang Kai wrote:

On 2018年06月13日 22:01, Khem Raj wrote:

On Wed, Jun 13, 2018 at 12:16 AM  wrote:

From: Kai Kang 

When include conf/distro/include/security_flags.inc, NOPIE flags are
still required for MIPS64 target builds. Otherwise it fails to build
packages such as glide which inherit go.bbclass:

| 
.../tmp-glibc/work/mips64-wrs-linux/glide/0.13.1-r0/recipe-sysroot-native/usr/bin/mips64-wrs-linux/../../libexec/mips64-wrs-linux/ 

| gcc/mips64-wrs-linux/7.3.0/ld: 
.../tmp-glibc/work/mips64-wrs-linux/glide/0.13.1-r0/go-tmp/go-link-518447869/go.o: 

| relocation R_MIPS_26 against `a local symbol' can not be used 
when making a shared object; recompile with -fPIC`


Signed-off-by: Kai Kang 
---
  meta/classes/goarch.bbclass | 1 +
  1 file changed, 1 insertion(+)

diff --git a/meta/classes/goarch.bbclass b/meta/classes/goarch.bbclass
index f54c5169e3e..5fd9f294a8a 100644
--- a/meta/classes/goarch.bbclass
+++ b/meta/classes/goarch.bbclass
@@ -36,6 +36,7 @@ COMPATIBLE_HOST_mipsarchn32 = "null"
  ARM_INSTRUCTION_SET = "arm"
  TUNE_CCARGS_remove = "-march=mips32r2"
  SECURITY_CFLAGS_mips = "${SECURITY_NOPIE_CFLAGS}"
+SECURITY_CFLAGS_mips64 = "${SECURITY_NOPIE_CFLAGS}"

perhaps we should use _mipsall once

Hi Khem,

I don't quite follow you. It seems no such override '_mipsall' 
exists. Do you mean 'mipsarch' or something else? Thanks.




yes mipsarch indeed.


Thanks. V2 will be sent.

--Kai



Regards,
Kai



  SECURITY_NOPIE_CFLAGS ??= ""

  def go_map_arch(a, d):
--
2.17.1

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







--
Regards,
Neil | Kai Kang

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


[OE-core] [PATCH 1/1] oeqa/runtime/cases/rpm.py: change to use base-passwd-doc

2018-06-13 Thread Chen Qi
The test cases assume that rpm-doc is built out, as it says it its
comment. This is not always true. And it sometimes results in
following error.

  | cls.tc.target.copyTo(test_file, dst)
  | UnboundLocalError: local variable 'test_file' referenced before assignment

Change to use base-passwd-doc, as this package is more likely to be
built out than rpm-doc.

Signed-off-by: Chen Qi 
---
 meta/lib/oeqa/runtime/cases/rpm.py | 26 +-
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/meta/lib/oeqa/runtime/cases/rpm.py 
b/meta/lib/oeqa/runtime/cases/rpm.py
index 58df28b..1e5e463 100644
--- a/meta/lib/oeqa/runtime/cases/rpm.py
+++ b/meta/lib/oeqa/runtime/cases/rpm.py
@@ -39,31 +39,31 @@ class RpmInstallRemoveTest(OERuntimeTestCase):
 
 pkgarch = cls.td['TUNE_PKGARCH'].replace('-', '_')
 rpmdir = os.path.join(cls.tc.td['DEPLOY_DIR'], 'rpm', pkgarch)
-# Pick rpm-doc as a test file to get installed, because it's small
+# Pick base-passwd-doc as a test file to get installed, because it's 
small
 # and it will always be built for standard targets
-rpm_doc = 'rpm-doc-*.%s.rpm' % pkgarch
+rpm_doc = 'base-passwd-doc-*.%s.rpm' % pkgarch
 for f in fnmatch.filter(os.listdir(rpmdir), rpm_doc):
 test_file = os.path.join(rpmdir, f)
-dst = '/tmp/rpm-doc.rpm'
+dst = '/tmp/base-passwd-doc.rpm'
 cls.tc.target.copyTo(test_file, dst)
 
 @classmethod
 def tearDownClass(cls):
-dst = '/tmp/rpm-doc.rpm'
+dst = '/tmp/base-passwd-doc.rpm'
 cls.tc.target.run('rm -f %s' % dst)
 
 @OETestID(192)
 @OETestDepends(['rpm.RpmBasicTest.test_rpm_help'])
 def test_rpm_install(self):
-status, output = self.target.run('rpm -ivh /tmp/rpm-doc.rpm')
-msg = 'Failed to install rpm-doc package: %s' % output
+status, output = self.target.run('rpm -ivh /tmp/base-passwd-doc.rpm')
+msg = 'Failed to install base-passwd-doc package: %s' % output
 self.assertEqual(status, 0, msg=msg)
 
 @OETestID(194)
 @OETestDepends(['rpm.RpmInstallRemoveTest.test_rpm_install'])
 def test_rpm_remove(self):
-status,output = self.target.run('rpm -e rpm-doc')
-msg = 'Failed to remove rpm-doc package: %s' % output
+status,output = self.target.run('rpm -e base-passwd-doc')
+msg = 'Failed to remove base-passwd-doc package: %s' % output
 self.assertEqual(status, 0, msg=msg)
 
 @OETestID(1096)
@@ -119,16 +119,16 @@ class RpmInstallRemoveTest(OERuntimeTestCase):
 self.assertEqual(0, status, msg=msg)
 
 # Remove the package just in case
-self.target.run('rpm -e rpm-doc')
+self.target.run('rpm -e base-passwd-doc')
 
 # Install/Remove a package 10 times
 for i in range(10):
-status, output = self.target.run('rpm -ivh /tmp/rpm-doc.rpm')
-msg = 'Failed to install rpm-doc package. Reason: 
{}'.format(output)
+status, output = self.target.run('rpm -ivh 
/tmp/base-passwd-doc.rpm')
+msg = 'Failed to install base-passwd-doc package. Reason: 
{}'.format(output)
 self.assertEqual(0, status, msg=msg)
 
-status, output = self.target.run('rpm -e rpm-doc')
-msg = 'Failed to remove rpm-doc package. Reason: {}'.format(output)
+status, output = self.target.run('rpm -e base-passwd-doc')
+msg = 'Failed to remove base-passwd-doc package. Reason: 
{}'.format(output)
 self.assertEqual(0, status, msg=msg)
 
 # if using systemd this should ensure all entries are flushed to /var
-- 
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] oeqa/runtime/cases/rpm.py: change to use base-passwd-doc

2018-06-13 Thread Chen Qi
The following changes since commit ddbd7b0cd6580ee26e11aa87e426fb294b372d64:

  meta-yocto-bsp: bump to the latest linux stable kernel for 
edgerouter/beaglebone (2018-06-12 23:34:40 +0100)

are available in the git repository at:

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

Chen Qi (1):
  oeqa/runtime/cases/rpm.py: change to use base-passwd-doc

 meta/lib/oeqa/runtime/cases/rpm.py | 26 +-
 1 file changed, 13 insertions(+), 13 deletions(-)

-- 
1.9.1

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


[OE-core] [PATCH][sumo] Qemu: CVE-2018-11806 slirp-heap-buffer-overflow

2018-06-13 Thread Jeremy Puhlman
Signed-off-by: Jeremy Puhlman 
---
 ...018-11806-QEMU-slirp-heap-buffer-overflow.patch | 65 ++
 meta/recipes-devtools/qemu/qemu_2.11.1.bb  |  1 +
 2 files changed, 66 insertions(+)
 create mode 100644 
meta/recipes-devtools/qemu/qemu/0001-CVE-2018-11806-QEMU-slirp-heap-buffer-overflow.patch

diff --git 
a/meta/recipes-devtools/qemu/qemu/0001-CVE-2018-11806-QEMU-slirp-heap-buffer-overflow.patch
 
b/meta/recipes-devtools/qemu/qemu/0001-CVE-2018-11806-QEMU-slirp-heap-buffer-overflow.patch
new file mode 100644
index 00..002a1332bf
--- /dev/null
+++ 
b/meta/recipes-devtools/qemu/qemu/0001-CVE-2018-11806-QEMU-slirp-heap-buffer-overflow.patch
@@ -0,0 +1,65 @@
+From dc21a9d2951f0a2a7e63633e2b5c68c54e4edc4b Mon Sep 17 00:00:00 2001
+From: Jeremy Puhlman 
+Date: Thu, 14 Jun 2018 01:28:49 +
+Subject: [PATCH] CVE-2018-11806 QEMU: slirp: heap buffer overflow
+
+Subject: [Qemu-devel] [PATCH 1/2] slirp: correct size computation while 
concatenating mbuf
+Date:  Tue, 5 Jun 2018 23:38:35 +0530
+From: Prasad J Pandit 
+
+While reassembling incoming fragmented datagrams, 'm_cat' routine
+extends the 'mbuf' buffer, if it has insufficient room. It computes
+a wrong buffer size, which leads to overwriting adjacent heap buffer
+area. Correct this size computation in m_cat.
+
+Reported-by: ZDI Disclosures 
+Signed-off-by: Prasad J Pandit 
+---
+ slirp/mbuf.c | 8 
+ 1 file changed, 4 insertions(+), 4 deletions(-)
+
+Signed-off-by: Jeremy Puhlman 
+---
+ slirp/mbuf.c | 8 
+ 1 file changed, 4 insertions(+), 4 deletions(-)
+
+diff --git a/slirp/mbuf.c b/slirp/mbuf.c
+index 5ff2455..7fb4501 100644
+--- a/slirp/mbuf.c
 b/slirp/mbuf.c
+@@ -138,7 +138,7 @@ m_cat(struct mbuf *m, struct mbuf *n)
+* If there's no room, realloc
+*/
+   if (M_FREEROOM(m) < n->m_len)
+-  m_inc(m,m->m_size+MINCSIZE);
++   m_inc(m, m->m_len + n->m_len);
+ 
+   memcpy(m->m_data+m->m_len, n->m_data, n->m_len);
+   m->m_len += n->m_len;
+@@ -158,12 +158,12 @@ m_inc(struct mbuf *m, int size)
+ 
+ if (m->m_flags & M_EXT) {
+ datasize = m->m_data - m->m_ext;
+-  m->m_ext = g_realloc(m->m_ext, size);
++  m->m_ext = g_realloc(m->m_ext, size + datasize);
+ m->m_data = m->m_ext + datasize;
+ } else {
+ char *dat;
+ datasize = m->m_data - m->m_dat;
+-  dat = g_malloc(size);
++  dat = g_malloc(size + datasize);
+ memcpy(dat, m->m_dat, m->m_size);
+ 
+ m->m_ext = dat;
+@@ -171,7 +171,7 @@ m_inc(struct mbuf *m, int size)
+ m->m_flags |= M_EXT;
+ }
+ 
+-m->m_size = size;
++m->m_size = size + datasize;
+ 
+ }
+ 
+-- 
+2.13.3
+
diff --git a/meta/recipes-devtools/qemu/qemu_2.11.1.bb 
b/meta/recipes-devtools/qemu/qemu_2.11.1.bb
index f4b7d69fca..5dc3934f62 100644
--- a/meta/recipes-devtools/qemu/qemu_2.11.1.bb
+++ b/meta/recipes-devtools/qemu/qemu_2.11.1.bb
@@ -22,6 +22,7 @@ SRC_URI = 
"http://wiki.qemu-project.org/download/${BP}.tar.bz2 \
file://linux-user-Fix-webkitgtk-hangs-on-32-bit-x86-target.patch \
file://memfd.patch \

file://0001-arm-translate-a64-treat-DISAS_UPDATE-as-variant-of-D.patch \
+   file://0001-CVE-2018-11806-QEMU-slirp-heap-buffer-overflow.patch \
"
 UPSTREAM_CHECK_REGEX = "qemu-(?P\d+\..*)\.tar"
 
-- 
2.14.1.459.g238e487

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


[OE-core] [PATCH][rocko] Qemu CVE-2018-11806 slirp-heap-buffer-overflow

2018-06-13 Thread Jeremy Puhlman
Signed-off-by: Jeremy Puhlman 
---
 ...018-11806-QEMU-slirp-heap-buffer-overflow.patch | 69 ++
 meta/recipes-devtools/qemu/qemu_2.10.0.bb  |  1 +
 2 files changed, 70 insertions(+)
 create mode 100644 
meta/recipes-devtools/qemu/qemu/0001-CVE-2018-11806-QEMU-slirp-heap-buffer-overflow.patch

diff --git 
a/meta/recipes-devtools/qemu/qemu/0001-CVE-2018-11806-QEMU-slirp-heap-buffer-overflow.patch
 
b/meta/recipes-devtools/qemu/qemu/0001-CVE-2018-11806-QEMU-slirp-heap-buffer-overflow.patch
new file mode 100644
index 00..6a518b48dc
--- /dev/null
+++ 
b/meta/recipes-devtools/qemu/qemu/0001-CVE-2018-11806-QEMU-slirp-heap-buffer-overflow.patch
@@ -0,0 +1,69 @@
+Upstream-status: Backport
+
+https://lists.gnu.org/archive/html/qemu-devel/2018-06/msg01012.html
+
+From dc21a9d2951f0a2a7e63633e2b5c68c54e4edc4b Mon Sep 17 00:00:00 2001
+From: Jeremy Puhlman 
+Date: Thu, 14 Jun 2018 01:28:49 +
+Subject: [PATCH] CVE-2018-11806 QEMU: slirp: heap buffer overflow
+
+Subject: [Qemu-devel] [PATCH 1/2] slirp: correct size computation while 
concatenating mbuf
+Date:  Tue, 5 Jun 2018 23:38:35 +0530
+From: Prasad J Pandit 
+
+While reassembling incoming fragmented datagrams, 'm_cat' routine
+extends the 'mbuf' buffer, if it has insufficient room. It computes
+a wrong buffer size, which leads to overwriting adjacent heap buffer
+area. Correct this size computation in m_cat.
+
+Reported-by: ZDI Disclosures 
+Signed-off-by: Prasad J Pandit 
+---
+ slirp/mbuf.c | 8 
+ 1 file changed, 4 insertions(+), 4 deletions(-)
+
+Signed-off-by: Jeremy Puhlman 
+---
+ slirp/mbuf.c | 8 
+ 1 file changed, 4 insertions(+), 4 deletions(-)
+
+diff --git a/slirp/mbuf.c b/slirp/mbuf.c
+index 5ff2455..7fb4501 100644
+--- a/slirp/mbuf.c
 b/slirp/mbuf.c
+@@ -138,7 +138,7 @@ m_cat(struct mbuf *m, struct mbuf *n)
+* If there's no room, realloc
+*/
+   if (M_FREEROOM(m) < n->m_len)
+-  m_inc(m,m->m_size+MINCSIZE);
++   m_inc(m, m->m_len + n->m_len);
+ 
+   memcpy(m->m_data+m->m_len, n->m_data, n->m_len);
+   m->m_len += n->m_len;
+@@ -158,12 +158,12 @@ m_inc(struct mbuf *m, int size)
+ 
+ if (m->m_flags & M_EXT) {
+ datasize = m->m_data - m->m_ext;
+-  m->m_ext = g_realloc(m->m_ext, size);
++  m->m_ext = g_realloc(m->m_ext, size + datasize);
+ m->m_data = m->m_ext + datasize;
+ } else {
+ char *dat;
+ datasize = m->m_data - m->m_dat;
+-  dat = g_malloc(size);
++  dat = g_malloc(size + datasize);
+ memcpy(dat, m->m_dat, m->m_size);
+ 
+ m->m_ext = dat;
+@@ -171,7 +171,7 @@ m_inc(struct mbuf *m, int size)
+ m->m_flags |= M_EXT;
+ }
+ 
+-m->m_size = size;
++m->m_size = size + datasize;
+ 
+ }
+ 
+-- 
+2.13.3
+
diff --git a/meta/recipes-devtools/qemu/qemu_2.10.0.bb 
b/meta/recipes-devtools/qemu/qemu_2.10.0.bb
index bdf6c21f87..89c68f272e 100644
--- a/meta/recipes-devtools/qemu/qemu_2.10.0.bb
+++ b/meta/recipes-devtools/qemu/qemu_2.10.0.bb
@@ -30,6 +30,7 @@ SRC_URI = 
"http://wiki.qemu-project.org/download/${BP}.tar.bz2 \
file://CVE-2017-14167.patch \
file://ppc_locking.patch \
file://memfd.patch \
+   file://0001-CVE-2018-11806-QEMU-slirp-heap-buffer-overflow.patch \
"
 UPSTREAM_CHECK_REGEX = "qemu-(?P\d+\..*)\.tar"
 
-- 
2.14.1.459.g238e487

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


Re: [OE-core] [PATCH] meta-toolchain: Added dnf-nativesdk into cross-development toolchain.

2018-06-13 Thread Zheng, Ruoqin
Hi Ross:

I submitted this patch aim to use dnf out of Yocto build system to manage 
packages.
So I need to add dnf-nativesdk into cross-development toolchain.

My plan is as following:
Step 1. Add dnf-nativesdk into cross-development toolchain to support using dnf 
command line.
Step 2. Add  Text-based UI for dnf to make it more flexible and user friendly.

Finally, about the usage of dnf-nativesdk, please reference to 
https://github.com/ubinux/dnf/tree/dnf-yocto2.5 .

In V2 patch, I will split V1 patch up into multiple patches.

I'm glad to hear your advice.

--
Zheng Ruoqin
Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST)
ADDR.: No.6 Wenzhu Road, Software Avenue,
   Nanjing, 210012, China
MAIL : zhengrq.f...@cn.fujistu.com


-Original Message-
From: Burton, Ross [mailto:ross.bur...@intel.com] 
Sent: Monday, June 11, 2018 5:56 PM
To: Zheng, Ruoqin/郑 若钦 
Cc: OE-core 
Subject: Re: [OE-core] [PATCH] meta-toolchain: Added dnf-nativesdk into 
cross-development toolchain.

Please split this up into multiple patches: slang, libnewt, etc.  Also what's 
the use-case for using a nativesdk-dnf?  How is that useful?

Ross

On 28 May 2018 at 11:20, Zheng Ruoqin  wrote:
> To make dnf work on cross-development environment.
>
> Signed-off-by: Zheng Ruoqin 
> ---
>  meta/classes/toolchain-scripts.bbclass |  1 +
>  .../nativesdk-packagegroup-sdk-host.bb |  4 +++
>  meta/recipes-core/update-rc.d/update-rc.d_0.7.bb   |  2 +-
>  .../createrepo-c/createrepo-c_git.bb   |  7 -
>  meta/recipes-devtools/file/file_5.32.bb|  2 ++
>  meta/recipes-devtools/rpm/rpm_4.14.1.bb| 34 
> ++
>  .../newt/libnewt-python_0.52.20.bb |  2 +-
>  meta/recipes-extended/newt/libnewt_0.52.20.bb  |  2 +-
>  meta/recipes-extended/slang/slang_2.3.2.bb |  2 +-
>  9 files changed, 46 insertions(+), 10 deletions(-)
>
> diff --git a/meta/classes/toolchain-scripts.bbclass 
> b/meta/classes/toolchain-scripts.bbclass
> index 71da5e5..58dd00e 100644
> --- a/meta/classes/toolchain-scripts.bbclass
> +++ b/meta/classes/toolchain-scripts.bbclass
> @@ -97,6 +97,7 @@ toolchain_shared_env_script () {
> echo 'export CPPFLAGS="${TARGET_CPPFLAGS}"' >> $script
> echo 'export KCFLAGS="--sysroot=$SDKTARGETSYSROOT"' >> $script
> echo 'export OECORE_DISTRO_VERSION="${DISTRO_VERSION}"' >> 
> $script
> +echo 'export MACHINE_ARCH=${MACHINE_ARCH}' >> $script
> echo 'export OECORE_SDK_VERSION="${SDK_VERSION}"' >> $script
> echo 'export ARCH=${ARCH}' >> $script
> echo 'export CROSS_COMPILE=${TARGET_PREFIX}' >> $script diff 
> --git 
> a/meta/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bb 
> b/meta/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bb
> index e2f6169..1370a82 100644
> --- 
> a/meta/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bb
> +++ b/meta/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.
> +++ bb
> @@ -25,6 +25,10 @@ RDEPENDS_${PN} = "\
>  nativesdk-cmake \
>  ${@bb.utils.contains('DISTRO_FEATURES', 'wayland', 'nativesdk-wayland', 
> '', d)} \
>  nativesdk-sdk-provides-dummy \
> +nativesdk-libnewt-python \
> +nativesdk-createrepo-c \
> +nativesdk-gpgme \
> +nativesdk-update-rc.d \
>  "
>
>  RDEPENDS_${PN}_darwin = "\
> diff --git a/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb 
> b/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb
> index 76d4312..d3d3e2f 100644
> --- a/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb
> +++ b/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb
> @@ -30,4 +30,4 @@ do_install() {
> install -m 0755 ${S}/update-rc.d ${D}${sbindir}/update-rc.d  }
>
> -BBCLASSEXTEND = "native"
> +BBCLASSEXTEND = "native nativesdk"
> diff --git a/meta/recipes-devtools/createrepo-c/createrepo-c_git.bb 
> b/meta/recipes-devtools/createrepo-c/createrepo-c_git.bb
> index 3176136..9be9f9e 100644
> --- a/meta/recipes-devtools/createrepo-c/createrepo-c_git.bb
> +++ b/meta/recipes-devtools/createrepo-c/createrepo-c_git.bb
> @@ -21,7 +21,7 @@ inherit cmake pkgconfig bash-completion 
> distutils3-base
>
>  EXTRA_OECMAKE = " -DPYTHON_INSTALL_DIR=${PYTHON_SITEPACKAGES_DIR} 
> -DPYTHON_DESIRED=3"
>
> -BBCLASSEXTEND = "native"
> +BBCLASSEXTEND = "native nativesdk"
>
>  # Direct createrepo to read rpm configuration from our sysroot, not 
> the one it was compiled in
>  do_install_append_class-native() {
> @@ -29,3 +29,8 @@ do_install_append_class-native() {
>  RPM_CONFIGDIR=${STAGING_LIBDIR_NATIVE}/rpm
>  }
>
> +do_install_append_class-nativesdk() {
> +create_wrapper ${D}/${bindir}/createrepo_c \
> +RPM_CONFIGDIR=${SDKPATHNATIVE}${libdir_nativesdk}/rpm
> +rm -rf ${D}/etc
> +}
> diff --git a/meta/recipes-devtools/file/file_5.32.bb 
> b/meta/recipes-devtools/file/file_5.32.bb
> index 5e15925..9b13261 100644
> 

[OE-core] [PATCH] Qemu: CVE-2018-11806 slirp heap buffer overflow

2018-06-13 Thread Jeremy Puhlman
---
 ...018-11806-QEMU-slirp-heap-buffer-overflow.patch | 65 ++
 meta/recipes-devtools/qemu/qemu_2.12.0.bb  |  1 +
 2 files changed, 66 insertions(+)
 create mode 100644 
meta/recipes-devtools/qemu/qemu/0001-CVE-2018-11806-QEMU-slirp-heap-buffer-overflow.patch

diff --git 
a/meta/recipes-devtools/qemu/qemu/0001-CVE-2018-11806-QEMU-slirp-heap-buffer-overflow.patch
 
b/meta/recipes-devtools/qemu/qemu/0001-CVE-2018-11806-QEMU-slirp-heap-buffer-overflow.patch
new file mode 100644
index 00..002a1332bf
--- /dev/null
+++ 
b/meta/recipes-devtools/qemu/qemu/0001-CVE-2018-11806-QEMU-slirp-heap-buffer-overflow.patch
@@ -0,0 +1,65 @@
+From dc21a9d2951f0a2a7e63633e2b5c68c54e4edc4b Mon Sep 17 00:00:00 2001
+From: Jeremy Puhlman 
+Date: Thu, 14 Jun 2018 01:28:49 +
+Subject: [PATCH] CVE-2018-11806 QEMU: slirp: heap buffer overflow
+
+Subject: [Qemu-devel] [PATCH 1/2] slirp: correct size computation while 
concatenating mbuf
+Date:  Tue, 5 Jun 2018 23:38:35 +0530
+From: Prasad J Pandit 
+
+While reassembling incoming fragmented datagrams, 'm_cat' routine
+extends the 'mbuf' buffer, if it has insufficient room. It computes
+a wrong buffer size, which leads to overwriting adjacent heap buffer
+area. Correct this size computation in m_cat.
+
+Reported-by: ZDI Disclosures 
+Signed-off-by: Prasad J Pandit 
+---
+ slirp/mbuf.c | 8 
+ 1 file changed, 4 insertions(+), 4 deletions(-)
+
+Signed-off-by: Jeremy Puhlman 
+---
+ slirp/mbuf.c | 8 
+ 1 file changed, 4 insertions(+), 4 deletions(-)
+
+diff --git a/slirp/mbuf.c b/slirp/mbuf.c
+index 5ff2455..7fb4501 100644
+--- a/slirp/mbuf.c
 b/slirp/mbuf.c
+@@ -138,7 +138,7 @@ m_cat(struct mbuf *m, struct mbuf *n)
+* If there's no room, realloc
+*/
+   if (M_FREEROOM(m) < n->m_len)
+-  m_inc(m,m->m_size+MINCSIZE);
++   m_inc(m, m->m_len + n->m_len);
+ 
+   memcpy(m->m_data+m->m_len, n->m_data, n->m_len);
+   m->m_len += n->m_len;
+@@ -158,12 +158,12 @@ m_inc(struct mbuf *m, int size)
+ 
+ if (m->m_flags & M_EXT) {
+ datasize = m->m_data - m->m_ext;
+-  m->m_ext = g_realloc(m->m_ext, size);
++  m->m_ext = g_realloc(m->m_ext, size + datasize);
+ m->m_data = m->m_ext + datasize;
+ } else {
+ char *dat;
+ datasize = m->m_data - m->m_dat;
+-  dat = g_malloc(size);
++  dat = g_malloc(size + datasize);
+ memcpy(dat, m->m_dat, m->m_size);
+ 
+ m->m_ext = dat;
+@@ -171,7 +171,7 @@ m_inc(struct mbuf *m, int size)
+ m->m_flags |= M_EXT;
+ }
+ 
+-m->m_size = size;
++m->m_size = size + datasize;
+ 
+ }
+ 
+-- 
+2.13.3
+
diff --git a/meta/recipes-devtools/qemu/qemu_2.12.0.bb 
b/meta/recipes-devtools/qemu/qemu_2.12.0.bb
index 21796df9d7..98db44a8ef 100644
--- a/meta/recipes-devtools/qemu/qemu_2.12.0.bb
+++ b/meta/recipes-devtools/qemu/qemu_2.12.0.bb
@@ -21,6 +21,7 @@ SRC_URI = 
"http://wiki.qemu-project.org/download/${BP}.tar.bz2 \
file://0009-apic-fixup-fallthrough-to-PIC.patch \

file://0010-linux-user-Fix-webkitgtk-hangs-on-32-bit-x86-target.patch \

file://0011-Revert-linux-user-fix-mmap-munmap-mprotect-mremap-sh.patch \
+   file://0001-CVE-2018-11806-QEMU-slirp-heap-buffer-overflow.patch \
"
 UPSTREAM_CHECK_REGEX = "qemu-(?P\d+\..*)\.tar"
 
-- 
2.14.1.459.g238e487

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


Re: [OE-core] [PATCH] goarch.bbclass: set SECURITY_CFLAGS for mips64

2018-06-13 Thread Khem Raj



On 6/13/18 8:15 PM, Kang Kai wrote:

On 2018年06月13日 22:01, Khem Raj wrote:

On Wed, Jun 13, 2018 at 12:16 AM  wrote:

From: Kai Kang 

When include conf/distro/include/security_flags.inc, NOPIE flags are
still required for MIPS64 target builds. Otherwise it fails to build
packages such as glide which inherit go.bbclass:

| 
.../tmp-glibc/work/mips64-wrs-linux/glide/0.13.1-r0/recipe-sysroot-native/usr/bin/mips64-wrs-linux/../../libexec/mips64-wrs-linux/ 

| gcc/mips64-wrs-linux/7.3.0/ld: 
.../tmp-glibc/work/mips64-wrs-linux/glide/0.13.1-r0/go-tmp/go-link-518447869/go.o: 

| relocation R_MIPS_26 against `a local symbol' can not be used when 
making a shared object; recompile with -fPIC`


Signed-off-by: Kai Kang 
---
  meta/classes/goarch.bbclass | 1 +
  1 file changed, 1 insertion(+)

diff --git a/meta/classes/goarch.bbclass b/meta/classes/goarch.bbclass
index f54c5169e3e..5fd9f294a8a 100644
--- a/meta/classes/goarch.bbclass
+++ b/meta/classes/goarch.bbclass
@@ -36,6 +36,7 @@ COMPATIBLE_HOST_mipsarchn32 = "null"
  ARM_INSTRUCTION_SET = "arm"
  TUNE_CCARGS_remove = "-march=mips32r2"
  SECURITY_CFLAGS_mips = "${SECURITY_NOPIE_CFLAGS}"
+SECURITY_CFLAGS_mips64 = "${SECURITY_NOPIE_CFLAGS}"

perhaps we should use _mipsall once

Hi Khem,

I don't quite follow you. It seems no such override '_mipsall' exists. 
Do you mean 'mipsarch' or something else? Thanks.




yes mipsarch indeed.


Regards,
Kai



  SECURITY_NOPIE_CFLAGS ??= ""

  def go_map_arch(a, d):
--
2.17.1

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




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


Re: [OE-core] [PATCH] goarch.bbclass: set SECURITY_CFLAGS for mips64

2018-06-13 Thread Kang Kai

On 2018年06月13日 22:01, Khem Raj wrote:

On Wed, Jun 13, 2018 at 12:16 AM  wrote:

From: Kai Kang 

When include conf/distro/include/security_flags.inc, NOPIE flags are
still required for MIPS64 target builds. Otherwise it fails to build
packages such as glide which inherit go.bbclass:

| 
.../tmp-glibc/work/mips64-wrs-linux/glide/0.13.1-r0/recipe-sysroot-native/usr/bin/mips64-wrs-linux/../../libexec/mips64-wrs-linux/
| gcc/mips64-wrs-linux/7.3.0/ld: 
.../tmp-glibc/work/mips64-wrs-linux/glide/0.13.1-r0/go-tmp/go-link-518447869/go.o:
| relocation R_MIPS_26 against `a local symbol' can not be used when making a 
shared object; recompile with -fPIC`

Signed-off-by: Kai Kang 
---
  meta/classes/goarch.bbclass | 1 +
  1 file changed, 1 insertion(+)

diff --git a/meta/classes/goarch.bbclass b/meta/classes/goarch.bbclass
index f54c5169e3e..5fd9f294a8a 100644
--- a/meta/classes/goarch.bbclass
+++ b/meta/classes/goarch.bbclass
@@ -36,6 +36,7 @@ COMPATIBLE_HOST_mipsarchn32 = "null"
  ARM_INSTRUCTION_SET = "arm"
  TUNE_CCARGS_remove = "-march=mips32r2"
  SECURITY_CFLAGS_mips = "${SECURITY_NOPIE_CFLAGS}"
+SECURITY_CFLAGS_mips64 = "${SECURITY_NOPIE_CFLAGS}"

perhaps we should use _mipsall once

Hi Khem,

I don't quite follow you. It seems no such override '_mipsall' exists. 
Do you mean 'mipsarch' or something else? Thanks.


Regards,
Kai



  SECURITY_NOPIE_CFLAGS ??= ""

  def go_map_arch(a, d):
--
2.17.1

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



--
Regards,
Neil | Kai Kang

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


[OE-core] [PATCH V2 0/1] linux-yocto: add ptest support

2018-06-13 Thread Dengke Du
Changed in V2:
Put the run-ptest script in linux-yocto directory.

The following changes since commit ddbd7b0cd6580ee26e11aa87e426fb294b372d64:

  meta-yocto-bsp: bump to the latest linux stable kernel for 
edgerouter/beaglebone (2018-06-12 23:34:40 +0100)

are available in the git repository at:

  https://github.com/DengkeDu/openembedded-core.git kernel-ptest
  https://github.com//tree/kernel-ptest

Dengke Du (1):
  linux-yocto: add ptest support

 meta/recipes-kernel/linux/linux-yocto/run-ptest | 138 
 meta/recipes-kernel/linux/linux-yocto_4.14.bb   |   9 ++
 2 files changed, 147 insertions(+)
 create mode 100644 meta/recipes-kernel/linux/linux-yocto/run-ptest

-- 
2.7.4

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


[OE-core] [PATCH V2 1/1] linux-yocto: add ptest support

2018-06-13 Thread Dengke Du
Signed-off-by: Dengke Du 
---
 meta/recipes-kernel/linux/linux-yocto/run-ptest | 138 
 meta/recipes-kernel/linux/linux-yocto_4.14.bb   |   9 ++
 2 files changed, 147 insertions(+)
 create mode 100644 meta/recipes-kernel/linux/linux-yocto/run-ptest

diff --git a/meta/recipes-kernel/linux/linux-yocto/run-ptest 
b/meta/recipes-kernel/linux/linux-yocto/run-ptest
new file mode 100644
index 000..6db4d93
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto/run-ptest
@@ -0,0 +1,138 @@
+#!/bin/bash
+depmod
+touch kernel.log
+
+#dma-example bytestream-example inttype-example record-example
+list1=("dma-example" "bytestream-example" "inttype-example" "record-example")
+for i in "${list1[@]}"
+do
+  dmesg -c
+  modprobe "$i"
+  result=""
+  IFS="-" read -ra array <<< "$i"
+  len=${#array[@]}
+  if [ $len -eq 2 ];then
+result="${array[0]}_${array[1]}"
+  elif [ $len -eq 3 ];then
+result="${array[0]}_${array[1]}_${array[2]}"
+  fi
+  lsmod | grep -q "$result"
+  if [ $? -eq 0 ];then
+dmesg | grep "test passed"
+if [ $? -eq 0 ];then
+  echo "$i: PASS" >> kernel.log
+fi
+  else
+echo "$i: FAILED" >> kernel.log
+  fi
+  rmmod "$i"
+done
+
+#kobject-example kset-example
+list2=("kobject-example" "kset-example")
+for i in "${list2[@]}"
+do
+  dmesg -c
+  modprobe "$i"
+  result=""
+  IFS="-" read -ra array <<< "$i"
+  len=${#array[@]}
+  if [ $len -eq 2 ];then
+result="${array[0]}_${array[1]}"
+  elif [ $len -eq 3 ];then
+result="${array[0]}_${array[1]}_${array[2]}"
+  fi
+  basedir="/sys/kernel/${result}"
+  echo "$basedir"
+  if [ -e ${basedir}/bar -a -e ${basedir}/baz -a -e ${basedir}/foo ];then
+echo "$i: PASS" >> kernel.log
+  else
+echo "$i: FAILED" >> kernel.log
+  fi
+  rmmod "$i"
+done
+
+#trace-events-sample
+list3="trace-events-sample"
+result=""
+IFS="-" read -ra array <<< "$list3"
+len=${#array[@]}
+if [ $len -eq 2 ];then
+  result="${array[0]}_${array[1]}"
+elif [ $len -eq 3 ];then
+  result="${array[0]}_${array[1]}_${array[2]}"
+fi
+modprobe "$list3"
+lsmod | grep "$result"
+if [ $? -eq 0 ];then
+  if [ -e "/sys/kernel/debug/tracing/events/sample-trace" ];then
+echo 1 > /sys/kernel/debug/tracing/events/sample-trace/enable
+sleep 5
+ret=`cat /sys/kernel/debug/tracing/trace | grep hello | head -n1 | cut 
-d':' -f2`
+if [ "$ret" = " foo_bar" ];then
+  echo "$list3: PASS"  >> kernel.log
+else
+  echo "$list3: FAILED-" >> kernel.log
+fi
+  else
+echo "$list3: FAILED--" >> kernel.log
+  fi
+else
+  echo "$list3: FAILED---" >> kernel.log
+fi
+rmmod "$list3"
+
+#trace-printk
+list4="trace-printk"
+modprobe "$list4"
+lsmod | grep "trace_printk"
+if [ $? -eq 0 ];then
+  ret=`cat /sys/kernel/debug/tracing/trace | grep trace_printk | head -n1 | 
cut -d':' -f2`
+  if [ "$ret" = " trace_printk_irq_work" ];then
+echo "$list4: PASS" >> kernel.log
+rmmod "$list4"
+  else
+echo "$list4: FAILED" >> kernel.log
+  fi
+else
+  echo "$list4: FAILED" >> kernel.log
+fi
+rmmod "$list4"
+
+#kprobe_example
+list5="kprobe_example"
+dmesg -c
+modprobe "$list5"
+lsmod | grep "$list5"
+if [ $? -eq 0 ];then
+  dmesg | grep "_do_fork"
+  if [ $? -eq 0 ];then
+echo "$list5: PASS" >> kernel.log
+  else
+echo "$list5: FAILED" >> kernel.log
+  fi
+else
+  echo "$list5: FAILED" >> kernel.log
+fi
+rmmod "$list5"
+
+#kretprobe_example
+list6="kretprobe_example"
+dmesg -c
+modprobe "$list6"
+lsmod | grep "$list6"
+if [ $? -eq 0 ];then
+  dmesg | grep "_do_fork returned"
+  if [ $? -eq 0 ];then
+echo "$list6: PASS" >> kernel.log
+  else
+echo "$list6: FAILED" >> kernel.log
+  fi
+else
+  echo "$list6: FAILED" >> kernel.log
+fi
+rmmod "$list6"
+
+echo "#result#"
+cat kernel.log
+rm kernel.log
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.14.bb 
b/meta/recipes-kernel/linux/linux-yocto_4.14.bb
index 0449213..9650ee2 100644
--- a/meta/recipes-kernel/linux/linux-yocto_4.14.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_4.14.bb
@@ -45,3 +45,12 @@ 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)}"
+
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+inherit ptest
+SRC_URI_append = " file://run-ptest \
+"
+do_install_ptest_append() {
+install -D ${WORKDIR}/run-ptest ${D}${PTEST_PATH}/run-ptest
+}
+KERNEL_FEATURES_append = " ${@bb.utils.contains("DISTRO_FEATURES", "ptest", 
"features/kernel-sample/kernel-sample.scc", "", d)}"
-- 
2.7.4

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


Re: [OE-core] [PATCH v4 01/12] gstreamer: enable ptest support

2018-06-13 Thread Anuj Mittal
Ping.

On 05/25/2018 02:20 PM, Anuj Mittal wrote:
> Make sure that the tests are packaged and can be executed
> when ptest is enabled. Also, remove build host specific references
> from Makefile.
> 
> Signed-off-by: Anuj Mittal 
> ---
> 
> v4:
> Tweak AM_TESTS_ENVIRONMENT to remove hardcoded paths.
> 
> ---
>  .../files/add-a-target-to-compile-tests.patch | 69 +++
>  .../gstreamer/files/run-ptest |  3 +
>  .../gstreamer/gstreamer1.0_1.14.0.bb  | 26 ++-
>  3 files changed, 96 insertions(+), 2 deletions(-)
>  create mode 100644 
> meta/recipes-multimedia/gstreamer/files/add-a-target-to-compile-tests.patch
>  create mode 100644 meta/recipes-multimedia/gstreamer/files/run-ptest
> 
> diff --git 
> a/meta/recipes-multimedia/gstreamer/files/add-a-target-to-compile-tests.patch 
> b/meta/recipes-multimedia/gstreamer/files/add-a-target-to-compile-tests.patch
> new file mode 100644
> index 00..d02d869410
> --- /dev/null
> +++ 
> b/meta/recipes-multimedia/gstreamer/files/add-a-target-to-compile-tests.patch
> @@ -0,0 +1,69 @@
> +From d61414bc17cf2df019510c2908048c4cabf5cf09 Mon Sep 17 00:00:00 2001
> +From: Anuj Mittal 
> +Date: Tue, 27 Feb 2018 09:27:01 +0800
> +Subject: [PATCH] add targets for test installation
> +
> +Targets to make sure tests can be installed and then run on
> +the target.
> +
> +Upstream-Status: Inappropriate [specific to oe setup]
> +
> +Signed-off-by: Anuj Mittal 
> +
> +---
> + tests/check/Makefile.am | 27 ---
> + 1 file changed, 20 insertions(+), 7 deletions(-)
> +
> +diff --git a/tests/check/Makefile.am b/tests/check/Makefile.am
> +index 13b916d..a66786d 100644
> +--- a/tests/check/Makefile.am
>  b/tests/check/Makefile.am
> +@@ -8,11 +8,7 @@ REGISTRY_ENVIRONMENT = \
> + GST_REGISTRY=$(CHECK_REGISTRY)
> + 
> + AM_TESTS_ENVIRONMENT += \
> +-GST_STATE_IGNORE_ELEMENTS="$(STATE_IGNORE_ELEMENTS)"\
> +-$(REGISTRY_ENVIRONMENT) \
> +-
> GST_PLUGIN_SCANNER_1_0=$(top_builddir)/libs/gst/helpers/gst-plugin-scanner \
> +-GST_PLUGIN_SYSTEM_PATH_1_0= \
> +-GST_PLUGIN_PATH_1_0=$(top_builddir)/plugins
> ++GST_STATE_IGNORE_ELEMENTS="$(STATE_IGNORE_ELEMENTS)"
> + 
> + plugindir = $(libdir)/gstreamer-@GST_API_VERSION@
> + 
> +@@ -178,6 +174,23 @@ noinst_PROGRAMS =
> + 
> + TESTS = $(check_PROGRAMS)
> + 
> ++install-ptest: $(TESTS)
> ++@$(INSTALL) -d $(DESTDIR)
> ++@for dir in `find -maxdepth 1 -type d`; do \
> ++if [ -x $$dir/.libs ]; then \
> ++$(INSTALL) -d $(DESTDIR)/$$dir; \
> ++$(INSTALL_PROGRAM) $$dir/.libs/* $(DESTDIR)/$$dir/; \
> ++fi \
> ++done
> ++
> ++runtests:
> ++@for b in $(TESTS); do \
> ++if [ -x $$b ]; then \
> ++$(AM_TESTS_ENVIRONMENT) $(SHELL) test-driver 
> --test-name "$$b" \
> ++--log-file $$b.log --trs-file $$b.trs $$b; \
> ++fi \
> ++done
> ++
> + noinst_HEADERS = \
> + gst/capslist.h \
> + gst/struct_arm.h \
> +@@ -221,9 +234,9 @@ gst_gstprintf_LDADD = \
> + $(LDADD)
> + 
> + elements_fdsrc_CFLAGS=$(GST_OBJ_CFLAGS) $(AM_CFLAGS) \
> +--DTESTFILE=\"$(top_srcdir)/configure.ac\"
> ++-DTESTFILE=\"Makefile\"
> + elements_filesrc_CFLAGS=$(GST_OBJ_CFLAGS) $(AM_CFLAGS) \
> +--DTESTFILE=\"$(top_srcdir)/configure.ac\"
> ++-DTESTFILE=\"Makefile\"
> + 
> + libs_controller_LDADD = \
> + 
> $(top_builddir)/libs/gst/controller/libgstcontroller-@GST_API_VERSION@.la \
> diff --git a/meta/recipes-multimedia/gstreamer/files/run-ptest 
> b/meta/recipes-multimedia/gstreamer/files/run-ptest
> new file mode 100644
> index 00..473d0b67a7
> --- /dev/null
> +++ b/meta/recipes-multimedia/gstreamer/files/run-ptest
> @@ -0,0 +1,3 @@
> +#!/bin/sh
> +
> +make -k runtests
> diff --git a/meta/recipes-multimedia/gstreamer/gstreamer1.0_1.14.0.bb 
> b/meta/recipes-multimedia/gstreamer/gstreamer1.0_1.14.0.bb
> index b4398c8111..e842f30c5a 100644
> --- a/meta/recipes-multimedia/gstreamer/gstreamer1.0_1.14.0.bb
> +++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0_1.14.0.bb
> @@ -8,7 +8,7 @@ LICENSE = "LGPLv2+"
>  
>  DEPENDS = "glib-2.0 glib-2.0-native libcap libxml2 bison-native flex-native"
>  
> -inherit autotools pkgconfig gettext upstream-version-is-even 
> gobject-introspection gtk-doc
> +inherit autotools pkgconfig gettext upstream-version-is-even 
> gobject-introspection gtk-doc ptest
>  
>  # This way common/m4/introspection.m4 will come first
>  # (it has a custom INTROSPECTION_INIT macro, and so must be used instead of 
> our common introspection.m4 file)
> @@ -24,11 +24,14 @@ SRC_URI = " \
>  file://0001-introspection.m4-prefix-pkgconfig-paths-with-PKG_CON.patch \
>  file://gtk-doc-tweaks.patch \
>  file://0001-gst-gstpluginloader.c-when-env-var-is-set-do-not-fal.patch \
> +

Re: [OE-core] [PATCH 07/12] libunistring: upgrade to 0.9.10

2018-06-13 Thread Randy MacLeod

On 06/13/2018 04:29 AM, Maxin B. John wrote:

Hi Randy,

On Tue, Jun 12, 2018 at 09:21:17PM -0400, Randy MacLeod wrote:

On 06/12/2018 07:18 AM, Maxin B. John wrote:

License-Update: Checksum changed due to updation in documentation. There
are no changes in the license terms.


That's correct but I'm not sure if we should include
a checksum on the (GPLv3) COPYING file since the README
says [1] that:
This license is based on the GNU GPL version 3, see file COPYING.
I'd like to know if the COPYING file changed to say the _actual_
GPLv2 some day so a checksum would help track such changes.


The README statement is an odd way to convey the license terms.
Is this just standard FSFese?


Yes, it is odd.

README says 'The libunistring library and its header files are dual-licensed 
under
"the GNU LGPLv3+ or the GNU GPLv2"' and the project includes a GPL v3 license 
(COPYING).

Though not 100% sure, I would assume that it is ok continue with
LICENSE = "LGPLv3+ | GPLv2"


Yes, that still makes sense.



If anyone think it is the wrong way to go, please share your views/suggestions.



I guess we'll just accept the lack of a COPYING.gplv2 and
the odd why that the license is stipulated.

Thanks,

../Randy


The libunistring commit that sets out these terms is from 0.9:

commit 3c15d3a96963703fc02cddda7e968e508638d1b8
Author: Bruno Haible 
Date:   Sun Mar 15 02:10:58 2009 +0100

 License information.

  COPYING | 674 ...
  COPYING.LIB | 165 +...
  ChangeLog   |   3 +
  README  |   2 +-
  4 files changed, 843 insertions(+), 1 deletion(-)


which doesn't help much other than the ChangeLog:

+   * COPYING.LIB: New file, from gnulib/doc/COPYING.LESSERv3.
+   * COPYING: New file, from gnulib/doc/COPYINGv3.


../Randy


Best Regards,
Maxin



[1] From README:

Copyright
-

The libunistring library and its header files are dual-licensed under
"the GNU LGPLv3+ or the GNU GPLv2". This means, you can use it under either
   - the terms of the GNU Lesser General Public License (LGPL) version 3 or
 (at your option) any later version, or
   - the terms of the GNU General Public License (GPL) version 2, or
   - the same dual license "the GNU LGPLv3+ or the GNU GPLv2".

You find the GNU LGPL version 3 in the file COPYING.LIB.  This license is
based on the GNU GPL version 3, see file COPYING.

You can find the GNU GPL version 2 at
.

Note: This dual license makes it possible for the libunistring library
to be used by packages under GPLv2 or GPLv2+ licenses, in particular. See
the table in .

The documentation is under another license; see in the documentation.



Signed-off-by: Maxin B. John 
---
  .../libunistring/{libunistring_0.9.9.bb => libunistring_0.9.10.bb}  | 6 +++---
  1 file changed, 3 insertions(+), 3 deletions(-)
  rename meta/recipes-support/libunistring/{libunistring_0.9.9.bb => 
libunistring_0.9.10.bb} (85%)

diff --git a/meta/recipes-support/libunistring/libunistring_0.9.9.bb 
b/meta/recipes-support/libunistring/libunistring_0.9.10.bb
similarity index 85%
rename from meta/recipes-support/libunistring/libunistring_0.9.9.bb
rename to meta/recipes-support/libunistring/libunistring_0.9.10.bb
index ab7cba5..97fac4e 100644
--- a/meta/recipes-support/libunistring/libunistring_0.9.9.bb
+++ b/meta/recipes-support/libunistring/libunistring_0.9.10.bb
@@ -16,15 +16,15 @@ SECTION = "devel"
  LICENSE = "LGPLv3+ | GPLv2"
  LIC_FILES_CHKSUM = "file://COPYING.LIB;md5=6a6a8e020838b23406c81b19c1d46df6 \
  
file://README;beginline=45;endline=65;md5=08287d16ba8d839faed8d2dc14d7d6a5 \
-
file://doc/libunistring.texi;md5=efb80a3799a60f95feaf80661d4f204c \
+
file://doc/libunistring.texi;md5=287fa6075f78a3c85c1a52b0a92547cd \
 "
  SRC_URI = "${GNU_MIRROR}/libunistring/libunistring-${PV}.tar.gz \
 file://iconv-m4-remove-the-test-to-convert-euc-jp.patch \
 file://0001-Unset-need_charset_alias-when-building-for-musl.patch \
  "
-SRC_URI[md5sum] = "4f689e37e4c3bd67de5786aa51d98b13"
-SRC_URI[sha256sum] = 
"f5e90c08f9e5427ca3a2c0c53f19aa38b25c500913510ad25afef86448bea84a"
+SRC_URI[md5sum] = "0d3274e9838396b12200f8b54ddaf43b"
+SRC_URI[sha256sum] = 
"a82e5b39a88ea4608e4635479a1cfb2e01aafb925e1290b65710d43f610b"
  inherit autotools texinfo
  BBCLASSEXTEND = "native nativesdk"




--
# Randy MacLeod
# Wind River Linux





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


Re: [OE-core] [poky][PATCH] poky: add ubuntu-18.04 to SANITY_TESTED_DISTROS

2018-06-13 Thread Burton, Ross
Generally we'll only do this when the autobuilders actually have a
18.04 builder, which we don't have yet.

Ross

On 13 June 2018 at 23:25,   wrote:
> From: Oleksandr Kravchuk 
>
> Signed-off-by: Oleksandr Kravchuk 
> ---
>  meta-poky/conf/distro/poky.conf | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/meta-poky/conf/distro/poky.conf b/meta-poky/conf/distro/poky.conf
> index 9bd9ee58c4..19459b1791 100644
> --- a/meta-poky/conf/distro/poky.conf
> +++ b/meta-poky/conf/distro/poky.conf
> @@ -71,6 +71,7 @@ SANITY_TESTED_DISTROS ?= " \
>  ubuntu-16.04 \n \
>  ubuntu-16.10 \n \
>  ubuntu-17.04 \n \
> +ubuntu-18.04 \n \
>  fedora-24 \n \
>  fedora-25 \n \
>  fedora-26 \n \
> --
> 2.17.1
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [poky][PATCH] poky: add ubuntu-18.04 to SANITY_TESTED_DISTROS

2018-06-13 Thread open . source
From: Oleksandr Kravchuk 

Signed-off-by: Oleksandr Kravchuk 
---
 meta-poky/conf/distro/poky.conf | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta-poky/conf/distro/poky.conf b/meta-poky/conf/distro/poky.conf
index 9bd9ee58c4..19459b1791 100644
--- a/meta-poky/conf/distro/poky.conf
+++ b/meta-poky/conf/distro/poky.conf
@@ -71,6 +71,7 @@ SANITY_TESTED_DISTROS ?= " \
 ubuntu-16.04 \n \
 ubuntu-16.10 \n \
 ubuntu-17.04 \n \
+ubuntu-18.04 \n \
 fedora-24 \n \
 fedora-25 \n \
 fedora-26 \n \
-- 
2.17.1

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


Re: [OE-core] [PATCH] Only add uninative and checksum if inherited uninative class

2018-06-13 Thread Jeremy Puhlman
Any issue with this patch?

On Wed, Apr 25, 2018 at 2:18 PM, Jeremy Puhlman  wrote:

> The checksum value is only calculated if the uninative class is
> inherited, so check for inherit before adding it to local.conf
>
> Signed-off-by: Jeremy Puhlman 
> ---
>  meta/classes/populate_sdk_ext.bbclass | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/meta/classes/populate_sdk_ext.bbclass
> b/meta/classes/populate_sdk_ext.bbclass
> index e1bba49eaf..8dfb8df52e 100644
> --- a/meta/classes/populate_sdk_ext.bbclass
> +++ b/meta/classes/populate_sdk_ext.bbclass
> @@ -325,8 +325,9 @@ python copy_buildsystem () {
>  f.write('TCLIBCAPPEND = ""\n')
>  f.write('DL_DIR = "${TOPDIR}/downloads"\n')
>
> -f.write('INHERIT += "%s"\n' % 'uninative')
> -f.write('UNINATIVE_CHECKSUM[%s] = "%s"\n\n' %
> (d.getVar('BUILD_ARCH'), uninative_checksum))
> +if bb.data.inherits_class('uninative', d):
> +   f.write('INHERIT += "%s"\n' % 'uninative')
> +   f.write('UNINATIVE_CHECKSUM[%s] = "%s"\n\n' %
> (d.getVar('BUILD_ARCH'), uninative_checksum))
>  f.write('CONF_VERSION = "%s"\n\n' % d.getVar('CONF_VERSION',
> False))
>
>  # Some classes are not suitable for SDK, remove them from
> INHERIT
> --
> 2.11.1
>
>


-- 
Jeremy Puhlman
Montavista Software, LLC.
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH] atk: Correct multilib conflict in header.

2018-06-13 Thread Jeremy Puhlman
The headers don't contain any code differences, but they include the full paths
to the build location in the header file. Removing the build location resolves
the install conflict.

Error: Transaction check error:
  file /usr/include/atk-1.0/atk/atk-enum-types.h conflicts between attempted 
installs of atk-dev-2.28.1-r0.corei7_64 and lib32-atk-dev-2.28.1-r0.i586
---
 meta/recipes-support/atk/atk_2.28.1.bb | 5 +
 1 file changed, 5 insertions(+)

diff --git a/meta/recipes-support/atk/atk_2.28.1.bb 
b/meta/recipes-support/atk/atk_2.28.1.bb
index 657c69d..aedb036 100644
--- a/meta/recipes-support/atk/atk_2.28.1.bb
+++ b/meta/recipes-support/atk/atk_2.28.1.bb
@@ -33,3 +33,8 @@ SRC_URI[archive.sha256sum] = 
"cd3a1ea6ecc268a2497f0cd018e970860de24a6d42086919d6
 
 BBCLASSEXTEND = "native"
 
+do_install_append () {
+   if [ -e ${D}${includedir}/atk-1.0/atk/atk-enum-types.h ] ; then
+  sed -i ${D}${includedir}/atk-1.0/atk/atk-enum-types.h -e "s,${B},,"
+   fi
+}
-- 
2.6.4

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


[OE-core] [PATCH] Remove libdir specification from xorgproto .pc files

2018-06-13 Thread Jeremy Puhlman
Signed-off-by: Jeremy Puhlman 
---
 .../0001-Remove-libdir-specification.patch | 468 +
 .../xorg-proto/xorgproto_2018.4.bb |   2 +
 2 files changed, 470 insertions(+)
 create mode 100644 
meta/recipes-graphics/xorg-proto/xorgproto/0001-Remove-libdir-specification.patch

diff --git 
a/meta/recipes-graphics/xorg-proto/xorgproto/0001-Remove-libdir-specification.patch
 
b/meta/recipes-graphics/xorg-proto/xorgproto/0001-Remove-libdir-specification.patch
new file mode 100644
index 000..48296f7
--- /dev/null
+++ 
b/meta/recipes-graphics/xorg-proto/xorgproto/0001-Remove-libdir-specification.patch
@@ -0,0 +1,468 @@
+Upstream-Status: Submitted
+
+https://cgit.freedesktop.org/xorg/proto/xorgproto/commit/?id=91c1c8e1490c970379efb16784003426faec806e
+
+From 6feb974e0deb3355908c30e07293d82a3f6996ed Mon Sep 17 00:00:00 2001
+From: Jeremy Puhlman 
+Date: Mon, 11 Jun 2018 16:42:43 +
+Subject: [PATCH] Remove libdir specification.
+
+Currently the pc files define libdir, however they are installed into
+/usr/share, which means they should be architecture agnostic. In a
+multilib system, xorg-proto built for each multilib abi, the value of
+libdir is going to be different. These should either be installed in
+/pkgconfig or they shouldn't define libdir, espeically since
+they don't actually use the definition. This specifically causes an
+issue when trying to install both abis at the same time, since they are
+not binary identical, something like rpm will complain that they
+
+---
+ applewmproto.pc.in | 1 -
+ bigreqsproto.pc.in | 1 -
+ compositeproto.pc.in   | 1 -
+ damageproto.pc.in  | 1 -
+ dmxproto.pc.in | 1 -
+ dri2proto.pc.in| 1 -
+ dri3proto.pc.in| 1 -
+ evieproto.pc.in| 1 -
+ fixesproto.pc.in   | 1 -
+ fontcacheproto.pc.in   | 1 -
+ fontsproto.pc.in   | 1 -
+ glproto.pc.in  | 1 -
+ inputproto.pc.in   | 1 -
+ kbproto.pc.in  | 1 -
+ lg3dproto.pc.in| 1 -
+ presentproto.pc.in | 1 -
+ printproto.pc.in   | 1 -
+ randrproto.pc.in   | 1 -
+ recordproto.pc.in  | 1 -
+ renderproto.pc.in  | 1 -
+ resourceproto.pc.in| 1 -
+ scrnsaverproto.pc.in   | 1 -
+ trapproto.pc.in| 1 -
+ videoproto.pc.in   | 1 -
+ windowswmproto.pc.in   | 1 -
+ xcalibrateproto.pc.in  | 1 -
+ xcmiscproto.pc.in  | 1 -
+ xextproto.pc.in| 1 -
+ xf86bigfontproto.pc.in | 1 -
+ xf86dgaproto.pc.in | 1 -
+ xf86driproto.pc.in | 1 -
+ xf86miscproto.pc.in| 1 -
+ xf86rushproto.pc.in| 1 -
+ xf86vidmodeproto.pc.in | 1 -
+ xineramaproto.pc.in| 1 -
+ xproto.pc.in   | 1 -
+ xproxymngproto.pc.in   | 1 -
+ 37 files changed, 37 deletions(-)
+
+diff --git a/applewmproto.pc.in b/applewmproto.pc.in
+index 17841ac..3227b21 100644
+--- a/applewmproto.pc.in
 b/applewmproto.pc.in
+@@ -1,6 +1,5 @@
+ prefix=@prefix@
+ exec_prefix=@exec_prefix@
+-libdir=@libdir@
+ includedir=@includedir@
+  
+ Name: AppleWMProto
+diff --git a/bigreqsproto.pc.in b/bigreqsproto.pc.in
+index 94577ed..e21bb59 100644
+--- a/bigreqsproto.pc.in
 b/bigreqsproto.pc.in
+@@ -1,6 +1,5 @@
+ prefix=@prefix@
+ exec_prefix=@exec_prefix@
+-libdir=@libdir@
+ includedir=@includedir@
+  
+ Name: BigReqsProto
+diff --git a/compositeproto.pc.in b/compositeproto.pc.in
+index da429c7..b0dada1 100644
+--- a/compositeproto.pc.in
 b/compositeproto.pc.in
+@@ -1,6 +1,5 @@
+ prefix=@prefix@
+ exec_prefix=@exec_prefix@
+-libdir=@libdir@
+ includedir=@includedir@
+ 
+ Name: CompositeExt
+diff --git a/damageproto.pc.in b/damageproto.pc.in
+index 6fd9ef1..bfd5244 100644
+--- a/damageproto.pc.in
 b/damageproto.pc.in
+@@ -1,6 +1,5 @@
+ prefix=@prefix@
+ exec_prefix=@exec_prefix@
+-libdir=@libdir@
+ includedir=@includedir@
+ 
+ Name: DamageProto
+diff --git a/dmxproto.pc.in b/dmxproto.pc.in
+index e82ee7d..d140e1c 100644
+--- a/dmxproto.pc.in
 b/dmxproto.pc.in
+@@ -1,6 +1,5 @@
+ prefix=@prefix@
+ exec_prefix=@exec_prefix@
+-libdir=@libdir@
+ includedir=@includedir@
+  
+ Name: DMXProto
+diff --git a/dri2proto.pc.in b/dri2proto.pc.in
+index cb5b171..fa9d24d 100644
+--- a/dri2proto.pc.in
 b/dri2proto.pc.in
+@@ -1,6 +1,5 @@
+ prefix=@prefix@
+ exec_prefix=@exec_prefix@
+-libdir=@libdir@
+ includedir=@includedir@
+  
+ Name: DRI2Proto
+diff --git a/dri3proto.pc.in b/dri3proto.pc.in
+index e42d60e..20da358 100644
+--- a/dri3proto.pc.in
 b/dri3proto.pc.in
+@@ -1,6 +1,5 @@
+ prefix=@prefix@
+ exec_prefix=@exec_prefix@
+-libdir=@libdir@
+ includedir=@includedir@
+  
+ Name: DRI3Proto
+diff --git a/evieproto.pc.in b/evieproto.pc.in
+index 64e0ec4..fd5442b 100644
+--- a/evieproto.pc.in
 b/evieproto.pc.in
+@@ -1,6 +1,5 @@
+ prefix=@prefix@
+ exec_prefix=@exec_prefix@
+-libdir=@libdir@
+ includedir=@includedir@
+ 
+ Name: EvIEExt
+diff --git a/fixesproto.pc.in b/fixesproto.pc.in
+index f8258e2..c7fcb81 100644
+--- a/fixesproto.pc.in
 b/fixesproto.pc.in
+@@ -1,6 +1,5 @@
+ prefix=@prefix@
+ exec_prefix=@exec_prefix@

[OE-core] [PATCH master, sumo, rocko] Multilibize the UPDATERCPN variable

2018-06-13 Thread Jeremy Puhlman
The audit package specifies the following:
UPDATERCPN = "auditd"

However because it is not multilibized, the value "auditd" is used to
search for the package to add the post install script too. In the mutlilib
alternate abi case, that package does not exist. It ends up assigning
the post install script to the lib32-audit-lic package, which
subsequently failes to execute the script due to the initscript it is
trying to turn on is not installed.

Signed-off-by: Jeremy Puhlman 
---
 meta/classes/multilib.bbclass | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/classes/multilib.bbclass b/meta/classes/multilib.bbclass
index 5f9dc311f4..1dcd350298 100644
--- a/meta/classes/multilib.bbclass
+++ b/meta/classes/multilib.bbclass
@@ -115,6 +115,7 @@ python __anonymous () {
 clsextend.map_variable("INITSCRIPT_PACKAGES")
 clsextend.map_variable("USERADD_PACKAGES")
 clsextend.map_variable("SYSTEMD_PACKAGES")
+clsextend.map_variable("UPDATERCPN")
 }
 
 PACKAGEFUNCS_append = " do_package_qa_multilib"
-- 
2.14.1.459.g238e487

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


[OE-core] [PATCH] default-versions.inc: use weak assignments to allow overwrite

2018-06-13 Thread Stefan Stanacar
default-versions.inc is included by defaultsetup.conf which in bitbake.conf
is included after local/machine/distro.conf.
If these are hard assignments distros can's overwrite them.

Signed-off-by: Stefan Stanacar 
---
 meta/conf/distro/include/default-versions.inc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta/conf/distro/include/default-versions.inc 
b/meta/conf/distro/include/default-versions.inc
index 868073843a..3d88e8f656 100644
--- a/meta/conf/distro/include/default-versions.inc
+++ b/meta/conf/distro/include/default-versions.inc
@@ -2,6 +2,6 @@
 # Default preferred versions
 #
 
-PREFERRED_VERSION_openssl = "1.0.%"
-PREFERRED_VERSION_openssl-native = "1.0.%"
-PREFERRED_VERSION_nativesdk-openssl = "1.0.%"
+PREFERRED_VERSION_openssl ?= "1.0.%"
+PREFERRED_VERSION_openssl-native ?= "1.0.%"
+PREFERRED_VERSION_nativesdk-openssl ?= "1.0.%"
-- 
2.17.1

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


[OE-core] [PATCH 1/2] runqemu-extract-sdk: support tar.xz format

2018-06-13 Thread Dennis Menschel
As the format "tar.xz" is included in the IMAGE_TYPES bitbake variable
as defined in meta/classes/image_types.bbclass, it should also be
possible to extract a rootfs that has been built using that format.

Signed-off-by: Dennis Menschel 
---
 scripts/runqemu-extract-sdk | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/scripts/runqemu-extract-sdk b/scripts/runqemu-extract-sdk
index f4286efb1f..13e02fa2ca 100755
--- a/scripts/runqemu-extract-sdk
+++ b/scripts/runqemu-extract-sdk
@@ -53,6 +53,9 @@ if [[ ${SDK_ROOTFS_DIR:0:1} != "/" ]]; then
 fi
 
 TAR_OPTS=""
+if [[ "$ROOTFS_TARBALL" =~ tar\.xz$ ]]; then
+   TAR_OPTS="--numeric-owner -xJf"
+fi
 if [[ "$ROOTFS_TARBALL" =~ tar\.bz2$ ]]; then
TAR_OPTS="--numeric-owner -xjf"
 fi
@@ -64,7 +67,7 @@ if [[ "$ROOTFS_TARBALL" =~ \.tar$ ]]; then
 fi
 if [ -z "$TAR_OPTS" ]; then
echo "Error: Unable to determine sdk tarball format"
-   echo "Accepted types: .tar / .tar.gz / .tar.bz2"
+   echo "Accepted types: .tar / .tar.gz / .tar.bz2 / .tar.xz"
exit 1
 fi
 
-- 
2.17.1

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


[OE-core] [PATCH 2/2] runqemu-extract-sdk: fix whitespace errors

2018-06-13 Thread Dennis Menschel
Indentation using a mix of whitespaces and tabs has been unified in
favor of tabs.

Signed-off-by: Dennis Menschel 
---
 scripts/runqemu-extract-sdk | 14 +++---
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/scripts/runqemu-extract-sdk b/scripts/runqemu-extract-sdk
index 13e02fa2ca..4da3eb10a7 100755
--- a/scripts/runqemu-extract-sdk
+++ b/scripts/runqemu-extract-sdk
@@ -31,9 +31,9 @@ fi
 
 SYSROOT_SETUP_SCRIPT=`which oe-find-native-sysroot 2> /dev/null`
 if [ -z "$SYSROOT_SETUP_SCRIPT" ]; then
-echo "Error: Unable to find the oe-find-native-sysroot script"
-echo "Did you forget to source your build system environment setup script?"
-exit 1
+   echo "Error: Unable to find the oe-find-native-sysroot script"
+   echo "Did you forget to source your build system environment setup 
script?"
+   exit 1
 fi
 . $SYSROOT_SETUP_SCRIPT meta-ide-support
 PSEUDO_OPTS="-P $OECORE_NATIVE_SYSROOT/usr"
@@ -42,9 +42,9 @@ ROOTFS_TARBALL=$1
 SDK_ROOTFS_DIR=$2
 
 if [ ! -e "$ROOTFS_TARBALL" ]; then
-   echo "Error: sdk tarball '$ROOTFS_TARBALL' does not exist"
-   usage
-   exit 1
+   echo "Error: sdk tarball '$ROOTFS_TARBALL' does not exist"
+   usage
+   exit 1
 fi
 
 # Convert SDK_ROOTFS_DIR to a full pathname
@@ -84,7 +84,7 @@ debug_image="`echo $ROOTFS_TARBALL | grep '\-dbg\.tar\.'`"
 if [ -e "$pseudo_state_dir" -a -z "$debug_image" ]; then
echo "Error: $pseudo_state_dir already exists!"
echo "Please delete the rootfs tree and pseudo directory manually"
-echo "if this is really what you want."
+   echo "if this is really what you want."
exit 1
 fi
 
-- 
2.17.1

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


Re: [OE-core] [PATCH] gcc8: drop stray uClibc specific patch

2018-06-13 Thread Khem Raj
On 6/13/18 10:28 AM, Andre McCurdy wrote:
> The patch was previously removed for gcc7 but came back with gcc8.
> 
>   
> http://git.openembedded.org/openembedded-core/commit/?id=f71bc69e5b7581c53071055b694bb0dbfe4b4a87
> 

This is ok to apply, thanks for noticing it. I am planning to look into
the patches wholesale and see what we can remove. We have been carrying
several patches for long time.

> Signed-off-by: Andre McCurdy 
> ---
>  meta/recipes-devtools/gcc/gcc-8.1.inc  |  1 -
>  .../gcc/gcc-8.1/0002-c99-snprintf.patch| 28 
> --
>  2 files changed, 29 deletions(-)
>  delete mode 100644 meta/recipes-devtools/gcc/gcc-8.1/0002-c99-snprintf.patch
> 
> diff --git a/meta/recipes-devtools/gcc/gcc-8.1.inc 
> b/meta/recipes-devtools/gcc/gcc-8.1.inc
> index cb0fbd9..d83ba65 100644
> --- a/meta/recipes-devtools/gcc/gcc-8.1.inc
> +++ b/meta/recipes-devtools/gcc/gcc-8.1.inc
> @@ -32,7 +32,6 @@ BASEURI ?= "${GNU_MIRROR}/gcc/gcc-${PV}/gcc-${PV}.tar.xz"
>  SRC_URI = "\
> ${BASEURI} \
> file://0001-gcc-4.3.1-ARCH_FLAGS_FOR_TARGET.patch \
> -   file://0002-c99-snprintf.patch \
> file://0003-gcc-poison-system-directories.patch \
> file://0004-gcc-poison-dir-extend.patch \
> file://0005-gcc-4.3.3-SYSROOT_CFLAGS_FOR_TARGET.patch \
> diff --git a/meta/recipes-devtools/gcc/gcc-8.1/0002-c99-snprintf.patch 
> b/meta/recipes-devtools/gcc/gcc-8.1/0002-c99-snprintf.patch
> deleted file mode 100644
> index aa123b4..000
> --- a/meta/recipes-devtools/gcc/gcc-8.1/0002-c99-snprintf.patch
> +++ /dev/null
> @@ -1,28 +0,0 @@
> -From 5fbfcf247ed6dd01263639daf0c9c3a291e2fd3a Mon Sep 17 00:00:00 2001
> -From: Khem Raj 
> -Date: Fri, 29 Mar 2013 08:49:03 +0400
> -Subject: [PATCH 02/39] c99-snprintf
> -
> -Signed-off-by: Khem Raj 
> -
> -Upstream-Status: Pending
> 
> - libstdc++-v3/include/c_std/cstdio | 2 +-
> - 1 file changed, 1 insertion(+), 1 deletion(-)
> -
> -diff --git a/libstdc++-v3/include/c_std/cstdio 
> b/libstdc++-v3/include/c_std/cstdio
> -index 1b9571eaa8d..ad816be4fd1 100644
>  a/libstdc++-v3/include/c_std/cstdio
> -+++ b/libstdc++-v3/include/c_std/cstdio
> -@@ -144,7 +144,7 @@ namespace std
> -   using ::vsprintf;
> - } // namespace std
> - 
> --#if _GLIBCXX_USE_C99_STDIO
> -+#if _GLIBCXX_USE_C99_STDIO || defined(__UCLIBC__)
> - 
> - #undef snprintf
> - #undef vfscanf
> --- 
> -2.17.0
> -
> 




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


Re: [OE-core] [PATCH v3] ltp: fix cve-2017-5669 test case

2018-06-13 Thread Saul Wold

Can this be backported to both Rocko and Sumo?

Or is this a case to update LTP in those older releases?


Sau!


On 06/12/2018 12:34 AM, Naresh Kamboju wrote:

Adding cve-2017-5669 test fix patch which is accepted upstream in LTP repo.

Ref:
cve-2017-5669: shmat() for 0 (or https://github.com/linux-test-project/ltp/pull/324

Upstream-Status: Accepted [https://github.com/linux-test-project/ltp/pull/324]
CVE: cve-2017-5669
Signed-off-by: Naresh Kamboju 
---
  ...69-shmat-for-0-or-PAGESIZE-with-RND-flag-.patch | 97 ++
  meta/recipes-extended/ltp/ltp_20180515.bb  |  1 +
  2 files changed, 98 insertions(+)
  create mode 100644 
meta/recipes-extended/ltp/ltp/0041-cve-2017-5669-shmat-for-0-or-PAGESIZE-with-RND-flag-.patch

diff --git 
a/meta/recipes-extended/ltp/ltp/0041-cve-2017-5669-shmat-for-0-or-PAGESIZE-with-RND-flag-.patch
 
b/meta/recipes-extended/ltp/ltp/0041-cve-2017-5669-shmat-for-0-or-PAGESIZE-with-RND-flag-.patch
new file mode 100644
index 000..2a47785
--- /dev/null
+++ 
b/meta/recipes-extended/ltp/ltp/0041-cve-2017-5669-shmat-for-0-or-PAGESIZE-with-RND-flag-.patch
@@ -0,0 +1,97 @@
+From b767b73ef027ba8d35f297c7d3659265ac80425b Mon Sep 17 00:00:00 2001
+From: Rafael David Tinoco 
+Date: Wed, 30 May 2018 09:14:34 -0300
+Subject: [PATCH] cve-2017-5669: shmat() for 0 (or https://github.com/linux-test-project/ltp/issues/319
+
+According to upstream thread (https://lkml.org/lkml/2018/5/28/2056),
+cve-2017-5669 needs to address the "new" way of handling nil addresses
+for shmat() when used with MAP_FIXED or SHM_REMAP flags.
+
+- mapping nil-page is OK on lower addresses with MAP_FIXED (or else X11 is 
broken)
+- mapping nil-page is NOT OK with SHM_REMAP on lower addresses
+
+Addresses Davidlohr Bueso's comments/changes:
+
+commit 8f89c007b6de
+Author: Davidlohr Bueso 
+Date:   Fri May 25 14:47:30 2018 -0700
+
+ipc/shm: fix shmat() nil address after round-down when remapping
+
+commit a73ab244f0da
+Author: Davidlohr Bueso 
+Date:   Fri May 25 14:47:27 2018 -0700
+
+Revert "ipc/shm: Fix shmat mmap nil-page protection"
+
+For previously test, and now broken, made based on:
+
+commit 95e91b831f87
+Author: Davidlohr Bueso 
+Date:   Mon Feb 27 14:28:24 2017 -0800
+
+ipc/shm: Fix shmat mmap nil-page protection
+
+Signed-off-by: Rafael David Tinoco 
+Tested-by: Naresh Kamboju 
+Reviewed-by: Jan Stancek 
+
+Upstream-Status: Accepted [https://github.com/linux-test-project/ltp/pull/324]
+CVE: cve-2017-5669
+Signed-off-by: Rafael David Tinoco 
+---
+ testcases/cve/cve-2017-5669.c | 20 +++-
+ 1 file changed, 19 insertions(+), 1 deletion(-)
+
+diff --git a/testcases/cve/cve-2017-5669.c b/testcases/cve/cve-2017-5669.c
+index 1ca5983..0834626 100644
+--- a/testcases/cve/cve-2017-5669.c
 b/testcases/cve/cve-2017-5669.c
+@@ -28,7 +28,20 @@
+  * is just to see if we get an access error or some other unexpected 
behaviour.
+  *
+  * See commit 95e91b831f (ipc/shm: Fix shmat mmap nil-page protection)
++ *
++ * The commit above disallowed SHM_RND maps to zero (and rounded) entirely and
++ * that broke userland for cases like Xorg. New behavior disallows REMAPs to
++ * lower addresses (0<=PAGESIZE).
++ *
++ * See commit a73ab244f0da (Revert "ipc/shm: Fix shmat mmap nil-page 
protect...)
++ * See commit 8f89c007b6de (ipc/shm: fix shmat() nil address after 
round-dow...)
++ * See https://github.com/linux-test-project/ltp/issues/319
++ *
++ * This test needs root permissions or else security_mmap_addr(), from
++ * get_unmapped_area(), will cause permission errors when trying to mmap lower
++ * addresses.
+  */
++
+ #include 
+ #include 
+ #include 
+@@ -60,7 +73,11 @@ static void cleanup(void)
+ static void run(void)
+ {
+   tst_res(TINFO, "Attempting to attach shared memory to null page");
+-  shm_addr = shmat(shm_id, ((void *)1), SHM_RND);
++  /*
++   * shmat() for 0 (or < PAGESIZE with RND flag) has to fail with REMAPs
++   * https://github.com/linux-test-project/ltp/issues/319
++   */
++  shm_addr = shmat(shm_id, ((void *)1), SHM_RND | SHM_REMAP);
+   if (shm_addr == (void *)-1) {
+   shm_addr = NULL;
+   if (errno == EINVAL) {
+@@ -89,6 +106,7 @@ static void run(void)
+ }
+
+ static struct tst_test test = {
++  .needs_root = 1,
+   .setup = setup,
+   .cleanup = cleanup,
+   .test_all = run,
+--
+2.7.4
+
diff --git a/meta/recipes-extended/ltp/ltp_20180515.bb 
b/meta/recipes-extended/ltp/ltp_20180515.bb
index b07c1b9..48739f1 100644
--- a/meta/recipes-extended/ltp/ltp_20180515.bb
+++ b/meta/recipes-extended/ltp/ltp_20180515.bb
@@ -41,6 +41,7 @@ SRC_URI = "git://github.com/linux-test-project/ltp.git \
 
file://0036-testcases-network-nfsv4-acl-acl1.c-Security-fix-on-s.patch \
 file://0039-commands-ar01-Fix-for-test-in-deterministic-mode.patch 
\
 
file://0040-read_all-Define-FNM_EXTMATCH-if-not-already-like-und.patch \
+   

[OE-core] [PATCH] gcc8: drop stray uClibc specific patch

2018-06-13 Thread Andre McCurdy
The patch was previously removed for gcc7 but came back with gcc8.

  
http://git.openembedded.org/openembedded-core/commit/?id=f71bc69e5b7581c53071055b694bb0dbfe4b4a87

Signed-off-by: Andre McCurdy 
---
 meta/recipes-devtools/gcc/gcc-8.1.inc  |  1 -
 .../gcc/gcc-8.1/0002-c99-snprintf.patch| 28 --
 2 files changed, 29 deletions(-)
 delete mode 100644 meta/recipes-devtools/gcc/gcc-8.1/0002-c99-snprintf.patch

diff --git a/meta/recipes-devtools/gcc/gcc-8.1.inc 
b/meta/recipes-devtools/gcc/gcc-8.1.inc
index cb0fbd9..d83ba65 100644
--- a/meta/recipes-devtools/gcc/gcc-8.1.inc
+++ b/meta/recipes-devtools/gcc/gcc-8.1.inc
@@ -32,7 +32,6 @@ BASEURI ?= "${GNU_MIRROR}/gcc/gcc-${PV}/gcc-${PV}.tar.xz"
 SRC_URI = "\
${BASEURI} \
file://0001-gcc-4.3.1-ARCH_FLAGS_FOR_TARGET.patch \
-   file://0002-c99-snprintf.patch \
file://0003-gcc-poison-system-directories.patch \
file://0004-gcc-poison-dir-extend.patch \
file://0005-gcc-4.3.3-SYSROOT_CFLAGS_FOR_TARGET.patch \
diff --git a/meta/recipes-devtools/gcc/gcc-8.1/0002-c99-snprintf.patch 
b/meta/recipes-devtools/gcc/gcc-8.1/0002-c99-snprintf.patch
deleted file mode 100644
index aa123b4..000
--- a/meta/recipes-devtools/gcc/gcc-8.1/0002-c99-snprintf.patch
+++ /dev/null
@@ -1,28 +0,0 @@
-From 5fbfcf247ed6dd01263639daf0c9c3a291e2fd3a Mon Sep 17 00:00:00 2001
-From: Khem Raj 
-Date: Fri, 29 Mar 2013 08:49:03 +0400
-Subject: [PATCH 02/39] c99-snprintf
-
-Signed-off-by: Khem Raj 
-
-Upstream-Status: Pending

- libstdc++-v3/include/c_std/cstdio | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/libstdc++-v3/include/c_std/cstdio 
b/libstdc++-v3/include/c_std/cstdio
-index 1b9571eaa8d..ad816be4fd1 100644
 a/libstdc++-v3/include/c_std/cstdio
-+++ b/libstdc++-v3/include/c_std/cstdio
-@@ -144,7 +144,7 @@ namespace std
-   using ::vsprintf;
- } // namespace std
- 
--#if _GLIBCXX_USE_C99_STDIO
-+#if _GLIBCXX_USE_C99_STDIO || defined(__UCLIBC__)
- 
- #undef snprintf
- #undef vfscanf
--- 
-2.17.0
-
-- 
1.9.1

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


Re: [OE-core] [PATCH 6/8] xserver-xorg: upgrade 1.19.6 -> 1.20.0

2018-06-13 Thread Burton, Ross
On 1 June 2018 at 16:15, akuster808  wrote:
>
>
> On 05/28/2018 07:25 AM, akuster808 wrote:
>>
>> On 05/23/2018 04:01 AM, Burton, Ross wrote:
>>> This is breaking a number of other bits of X:
>>>
>>> - xf86-video-intel (was DRI1 removed or disabled in 1.20?)
> DRI 1 is still there.

https://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=359477215092ac1b602ad1e2f17a28963d9224c2
claims otherwise.  Trivial enough to disable in our recipe, I'll send
a patch shortly.

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


Re: [OE-core] [PATCH] xorgproto: Install .pc files in ${libdir}/pkgconfig

2018-06-13 Thread Burton, Ross
Send the patch in to oe-core with Upstream-Status: Submitted, and
hopefully we can drop it shortly.

Ross

On 13 June 2018 at 15:32, Jeremy A. Puhlman  wrote:
> Okay I did some test builds and nuking the libdir lines worked fine.
>
> The patch is submitted here:
> https://lists.x.org/archives/xorg-devel/2018-June/057123.html
>
> It wasn't rejected out of hand. Did you want me to roll a update to this
> with the submitted
> patch, or did you want to wait to see how it pays out on the x-org list?
>
>
> On 6/11/2018 9:35 AM, Burton, Ross wrote:
>>
>> I'd recommend deleting the libdir lines in every .pc file (and pushing
>> the patch upstream).
>>
>> Ross
>>
>> On 11 June 2018 at 17:19, Jeremy A. Puhlman  wrote:
>>>
>>>
>>> On 6/11/2018 3:23 AM, Burton, Ross wrote:

 Upstream will (and do) argue that $datadir is the right location as
 these headers are architecture-independent.

 Would the package manager do the right thing if the files didn't have
 the libdir line in, so where bit-identical?
>>>
>>>
>>> Yes, if the files are binary identical then the package manager would not
>>> call it a conflict.
>>>
>>>
 Ross

 On 10 June 2018 at 20:01, Jeremy Puhlman  wrote:
>
> * --data dir config option is only used to install pkgconfig
> * Installing into ${datadir} causes mutlilib conficts on install
>
> file /usr/share/pkgconfig/applewmproto.pc conflicts between
> attempted
> installs of lib32-xorgproto-dev-2018.4-r0.i586 and
> xorgproto-dev-2018.4-r0.corei7_64
> file /usr/share/pkgconfig/bigreqsproto.pc conflicts between
> attempted
> installs of lib32-xorgproto-dev-2018.4-r0.i586 and
> xorgproto-dev-2018.4-r0.corei7_64
>
> and so on.
>
> Signed-off-by: Jeremy Puhlman 
> ---
>meta/recipes-graphics/xorg-proto/xorg-proto-common.inc | 2 +-
>1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-graphics/xorg-proto/xorg-proto-common.inc
> b/meta/recipes-graphics/xorg-proto/xorg-proto-common.inc
> index 7a417c9..7377283 100644
> --- a/meta/recipes-graphics/xorg-proto/xorg-proto-common.inc
> +++ b/meta/recipes-graphics/xorg-proto/xorg-proto-common.inc
> @@ -14,7 +14,7 @@ S = "${WORKDIR}/${XORG_PN}-${PV}"
>DEPENDS = "util-macros"
>
>inherit autotools pkgconfig
> -EXTRA_OECONF = "--without-fop"
> +EXTRA_OECONF = "--without-fop --datadir=${libdir}"
>
>UNKNOWN_CONFIGURE_WHITELIST += "--without-fop --without-xmlto
> --with-xmlto"
>
> --
> 2.6.2
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>>
>>>
>>> --
>>> Jeremy A. Puhlman
>>> jpuhl...@mvista.com
>>>
>
> --
> Jeremy A. Puhlman
> jpuhl...@mvista.com
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH v2] sqlite3: upgrade to 3.24.0

2018-06-13 Thread Khem Raj

Hi Maxin

On 6/13/18 7:54 AM, Maxin B. John wrote:

Disable fts5 support as it causes build errors for pseudo.

Signed-off-by: Maxin B. John 
---
  meta/recipes-support/sqlite/sqlite3.inc  | 1 +
  meta/recipes-support/sqlite/{sqlite3_3.23.1.bb => sqlite3_3.24.0.bb} | 4 ++--
  2 files changed, 3 insertions(+), 2 deletions(-)
  rename meta/recipes-support/sqlite/{sqlite3_3.23.1.bb => sqlite3_3.24.0.bb} 
(59%)

diff --git a/meta/recipes-support/sqlite/sqlite3.inc 
b/meta/recipes-support/sqlite/sqlite3.inc
index 95ec89c..7312c84 100644
--- a/meta/recipes-support/sqlite/sqlite3.inc
+++ b/meta/recipes-support/sqlite/sqlite3.inc
@@ -31,6 +31,7 @@ EXTRA_OECONF = " \
  --enable-shared \
  --enable-threadsafe \
  --disable-static-shell \
+--enable-fts5=no \
  "


is this causing issues for pseudo target recipe ?
perhaps its better to turn it into a packageconfig

  
  CFLAGS_append = " -fPIC"

diff --git a/meta/recipes-support/sqlite/sqlite3_3.23.1.bb 
b/meta/recipes-support/sqlite/sqlite3_3.24.0.bb
similarity index 59%
rename from meta/recipes-support/sqlite/sqlite3_3.23.1.bb
rename to meta/recipes-support/sqlite/sqlite3_3.24.0.bb
index 3755761..ce18fec 100644
--- a/meta/recipes-support/sqlite/sqlite3_3.23.1.bb
+++ b/meta/recipes-support/sqlite/sqlite3_3.24.0.bb
@@ -6,5 +6,5 @@ LIC_FILES_CHKSUM = 
"file://sqlite3.h;endline=11;md5=786d3dc581eff03f4fd9e4a77ed0
  SRC_URI = "\
http://www.sqlite.org/2018/sqlite-autoconf-${SQLITE_PV}.tar.gz \
"
-SRC_URI[md5sum] = "99a51b40a66872872a91c92f6d0134fa"
-SRC_URI[sha256sum] = 
"92842b283e5e744eff5da29ed3c69391de7368fccc4d0ee6bf62490ce555ef25"
+SRC_URI[md5sum] = "dcd96fb9bbb603d29f6b0ad9554932ee"
+SRC_URI[sha256sum] = 
"d9d14e88c6fb6d68de9ca0d1f9797477d82fc3aed613558f87ffbdbbc5ceb74a"


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


[OE-core] [PATCH v2] sqlite3: upgrade to 3.24.0

2018-06-13 Thread Maxin B. John
Disable fts5 support as it causes build errors for pseudo.

Signed-off-by: Maxin B. John 
---
 meta/recipes-support/sqlite/sqlite3.inc  | 1 +
 meta/recipes-support/sqlite/{sqlite3_3.23.1.bb => sqlite3_3.24.0.bb} | 4 ++--
 2 files changed, 3 insertions(+), 2 deletions(-)
 rename meta/recipes-support/sqlite/{sqlite3_3.23.1.bb => sqlite3_3.24.0.bb} 
(59%)

diff --git a/meta/recipes-support/sqlite/sqlite3.inc 
b/meta/recipes-support/sqlite/sqlite3.inc
index 95ec89c..7312c84 100644
--- a/meta/recipes-support/sqlite/sqlite3.inc
+++ b/meta/recipes-support/sqlite/sqlite3.inc
@@ -31,6 +31,7 @@ EXTRA_OECONF = " \
 --enable-shared \
 --enable-threadsafe \
 --disable-static-shell \
+--enable-fts5=no \
 "
 
 CFLAGS_append = " -fPIC"
diff --git a/meta/recipes-support/sqlite/sqlite3_3.23.1.bb 
b/meta/recipes-support/sqlite/sqlite3_3.24.0.bb
similarity index 59%
rename from meta/recipes-support/sqlite/sqlite3_3.23.1.bb
rename to meta/recipes-support/sqlite/sqlite3_3.24.0.bb
index 3755761..ce18fec 100644
--- a/meta/recipes-support/sqlite/sqlite3_3.23.1.bb
+++ b/meta/recipes-support/sqlite/sqlite3_3.24.0.bb
@@ -6,5 +6,5 @@ LIC_FILES_CHKSUM = 
"file://sqlite3.h;endline=11;md5=786d3dc581eff03f4fd9e4a77ed0
 SRC_URI = "\
   http://www.sqlite.org/2018/sqlite-autoconf-${SQLITE_PV}.tar.gz \
   "
-SRC_URI[md5sum] = "99a51b40a66872872a91c92f6d0134fa"
-SRC_URI[sha256sum] = 
"92842b283e5e744eff5da29ed3c69391de7368fccc4d0ee6bf62490ce555ef25"
+SRC_URI[md5sum] = "dcd96fb9bbb603d29f6b0ad9554932ee"
+SRC_URI[sha256sum] = 
"d9d14e88c6fb6d68de9ca0d1f9797477d82fc3aed613558f87ffbdbbc5ceb74a"
-- 
2.4.0

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


Re: [OE-core] [PATCH 6/8] xserver-xorg: upgrade 1.19.6 -> 1.20.0

2018-06-13 Thread akuster808



On 06/13/2018 03:17 AM, Burton, Ross wrote:
> On 1 June 2018 at 16:15, akuster808  wrote:
 - xf86-video-intel (was DRI1 removed or disabled in 1.20?)
>> DRI 1 is still there.
>>
 - xf86-input-mouse
>> sent fixed for xf86-inout-mount
>>
 - xf86-video-omapfb
>>> hmm, will double check
> Tried it again last night:
>
> omapfb: http://errors.yoctoproject.org/Errors/Details/179606/
> intel: http://errors.yoctoproject.org/Errors/Details/179607/

thanks.

please pull the update. fixing those two very old packages may take a while.

- armin
>
> Ross


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


Re: [OE-core] [PATCH] xorgproto: Install .pc files in ${libdir}/pkgconfig

2018-06-13 Thread Jeremy A. Puhlman

Okay I did some test builds and nuking the libdir lines worked fine.

The patch is submitted here:
https://lists.x.org/archives/xorg-devel/2018-June/057123.html

It wasn't rejected out of hand. Did you want me to roll a update to this 
with the submitted

patch, or did you want to wait to see how it pays out on the x-org list?

On 6/11/2018 9:35 AM, Burton, Ross wrote:

I'd recommend deleting the libdir lines in every .pc file (and pushing
the patch upstream).

Ross

On 11 June 2018 at 17:19, Jeremy A. Puhlman  wrote:


On 6/11/2018 3:23 AM, Burton, Ross wrote:

Upstream will (and do) argue that $datadir is the right location as
these headers are architecture-independent.

Would the package manager do the right thing if the files didn't have
the libdir line in, so where bit-identical?


Yes, if the files are binary identical then the package manager would not
call it a conflict.



Ross

On 10 June 2018 at 20:01, Jeremy Puhlman  wrote:

* --data dir config option is only used to install pkgconfig
* Installing into ${datadir} causes mutlilib conficts on install

file /usr/share/pkgconfig/applewmproto.pc conflicts between attempted
installs of lib32-xorgproto-dev-2018.4-r0.i586 and
xorgproto-dev-2018.4-r0.corei7_64
file /usr/share/pkgconfig/bigreqsproto.pc conflicts between attempted
installs of lib32-xorgproto-dev-2018.4-r0.i586 and
xorgproto-dev-2018.4-r0.corei7_64

and so on.

Signed-off-by: Jeremy Puhlman 
---
   meta/recipes-graphics/xorg-proto/xorg-proto-common.inc | 2 +-
   1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-graphics/xorg-proto/xorg-proto-common.inc
b/meta/recipes-graphics/xorg-proto/xorg-proto-common.inc
index 7a417c9..7377283 100644
--- a/meta/recipes-graphics/xorg-proto/xorg-proto-common.inc
+++ b/meta/recipes-graphics/xorg-proto/xorg-proto-common.inc
@@ -14,7 +14,7 @@ S = "${WORKDIR}/${XORG_PN}-${PV}"
   DEPENDS = "util-macros"

   inherit autotools pkgconfig
-EXTRA_OECONF = "--without-fop"
+EXTRA_OECONF = "--without-fop --datadir=${libdir}"

   UNKNOWN_CONFIGURE_WHITELIST += "--without-fop --without-xmlto
--with-xmlto"

--
2.6.2

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


--
Jeremy A. Puhlman
jpuhl...@mvista.com



--
Jeremy A. Puhlman
jpuhl...@mvista.com

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


Re: [OE-core] [PATCH 10/12] sqlite3: upgrade to 3.24.0

2018-06-13 Thread Maxin B. John
Hi Ross,

On Tue, Jun 12, 2018 at 04:22:30PM +0100, Burton, Ross wrote:
> Fails for me when building pseudo:
> 
> | 
> /data/poky-tmp/master/work/x86_64-linux/pseudo-native/1.9.0+gitAUTOINC+fddbe854c9-r0/recipe-sysroot-native/usr/lib/libsqlite3.a(sqlite3.o):
> In function `fts5Bm25Function':
> | sqlite3.c:(.text+0x2a3b8): undefined reference to `log'

In the previous version of sqlite3, FTS5 (full-text search) support was disabled
by default. However, in version 3.24.0, fts5 is "silently" enabled by default.
That causes this build failure. We can explicitly disable fts5 in sqlite3 to 
fix it.

> Ross

Best Regards,
Maxin

> On 12 June 2018 at 12:18, Maxin B. John  wrote:
> > 3.23.1 -> 3.24.0
> >
> > Signed-off-by: Maxin B. John 
> > ---
> >  meta/recipes-support/sqlite/{sqlite3_3.23.1.bb => sqlite3_3.24.0.bb} | 4 
> > ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> >  rename meta/recipes-support/sqlite/{sqlite3_3.23.1.bb => 
> > sqlite3_3.24.0.bb} (59%)
> >
> > diff --git a/meta/recipes-support/sqlite/sqlite3_3.23.1.bb 
> > b/meta/recipes-support/sqlite/sqlite3_3.24.0.bb
> > similarity index 59%
> > rename from meta/recipes-support/sqlite/sqlite3_3.23.1.bb
> > rename to meta/recipes-support/sqlite/sqlite3_3.24.0.bb
> > index 3755761..ce18fec 100644
> > --- a/meta/recipes-support/sqlite/sqlite3_3.23.1.bb
> > +++ b/meta/recipes-support/sqlite/sqlite3_3.24.0.bb
> > @@ -6,5 +6,5 @@ LIC_FILES_CHKSUM = 
> > "file://sqlite3.h;endline=11;md5=786d3dc581eff03f4fd9e4a77ed0
> >  SRC_URI = "\
> >http://www.sqlite.org/2018/sqlite-autoconf-${SQLITE_PV}.tar.gz \
> >"
> > -SRC_URI[md5sum] = "99a51b40a66872872a91c92f6d0134fa"
> > -SRC_URI[sha256sum] = 
> > "92842b283e5e744eff5da29ed3c69391de7368fccc4d0ee6bf62490ce555ef25"
> > +SRC_URI[md5sum] = "dcd96fb9bbb603d29f6b0ad9554932ee"
> > +SRC_URI[sha256sum] = 
> > "d9d14e88c6fb6d68de9ca0d1f9797477d82fc3aed613558f87ffbdbbc5ceb74a"
> > --
> > 2.4.0
> >
> > --
> > ___
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH] goarch.bbclass: set SECURITY_CFLAGS for mips64

2018-06-13 Thread Khem Raj
On Wed, Jun 13, 2018 at 12:16 AM  wrote:
>
> From: Kai Kang 
>
> When include conf/distro/include/security_flags.inc, NOPIE flags are
> still required for MIPS64 target builds. Otherwise it fails to build
> packages such as glide which inherit go.bbclass:
>
> | 
> .../tmp-glibc/work/mips64-wrs-linux/glide/0.13.1-r0/recipe-sysroot-native/usr/bin/mips64-wrs-linux/../../libexec/mips64-wrs-linux/
> | gcc/mips64-wrs-linux/7.3.0/ld: 
> .../tmp-glibc/work/mips64-wrs-linux/glide/0.13.1-r0/go-tmp/go-link-518447869/go.o:
> | relocation R_MIPS_26 against `a local symbol' can not be used when making a 
> shared object; recompile with -fPIC`
>
> Signed-off-by: Kai Kang 
> ---
>  meta/classes/goarch.bbclass | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/meta/classes/goarch.bbclass b/meta/classes/goarch.bbclass
> index f54c5169e3e..5fd9f294a8a 100644
> --- a/meta/classes/goarch.bbclass
> +++ b/meta/classes/goarch.bbclass
> @@ -36,6 +36,7 @@ COMPATIBLE_HOST_mipsarchn32 = "null"
>  ARM_INSTRUCTION_SET = "arm"
>  TUNE_CCARGS_remove = "-march=mips32r2"
>  SECURITY_CFLAGS_mips = "${SECURITY_NOPIE_CFLAGS}"
> +SECURITY_CFLAGS_mips64 = "${SECURITY_NOPIE_CFLAGS}"

perhaps we should use _mipsall once

>  SECURITY_NOPIE_CFLAGS ??= ""
>
>  def go_map_arch(a, d):
> --
> 2.17.1
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH] libdrm: port to Meson

2018-06-13 Thread Ross Burton
Signed-off-by: Ross Burton 
---
 ...ac-Allow-explicit-enabling-of-cunit-tests.patch | 53 --
 .../recipes-graphics/drm/libdrm/installtests.patch | 25 --
 meta/recipes-graphics/drm/libdrm_2.4.92.bb | 23 --
 3 files changed, 9 insertions(+), 92 deletions(-)
 delete mode 100644 
meta/recipes-graphics/drm/libdrm/0001-configure.ac-Allow-explicit-enabling-of-cunit-tests.patch
 delete mode 100644 meta/recipes-graphics/drm/libdrm/installtests.patch

diff --git 
a/meta/recipes-graphics/drm/libdrm/0001-configure.ac-Allow-explicit-enabling-of-cunit-tests.patch
 
b/meta/recipes-graphics/drm/libdrm/0001-configure.ac-Allow-explicit-enabling-of-cunit-tests.patch
deleted file mode 100644
index 40bebc0f50c..000
--- 
a/meta/recipes-graphics/drm/libdrm/0001-configure.ac-Allow-explicit-enabling-of-cunit-tests.patch
+++ /dev/null
@@ -1,53 +0,0 @@
-From e6bd4205b0b546afe991ae6f72256645f4404ad4 Mon Sep 17 00:00:00 2001
-From: Jussi Kukkonen 
-Date: Mon, 5 Sep 2016 14:41:37 +0300
-Subject: [PATCH libdrm] configure.ac: Allow explicit enabling of cunit tests
-
-Add --with-cunit to make it easier to do reproducible builds. Default
-is still to probe cunit and build opportunistically.
-
-Signed-off-by: Jussi Kukkonen 
-Upstream-Status: Submitted [mailing list]

- configure.ac | 14 --
- 1 file changed, 12 insertions(+), 2 deletions(-)
-
-Index: libdrm-2.4.91/configure.ac
-===
 libdrm-2.4.91.orig/configure.ac
-+++ libdrm-2.4.91/configure.ac
-@@ -163,6 +163,12 @@ AC_ARG_ENABLE(install-test-programs,
- [Install test programs (default: no)]),
- [INSTALL_TESTS=$enableval], [INSTALL_TESTS=no])
- 
-+AC_ARG_WITH([cunit],
-+[AS_HELP_STRING([--with-cunit],
-+[Build tests that use cunit (default: auto)])],
-+[],
-+[with_cunit=auto])
-+
- dnl 
===
- dnl check compiler flags
- AC_DEFUN([LIBDRM_CC_TRY_FLAG], [
-@@ -411,7 +417,7 @@ else
-   AC_DEFINE(HAVE_RADEON, 0)
- fi
- 
--if test "x$AMDGPU" != xno; then
-+if test "x$with_cunit" != xno -a "x$AMDGPU" != xno; then
-   # Detect cunit library
-   PKG_CHECK_MODULES([CUNIT], [cunit >= 2.1], [have_cunit=yes], 
[have_cunit=no])
-   # If pkg-config does not find cunit, check it using AC_CHECK_LIB.  We
-@@ -436,7 +442,11 @@ if test "x$AMDGPU" = xyes; then
-   AC_DEFINE(HAVE_AMDGPU, 1, [Have amdgpu support])
- 
-   if test "x$have_cunit" = "xno"; then
--  AC_MSG_WARN([Could not find cunit library. Disabling amdgpu 
tests])
-+  if test "x$with_cunit" = "xyes"; then
-+  AC_MSG_ERROR([Could not find cunit library but 
--with-cunit was given])
-+  elif test "x$with_cunit" = "xauto"; then
-+  AC_MSG_WARN([Could not find cunit library. Disabling 
amdgpu tests])
-+  fi
-   fi
- else
-   AC_DEFINE(HAVE_AMDGPU, 0)
diff --git a/meta/recipes-graphics/drm/libdrm/installtests.patch 
b/meta/recipes-graphics/drm/libdrm/installtests.patch
deleted file mode 100644
index ec1fb0236e4..000
--- a/meta/recipes-graphics/drm/libdrm/installtests.patch
+++ /dev/null
@@ -1,25 +0,0 @@
-From 5c6eb43c2f6e7f2ee7c25c92e42f4e4403fa0527 Mon Sep 17 00:00:00 2001
-From: Jussi Kukkonen 
-Date: Tue, 21 Feb 2017 14:37:52 +0200
-Subject: [PATCH] tests: also install test apps
-
-Upstream-Status: Inappropriate [configuration]
-
-Signed-off-by: Yu Ke 
-Signed-off-by: Jussi Kukkonen 

- tests/Makefile.am | 1 +
- 1 file changed, 1 insertion(+)
-
-diff --git a/tests/Makefile.am b/tests/Makefile.am
-index 0355a92..b4882cd 100644
 a/tests/Makefile.am
-+++ b/tests/Makefile.am
-@@ -45,3 +45,4 @@ TESTS = \
- check_PROGRAMS = \
-   $(TESTS) \
-   drmdevice
-+bin_PROGRAMS = $(check_PROGRAMS)
--- 
-2.1.4
-
diff --git a/meta/recipes-graphics/drm/libdrm_2.4.92.bb 
b/meta/recipes-graphics/drm/libdrm_2.4.92.bb
index 2b3bf4f83d2..e77ac671e9d 100644
--- a/meta/recipes-graphics/drm/libdrm_2.4.92.bb
+++ b/meta/recipes-graphics/drm/libdrm_2.4.92.bb
@@ -10,24 +10,19 @@ LIC_FILES_CHKSUM = 
"file://xf86drm.c;beginline=9;endline=32;md5=c8a3b961af7667c5
 PROVIDES = "drm"
 DEPENDS = "libpthread-stubs libpciaccess"
 
-SRC_URI = "http://dri.freedesktop.org/libdrm/${BP}.tar.bz2 \
-   file://installtests.patch \
-   
file://0001-configure.ac-Allow-explicit-enabling-of-cunit-tests.patch \
-  "
-
+SRC_URI = "http://dri.freedesktop.org/libdrm/${BP}.tar.bz2;
 SRC_URI[md5sum] = "f9b00d985f82d0be6ecc20c799acc89e"
 SRC_URI[sha256sum] = 
"e9e48fdb4de139dc4d9880aa1473158a16ff6aff63d14341367bd30a51ff39fa"
 
-inherit autotools pkgconfig manpages
+inherit meson pkgconfig manpages
+
+EXTRA_OEMESON = "-Dvalgrind=false \
+ -Dcairo-tests=false \
+ -Dinstall-test-programs=true \
+ 

Re: [OE-core] [PATCH 1/7] openssh: stop adding -D__FILE_OFFSET_BITS=64 to CFLAGS

2018-06-13 Thread Burton, Ross
Looks good to me, marked for MUT.

Ross

On 12 June 2018 at 18:38, Andre McCurdy  wrote:
> On Thu, Jun 7, 2018 at 11:48 AM, Andre McCurdy  wrote:
>> Openssh takes care of enabling large-file support automatically via
>> the AC_SYS_LARGEFILE in the configure.ac, so additional help from the
>> recipe is not required.
>>
>> Even if it were once required, defining __FILE_OFFSET_BITS (ie with
>> double leading underscores) looks like a typo and probably never had
>> any effect anyway?
>
> Ping.
>
> Any issues with this (the whole series of 7)?
>
>> Signed-off-by: Andre McCurdy 
>> ---
>>  meta/recipes-connectivity/openssh/openssh_7.7p1.bb | 3 ---
>>  1 file changed, 3 deletions(-)
>>
>> diff --git a/meta/recipes-connectivity/openssh/openssh_7.7p1.bb 
>> b/meta/recipes-connectivity/openssh/openssh_7.7p1.bb
>> index 7b6ee5c..7cf34eb 100644
>> --- a/meta/recipes-connectivity/openssh/openssh_7.7p1.bb
>> +++ b/meta/recipes-connectivity/openssh/openssh_7.7p1.bb
>> @@ -46,9 +46,6 @@ SYSTEMD_SERVICE_${PN}-sshd = "sshd.socket"
>>
>>  inherit autotools-brokensep ptest
>>
>> -# LFS support:
>> -CFLAGS += "-D__FILE_OFFSET_BITS=64"
>> -
>>  EXTRA_AUTORECONF += "--exclude=aclocal"
>>
>>  # login path is hardcoded in sshd
>> --
>> 1.9.1
>>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH] meson: only use lists of commands in cross file if required

2018-06-13 Thread Ross Burton
There's a bug in Meson[1] where it find_program("foo") will fail if foo is
defined in the cross file as a list.

This is causing the Meson build of libdrm to fail, but for this instance we can
work around the problem by only using lists in the cross file if there are
arguments, and just using a string if there are not.

[1] https://github.com/mesonbuild/meson/issues/3737

Signed-off-by: Ross Burton 
---
 meta/classes/meson.bbclass | 25 +
 1 file changed, 13 insertions(+), 12 deletions(-)

diff --git a/meta/classes/meson.bbclass b/meta/classes/meson.bbclass
index 5881765abba..e572344bd20 100644
--- a/meta/classes/meson.bbclass
+++ b/meta/classes/meson.bbclass
@@ -42,7 +42,8 @@ MESON_CROSS_FILE_class-target = "--cross-file 
${WORKDIR}/meson.cross"
 MESON_CROSS_FILE_class-nativesdk = "--cross-file ${WORKDIR}/meson.cross"
 
 def meson_array(var, d):
-return "', '".join(d.getVar(var).split()).join(("'", "'"))
+items = d.getVar(var).split()
+return repr(items[0] if len(items) == 1 else items)
 
 addtask write_config before do_configure
 do_write_config[vardeps] += "MESON_C_ARGS MESON_CPP_ARGS MESON_LINK_ARGS CC 
CXX LD AR NM STRIP READELF"
@@ -50,21 +51,21 @@ do_write_config() {
 # This needs to be Py to split the args into single-element lists
 cat >${WORKDIR}/meson.cross 

Re: [OE-core] [PATCH 6/8] xserver-xorg: upgrade 1.19.6 -> 1.20.0

2018-06-13 Thread Burton, Ross
On 1 June 2018 at 16:15, akuster808  wrote:
>>> - xf86-video-intel (was DRI1 removed or disabled in 1.20?)
> DRI 1 is still there.
>
>>> - xf86-input-mouse
> sent fixed for xf86-inout-mount
>
>>> - xf86-video-omapfb
>> hmm, will double check

Tried it again last night:

omapfb: http://errors.yoctoproject.org/Errors/Details/179606/
intel: http://errors.yoctoproject.org/Errors/Details/179607/

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


Re: [OE-core] [PATCH V2] bitbake.conf: add BB_CURRENT_MC to OVERRIDES

2018-06-13 Thread Ming Liu
Yes, that is true, but then I will need have a mc-default override set in
local.conf any way, since I need distinguish the build for all
multiconfigs, that makes me think it'd better to have a single
mc-${BB_CURRENT_MC} set in OVERRIDES.

//Ming Liu

2018-06-12 19:49 GMT+02:00 Andre McCurdy :

> On Tue, Jun 12, 2018 at 4:43 AM, Ming Liu  wrote:
> > Hi, Andre:
> > The reason for needing this multiconfig to be in OVERRIDES, for me, is
> the
> > scenario that I have one recipe but some variables/tasks in it are
> different
> > for multiconfig, for instance:
> >
> > do_install-mc-default () {}
> >
> > do_install-mc-foo() {}
> >
> > and I do not want split them into several almost same recipes with only
> one
> > task different.
>
> Yes, that's clear. But the question is whether you can make the
> over-rides you need self contained within the multiconfig config file?
>
> e.g. to enable an over-ride when you build with multiconfig foo, add:
>
>   OVERRIDES .= ":mc-foo"
>
> to foo.conf
>
> If it works, then it gives you more flexibility - you can pick your
> own over-ride naming, define multiple over-rides per multiconfig, etc.
>
> > //Ming Liu
> >
> > 2018-06-12 1:15 GMT+02:00 Andre McCurdy :
> >>
> >> On Mon, Jun 11, 2018 at 4:34 AM,   wrote:
> >> > From: Ming Liu 
> >> >
> >> > This is useful when the users want different variables/tasks when
> using
> >> > multiconfig.
> >>
> >> Isn't the idea of multiconfig to select between configurations which
> >> already fully define all necessary over-rides?
> >>
> >> If a particular multiconfig build needs a custom over-ride then the
> >> multiconfig can append to OVERRIDES (or MACHINEOVERRIDES etc, as
> >> appropriate) directly.
> >>
> >> ie to avoid confusion isn't it good if building with a multiconfig
> >> enabled is always equivalent to building with the contents of the
> >> multiconfig file copied directly in local.conf?
> >>
> >> > Signed-off-by: Ming Liu 
> >> > ---
> >> >  meta/conf/bitbake.conf | 2 +-
> >> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >> >
> >> > diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> >> > index 3b2ef9f..0c803d5 100644
> >> > --- a/meta/conf/bitbake.conf
> >> > +++ b/meta/conf/bitbake.conf
> >> > @@ -731,7 +731,7 @@ DISTRO_NAME ??= "OpenEmbedded"
> >> >  # And finally '_forcevariable' overrides any standard variable,
> >> > with the highest priority.
> >> >  # This works for functions as well, they are really just variables.
> >> >  #
> >> > -OVERRIDES =
> >> > "${TARGET_OS}:${TRANSLATED_TARGET_ARCH}:pn-${PN}:${
> MACHINEOVERRIDES}:${DISTROOVERRIDES}:${CLASSOVERRIDE}${LIBCOVERRIDE}:
> forcevariable"
> >> > +OVERRIDES =
> >> > "${TARGET_OS}:${TRANSLATED_TARGET_ARCH}:pn-${PN}:${
> MACHINEOVERRIDES}:${DISTROOVERRIDES}:${CLASSOVERRIDE}${LIBCOVERRIDE}:
> mc-${BB_CURRENT_MC}:forcevariable"
> >> >  LIBCOVERRIDE ?= ""
> >> >  CLASSOVERRIDE ?= "class-target"
> >> >  DISTROOVERRIDES ?= "${@d.getVar('DISTRO') or ''}"
> >> > --
> >> > 2.7.4
> >> >
> >> > --
> >> > ___
> >> > Openembedded-core mailing list
> >> > Openembedded-core@lists.openembedded.org
> >> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
> >
> >
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH 07/12] libunistring: upgrade to 0.9.10

2018-06-13 Thread Maxin B. John
Hi Randy,

On Tue, Jun 12, 2018 at 09:21:17PM -0400, Randy MacLeod wrote:
> On 06/12/2018 07:18 AM, Maxin B. John wrote:
> >License-Update: Checksum changed due to updation in documentation. There
> >are no changes in the license terms.
> 
> That's correct but I'm not sure if we should include
> a checksum on the (GPLv3) COPYING file since the README
> says [1] that:
>This license is based on the GNU GPL version 3, see file COPYING.
> I'd like to know if the COPYING file changed to say the _actual_
> GPLv2 some day so a checksum would help track such changes.
> 
> 
> The README statement is an odd way to convey the license terms.
> Is this just standard FSFese?

Yes, it is odd.

README says 'The libunistring library and its header files are dual-licensed 
under
"the GNU LGPLv3+ or the GNU GPLv2"' and the project includes a GPL v3 license 
(COPYING).

Though not 100% sure, I would assume that it is ok continue with 
LICENSE = "LGPLv3+ | GPLv2"  

If anyone think it is the wrong way to go, please share your views/suggestions.

> The libunistring commit that sets out these terms is from 0.9:
> 
> commit 3c15d3a96963703fc02cddda7e968e508638d1b8
> Author: Bruno Haible 
> Date:   Sun Mar 15 02:10:58 2009 +0100
> 
> License information.
> 
>  COPYING | 674 ...
>  COPYING.LIB | 165 +...
>  ChangeLog   |   3 +
>  README  |   2 +-
>  4 files changed, 843 insertions(+), 1 deletion(-)
> 
> 
> which doesn't help much other than the ChangeLog:
> 
> +   * COPYING.LIB: New file, from gnulib/doc/COPYING.LESSERv3.
> +   * COPYING: New file, from gnulib/doc/COPYINGv3.
> 
> 
> ../Randy

Best Regards,
Maxin

> 
> [1] From README:
> 
> Copyright
> -
> 
> The libunistring library and its header files are dual-licensed under
> "the GNU LGPLv3+ or the GNU GPLv2". This means, you can use it under either
>   - the terms of the GNU Lesser General Public License (LGPL) version 3 or
> (at your option) any later version, or
>   - the terms of the GNU General Public License (GPL) version 2, or
>   - the same dual license "the GNU LGPLv3+ or the GNU GPLv2".
> 
> You find the GNU LGPL version 3 in the file COPYING.LIB.  This license is
> based on the GNU GPL version 3, see file COPYING.
> 
> You can find the GNU GPL version 2 at
> .
> 
> Note: This dual license makes it possible for the libunistring library
> to be used by packages under GPLv2 or GPLv2+ licenses, in particular. See
> the table in .
> 
> The documentation is under another license; see in the documentation.
> 
> >
> >Signed-off-by: Maxin B. John 
> >---
> >  .../libunistring/{libunistring_0.9.9.bb => libunistring_0.9.10.bb}  | 6 
> > +++---
> >  1 file changed, 3 insertions(+), 3 deletions(-)
> >  rename meta/recipes-support/libunistring/{libunistring_0.9.9.bb => 
> > libunistring_0.9.10.bb} (85%)
> >
> >diff --git a/meta/recipes-support/libunistring/libunistring_0.9.9.bb 
> >b/meta/recipes-support/libunistring/libunistring_0.9.10.bb
> >similarity index 85%
> >rename from meta/recipes-support/libunistring/libunistring_0.9.9.bb
> >rename to meta/recipes-support/libunistring/libunistring_0.9.10.bb
> >index ab7cba5..97fac4e 100644
> >--- a/meta/recipes-support/libunistring/libunistring_0.9.9.bb
> >+++ b/meta/recipes-support/libunistring/libunistring_0.9.10.bb
> >@@ -16,15 +16,15 @@ SECTION = "devel"
> >  LICENSE = "LGPLv3+ | GPLv2"
> >  LIC_FILES_CHKSUM = 
> > "file://COPYING.LIB;md5=6a6a8e020838b23406c81b19c1d46df6 \
> >  
> > file://README;beginline=45;endline=65;md5=08287d16ba8d839faed8d2dc14d7d6a5 \
> >-
> >file://doc/libunistring.texi;md5=efb80a3799a60f95feaf80661d4f204c \
> >+
> >file://doc/libunistring.texi;md5=287fa6075f78a3c85c1a52b0a92547cd \
> > "
> >  SRC_URI = "${GNU_MIRROR}/libunistring/libunistring-${PV}.tar.gz \
> > file://iconv-m4-remove-the-test-to-convert-euc-jp.patch \
> > 
> > file://0001-Unset-need_charset_alias-when-building-for-musl.patch \
> >  "
> >-SRC_URI[md5sum] = "4f689e37e4c3bd67de5786aa51d98b13"
> >-SRC_URI[sha256sum] = 
> >"f5e90c08f9e5427ca3a2c0c53f19aa38b25c500913510ad25afef86448bea84a"
> >+SRC_URI[md5sum] = "0d3274e9838396b12200f8b54ddaf43b"
> >+SRC_URI[sha256sum] = 
> >"a82e5b39a88ea4608e4635479a1cfb2e01aafb925e1290b65710d43f610b"
> >  inherit autotools texinfo
> >  BBCLASSEXTEND = "native nativesdk"
> >
> 
> 
> -- 
> # Randy MacLeod
> # Wind River Linux
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH 3/7] watchdog: disable systemd services by default

2018-06-13 Thread Chen Qi
systemd has internal support for watchdog. See the RuntimeWatchdogSec
in /etc/systemd/system.conf.

We'd better just disable this service by default. If users want to use
watchdog, consider using the systemd one.

Signed-off-by: Chen Qi 
---
 meta/recipes-extended/watchdog/watchdog_5.15.bb | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-extended/watchdog/watchdog_5.15.bb 
b/meta/recipes-extended/watchdog/watchdog_5.15.bb
index d3f0353..bfaed9a 100644
--- a/meta/recipes-extended/watchdog/watchdog_5.15.bb
+++ b/meta/recipes-extended/watchdog/watchdog_5.15.bb
@@ -40,6 +40,9 @@ INITSCRIPT_PARAMS_${PN}-keepalive = "start 15 1 2 3 4 5 . 
stop 85 0 6 ."
 SYSTEMD_PACKAGES = "${PN} ${PN}-keepalive"
 SYSTEMD_SERVICE_${PN} = "watchdog.service"
 SYSTEMD_SERVICE_${PN}-keepalive = "wd_keepalive.service"
+# When using systemd, consider making use of internal watchdog support of 
systemd.
+# See RuntimeWatchdogSec in /etc/systemd/system.conf.
+SYSTEMD_AUTO_ENABLE = "disable"
 
 do_install_append() {
install -d ${D}${systemd_system_unitdir}
-- 
1.9.1

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


[OE-core] [PATCH 5/7] watchdog: fix init script for sysvinit

2018-06-13 Thread Chen Qi
The current init script is installed from source with redhat style.
It does not get configuration from /etc/default/watchdog. We should use
debian style init script.

Write our own script just like what wd_keepalive does.
Also, in the init script, we check the existence of /dev/watchdog to
determine whether to start the daemon or not.

Signed-off-by: Chen Qi 
---
 .../watchdog/watchdog/watchdog-init.patch  |  56 ---
 .../watchdog/watchdog/watchdog.init| 110 +
 meta/recipes-extended/watchdog/watchdog_5.15.bb|   6 +-
 3 files changed, 113 insertions(+), 59 deletions(-)
 delete mode 100644 meta/recipes-extended/watchdog/watchdog/watchdog-init.patch
 create mode 100644 meta/recipes-extended/watchdog/watchdog/watchdog.init

diff --git a/meta/recipes-extended/watchdog/watchdog/watchdog-init.patch 
b/meta/recipes-extended/watchdog/watchdog/watchdog-init.patch
deleted file mode 100644
index b2765f1..000
--- a/meta/recipes-extended/watchdog/watchdog/watchdog-init.patch
+++ /dev/null
@@ -1,56 +0,0 @@
-Signed-off-by: Diego Rondini 
-Upstream-Status: Inappropriate
-
 watchdog-5.13.orig/redhat/watchdog.init2014-11-12 17:18:39.125943000 
+0100
-+++ watchdog-5.13/redhat/watchdog.init 2014-11-12 18:27:36.189943000 +0100
-@@ -7,7 +7,7 @@
- # Henning P. Schmiedehausen 
- 
- # Source function library.
--. /etc/rc.d/init.d/functions
-+. /etc/init.d/functions
- 
- [ -x /usr/sbin/watchdog -a -e /etc/watchdog.conf ] || exit 0
- 
-@@ -23,22 +23,22 @@
- 
- start() {
- 
--  echo -n $"Starting $prog: "
-+  echo -n "Starting $prog: "
-   if [ -n "$(pidofproc $prog)" ]; then
--  echo -n $"$prog: already running"
--  echo_failure
-+  echo -n "$prog: already running "
-+  failure
-   echo
-   return 1
-   fi
-   if [ "$VERBOSE" = "yes" ]; then
--  daemon /usr/sbin/${prog} -v
-+  /usr/sbin/${prog} -v
-   else
--  daemon /usr/sbin/${prog}
-+  /usr/sbin/${prog}
- fi
-   RETVAL=$?
-   [ $RETVAL -eq 0 ] && touch $lockfile
--  [ $RETVAL -eq 0 ] && echo_success
--  [ $RETVAL -ne 0 ] && echo_failure
-+  [ $RETVAL -eq 0 ] && success
-+  [ $RETVAL -ne 0 ] && failure
-   echo
-   return $RETVAL
- }
-@@ -50,8 +50,10 @@
-   # and reboot the box.
-   killproc $prog -TERM
-   RETVAL=$?
--  echo
-   [ $RETVAL -eq 0 ] && rm -f $lockfile $pidfile
-+  [ $RETVAL -eq 0 ] && success
-+  [ $RETVAL -ne 0 ] && failure
-+  echo
-   return $RETVAL
- }
- 
diff --git a/meta/recipes-extended/watchdog/watchdog/watchdog.init 
b/meta/recipes-extended/watchdog/watchdog/watchdog.init
new file mode 100644
index 000..d37107c
--- /dev/null
+++ b/meta/recipes-extended/watchdog/watchdog/watchdog.init
@@ -0,0 +1,110 @@
+#!/bin/sh
+#/etc/init.d/watchdog: start watchdog daemon.
+
+### BEGIN INIT INFO
+# Provides:  watchdog
+# Short-Description: Start software watchdog daemon
+# Required-Start:$all
+# Required-Stop: $all
+# Should-Start:  
+# Should-Stop:   
+# Default-Start: 2 3 4 5
+# Default-Stop:  0 1 6
+### END INIT INFO
+
+PATH=/bin:/usr/bin:/sbin:/usr/sbin
+
+test -x /usr/sbin/watchdog || exit 0
+
+# For configuration of the init script use the file
+# /etc/default/watchdog, do not edit this init script.
+
+# Set run_watchdog to 1 to start watchdog or 0 to disable it.
+run_watchdog=0
+
+# Specify additional watchdog options here (see manpage).
+watchdog_options=""
+
+# Specify module to load
+watchdog_module="none"
+
+[ -e /etc/default/watchdog ] && . /etc/default/watchdog
+
+NAME=watchdog
+DAEMON=/usr/sbin/watchdog
+
+STOP_RETRY_SCHEDULE='TERM/10/forever/KILL/1'
+
+. /etc/init.d/functions
+
+# Mock Debian stuff
+log_begin_msg() {
+echo -n $*
+}
+
+log_end_msg() {
+if [ "$1" = "0" ]; then
+echo 'done'
+else
+echo 'error'
+fi
+}
+
+log_daemon_msg() {
+echo $*
+}
+
+log_progress_msg() {
+echo $*
+}
+
+case "$1" in
+  start)
+if [ $run_watchdog = 1 ]
+then
+   # do we have to load a module?
+   [ "${watchdog_module:-none}" != "none" ] && /sbin/modprobe 
$watchdog_module
+
+   # Check /dev/watchdog here because if it does not exist after module 
loading,
+   # it makes no sense to start the daemon
+   test -e /dev/watchdog || { log_daemon_msg "daemon not start due to lack 
of /dev/watchdog"; exit 0; }
+
+   log_begin_msg "Starting watchdog daemon..."
+   start-stop-daemon --start --quiet --pidfile /var/run/$NAME.pid \
+ --exec $DAEMON -- $watchdog_options
+   log_end_msg $?
+fi
+;;
+
+  stop)
+if [ $run_watchdog = 1 ]
+then
+   log_begin_msg "Stopping watchdog daemon..."
+   start-stop-daemon --stop --quiet --retry $STOP_RETRY_SCHEDULE \
+   --pidfile /var/run/$NAME.pid
+   
+fi
+;;
+
+  restart)
+$0 force-reload
+;;

[OE-core] [PATCH 7/7] dnf: default to disable systemd units

2018-06-13 Thread Chen Qi
The services and timers are not useful if a repo is not configured.
In OE, we default to have no repo configured. So we default to disable
these units.

The problem was found by the test_systemd_failed runtime test case.
dnf-makecache.service is found to fail. This is due to lack of repo.
Note that as this service is started by the dnf-makecache.timer, it's
possible that test_systemd_failed passes in case the timer is not started
yet.

Signed-off-by: Chen Qi 
---
 meta/recipes-devtools/dnf/dnf_2.7.5.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-devtools/dnf/dnf_2.7.5.bb 
b/meta/recipes-devtools/dnf/dnf_2.7.5.bb
index b88ddb4..df60d73 100644
--- a/meta/recipes-devtools/dnf/dnf_2.7.5.bb
+++ b/meta/recipes-devtools/dnf/dnf_2.7.5.bb
@@ -72,3 +72,4 @@ SYSTEMD_SERVICE_${PN} = "dnf-makecache.service 
dnf-makecache.timer \
  dnf-automatic-install.service 
dnf-automatic-install.timer \
  dnf-automatic-notifyonly.service 
dnf-automatic-notifyonly.timer \
 "
+SYSTEMD_AUTO_ENABLE ?= "disable"
-- 
1.9.1

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


[OE-core] [PATCH 0/7] Fix failures discoved by parselogs and systemd test cases

2018-06-13 Thread Chen Qi
The following changes since commit ddbd7b0cd6580ee26e11aa87e426fb294b372d64:

  meta-yocto-bsp: bump to the latest linux stable kernel for 
edgerouter/beaglebone (2018-06-12 23:34:40 +0100)

are available in the git repository at:

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

Chen Qi (7):
  oeqa/runtime/cases/parselogs.py: extend common_errors list
  watchdog: remove the useless watchdog-conf.patch
  watchdog: disable systemd services by default
  watchdog: make init script start after syslog
  watchdog: fix init script for sysvinit
  oeqa/runtime/cases/parselogs.py: ignore a message from watchdog
  dnf: default to disable systemd units

 meta/lib/oeqa/runtime/cases/parselogs.py   |   2 +
 meta/recipes-devtools/dnf/dnf_2.7.5.bb |   1 +
 .../watchdog/watchdog/watchdog-conf.patch  |  16 ---
 .../watchdog/watchdog/watchdog-init.patch  |  56 ---
 .../watchdog/watchdog/watchdog.init| 110 +
 meta/recipes-extended/watchdog/watchdog_5.15.bb|  14 +--
 6 files changed, 121 insertions(+), 78 deletions(-)
 delete mode 100644 meta/recipes-extended/watchdog/watchdog/watchdog-conf.patch
 delete mode 100644 meta/recipes-extended/watchdog/watchdog/watchdog-init.patch
 create mode 100644 meta/recipes-extended/watchdog/watchdog/watchdog.init

-- 
1.9.1

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


[OE-core] [PATCH 1/7] oeqa/runtime/cases/parselogs.py: extend common_errors list

2018-06-13 Thread Chen Qi
Add the following line to common_errors list.

  Failed to read /var/lib/nfs/statd/state: Success

This message is not harmful, it does not result in rpc.statd starting
failure.

Signed-off-by: Chen Qi 
---
 meta/lib/oeqa/runtime/cases/parselogs.py | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/lib/oeqa/runtime/cases/parselogs.py 
b/meta/lib/oeqa/runtime/cases/parselogs.py
index 1f36c61..bfebb38 100644
--- a/meta/lib/oeqa/runtime/cases/parselogs.py
+++ b/meta/lib/oeqa/runtime/cases/parselogs.py
@@ -49,6 +49,7 @@ common_errors = [
 "error: couldn\'t mount because of unsupported optional features",
 "GPT: Use GNU Parted to correct GPT errors",
 "Cannot set xattr user.Librepo.DownloadInProgress",
+"Failed to read /var/lib/nfs/statd/state: Success",
 ]
 
 video_related = [
-- 
1.9.1

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


[OE-core] [PATCH 4/7] watchdog: make init script start after syslog

2018-06-13 Thread Chen Qi
We need to make sure logs are not lost. As long as there's no
strong and vaild reason, we should make daemons start after syslog.

As a side effect, we could check the logs to see if there are
some potential problem. In OE, the 'parselogs' test case could
do it automatically.

Signed-off-by: Chen Qi 
---
 meta/recipes-extended/watchdog/watchdog_5.15.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-extended/watchdog/watchdog_5.15.bb 
b/meta/recipes-extended/watchdog/watchdog_5.15.bb
index bfaed9a..8353ec0 100644
--- a/meta/recipes-extended/watchdog/watchdog_5.15.bb
+++ b/meta/recipes-extended/watchdog/watchdog_5.15.bb
@@ -32,10 +32,10 @@ EXTRA_OECONF += " --disable-nfs "
 INITSCRIPT_PACKAGES = "${PN} ${PN}-keepalive"
 
 INITSCRIPT_NAME_${PN} = "watchdog.sh"
-INITSCRIPT_PARAMS_${PN} = "start 15 1 2 3 4 5 . stop 85 0 6 ."
+INITSCRIPT_PARAMS_${PN} = "start 25 1 2 3 4 5 . stop 85 0 6 ."
 
 INITSCRIPT_NAME_${PN}-keepalive = "wd_keepalive"
-INITSCRIPT_PARAMS_${PN}-keepalive = "start 15 1 2 3 4 5 . stop 85 0 6 ."
+INITSCRIPT_PARAMS_${PN}-keepalive = "start 25 1 2 3 4 5 . stop 85 0 6 ."
 
 SYSTEMD_PACKAGES = "${PN} ${PN}-keepalive"
 SYSTEMD_SERVICE_${PN} = "watchdog.service"
-- 
1.9.1

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


[OE-core] [PATCH 6/7] oeqa/runtime/cases/parselogs.py: ignore a message from watchdog

2018-06-13 Thread Chen Qi
The following message from watchdog is not an error.

  "error retry time-out = 60 seconds"

Checking watchdog's source codes, we have:

  src/watchdog.c: log_message(LOG_INFO, "error retry time-out = %d seconds", 
retry_timeout);

It's clear this is an info message, so parselogs should ignore it.

Signed-off-by: Chen Qi 
---
 meta/lib/oeqa/runtime/cases/parselogs.py | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/lib/oeqa/runtime/cases/parselogs.py 
b/meta/lib/oeqa/runtime/cases/parselogs.py
index bfebb38..1cdea58 100644
--- a/meta/lib/oeqa/runtime/cases/parselogs.py
+++ b/meta/lib/oeqa/runtime/cases/parselogs.py
@@ -50,6 +50,7 @@ common_errors = [
 "GPT: Use GNU Parted to correct GPT errors",
 "Cannot set xattr user.Librepo.DownloadInProgress",
 "Failed to read /var/lib/nfs/statd/state: Success",
+"error retry time-out =",
 ]
 
 video_related = [
-- 
1.9.1

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


[OE-core] [PATCH 2/7] watchdog: remove the useless watchdog-conf.patch

2018-06-13 Thread Chen Qi
This patch modifies watchdog.conf file. But this file is deliberately
deleted in do_install. The current mechanism in OE is to use another
recipe watchdog-conf to handle watchdog configuration. So the patch
is really useless.

Signed-off-by: Chen Qi 
---
 .../watchdog/watchdog/watchdog-conf.patch| 16 
 meta/recipes-extended/watchdog/watchdog_5.15.bb  |  1 -
 2 files changed, 17 deletions(-)
 delete mode 100644 meta/recipes-extended/watchdog/watchdog/watchdog-conf.patch

diff --git a/meta/recipes-extended/watchdog/watchdog/watchdog-conf.patch 
b/meta/recipes-extended/watchdog/watchdog/watchdog-conf.patch
deleted file mode 100644
index ec44c80..000
--- a/meta/recipes-extended/watchdog/watchdog/watchdog-conf.patch
+++ /dev/null
@@ -1,16 +0,0 @@
-Signed-off-by: Diego Rondini 
-Upstream-Status: Inappropriate
-
-Index: watchdog-5.15/watchdog.conf
-===
 watchdog-5.15.orig/watchdog.conf
-+++ watchdog-5.15/watchdog.conf
-@@ -28,7 +28,7 @@
- #retry-timeout= 60
- #repair-maximum   = 1
- 
--#watchdog-device  = /dev/watchdog
-+watchdog-device   = /dev/watchdog
- 
- # Defaults compiled into the binary
- #temperature-sensor   =
diff --git a/meta/recipes-extended/watchdog/watchdog_5.15.bb 
b/meta/recipes-extended/watchdog/watchdog_5.15.bb
index 24791c4..d3f0353 100644
--- a/meta/recipes-extended/watchdog/watchdog_5.15.bb
+++ b/meta/recipes-extended/watchdog/watchdog_5.15.bb
@@ -12,7 +12,6 @@ SRC_URI = 
"${SOURCEFORGE_MIRROR}/watchdog/watchdog-${PV}.tar.gz \

file://0001-Include-linux-param.h-for-EXEC_PAGESIZE-definition.patch \

file://0001-watchdog-remove-interdependencies-of-watchdog-and-wd.patch \
file://watchdog-init.patch \
-   file://watchdog-conf.patch \
file://wd_keepalive.init \
 "
 
-- 
1.9.1

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


[OE-core] [PATCH] openssh: add nativesdk support

2018-06-13 Thread Mikko Rapeli
And use bitbake variables for install paths to fix nativesdk-openssh
compilation.

Signed-off-by: Mikko Rapeli 
---
 meta/recipes-connectivity/openssh/openssh_7.7p1.bb | 6 --
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-connectivity/openssh/openssh_7.7p1.bb 
b/meta/recipes-connectivity/openssh/openssh_7.7p1.bb
index 7b6ee5c..bdd6123 100644
--- a/meta/recipes-connectivity/openssh/openssh_7.7p1.bb
+++ b/meta/recipes-connectivity/openssh/openssh_7.7p1.bb
@@ -55,9 +55,9 @@ EXTRA_AUTORECONF += "--exclude=aclocal"
 EXTRA_OECONF = "'LOGIN_PROGRAM=${base_bindir}/login' \
 ${@bb.utils.contains('DISTRO_FEATURES', 'pam', '--with-pam', 
'--without-pam', d)} \
 --without-zlib-version-check \
---with-privsep-path=/var/run/sshd \
+--with-privsep-path=${localstatedir}/run/sshd \
 --sysconfdir=${sysconfdir}/ssh \
---with-xauth=/usr/bin/xauth \
+--with-xauth=${bindir}/xauth \
 --disable-strip \
 "
 
@@ -164,3 +164,5 @@ CONFFILES_${PN}-ssh = "${sysconfdir}/ssh/ssh_config"
 ALTERNATIVE_PRIORITY = "90"
 ALTERNATIVE_${PN}-scp = "scp"
 ALTERNATIVE_${PN}-ssh = "ssh"
+
+BBCLASSEXTEND += "nativesdk"
-- 
1.9.1

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


[OE-core] [PATCH] goarch.bbclass: set SECURITY_CFLAGS for mips64

2018-06-13 Thread kai.kang
From: Kai Kang 

When include conf/distro/include/security_flags.inc, NOPIE flags are
still required for MIPS64 target builds. Otherwise it fails to build
packages such as glide which inherit go.bbclass:

| 
.../tmp-glibc/work/mips64-wrs-linux/glide/0.13.1-r0/recipe-sysroot-native/usr/bin/mips64-wrs-linux/../../libexec/mips64-wrs-linux/
| gcc/mips64-wrs-linux/7.3.0/ld: 
.../tmp-glibc/work/mips64-wrs-linux/glide/0.13.1-r0/go-tmp/go-link-518447869/go.o:
| relocation R_MIPS_26 against `a local symbol' can not be used when making a 
shared object; recompile with -fPIC`

Signed-off-by: Kai Kang 
---
 meta/classes/goarch.bbclass | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/classes/goarch.bbclass b/meta/classes/goarch.bbclass
index f54c5169e3e..5fd9f294a8a 100644
--- a/meta/classes/goarch.bbclass
+++ b/meta/classes/goarch.bbclass
@@ -36,6 +36,7 @@ COMPATIBLE_HOST_mipsarchn32 = "null"
 ARM_INSTRUCTION_SET = "arm"
 TUNE_CCARGS_remove = "-march=mips32r2"
 SECURITY_CFLAGS_mips = "${SECURITY_NOPIE_CFLAGS}"
+SECURITY_CFLAGS_mips64 = "${SECURITY_NOPIE_CFLAGS}"
 SECURITY_NOPIE_CFLAGS ??= ""
 
 def go_map_arch(a, d):
-- 
2.17.1

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