Re: [OE-core] [meta-oe][PATCH 1/2] chrpath: fix SRC_URI

[Alexander Kanavin]

2018-06-02 1:14 GMT+03:00 Oleksandr Kravchuk
:
> -SRC_URI = 
> "https://alioth.debian.org/frs/download.php/file/3979/chrpath-0.16.tar.gz \
> +SRC_URI = 
> "https://src.fedoraproject.org/lookaside/extras/chrpath/chrpath-0.16.tar.gz/2bf8d1d1ee345fc8a7915576f5649982/chrpath-0.16.tar.gz
>  \
> file://standarddoc.patch"

It's better to stick with debian, the tarball is still available
through ${DEBIAN_MIRROR}:
http://http.debian.net/debian/pool/main/c/chrpath/chrpath_0.16.orig.tar.gz

Can you also investigate the other instances of alioth, namely shadow
and minicom please?

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

Re: [OE-core] [meta-oe][PATCH 2/2] iso-codes: fix SRC_URI

[Alexander Kanavin]

2018-06-02 1:14 GMT+03:00 Oleksandr Kravchuk
:
>  SRC_URI = 
> "https://pkg-isocodes.alioth.debian.org/downloads/iso-codes-${PV}.tar.xz;
> +SRC_URI = 
> "https://ftp.osuosl.org/pub/blfs/conglomeration/iso-codes/iso-codes-${PV}.tar.xz;

The correct new URI is
https://salsa.debian.org/iso-codes-team/iso-codes, don't grab a random
ftp from google search results please.

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

Re: [OE-core] [PATCH 1/2] [meta] dbus: Fix X11 compille errors

[Alexander Kanavin]

Wait, why is this problem not seen by anyone else, particularly on the
autobuilder? Can you provide the failure log please?

And do the same for the other patch to atk.

Alex

2018-06-02 1:14 GMT+03:00 Alistair Francis :
> When building with X11 set in DISTRO_FEATURES we need to specify that we
> depend on X11 native for building dbus. Otherwise we see missing include
> file compile errors.
>
> Signed-off-by: Alistair Francis 
> ---
>  meta/recipes-core/dbus/dbus_1.12.8.bb | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-core/dbus/dbus_1.12.8.bb 
> b/meta/recipes-core/dbus/dbus_1.12.8.bb
> index b3ddaafab5..40868628f6 100644
> --- a/meta/recipes-core/dbus/dbus_1.12.8.bb
> +++ b/meta/recipes-core/dbus/dbus_1.12.8.bb
> @@ -6,6 +6,7 @@ LICENSE = "AFL-2 | GPLv2+"
>  LIC_FILES_CHKSUM = "file://COPYING;md5=10dded3b58148f3f1fd804b26354af3e \
>  
> file://dbus/dbus.h;beginline=6;endline=20;md5=7755c9d7abccd5dbd25a6a974538bb3c"
>  DEPENDS = "expat virtual/libintl autoconf-archive"
> +DEPENDS += "${@bb.utils.contains('DISTRO_FEATURES', 'x11', 'libx11-native', 
> '', d)}"
>  RDEPENDS_dbus_class-native = ""
>  RDEPENDS_dbus_class-nativesdk = ""
>  PACKAGES += "${@bb.utils.contains('DISTRO_FEATURES', 'ptest', '${PN}-ptest', 
> '', d)}"
> --
> 2.17.0
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] systemd: fix build with gcc8

[akuster808]

On 06/01/2018 08:42 AM, Martin Jansa wrote:
> Signed-off-by: Martin Jansa 
> ---
>  ...ild-with-gcc8-Werror-format-truncati.patch | 53 +++
>  meta/recipes-core/systemd/systemd_237.bb  |  1 +
>  2 files changed, 54 insertions(+)

I am seeing this same issue in Sumo and I have applied this patch.  Its
currently running a test build.
- armin
>  create mode 100644 
> meta/recipes-core/systemd/systemd/0036-time-util-fix-build-with-gcc8-Werror-format-truncati.patch
>
> diff --git 
> a/meta/recipes-core/systemd/systemd/0036-time-util-fix-build-with-gcc8-Werror-format-truncati.patch
>  
> b/meta/recipes-core/systemd/systemd/0036-time-util-fix-build-with-gcc8-Werror-format-truncati.patch
> new file mode 100644
> index 00..e44f431073
> --- /dev/null
> +++ 
> b/meta/recipes-core/systemd/systemd/0036-time-util-fix-build-with-gcc8-Werror-format-truncati.patch
> @@ -0,0 +1,53 @@
> +From f9fd4546c25a15629544bc4642a74d7909cc0840 Mon Sep 17 00:00:00 2001
> +From: Martin Jansa 
> +Date: Fri, 1 Jun 2018 15:22:28 +
> +Subject: [PATCH] time-util: fix build with gcc8 -Werror=format-truncation=
> +
> +* it fails with gcc8 when -O1 or -Os is used (and -ftree-vrp which is added 
> by -O2 and higher isn't used)
> +
> +../git/src/basic/time-util.c: In function 'format_timespan':
> +../git/src/basic/time-util.c:508:46: error: '%0*llu' directive output 
> between 1 and 2147483647 bytes may cause result to exceed 'INT_MAX' 
> [-Werror=format-truncation=]
> +  "%s"USEC_FMT".%0*"PRI_USEC"%s",
> +  ^~~~
> +../git/src/basic/time-util.c:508:60: note: format string is defined here
> +  "%s"USEC_FMT".%0*"PRI_USEC"%s",
> +../git/src/basic/time-util.c:508:46: note: directive argument in the range 
> [0, 18446744073709551614]
> +  "%s"USEC_FMT".%0*"PRI_USEC"%s",
> +  ^~~~
> +../git/src/basic/time-util.c:507:37: note: 'snprintf' output 4 or more bytes 
> (assuming 2147483651) into a destination of size 4294967295
> + k = snprintf(p, l,
> + ^~
> +  "%s"USEC_FMT".%0*"PRI_USEC"%s",
> +  ~~~
> +  p > buf ? " " : "",
> +  ~~~
> +  a,
> +  ~~
> +  j,
> +  ~~
> +  b,
> +  ~~
> +  table[i].suffix);
> +  
> +cc1: some warnings being treated as errors
> +
> +Upstream-Status: Submitted https://github.com/systemd/systemd/pull/9156
> +
> +Signed-off-by: Martin Jansa 
> +---
> + src/basic/time-util.c | 2 +-
> + 1 file changed, 1 insertion(+), 1 deletion(-)
> +
> +diff --git a/src/basic/time-util.c b/src/basic/time-util.c
> +index 0601d4fa9..db5a9cd78 100644
> +--- a/src/basic/time-util.c
>  b/src/basic/time-util.c
> +@@ -484,7 +484,7 @@ char *format_timespan(char *buf, size_t l, usec_t t, 
> usec_t accuracy) {
> + /* Let's see if we should shows this in dot notation */
> + if (t < USEC_PER_MINUTE && b > 0) {
> + usec_t cc;
> +-int j;
> ++char j;
> + 
> + j = 0;
> + for (cc = table[i].usec; cc > 1; cc /= 10)
> diff --git a/meta/recipes-core/systemd/systemd_237.bb 
> b/meta/recipes-core/systemd/systemd_237.bb
> index 2e6558ded1..0113c2dc72 100644
> --- a/meta/recipes-core/systemd/systemd_237.bb
> +++ b/meta/recipes-core/systemd/systemd_237.bb
> @@ -54,6 +54,7 @@ SRC_URI += "file://touchscreen.rules \
> file://libmount.patch \
> 
> file://0034-Fix-format-truncation-compile-failure-by-typecasting.patch \
> 
> file://0035-Define-glibc-compatible-basename-for-non-glibc-syste.patch \
> +   
> file://0036-time-util-fix-build-with-gcc8-Werror-format-truncati.patch \
> "
>  SRC_URI_append_qemuall = " 
> file://0001-core-device.c-Change-the-default-device-timeout-to-2.patch"
>  

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

Re: [OE-core] [PATCH] Meta runtime cases: add testcases for kernel sample

[Hongzhi, Song]

Hi Richard,

I have made patch-v2 with shared functions.
And these kernel-samples are just for testing, so maybe it's unnecessary 
to enable them by default.



On 2018年06月01日 16:12, Richard Purdie wrote:

On Fri, 2018-06-01 at 04:02 -0400, Hongzhi.Song wrote:

We are going to let runtime test support kernel tests. Now we just
add
kernel self-contained sample tests. And we plan to add overall kernel
tests in the future.

This patch is just add kernel samples test which contains about 13
tests
enabled by kernel-sample.scc. So it needs statement,
KERNEL_FEATURES_append += " kernel-sample/kernel-sample.scc" in
local.conf.

Signed-off-by: Hongzhi.Song 
---
  meta/lib/oeqa/runtime/cases/ksample.py | 440
+
  1 file changed, 440 insertions(+)
  create mode 100644 meta/lib/oeqa/runtime/cases/ksample.py

[...]

+# check config
+status, ret = self.target.run('zcat /proc/config.gz | grep 
CONFIG_TRACING_SUPPORT')
+result = "CONFIG_TRACING_SUPPORT=y" in ret
+if not result:
+self.skipTest("CONFIG error")
+# make sure if module exists
+status, ret = self.target.run('uname -r')
+cmd = "ls " + "/lib/modules/" + ret + 
"/kernel/samples/trace_events/trace-events-sample.ko"
+status, output = self.target.run(cmd)
+if status != 0:
+self.skipTest("trace-events-sample.ko doesn't exist")


There looks to be a fair bit of copy and paste code in these tests such
as the code above to look at config.gz. Could you turn some of these
into shared functions please?

Also, do we want to include this kernel-sample feature to the qemu
machines by default so that we enable these tests?

Cheers,

Richard




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

Re: [OE-core] [PATCH] tune-i586-nlp.inc: drop tuning file for Intel Quark/X1000 CPU

[Richard Purdie]

On Fri, 2018-06-01 at 10:21 -0700, Andre McCurdy wrote:
> On Fri, Jun 1, 2018 at 7:58 AM, Mark Hatle 
> wrote:
> > 
> > On 5/31/18 6:10 PM, Andre McCurdy wrote:
> > > 
> > > The Quark machine was EOL'ed at the end of 2017 and all support
> > > for
> > > it has now been removed from meta-intel. Drop the associated
> > > tuning
> > > file from oe-core.
> > I would rather this remain.  There are still a lot of people using
> > the quark
> > based boards as hobbyists... there is little effort to maintain it
> > for now.
> > 
> > (we still have support for ARMv4 for instance, which hasn't really
> > been used in
> > new designs in a while..)
> Is there ever a case when we would drop old tuning files? Or should
> they live on forever?
> 
> We dropped GPLv2 recipes from oe-core on the grounds that they are
> old, unmaintained and untested. ARMv4 CPU tuning files meet those
> criteria too.

We removed the GPLv2 recipes as they created a false sense of security
for people and a message needed to be sent out about them. They were a
maintenance problem.

These tune files aren't really causing a problem right now, from a
maintenance or security perspective.

Yes, we should remove things which are stale/obsolete and not useful
but I think people are using this file and its not causing a problem.

Cheers,

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

[OE-core] [PATCH 2/2] [meta] atk: Specify gettext-native dependency

[Alistair Francis]

atk requires xgettext to compile, specify it as a dependency.

Signed-off-by: Alistair Francis 
---
 meta/recipes-support/atk/atk_2.28.1.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-support/atk/atk_2.28.1.bb 
b/meta/recipes-support/atk/atk_2.28.1.bb
index 657c69d576..1198005804 100644
--- a/meta/recipes-support/atk/atk_2.28.1.bb
+++ b/meta/recipes-support/atk/atk_2.28.1.bb
@@ -8,7 +8,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=3bf50002aefd002f49e7bb854063f7e7 \
 
file://atk/atkutil.c;endline=18;md5=6fd31cd2fdc9b30f619ca8d819bc12d3 \
 
file://atk/atk.h;endline=18;md5=fcd7710187e0eae485e356c30d1b0c3b"
 
-DEPENDS = "glib-2.0"
+DEPENDS = "glib-2.0 gettext-native"
 
 GNOMEBASEBUILDCLASS = "meson"
 inherit gnomebase gtk-doc gettext upstream-version-is-even 
gobject-introspection
-- 
2.17.0

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

[OE-core] [PATCH 1/2] [meta] dbus: Fix X11 compille errors

[Alistair Francis]

When building with X11 set in DISTRO_FEATURES we need to specify that we
depend on X11 native for building dbus. Otherwise we see missing include
file compile errors.

Signed-off-by: Alistair Francis 
---
 meta/recipes-core/dbus/dbus_1.12.8.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-core/dbus/dbus_1.12.8.bb 
b/meta/recipes-core/dbus/dbus_1.12.8.bb
index b3ddaafab5..40868628f6 100644
--- a/meta/recipes-core/dbus/dbus_1.12.8.bb
+++ b/meta/recipes-core/dbus/dbus_1.12.8.bb
@@ -6,6 +6,7 @@ LICENSE = "AFL-2 | GPLv2+"
 LIC_FILES_CHKSUM = "file://COPYING;md5=10dded3b58148f3f1fd804b26354af3e \
 
file://dbus/dbus.h;beginline=6;endline=20;md5=7755c9d7abccd5dbd25a6a974538bb3c"
 DEPENDS = "expat virtual/libintl autoconf-archive"
+DEPENDS += "${@bb.utils.contains('DISTRO_FEATURES', 'x11', 'libx11-native', 
'', d)}"
 RDEPENDS_dbus_class-native = ""
 RDEPENDS_dbus_class-nativesdk = ""
 PACKAGES += "${@bb.utils.contains('DISTRO_FEATURES', 'ptest', '${PN}-ptest', 
'', d)}"
-- 
2.17.0

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

Re: [OE-core] [PATCH v2 5/7] toolchain-shar-extract: pass env to post-relocate

[Martin Kelly]

On 06/01/2018 03:08 PM, Joshua Watt wrote:

On Fri, 2018-06-01 at 14:02 -0700, Martin Kelly wrote:

It's useful for the post-relocate scripts to be able to see the SDK
environment, for example to see the values of CC, CXX etc. in order
to
dynamically generate toolchain files.

To enable this, source the SDK environment script prior to calling
the
relocate scripts.

Signed-off-by: Martin Kelly 
---
  meta/classes/toolchain-scripts.bbclass | 17 +
  meta/recipes-core/meta/meta-environment.bb |  5 +++--
  2 files changed, 16 insertions(+), 6 deletions(-)

diff --git a/meta/classes/toolchain-scripts.bbclass
b/meta/classes/toolchain-scripts.bbclass
index ae7bbef034..5f99fd8c03 100644
--- a/meta/classes/toolchain-scripts.bbclass
+++ b/meta/classes/toolchain-scripts.bbclass
@@ -118,11 +118,20 @@ EOF
  }
  
  toolchain_create_post_relocate_script() {

-   script=$1
-   rm -f $script
-   touch $script
+   relocate_script=$1
+   sdk_script=$2
+   rm -f $relocate_script
+   touch $relocate_script
+
+cat >> $relocate_script <

I had originally done something similar to this when I added support
for the post-relocate scripts with icecream. However, it is insufficent
because there can be multiple SDK environment scripts that need to be
sourced. In order to get a fully correct environment, I had to do:

  # Setup environment
  for env_setup_script in `ls $1/environment-setup-*`; do
. $env_setup_script
  done

see meta/recipes-devtools/icecc-toolchain/icecc-toolchain/icecc-
setup.sh




There's one overall "SDK environment" script (the one you source as a 
user to enter the SDK environment), and also customizable ones installed 
by nativesdk-* packages (e.g. one that cmake uses). In this patch, I had 
not intended that post-relocate scripts should be able to see the 
environment scripts for every project but instead just for the global 
SDK enivorment (to get at variables like OECORE_NATIVE_SYSROOT).


Let me know if I have missed something and not including the other 
environments could cause breakage.


Here's what I mean from an example extracted SDK:

martin@columbia:~$ ls /opt/xos/nanopi-neo-plus2/*environment*
/opt/xos/nanopi-neo-plus2/environment-setup-aarch64-poky-linux

martin@columbia:~$ ls 
/opt/xos/nanopi-neo-plus2/sysroots/x86_64-xevo-linux/environment-setup.d/

cmake.sh

In the above example, we are currently sourcing only 
/opt/xos/nanopi-neo-plus2/environment-setup-aarch64-poky-linux and not 
cmake.sh.

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

[OE-core] [meta-oe][PATCH 1/2] chrpath: fix SRC_URI

[Oleksandr Kravchuk]

Signed-off-by: Oleksandr Kravchuk 
---
 meta/recipes-devtools/chrpath/chrpath_0.16.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/chrpath/chrpath_0.16.bb 
b/meta/recipes-devtools/chrpath/chrpath_0.16.bb
index b61eef9c8b..0428210567 100644
--- a/meta/recipes-devtools/chrpath/chrpath_0.16.bb
+++ b/meta/recipes-devtools/chrpath/chrpath_0.16.bb
@@ -7,7 +7,7 @@ BUGTRACKER = 
"http://alioth.debian.org/tracker/?atid=412807_id=31052;
 LICENSE = "GPLv2"
 LIC_FILES_CHKSUM = "file://COPYING;md5=59530bdf33659b29e73d4adb9f9f6552"
 
-SRC_URI = 
"https://alioth.debian.org/frs/download.php/file/3979/chrpath-0.16.tar.gz \
+SRC_URI = 
"https://src.fedoraproject.org/lookaside/extras/chrpath/chrpath-0.16.tar.gz/2bf8d1d1ee345fc8a7915576f5649982/chrpath-0.16.tar.gz
 \
file://standarddoc.patch"
 
 SRC_URI[md5sum] = "2bf8d1d1ee345fc8a7915576f5649982"
-- 
2.17.0

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

[OE-core] [meta-oe][PATCH 2/2] iso-codes: fix SRC_URI

[Oleksandr Kravchuk]

Signed-off-by: Oleksandr Kravchuk 
---
 meta/recipes-support/iso-codes/iso-codes_3.77.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-support/iso-codes/iso-codes_3.77.bb 
b/meta/recipes-support/iso-codes/iso-codes_3.77.bb
index bd613ac573..d899a7fa82 100644
--- a/meta/recipes-support/iso-codes/iso-codes_3.77.bb
+++ b/meta/recipes-support/iso-codes/iso-codes_3.77.bb
@@ -3,6 +3,7 @@ LICENSE = "LGPLv2.1"
 LIC_FILES_CHKSUM = "file://COPYING;md5=4fbd65380cdd255951079008b364516c"
 
 SRC_URI = 
"https://pkg-isocodes.alioth.debian.org/downloads/iso-codes-${PV}.tar.xz;
+SRC_URI = 
"https://ftp.osuosl.org/pub/blfs/conglomeration/iso-codes/iso-codes-${PV}.tar.xz;
 SRC_URI[md5sum] = "9d0d06cfb4634428b300845edcd7140a"
 SRC_URI[sha256sum] = 
"21cd73a4c6f95d9474ebfcffd4e065223857720f24858e564f4409b19f7f0d90"
 
-- 
2.17.0

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

Re: [OE-core] [PATCH v2 5/7] toolchain-shar-extract: pass env to post-relocate

[Joshua Watt]

On Fri, 2018-06-01 at 14:02 -0700, Martin Kelly wrote:
> It's useful for the post-relocate scripts to be able to see the SDK
> environment, for example to see the values of CC, CXX etc. in order
> to
> dynamically generate toolchain files.
> 
> To enable this, source the SDK environment script prior to calling
> the
> relocate scripts.
> 
> Signed-off-by: Martin Kelly 
> ---
>  meta/classes/toolchain-scripts.bbclass | 17 +
>  meta/recipes-core/meta/meta-environment.bb |  5 +++--
>  2 files changed, 16 insertions(+), 6 deletions(-)
> 
> diff --git a/meta/classes/toolchain-scripts.bbclass
> b/meta/classes/toolchain-scripts.bbclass
> index ae7bbef034..5f99fd8c03 100644
> --- a/meta/classes/toolchain-scripts.bbclass
> +++ b/meta/classes/toolchain-scripts.bbclass
> @@ -118,11 +118,20 @@ EOF
>  }
>  
>  toolchain_create_post_relocate_script() {
> - script=$1
> - rm -f $script
> - touch $script
> + relocate_script=$1
> + sdk_script=$2
> + rm -f $relocate_script
> + touch $relocate_script
> +
> +cat >> $relocate_script < +# Source the SDK env script in case it is needed for the relocate
> scripts.
> +. $sdk_script

I had originally done something similar to this when I added support
for the post-relocate scripts with icecream. However, it is insufficent
because there can be multiple SDK environment scripts that need to be
sourced. In order to get a fully correct environment, I had to do:

 # Setup environment
 for env_setup_script in `ls $1/environment-setup-*`; do
. $env_setup_script
 done

see meta/recipes-devtools/icecc-toolchain/icecc-toolchain/icecc-
setup.sh


> +status=\$?
> +if [ \$status != 0 ]; then
> +echo "\$0: Failed to source $sdk_script with status \$status"
> +exit \$status
> +fi
>  
> -cat >> $script <  if [ -d "${SDKPATHNATIVE}/post-relocate-setup.d/" ]; then
>  for s in ${SDKPATHNATIVE}/post-relocate-setup.d/*; do
>  \$s "\$1"
> diff --git a/meta/recipes-core/meta/meta-environment.bb
> b/meta/recipes-core/meta/meta-environment.bb
> index 09f757a087..74c0600c3d 100644
> --- a/meta/recipes-core/meta/meta-environment.bb
> +++ b/meta/recipes-core/meta/meta-environment.bb
> @@ -51,12 +51,13 @@ create_sdk_files() {
>   # Setup site file for external use
>   toolchain_create_sdk_siteconfig
> ${SDK_OUTPUT}/${SDKPATH}/site-config-${REAL_MULTIMACH_TARGET_SYS}
>  
> - toolchain_create_sdk_env_script
> ${SDK_OUTPUT}/${SDKPATH}/environment-setup-
> ${REAL_MULTIMACH_TARGET_SYS}
> + sdk_script="${SDKPATH}/environment-setup-
> ${REAL_MULTIMACH_TARGET_SYS}"
> + toolchain_create_sdk_env_script ${SDK_OUTPUT}/${sdk_script}
>  
>   # Add version information
>   toolchain_create_sdk_version
> ${SDK_OUTPUT}/${SDKPATH}/version-${REAL_MULTIMACH_TARGET_SYS}
>  
> - toolchain_create_post_relocate_script
> ${SDK_OUTPUT}/${SDKPATH}/post-relocate-setup.sh
> + toolchain_create_post_relocate_script
> ${SDK_OUTPUT}/${SDKPATH}/post-relocate-setup.sh ${sdk_script}
>  }
>  
>  do_install() {
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH v2 4/7] toolchain-shar-extract: print post-relocate error

[Martin Kelly]

On 06/01/2018 02:57 PM, Joshua Watt wrote:

On Fri, 2018-06-01 at 14:02 -0700, Martin Kelly wrote:

Currently, if a post-relocate script fails, it fails silently. We
should
be louder about this, as it likely indicates a broken SDK.

Print a message if a post-relocate script fails.

Signed-off-by: Martin Kelly 
---
  meta/classes/toolchain-scripts.bbclass | 5 +
  1 file changed, 5 insertions(+)

diff --git a/meta/classes/toolchain-scripts.bbclass
b/meta/classes/toolchain-scripts.bbclass
index cbba07838a..ae7bbef034 100644
--- a/meta/classes/toolchain-scripts.bbclass
+++ b/meta/classes/toolchain-scripts.bbclass
@@ -126,6 +126,11 @@ toolchain_create_post_relocate_script() {
  if [ -d "${SDKPATHNATIVE}/post-relocate-setup.d/" ]; then
  for s in ${SDKPATHNATIVE}/post-relocate-setup.d/*; do


Perhaps worth adding:

  [ -x \$s ] || continue

?



Yes, good idea. I will add it in the next revision, after I wait a day 
or two more for other reviews.



  \$s "\$1"
+status=\$?
+if [ \$status != 0 ]; then
+echo "post-relocate command \"\$s \$1\" failed with
status \$status" >&2
+exit \$status
+fi
  done
  rm -rf "${SDKPATHNATIVE}/post-relocate-setup.d"
  fi

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

Re: [OE-core] [PATCH v2 4/7] toolchain-shar-extract: print post-relocate error

[Joshua Watt]

On Fri, 2018-06-01 at 14:02 -0700, Martin Kelly wrote:
> Currently, if a post-relocate script fails, it fails silently. We
> should
> be louder about this, as it likely indicates a broken SDK.
> 
> Print a message if a post-relocate script fails.
> 
> Signed-off-by: Martin Kelly 
> ---
>  meta/classes/toolchain-scripts.bbclass | 5 +
>  1 file changed, 5 insertions(+)
> 
> diff --git a/meta/classes/toolchain-scripts.bbclass
> b/meta/classes/toolchain-scripts.bbclass
> index cbba07838a..ae7bbef034 100644
> --- a/meta/classes/toolchain-scripts.bbclass
> +++ b/meta/classes/toolchain-scripts.bbclass
> @@ -126,6 +126,11 @@ toolchain_create_post_relocate_script() {
>  if [ -d "${SDKPATHNATIVE}/post-relocate-setup.d/" ]; then
>  for s in ${SDKPATHNATIVE}/post-relocate-setup.d/*; do

Perhaps worth adding:

 [ -x \$s ] || continue

?

>  \$s "\$1"
> +status=\$?
> +if [ \$status != 0 ]; then
> +echo "post-relocate command \"\$s \$1\" failed with
> status \$status" >&2
> +exit \$status
> +fi
>  done
>  rm -rf "${SDKPATHNATIVE}/post-relocate-setup.d"
>  fi
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH v2 6/7] meson: handle exe wrappers

[Martin Kelly]

Add patches to enable meson to handle being wrapped with a shell script.  This
will enable us to do so for supporting the SDK, which requires us to setup env
vars and point to a meson.cross file inside the SDK.

These patches are all merged upstream, so we can drop them soon.

Signed-off-by: Martin Kelly 
---
v2:
- Switch to new version of patches to fix exe wrappers, as upstream tweaked the
  previous patch.

 ...0004-Prettifying-some-output-with-pathlib.patch | 188 +
 ...on-command-to-use-when-we-know-what-it-is.patch | 851 +
 meta/recipes-devtools/meson/meson_0.46.1.bb|   2 +
 3 files changed, 1041 insertions(+)
 create mode 100644 
meta/recipes-devtools/meson/meson/0004-Prettifying-some-output-with-pathlib.patch
 create mode 100644 
meta/recipes-devtools/meson/meson/0005-Set-the-meson-command-to-use-when-we-know-what-it-is.patch

diff --git 
a/meta/recipes-devtools/meson/meson/0004-Prettifying-some-output-with-pathlib.patch
 
b/meta/recipes-devtools/meson/meson/0004-Prettifying-some-output-with-pathlib.patch
new file mode 100644
index 00..e75633beb9
--- /dev/null
+++ 
b/meta/recipes-devtools/meson/meson/0004-Prettifying-some-output-with-pathlib.patch
@@ -0,0 +1,188 @@
+From 253ab5bf6d6d925abcf625b72f5fcacf99be13bd Mon Sep 17 00:00:00 2001
+From: Niklas Claesson 
+Date: Wed, 18 Apr 2018 15:25:03 +0200
+Subject: [PATCH] Prettifying some output with pathlib
+
+This is a backport required in order to make
+0005-Set-the-meson-command-to-use-when-we-know-what-it-is.patch apply.
+
+Upstream-Status: Accepted [https://github.com/mesonbuild/meson/pull/3423]
+Should be in the 0.47.0 release.
+
+Signed-off-by: Martin Kelly 
+---
+ run_cross_test.py|  6 --
+ run_project_tests.py | 51 +--
+ 2 files changed, 33 insertions(+), 24 deletions(-)
+
+diff --git a/run_cross_test.py b/run_cross_test.py
+index e285e218..71914028 100755
+--- a/run_cross_test.py
 b/run_cross_test.py
+@@ -22,13 +22,15 @@ Not part of the main test suite because of two reasons:
+ 
+ Eventually migrate to something fancier.'''
+ 
+-import sys, os
++import sys
++import os
++from pathlib import Path
+ 
+ from run_project_tests import gather_tests, run_tests, StopException, 
setup_commands
+ from run_project_tests import failing_logs
+ 
+ def runtests(cross_file):
+-commontests = [('common', gather_tests('test cases/common'), False)]
++commontests = [('common', gather_tests(Path('test cases', 'common')), 
False)]
+ try:
+ (passing_tests, failing_tests, skipped_tests) = 
run_tests(commontests, 'meson-cross-test-run', ['--cross', cross_file])
+ except StopException:
+diff --git a/run_project_tests.py b/run_project_tests.py
+index 8c02a9ee..3c516240 100755
+--- a/run_project_tests.py
 b/run_project_tests.py
+@@ -14,14 +14,22 @@
+ # See the License for the specific language governing permissions and
+ # limitations under the License.
+ 
+-from glob import glob
+ import itertools
+-import os, subprocess, shutil, sys, signal
++import os
++import subprocess
++import shutil
++import sys
++import signal
+ from io import StringIO
+ from ast import literal_eval
+ from enum import Enum
+ import tempfile
+-from mesonbuild import build, environment, mesonlib, mlog, mtest
++from pathlib import Path, PurePath
++from mesonbuild import build
++from mesonbuild import environment
++from mesonbuild import mesonlib
++from mesonbuild import mlog
++from mesonbuild import mtest
+ from mesonbuild.mesonlib import stringlistify, Popen_safe
+ from mesonbuild.coredata import backendlist
+ import argparse
+@@ -198,7 +206,7 @@ def validate_install(srcdir, installdir, compiler, env):
+ 
+ def log_text_file(logfile, testdir, stdo, stde):
+ global stop, executor, futures
+-logfile.write('%s\nstdout\n\n---\n' % testdir)
++logfile.write('%s\nstdout\n\n---\n' % testdir.as_posix())
+ logfile.write(stdo)
+ logfile.write('\n\n---\n\nstderr\n\n---\n')
+ logfile.write(stde)
+@@ -245,11 +253,11 @@ def run_test_inprocess(testdir):
+ sys.stderr = mystderr = StringIO()
+ old_cwd = os.getcwd()
+ os.chdir(testdir)
+-test_log_fname = 'meson-logs/testlog.txt'
++test_log_fname = Path('meson-logs', 'testlog.txt')
+ try:
+ returncode_test = mtest.run(['--no-rebuild'])
+-if os.path.exists(test_log_fname):
+-test_log = open(test_log_fname, errors='ignore').read()
++if test_log_fname.exists():
++test_log = test_log_fname.open(errors='ignore').read()
+ else:
+ test_log = ''
+ returncode_benchmark = mtest.run(['--no-rebuild', '--benchmark', 
'--logbase', 'benchmarklog'])
+@@ -318,9 +326,8 @@ def _run_test(testdir, test_build_dir, install_dir, 
extra_args, compiler, backen
+ gen_args += [testdir, test_build_dir] + flags + test_args + extra_args
+ (returncode, stdo, stde) = run_configure(meson_command, gen_args)
+ try:
+-logfile = 

[OE-core] [PATCH v2 7/7] meson: enable nativesdk

[Martin Kelly]

Currently, we can't build meson into SDKs because we don't autogenerate
the required meson.cross file.

Enable this by using the post-relocate hooks and generating a
meson.cross file based on the SDK environment passed into the
post-relocate hook.

Signed-off-by: Martin Kelly 
---
 meta/recipes-devtools/meson/meson.inc  | 22 +++
 meta/recipes-devtools/meson/meson/meson-setup.py   | 62 ++
 meta/recipes-devtools/meson/meson/meson-wrapper| 14 
 meta/recipes-devtools/meson/meson_0.46.1.bb| 22 +--
 .../meson/nativesdk-meson_0.46.1.bb| 74 ++
 5 files changed, 173 insertions(+), 21 deletions(-)
 create mode 100644 meta/recipes-devtools/meson/meson.inc
 create mode 100755 meta/recipes-devtools/meson/meson/meson-setup.py
 create mode 100755 meta/recipes-devtools/meson/meson/meson-wrapper
 create mode 100644 meta/recipes-devtools/meson/nativesdk-meson_0.46.1.bb

diff --git a/meta/recipes-devtools/meson/meson.inc 
b/meta/recipes-devtools/meson/meson.inc
new file mode 100644
index 00..4c113dcaf7
--- /dev/null
+++ b/meta/recipes-devtools/meson/meson.inc
@@ -0,0 +1,22 @@
+HOMEPAGE = "http://mesonbuild.com;
+SUMMARY = "A high performance build system"
+
+LICENSE = "Apache-2.0"
+LIC_FILES_CHKSUM = "file://COPYING;md5=3b83ef96387f14655fc854ddc3c6bd57"
+
+SRC_URI = 
"https://github.com/mesonbuild/meson/releases/download/${PV}/meson-${PV}.tar.gz 
\
+   file://0001-gtkdoc-fix-issues-that-arise-when-cross-compiling.patch 
\
+   
file://0002-gobject-introspection-determine-g-ir-scanner-and-g-i.patch \
+   
file://0001-Linker-rules-move-cross_args-in-front-of-output_args.patch \
+   file://0003-native_bindir.patch \
+   file://0004-Prettifying-some-output-with-pathlib.patch \
+   
file://0005-Set-the-meson-command-to-use-when-we-know-what-it-is.patch \
+   "
+
+SRC_URI[md5sum] = "1698f6526574839de5dcdc45e3f7d582"
+SRC_URI[sha256sum] = 
"19497a03e7e5b303d8d11f98789a79aba59b5ad4a81bd00f4d099be0212cee78"
+UPSTREAM_CHECK_URI = "https://github.com/mesonbuild/meson/releases;
+
+inherit setuptools3
+
+RDEPENDS_${PN} = "ninja python3-core python3-modules"
diff --git a/meta/recipes-devtools/meson/meson/meson-setup.py 
b/meta/recipes-devtools/meson/meson/meson-setup.py
new file mode 100755
index 00..a9749eae9d
--- /dev/null
+++ b/meta/recipes-devtools/meson/meson/meson-setup.py
@@ -0,0 +1,62 @@
+#!/usr/bin/env python3
+
+import os
+import sys
+
+def bail(msg):
+print(msg, file=sys.stderr)
+sys.exit(1)
+
+_MARKER = '@@'
+def transform_line(line):
+# Substitute any special markers of this form:
+# @@ENV@@
+# with the value of ENV, split into meson array syntax.
+start = line.find(_MARKER)
+if start == -1:
+return line
+
+end = line.rfind(_MARKER)
+if end == start:
+return line
+
+# Lookup value of the env var.
+var = line[start+len(_MARKER):end]
+try:
+val = os.environ[var]
+except KeyError:
+bail('cannot generate meson.cross; env var %s not set' % var)
+
+# Transform into meson array.
+val = ["'%s'" % x for x in val.split()]
+val = ', '.join(val)
+val = '[%s]' % val
+
+before = line[:start]
+after = line[end+len(_MARKER):]
+
+return '%s%s%s' % (before, val, after)
+
+# Make sure this is really an SDK extraction environment.
+try:
+sysroot = os.environ['OECORE_NATIVE_SYSROOT']
+except KeyError:
+bail('OECORE_NATIVE_SYSROOT env var must be set')
+
+cross_file = os.path.join(sysroot, 'usr/share/meson/meson.cross')
+tmp_cross_file = '%s.tmp' % cross_file
+
+# Read through and transform the current meson.cross.
+lines = []
+with open(cross_file, 'r') as f:
+for line in f:
+lines.append(transform_line(line))
+
+# Write the transformed result to a tmp file and atomically rename it. In case
+# we crash during the file write, we don't want an invalid meson.cross file.
+with open(tmp_cross_file, 'w') as f:
+for line in lines:
+f.write(line)
+f.flush()
+os.fdatasync(f.fileno())
+os.rename(tmp_cross_file, cross_file)
diff --git a/meta/recipes-devtools/meson/meson/meson-wrapper 
b/meta/recipes-devtools/meson/meson/meson-wrapper
new file mode 100755
index 00..b2e00da513
--- /dev/null
+++ b/meta/recipes-devtools/meson/meson/meson-wrapper
@@ -0,0 +1,14 @@
+#!/bin/sh
+
+if [ -z "$OECORE_NATIVE_SYSROOT" ]; then
+echo "OECORE_NATIVE_SYSROOT not set; are you in a Yocto SDK environment?" 
>&2
+fi
+
+# If these are set to a cross-compile path, meson will get confused and try to
+# use them as native tools. Unset them to prevent this, as all the 
cross-compile
+# config is already in meson.cross.
+unset CC CXX CPP LD AR NM STRIP
+
+exec "$OECORE_NATIVE_SYSROOT/usr/bin/meson.real" \
+ --cross-file "$OECORE_NATIVE_SYSROOT/usr/share/meson/meson.cross" \
+ "$@"
diff --git a/meta/recipes-devtools/meson/meson_0.46.1.bb 

[OE-core] [PATCH v2 5/7] toolchain-shar-extract: pass env to post-relocate

[Martin Kelly]

It's useful for the post-relocate scripts to be able to see the SDK
environment, for example to see the values of CC, CXX etc. in order to
dynamically generate toolchain files.

To enable this, source the SDK environment script prior to calling the
relocate scripts.

Signed-off-by: Martin Kelly 
---
 meta/classes/toolchain-scripts.bbclass | 17 +
 meta/recipes-core/meta/meta-environment.bb |  5 +++--
 2 files changed, 16 insertions(+), 6 deletions(-)

diff --git a/meta/classes/toolchain-scripts.bbclass 
b/meta/classes/toolchain-scripts.bbclass
index ae7bbef034..5f99fd8c03 100644
--- a/meta/classes/toolchain-scripts.bbclass
+++ b/meta/classes/toolchain-scripts.bbclass
@@ -118,11 +118,20 @@ EOF
 }
 
 toolchain_create_post_relocate_script() {
-   script=$1
-   rm -f $script
-   touch $script
+   relocate_script=$1
+   sdk_script=$2
+   rm -f $relocate_script
+   touch $relocate_script
+
+cat >> $relocate_script <> $script 

[OE-core] [PATCH v2 3/7] toolchain-shar-extract: allow non-sh post-relocate

[Martin Kelly]

Currently, we look only for scripts matching *.sh, which means we can't
write post-relocate scripts in other languages.

Expand this to allow any type of script.

Signed-off-by: Martin Kelly 
---
 meta/classes/toolchain-scripts.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/toolchain-scripts.bbclass 
b/meta/classes/toolchain-scripts.bbclass
index 71da5e5409..cbba07838a 100644
--- a/meta/classes/toolchain-scripts.bbclass
+++ b/meta/classes/toolchain-scripts.bbclass
@@ -124,7 +124,7 @@ toolchain_create_post_relocate_script() {
 
 cat >> $script 

[OE-core] [PATCH v2 4/7] toolchain-shar-extract: print post-relocate error

[Martin Kelly]

Currently, if a post-relocate script fails, it fails silently. We should
be louder about this, as it likely indicates a broken SDK.

Print a message if a post-relocate script fails.

Signed-off-by: Martin Kelly 
---
 meta/classes/toolchain-scripts.bbclass | 5 +
 1 file changed, 5 insertions(+)

diff --git a/meta/classes/toolchain-scripts.bbclass 
b/meta/classes/toolchain-scripts.bbclass
index cbba07838a..ae7bbef034 100644
--- a/meta/classes/toolchain-scripts.bbclass
+++ b/meta/classes/toolchain-scripts.bbclass
@@ -126,6 +126,11 @@ toolchain_create_post_relocate_script() {
 if [ -d "${SDKPATHNATIVE}/post-relocate-setup.d/" ]; then
 for s in ${SDKPATHNATIVE}/post-relocate-setup.d/*; do
 \$s "\$1"
+status=\$?
+if [ \$status != 0 ]; then
+echo "post-relocate command \"\$s \$1\" failed with status 
\$status" >&2
+exit \$status
+fi
 done
 rm -rf "${SDKPATHNATIVE}/post-relocate-setup.d"
 fi
-- 
2.11.0

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

[OE-core] [PATCH v2 1/7] meson.bbclass: refactor native override

[Martin Kelly]

The native override is specified in two different places, so let's move
it into a function to reduce code duplication.

Signed-off-by: Martin Kelly 
---
 meta/classes/meson.bbclass | 17 +++--
 1 file changed, 7 insertions(+), 10 deletions(-)

diff --git a/meta/classes/meson.bbclass b/meta/classes/meson.bbclass
index 2d7ee4fffc..5881765abb 100644
--- a/meta/classes/meson.bbclass
+++ b/meta/classes/meson.bbclass
@@ -90,7 +90,7 @@ meson_do_configure() {
 fi
 }
 
-meson_do_configure_prepend_class-target() {
+override_native_tools() {
 # Set these so that meson uses the native tools for its build sanity tests,
 # which require executables to be runnable. The cross file will still
 # override these for the target build. Note that we do *not* set CFLAGS,
@@ -100,18 +100,15 @@ meson_do_configure_prepend_class-target() {
 export CXX="${BUILD_CXX}"
 export LD="${BUILD_LD}"
 export AR="${BUILD_AR}"
+
+}
+
+meson_do_configure_prepend_class-target() {
+override_native_tools
 }
 
 meson_do_configure_prepend_class-nativesdk() {
-# Set these so that meson uses the native tools for its build sanity tests,
-# which require executables to be runnable. The cross file will still
-# override these for the nativesdk build. Note that we do *not* set CFLAGS,
-# LDFLAGS, etc. as they will be slurped in by meson and applied to the
-# nativesdk build, causing errors.
-export CC="${BUILD_CC}"
-export CXX="${BUILD_CXX}"
-export LD="${BUILD_LD}"
-export AR="${BUILD_AR}"
+override_native_tools
 }
 
 meson_do_configure_prepend_class-native() {
-- 
2.11.0

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

[OE-core] [PATCH v2 2/7] nativesdk-python*: suppress user site dirs

[Martin Kelly]

Currently, $HOME/.local is being added into sys.path in the Python SDK
causing subtle host contamination. Suppress this by exporting
PYTHONNOUSERSITE = "1" as documented in PEP 370.

This issue occurred in the past for python*-native and was fixed
similarly in OE-core commit 8fe9fb4d5a61dcbcb3fc5b9ee0234cc135af873f
("python*native.bbclass: suppress user site dirs").

Signed-off-by: Martin Kelly 
---
 meta/recipes-devtools/python/python-scons-native_3.0.1.bb | 2 +-
 meta/recipes-devtools/python/python3_3.5.5.bb | 2 +-
 meta/recipes-devtools/python/python_2.7.14.bb | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-devtools/python/python-scons-native_3.0.1.bb 
b/meta/recipes-devtools/python/python-scons-native_3.0.1.bb
index dae89ab5d2..68b63c9357 100644
--- a/meta/recipes-devtools/python/python-scons-native_3.0.1.bb
+++ b/meta/recipes-devtools/python/python-scons-native_3.0.1.bb
@@ -4,5 +4,5 @@ DEPENDS = "python-native"
 RDEPENDS_${PN} = ""
 
 do_install_append() {
-create_wrapper ${D}${bindir}/scons 
SCONS_LIB_DIR='${STAGING_DIR_HOST}/${PYTHON_SITEPACKAGES_DIR}'
+create_wrapper ${D}${bindir}/scons 
SCONS_LIB_DIR='${STAGING_DIR_HOST}/${PYTHON_SITEPACKAGES_DIR}' 
PYTHONNOUSERSITE='1'
 }
diff --git a/meta/recipes-devtools/python/python3_3.5.5.bb 
b/meta/recipes-devtools/python/python3_3.5.5.bb
index f893b846ad..4dae4fa4c6 100644
--- a/meta/recipes-devtools/python/python3_3.5.5.bb
+++ b/meta/recipes-devtools/python/python3_3.5.5.bb
@@ -176,7 +176,7 @@ do_install() {
 }
 
 do_install_append_class-nativesdk () {
-   create_wrapper ${D}${bindir}/python${PYTHON_MAJMIN} 
TERMINFO_DIRS='${sysconfdir}/terminfo:/etc/terminfo:/usr/share/terminfo:/usr/share/misc/terminfo:/lib/terminfo'
+   create_wrapper ${D}${bindir}/python${PYTHON_MAJMIN} 
TERMINFO_DIRS='${sysconfdir}/terminfo:/etc/terminfo:/usr/share/terminfo:/usr/share/misc/terminfo:/lib/terminfo'
 PYTHONNOUSERSITE='1'
 }
 
 SSTATE_SCAN_FILES += "Makefile"
diff --git a/meta/recipes-devtools/python/python_2.7.14.bb 
b/meta/recipes-devtools/python/python_2.7.14.bb
index 41a8609b15..b923b9237b 100644
--- a/meta/recipes-devtools/python/python_2.7.14.bb
+++ b/meta/recipes-devtools/python/python_2.7.14.bb
@@ -130,7 +130,7 @@ do_install() {
 }
 
 do_install_append_class-nativesdk () {
-   create_wrapper ${D}${bindir}/python2.7 PYTHONHOME='${prefix}' 
TERMINFO_DIRS='${sysconfdir}/terminfo:/etc/terminfo:/usr/share/terminfo:/usr/share/misc/terminfo:/lib/terminfo'
+   create_wrapper ${D}${bindir}/python2.7 PYTHONHOME='${prefix}' 
TERMINFO_DIRS='${sysconfdir}/terminfo:/etc/terminfo:/usr/share/terminfo:/usr/share/misc/terminfo:/lib/terminfo'
 PYTHONNOUSERSITE='1'
 }
 
 SSTATE_SCAN_FILES += "Makefile"
-- 
2.11.0

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

[OE-core] [PATCH v2 0/7] meson: implement nativesdk support

[Martin Kelly]

This patch series implements nativesdk support fer meson. In order to do so, it
adds a few features to the toolchain-shar-extract functionality, which enables a
script to run prior to the SDK being extracted. This is important because the
meson.cross file (which meson uses to find its cross toolchain) allows for only
absolute paths. Thus, it is important to customize those paths to point to the
SDK at SDK extraction time. For comparison, cmake did not need this
functionality because it supports referencing environment variables in the
toolchain file, so we can just reference the SDK root environment variables. The
meson maintainers did not want to take that approach, so this seemed like the
best option.

If curious, see the following threads for more background information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-January/146210.html
http://lists.openembedded.org/pipermail/openembedded-core/2018-January/146225.html
http://lists.openembedded.org/pipermail/openembedded-core/2018-January/146236.html
http://lists.openembedded.org/pipermail/openembedded-core/2018-January/146241.html
http://lists.openembedded.org/pipermail/openembedded-core/2018-January/146261.html
http://lists.openembedded.org/pipermail/openembedded-core/2018-January/146262.html

v2:
- Switch to new version of patches to fix exe wrappers, as upstream tweaked the
  previous patch.

Martin Kelly (7):
  meson.bbclass: refactor native override
  nativesdk-python*: suppress user site dirs
  toolchain-shar-extract: allow non-sh post-relocate
  toolchain-shar-extract: print post-relocate error
  toolchain-shar-extract: pass env to post-relocate
  meson: handle exe wrappers
  meson: enable nativesdk

 meta/classes/meson.bbclass |  17 +-
 meta/classes/toolchain-scripts.bbclass |  24 +-
 meta/recipes-core/meta/meta-environment.bb |   5 +-
 meta/recipes-devtools/meson/meson.inc  |  22 +
 ...0004-Prettifying-some-output-with-pathlib.patch | 188 +
 ...on-command-to-use-when-we-know-what-it-is.patch | 851 +
 meta/recipes-devtools/meson/meson/meson-setup.py   |  62 ++
 meta/recipes-devtools/meson/meson/meson-wrapper|  14 +
 meta/recipes-devtools/meson/meson_0.46.1.bb|  20 +-
 .../meson/nativesdk-meson_0.46.1.bb|  74 ++
 .../python/python-scons-native_3.0.1.bb|   2 +-
 meta/recipes-devtools/python/python3_3.5.5.bb  |   2 +-
 meta/recipes-devtools/python/python_2.7.14.bb  |   2 +-
 13 files changed, 1244 insertions(+), 39 deletions(-)
 create mode 100644 meta/recipes-devtools/meson/meson.inc
 create mode 100644 
meta/recipes-devtools/meson/meson/0004-Prettifying-some-output-with-pathlib.patch
 create mode 100644 
meta/recipes-devtools/meson/meson/0005-Set-the-meson-command-to-use-when-we-know-what-it-is.patch
 create mode 100755 meta/recipes-devtools/meson/meson/meson-setup.py
 create mode 100755 meta/recipes-devtools/meson/meson/meson-wrapper
 create mode 100644 meta/recipes-devtools/meson/nativesdk-meson_0.46.1.bb

-- 
2.11.0

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

Re: [OE-core] [PATCH v2] ltp: bump to release 20180515

[Denys Dmytriyenko]

On Thu, May 31, 2018 at 11:10:11PM -0500, Daniel Díaz wrote:
> The following patches have made it to upstream:
> * 0001-configure-Fix-default-value-of-without-numa-switch-i.patch
> * 0001-configure-add-knob-to-control-numa-support.patch
> * 0003-Add-knob-to-control-tirpc-support.patch
> * 0010-replace-__BEGIN_DECLS-and-__END_DECLS.patch
> * 0040-safe_macros-make-is_fuse-return-zero-if-fs_type-is-N.patch
> 
> These patches have been refreshed in order to apply cleanly
> and without any fuzz:
> * 0004-build-Add-option-to-select-libc-implementation.patch
> * 0008-Check-if-__GLIBC_PREREQ-is-defined-before-using-it.patch
> * 0021-Define-_GNU_SOURCE-for-MREMAP_MAYMOVE-definition.patch
> * 0028-rt_sigaction.h-Use-sighandler_t-instead-of-__sighand.patch
> * 0036-testcases-network-nfsv4-acl-acl1.c-Security-fix-on-s.patch
> 
> Signed-off-by: Daniel Díaz 
> ---
> v2: Actually change SRCREV, refresh/remove patches as needed.
> 
>  .../ltp/0001-Disable-rpc01-on-glibc-and-musl.patch |  29 -
>  ...ix-default-value-of-without-numa-switch-i.patch |  31 --
>  ...onfigure-add-knob-to-control-numa-support.patch |  50 -
>  .../0003-Add-knob-to-control-tirpc-support.patch   |  46 
>  ...-Add-option-to-select-libc-implementation.patch |  77 --
>  ...__GLIBC_PREREQ-is-defined-before-using-it.patch |  26 ++---
>  ...010-replace-__BEGIN_DECLS-and-__END_DECLS.patch |  75 -
>  ..._GNU_SOURCE-for-MREMAP_MAYMOVE-definition.patch |  27 ++---
>  ...n.h-Use-sighandler_t-instead-of-__sighand.patch |  20 ++--
>  ...etwork-nfsv4-acl-acl1.c-Security-fix-on-s.patch |   2 +-
>  ...-make-is_fuse-return-zero-if-fs_type-is-N.patch |  40 ---
>  meta/recipes-extended/ltp/ltp_20180118.bb  | 117 
> -
>  meta/recipes-extended/ltp/ltp_20180515.bb  | 111 +++

Can the recipe update itself be a diff as well, git --find-renames?


>  13 files changed, 197 insertions(+), 454 deletions(-)
>  delete mode 100644 
> meta/recipes-extended/ltp/ltp/0001-Disable-rpc01-on-glibc-and-musl.patch
>  delete mode 100644 
> meta/recipes-extended/ltp/ltp/0001-configure-Fix-default-value-of-without-numa-switch-i.patch
>  delete mode 100644 
> meta/recipes-extended/ltp/ltp/0001-configure-add-knob-to-control-numa-support.patch
>  delete mode 100644 
> meta/recipes-extended/ltp/ltp/0003-Add-knob-to-control-tirpc-support.patch
>  delete mode 100644 
> meta/recipes-extended/ltp/ltp/0010-replace-__BEGIN_DECLS-and-__END_DECLS.patch
>  delete mode 100644 
> meta/recipes-extended/ltp/ltp/0040-safe_macros-make-is_fuse-return-zero-if-fs_type-is-N.patch
>  delete mode 100644 meta/recipes-extended/ltp/ltp_20180118.bb
>  create mode 100644 meta/recipes-extended/ltp/ltp_20180515.bb
> 
> diff --git 
> a/meta/recipes-extended/ltp/ltp/0001-Disable-rpc01-on-glibc-and-musl.patch 
> b/meta/recipes-extended/ltp/ltp/0001-Disable-rpc01-on-glibc-and-musl.patch
> deleted file mode 100644
> index 78c6dfb..000
> --- a/meta/recipes-extended/ltp/ltp/0001-Disable-rpc01-on-glibc-and-musl.patch
> +++ /dev/null
> @@ -1,29 +0,0 @@
> -From ff39e6b69f0b26dad8ab685ee6116ff92bc363db Mon Sep 17 00:00:00 2001
> -From: Khem Raj 
> -Date: Sat, 28 Apr 2018 00:08:55 -0700
> -Subject: [PATCH] Disable rpc01 on glibc and musl
> -
> -It is not buildable with libtirpc
> -
> -Signed-off-by: Khem Raj 
> 
> -Upstream-Status: Pending
> -
> - testcases/network/rpc/basic_tests/Makefile | 3 +++
> - 1 file changed, 3 insertions(+)
> -
> -diff --git a/testcases/network/rpc/basic_tests/Makefile 
> b/testcases/network/rpc/basic_tests/Makefile
> -index 66e9d5675..16a64e7da 100644
>  a/testcases/network/rpc/basic_tests/Makefile
> -+++ b/testcases/network/rpc/basic_tests/Makefile
> -@@ -23,4 +23,7 @@
> - top_srcdir  ?= ../../../..
> - 
> - include $(top_srcdir)/include/mk/env_pre.mk
> -+
> -+FILTER_OUT_DIRS += rpc01
> -+
> - include $(top_srcdir)/include/mk/generic_trunk_target.mk
> --- 
> -2.17.0
> -
> diff --git 
> a/meta/recipes-extended/ltp/ltp/0001-configure-Fix-default-value-of-without-numa-switch-i.patch
>  
> b/meta/recipes-extended/ltp/ltp/0001-configure-Fix-default-value-of-without-numa-switch-i.patch
> deleted file mode 100644
> index da62687..000
> --- 
> a/meta/recipes-extended/ltp/ltp/0001-configure-Fix-default-value-of-without-numa-switch-i.patch
> +++ /dev/null
> @@ -1,31 +0,0 @@
> -From 4ace68a6ba501907a0741dba5f5f155e06a74c35 Mon Sep 17 00:00:00 2001
> -From: Petr Vorel 
> -Date: Wed, 7 Feb 2018 11:09:49 +0100
> -Subject: [PATCH] configure: Fix default value of --without-numa switch in 
> help
> -
> -The default value is no.
> -
> -Fixes: 39a85a1f1 ("configure: add knob to control numa support")
> -
> -Signed-off-by: Petr Vorel 
> -Upstream-Status: Accepted
> 
> - configure.ac | 2 +-
> - 1 file changed, 1 insertion(+), 1 deletion(-)
> -
> -diff --git a/configure.ac b/configure.ac
> -index b39a31d..d66ea00 100644
>  a/configure.ac
> -+++ b/configure.ac
> -@@ -86,7 +86,7 @@ fi
> - # Numa

Re: [OE-core] [PATCH] tune-i586-nlp.inc: drop tuning file for Intel Quark/X1000 CPU

[Mark Hatle]

On 6/1/18 12:21 PM, Andre McCurdy wrote:
> On Fri, Jun 1, 2018 at 7:58 AM, Mark Hatle  wrote:
>> On 5/31/18 6:10 PM, Andre McCurdy wrote:
>>> The Quark machine was EOL'ed at the end of 2017 and all support for
>>> it has now been removed from meta-intel. Drop the associated tuning
>>> file from oe-core.
>>
>> I would rather this remain.  There are still a lot of people using the quark
>> based boards as hobbyists... there is little effort to maintain it for now.
>>
>> (we still have support for ARMv4 for instance, which hasn't really been used 
>> in
>> new designs in a while..)
> 
> Is there ever a case when we would drop old tuning files? Or should
> they live on forever?

If we actively know they do not work any longer, (which is probably when GCC
support is declared to be obsolete.)

> We dropped GPLv2 recipes from oe-core on the grounds that they are
> old, unmaintained and untested. ARMv4 CPU tuning files meet those
> criteria too.

I'm not sure they are unmaintained, but certainly untested.  We've had and
continue to get contributions to tuning files that are clearly never tested.

(Besides, a lot of us don't use meta-intel, we use our own BSP layers..)

--Mark

>>>   
>>> http://git.yoctoproject.org/cgit.cgi/meta-intel/commit/?id=5dbc69e339588834317b632119717996584b0d6c
>>>
>>> Signed-off-by: Andre McCurdy 
>>> ---
>>>  meta/conf/machine/include/tune-i586-nlp.inc | 19 ---
>>>  1 file changed, 19 deletions(-)
>>>  delete mode 100644 meta/conf/machine/include/tune-i586-nlp.inc
>>>
>>> diff --git a/meta/conf/machine/include/tune-i586-nlp.inc 
>>> b/meta/conf/machine/include/tune-i586-nlp.inc
>>> deleted file mode 100644
>>> index 88e5903..000
>>> --- a/meta/conf/machine/include/tune-i586-nlp.inc
>>> +++ /dev/null
>>> @@ -1,19 +0,0 @@
>>> -# Settings for the GCC(1) cpu-type "quark":
>>> -#
>>> -#
>>> -#
>>> -DEFAULTTUNE ?= "i586-nlp-32"
>>> -
>>> -# Include the previous tune to pull in PACKAGE_EXTRA_ARCHS
>>> -require conf/machine/include/x86/arch-x86.inc
>>> -
>>> -# x86 with no lock prefix
>>> -TUNEVALID[i586-nlp] = "IA32 with Lock Prefix omitted"
>>> -TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'i586-nlp', ' 
>>> -march=i586 -Wa,-momit-lock-prefix=yes', '', d)}"
>>> -
>>> -# Quark tune feature
>>> -AVAILTUNES = "i586-nlp-32"
>>> -TUNE_FEATURES_tune-i586-nlp-32 = "${TUNE_FEATURES_tune-x86} i586-nlp"
>>> -BASE_LIB_tune-i586-nlp-32 = "lib"
>>> -TUNE_PKGARCH_tune-i586-nlp-32 = "i586-nlp-32"
>>> -PACKAGE_EXTRA_ARCHS_tune-i586-nlp-32 = "i586-nlp-32"
>>>
>>

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

Re: [OE-core] [PATCH] boost: Improve reproducibility

[Alexander Kanavin]

On 06/01/2018 09:33 PM, Khem Raj wrote:

The .s file is not generated and it does not contain any .file
directives. The .o file also does not contain the path. It appears in
the final .so library at linking stage.


Can you share the linker cmdline ?


https://pastebin.com/WK9GVDfj

Note that of the three assembly-generated object files, only the path to 
the first shows up in the .so - because of assembly labels I believe.


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

[OE-core] [PATCH 3/3] tune-cortexa17: add tunes for ARM Cortex-A35

[ayaka]

https://developer.arm.com/products/processors/cortex-a/cortex-a35

Signe-off-by: ayaka 
---
 meta/conf/machine/include/tune-cortexa35.inc | 24 
 1 file changed, 24 insertions(+)
 create mode 100644 meta/conf/machine/include/tune-cortexa35.inc

diff --git a/meta/conf/machine/include/tune-cortexa35.inc 
b/meta/conf/machine/include/tune-cortexa35.inc
new file mode 100644
index 00..62570e0943
--- /dev/null
+++ b/meta/conf/machine/include/tune-cortexa35.inc
@@ -0,0 +1,24 @@
+DEFAULTTUNE ?= "armv8ahf-crypto"
+
+require conf/machine/include/arm/arch-armv8a.inc
+
+TUNEVALID[cortexa35] = "Enable Cortex-A35 specific processor optimizations"
+TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'cortexa35', ' 
-mcpu=cortex-a35', '', d)}"
+
+# Little Endian base configs
+AVAILTUNES += "cortexa35 cortexa35-crypto"
+ARMPKGARCH_tune-cortexa35 = "cortexa35"
+ARMPKGARCH_tune-cortexa35t-crypto = "cortexa35"
+TUNE_FEATURES_tune-cortexa35  = "${TUNE_FEATURES_tune-armv8a} 
cortexa35"
+TUNE_FEATURES_tune-cortexa35t-crypto  = "${TUNE_FEATURES_tune-armv8a-crypto} 
cortexa35"
+PACKAGE_EXTRA_ARCHS_tune-cortexa35 = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8a} cortexa35"
+PACKAGE_EXTRA_ARCHS_tune-cortexa35-crypto  = 
"${PACKAGE_EXTRA_ARCHS_tune-cortexa35} cortexa35-crypto"
+
+# HF Tunes
+AVAILTUNES += "cortexa35hf cortexa35hf-crypto"
+ARMPKGARCH_tune-cortexa35hf = "cortexa35"
+ARMPKGARCH_tune-cortexa35hf-crypto  = "cortexa35"
+TUNE_FEATURES_tune-cortexa35hf = "${TUNE_FEATURES_tune-armv8ahf} 
cortexa35"
+TUNE_FEATURES_tune-cortexa35hf-crypto  = 
"${TUNE_FEATURES_tune-armv8ahf-crypto} cortexa35"
+PACKAGE_EXTRA_ARCHS_tune-cortexa35hf = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8ahf} cortexa35hf"
+PACKAGE_EXTRA_ARCHS_tune-cortexa35hf-crypto  = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8ahf-crypto} cortexa35hf-crypto"
-- 
2.14.3

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

[OE-core] [PATCH 2/3] arch-armv8a.inc: add tune include for armv8

[ayaka]

There are some addtional instructions apart from bare armv8,
also there is armv8.1, armv8.2.

Signed-off-by: ayaka 
---
 meta/conf/machine/include/arm/arch-armv8.inc  |  1 -
 meta/conf/machine/include/arm/arch-armv8a.inc | 49 +++
 2 files changed, 49 insertions(+), 1 deletion(-)
 delete mode 100644 meta/conf/machine/include/arm/arch-armv8.inc
 create mode 100644 meta/conf/machine/include/arm/arch-armv8a.inc

diff --git a/meta/conf/machine/include/arm/arch-armv8.inc 
b/meta/conf/machine/include/arm/arch-armv8.inc
deleted file mode 100644
index 5e832fae6d..00
--- a/meta/conf/machine/include/arm/arch-armv8.inc
+++ /dev/null
@@ -1 +0,0 @@
-require conf/machine/include/arm/arch-arm64.inc
diff --git a/meta/conf/machine/include/arm/arch-armv8a.inc 
b/meta/conf/machine/include/arm/arch-armv8a.inc
new file mode 100644
index 00..43c2d456ab
--- /dev/null
+++ b/meta/conf/machine/include/arm/arch-armv8a.inc
@@ -0,0 +1,49 @@
+DEFAULTTUNE ?= "armv8ah"
+
+TUNEVALID[armv8] = "Enable instructions for ARMv8-a"
+TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'armv8a', ' 
-march=armv8-a', '', d)}"
+MACHINEOVERRIDES =. "${@bb.utils.contains('TUNE_FEATURES', 'armv8a', 
'armv8a:', '' ,d)}"
+
+require conf/machine/include/arm/arch-arm64.inc
+
+# Little Endian base configs
+AVAILTUNES += "armv8a armv8a-crc armv8a-simd armv8a-crypto armv8a-crc-simd 
armv8a-crc-simd-crypto"
+ARMPKGARCH_tune-armv8a?= "armv8a"
+ARMPKGARCH_tune-armv8a-crc?= "armv8a"
+ARMPKGARCH_tune-armv8a-simd   ?= "armv8a"
+ARMPKGARCH_tune-armv8a-crypto ?= "armv8a"
+ARMPKGARCH_tune-armv8a-crc-simd   ?= "armv8a"
+ARMPKGARCH_tune-armv8a-crc-simd-crypto?= "armv8a"
+TUNE_FEATURES_tune-armv8a = "armv8a"
+TUNE_FEATURES_tune-armv8a-crc = "${ARMPKGARCH_tune-armv8a} crc"
+TUNE_FEATURES_tune-armv8a-simd= "${ARMPKGARCH_tune-armv8a} simd"
+TUNE_FEATURES_tune-armv8a-crypto  = "${ARMPKGARCH_tune-armv8a} crypto"
+TUNE_FEATURES_tune-armv8a-crc-simd= "${TUNE_FEATURES_tune-armv8a-crc} 
simd"
+TUNE_FEATURES_tune-armv8a-crc-simd-crypto = 
"${TUNE_FEATURES_tune-armv8a-crc-simd} crypto"
+PACKAGE_EXTRA_ARCHS_tune-armv8a = "aarch64 armv8a"
+PACKAGE_EXTRA_ARCHS_tune-armv8a-crc = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8a} crc"
+PACKAGE_EXTRA_ARCHS_tune-armv8a-simd= 
"${PACKAGE_EXTRA_ARCHS_tune-armv8a} simd"
+PACKAGE_EXTRA_ARCHS_tune-armv8a-crypto  = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8a} crypto"
+PACKAGE_EXTRA_ARCHS_tune-armv8a-crc-simd= 
"${PACKAGE_EXTRA_ARCHS_tune-armv8a-crc} simd"
+PACKAGE_EXTRA_ARCHS_tune-armv8a-crc-simd-crypto = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8a-crc-simd} crypto"
+
+# HF Tunes
+AVAILTUNES += "armv8ahf armv8ahf-crc armv8ahf-simd armv8ahf-crypto 
armv8ahf-crc-simd armv8ahf-crc-simd-crypto"
+ARMPKGARCH_tune-armv8ahf?= "armv8a"
+ARMPKGARCH_tune-armv8ahf-crc?= "armv8a"
+ARMPKGARCH_tune-armv8ahf-simd   ?= "armv8a"
+ARMPKGARCH_tune-armv8ahf-crypto ?= "armv8a"
+ARMPKGARCH_tune-armv8ahf-crc-simd   ?= "armv8a"
+ARMPKGARCH_tune-armv8ahf-crc-simd-crypto?= "armv8a"
+TUNE_FEATURES_tune-armv8ahf = "${TUNE_FEATURES_tune-armv8a} 
callconvention-hard"
+TUNE_FEATURES_tune-armv8ahf-crc = 
"${TUNE_FEATURES_tune-armv8a-crc} callconvention-hard"
+TUNE_FEATURES_tune-armv8ahf-simd= 
"${TUNE_FEATURES_tune-armv8a-crc-simd} callconvention-hard"
+TUNE_FEATURES_tune-armv8ahf-crypto  = 
"${TUNE_FEATURES_tune-armv8a-crypto} callconvention-hard"
+TUNE_FEATURES_tune-armv8ahf-crc-simd= 
"${TUNE_FEATURES_tune-armv8a-crc-simd} callconvention-hard"
+TUNE_FEATURES_tune-armv8ahf-crc-simd-crypto = 
"${TUNE_FEATURES_tune-armv8a-crc-simd-crypto} callconvention-hard"
+PACKAGE_EXTRA_ARCHS_tune-armv8ahf = "armv8ahf"
+PACKAGE_EXTRA_ARCHS_tune-armv8ahf-crc = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8ahf} crc"
+PACKAGE_EXTRA_ARCHS_tune-armv8ahf-simd= 
"${PACKAGE_EXTRA_ARCHS_tune-armv8ahf} simd"
+PACKAGE_EXTRA_ARCHS_tune-armv8ahf-crypto  = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8ahf} crypto"
+PACKAGE_EXTRA_ARCHS_tune-armv8ahf-crc-simd= 
"${PACKAGE_EXTRA_ARCHS_tune-armv8ahf-crc} simd"
+PACKAGE_EXTRA_ARCHS_tune-armv8ahf-crc-simd-crypto = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8ahf-crc-simd} crypto"
-- 
2.14.3

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

[OE-core] [PATCH 0/3] Add tune for ARMv8 and cortex a35

[ayaka]

I saw there is a patch serial that try to add tuning for ARMv8 a year
ago, but at that time, there is not much tune opinions, even the NEON
FPU is not optional in all the cortex.

But when the A35 comes and gcc support more opinions on them, I think it
is necessary to add support those thing in armv8.

I have no idea how to support those big.little combo, there is too much
pattern, I would like to only create tuning file for echo cortex IPs first.

This patch is just sending for early check, whether it would be welcome.

ayaka (3):
  [WIP]: arch-arm64.inc: allow soft fpu configure
  arch-armv8a.inc: add tune include for armv8
  tune-cortexa17: add tunes for ARM Cortex-A35

 meta/conf/machine/include/arm/arch-arm64.inc  |  2 +-
 meta/conf/machine/include/arm/arch-armv8.inc  |  1 -
 meta/conf/machine/include/arm/arch-armv8a.inc | 49 +++
 meta/conf/machine/include/tune-cortexa35.inc  | 24 +
 4 files changed, 74 insertions(+), 2 deletions(-)
 delete mode 100644 meta/conf/machine/include/arm/arch-armv8.inc
 create mode 100644 meta/conf/machine/include/arm/arch-armv8a.inc
 create mode 100644 meta/conf/machine/include/tune-cortexa35.inc

-- 
2.14.3

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

[OE-core] [PATCH 1/3] [WIP]: arch-arm64.inc: allow soft fpu configure

[ayaka]

From ARM® Cortex®-A35 Processor Techinical Reference Manual,
the NEON is optional. I am not sure about the VFP part.

Signed-off-by: ayaka 
---
 meta/conf/machine/include/arm/arch-arm64.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/conf/machine/include/arm/arch-arm64.inc 
b/meta/conf/machine/include/arm/arch-arm64.inc
index 5f90763f7f..3707c61694 100644
--- a/meta/conf/machine/include/arm/arch-arm64.inc
+++ b/meta/conf/machine/include/arm/arch-arm64.inc
@@ -22,7 +22,7 @@ ARMPKGSFX_ENDIAN_64 = "${@bb.utils.contains('TUNE_FEATURES', 
'bigendian', '_be',
 TUNE_ARCH_64 = "aarch64${ARMPKGSFX_ENDIAN_64}"
 TUNE_PKGARCH_64 = "aarch64${ARMPKGSFX_ENDIAN_64}"
 ABIEXTENSION_64 = ""
-TARGET_FPU_64 = ""
+TARGET_FPU_64 = "${@d.getVar('TUNE_CCARGS_MFLOAT') or 'soft'}"
 
 # Duplicated from arch-arm.inc
 TUNE_ARCH_32 = "${@bb.utils.contains('TUNE_FEATURES', 'bigendian', 'armeb', 
'arm', d)}"
-- 
2.14.3

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

Re: [OE-core] [PATCH] boost: Improve reproducibility

[Khem Raj]

On 6/1/18 10:56 AM, Alexander Kanavin wrote:
> 2018-06-01 20:07 GMT+03:00 Khem Raj :
>> these symbols are added by assembler, if you have .file asm directive
>> either explicitly added to .s file or emitted by compiler, compiler
>> would emit it if the path specified to source file is absolute during
>> compiler invocation, it will take it verbatim and put it in generated .s
>> file
> 
> The .s file is not generated and it does not contain any .file
> directives. The .o file also does not contain the path. It appears in
> the final .so library at linking stage.

Can you share the linker cmdline ?

> 
> Alex
> 




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] boost: Improve reproducibility

[Alexander Kanavin]

2018-06-01 20:07 GMT+03:00 Khem Raj :
> these symbols are added by assembler, if you have .file asm directive
> either explicitly added to .s file or emitted by compiler, compiler
> would emit it if the path specified to source file is absolute during
> compiler invocation, it will take it verbatim and put it in generated .s
> file

The .s file is not generated and it does not contain any .file
directives. The .o file also does not contain the path. It appears in
the final .so library at linking stage.

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

Re: [OE-core] [devtool][PATCH] devtool deploy-target: optionally specify package

[Andre McCurdy]

On Fri, Jun 1, 2018 at 7:58 AM, Trevor Woerner  wrote:
> On Thu, May 31, 2018 at 11:07 PM, Andre McCurdy  wrote:
>> On Thu, May 31, 2018 at 7:23 PM, Trevor Woerner 
>> wrote:
>>
>> I wonder whether the default behaviour should just be to not deploy
>> files from the -dev package?
>>
>
> That would certainly be an improvement. But it still wouldn't make sense to
> copy over the -staticdev or -doc packages either. Maybe a better default
> behaviour would be to not copy over the -dev, -staticdev, -doc, -dbg, and
> -locale packages?

Right. The list of packages to blacklist by default would need some
thought and it's probably more than just the -dev package.

> Or better yet: just copy over the core packages, not any
> of the core- packages? I'm guessing bitbake has a list somewhere
> of these -somethings?

The core packages can be named almost anything, so blacklisting the
packages which shouldn't be deployed is going to be easier than
whitelisting core packages which should be deployed.

> I wouldn't be surprised if the current behaviour exists simply because ${D}
> is already there and ready to go. My tweak extends the behaviour to send
> another already-there directory: ${PKGDEST} + .
>
> If we were to go this route (i.e. being more selective about which packages
> are sent) do you think this should be the new default behaviour, or should
> the existing default behaviour be preserved and a flag used for this tweak?

I was thinking maybe to exclude -dev packages etc by default and
provide a new command line option to over-ride that and deploy
everything (ie a new command line option gets you back to the current
behaviour).

I don't know whether there's a common use case in the devtool workflow
which relies on -dev packages etc being deployed and would be broken
by that change in behaviour though.

>> >> Are the going to be problems if users want to deploy more than one
>> >> package (or switch between a full deploy and a package) and don't
>> >> deploy and undeploy in the right order?
>> >
>> >
>> > In my patch I added a --package option to "devtool deploy-target" but
>> > not to
>> > "devtool undeploy-target". devtool keeps track of what files were
>> > uploaded
>> > by creating a per-package list on the target itself (in /.devtool). When
>> > you
>> > undeploy a recipe, it simply looks for this recipe file on the target,
>> > reads
>> > the files listed there, and undeploys each of the files in that list.
>> >
>> > Therefore, mixing and matching deploys and undeploys amongst recipes
>> > don't
>> > interfere with each other.
>> >
>> > I checked at the time, but I'm not 100% sure now, but I believe if one
>> > deploys two packages from one recipe, the on-target file gets appended.
>> > But
>> > now I'm not 100% sure, so I'll verify this tomorrow (thanks for the
>> > reminder). As such, under my scheme, you can deploy recipes and packages
>> > at
>> > will, but then only undeploy the whole kit and caboodle in one go; given
>> > a
>> > recipe name to undeploy, whatever it finds in the on-target record will
>> > get
>> > undeployed.
>> >
>> > I think any developer will find this reasonable behaviour (but maybe
>> > not?).
>>
>> If that's how it works then it seems reasonable to me.
>>
>
> Unfortunately this morning's investigation shows this is not the case. When
> a recipe is deployed to the target, the on-target script looks for evidence
> of this recipe having already been deployed. If that is the case, it
> undeploys the previous deploy before deploying this deploy. That is very
> good behaviour since it catches the cases where the file list might change
> between deployments. But with my tweak as-is, if the user deploys two
> packages from the same recipe, the first one will be undeployed and only the
> second one will remain deployed; this is not reasonable.
>
> Therefore a v2 will be necessary. The question is, which route do I take?
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] tune-i586-nlp.inc: drop tuning file for Intel Quark/X1000 CPU

[Andre McCurdy]

On Fri, Jun 1, 2018 at 7:58 AM, Mark Hatle  wrote:
> On 5/31/18 6:10 PM, Andre McCurdy wrote:
>> The Quark machine was EOL'ed at the end of 2017 and all support for
>> it has now been removed from meta-intel. Drop the associated tuning
>> file from oe-core.
>
> I would rather this remain.  There are still a lot of people using the quark
> based boards as hobbyists... there is little effort to maintain it for now.
>
> (we still have support for ARMv4 for instance, which hasn't really been used 
> in
> new designs in a while..)

Is there ever a case when we would drop old tuning files? Or should
they live on forever?

We dropped GPLv2 recipes from oe-core on the grounds that they are
old, unmaintained and untested. ARMv4 CPU tuning files meet those
criteria too.

>>   
>> http://git.yoctoproject.org/cgit.cgi/meta-intel/commit/?id=5dbc69e339588834317b632119717996584b0d6c
>>
>> Signed-off-by: Andre McCurdy 
>> ---
>>  meta/conf/machine/include/tune-i586-nlp.inc | 19 ---
>>  1 file changed, 19 deletions(-)
>>  delete mode 100644 meta/conf/machine/include/tune-i586-nlp.inc
>>
>> diff --git a/meta/conf/machine/include/tune-i586-nlp.inc 
>> b/meta/conf/machine/include/tune-i586-nlp.inc
>> deleted file mode 100644
>> index 88e5903..000
>> --- a/meta/conf/machine/include/tune-i586-nlp.inc
>> +++ /dev/null
>> @@ -1,19 +0,0 @@
>> -# Settings for the GCC(1) cpu-type "quark":
>> -#
>> -#
>> -#
>> -DEFAULTTUNE ?= "i586-nlp-32"
>> -
>> -# Include the previous tune to pull in PACKAGE_EXTRA_ARCHS
>> -require conf/machine/include/x86/arch-x86.inc
>> -
>> -# x86 with no lock prefix
>> -TUNEVALID[i586-nlp] = "IA32 with Lock Prefix omitted"
>> -TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'i586-nlp', ' 
>> -march=i586 -Wa,-momit-lock-prefix=yes', '', d)}"
>> -
>> -# Quark tune feature
>> -AVAILTUNES = "i586-nlp-32"
>> -TUNE_FEATURES_tune-i586-nlp-32 = "${TUNE_FEATURES_tune-x86} i586-nlp"
>> -BASE_LIB_tune-i586-nlp-32 = "lib"
>> -TUNE_PKGARCH_tune-i586-nlp-32 = "i586-nlp-32"
>> -PACKAGE_EXTRA_ARCHS_tune-i586-nlp-32 = "i586-nlp-32"
>>
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 1/2] busybox: update to 1.28.4

[Andre McCurdy]

On Fri, Jun 1, 2018 at 8:00 AM, Armin Kuster  wrote:
> Decided to update again.
>
> 1.28.3
> [v3]
> Update defconfig based on feedback

It looks like you've incorporated the contents of the config fragments
into the new defconfig. e.g. CONFIG_FEATURE_VOLUMEID_EXT (which should
only be enabled if mount-via-label.cfg is included in SRC_URI) will
now be enabled unconditionally, etc.

When you refresh the defconfig you should do so without any config
fragments enabled. The config fragments should then be reviewed
individually too.

> [v2]
> Add back busybox-udhcpc-no_deconfig.patch ti SRC_URI, missed earlier
>
> [v1]
> removed patches included in update:
> busybox/CVE-2011-5325.patch
> busybox/CVE-2017-15873.patch
> busybox/busybox-CVE-2017-16544.patch
>
> refactored busybox-udhcpc-no_deconfig.patch for this update
>
> Signed-off-by: Armin Kuster 
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [devtool][PATCH] devtool deploy-target: optionally specify package

[Khem Raj]

On 5/31/18 1:06 PM, Trevor Woerner wrote:
> Instead of installing an entire recipe's build output (i.e. ${D}), allow the
> user to optionally specify a package from said recipe to be installed
> exclusively (i.e. ${PKGDEST}/).
> 

Thinking of developer's workflow, it might be needed to be able to
install debug/dev packages to debug the package on device.

although I think we should be able to segment it and may be have an
option to install the dev part separately

> Signed-off-by: Trevor Woerner 
> ---
>  scripts/lib/devtool/deploy.py | 26 ++
>  1 file changed, 18 insertions(+), 8 deletions(-)
> 
> diff --git a/scripts/lib/devtool/deploy.py b/scripts/lib/devtool/deploy.py
> index 52e261d560..c022757519 100644
> --- a/scripts/lib/devtool/deploy.py
> +++ b/scripts/lib/devtool/deploy.py
> @@ -169,11 +169,20 @@ def deploy(args, config, basepath, workspace):
>  except Exception as e:
>  raise DevtoolError('Exception parsing recipe %s: %s' %
>  (args.recipename, e))
> -recipe_outdir = rd.getVar('D')
> +if args.package:
> +recipe_outdir = os.path.join(rd.getVar('PKGDEST'), args.package)
> +else:
> +recipe_outdir = rd.getVar('D')
>  if not os.path.exists(recipe_outdir) or not 
> os.listdir(recipe_outdir):
> -raise DevtoolError('No files to deploy - have you built the %s '
> -'recipe? If so, the install step has not 
> installed '
> -'any files.' % args.recipename)
> +if args.package:
> +raise DevtoolError('No files to deploy - have you built the 
> %s '
> +'package of the %s recipe? If so, the 
> install '
> +'step has not installed any files.'
> +% (args.package, args.recipename))
> +else:
> +raise DevtoolError('No files to deploy - have you built the 
> %s '
> +'recipe? If so, the install step has not 
> installed '
> +'any files.' % args.recipename)
>  
>  if args.strip and not args.dry_run:
>  # Fakeroot copy to new destination
> @@ -314,8 +323,8 @@ def register_commands(subparsers, context):
>  """Register devtool subcommands from the deploy plugin"""
>  
>  parser_deploy = subparsers.add_parser('deploy-target',
> -  help='Deploy recipe output files 
> to live target machine',
> -  description='Deploys a recipe\'s 
> build output (i.e. the output of the do_install task) to a live target 
> machine over ssh. By default, any existing files will be preserved instead of 
> being overwritten and will be restored if you run devtool undeploy-target. 
> Note: this only deploys the recipe itself and not any runtime dependencies, 
> so it is assumed that those have been installed on the target beforehand.',
> +  help='Deploy build output to a 
> live target machine',
> +  description='Deploys either the 
> full recipe\'s build output (i.e. the output of the do_install task) or a 
> package of a recipe to a live target machine over ssh. By default, any 
> existing files will be preserved instead of being overwritten and will be 
> restored if you run devtool undeploy-target. Note: this only deploys the 
> specified item itself and not any runtime dependencies, so it is assumed that 
> those have been installed on the target beforehand.',
>group='testbuild')
>  parser_deploy.add_argument('recipename', help='Recipe to deploy')
>  parser_deploy.add_argument('target', help='Live target machine running 
> an ssh server: user@hostname[:destdir]')
> @@ -325,6 +334,7 @@ def register_commands(subparsers, context):
>  parser_deploy.add_argument('-p', '--no-preserve', help='Do not preserve 
> existing files', action='store_true')
>  parser_deploy.add_argument('--no-check-space', help='Do not check for 
> available space before deploying', action='store_true')
>  parser_deploy.add_argument('-P', '--port', help='Specify port to use for 
> connection to the target')
> +parser_deploy.add_argument('--package', help='Specify a recipe\'s 
> package to deploy', dest='package')
>  
>  strip_opts = parser_deploy.add_mutually_exclusive_group(required=False)
>  strip_opts.add_argument('-S', '--strip',
> @@ -337,8 +347,8 @@ def register_commands(subparsers, context):
>  parser_deploy.set_defaults(func=deploy)
>  
>  parser_undeploy = subparsers.add_parser('undeploy-target',
> -help='Undeploy recipe output 
> files in live target machine',
> -description='Un-deploys recipe 
> output 

Re: [OE-core] [PATCH 1/3] systemd: Fix build with gcc8

[Khem Raj]

On 6/1/18 7:01 AM, Martin Jansa wrote:
> No change in PACKAGECONFIG, just default nodistro qemux86 with added
> systemd and debug build:
> DISTRO_FEATURES_append = " systemd"
> DEBUG_BUILD = "1"
> 

hmm so must be some code which is eliminated by compiler optimizations
with -O2 since with debug build it will use -O1

> 
> On Thu, May 31, 2018 at 6:17 PM Khem Raj  > wrote:
> 
> On Thu, May 31, 2018 at 9:05 AM, Martin Jansa
> mailto:martin.ja...@gmail.com>> wrote:
> > Unlike the previous version you had in your RFT branch (which added
> > -Wno-error=format-truncation) this doesn't seem to be complete fix.
> >
> > In qemux86 build which already includes this change I'm seeing:
> > ../git/src/basic/time-util.c: In function 'format_timespan':
> > ../git/src/basic/time-util.c:508:46: error: '%0*llu' directive output
> > between 1 and 2147483647 bytes may cause result to exceed 'INT_MAX'
> > [-Werror=format-truncation=]
> >
> > "%s"USEC_FMT".%0*"PRI_USEC"%s",
> >                                               ^~~~
> > ../git/src/basic/time-util.c:508:60: note: format string is
> defined here
> >
> > "%s"USEC_FMT".%0*"PRI_USEC"%s",
> > ../git/src/basic/time-util.c:508:46: note: directive argument in
> the range
> > [0, 18446744073709551614]
> >
> > "%s"USEC_FMT".%0*"PRI_USEC"%s",
> >                                               ^~~~
> >
> > And this part doesn't seem to be fixed upstream yet.
> >
> 
> Its possible, that default config I build is not using this code. Do
> you enable/disable some specific packageconfig and what arch are you
> targetting
> 
> > Cheers,
> >
> > On Mon, May 28, 2018 at 5:58 PM Khem Raj  > wrote:
> >>
> >> Signed-off-by: Khem Raj  >
> >> ---
> >>  ...ange-the-default-device-timeout-to-2.patch |   9 +-
> >>  ...ation-compile-failure-by-typecasting.patch | 173
> ++
> >>  meta/recipes-core/systemd/systemd_237.bb
>       |   1 +
> >>  3 files changed, 177 insertions(+), 6 deletions(-)
> >>  create mode 100644
> >>
> 
> meta/recipes-core/systemd/systemd/0034-Fix-format-truncation-compile-failure-by-typecasting.patch
> >>
> >> diff --git
> >>
> 
> a/meta/recipes-core/systemd/systemd/0001-core-device.c-Change-the-default-device-timeout-to-2.patch
> >>
> 
> b/meta/recipes-core/systemd/systemd/0001-core-device.c-Change-the-default-device-timeout-to-2.patch
> >> index b7b1ea0886..98c83620ff 100644
> >> ---
> >>
> 
> a/meta/recipes-core/systemd/systemd/0001-core-device.c-Change-the-default-device-timeout-to-2.patch
> >> +++
> >>
> 
> b/meta/recipes-core/systemd/systemd/0001-core-device.c-Change-the-default-device-timeout-to-2.patch
> >> @@ -1,4 +1,4 @@
> >> -From 9820c165a9e559cf851e3beb60fad2571de4ded2 Mon Sep 17
> 00:00:00 2001
> >> +From 7844e070745611a52e355b73e7890f360dd540d0 Mon Sep 17
> 00:00:00 2001
> >>  From: Khem Raj mailto:raj.k...@gmail.com>>
> >>  Date: Mon, 14 Dec 2015 04:09:19 +
> >>  Subject: [PATCH] core/device.c: Change the default device
> timeout to 240
> >> sec.
> >> @@ -16,10 +16,10 @@ Signed-off-by: Khem Raj  >
> >>   1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >>  diff --git a/src/core/device.c b/src/core/device.c
> >> -index 77601c552..98bf49ba2 100644
> >> +index a43664d3b..4b16a8aec 100644
> >>  --- a/src/core/device.c
> >>  +++ b/src/core/device.c
> >> -@@ -112,7 +112,7 @@ static void device_init(Unit *u) {
> >> +@@ -113,7 +113,7 @@ static void device_init(Unit *u) {
> >>            * indefinitely for plugged in devices, something which
> cannot
> >>            * happen for the other units since their operations
> time out
> >>            * anyway. */
> >> @@ -28,6 +28,3 @@ index 77601c552..98bf49ba2 100644
> >>
> >>           u->ignore_on_isolate = true;
> >>   }
> >> ---
> >> -2.16.1
> >> -
> >> diff --git
> >>
> 
> a/meta/recipes-core/systemd/systemd/0034-Fix-format-truncation-compile-failure-by-typecasting.patch
> >>
> 
> b/meta/recipes-core/systemd/systemd/0034-Fix-format-truncation-compile-failure-by-typecasting.patch
> >> new file mode 100644
> >> index 00..e56061f41b
> >> --- /dev/null
> >> +++
> >>
> 
> b/meta/recipes-core/systemd/systemd/0034-Fix-format-truncation-compile-failure-by-typecasting.patch
> >> @@ -0,0 +1,173 @@
> >> +From c2b3ebe112ebfd9f9e82fb1531ee225c3152ca83 Mon Sep 17
> 00:00:00 2001
> >> +From: Patrick Uiterwijk  >
> >> +Date: Thu, 22 Feb 2018 19:41:30 +0100
> >> +Subject: [PATCH] Fix format-truncation compile 

Re: [OE-core] [PATCH] boost: Improve reproducibility

[Khem Raj]

On 5/31/18 10:38 PM, Yu, Mingli wrote:
> 
> 
> On 2018年06月01日 13:08, Alexander Kanavin wrote:
>> 2018-06-01 4:39 GMT+03:00 Yu, Mingli :
>>
 This looks very unlikely to ever make it upstream. Rather than carrying
 a patch to boost forever would we want to just strip the file in
 question with a custom command?
>>>
>>>
>>> Thanks very much Richard for your respond!
>>> I did try to strip only file which in question, but not find out the
>>> solution and then turn to strip the context library.
>>>
>>> Alex,
>>> Do you have any suggestion?
>>
>> Yes - as RP said, please investigate how the path gets into this
>> specific file (but not other files) in the first place, and whether we
>> can disable or make it not happen, rather than strip the path after
>> the fact.
> 
> Hi Alex,
> 
> Thanks for your respond!
> I did investigate the path a lot before send out the patch, but didn't
> figure out why it introduce the path for make_x86_64_sysv_elf_gas.o
> whose source file is make_x86_64_sysv_elf_gas.S.
> 
> Anyway, I will try to dig more.
> 
> If you have any ideas, welcome to help provide some hint.
> 

these symbols are added by assembler, if you have .file asm directive
either explicitly added to .s file or emitted by compiler, compiler
would emit it if the path specified to source file is absolute during
compiler invocation, it will take it verbatim and put it in generated .s
file

you might then want to check if you can see whats happening when this
file is being either compiled or assembled and make the changes there
such that it can be specified via a topdir relative path. that should
fix the issue.

> Thanks,
> 
> 
>>
>> Alex
>>




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] [master][PATCH 2/4] qemu: upgrade to 2.12.0

[Alistair Francis]

On Fri, Jun 1, 2018 at 3:29 AM, Martin Jansa  wrote:
> From: Martin Jansa 
>
> * drop patches which are now included upstream
> * revert "linux-user: fix mmap/munmap/mprotect/mremap/shma" which is
>   causing
>   0010-linux-user-Fix-webkitgtk-hangs-on-32-bit-x86-target.patch
>   to stop working and qemu-i386 hanging during gobject-introspection in
>   webkitgtk when building for qemux86 with musl
>
> Signed-off-by: Martin Jansa 
> Signed-off-by: Ross Burton 

This fixes the hang for me.

Alistair

> ---
>  meta/conf/distro/include/tcmode-default.inc   |   2 +-
>  ...-allow-user-to-disable-pointer-grabs.patch |  23 +--
>  ...emu-Add-missing-wacom-HID-descriptor.patch |   6 +-
>  ...test-which-runs-all-unit-test-cases-.patch |   6 +-
>  ...n-environment-space-to-boot-loader-q.patch |   6 +-
>  .../qemu/0005-qemu-disable-Valgrind.patch |   6 +-
>  ...-searched-during-user-mode-emulation.patch |   4 +-
>  ...ld.bfd-fix-cflags-and-set-some-envir.patch |   8 +-
>  ...-connect-socket-to-a-spawned-command.patch |  60 
>  .../0009-apic-fixup-fallthrough-to-PIC.patch  |   6 +-
>  ...webkitgtk-hangs-on-32-bit-x86-target.patch |   6 +-
>  ...r-fix-mmap-munmap-mprotect-mremap-sh.patch | 141 ++
>  .../qemu/0011-memfd-fix-configure-test.patch  |  54 ---
>  ...4-treat-DISAS_UPDATE-as-variant-of-D.patch |  64 
>  ...-libcap-header-issue-on-some-distro.patch} |   4 +-
>  ...messages-when-qemi_cpu_kick_thread-.patch} |  10 +-
>  ...2Queue-pointers-in-post_load-routine.patch |  60 
>  .../qemu/{qemu_2.11.1.bb => qemu_2.12.0.bb}   |  12 +-
>  18 files changed, 220 insertions(+), 258 deletions(-)
>  create mode 100644 
> meta/recipes-devtools/qemu/qemu/0011-Revert-linux-user-fix-mmap-munmap-mprotect-mremap-sh.patch
>  delete mode 100644 
> meta/recipes-devtools/qemu/qemu/0011-memfd-fix-configure-test.patch
>  delete mode 100644 
> meta/recipes-devtools/qemu/qemu/0012-arm-translate-a64-treat-DISAS_UPDATE-as-variant-of-D.patch
>  rename 
> meta/recipes-devtools/qemu/qemu/{0014-fix-libcap-header-issue-on-some-distro.patch
>  => 0012-fix-libcap-header-issue-on-some-distro.patch} (96%)
>  rename 
> meta/recipes-devtools/qemu/qemu/{0015-cpus.c-Add-error-messages-when-qemi_cpu_kick_thread-.patch
>  => 0013-cpus.c-Add-error-messages-when-qemi_cpu_kick_thread-.patch} (87%)
>  delete mode 100644 
> meta/recipes-devtools/qemu/qemu/0013-ps2-check-PS2Queue-pointers-in-post_load-routine.patch
>  rename meta/recipes-devtools/qemu/{qemu_2.11.1.bb => qemu_2.12.0.bb} (80%)
>
> diff --git a/meta/conf/distro/include/tcmode-default.inc 
> b/meta/conf/distro/include/tcmode-default.inc
> index 4b58df0459..48383d4ac0 100644
> --- a/meta/conf/distro/include/tcmode-default.inc
> +++ b/meta/conf/distro/include/tcmode-default.inc
> @@ -28,7 +28,7 @@ BINUVERSION ?= "2.30%"
>  GDBVERSION ?= "8.1%"
>  GLIBCVERSION ?= "2.27%"
>  LINUXLIBCVERSION ?= "4.15%"
> -QEMUVERSION ?= "2.11%"
> +QEMUVERSION ?= "2.12%"
>
>  PREFERRED_VERSION_gcc ?= "${GCCVERSION}"
>  PREFERRED_VERSION_gcc-cross-${TARGET_ARCH} ?= "${GCCVERSION}"
> diff --git 
> a/meta/recipes-devtools/qemu/qemu/0001-sdl.c-allow-user-to-disable-pointer-grabs.patch
>  
> b/meta/recipes-devtools/qemu/qemu/0001-sdl.c-allow-user-to-disable-pointer-grabs.patch
> index add5d8b02f..b8a9206fee 100644
> --- 
> a/meta/recipes-devtools/qemu/qemu/0001-sdl.c-allow-user-to-disable-pointer-grabs.patch
> +++ 
> b/meta/recipes-devtools/qemu/qemu/0001-sdl.c-allow-user-to-disable-pointer-grabs.patch
> @@ -1,4 +1,4 @@
> -From 273e1af49d3e0a58bb9464369deb2652f243e649 Mon Sep 17 00:00:00 2001
> +From 18fb45c34a473c4ba247bb82bcea94b7c3ba493a Mon Sep 17 00:00:00 2001
>  From: Ross Burton 
>  Date: Wed, 18 Sep 2013 14:04:54 +0100
>  Subject: [PATCH] sdl.c: allow user to disable pointer grabs
> @@ -22,25 +22,26 @@ Upstream-Status: Pending
>  Signed-off-by: Ross Burton 
>  Signed-off-by: Eric Bénard 
>  ---
> - ui/sdl.c | 12 ++--
> - 1 file changed, 10 insertions(+), 2 deletions(-)
> + ui/sdl.c | 13 +++--
> + 1 file changed, 11 insertions(+), 2 deletions(-)
>
>  diff --git a/ui/sdl.c b/ui/sdl.c
> -index 7b71a9a..29ce1b9 100644
> +index a5fd503c25..ab8d1b1eb1 100644
>  --- a/ui/sdl.c
>  +++ b/ui/sdl.c
> -@@ -63,6 +63,10 @@ static SDL_PixelFormat host_format;
> - static int scaling_active = 0;
> - static Notifier mouse_mode_notifier;
> - static int idle_counter;
> +@@ -68,6 +68,11 @@ static int idle_counter;
> + static const guint16 *keycode_map;
> + static size_t keycode_maplen;
> +
>  +#ifndef True
>  +#define True 1
>  +#endif
>  +static doing_grabs = True;
> -
> ++
>   #define SDL_REFRESH_INTERVAL_BUSY 10
>   #define SDL_MAX_IDLE_COUNT (2 * GUI_REFRESH_INTERVAL_DEFAULT \
> -@@ -431,14 +435,16 @@ static void sdl_grab_start(void)
> + / SDL_REFRESH_INTERVAL_BUSY + 1)
> +@@ -398,14 +403,16 @@ static void sdl_grab_start(void)
>   }
>   } else
>   sdl_hide_cursor();
> @@ -59,7 +60,7 @@ index 7b71a9a..29ce1b9 100644
>   

[OE-core] [meta][lib/oeqa][PATCH v2] Meta runtime cases: add testcases for kernel sample

[Hongzhi.Song]

We are going to let runtime test support kernel tests. Now we just add
kernel self-contained sample tests. And we plan to add overall kernel
tests in the future.

This patch is just add kernel samples test which contains about 13 tests
enabled by kernel-sample.scc. So it needs statement,
KERNEL_FEATURES_append += " kernel-sample/kernel-sample.scc" in
local.conf.

Signed-off-by: Hongzhi.Song 
---
 meta/lib/oeqa/runtime/cases/ksample.py | 272 +
 meta/lib/oeqa/runtime/cases/ksample_abs.py | 272 +
 2 files changed, 544 insertions(+)
 create mode 100644 meta/lib/oeqa/runtime/cases/ksample.py
 create mode 100644 meta/lib/oeqa/runtime/cases/ksample_abs.py

diff --git a/meta/lib/oeqa/runtime/cases/ksample.py 
b/meta/lib/oeqa/runtime/cases/ksample.py
new file mode 100644
index 000..719f1a0
--- /dev/null
+++ b/meta/lib/oeqa/runtime/cases/ksample.py
@@ -0,0 +1,272 @@
+import os
+import time
+
+from oeqa.runtime.case import OERuntimeTestCase
+from oeqa.core.decorator.depends import OETestDepends
+from oeqa.core.decorator.oeid import OETestID
+from oeqa.core.decorator.data import skipIfNotFeature
+
+class KSample(OERuntimeTestCase):
+def send_cmd(self, cmd='', content=''):
+comd = cmd + " " + content
+status, ret = self.target.run(comd)
+msg = '%s failed, %s' % (comd, ret)
+self.assertEqual(status, 0, msg=msg)
+
+def check_config(self, config_opt=''):
+cmd = "zcat /proc/config.gz | grep %s" % config_opt
+status, ret = self.target.run(cmd)
+result = ("%s=y" % config_opt) in ret
+if not result:
+self.skipTest("CONFIG error")
+
+def check_module_exist(self, path='', module_name=''):
+status, ret = self.target.run("uname -r")
+cmd = "ls " + "/lib/modules/" + ret + "/kernel/samples/" + path + 
module_name
+status, output = self.target.run(cmd)
+if status != 0:
+error_info = module_name + "doesn't exist"
+self.skipTest(error_info)
+
+def send_check(self, cmd='', content='', comp=''):
+comd = cmd + " " + content
+status, ret = self.target.run(comd)
+self.assertEqual(ret, comp, comd)
+
+def send_check_in(self, cmd='', content='', comp=''):
+comd = cmd + " " + content
+status, ret = self.target.run(comd)
+result = ("%s" % comp) in ret
+self.assertTrue(result)
+self.assertEqual(status, 0, comd)
+
+class KSampleTest(KSample):
+#trace
+@OETestID(33)
+@OETestDepends(['ssh.SSHTest.test_ssh'])
+def test_trace_events(self):
+# check config
+self.check_config("CONFIG_TRACING_SUPPORT")
+# make sure if module exists
+self.check_module_exist("trace_events/", "trace-events-sample.ko")
+# modprobe
+self.send_cmd("modprobe", "trace-events-sample")
+# lsmod
+self.send_check("lsmod", "| grep trace_events_sample | cut -d\' \' 
-f1", "trace_events_sample")
+# check dir
+self.send_check("ls", "/sys/kernel/debug/tracing/events/ | grep 
sample-trace", "sample-trace")
+# enable trace
+self.send_cmd("echo 1 > 
/sys/kernel/debug/tracing/events/sample-trace/enable")
+self.send_cmd("cat 
/sys/kernel/debug/tracing/events/sample-trace/enable")
+# check result
+self.send_check("cat", "/sys/kernel/debug/tracing/trace | grep hello | 
head -n1 | cut -d\':\' -f2", " foo_bar")
+# disable trace
+self.send_cmd('echo 0 > 
/sys/kernel/debug/tracing/events/sample-trace/enable')
+# clean up trace
+self.send_cmd('echo > /sys/kernel/debug/tracing/trace')
+# rmmod
+self.send_cmd('rmmod trace-events-sample')
+
+@OETestID(34)
+@OETestDepends(['ssh.SSHTest.test_ssh'])
+def test_trace_printk(self):
+# check config
+self.check_config("CONFIG_TRACING_SUPPORT")
+# make sure if module exists
+self.check_module_exist("trace_printk/", "trace-printk.ko")
+# modprobe
+self.send_cmd('modprobe', 'trace-printk')
+# lsmod
+self.send_check("lsmod", "| grep trace_printk | cut -d\' \' -f1", 
"trace_printk")
+# check result
+self.send_check("cat", "/sys/kernel/debug/tracing/trace | grep 
trace_printk_irq_work | head -n1 | cut -d\':\' -f2", " trace_printk_irq_work")
+# clean up trace
+self.send_cmd('echo > /sys/kernel/debug/tracing/trace')
+# rmmod
+self.send_cmd('rmmod trace-printk')
+# kprobe
+@OETestID(43)
+@OETestDepends(['ssh.SSHTest.test_ssh'])
+def test_kprobe_example(self):
+# check config
+self.check_config("CONFIG_KPROBES")
+# make sure if module exists
+self.check_module_exist("kprobes/", "kprobe_example.ko")
+# modprobe
+self.send_cmd('modprobe', 'kprobe_example')
+# lsmod
+self.send_check("lsmod", "| grep kprobe_example | 

[OE-core] [PATCH] systemd: fix build with gcc8

[Martin Jansa]

Signed-off-by: Martin Jansa 
---
 ...ild-with-gcc8-Werror-format-truncati.patch | 53 +++
 meta/recipes-core/systemd/systemd_237.bb  |  1 +
 2 files changed, 54 insertions(+)
 create mode 100644 
meta/recipes-core/systemd/systemd/0036-time-util-fix-build-with-gcc8-Werror-format-truncati.patch

diff --git 
a/meta/recipes-core/systemd/systemd/0036-time-util-fix-build-with-gcc8-Werror-format-truncati.patch
 
b/meta/recipes-core/systemd/systemd/0036-time-util-fix-build-with-gcc8-Werror-format-truncati.patch
new file mode 100644
index 00..e44f431073
--- /dev/null
+++ 
b/meta/recipes-core/systemd/systemd/0036-time-util-fix-build-with-gcc8-Werror-format-truncati.patch
@@ -0,0 +1,53 @@
+From f9fd4546c25a15629544bc4642a74d7909cc0840 Mon Sep 17 00:00:00 2001
+From: Martin Jansa 
+Date: Fri, 1 Jun 2018 15:22:28 +
+Subject: [PATCH] time-util: fix build with gcc8 -Werror=format-truncation=
+
+* it fails with gcc8 when -O1 or -Os is used (and -ftree-vrp which is added by 
-O2 and higher isn't used)
+
+../git/src/basic/time-util.c: In function 'format_timespan':
+../git/src/basic/time-util.c:508:46: error: '%0*llu' directive output between 
1 and 2147483647 bytes may cause result to exceed 'INT_MAX' 
[-Werror=format-truncation=]
+  "%s"USEC_FMT".%0*"PRI_USEC"%s",
+  ^~~~
+../git/src/basic/time-util.c:508:60: note: format string is defined here
+  "%s"USEC_FMT".%0*"PRI_USEC"%s",
+../git/src/basic/time-util.c:508:46: note: directive argument in the range [0, 
18446744073709551614]
+  "%s"USEC_FMT".%0*"PRI_USEC"%s",
+  ^~~~
+../git/src/basic/time-util.c:507:37: note: 'snprintf' output 4 or more bytes 
(assuming 2147483651) into a destination of size 4294967295
+ k = snprintf(p, l,
+ ^~
+  "%s"USEC_FMT".%0*"PRI_USEC"%s",
+  ~~~
+  p > buf ? " " : "",
+  ~~~
+  a,
+  ~~
+  j,
+  ~~
+  b,
+  ~~
+  table[i].suffix);
+  
+cc1: some warnings being treated as errors
+
+Upstream-Status: Submitted https://github.com/systemd/systemd/pull/9156
+
+Signed-off-by: Martin Jansa 
+---
+ src/basic/time-util.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/basic/time-util.c b/src/basic/time-util.c
+index 0601d4fa9..db5a9cd78 100644
+--- a/src/basic/time-util.c
 b/src/basic/time-util.c
+@@ -484,7 +484,7 @@ char *format_timespan(char *buf, size_t l, usec_t t, 
usec_t accuracy) {
+ /* Let's see if we should shows this in dot notation */
+ if (t < USEC_PER_MINUTE && b > 0) {
+ usec_t cc;
+-int j;
++char j;
+ 
+ j = 0;
+ for (cc = table[i].usec; cc > 1; cc /= 10)
diff --git a/meta/recipes-core/systemd/systemd_237.bb 
b/meta/recipes-core/systemd/systemd_237.bb
index 2e6558ded1..0113c2dc72 100644
--- a/meta/recipes-core/systemd/systemd_237.bb
+++ b/meta/recipes-core/systemd/systemd_237.bb
@@ -54,6 +54,7 @@ SRC_URI += "file://touchscreen.rules \
file://libmount.patch \

file://0034-Fix-format-truncation-compile-failure-by-typecasting.patch \

file://0035-Define-glibc-compatible-basename-for-non-glibc-syste.patch \
+   
file://0036-time-util-fix-build-with-gcc8-Werror-format-truncati.patch \
"
 SRC_URI_append_qemuall = " 
file://0001-core-device.c-Change-the-default-device-timeout-to-2.patch"
 
-- 
2.17.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

[akuster808]

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.

>> - xf86-input-mouse
sent fixed for xf86-inout-mount

>> - xf86-video-omapfb
> hmm, will double check
>
> - armin
>> Ross
>>
>> On 19 May 2018 at 03:13, Armin Kuster  wrote:
>>> From: Armin Kuster 
>>>
>>> Signed-off-by: Armin Kuster 
>>> ---
>>>  ...1-configure.ac-Fix-check-for-CLOCK_MONOTONIC.patch | 19 
>>> +--
>>>  ...{xserver-xorg_1.19.6.bb => xserver-xorg_1.20.0.bb} |  4 ++--
>>>  2 files changed, 11 insertions(+), 12 deletions(-)
>>>  rename meta/recipes-graphics/xorg-xserver/{xserver-xorg_1.19.6.bb => 
>>> xserver-xorg_1.20.0.bb} (89%)
>>>
>>> diff --git 
>>> a/meta/recipes-graphics/xorg-xserver/xserver-xorg/0001-configure.ac-Fix-check-for-CLOCK_MONOTONIC.patch
>>>  
>>> b/meta/recipes-graphics/xorg-xserver/xserver-xorg/0001-configure.ac-Fix-check-for-CLOCK_MONOTONIC.patch
>>> index 16ec3ed..020a1cf 100644
>>> --- 
>>> a/meta/recipes-graphics/xorg-xserver/xserver-xorg/0001-configure.ac-Fix-check-for-CLOCK_MONOTONIC.patch
>>> +++ 
>>> b/meta/recipes-graphics/xorg-xserver/xserver-xorg/0001-configure.ac-Fix-check-for-CLOCK_MONOTONIC.patch
>>> @@ -1,12 +1,13 @@
>>> -Discover monotonic clock using compile-time check
>>> +From 8a91316c4a38f20e7866289f3d779a037d27a129 Mon Sep 17 00:00:00 2001
>>> +From: Jussi Kukkonen 
>>> +Date: Mon, 12 Dec 2016 12:11:39 +0200
>>> +Subject: [PATCH] Discover monotonic clock using compile-time check
>>>
>>>  monotonic clock check does not work when cross-compiling.
>>>
>>>  Upstream-Status: Denied [Does not work on OpenBSD]
>>>  Signed-off-by: Jussi Kukkonen 
>>>
>>> -
>>> -
>>>  Original patch follows:
>>>
>>>  When xorg-xserver is being cross-compiled, there is currently no way
>>> @@ -21,15 +22,16 @@ monotonic clock is available. This check can run just 
>>> fine when we are
>>>  cross-compiling.
>>>
>>>  Signed-off-by: David James 
>>> +
>>>  ---
>>>   configure.ac | 17 +++--
>>>   1 file changed, 7 insertions(+), 10 deletions(-)
>>>
>>>  diff --git a/configure.ac b/configure.ac
>>> -index f7ab48c..26e85cd 100644
>>> +index 2b21667..786e002 100644
>>>  --- a/configure.ac
>>>  +++ b/configure.ac
>>> -@@ -1048,19 +1048,16 @@ if ! test "x$have_clock_gettime" = xno; then
>>> +@@ -984,19 +984,16 @@ if ! test "x$have_clock_gettime" = xno; then
>>>   CPPFLAGS="$CPPFLAGS -D_POSIX_C_SOURCE=200112L"
>>>   fi
>>>
>>> @@ -54,8 +56,5 @@ index f7ab48c..26e85cd 100644
>>>  -   [MONOTONIC_CLOCK="cross compiling"])
>>>  +]])],[MONOTONIC_CLOCK=yes], [MONOTONIC_CLOCK=no])
>>>
>>> - LIBS="$LIBS_SAVE"
>>> - CPPFLAGS="$CPPFLAGS_SAVE"
>>> ---
>>> -2.1.4
>>> -
>>> + if test "$MONOTONIC_CLOCK" = "cross compiling"; then
>>> + AC_CHECK_DECL([CLOCK_MONOTONIC],[MONOTONIC_CLOCK="guessing 
>>> yes"],[MONOTONIC_CLOCK=no],[#include ])
>>> diff --git a/meta/recipes-graphics/xorg-xserver/xserver-xorg_1.19.6.bb 
>>> b/meta/recipes-graphics/xorg-xserver/xserver-xorg_1.20.0.bb
>>> similarity index 89%
>>> rename from meta/recipes-graphics/xorg-xserver/xserver-xorg_1.19.6.bb
>>> rename to meta/recipes-graphics/xorg-xserver/xserver-xorg_1.20.0.bb
>>> index c680cf9..620eb7b 100644
>>> --- a/meta/recipes-graphics/xorg-xserver/xserver-xorg_1.19.6.bb
>>> +++ b/meta/recipes-graphics/xorg-xserver/xserver-xorg_1.20.0.bb
>>> @@ -6,8 +6,8 @@ SRC_URI += "file://musl-arm-inb-outb.patch \
>>>  file://0003-Remove-check-for-useSIGIO-option.patch \
>>>  
>>> file://0001-xf86pciBus.c-use-Intel-ddx-only-for-pre-gen4-hardwar.patch \
>>>  "
>>> -SRC_URI[md5sum] = "3e4ff034a331aed2322b078694a8"
>>> -SRC_URI[sha256sum] = 
>>> "a732502f1db000cf36a376cd0c010ffdbf32ecdd7f1fa08ba7f5bdf9601cc197"
>>> +SRC_URI[md5sum] = "c1ca1ea0a905ea788da03c77cc38b06e"
>>> +SRC_URI[sha256sum] = 
>>> "9d967d185f05709274ee0c4f861a4672463986e550ca05725ce27974f550d3e6"
>>>
>>>  # These extensions are now integrated into the server, so declare the 
>>> migration
>>>  # path for in-place upgrades.
>>> --
>>> 2.7.4
>>>
>>> --
>>> ___
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.openembedded.org/mailman/listinfo/openembedded-core

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

[OE-core] [PATCH 2/2] xf86-input-mouse: add fix for buld fix do for 1.20 xorg-server update

[Armin Kuster]

 ../../xf86-input-mouse-1.9.2/src/mouse.c:824:5: error: implicit declaration of 
function 'xf86GetOS'; did you mean 'xf86SetDpi'? 
[-Werror=implicit-function-declaration]
|  xf86GetOS(, NULL, NULL, NULL);
|  ^

Signed-off-by: Armin Kuster 
---
 .../0001-Adapt-to-removal-of-xf86GetOS.patch   | 48 ++
 .../xorg-driver/xf86-input-mouse_1.9.2.bb  |  2 +
 2 files changed, 50 insertions(+)
 create mode 100644 
meta/recipes-graphics/xorg-driver/xf86-input-mouse/0001-Adapt-to-removal-of-xf86GetOS.patch

diff --git 
a/meta/recipes-graphics/xorg-driver/xf86-input-mouse/0001-Adapt-to-removal-of-xf86GetOS.patch
 
b/meta/recipes-graphics/xorg-driver/xf86-input-mouse/0001-Adapt-to-removal-of-xf86GetOS.patch
new file mode 100644
index 000..4a082c0
--- /dev/null
+++ 
b/meta/recipes-graphics/xorg-driver/xf86-input-mouse/0001-Adapt-to-removal-of-xf86GetOS.patch
@@ -0,0 +1,48 @@
+From 3c8f243b750a92d5837a449d344ff884dbd02b57 Mon Sep 17 00:00:00 2001
+From: Adam Jackson 
+Date: Thu, 16 Feb 2017 09:21:21 -0500
+Subject: [PATCH] Adapt to removal of xf86GetOS
+
+Signed-off-by: Adam Jackson 
+
+Upstream-Status: Backport
+Fixes build issue with updated xorg-server changes.
+
+Signed-off-by: Armin Kuster 
+
+---
+ src/mouse.c | 11 +--
+ 1 file changed, 5 insertions(+), 6 deletions(-)
+
+diff --git a/src/mouse.c b/src/mouse.c
+index dae98aa..40d97a9 100644
+--- a/src/mouse.c
 b/src/mouse.c
+@@ -794,7 +794,6 @@ InitProtocols(void)
+ {
+ int classes;
+ int i;
+-const char *osname = NULL;
+ 
+ if (osInfo)
+ return TRUE;
+@@ -821,11 +820,11 @@ InitProtocols(void)
+ mouseProtocols[i].id = PROT_UNSUP;
+ 
+ /* NetBSD uses PROT_BM for "PS/2". */
+-xf86GetOS(, NULL, NULL, NULL);
+-if (osname && xf86NameCmp(osname, "netbsd") == 0)
+-for (i = 0; mouseProtocols[i].name; i++)
+-if (mouseProtocols[i].id == PROT_PS2)
+-mouseProtocols[i].id = PROT_BM;
++#if defined(__NetBSD__)
++for (i = 0; mouseProtocols[i].name; i++)
++if (mouseProtocols[i].id == PROT_PS2)
++mouseProtocols[i].id = PROT_BM;
++#endif
+ 
+ return TRUE;
+ }
+-- 
+2.7.4
+
diff --git a/meta/recipes-graphics/xorg-driver/xf86-input-mouse_1.9.2.bb 
b/meta/recipes-graphics/xorg-driver/xf86-input-mouse_1.9.2.bb
index 0750476..8dea384 100644
--- a/meta/recipes-graphics/xorg-driver/xf86-input-mouse_1.9.2.bb
+++ b/meta/recipes-graphics/xorg-driver/xf86-input-mouse_1.9.2.bb
@@ -10,5 +10,7 @@ driver."
 
 LIC_FILES_CHKSUM = "file://COPYING;md5=90ea9f90d72b6d9327dede5ffdb2a510"
 
+SRC_URI += "file://0001-Adapt-to-removal-of-xf86GetOS.patch"
+
 SRC_URI[md5sum] = "ce2d679283a22c8e0dccdd9248594845"
 SRC_URI[sha256sum] = 
"f425d5b05c6ab412a27e0a1106bb83f9e2662b307210abbe48270892387f4b2f"
-- 
2.7.4

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

[OE-core] [PATCH 1/2] busybox: update to 1.28.4

[Armin Kuster]

Decided to update again.

1.28.3
[v3]
Update defconfig based on feedback

[v2]
Add back busybox-udhcpc-no_deconfig.patch ti SRC_URI, missed earlier

[v1]
removed patches included in update:
busybox/CVE-2011-5325.patch
busybox/CVE-2017-15873.patch
busybox/busybox-CVE-2017-16544.patch

refactored busybox-udhcpc-no_deconfig.patch for this update

Signed-off-by: Armin Kuster 
---
 .../busybox/busybox/CVE-2011-5325.patch| 481 -
 .../busybox/busybox/CVE-2017-15873.patch   |  95 
 .../busybox/busybox/busybox-CVE-2017-16544.patch   |  43 --
 .../busybox/busybox-udhcpc-no_deconfig.patch   |  36 +-
 meta/recipes-core/busybox/busybox/defconfig| 262 +--
 .../{busybox_1.27.2.bb => busybox_1.28.4.bb}   |   7 +-
 6 files changed, 154 insertions(+), 770 deletions(-)
 delete mode 100755 meta/recipes-core/busybox/busybox/CVE-2011-5325.patch
 delete mode 100644 meta/recipes-core/busybox/busybox/CVE-2017-15873.patch
 delete mode 100644 
meta/recipes-core/busybox/busybox/busybox-CVE-2017-16544.patch
 rename meta/recipes-core/busybox/{busybox_1.27.2.bb => busybox_1.28.4.bb} (86%)

diff --git a/meta/recipes-core/busybox/busybox/CVE-2011-5325.patch 
b/meta/recipes-core/busybox/busybox/CVE-2011-5325.patch
deleted file mode 100755
index 0926107..000
--- a/meta/recipes-core/busybox/busybox/CVE-2011-5325.patch
+++ /dev/null
@@ -1,481 +0,0 @@
-busybox-1.27.2: Fix CVE-2011-5325
-
-[No upstream tracking] -- https://bugs.busybox.net/show_bug.cgi?id=8411
-
-libarchive: do not extract unsafe symlinks
-
-Prevent unsafe links extracting unless env variable $EXTRACT_UNSAFE_SYMLINKS=1
-is not set. Untarring file with -C DESTDIR parameter could be extracted with
-unwanted symlinks. This doesn't feel right, and IIRC GNU tar doesn't do that.
-Include necessary changes from previous commits.
-
-Upstream-Status: Backport 
[https://git.busybox.net/busybox/commit/?id=bc9bbeb2b81001e8731cd2ae501c8fccc8d87cc7]
-CVE: CVE-2011-5325
-bug: 8411
-Signed-off-by: Radovan Scasny 
-Signed-off-by: Andrej Valek 
-
-diff --git a/archival/libarchive/Kbuild.src b/archival/libarchive/Kbuild.src
-index 942e755..e1a8a75 100644
 a/archival/libarchive/Kbuild.src
-+++ b/archival/libarchive/Kbuild.src
-@@ -12,6 +12,8 @@ COMMON_FILES:= \
-   data_extract_all.o \
-   data_extract_to_stdout.o \
- \
-+  unsafe_symlink_target.o \
-+\
-   filter_accept_all.o \
-   filter_accept_list.o \
-   filter_accept_reject_list.o \
-diff --git a/archival/libarchive/data_extract_all.c 
b/archival/libarchive/data_extract_all.c
-index 1830ffb..b828b65 100644
 a/archival/libarchive/data_extract_all.c
-+++ b/archival/libarchive/data_extract_all.c
-@@ -128,10 +128,9 @@ void FAST_FUNC data_extract_all(archive_handle_t 
*archive_handle)
-   res = link(hard_link, dst_name);
-   if (res != 0 && !(archive_handle->ah_flags & 
ARCHIVE_EXTRACT_QUIET)) {
-   /* shared message */
--  bb_perror_msg("can't create %slink "
--  "%s to %s", "hard",
--  dst_name,
--  hard_link);
-+  bb_perror_msg("can't create %slink '%s' to '%s'",
-+   "hard", dst_name, hard_link
-+  );
-   }
-   /* Hardlinks have no separate mode/ownership, skip chown/chmod 
*/
-   goto ret;
-@@ -178,15 +177,17 @@ void FAST_FUNC data_extract_all(archive_handle_t 
*archive_handle)
-   case S_IFLNK:
-   /* Symlink */
- //TODO: what if file_header->link_target == NULL (say, corrupted tarball?)
--  res = symlink(file_header->link_target, dst_name);
--  if (res != 0
--   && !(archive_handle->ah_flags & ARCHIVE_EXTRACT_QUIET)
--  ) {
--  /* shared message */
--  bb_perror_msg("can't create %slink "
--  "%s to %s", "sym",
--  dst_name,
--  file_header->link_target);
-+  if (!unsafe_symlink_target(file_header->link_target)) {
-+  res = symlink(file_header->link_target, dst_name);
-+  if (res != 0
-+  && !(archive_handle->ah_flags & 
ARCHIVE_EXTRACT_QUIET)
-+  ) {
-+  /* shared message */
-+  bb_perror_msg("can't create 
%slink '%s' to '%s'",
-+  "sym",
-+  dst_name, 
file_header->link_target
-+  );
-+  }
-   }
-   break;
-   case S_IFSOCK:
-diff --git a/archival/libarchive/unsafe_symlink_target.c 

Re: [OE-core] [PATCH] tune-i586-nlp.inc: drop tuning file for Intel Quark/X1000 CPU

[Mark Hatle]

On 5/31/18 6:10 PM, Andre McCurdy wrote:
> The Quark machine was EOL'ed at the end of 2017 and all support for
> it has now been removed from meta-intel. Drop the associated tuning
> file from oe-core.

I would rather this remain.  There are still a lot of people using the quark
based boards as hobbyists... there is little effort to maintain it for now.

(we still have support for ARMv4 for instance, which hasn't really been used in
new designs in a while..)

--Mark

>   
> http://git.yoctoproject.org/cgit.cgi/meta-intel/commit/?id=5dbc69e339588834317b632119717996584b0d6c
> 
> Signed-off-by: Andre McCurdy 
> ---
>  meta/conf/machine/include/tune-i586-nlp.inc | 19 ---
>  1 file changed, 19 deletions(-)
>  delete mode 100644 meta/conf/machine/include/tune-i586-nlp.inc
> 
> diff --git a/meta/conf/machine/include/tune-i586-nlp.inc 
> b/meta/conf/machine/include/tune-i586-nlp.inc
> deleted file mode 100644
> index 88e5903..000
> --- a/meta/conf/machine/include/tune-i586-nlp.inc
> +++ /dev/null
> @@ -1,19 +0,0 @@
> -# Settings for the GCC(1) cpu-type "quark":
> -#
> -#
> -#
> -DEFAULTTUNE ?= "i586-nlp-32"
> -
> -# Include the previous tune to pull in PACKAGE_EXTRA_ARCHS
> -require conf/machine/include/x86/arch-x86.inc
> -
> -# x86 with no lock prefix
> -TUNEVALID[i586-nlp] = "IA32 with Lock Prefix omitted"
> -TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'i586-nlp', ' 
> -march=i586 -Wa,-momit-lock-prefix=yes', '', d)}"
> -
> -# Quark tune feature
> -AVAILTUNES = "i586-nlp-32"
> -TUNE_FEATURES_tune-i586-nlp-32 = "${TUNE_FEATURES_tune-x86} i586-nlp"
> -BASE_LIB_tune-i586-nlp-32 = "lib"
> -TUNE_PKGARCH_tune-i586-nlp-32 = "i586-nlp-32"
> -PACKAGE_EXTRA_ARCHS_tune-i586-nlp-32 = "i586-nlp-32"
> 

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

Re: [OE-core] [devtool][PATCH] devtool deploy-target: optionally specify package

[Trevor Woerner]

On Thu, May 31, 2018 at 11:07 PM, Andre McCurdy  wrote:

> On Thu, May 31, 2018 at 7:23 PM, Trevor Woerner 
> wrote:
>
> I wonder whether the default behaviour should just be to not deploy
> files from the -dev package?
>
>
That would certainly be an improvement. But it still wouldn't make sense to
copy over the -staticdev or -doc packages either. Maybe a better default
behaviour would be to not copy over the -dev, -staticdev, -doc, -dbg, and
-locale packages? Or better yet: just copy over the core packages, not any
of the core- packages? I'm guessing bitbake has a list somewhere
of these -somethings?

I wouldn't be surprised if the current behaviour exists simply because ${D}
is already there and ready to go. My tweak extends the behaviour to send
another already-there directory: ${PKGDEST} + .

If we were to go this route (i.e. being more selective about which packages
are sent) do you think this should be the new default behaviour, or should
the existing default behaviour be preserved and a flag used for this tweak?




> >> Are the going to be problems if users want to deploy more than one
> >> package (or switch between a full deploy and a package) and don't
> >> deploy and undeploy in the right order?
> >
> >
> > In my patch I added a --package option to "devtool deploy-target" but
> not to
> > "devtool undeploy-target". devtool keeps track of what files were
> uploaded
> > by creating a per-package list on the target itself (in /.devtool). When
> you
> > undeploy a recipe, it simply looks for this recipe file on the target,
> reads
> > the files listed there, and undeploys each of the files in that list.
> >
> > Therefore, mixing and matching deploys and undeploys amongst recipes
> don't
> > interfere with each other.
> >
> > I checked at the time, but I'm not 100% sure now, but I believe if one
> > deploys two packages from one recipe, the on-target file gets appended.
> But
> > now I'm not 100% sure, so I'll verify this tomorrow (thanks for the
> > reminder). As such, under my scheme, you can deploy recipes and packages
> at
> > will, but then only undeploy the whole kit and caboodle in one go; given
> a
> > recipe name to undeploy, whatever it finds in the on-target record will
> get
> > undeployed.
> >
> > I think any developer will find this reasonable behaviour (but maybe
> not?).
>
> If that's how it works then it seems reasonable to me.
>
>
Unfortunately this morning's investigation shows this is not the case. When
a recipe is deployed to the target, the on-target script looks for evidence
of this recipe having already been deployed. If that is the case, it
undeploys the previous deploy before deploying this deploy. That is very
good behaviour since it catches the cases where the file list might change
between deployments. But with my tweak as-is, if the user deploys two
packages from the same recipe, the first one will be undeployed and only
the second one will remain deployed; this is not reasonable.

Therefore a v2 will be necessary. The question is, which route do I take?
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 1/3] systemd: Fix build with gcc8

[Martin Jansa]

It fails when -O1 or -Os is being used, builds ok with -O0, -O2, -O3.

Checking a bit more shows that it doesn't fail when -ftree-vrp is used,
probably because this check is removed as the documentation for -ftree-vrp
says:

-ftree-vrp
Perform Value Range Propagation on trees. This is similar to the constant
propagation pass, but instead of values, ranges of values are propagated.
This allows the optimizers to remove unnecessary range checks like array
bound checks and null pointer checks. This is enabled by default at -O2 and
higher. Null pointer check elimination is only done if
-fdelete-null-pointer-checks is enabled.


On Fri, Jun 1, 2018 at 4:01 PM Martin Jansa  wrote:

> No change in PACKAGECONFIG, just default nodistro qemux86 with added
> systemd and debug build:
> DISTRO_FEATURES_append = " systemd"
> DEBUG_BUILD = "1"
>
>
> On Thu, May 31, 2018 at 6:17 PM Khem Raj  wrote:
>
>> On Thu, May 31, 2018 at 9:05 AM, Martin Jansa 
>> wrote:
>> > Unlike the previous version you had in your RFT branch (which added
>> > -Wno-error=format-truncation) this doesn't seem to be complete fix.
>> >
>> > In qemux86 build which already includes this change I'm seeing:
>> > ../git/src/basic/time-util.c: In function 'format_timespan':
>> > ../git/src/basic/time-util.c:508:46: error: '%0*llu' directive output
>> > between 1 and 2147483647 bytes may cause result to exceed 'INT_MAX'
>> > [-Werror=format-truncation=]
>> >
>> > "%s"USEC_FMT".%0*"PRI_USEC"%s",
>> >   ^~~~
>> > ../git/src/basic/time-util.c:508:60: note: format string is defined here
>> >
>> > "%s"USEC_FMT".%0*"PRI_USEC"%s",
>> > ../git/src/basic/time-util.c:508:46: note: directive argument in the
>> range
>> > [0, 18446744073709551614]
>> >
>> > "%s"USEC_FMT".%0*"PRI_USEC"%s",
>> >   ^~~~
>> >
>> > And this part doesn't seem to be fixed upstream yet.
>> >
>>
>> Its possible, that default config I build is not using this code. Do
>> you enable/disable some specific packageconfig and what arch are you
>> targetting
>>
>> > Cheers,
>> >
>> > On Mon, May 28, 2018 at 5:58 PM Khem Raj  wrote:
>> >>
>> >> Signed-off-by: Khem Raj 
>> >> ---
>> >>  ...ange-the-default-device-timeout-to-2.patch |   9 +-
>> >>  ...ation-compile-failure-by-typecasting.patch | 173 ++
>> >>  meta/recipes-core/systemd/systemd_237.bb  |   1 +
>> >>  3 files changed, 177 insertions(+), 6 deletions(-)
>> >>  create mode 100644
>> >>
>> meta/recipes-core/systemd/systemd/0034-Fix-format-truncation-compile-failure-by-typecasting.patch
>> >>
>> >> diff --git
>> >>
>> a/meta/recipes-core/systemd/systemd/0001-core-device.c-Change-the-default-device-timeout-to-2.patch
>> >>
>> b/meta/recipes-core/systemd/systemd/0001-core-device.c-Change-the-default-device-timeout-to-2.patch
>> >> index b7b1ea0886..98c83620ff 100644
>> >> ---
>> >>
>> a/meta/recipes-core/systemd/systemd/0001-core-device.c-Change-the-default-device-timeout-to-2.patch
>> >> +++
>> >>
>> b/meta/recipes-core/systemd/systemd/0001-core-device.c-Change-the-default-device-timeout-to-2.patch
>> >> @@ -1,4 +1,4 @@
>> >> -From 9820c165a9e559cf851e3beb60fad2571de4ded2 Mon Sep 17 00:00:00 2001
>> >> +From 7844e070745611a52e355b73e7890f360dd540d0 Mon Sep 17 00:00:00 2001
>> >>  From: Khem Raj 
>> >>  Date: Mon, 14 Dec 2015 04:09:19 +
>> >>  Subject: [PATCH] core/device.c: Change the default device timeout to
>> 240
>> >> sec.
>> >> @@ -16,10 +16,10 @@ Signed-off-by: Khem Raj 
>> >>   1 file changed, 1 insertion(+), 1 deletion(-)
>> >>
>> >>  diff --git a/src/core/device.c b/src/core/device.c
>> >> -index 77601c552..98bf49ba2 100644
>> >> +index a43664d3b..4b16a8aec 100644
>> >>  --- a/src/core/device.c
>> >>  +++ b/src/core/device.c
>> >> -@@ -112,7 +112,7 @@ static void device_init(Unit *u) {
>> >> +@@ -113,7 +113,7 @@ static void device_init(Unit *u) {
>> >>* indefinitely for plugged in devices, something which
>> cannot
>> >>* happen for the other units since their operations time out
>> >>* anyway. */
>> >> @@ -28,6 +28,3 @@ index 77601c552..98bf49ba2 100644
>> >>
>> >>   u->ignore_on_isolate = true;
>> >>   }
>> >> ---
>> >> -2.16.1
>> >> -
>> >> diff --git
>> >>
>> a/meta/recipes-core/systemd/systemd/0034-Fix-format-truncation-compile-failure-by-typecasting.patch
>> >>
>> b/meta/recipes-core/systemd/systemd/0034-Fix-format-truncation-compile-failure-by-typecasting.patch
>> >> new file mode 100644
>> >> index 00..e56061f41b
>> >> --- /dev/null
>> >> +++
>> >>
>> b/meta/recipes-core/systemd/systemd/0034-Fix-format-truncation-compile-failure-by-typecasting.patch
>> >> @@ -0,0 +1,173 @@
>> >> +From c2b3ebe112ebfd9f9e82fb1531ee225c3152ca83 Mon Sep 17 00:00:00 2001
>> >> +From: Patrick Uiterwijk 
>> >> +Date: Thu, 22 Feb 2018 19:41:30 +0100
>> >> +Subject: [PATCH] Fix format-truncation compile failure by typecasting
>> USB
>> >> IDs
>> >> + (#8250)
>> >> +
>> >> +This patch adds 

Re: [OE-core] [PATCH 1/3] systemd: Fix build with gcc8

[Martin Jansa]

No change in PACKAGECONFIG, just default nodistro qemux86 with added
systemd and debug build:
DISTRO_FEATURES_append = " systemd"
DEBUG_BUILD = "1"


On Thu, May 31, 2018 at 6:17 PM Khem Raj  wrote:

> On Thu, May 31, 2018 at 9:05 AM, Martin Jansa 
> wrote:
> > Unlike the previous version you had in your RFT branch (which added
> > -Wno-error=format-truncation) this doesn't seem to be complete fix.
> >
> > In qemux86 build which already includes this change I'm seeing:
> > ../git/src/basic/time-util.c: In function 'format_timespan':
> > ../git/src/basic/time-util.c:508:46: error: '%0*llu' directive output
> > between 1 and 2147483647 bytes may cause result to exceed 'INT_MAX'
> > [-Werror=format-truncation=]
> >
> > "%s"USEC_FMT".%0*"PRI_USEC"%s",
> >   ^~~~
> > ../git/src/basic/time-util.c:508:60: note: format string is defined here
> >
> > "%s"USEC_FMT".%0*"PRI_USEC"%s",
> > ../git/src/basic/time-util.c:508:46: note: directive argument in the
> range
> > [0, 18446744073709551614]
> >
> > "%s"USEC_FMT".%0*"PRI_USEC"%s",
> >   ^~~~
> >
> > And this part doesn't seem to be fixed upstream yet.
> >
>
> Its possible, that default config I build is not using this code. Do
> you enable/disable some specific packageconfig and what arch are you
> targetting
>
> > Cheers,
> >
> > On Mon, May 28, 2018 at 5:58 PM Khem Raj  wrote:
> >>
> >> Signed-off-by: Khem Raj 
> >> ---
> >>  ...ange-the-default-device-timeout-to-2.patch |   9 +-
> >>  ...ation-compile-failure-by-typecasting.patch | 173 ++
> >>  meta/recipes-core/systemd/systemd_237.bb  |   1 +
> >>  3 files changed, 177 insertions(+), 6 deletions(-)
> >>  create mode 100644
> >>
> meta/recipes-core/systemd/systemd/0034-Fix-format-truncation-compile-failure-by-typecasting.patch
> >>
> >> diff --git
> >>
> a/meta/recipes-core/systemd/systemd/0001-core-device.c-Change-the-default-device-timeout-to-2.patch
> >>
> b/meta/recipes-core/systemd/systemd/0001-core-device.c-Change-the-default-device-timeout-to-2.patch
> >> index b7b1ea0886..98c83620ff 100644
> >> ---
> >>
> a/meta/recipes-core/systemd/systemd/0001-core-device.c-Change-the-default-device-timeout-to-2.patch
> >> +++
> >>
> b/meta/recipes-core/systemd/systemd/0001-core-device.c-Change-the-default-device-timeout-to-2.patch
> >> @@ -1,4 +1,4 @@
> >> -From 9820c165a9e559cf851e3beb60fad2571de4ded2 Mon Sep 17 00:00:00 2001
> >> +From 7844e070745611a52e355b73e7890f360dd540d0 Mon Sep 17 00:00:00 2001
> >>  From: Khem Raj 
> >>  Date: Mon, 14 Dec 2015 04:09:19 +
> >>  Subject: [PATCH] core/device.c: Change the default device timeout to
> 240
> >> sec.
> >> @@ -16,10 +16,10 @@ Signed-off-by: Khem Raj 
> >>   1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >>  diff --git a/src/core/device.c b/src/core/device.c
> >> -index 77601c552..98bf49ba2 100644
> >> +index a43664d3b..4b16a8aec 100644
> >>  --- a/src/core/device.c
> >>  +++ b/src/core/device.c
> >> -@@ -112,7 +112,7 @@ static void device_init(Unit *u) {
> >> +@@ -113,7 +113,7 @@ static void device_init(Unit *u) {
> >>* indefinitely for plugged in devices, something which cannot
> >>* happen for the other units since their operations time out
> >>* anyway. */
> >> @@ -28,6 +28,3 @@ index 77601c552..98bf49ba2 100644
> >>
> >>   u->ignore_on_isolate = true;
> >>   }
> >> ---
> >> -2.16.1
> >> -
> >> diff --git
> >>
> a/meta/recipes-core/systemd/systemd/0034-Fix-format-truncation-compile-failure-by-typecasting.patch
> >>
> b/meta/recipes-core/systemd/systemd/0034-Fix-format-truncation-compile-failure-by-typecasting.patch
> >> new file mode 100644
> >> index 00..e56061f41b
> >> --- /dev/null
> >> +++
> >>
> b/meta/recipes-core/systemd/systemd/0034-Fix-format-truncation-compile-failure-by-typecasting.patch
> >> @@ -0,0 +1,173 @@
> >> +From c2b3ebe112ebfd9f9e82fb1531ee225c3152ca83 Mon Sep 17 00:00:00 2001
> >> +From: Patrick Uiterwijk 
> >> +Date: Thu, 22 Feb 2018 19:41:30 +0100
> >> +Subject: [PATCH] Fix format-truncation compile failure by typecasting
> USB
> >> IDs
> >> + (#8250)
> >> +
> >> +This patch adds safe_atoux16 for parsing an unsigned hexadecimal 16bit
> >> int, and
> >> +uses that for parsing USB device and vendor IDs.
> >> +
> >> +This fixes a compile error with gcc-8 because while we know that USB
> IDs
> >> are 2 bytes,
> >> +the compiler does not know that.
> >> +
> >> +../src/udev/udev-builtin-hwdb.c:80:38: error: '%04X' directive output
> may
> >> be
> >> +truncated writing between 4 and 8 bytes into a region of size between 2
> >> and 6
> >> +[-Werror=format-truncation=]
> >> +
> >> +Upstream-Status: Backport
> >> [
> https://github.com/systemd/systemd/commit/5547c12503a683290eaed47954ffcfb2d1bc03cd
> ]
> >> +
> >> +Signed-off-by: Adam Williamson 
> >> +Signed-off-by: Patrick Uiterwijk 
> >> +---
> >> + src/basic/parse-util.c   | 24 ++
> >> + 

[OE-core] [master][PATCH 3/4] qemu: add PACKAGECONFIG for virglrenderer, usb-redir and spice

[Martin Jansa]

* drop "fdt sdl" listed twice in PACKAGECONFIG
* keep all 3 disabled by default
* spice, usbredir recipes will eventually be in meta-networking layer
  (you can use jansa/spice branch from meta-openembedded-contrib repository)
* virglrenderer recipe will eventually be in oe-core layer
  (you can use jansa/qemu branch from openembedded-core-contrib repository)

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

diff --git a/meta/recipes-devtools/qemu/qemu.inc 
b/meta/recipes-devtools/qemu/qemu.inc
index dc73df813a..773ac81a6e 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -74,10 +74,9 @@ do_install_append() {
 # END of qemu-mips workaround
 
 PACKAGECONFIG ??= " \
-   fdt sdl \
-   fdt sdl kvm \
-   ${@bb.utils.filter('DISTRO_FEATURES', 'alsa xen', d)} \
-   "
+fdt sdl kvm \
+${@bb.utils.filter('DISTRO_FEATURES', 'alsa xen', d)} \
+"
 PACKAGECONFIG_class-native ??= "fdt alsa kvm"
 PACKAGECONFIG_class-nativesdk ??= "fdt sdl kvm"
 
@@ -115,5 +114,10 @@ PACKAGECONFIG[bzip2] = 
"--enable-bzip2,--disable-bzip2,bzip2"
 PACKAGECONFIG[bluez] = "--enable-bluez,--disable-bluez,${BLUEZ}"
 PACKAGECONFIG[libiscsi] = "--enable-libiscsi,--disable-libiscsi"
 PACKAGECONFIG[kvm] = "--enable-kvm,--disable-kvm"
+PACKAGECONFIG[virglrenderer] = 
"--enable-virglrenderer,--disable-virglrenderer,virglrenderer"
+# spice will be in meta-networking layer
+PACKAGECONFIG[spice] = "--enable-spice,--disable-spice,spice"
+# usbredir will be in meta-networking layer
+PACKAGECONFIG[usb-redir] = "--enable-usb-redir,--disable-usb-redir,usbredir"
 
 INSANE_SKIP_${PN} = "arch"
-- 
2.17.0

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

[OE-core] [master][PATCH 4/4] qemu: use sdl2 instead of sdl1

[Martin Jansa]

* sdl1 since qemu-2.12.0 depends on x11 in DISTRO_FEATURES, switch to sdl2

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

diff --git a/meta/recipes-devtools/qemu/qemu.inc 
b/meta/recipes-devtools/qemu/qemu.inc
index 773ac81a6e..faaea781cd 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -87,7 +87,7 @@ PACKAGECONFIG_class-native_remove = "${@'kvm' if not 
os.path.exists('/usr/includ
 PACKAGECONFIG_remove_darwin = "kvm"
 PACKAGECONFIG_remove_mingw32 = "kvm"
 
-PACKAGECONFIG[sdl] = "--enable-sdl,--disable-sdl,libsdl"
+PACKAGECONFIG[sdl] = "--enable-sdl --with-sdlabi=2.0,--disable-sdl,libsdl2"
 PACKAGECONFIG[virtfs] = "--enable-virtfs --enable-attr,--disable-virtfs,libcap 
attr,"
 PACKAGECONFIG[aio] = "--enable-linux-aio,--disable-linux-aio,libaio,"
 PACKAGECONFIG[xfs] = "--enable-xfsctl,--disable-xfsctl,xfsprogs,"
-- 
2.17.0

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

[OE-core] [master][PATCH 2/4] qemu: upgrade to 2.12.0

[Martin Jansa]

From: Martin Jansa 

* drop patches which are now included upstream
* revert "linux-user: fix mmap/munmap/mprotect/mremap/shma" which is
  causing
  0010-linux-user-Fix-webkitgtk-hangs-on-32-bit-x86-target.patch
  to stop working and qemu-i386 hanging during gobject-introspection in
  webkitgtk when building for qemux86 with musl

Signed-off-by: Martin Jansa 
Signed-off-by: Ross Burton 
---
 meta/conf/distro/include/tcmode-default.inc   |   2 +-
 ...-allow-user-to-disable-pointer-grabs.patch |  23 +--
 ...emu-Add-missing-wacom-HID-descriptor.patch |   6 +-
 ...test-which-runs-all-unit-test-cases-.patch |   6 +-
 ...n-environment-space-to-boot-loader-q.patch |   6 +-
 .../qemu/0005-qemu-disable-Valgrind.patch |   6 +-
 ...-searched-during-user-mode-emulation.patch |   4 +-
 ...ld.bfd-fix-cflags-and-set-some-envir.patch |   8 +-
 ...-connect-socket-to-a-spawned-command.patch |  60 
 .../0009-apic-fixup-fallthrough-to-PIC.patch  |   6 +-
 ...webkitgtk-hangs-on-32-bit-x86-target.patch |   6 +-
 ...r-fix-mmap-munmap-mprotect-mremap-sh.patch | 141 ++
 .../qemu/0011-memfd-fix-configure-test.patch  |  54 ---
 ...4-treat-DISAS_UPDATE-as-variant-of-D.patch |  64 
 ...-libcap-header-issue-on-some-distro.patch} |   4 +-
 ...messages-when-qemi_cpu_kick_thread-.patch} |  10 +-
 ...2Queue-pointers-in-post_load-routine.patch |  60 
 .../qemu/{qemu_2.11.1.bb => qemu_2.12.0.bb}   |  12 +-
 18 files changed, 220 insertions(+), 258 deletions(-)
 create mode 100644 
meta/recipes-devtools/qemu/qemu/0011-Revert-linux-user-fix-mmap-munmap-mprotect-mremap-sh.patch
 delete mode 100644 
meta/recipes-devtools/qemu/qemu/0011-memfd-fix-configure-test.patch
 delete mode 100644 
meta/recipes-devtools/qemu/qemu/0012-arm-translate-a64-treat-DISAS_UPDATE-as-variant-of-D.patch
 rename 
meta/recipes-devtools/qemu/qemu/{0014-fix-libcap-header-issue-on-some-distro.patch
 => 0012-fix-libcap-header-issue-on-some-distro.patch} (96%)
 rename 
meta/recipes-devtools/qemu/qemu/{0015-cpus.c-Add-error-messages-when-qemi_cpu_kick_thread-.patch
 => 0013-cpus.c-Add-error-messages-when-qemi_cpu_kick_thread-.patch} (87%)
 delete mode 100644 
meta/recipes-devtools/qemu/qemu/0013-ps2-check-PS2Queue-pointers-in-post_load-routine.patch
 rename meta/recipes-devtools/qemu/{qemu_2.11.1.bb => qemu_2.12.0.bb} (80%)

diff --git a/meta/conf/distro/include/tcmode-default.inc 
b/meta/conf/distro/include/tcmode-default.inc
index 4b58df0459..48383d4ac0 100644
--- a/meta/conf/distro/include/tcmode-default.inc
+++ b/meta/conf/distro/include/tcmode-default.inc
@@ -28,7 +28,7 @@ BINUVERSION ?= "2.30%"
 GDBVERSION ?= "8.1%"
 GLIBCVERSION ?= "2.27%"
 LINUXLIBCVERSION ?= "4.15%"
-QEMUVERSION ?= "2.11%"
+QEMUVERSION ?= "2.12%"
 
 PREFERRED_VERSION_gcc ?= "${GCCVERSION}"
 PREFERRED_VERSION_gcc-cross-${TARGET_ARCH} ?= "${GCCVERSION}"
diff --git 
a/meta/recipes-devtools/qemu/qemu/0001-sdl.c-allow-user-to-disable-pointer-grabs.patch
 
b/meta/recipes-devtools/qemu/qemu/0001-sdl.c-allow-user-to-disable-pointer-grabs.patch
index add5d8b02f..b8a9206fee 100644
--- 
a/meta/recipes-devtools/qemu/qemu/0001-sdl.c-allow-user-to-disable-pointer-grabs.patch
+++ 
b/meta/recipes-devtools/qemu/qemu/0001-sdl.c-allow-user-to-disable-pointer-grabs.patch
@@ -1,4 +1,4 @@
-From 273e1af49d3e0a58bb9464369deb2652f243e649 Mon Sep 17 00:00:00 2001
+From 18fb45c34a473c4ba247bb82bcea94b7c3ba493a Mon Sep 17 00:00:00 2001
 From: Ross Burton 
 Date: Wed, 18 Sep 2013 14:04:54 +0100
 Subject: [PATCH] sdl.c: allow user to disable pointer grabs
@@ -22,25 +22,26 @@ Upstream-Status: Pending
 Signed-off-by: Ross Burton 
 Signed-off-by: Eric Bénard 
 ---
- ui/sdl.c | 12 ++--
- 1 file changed, 10 insertions(+), 2 deletions(-)
+ ui/sdl.c | 13 +++--
+ 1 file changed, 11 insertions(+), 2 deletions(-)
 
 diff --git a/ui/sdl.c b/ui/sdl.c
-index 7b71a9a..29ce1b9 100644
+index a5fd503c25..ab8d1b1eb1 100644
 --- a/ui/sdl.c
 +++ b/ui/sdl.c
-@@ -63,6 +63,10 @@ static SDL_PixelFormat host_format;
- static int scaling_active = 0;
- static Notifier mouse_mode_notifier;
- static int idle_counter;
+@@ -68,6 +68,11 @@ static int idle_counter;
+ static const guint16 *keycode_map;
+ static size_t keycode_maplen;
+ 
 +#ifndef True
 +#define True 1
 +#endif
 +static doing_grabs = True;
- 
++
  #define SDL_REFRESH_INTERVAL_BUSY 10
  #define SDL_MAX_IDLE_COUNT (2 * GUI_REFRESH_INTERVAL_DEFAULT \
-@@ -431,14 +435,16 @@ static void sdl_grab_start(void)
+ / SDL_REFRESH_INTERVAL_BUSY + 1)
+@@ -398,14 +403,16 @@ static void sdl_grab_start(void)
  }
  } else
  sdl_hide_cursor();
@@ -59,7 +60,7 @@ index 7b71a9a..29ce1b9 100644
  gui_grab = 0;
  sdl_show_cursor();
  sdl_update_caption();
-@@ -986,6 +992,8 @@ void sdl_display_init(DisplayState *ds, int full_screen, 
int no_frame)
+@@ -945,6 +952,8 @@ static void sdl1_display_init(DisplayState *ds, 
DisplayOptions *o)
   * This requires SDL >= 1.2.14. */
  

[OE-core] [master][PATCH 1/4] qemu: refresh patches with devtool and make them applicable with git

[Martin Jansa]

From: Martin Jansa 

Signed-off-by: Martin Jansa 
Signed-off-by: Ross Burton 
---
 ...allow-user-to-disable-pointer-grabs.patch} | 25 +++---
 ...mu-Add-missing-wacom-HID-descriptor.patch} | 24 -
 ...est-which-runs-all-unit-test-cases-.patch} | 12 ---
 ...-environment-space-to-boot-loader-q.patch} | 17 +-
 ...patch => 0005-qemu-disable-Valgrind.patch} | 18 --
 ...searched-during-user-mode-emulation.patch} | 34 ---
 ...d.bfd-fix-cflags-and-set-some-envir.patch} | 12 ++-
 ...connect-socket-to-a-spawned-command.patch} | 33 --
 ... 0009-apic-fixup-fallthrough-to-PIC.patch} | 14 
 ...ebkitgtk-hangs-on-32-bit-x86-target.patch} |  9 ++---
 ...ch => 0011-memfd-fix-configure-test.patch} | 15 
 ...-treat-DISAS_UPDATE-as-variant-of-D.patch} |  9 ++---
 ...Queue-pointers-in-post_load-routine.patch} |  5 +--
 ...-libcap-header-issue-on-some-distro.patch} | 15 
 ...messages-when-qemi_cpu_kick_thread-.patch} | 11 +++---
 meta/recipes-devtools/qemu/qemu_2.11.1.bb | 31 -
 16 files changed, 156 insertions(+), 128 deletions(-)
 rename meta/recipes-devtools/qemu/qemu/{disable-grabs.patch => 
0001-sdl.c-allow-user-to-disable-pointer-grabs.patch} (86%)
 rename meta/recipes-devtools/qemu/qemu/{wacom.patch => 
0002-qemu-Add-missing-wacom-HID-descriptor.patch} (87%)
 rename meta/recipes-devtools/qemu/qemu/{add-ptest-in-makefile-v10.patch => 
0003-Add-subpackage-ptest-which-runs-all-unit-test-cases-.patch} (65%)
 rename meta/recipes-devtools/qemu/qemu/{qemu-enlarge-env-entry-size.patch => 
0004-qemu-Add-addition-environment-space-to-boot-loader-q.patch} (66%)
 rename meta/recipes-devtools/qemu/qemu/{no-valgrind.patch => 
0005-qemu-disable-Valgrind.patch} (47%)
 rename meta/recipes-devtools/qemu/qemu/{pathlimit.patch => 
0006-qemu-Limit-paths-searched-during-user-mode-emulation.patch} (78%)
 rename meta/recipes-devtools/qemu/qemu/{qemu-2.5.0-cflags.patch => 
0007-qemu-native-set-ld.bfd-fix-cflags-and-set-some-envir.patch} (51%)
 rename 
meta/recipes-devtools/qemu/qemu/{chardev-connect-socket-to-a-spawned-command.patch
 => 0008-chardev-connect-socket-to-a-spawned-command.patch} (92%)
 rename meta/recipes-devtools/qemu/qemu/{apic-fixup-fallthrough-to-PIC.patch => 
0009-apic-fixup-fallthrough-to-PIC.patch} (80%)
 rename 
meta/recipes-devtools/qemu/qemu/{linux-user-Fix-webkitgtk-hangs-on-32-bit-x86-target.patch
 => 0010-linux-user-Fix-webkitgtk-hangs-on-32-bit-x86-target.patch} (87%)
 rename meta/recipes-devtools/qemu/qemu/{memfd.patch => 
0011-memfd-fix-configure-test.patch} (88%)
 rename 
meta/recipes-devtools/qemu/qemu/{0001-arm-translate-a64-treat-DISAS_UPDATE-as-variant-of-D.patch
 => 0012-arm-translate-a64-treat-DISAS_UPDATE-as-variant-of-D.patch} (93%)
 rename 
meta/recipes-devtools/qemu/qemu/{check-PS2Queue-pointers-in-post_load-routine.patch
 => 0013-ps2-check-PS2Queue-pointers-in-post_load-routine.patch} (96%)
 rename 
meta/recipes-devtools/qemu/qemu/{fix-libcap-header-issue-on-some-distro.patch 
=> 0014-fix-libcap-header-issue-on-some-distro.patch} (88%)
 rename 
meta/recipes-devtools/qemu/qemu/{cpus.c-qemu_cpu_kick_thread_debugging.patch => 
0015-cpus.c-Add-error-messages-when-qemi_cpu_kick_thread-.patch} (88%)

diff --git a/meta/recipes-devtools/qemu/qemu/disable-grabs.patch 
b/meta/recipes-devtools/qemu/qemu/0001-sdl.c-allow-user-to-disable-pointer-grabs.patch
similarity index 86%
rename from meta/recipes-devtools/qemu/qemu/disable-grabs.patch
rename to 
meta/recipes-devtools/qemu/qemu/0001-sdl.c-allow-user-to-disable-pointer-grabs.patch
index 77117890f4..add5d8b02f 100644
--- a/meta/recipes-devtools/qemu/qemu/disable-grabs.patch
+++ 
b/meta/recipes-devtools/qemu/qemu/0001-sdl.c-allow-user-to-disable-pointer-grabs.patch
@@ -1,3 +1,11 @@
+From 273e1af49d3e0a58bb9464369deb2652f243e649 Mon Sep 17 00:00:00 2001
+From: Ross Burton 
+Date: Wed, 18 Sep 2013 14:04:54 +0100
+Subject: [PATCH] sdl.c: allow user to disable pointer grabs
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
 When the pointer enters the Qemu window it calls SDL_WM_GrabInput, which calls
 XGrabPointer in a busyloop until it returns GrabSuccess. However if there's 
already
 a pointer grab (screen is locked, a menu is open) then qemu will hang until the
@@ -11,23 +19,16 @@ them in a conditional that can be set by the autobuilder 
environment, preserving
 the current grabbing behaviour for everyone else.
 
 Upstream-Status: Pending
-Signed-off-by: Ross Burton 
-
-From 4b1988ecb01a178269ec0513a75f2ec620c7ef6a Mon Sep 17 00:00:00 2001
-From: Ross Burton 
-Date: Wed, 18 Sep 2013 14:04:54 +0100
-Subject: [PATCH] sdl.c: allow user to disable pointer grabs
-
 Signed-off-by: Ross Burton 
 Signed-off-by: Eric Bénard 
 ---
  ui/sdl.c | 12 ++--
  1 file changed, 10 insertions(+), 2 deletions(-)
 
-Index: qemu-2.11.1/ui/sdl.c
-===
 

[OE-core] [master][PATCH 0/4] QEmu upgrade to 2.12.0 and switch to libsdl2

[Martin Jansa]

The following changes since commit 760103cdaed3e820888d8984ec0b76cfc831d534:

  nativesdk-rpm: Add wrappers for nativesdk support (2018-05-29 21:06:03 +0100)

are available in the Git repository at:

  git://git.openembedded.org/openembedded-core-contrib jansa/thud
  http://cgit.openembedded.org/openembedded-core-contrib/log/?h=jansa/thud

Martin Jansa (4):
  qemu: refresh patches with devtool and make them applicable with git
  qemu: upgrade to 2.12.0
  qemu: add PACKAGECONFIG for virglrenderer, usb-redir and spice
  qemu: use sdl2 instead of sdl1

 meta/conf/distro/include/tcmode-default.inc   |   2 +-
 meta/recipes-devtools/qemu/qemu.inc   |  14 +-
 ...4-treat-DISAS_UPDATE-as-variant-of-D.patch |  67 -
 ...allow-user-to-disable-pointer-grabs.patch} |  42 +++---
 ...mu-Add-missing-wacom-HID-descriptor.patch} |  24 ++-
 ...est-which-runs-all-unit-test-cases-.patch} |  12 +-
 ...-environment-space-to-boot-loader-q.patch} |  17 ++-
 ...patch => 0005-qemu-disable-Valgrind.patch} |  18 ++-
 ...searched-during-user-mode-emulation.patch} |  34 +++--
 ...d.bfd-fix-cflags-and-set-some-envir.patch} |  14 +-
 ...connect-socket-to-a-spawned-command.patch} |  51 +++
 ... 0009-apic-fixup-fallthrough-to-PIC.patch} |  14 +-
 ...ebkitgtk-hangs-on-32-bit-x86-target.patch} |   9 +-
 ...r-fix-mmap-munmap-mprotect-mremap-sh.patch | 141 ++
 ...-libcap-header-issue-on-some-distro.patch} |  15 +-
 ...messages-when-qemi_cpu_kick_thread-.patch} |  13 +-
 ...2Queue-pointers-in-post_load-routine.patch |  63 
 meta/recipes-devtools/qemu/qemu/memfd.patch   |  57 ---
 .../qemu/{qemu_2.11.1.bb => qemu_2.12.0.bb}   |  33 ++--
 19 files changed, 317 insertions(+), 323 deletions(-)
 delete mode 100644 
meta/recipes-devtools/qemu/qemu/0001-arm-translate-a64-treat-DISAS_UPDATE-as-variant-of-D.patch
 rename meta/recipes-devtools/qemu/qemu/{disable-grabs.patch => 
0001-sdl.c-allow-user-to-disable-pointer-grabs.patch} (74%)
 rename meta/recipes-devtools/qemu/qemu/{wacom.patch => 
0002-qemu-Add-missing-wacom-HID-descriptor.patch} (87%)
 rename meta/recipes-devtools/qemu/qemu/{add-ptest-in-makefile-v10.patch => 
0003-Add-subpackage-ptest-which-runs-all-unit-test-cases-.patch} (65%)
 rename meta/recipes-devtools/qemu/qemu/{qemu-enlarge-env-entry-size.patch => 
0004-qemu-Add-addition-environment-space-to-boot-loader-q.patch} (66%)
 rename meta/recipes-devtools/qemu/qemu/{no-valgrind.patch => 
0005-qemu-disable-Valgrind.patch} (47%)
 rename meta/recipes-devtools/qemu/qemu/{pathlimit.patch => 
0006-qemu-Limit-paths-searched-during-user-mode-emulation.patch} (78%)
 rename meta/recipes-devtools/qemu/qemu/{qemu-2.5.0-cflags.patch => 
0007-qemu-native-set-ld.bfd-fix-cflags-and-set-some-envir.patch} (45%)
 rename 
meta/recipes-devtools/qemu/qemu/{chardev-connect-socket-to-a-spawned-command.patch
 => 0008-chardev-connect-socket-to-a-spawned-command.patch} (87%)
 rename meta/recipes-devtools/qemu/qemu/{apic-fixup-fallthrough-to-PIC.patch => 
0009-apic-fixup-fallthrough-to-PIC.patch} (80%)
 rename 
meta/recipes-devtools/qemu/qemu/{linux-user-Fix-webkitgtk-hangs-on-32-bit-x86-target.patch
 => 0010-linux-user-Fix-webkitgtk-hangs-on-32-bit-x86-target.patch} (87%)
 create mode 100644 
meta/recipes-devtools/qemu/qemu/0011-Revert-linux-user-fix-mmap-munmap-mprotect-mremap-sh.patch
 rename 
meta/recipes-devtools/qemu/qemu/{fix-libcap-header-issue-on-some-distro.patch 
=> 0012-fix-libcap-header-issue-on-some-distro.patch} (88%)
 rename 
meta/recipes-devtools/qemu/qemu/{cpus.c-qemu_cpu_kick_thread_debugging.patch => 
0013-cpus.c-Add-error-messages-when-qemi_cpu_kick_thread-.patch} (87%)
 delete mode 100644 
meta/recipes-devtools/qemu/qemu/check-PS2Queue-pointers-in-post_load-routine.patch
 delete mode 100644 meta/recipes-devtools/qemu/qemu/memfd.patch
 rename meta/recipes-devtools/qemu/{qemu_2.11.1.bb => qemu_2.12.0.bb} (51%)

-- 
2.17.0

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

Re: [OE-core] [oe][meta-oe][PATCH 1/3] Mosquitto add a mosquitto conf and logging to the default mosquitto recipe

[nick83ola]

Thanks
Sorry for that I will submit everything to the right mailing list :-)

Nick

On 25 May 2018 at 20:19, Randy MacLeod  wrote:
> On 05/25/2018 10:14 AM, nick83ola wrote:
>>
>> The openembedded recipe for mosquitto doesn't provide a default
>> configuration file.
>>
>> Also it install a bunch of examples.
>>
>> This series of patches provide a "default" configuration file and setup
>> logging.
>
>
> The mosquitto recipe is part of meta-openembedded:
> http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-connectivity/mosquitto/mosquitto_1.4.14.bb?h=master
>
> so send a patch to:
>   openembedded-de...@lists.openembedded.org
>
> Also, patches in email attachments are not the right format, see:
>https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
>
>
> Thanks for working on the patch and good luck,
>
> ../Randy
>
>>
>>
>> Cheers
>>
>> Nicola Lunghi
>>
>>
>>
>>
>
>
> --
> # 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 v2] core: fix /sbin/nologin path

[Nicola Lunghi]

In some yocto recipes the /sbin/nologin path is incorrectly set to
/bin/nologin. set it to the correct path ${base_sbindir}/nologin

Signed-off-by: Nicola Lunghi 
---
 meta-selftest/files/static-passwd| 20 ++--
 meta/classes/rootfs-postcommands.bbclass |  4 ++--
 meta/recipes-core/systemd/systemd_237.bb | 19 +++
 3 files changed, 23 insertions(+), 20 deletions(-)

diff --git a/meta-selftest/files/static-passwd 
b/meta-selftest/files/static-passwd
index 412f85d469..fe1f3247d4 100644
--- a/meta-selftest/files/static-passwd
+++ b/meta-selftest/files/static-passwd
@@ -1,11 +1,11 @@
 messagebus:x:500:500::/var/lib/dbus:/bin/false
-systemd-bus-proxy:x:501:501::/:/bin/nologin
-systemd-network:x:502:502::/:/bin/nologin
-systemd-resolve:x:503:503::/:/bin/nologin
-systemd-timesync:x:504:504::/:/bin/nologin
-polkitd:x:505:505::/:/bin/nologin
-avahi:x:509:509::/:/bin/nologin
-avahi-autoipd:x:510:510::/:/bin/nologin
-rpc:x:511:511::/:/bin/nologin
-distcc:x:512:nogroup::/:/bin/nologin
-rpcuser:x:513:513::/var/lib/nfs:/bin/nologin
+systemd-bus-proxy:x:501:501::/:/sbin/nologin
+systemd-network:x:502:502::/:/sbin/nologin
+systemd-resolve:x:503:503::/:/sbin/nologin
+systemd-timesync:x:504:504::/:/sbin/nologin
+polkitd:x:505:505::/:/sbin/nologin
+avahi:x:509:509::/:/sbin/nologin
+avahi-autoipd:x:510:510::/:/sbin/nologin
+rpc:x:511:511::/:/sbin/nologin
+distcc:x:512:nogroup::/:/sbin/nologin
+rpcuser:x:513:513::/var/lib/nfs:/sbin/nologin
diff --git a/meta/classes/rootfs-postcommands.bbclass 
b/meta/classes/rootfs-postcommands.bbclass
index a4e627fef8..31f630af81 100644
--- a/meta/classes/rootfs-postcommands.bbclass
+++ b/meta/classes/rootfs-postcommands.bbclass
@@ -63,7 +63,7 @@ systemd_create_users () {
[ -e $conffile ] || continue
grep -v "^#" $conffile | sed -e '/^$/d' | while read type name 
id comment; do
if [ "$type" = "u" ]; then
-   useradd_params="--shell /sbin/nologin"
+   useradd_params="--shell ${base_sbindir}/nologin"
[ "$id" != "-" ] && useradd_params="$useradd_params 
--uid $id"
[ "$comment" != "-" ] && 
useradd_params="$useradd_params --comment $comment"
useradd_params="$useradd_params --system $name"
@@ -79,7 +79,7 @@ systemd_create_users () {
eval groupadd --root ${IMAGE_ROOTFS} --system 
$group
fi
if [ ! `grep -q "^${name}:" 
${IMAGE_ROOTFS}${sysconfdir}/passwd` ]; then
-   eval useradd --root ${IMAGE_ROOTFS} --shell 
/sbin/nologin --system $name
+   eval useradd --root ${IMAGE_ROOTFS} --shell 
${base_sbindir}/nologin --system $name
fi
eval usermod --root ${IMAGE_ROOTFS} -a -G $group $name
fi
diff --git a/meta/recipes-core/systemd/systemd_237.bb 
b/meta/recipes-core/systemd/systemd_237.bb
index 7ef42b2eae..b55614158d 100644
--- a/meta/recipes-core/systemd/systemd_237.bb
+++ b/meta/recipes-core/systemd/systemd_237.bb
@@ -300,16 +300,19 @@ SYSTEMD_PACKAGES = "${@bb.utils.contains('PACKAGECONFIG', 
'binfmt', '${PN}-binfm
 SYSTEMD_SERVICE_${PN}-binfmt = "systemd-binfmt.service"
 
 USERADD_PACKAGES = "${PN} ${PN}-extra-utils"
-USERADD_PARAM_${PN} += "${@bb.utils.contains('PACKAGECONFIG', 'microhttpd', 
'--system -d / -M --shell /bin/nologin systemd-journal-gateway;', '', d)}"
-USERADD_PARAM_${PN} += "${@bb.utils.contains('PACKAGECONFIG', 'microhttpd', 
'--system -d / -M --shell /bin/nologin systemd-journal-remote;', '', d)}"
-USERADD_PARAM_${PN} += "${@bb.utils.contains('PACKAGECONFIG', 
'journal-upload', '--system -d / -M --shell /bin/nologin 
systemd-journal-upload;', '', d)}"
-USERADD_PARAM_${PN} += "${@bb.utils.contains('PACKAGECONFIG', 'timesyncd', 
'--system -d / -M --shell /bin/nologin systemd-timesync;', '', d)}"
-USERADD_PARAM_${PN} += "${@bb.utils.contains('PACKAGECONFIG', 'networkd', 
'--system -d / -M --shell /bin/nologin systemd-network;', '', d)}"
-USERADD_PARAM_${PN} += "${@bb.utils.contains('PACKAGECONFIG', 'coredump', 
'--system -d / -M --shell /bin/nologin systemd-coredump;', '', d)}"
-USERADD_PARAM_${PN} += "${@bb.utils.contains('PACKAGECONFIG', 'resolved', 
'--system -d / -M --shell /bin/nologin systemd-resolve;', '', d)}"
+
+base_useradd_params = "--system -d / -M --shell ${base_sbindir}/nologin"
+
+USERADD_PARAM_${PN} += "${@bb.utils.contains('PACKAGECONFIG', 'microhttpd', 
'${base_useradd_params} systemd-journal-gateway;', '', d)}"
+USERADD_PARAM_${PN} += "${@bb.utils.contains('PACKAGECONFIG', 'microhttpd', 
'${base_useradd_params} systemd-journal-remote;', '', d)}"
+USERADD_PARAM_${PN} += "${@bb.utils.contains('PACKAGECONFIG', 
'journal-upload', '${base_useradd_params} systemd-journal-upload;', '', d)}"
+USERADD_PARAM_${PN} += "${@bb.utils.contains('PACKAGECONFIG', 'timesyncd', 

Re: [OE-core] [PATCH 2/3] qemu: upgrade to 2.12.0

[Martin Jansa]

Replaying the end of bisect got me a bit elsewhere:

git bisect start
# good: [9f750794985d7386f088da941c76b73880b2b6c4] sev/i386: add
sev_get_capabilities()
git bisect good 9f750794985d7386f088da941c76b73880b2b6c4
# bad: [91c60f124e682a78c9a2ef951e8e58ebab6441d0] target/ppc: fix tlbsync
to check privilege level depending on GTSE
git bisect bad 91c60f124e682a78c9a2ef951e8e58ebab6441d0
# bad: [a57946ff2acb9c0d95c9f127914540586b0b8c21] Merge remote-tracking
branch 'remotes/awilliam/tags/vfio-update-20180313.0' into staging
git bisect bad a57946ff2acb9c0d95c9f127914540586b0b8c21
# good: [5bdd374347b873ab59b356a284494a8bc1664008] Merge remote-tracking
branch 'remotes/bonzini/tags/for-upstream-sev' into staging
git bisect good 5bdd374347b873ab59b356a284494a8bc1664008
# bad: [55901900ec69d6fd6f332003d8ab81b2f8a38529] Merge remote-tracking
branch 'remotes/vivier2/tags/linux-user-for-2.12-pull-request' into staging
git bisect bad 55901900ec69d6fd6f332003d8ab81b2f8a38529
# bad: [d4090306c8079ca3df426f82c493314c3537064e] qemu-binfmt-conf.sh: add
qemu-xtensa
git bisect bad d4090306c8079ca3df426f82c493314c3537064e
# good: [d4247ec2d79ef2477cb886fa688706b068119736] linux-user: Support
f_flags in statfs when available.
git bisect good d4247ec2d79ef2477cb886fa688706b068119736
# bad: [3c5f6a5f888729f9fbc64211298f7c3e2fb42b64] linux-user: fix assertion
in shmdt
git bisect bad 3c5f6a5f888729f9fbc64211298f7c3e2fb42b64
# bad: [ebf9a3630c911d0cfc9c20f7cafe9ba4f88cf583] linux-user: fix
mmap/munmap/mprotect/mremap/shmat
git bisect bad ebf9a3630c911d0cfc9c20f7cafe9ba4f88cf583
# first bad commit: [ebf9a3630c911d0cfc9c20f7cafe9ba4f88cf583] linux-user:
fix mmap/munmap/mprotect/mremap/shmat

And this time reverting ebf9a3630c911d0cfc9c20f7cafe9ba4f88cf583 worked for
me. Sending v2 in few minutes for Ross to re-test it on AB.

On Fri, Jun 1, 2018 at 8:37 AM Martin Jansa  wrote:

> Yesterday I've tried to replay the end of the bisect and surprisingly I
> wasn't seeing the hang with d4247ec2d79ef2477cb886fa688706b068119736.
>
> With 2nd bad d4090306c8079ca3df426f82c493314c3537064e it hangs again.
>
> So either I didn't wait long enough for qemu-i386 to finish (I mark it as
> bad after it spends > 10mins inside qemu-i386 or the hang doesn't happen
> reliably even with "bad" revision of qemu.
>
> The revisions I'm trying are here:
>
> http://git.openembedded.org/openembedded-core-contrib/log/?h=jansa/qemu-hang
>
> On Fri, Jun 1, 2018 at 2:01 AM Alistair Francis 
> wrote:
>
>> On Thu, May 31, 2018 at 8:41 AM, Martin Jansa 
>> wrote:
>> > I've finished the bisect today:
>> >
>> > qemu$ git bisect log
>> > git bisect start
>> > # good: [9f750794985d7386f088da941c76b73880b2b6c4] sev/i386: add
>> > sev_get_capabilities()
>> > git bisect good 9f750794985d7386f088da941c76b73880b2b6c4
>> > # bad: [91c60f124e682a78c9a2ef951e8e58ebab6441d0] target/ppc: fix
>> tlbsync to
>> > check privilege level depending on GTSE
>> > git bisect bad 91c60f124e682a78c9a2ef951e8e58ebab6441d0
>> > # bad: [a57946ff2acb9c0d95c9f127914540586b0b8c21] Merge remote-tracking
>> > branch 'remotes/awilliam/tags/vfio-update-20180313.0' into staging
>> > git bisect bad a57946ff2acb9c0d95c9f127914540586b0b8c21
>> > # good: [5bdd374347b873ab59b356a284494a8bc1664008] Merge remote-tracking
>> > branch 'remotes/bonzini/tags/for-upstream-sev' into staging
>> > git bisect good 5bdd374347b873ab59b356a284494a8bc1664008
>> > # bad: [55901900ec69d6fd6f332003d8ab81b2f8a38529] Merge remote-tracking
>> > branch 'remotes/vivier2/tags/linux-user-for-2.12-pull-request' into
>> staging
>> > git bisect bad 55901900ec69d6fd6f332003d8ab81b2f8a38529
>> > # bad: [d4090306c8079ca3df426f82c493314c3537064e] qemu-binfmt-conf.sh:
>> add
>> > qemu-xtensa
>> > git bisect bad d4090306c8079ca3df426f82c493314c3537064e
>> > # bad: [d4247ec2d79ef2477cb886fa688706b068119736] linux-user: Support
>> > f_flags in statfs when available.
>> > git bisect bad d4247ec2d79ef2477cb886fa688706b068119736
>> > # good: [f8b985d65cf67004483816d5afcb7bf686e11702] linux-user: Remove
>> the
>> > unused "not implemented" signal handling stubs
>> > git bisect good f8b985d65cf67004483816d5afcb7bf686e11702
>> > # good: [3ff48453e894990ea6495574037e70ed9b91947e] linux-user: allows
>> to use
>> > "--systemd ALL" with qemu-binfmt-conf.sh
>> > git bisect good 3ff48453e894990ea6495574037e70ed9b91947e
>> > # first bad commit: [d4247ec2d79ef2477cb886fa688706b068119736]
>> linux-user:
>> > Support f_flags in statfs when available.
>>
>> Awesome! Thanks for this.
>>
>> >
>> >
>> > Unfortunately just revering "[d4247ec2d79ef2477cb886fa688706b068119736]
>> > linux-user: Support f_flags in statfs when available" at the top of
>> v2.12.0
>> > still hangs.
>> >
>> > I will try to dig a bit more, but any advice would be appreciated.
>>
>> I managed to reproduce the hang today, so I'll investigate tomorrow.
>> I'm surprised reverting the commit doesn't work.
>>
>> Alistair
>>
>> >
>> > On Tue, May 29, 2018 at 10:40 PM Martin Jansa 
>> > wrote:
>> >>

[OE-core] [PATCH] wic/engine.py: improve error message when required tools are missing

[Anuj Mittal]

Instead of showing that command 'None' was found, show the name of
actual command that wasn't found on the host machine or at the native
sysroot path provided by user.

Signed-off-by: Anuj Mittal 
---
 scripts/lib/wic/engine.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/scripts/lib/wic/engine.py b/scripts/lib/wic/engine.py
index edcfab39ef..94992365df 100644
--- a/scripts/lib/wic/engine.py
+++ b/scripts/lib/wic/engine.py
@@ -284,8 +284,8 @@ class Disk:
 aname = "_%s" % name
 if aname not in self.__dict__:
 setattr(self, aname, find_executable(name, self.paths))
-if aname not in self.__dict__:
-raise WicError("Can't find executable {}".format(name))
+if aname not in self.__dict__ or self.__dict__[aname] is None:
+raise WicError("Can't find executable '{}'".format(name))
 return self.__dict__[aname]
 return self.__dict__[name]
 
-- 
2.17.0

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

Re: [OE-core] [PATCH] boost: Improve reproducibility

[Alexander Kanavin]

2018-06-01 8:38 GMT+03:00 Yu, Mingli :

> I did investigate the path a lot before send out the patch, but didn't
> figure out why it introduce the path for make_x86_64_sysv_elf_gas.o whose
> source file is make_x86_64_sysv_elf_gas.S.
>
> Anyway, I will try to dig more.
>
> If you have any ideas, welcome to help provide some hint.

I'm not an expert in symbol tables and what goes into them, but I
strongly suspect the full path is introduced by linker because that .S
file has two assembly labels (trampoline, finish). The other two
assembly files have no such labels, and so their file paths are not
added to the .so. I'm also not sure why there needs to be a full path,
as opposed to just the file name, as is the case for .c files (maybe
to avoid clashes with labels of the same name in different files?).

We should probably just strip that one specific .o file before it's
linked into the library. Or if there is a way to prevent the labels
from being written into the symbol table by the assembler, we can use
that too. Sadly boost has its own build system, so doing such custom
tweaks may be tricky.

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

Re: [OE-core] [PATCH] Meta runtime cases: add testcases for kernel sample

[Richard Purdie]

On Fri, 2018-06-01 at 04:02 -0400, Hongzhi.Song wrote:
> We are going to let runtime test support kernel tests. Now we just
> add
> kernel self-contained sample tests. And we plan to add overall kernel
> tests in the future.
> 
> This patch is just add kernel samples test which contains about 13
> tests
> enabled by kernel-sample.scc. So it needs statement,
> KERNEL_FEATURES_append += " kernel-sample/kernel-sample.scc" in
> local.conf.
> 
> Signed-off-by: Hongzhi.Song 
> ---
>  meta/lib/oeqa/runtime/cases/ksample.py | 440
> +
>  1 file changed, 440 insertions(+)
>  create mode 100644 meta/lib/oeqa/runtime/cases/ksample.py
[...]
> +# check config
> +status, ret = self.target.run('zcat /proc/config.gz | grep 
> CONFIG_TRACING_SUPPORT')
> +result = "CONFIG_TRACING_SUPPORT=y" in ret
> +if not result:
> +self.skipTest("CONFIG error")
> +# make sure if module exists
> +status, ret = self.target.run('uname -r')
> +cmd = "ls " + "/lib/modules/" + ret + 
> "/kernel/samples/trace_events/trace-events-sample.ko"
> +status, output = self.target.run(cmd)
> +if status != 0:
> +self.skipTest("trace-events-sample.ko doesn't exist")


There looks to be a fair bit of copy and paste code in these tests such
as the code above to look at config.gz. Could you turn some of these
into shared functions please?

Also, do we want to include this kernel-sample feature to the qemu
machines by default so that we enable these tests?

Cheers,

Richard

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

[OE-core] [PATCH] Meta runtime cases: add testcases for kernel sample

[Hongzhi.Song]

We are going to let runtime test support kernel tests. Now we just add
kernel self-contained sample tests. And we plan to add overall kernel
tests in the future.

This patch is just add kernel samples test which contains about 13 tests
enabled by kernel-sample.scc. So it needs statement,
KERNEL_FEATURES_append += " kernel-sample/kernel-sample.scc" in
local.conf.

Signed-off-by: Hongzhi.Song 
---
 meta/lib/oeqa/runtime/cases/ksample.py | 440 +
 1 file changed, 440 insertions(+)
 create mode 100644 meta/lib/oeqa/runtime/cases/ksample.py

diff --git a/meta/lib/oeqa/runtime/cases/ksample.py 
b/meta/lib/oeqa/runtime/cases/ksample.py
new file mode 100644
index 000..8a9d136
--- /dev/null
+++ b/meta/lib/oeqa/runtime/cases/ksample.py
@@ -0,0 +1,440 @@
+import os
+import time
+
+from oeqa.runtime.case import OERuntimeTestCase
+from oeqa.core.decorator.depends import OETestDepends
+from oeqa.core.decorator.oeid import OETestID
+from oeqa.core.decorator.data import skipIfNotFeature
+
+class KSampleTest(OERuntimeTestCase):
+
+@OETestID(33)
+@OETestDepends(['ssh.SSHTest.test_ssh'])
+def test_trace_events(self):
+# check config
+status, ret = self.target.run('zcat /proc/config.gz | grep 
CONFIG_TRACING_SUPPORT')
+result = "CONFIG_TRACING_SUPPORT=y" in ret
+if not result:
+self.skipTest("CONFIG error")
+# make sure if module exists
+status, ret = self.target.run('uname -r')
+cmd = "ls " + "/lib/modules/" + ret + 
"/kernel/samples/trace_events/trace-events-sample.ko"
+status, output = self.target.run(cmd)
+if status != 0:
+self.skipTest("trace-events-sample.ko doesn't exist")
+
+# modprobe
+status, output = self.target.run('modprobe trace-events-sample')
+msg = 'modprobe trace-events failed, output: %s' % output
+self.assertEqual(status, 0, msg=msg)
+# lsmod
+status, output = self.target.run('lsmod | grep trace_events_sample | 
cut -d\' \' -f1')
+self.assertEqual(output, "trace_events_sample", 'lsmod 
trace_events_sample failed')
+msg = 'lsmod trace-events failed, output: %s' % output
+self.assertEqual(status, 0, msg=msg)
+# check dir
+status, output = self.target.run('ls /sys/kernel/debug/tracing/events/ 
| grep sample-trace')
+self.assertEqual(output, "sample-trace", 'no dir of sample-trace')
+msg = 'if create dir of sample-tree, output: %s' % output
+self.assertEqual(status, 0, msg=msg)
+# enable trace
+status, output = self.target.run('echo 1 > 
/sys/kernel/debug/tracing/events/sample-trace/enable')
+status, output = self.target.run('cat 
/sys/kernel/debug/tracing/events/sample-trace/enable')
+self.assertEqual(output, "1", 'failed to enable')
+msg = 'cat enable, output: %s' % output
+self.assertEqual(status, 0, msg=msg)
+# check result
+status, output = self.target.run('cat /sys/kernel/debug/tracing/trace 
| grep hello | head -n1 | cut -d\':\' -f2')
+self.assertEqual(output, " foo_bar", 'failed')
+msg = 'cat trace-events, output: %s' % output
+self.assertEqual(status, 0, msg=msg)
+# enable trace
+status, output = self.target.run('echo 0 > 
/sys/kernel/debug/tracing/events/sample-trace/enable')
+msg = 'disable, output: %s' % output
+self.assertEqual(status, 0, msg=msg)
+# clean up trace
+status, output = self.target.run('echo > 
/sys/kernel/debug/tracing/trace')
+msg = 'clearup trace, output: %s' % output
+self.assertEqual(status, 0, msg=msg)
+# rmmod
+status, output = self.target.run('rmmod trace-events-sample')
+msg = 'rmmod, output: %s' % output
+self.assertEqual(status, 0, msg=msg)
+
+@OETestID(34)
+@OETestDepends(['ssh.SSHTest.test_ssh'])
+def test_trace_printk(self):
+# check config
+status, ret = self.target.run('zcat /proc/config.gz | grep 
CONFIG_TRACING_SUPPORT')
+result = "CONFIG_TRACING_SUPPORT=y" in ret
+if not result:
+self.skipTest("CONFIG error")
+# make sure if module exists
+status, ret = self.target.run('uname -r')
+cmd = "ls " + "/lib/modules/" + ret + 
"/kernel/samples/trace_printk/trace-printk.ko"
+status, output = self.target.run(cmd)
+if status != 0:
+self.skipTest("trace-printk.ko doesn't exist")
+
+# modprobe
+status, output = self.target.run('modprobe trace-printk')
+msg = 'modprobe trace-printk failed, output: %s' % output
+self.assertEqual(status, 0, msg=msg)
+# lsmod
+status, output = self.target.run('lsmod | grep trace_printk | cut -d\' 
\' -f1')
+self.assertEqual(output, "trace_printk", 'lsmod trace_printk failed')
+msg = 'lsmod trace-printk failed, output: %s' % output
+

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

[Dengke Du]

On 2018年05月31日 22:08, lei yang wrote:


hi dengke,

some of the kernel modules were rmmod-ed twice, some of them forget to 
be rmmod-ed when it fails,


please take a look.



Thanks, after bruce update the SRCREV for kernel meta, I will send v2.


Lei



On 2018年05月31日 12:19, Bruce Ashfield wrote:



On Wed, May 30, 2018 at 11:08 PM, Dengke Du > wrote:


Signed-off-by: Dengke Du mailto:dengke...@windriver.com>>
---
 meta/recipes-kernel/linux/files/run-ptest    | 138
++


Nothing else in linux-yocto uses "files", and this shouldn't either.

We can't guarantee that these are version independent, so they need 
to be in  a versioned

kernel subdirectory.

 meta/recipes-kernel/linux/linux-yocto.inc    |   8 ++
 meta/recipes-kernel/linux/linux-yocto_4.14.bb
 |   2 +-
 3 files changed, 147 insertions(+), 1 deletion(-)
 create mode 100644 meta/recipes-kernel/linux/files/run-ptest

diff --git a/meta/recipes-kernel/linux/files/run-ptest
b/meta/recipes-kernel/linux/files/run-ptest
new file mode 100644
index 000..a3d9e14
--- /dev/null
+++ b/meta/recipes-kernel/linux/files/run-ptest
@@ -0,0 +1,138 @@
+#!/bin/bash


This script should have a license and proper header file.

Also, if the ptests are mainly trace/sample related, name the script 
to indicate that.


The kernel already has a significant number of selftests, which are 
likely better than

these ptests. Is there any reason why they aren't being used instead ?

+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
+    rmmod "$i"
+  else
+    echo "$i: FAILED" >> kernel.log
+  fi
+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
+    rmmod "$i"
+  else
+    echo "$i: FAILED" >> kernel.log
+  fi
+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 

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

[Dengke Du]

On 2018年05月31日 12:19, Bruce Ashfield wrote:



On Wed, May 30, 2018 at 11:08 PM, Dengke Du > wrote:


Signed-off-by: Dengke Du mailto:dengke...@windriver.com>>
---
 meta/recipes-kernel/linux/files/run-ptest    | 138
++


Nothing else in linux-yocto uses "files", and this shouldn't either.

We can't guarantee that these are version independent, so they need to 
be in  a versioned

kernel subdirectory.


Ok, I will put it in versioned kernel subdirectory.



 meta/recipes-kernel/linux/linux-yocto.inc     |  8 ++
 meta/recipes-kernel/linux/linux-yocto_4.14.bb
 |   2 +-
 3 files changed, 147 insertions(+), 1 deletion(-)
 create mode 100644 meta/recipes-kernel/linux/files/run-ptest

diff --git a/meta/recipes-kernel/linux/files/run-ptest
b/meta/recipes-kernel/linux/files/run-ptest
new file mode 100644
index 000..a3d9e14
--- /dev/null
+++ b/meta/recipes-kernel/linux/files/run-ptest
@@ -0,0 +1,138 @@
+#!/bin/bash


This script should have a license and proper header file.

Also, if the ptests are mainly trace/sample related, name the script 
to indicate that.


Ok.



The kernel already has a significant number of selftests, which are 
likely better than

these ptests. Is there any reason why they aren't being used instead ?


This is different to selftests, this ptest was based on kernel samples 
in sample directory,
those samples were some tutorial modules, the modules that we can modify 
it and learn
it(some basic kernel theory), in the end build it into our image to test 
and verification our

thought easily.


+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
+    rmmod "$i"
+  else
+    echo "$i: FAILED" >> kernel.log
+  fi
+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
+    rmmod "$i"
+  else
+    echo "$i: FAILED" >> kernel.log
+  fi
+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 

Re: [OE-core] [PATCH 2/3] qemu: upgrade to 2.12.0

[Martin Jansa]

Yesterday I've tried to replay the end of the bisect and surprisingly I
wasn't seeing the hang with d4247ec2d79ef2477cb886fa688706b068119736.

With 2nd bad d4090306c8079ca3df426f82c493314c3537064e it hangs again.

So either I didn't wait long enough for qemu-i386 to finish (I mark it as
bad after it spends > 10mins inside qemu-i386 or the hang doesn't happen
reliably even with "bad" revision of qemu.

The revisions I'm trying are here:
http://git.openembedded.org/openembedded-core-contrib/log/?h=jansa/qemu-hang

On Fri, Jun 1, 2018 at 2:01 AM Alistair Francis 
wrote:

> On Thu, May 31, 2018 at 8:41 AM, Martin Jansa 
> wrote:
> > I've finished the bisect today:
> >
> > qemu$ git bisect log
> > git bisect start
> > # good: [9f750794985d7386f088da941c76b73880b2b6c4] sev/i386: add
> > sev_get_capabilities()
> > git bisect good 9f750794985d7386f088da941c76b73880b2b6c4
> > # bad: [91c60f124e682a78c9a2ef951e8e58ebab6441d0] target/ppc: fix
> tlbsync to
> > check privilege level depending on GTSE
> > git bisect bad 91c60f124e682a78c9a2ef951e8e58ebab6441d0
> > # bad: [a57946ff2acb9c0d95c9f127914540586b0b8c21] Merge remote-tracking
> > branch 'remotes/awilliam/tags/vfio-update-20180313.0' into staging
> > git bisect bad a57946ff2acb9c0d95c9f127914540586b0b8c21
> > # good: [5bdd374347b873ab59b356a284494a8bc1664008] Merge remote-tracking
> > branch 'remotes/bonzini/tags/for-upstream-sev' into staging
> > git bisect good 5bdd374347b873ab59b356a284494a8bc1664008
> > # bad: [55901900ec69d6fd6f332003d8ab81b2f8a38529] Merge remote-tracking
> > branch 'remotes/vivier2/tags/linux-user-for-2.12-pull-request' into
> staging
> > git bisect bad 55901900ec69d6fd6f332003d8ab81b2f8a38529
> > # bad: [d4090306c8079ca3df426f82c493314c3537064e] qemu-binfmt-conf.sh:
> add
> > qemu-xtensa
> > git bisect bad d4090306c8079ca3df426f82c493314c3537064e
> > # bad: [d4247ec2d79ef2477cb886fa688706b068119736] linux-user: Support
> > f_flags in statfs when available.
> > git bisect bad d4247ec2d79ef2477cb886fa688706b068119736
> > # good: [f8b985d65cf67004483816d5afcb7bf686e11702] linux-user: Remove the
> > unused "not implemented" signal handling stubs
> > git bisect good f8b985d65cf67004483816d5afcb7bf686e11702
> > # good: [3ff48453e894990ea6495574037e70ed9b91947e] linux-user: allows to
> use
> > "--systemd ALL" with qemu-binfmt-conf.sh
> > git bisect good 3ff48453e894990ea6495574037e70ed9b91947e
> > # first bad commit: [d4247ec2d79ef2477cb886fa688706b068119736]
> linux-user:
> > Support f_flags in statfs when available.
>
> Awesome! Thanks for this.
>
> >
> >
> > Unfortunately just revering "[d4247ec2d79ef2477cb886fa688706b068119736]
> > linux-user: Support f_flags in statfs when available" at the top of
> v2.12.0
> > still hangs.
> >
> > I will try to dig a bit more, but any advice would be appreciated.
>
> I managed to reproduce the hang today, so I'll investigate tomorrow.
> I'm surprised reverting the commit doesn't work.
>
> Alistair
>
> >
> > On Tue, May 29, 2018 at 10:40 PM Martin Jansa 
> > wrote:
> >>
> >> After removing ld-is-gold I was able to reproduce the issue.
> >>
> >> Unfortunately removing the
> >>
> meta/recipes-devtools/qemu/qemu/linux-user-Fix-webkitgtk-hangs-on-32-bit-x86-target.patch
> >> doesn't help with the hang, then I've tried to upgrade to latest SRCREV
> in
> >> qemu master (currently 5a5c383b1373aeb6c87a0d6060f6c3dc7c53082b)
> >>
> >> Will try to bisect where it started to hang between 2.11.0 and 2.12.0,
> but
> >> it might be faster if Alistair Francis can chime in as the author of
> this
> >> patch, he might have better idea why it stopped working.
> >>
> >> Cheers,
> >>
> >> On Tue, May 29, 2018 at 2:56 PM Martin Jansa 
> >> wrote:
> >>>
> >>> I've tried to reproduce it locally, but g-ir-scanner-qemuwrapper is
> >>> failing for me in various recipes and I never got as far as webkitgtk
> >>>
> >>> pango:
> >>> Error relocating
> >>>
> TOPDIR/tmp-musl/work/i586-oe-linux-musl/pango/1.40.14-r0/recipe-sysroot//usr/lib/libGL.so.1:
> >>> __glX_tls_Context: symbol not found
> >>> http://errors.yoctoproject.org/Errors/Details/178988/
> >>>
> >>> after disabling GI for pango (GI_DATA_ENABLED_pn-pango = "False") it
> >>> failed in
> >>> librsvg:
> >>> Error relocating
> >>>
> TOPDIR/tmp-musl/work/i586-oe-linux-musl/librsvg/2.40.20-r0/recipe-sysroot//usr/lib/libGL.so.1:
> >>> __glX_tls_Context: symbol not found
> >>> http://errors.yoctoproject.org/Errors/Details/178991/
> >>>
> >>> gstreamer1.0-plugins-base:
> >>> Error relocating
> >>>
> TOPDIR/tmp-musl/work/i586-oe-linux-musl/gstreamer1.0-plugins-base/1.14.0-r0/recipe-sysroot//usr/lib/libEGL.so.1:
> >>> _egl_TLS: symbol not found
> >>> http://errors.yoctoproject.org/Errors/Details/178993/
> >>>
> >>> and gtk+3 as well, because of disabled GI for pango:
> >>> Couldn't find include 'Pango-1.0.gir' (search path:
> >>>
> '['TOPDIR/tmp-musl/work/i586-oe-linux-musl/gtk+3/3.22.29-r0/recipe-sysroot/usr/share/gir-1.0',
> >>> '../gdk',
> >>>
>