Re: [OE-core] [PATCH] json-c: update to current upstream head, with --disable-werror

2019-06-10 Thread Martin Jansa 
Also the version went from 0.13.2 to 1.0 which doesn't match with the
sources. Don't forget to set PV when migrating recipes to use git fetcher.

On Tue, Jun 11, 2019 at 3:58 AM Douglas Royds via Openembedded-core <
openembedded-core@lists.openembedded.org> wrote:

> Upstream json-c haven't made a release since March 2018.
> Adopt the current HEAD revision, pulling it directly from git.
>
> icecc preprocesses source files locally before shipping them off to be
> compiled
> on remote hosts. This preprocessing removes comments, including /*
> fallthough */
> comments in switch statements that normally prevent an implicit-fallthrough
> warning, see https://github.com/icecc/icecream/issues/419
>
> Rather than turning off -Werror by patching configure.ac, the upstream
> project
> has implemented a configure option, --disable-werror, in response to Ross's
> https://github.com/json-c/json-c/issues/489
>
> Signed-off-by: Douglas Royds 
> ---
>  meta/recipes-devtools/json-c/json-c_0.13.1.bb | 30 ---
>  meta/recipes-devtools/json-c/json-c_git.bb| 19 
>  2 files changed, 19 insertions(+), 30 deletions(-)
>  delete mode 100644 meta/recipes-devtools/json-c/json-c_0.13.1.bb
>  create mode 100644 meta/recipes-devtools/json-c/json-c_git.bb
>
> diff --git a/meta/recipes-devtools/json-c/json-c_0.13.1.bb
> b/meta/recipes-devtools/json-c/json-c_0.13.1.bb
> deleted file mode 100644
> index 5b10e68297..00
> --- a/meta/recipes-devtools/json-c/json-c_0.13.1.bb
> +++ /dev/null
> @@ -1,30 +0,0 @@
> -SUMMARY = "C bindings for apps which will manipulate JSON data"
> -DESCRIPTION = "JSON-C implements a reference counting object model that
> allows you to easily construct JSON objects in C."
> -HOMEPAGE = "https://github.com/json-c/json-c/wiki;
> -LICENSE = "MIT"
> -LIC_FILES_CHKSUM = "file://COPYING;md5=de54b60fbbc35123ba193fea8ee216f2"
> -
> -SRC_URI = "https://s3.amazonaws.com/json-c_releases/releases/${BP}.tar.gz
> "
> -SRC_URI[md5sum] = "04969ad59cc37bddd83741a08b98f350"
> -SRC_URI[sha256sum] =
> "b87e608d4d3f7bfdd36ef78d56d53c74e66ab278d318b71e6002a369d36f4873"
> -
> -UPSTREAM_CHECK_REGEX = "json-c-(?P\d+(\.\d+)+).tar"
> -# json-c releases page is fetching the list of releases in some weird XML
> format
> -# from https://s3.amazonaws.com/json-c_releases and processes it with
> javascript :-/
> -#UPSTREAM_CHECK_URI = "
> https://s3.amazonaws.com/json-c_releases/releases/index.html;
> -RECIPE_UPSTREAM_VERSION = "0.13.1"
> -RECIPE_UPSTREAM_DATE = "Mar 04, 2018"
> -CHECK_DATE = "May 02, 2018"
> -
> -RPROVIDES_${PN} = "libjson"
> -
> -inherit autotools
> -
> -EXTRA_OECONF = "--enable-rdrand"
> -
> -do_configure_prepend() {
> -# Clean up autoconf cruft that should not be in the tarball
> -rm -f ${S}/config.status
> -}
> -
> -BBCLASSEXTEND = "native nativesdk"
> diff --git a/meta/recipes-devtools/json-c/json-c_git.bb
> b/meta/recipes-devtools/json-c/json-c_git.bb
> new file mode 100644
> index 00..07daa5ba11
> --- /dev/null
> +++ b/meta/recipes-devtools/json-c/json-c_git.bb
> @@ -0,0 +1,19 @@
> +SUMMARY = "C bindings for apps which will manipulate JSON data"
> +DESCRIPTION = "JSON-C implements a reference counting object model that
> allows you to easily construct JSON objects in C."
> +HOMEPAGE = "https://github.com/json-c/json-c/wiki;
> +LICENSE = "MIT"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=de54b60fbbc35123ba193fea8ee216f2"
> +
> +SRC_URI = "git://github.com/json-c/json-c.git"
> +SRCREV = "07ea04e65193c3e5c902c5b79421d5fa48ff67c7"
> +S = "${WORKDIR}/git"
> +
> +RPROVIDES_${PN} = "libjson"
> +
> +inherit autotools
> +
> +EXTRA_OECONF = "--disable-werror \
> +--enable-rdrand \
> +"
> +
> +BBCLASSEXTEND = "native nativesdk"
> --
> 2.17.1
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] json-c: update to current upstream head, with --disable-werror

2019-06-10 Thread Douglas Royds via Openembedded-core 

On 11/06/19 4:57 PM, Adrian Bunk wrote:


On Tue, Jun 11, 2019 at 03:12:09PM +1200, Douglas Royds via Openembedded-core 
wrote:

On 11/06/19 3:05 PM, Kang Kai wrote:


On 2019/6/11 上午11:04, Douglas Royds wrote:

On 11/06/19 2:46 PM, Kang Kai wrote:

...

Use option '-M' of git format-patch may make the patch more
clear. And why not just backport the 'disable-werror' commit?


Re '-M': True, fair point.

Re the backport: There hasn't been a release in over a year, they
don't seem to have any plans to do so (see
https://github.com/json-c/json-c/issues/487), and this was easier.
If you have a substantial objection, yes, I could submit it again
with a patch instead of the update.

Just consider footprint, git repo will take more space than tar ball.
But no substantial objection.


We do also lose the RECIPE_UPSTREAM_VERSION functionality by switching to
the git HEAD, ie. there'll be no notification when they do (eventually)
release a new version.

I'm in two minds. Opinions?

The biggest worry is actually whether some random git snapshot is as
stable as a release.

Unless there is a good reason why a git snapshot is better than
release plus backported patch, the default should be to not switch
to using a git snapshot.

Starting to follow git snapshots brings the risk of frequent regressions
since it follows the latest upstream development.



Fair enough, patch it is. Watch this space.

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

Re: [OE-core] [PATCH] json-c: update to current upstream head, with --disable-werror

2019-06-10 Thread Adrian Bunk 
On Tue, Jun 11, 2019 at 03:12:09PM +1200, Douglas Royds via Openembedded-core 
wrote:
> On 11/06/19 3:05 PM, Kang Kai wrote:
> 
> > On 2019/6/11 上午11:04, Douglas Royds wrote:
> > > On 11/06/19 2:46 PM, Kang Kai wrote:
>...
> > > > Use option '-M' of git format-patch may make the patch more
> > > > clear. And why not just backport the 'disable-werror' commit?
> > > 
> > > 
> > > Re '-M': True, fair point.
> > > 
> > > Re the backport: There hasn't been a release in over a year, they
> > > don't seem to have any plans to do so (see
> > > https://github.com/json-c/json-c/issues/487), and this was easier.
> > > If you have a substantial objection, yes, I could submit it again
> > > with a patch instead of the update.
> > 
> > Just consider footprint, git repo will take more space than tar ball.
> > But no substantial objection.
> 
> 
> We do also lose the RECIPE_UPSTREAM_VERSION functionality by switching to
> the git HEAD, ie. there'll be no notification when they do (eventually)
> release a new version.
> 
> I'm in two minds. Opinions?

The biggest worry is actually whether some random git snapshot is as 
stable as a release.

Unless there is a good reason why a git snapshot is better than
release plus backported patch, the default should be to not switch
to using a git snapshot.

Starting to follow git snapshots brings the risk of frequent regressions 
since it follows the latest upstream development.

cu
Adrian

-- 

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

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

Re: [OE-core] [PATCH] [V2][PATCH] dhcp:"dhclient -x eth0" action is not correct.

2019-06-10 Thread Changqing Li 

Ping


patch 0006-site.h-enable-gentle-shutdown.patch is involved by 
https://git.openembedded.org/openembedded-core/commit/?id=2c789bac353e17637549a7b31706761ba848728e


to fix problem of signal SIGTERM not handled properly. but now this 
problem have fixed by upstream.


and the patch 0006-site.h-enable-gentle-shutdown.patch will cause action 
of "dhclient -x eth0" not correct since it do some work before stop.



refer: 
http://isc-dhcp-users.2343191.n4.nabble.com/dhcpclient-and-dhcpd-do-not-stop-on-sigterm-td2528.html


On 5/23/19 3:03 PM, Jiping Ma wrote:

Please ignore V1 of [OE-core][PATCH] dhcp:"dhclient -x eth0" action is not 
correct.

The action of "dhclient -x eth0" and "dhclient -r eth0" is
same when enable ENABLE_GENTLE_SHUTDOWN. Disable ENABLE_GENTLE_SHUTDOWN
that will use the default signal hander.

Signed-off-by: Jiping Ma 
---
  .../dhcp/0006-site.h-enable-gentle-shutdown.patch  | 27 --
  meta/recipes-connectivity/dhcp/dhcp_4.4.1.bb   |  1 -
  2 files changed, 28 deletions(-)
  delete mode 100644 
meta/recipes-connectivity/dhcp/dhcp/0006-site.h-enable-gentle-shutdown.patch

diff --git 
a/meta/recipes-connectivity/dhcp/dhcp/0006-site.h-enable-gentle-shutdown.patch 
b/meta/recipes-connectivity/dhcp/dhcp/0006-site.h-enable-gentle-shutdown.patch
deleted file mode 100644
index 6ef70cc..000
--- 
a/meta/recipes-connectivity/dhcp/dhcp/0006-site.h-enable-gentle-shutdown.patch
+++ /dev/null
@@ -1,27 +0,0 @@
-From 01641d146e4e6bea954e4a4ee1f6230b822665b4 Mon Sep 17 00:00:00 2001
-From: Chen Qi 
-Date: Tue, 15 Aug 2017 15:37:49 +0800
-Subject: [PATCH 06/11] site.h: enable gentle shutdown
-
-Upstream-Status: Inappropriate [configuration]
-Signed-off-by: Chen Qi 
-
-Rebase to 4.3.6
-Signed-off-by: Hongxu Jia 

- includes/site.h | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-Index: dhcp-4.4.1/includes/site.h
-===
 dhcp-4.4.1.orig/includes/site.h
-+++ dhcp-4.4.1/includes/site.h
-@@ -295,7 +295,7 @@
-situations.  We plan to revisit this feature and may
-make non-backwards compatible changes including the
-removal of this define.  Use at your own risk.  */
--/* #define ENABLE_GENTLE_SHUTDOWN */
-+#define ENABLE_GENTLE_SHUTDOWN
-
- /* Include old error codes.  This is provided in case you
-are building an external program similar to omshell for
diff --git a/meta/recipes-connectivity/dhcp/dhcp_4.4.1.bb 
b/meta/recipes-connectivity/dhcp/dhcp_4.4.1.bb
index ca0daa1..b4c0d5d 100644
--- a/meta/recipes-connectivity/dhcp/dhcp_4.4.1.bb
+++ b/meta/recipes-connectivity/dhcp/dhcp_4.4.1.bb
@@ -5,7 +5,6 @@ SRC_URI += 
"file://0001-define-macro-_PATH_DHCPD_CONF-and-_PATH_DHCLIENT_CON.pat
  file://0003-link-with-lcrypto.patch \
  file://0004-Fix-out-of-tree-builds.patch \
  
file://0005-dhcp-client-fix-invoke-dhclient-script-failed-on-Rea.patch \
-file://0006-site.h-enable-gentle-shutdown.patch \
  
file://0007-Add-configure-argument-to-make-the-libxml2-dependenc.patch \
  file://0009-remove-dhclient-script-bash-dependency.patch \
  file://0012-dhcp-correct-the-intention-for-xml2-lib-search.patch \


--
BRs

Sandy(Li Changqing)

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

Re: [OE-core] [PATCH] json-c: update to current upstream head, with --disable-werror

2019-06-10 Thread Douglas Royds via Openembedded-core 

On 11/06/19 3:05 PM, Kang Kai wrote:


On 2019/6/11 上午11:04, Douglas Royds wrote:

On 11/06/19 2:46 PM, Kang Kai wrote:


On 2019/6/11 上午9:57, Douglas Royds via Openembedded-core wrote:

Upstream json-c haven't made a release since March 2018.
Adopt the current HEAD revision, pulling it directly from git.

icecc preprocesses source files locally before shipping them off to 
be compiled
on remote hosts. This preprocessing removes comments, including /* 
fallthough */
comments in switch statements that normally prevent an 
implicit-fallthrough

warning, see https://github.com/icecc/icecream/issues/419

Rather than turning off -Werror by patching configure.ac, the 
upstream project
has implemented a configure option, --disable-werror, in response 
to Ross's

https://github.com/json-c/json-c/issues/489

Signed-off-by: Douglas Royds 
---
  meta/recipes-devtools/json-c/json-c_0.13.1.bb | 30 
---

  meta/recipes-devtools/json-c/json-c_git.bb    | 19 


Use option '-M' of git format-patch may make the patch more clear. 
And why not just backport the 'disable-werror' commit?



Re '-M': True, fair point.

Re the backport: There hasn't been a release in over a year, they 
don't seem to have any plans to do so (see 
https://github.com/json-c/json-c/issues/487), and this was easier. If 
you have a substantial objection, yes, I could submit it again with a 
patch instead of the update.


Just consider footprint, git repo will take more space than tar ball. 
But no substantial objection.



We do also lose the RECIPE_UPSTREAM_VERSION functionality by switching 
to the git HEAD, ie. there'll be no notification when they do 
(eventually) release a new version.


I'm in two minds. Opinions?




Kai






Regards,
Kai



  2 files changed, 19 insertions(+), 30 deletions(-)
  delete mode 100644 meta/recipes-devtools/json-c/json-c_0.13.1.bb
  create mode 100644 meta/recipes-devtools/json-c/json-c_git.bb

diff --git a/meta/recipes-devtools/json-c/json-c_0.13.1.bb 
b/meta/recipes-devtools/json-c/json-c_0.13.1.bb

deleted file mode 100644
index 5b10e68297..00
--- a/meta/recipes-devtools/json-c/json-c_0.13.1.bb
+++ /dev/null
@@ -1,30 +0,0 @@
-SUMMARY = "C bindings for apps which will manipulate JSON data"
-DESCRIPTION = "JSON-C implements a reference counting object model 
that allows you to easily construct JSON objects in C."

-HOMEPAGE = "https://github.com/json-c/json-c/wiki;
-LICENSE = "MIT"
-LIC_FILES_CHKSUM = 
"file://COPYING;md5=de54b60fbbc35123ba193fea8ee216f2"

-
-SRC_URI = 
"https://s3.amazonaws.com/json-c_releases/releases/${BP}.tar.gz;

-SRC_URI[md5sum] = "04969ad59cc37bddd83741a08b98f350"
-SRC_URI[sha256sum] = 
"b87e608d4d3f7bfdd36ef78d56d53c74e66ab278d318b71e6002a369d36f4873"

-
-UPSTREAM_CHECK_REGEX = "json-c-(?P\d+(\.\d+)+).tar"
-# json-c releases page is fetching the list of releases in some 
weird XML format
-# from https://s3.amazonaws.com/json-c_releases and processes it 
with javascript :-/
-#UPSTREAM_CHECK_URI = 
"https://s3.amazonaws.com/json-c_releases/releases/index.html;

-RECIPE_UPSTREAM_VERSION = "0.13.1"
-RECIPE_UPSTREAM_DATE = "Mar 04, 2018"
-CHECK_DATE = "May 02, 2018"
-
-RPROVIDES_${PN} = "libjson"
-
-inherit autotools
-
-EXTRA_OECONF = "--enable-rdrand"
-
-do_configure_prepend() {
-    # Clean up autoconf cruft that should not be in the tarball
-    rm -f ${S}/config.status
-}
-
-BBCLASSEXTEND = "native nativesdk"
diff --git a/meta/recipes-devtools/json-c/json-c_git.bb 
b/meta/recipes-devtools/json-c/json-c_git.bb

new file mode 100644
index 00..07daa5ba11
--- /dev/null
+++ b/meta/recipes-devtools/json-c/json-c_git.bb
@@ -0,0 +1,19 @@
+SUMMARY = "C bindings for apps which will manipulate JSON data"
+DESCRIPTION = "JSON-C implements a reference counting object model 
that allows you to easily construct JSON objects in C."

+HOMEPAGE = "https://github.com/json-c/json-c/wiki;
+LICENSE = "MIT"
+LIC_FILES_CHKSUM = 
"file://COPYING;md5=de54b60fbbc35123ba193fea8ee216f2"

+
+SRC_URI = "git://github.com/json-c/json-c.git"
+SRCREV = "07ea04e65193c3e5c902c5b79421d5fa48ff67c7"
+S = "${WORKDIR}/git"
+
+RPROVIDES_${PN} = "libjson"
+
+inherit autotools
+
+EXTRA_OECONF = "--disable-werror \
+    --enable-rdrand \
+    "
+
+BBCLASSEXTEND = "native nativesdk"










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

Re: [OE-core] [PATCH] json-c: update to current upstream head, with --disable-werror

2019-06-10 Thread Kang Kai 

On 2019/6/11 上午11:04, Douglas Royds wrote:

On 11/06/19 2:46 PM, Kang Kai wrote:


On 2019/6/11 上午9:57, Douglas Royds via Openembedded-core wrote:

Upstream json-c haven't made a release since March 2018.
Adopt the current HEAD revision, pulling it directly from git.

icecc preprocesses source files locally before shipping them off to 
be compiled
on remote hosts. This preprocessing removes comments, including /* 
fallthough */
comments in switch statements that normally prevent an 
implicit-fallthrough

warning, see https://github.com/icecc/icecream/issues/419

Rather than turning off -Werror by patching configure.ac, the 
upstream project
has implemented a configure option, --disable-werror, in response to 
Ross's

https://github.com/json-c/json-c/issues/489

Signed-off-by: Douglas Royds 
---
  meta/recipes-devtools/json-c/json-c_0.13.1.bb | 30 
---

  meta/recipes-devtools/json-c/json-c_git.bb    | 19 


Use option '-M' of git format-patch may make the patch more clear. 
And why not just backport the 'disable-werror' commit?



Re '-M': True, fair point.

Re the backport: There hasn't been a release in over a year, they 
don't seem to have any plans to do so (see 
https://github.com/json-c/json-c/issues/487), and this was easier. If 
you have a substantial objection, yes, I could submit it again with a 
patch instead of the update.


Just consider footprint, git repo will take more space than tar ball. 
But no substantial objection.


Kai






Regards,
Kai



  2 files changed, 19 insertions(+), 30 deletions(-)
  delete mode 100644 meta/recipes-devtools/json-c/json-c_0.13.1.bb
  create mode 100644 meta/recipes-devtools/json-c/json-c_git.bb

diff --git a/meta/recipes-devtools/json-c/json-c_0.13.1.bb 
b/meta/recipes-devtools/json-c/json-c_0.13.1.bb

deleted file mode 100644
index 5b10e68297..00
--- a/meta/recipes-devtools/json-c/json-c_0.13.1.bb
+++ /dev/null
@@ -1,30 +0,0 @@
-SUMMARY = "C bindings for apps which will manipulate JSON data"
-DESCRIPTION = "JSON-C implements a reference counting object model 
that allows you to easily construct JSON objects in C."

-HOMEPAGE = "https://github.com/json-c/json-c/wiki;
-LICENSE = "MIT"
-LIC_FILES_CHKSUM = 
"file://COPYING;md5=de54b60fbbc35123ba193fea8ee216f2"

-
-SRC_URI = 
"https://s3.amazonaws.com/json-c_releases/releases/${BP}.tar.gz;

-SRC_URI[md5sum] = "04969ad59cc37bddd83741a08b98f350"
-SRC_URI[sha256sum] = 
"b87e608d4d3f7bfdd36ef78d56d53c74e66ab278d318b71e6002a369d36f4873"

-
-UPSTREAM_CHECK_REGEX = "json-c-(?P\d+(\.\d+)+).tar"
-# json-c releases page is fetching the list of releases in some 
weird XML format
-# from https://s3.amazonaws.com/json-c_releases and processes it 
with javascript :-/
-#UPSTREAM_CHECK_URI = 
"https://s3.amazonaws.com/json-c_releases/releases/index.html;

-RECIPE_UPSTREAM_VERSION = "0.13.1"
-RECIPE_UPSTREAM_DATE = "Mar 04, 2018"
-CHECK_DATE = "May 02, 2018"
-
-RPROVIDES_${PN} = "libjson"
-
-inherit autotools
-
-EXTRA_OECONF = "--enable-rdrand"
-
-do_configure_prepend() {
-    # Clean up autoconf cruft that should not be in the tarball
-    rm -f ${S}/config.status
-}
-
-BBCLASSEXTEND = "native nativesdk"
diff --git a/meta/recipes-devtools/json-c/json-c_git.bb 
b/meta/recipes-devtools/json-c/json-c_git.bb

new file mode 100644
index 00..07daa5ba11
--- /dev/null
+++ b/meta/recipes-devtools/json-c/json-c_git.bb
@@ -0,0 +1,19 @@
+SUMMARY = "C bindings for apps which will manipulate JSON data"
+DESCRIPTION = "JSON-C implements a reference counting object model 
that allows you to easily construct JSON objects in C."

+HOMEPAGE = "https://github.com/json-c/json-c/wiki;
+LICENSE = "MIT"
+LIC_FILES_CHKSUM = 
"file://COPYING;md5=de54b60fbbc35123ba193fea8ee216f2"

+
+SRC_URI = "git://github.com/json-c/json-c.git"
+SRCREV = "07ea04e65193c3e5c902c5b79421d5fa48ff67c7"
+S = "${WORKDIR}/git"
+
+RPROVIDES_${PN} = "libjson"
+
+inherit autotools
+
+EXTRA_OECONF = "--disable-werror \
+    --enable-rdrand \
+    "
+
+BBCLASSEXTEND = "native nativesdk"








--
Kai Kang

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

Re: [OE-core] [PATCH] json-c: update to current upstream head, with --disable-werror

2019-06-10 Thread Douglas Royds via Openembedded-core 

On 11/06/19 2:46 PM, Kang Kai wrote:


On 2019/6/11 上午9:57, Douglas Royds via Openembedded-core wrote:

Upstream json-c haven't made a release since March 2018.
Adopt the current HEAD revision, pulling it directly from git.

icecc preprocesses source files locally before shipping them off to 
be compiled
on remote hosts. This preprocessing removes comments, including /* 
fallthough */
comments in switch statements that normally prevent an 
implicit-fallthrough

warning, see https://github.com/icecc/icecream/issues/419

Rather than turning off -Werror by patching configure.ac, the 
upstream project
has implemented a configure option, --disable-werror, in response to 
Ross's

https://github.com/json-c/json-c/issues/489

Signed-off-by: Douglas Royds 
---
  meta/recipes-devtools/json-c/json-c_0.13.1.bb | 30 ---
  meta/recipes-devtools/json-c/json-c_git.bb    | 19 


Use option '-M' of git format-patch may make the patch more clear. And 
why not just backport the 'disable-werror' commit?



Re '-M': True, fair point.

Re the backport: There hasn't been a release in over a year, they don't 
seem to have any plans to do so (see 
https://github.com/json-c/json-c/issues/487), and this was easier. If 
you have a substantial objection, yes, I could submit it again with a 
patch instead of the update.





Regards,
Kai



  2 files changed, 19 insertions(+), 30 deletions(-)
  delete mode 100644 meta/recipes-devtools/json-c/json-c_0.13.1.bb
  create mode 100644 meta/recipes-devtools/json-c/json-c_git.bb

diff --git a/meta/recipes-devtools/json-c/json-c_0.13.1.bb 
b/meta/recipes-devtools/json-c/json-c_0.13.1.bb

deleted file mode 100644
index 5b10e68297..00
--- a/meta/recipes-devtools/json-c/json-c_0.13.1.bb
+++ /dev/null
@@ -1,30 +0,0 @@
-SUMMARY = "C bindings for apps which will manipulate JSON data"
-DESCRIPTION = "JSON-C implements a reference counting object model 
that allows you to easily construct JSON objects in C."

-HOMEPAGE = "https://github.com/json-c/json-c/wiki;
-LICENSE = "MIT"
-LIC_FILES_CHKSUM = 
"file://COPYING;md5=de54b60fbbc35123ba193fea8ee216f2"

-
-SRC_URI = 
"https://s3.amazonaws.com/json-c_releases/releases/${BP}.tar.gz;

-SRC_URI[md5sum] = "04969ad59cc37bddd83741a08b98f350"
-SRC_URI[sha256sum] = 
"b87e608d4d3f7bfdd36ef78d56d53c74e66ab278d318b71e6002a369d36f4873"

-
-UPSTREAM_CHECK_REGEX = "json-c-(?P\d+(\.\d+)+).tar"
-# json-c releases page is fetching the list of releases in some 
weird XML format
-# from https://s3.amazonaws.com/json-c_releases and processes it 
with javascript :-/
-#UPSTREAM_CHECK_URI = 
"https://s3.amazonaws.com/json-c_releases/releases/index.html;

-RECIPE_UPSTREAM_VERSION = "0.13.1"
-RECIPE_UPSTREAM_DATE = "Mar 04, 2018"
-CHECK_DATE = "May 02, 2018"
-
-RPROVIDES_${PN} = "libjson"
-
-inherit autotools
-
-EXTRA_OECONF = "--enable-rdrand"
-
-do_configure_prepend() {
-    # Clean up autoconf cruft that should not be in the tarball
-    rm -f ${S}/config.status
-}
-
-BBCLASSEXTEND = "native nativesdk"
diff --git a/meta/recipes-devtools/json-c/json-c_git.bb 
b/meta/recipes-devtools/json-c/json-c_git.bb

new file mode 100644
index 00..07daa5ba11
--- /dev/null
+++ b/meta/recipes-devtools/json-c/json-c_git.bb
@@ -0,0 +1,19 @@
+SUMMARY = "C bindings for apps which will manipulate JSON data"
+DESCRIPTION = "JSON-C implements a reference counting object model 
that allows you to easily construct JSON objects in C."

+HOMEPAGE = "https://github.com/json-c/json-c/wiki;
+LICENSE = "MIT"
+LIC_FILES_CHKSUM = 
"file://COPYING;md5=de54b60fbbc35123ba193fea8ee216f2"

+
+SRC_URI = "git://github.com/json-c/json-c.git"
+SRCREV = "07ea04e65193c3e5c902c5b79421d5fa48ff67c7"
+S = "${WORKDIR}/git"
+
+RPROVIDES_${PN} = "libjson"
+
+inherit autotools
+
+EXTRA_OECONF = "--disable-werror \
+    --enable-rdrand \
+    "
+
+BBCLASSEXTEND = "native nativesdk"





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

Re: [OE-core] [PATCH] json-c: update to current upstream head, with --disable-werror

2019-06-10 Thread Kang Kai 

On 2019/6/11 上午9:57, Douglas Royds via Openembedded-core wrote:

Upstream json-c haven't made a release since March 2018.
Adopt the current HEAD revision, pulling it directly from git.

icecc preprocesses source files locally before shipping them off to be compiled
on remote hosts. This preprocessing removes comments, including /* fallthough */
comments in switch statements that normally prevent an implicit-fallthrough
warning, see https://github.com/icecc/icecream/issues/419

Rather than turning off -Werror by patching configure.ac, the upstream project
has implemented a configure option, --disable-werror, in response to Ross's
https://github.com/json-c/json-c/issues/489

Signed-off-by: Douglas Royds 
---
  meta/recipes-devtools/json-c/json-c_0.13.1.bb | 30 ---
  meta/recipes-devtools/json-c/json-c_git.bb| 19 


Use option '-M' of git format-patch may make the patch more clear. And 
why not just backport the 'disable-werror' commit?


Regards,
Kai



  2 files changed, 19 insertions(+), 30 deletions(-)
  delete mode 100644 meta/recipes-devtools/json-c/json-c_0.13.1.bb
  create mode 100644 meta/recipes-devtools/json-c/json-c_git.bb

diff --git a/meta/recipes-devtools/json-c/json-c_0.13.1.bb 
b/meta/recipes-devtools/json-c/json-c_0.13.1.bb
deleted file mode 100644
index 5b10e68297..00
--- a/meta/recipes-devtools/json-c/json-c_0.13.1.bb
+++ /dev/null
@@ -1,30 +0,0 @@
-SUMMARY = "C bindings for apps which will manipulate JSON data"
-DESCRIPTION = "JSON-C implements a reference counting object model that allows you 
to easily construct JSON objects in C."
-HOMEPAGE = "https://github.com/json-c/json-c/wiki;
-LICENSE = "MIT"
-LIC_FILES_CHKSUM = "file://COPYING;md5=de54b60fbbc35123ba193fea8ee216f2"
-
-SRC_URI = "https://s3.amazonaws.com/json-c_releases/releases/${BP}.tar.gz;
-SRC_URI[md5sum] = "04969ad59cc37bddd83741a08b98f350"
-SRC_URI[sha256sum] = 
"b87e608d4d3f7bfdd36ef78d56d53c74e66ab278d318b71e6002a369d36f4873"
-
-UPSTREAM_CHECK_REGEX = "json-c-(?P\d+(\.\d+)+).tar"
-# json-c releases page is fetching the list of releases in some weird XML 
format
-# from https://s3.amazonaws.com/json-c_releases and processes it with 
javascript :-/
-#UPSTREAM_CHECK_URI = 
"https://s3.amazonaws.com/json-c_releases/releases/index.html;
-RECIPE_UPSTREAM_VERSION = "0.13.1"
-RECIPE_UPSTREAM_DATE = "Mar 04, 2018"
-CHECK_DATE = "May 02, 2018"
-
-RPROVIDES_${PN} = "libjson"
-
-inherit autotools
-
-EXTRA_OECONF = "--enable-rdrand"
-
-do_configure_prepend() {
-# Clean up autoconf cruft that should not be in the tarball
-rm -f ${S}/config.status
-}
-
-BBCLASSEXTEND = "native nativesdk"
diff --git a/meta/recipes-devtools/json-c/json-c_git.bb 
b/meta/recipes-devtools/json-c/json-c_git.bb
new file mode 100644
index 00..07daa5ba11
--- /dev/null
+++ b/meta/recipes-devtools/json-c/json-c_git.bb
@@ -0,0 +1,19 @@
+SUMMARY = "C bindings for apps which will manipulate JSON data"
+DESCRIPTION = "JSON-C implements a reference counting object model that allows you 
to easily construct JSON objects in C."
+HOMEPAGE = "https://github.com/json-c/json-c/wiki;
+LICENSE = "MIT"
+LIC_FILES_CHKSUM = "file://COPYING;md5=de54b60fbbc35123ba193fea8ee216f2"
+
+SRC_URI = "git://github.com/json-c/json-c.git"
+SRCREV = "07ea04e65193c3e5c902c5b79421d5fa48ff67c7"
+S = "${WORKDIR}/git"
+
+RPROVIDES_${PN} = "libjson"
+
+inherit autotools
+
+EXTRA_OECONF = "--disable-werror \
+--enable-rdrand \
+"
+
+BBCLASSEXTEND = "native nativesdk"



--
Kai Kang

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

[OE-core] [V2][PATCH] kernel.bbclass: Make task clean depend on cleaning of make-mod-scripts

2019-06-10 Thread Haiqing Bai 
The package 'make-mod-scripts' creates files in 
'kernel-build-artifacts/include/config'
which are removed by 'cleanall/cleansstate' of 'virtual/kernel'. And this 
causes the
below error while building out of tree kernel module:
ERROR: Kernel configuration is invalid.
  include/generated/autoconf.h or include/config/auto.conf are missing.
  Run 'make oldconfig && make prepare' on kernel src to fix it.

Suggested-by: Jun Nie 

Signed-off-by: Haiqing Bai 
---
 meta/classes/kernel.bbclass | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index 111a0b2..a60e15b 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta/classes/kernel.bbclass
@@ -8,6 +8,7 @@ DEPENDS += "virtual/${TARGET_PREFIX}binutils 
virtual/${TARGET_PREFIX}gcc kmod-na
 PACKAGE_WRITE_DEPS += "depmodwrapper-cross"
 
 do_deploy[depends] += "depmodwrapper-cross:do_populate_sysroot"
+do_clean[depends] += "make-mod-scripts:do_clean"
 
 CVE_PRODUCT ?= "linux_kernel"
 
-- 
1.9.1

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

Re: [OE-core] [PATCH v2] json-c: Disable icecc to avoid implicit-fallthrough warning as error

2019-06-10 Thread Douglas Royds via Openembedded-core 
Please disregard this one, I've sent a recipe update to pick up the new 
--disable-werror configure option.


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

[OE-core] [PATCH] json-c: update to current upstream head, with --disable-werror

2019-06-10 Thread Douglas Royds via Openembedded-core 
Upstream json-c haven't made a release since March 2018.
Adopt the current HEAD revision, pulling it directly from git.

icecc preprocesses source files locally before shipping them off to be compiled
on remote hosts. This preprocessing removes comments, including /* fallthough */
comments in switch statements that normally prevent an implicit-fallthrough
warning, see https://github.com/icecc/icecream/issues/419

Rather than turning off -Werror by patching configure.ac, the upstream project
has implemented a configure option, --disable-werror, in response to Ross's
https://github.com/json-c/json-c/issues/489

Signed-off-by: Douglas Royds 
---
 meta/recipes-devtools/json-c/json-c_0.13.1.bb | 30 ---
 meta/recipes-devtools/json-c/json-c_git.bb| 19 
 2 files changed, 19 insertions(+), 30 deletions(-)
 delete mode 100644 meta/recipes-devtools/json-c/json-c_0.13.1.bb
 create mode 100644 meta/recipes-devtools/json-c/json-c_git.bb

diff --git a/meta/recipes-devtools/json-c/json-c_0.13.1.bb 
b/meta/recipes-devtools/json-c/json-c_0.13.1.bb
deleted file mode 100644
index 5b10e68297..00
--- a/meta/recipes-devtools/json-c/json-c_0.13.1.bb
+++ /dev/null
@@ -1,30 +0,0 @@
-SUMMARY = "C bindings for apps which will manipulate JSON data"
-DESCRIPTION = "JSON-C implements a reference counting object model that allows 
you to easily construct JSON objects in C."
-HOMEPAGE = "https://github.com/json-c/json-c/wiki;
-LICENSE = "MIT"
-LIC_FILES_CHKSUM = "file://COPYING;md5=de54b60fbbc35123ba193fea8ee216f2"
-
-SRC_URI = "https://s3.amazonaws.com/json-c_releases/releases/${BP}.tar.gz;
-SRC_URI[md5sum] = "04969ad59cc37bddd83741a08b98f350"
-SRC_URI[sha256sum] = 
"b87e608d4d3f7bfdd36ef78d56d53c74e66ab278d318b71e6002a369d36f4873"
-
-UPSTREAM_CHECK_REGEX = "json-c-(?P\d+(\.\d+)+).tar"
-# json-c releases page is fetching the list of releases in some weird XML 
format
-# from https://s3.amazonaws.com/json-c_releases and processes it with 
javascript :-/
-#UPSTREAM_CHECK_URI = 
"https://s3.amazonaws.com/json-c_releases/releases/index.html;
-RECIPE_UPSTREAM_VERSION = "0.13.1"
-RECIPE_UPSTREAM_DATE = "Mar 04, 2018"
-CHECK_DATE = "May 02, 2018"
-
-RPROVIDES_${PN} = "libjson"
-
-inherit autotools
-
-EXTRA_OECONF = "--enable-rdrand"
-
-do_configure_prepend() {
-# Clean up autoconf cruft that should not be in the tarball
-rm -f ${S}/config.status
-}
-
-BBCLASSEXTEND = "native nativesdk"
diff --git a/meta/recipes-devtools/json-c/json-c_git.bb 
b/meta/recipes-devtools/json-c/json-c_git.bb
new file mode 100644
index 00..07daa5ba11
--- /dev/null
+++ b/meta/recipes-devtools/json-c/json-c_git.bb
@@ -0,0 +1,19 @@
+SUMMARY = "C bindings for apps which will manipulate JSON data"
+DESCRIPTION = "JSON-C implements a reference counting object model that allows 
you to easily construct JSON objects in C."
+HOMEPAGE = "https://github.com/json-c/json-c/wiki;
+LICENSE = "MIT"
+LIC_FILES_CHKSUM = "file://COPYING;md5=de54b60fbbc35123ba193fea8ee216f2"
+
+SRC_URI = "git://github.com/json-c/json-c.git"
+SRCREV = "07ea04e65193c3e5c902c5b79421d5fa48ff67c7"
+S = "${WORKDIR}/git"
+
+RPROVIDES_${PN} = "libjson"
+
+inherit autotools
+
+EXTRA_OECONF = "--disable-werror \
+--enable-rdrand \
+"
+
+BBCLASSEXTEND = "native nativesdk"
-- 
2.17.1

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

Re: [OE-core] [PATCH 06/21] openssh: Avoid PROVIDES warning from rng-tools dependency

2019-06-10 Thread akuster808 



On 6/10/19 12:17 PM, Sylvain Lemieux wrote:
> Is there any plan to add a revision of this patch (From OE-Core rev:
> f93f026212ebc28fce66682cdb995e061586df45) and a revision of the patch
> that fix the "sshd startup is delayed" issue (From OE-Core rev:
> 9b01375236e19e3366c58877c4154d7c71632984) into thud?
Yeah, I don't see any reason why not. I will add it to my list.

thanks,
Armin
>
> p.s. I already added the change into a bbappend and tested it.
>
>
> Regards,
> Sylvain Lemieux
>
> On Mon, Jun 3, 2019 at 11:08 AM Armin Kuster  wrote:
>> From: Richard Purdie 
>>
>> Avoid the warning:
>>
>> WARNING: Nothing RPROVIDES 'nativesdk-rng-tools' (but 
>> virtual:nativesdk:/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-connectivity/openssh/openssh_7.9p1.bb
>>  RDEPENDS on or otherwise requires it)
>>
>> Signed-off-by: Richard Purdie 
>> Signed-off-by: Armin Kuster 
>> ---
>>  meta/recipes-connectivity/openssh/openssh_7.9p1.bb | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/meta/recipes-connectivity/openssh/openssh_7.9p1.bb 
>> b/meta/recipes-connectivity/openssh/openssh_7.9p1.bb
>> index 976bcc5..3b4ed72 100644
>> --- a/meta/recipes-connectivity/openssh/openssh_7.9p1.bb
>> +++ b/meta/recipes-connectivity/openssh/openssh_7.9p1.bb
>> @@ -148,7 +148,7 @@ FILES_${PN}-keygen = "${bindir}/ssh-keygen"
>>
>>  RDEPENDS_${PN} += "${PN}-scp ${PN}-ssh ${PN}-sshd ${PN}-keygen"
>>  RDEPENDS_${PN}-sshd += "${PN}-keygen 
>> ${@bb.utils.contains('DISTRO_FEATURES', 'pam', 'pam-plugin-keyinit 
>> pam-plugin-loginuid', '', d)}"
>> -RRECOMMENDS_${PN}-sshd += "rng-tools"
>> +RRECOMMENDS_${PN}-sshd_append_class-target = " rng-tools"
>>  RDEPENDS_${PN}-ptest += "${PN}-sftp ${PN}-misc ${PN}-sftp-server make sed"
>>
>>  RPROVIDES_${PN}-ssh = "ssh"
>> --
>> 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] Questions: Using OE toolchain of different arch.

2019-06-10 Thread Ying-Chun Liu (PaulLiu) 
Dear openembedded-core developers,


I need some help about using OE toolchain from different arch.


For example, on RPi3, we build the rootfs using armhf architecture.

(require  conf/machine/include/arm/arch-armv6.inc)

That means the whole rootfs is built by arm-linux-gnueabihf-*


But when adding TF-A and OPTEE. On RPi3, TF-A and OPTEE runs in 64-bit
mode. And TF-A will then load u-boot (BL33) and runs it in 32-bit mode.
So the rest of the systems still run on 32-bit mode.


The problem is now we want to build TF-A and OPTEE. So we need to
compile it by aarch64 toolchains. That is we should use
CROSS_COMPILE=aarch64-oe-linux-* from aarch64. But however it seems to
me that I cannot do that. I tried to make a recipe for TF-A by chainging
architecture of that recipe but I still don't have aarch64-oe-linux-*
available. Is there a proper way of doing this?

BTW, this is not about ilp32 because we still want the whole system runs
in armhf for compatibility.

Yours,
Paul


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

Re: [OE-core] [PATCH 06/21] openssh: Avoid PROVIDES warning from rng-tools dependency

2019-06-10 Thread Sylvain Lemieux 
Is there any plan to add a revision of this patch (From OE-Core rev:
f93f026212ebc28fce66682cdb995e061586df45) and a revision of the patch
that fix the "sshd startup is delayed" issue (From OE-Core rev:
9b01375236e19e3366c58877c4154d7c71632984) into thud?

p.s. I already added the change into a bbappend and tested it.


Regards,
Sylvain Lemieux

On Mon, Jun 3, 2019 at 11:08 AM Armin Kuster  wrote:
>
> From: Richard Purdie 
>
> Avoid the warning:
>
> WARNING: Nothing RPROVIDES 'nativesdk-rng-tools' (but 
> virtual:nativesdk:/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-connectivity/openssh/openssh_7.9p1.bb
>  RDEPENDS on or otherwise requires it)
>
> Signed-off-by: Richard Purdie 
> Signed-off-by: Armin Kuster 
> ---
>  meta/recipes-connectivity/openssh/openssh_7.9p1.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-connectivity/openssh/openssh_7.9p1.bb 
> b/meta/recipes-connectivity/openssh/openssh_7.9p1.bb
> index 976bcc5..3b4ed72 100644
> --- a/meta/recipes-connectivity/openssh/openssh_7.9p1.bb
> +++ b/meta/recipes-connectivity/openssh/openssh_7.9p1.bb
> @@ -148,7 +148,7 @@ FILES_${PN}-keygen = "${bindir}/ssh-keygen"
>
>  RDEPENDS_${PN} += "${PN}-scp ${PN}-ssh ${PN}-sshd ${PN}-keygen"
>  RDEPENDS_${PN}-sshd += "${PN}-keygen ${@bb.utils.contains('DISTRO_FEATURES', 
> 'pam', 'pam-plugin-keyinit pam-plugin-loginuid', '', d)}"
> -RRECOMMENDS_${PN}-sshd += "rng-tools"
> +RRECOMMENDS_${PN}-sshd_append_class-target = " rng-tools"
>  RDEPENDS_${PN}-ptest += "${PN}-sftp ${PN}-misc ${PN}-sftp-server make sed"
>
>  RPROVIDES_${PN}-ssh = "ssh"
> --
> 2.7.4
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 3/3] gtk+3: update 3.24.5 -> 3.24.8

2019-06-10 Thread Richard Purdie 
On Mon, 2019-06-10 at 13:32 +0100, Richard Purdie wrote:
> On Mon, 2019-06-10 at 12:47 +0100, Richard Purdie wrote:
> > On Sat, 2019-06-08 at 10:05 +0100, Richard Purdie wrote:
> > > On Fri, 2019-06-07 at 14:19 +0200, Alexander Kanavin wrote:
> > > > Rebase 0003-Add-disable-opengl-configure-option.patch
> > > > 
> > > > Signed-off-by: Alexander Kanavin 
> > > > ---
> > > >  ...-Add-disable-opengl-configure-option.patch | 41 ++-
> > > > --
> > > > --
> > > > --
> > > > --
> > > >  .../gtk+/{gtk+3_3.24.5.bb => gtk+3_3.24.8.bb} |  4 +-
> > > >  2 files changed, 23 insertions(+), 22 deletions(-)
> > > >  rename meta/recipes-gnome/gtk+/{gtk+3_3.24.5.bb =>
> > > > gtk+3_3.24.8.bb}
> > > > (84%)
> > > 
> > > I retested with the date/time on the workers fixed and this
> > > series
> > > present. We saw:
> > > 
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/47/builds/693
> > > 
> > > so I think there might be something not quite right with opengl
> > > disabled (the main difference to nodistro I can think of?)
> > 
> > Its now in master:
> > 
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/76/builds/687
> > 
> > so I think there is some kind of parallel make race in the new
> > gtk+?
> > 
> > The autobuilder is proving very tricky to read at the moment and
> > intermittent bugs are making it into master :(
> 
> I've realised the error wasn't:
> 
> Failed to open file “./gdk.gresource.xml”: No such file or directory
> 
> but
> 
> > glib-compile-resources --target=bloatpad-gresources.c --
> sourcedir=../../../gtk+-3.24.5/examples/bp --generate-source
> ../../../gtk+-3.24.5/examples/bp/bloatpad.gresources.xml
> > (glib-compile-resources:91029): GLib-ERROR **: 02:42:13.583:
> > creating
> thread 'gmain': Error creating thread: Resource temporarily
> unavailable
> > make[3]: *** [bloatpad-gresources.c] Trace/breakpoint trap
> 
> which sounds like a parallelism issue :/. Question is which resource
> we're running out of...

Looking at that machine, max user processes is 4096 which I think we've
had issues with in the past.

Cc'ing Michael.

Cheers,

Richard

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

Re: [OE-core] [PATCH 3/3] gtk+3: update 3.24.5 -> 3.24.8

2019-06-10 Thread Richard Purdie 
On Mon, 2019-06-10 at 12:47 +0100, Richard Purdie wrote:
> On Sat, 2019-06-08 at 10:05 +0100, Richard Purdie wrote:
> > On Fri, 2019-06-07 at 14:19 +0200, Alexander Kanavin wrote:
> > > Rebase 0003-Add-disable-opengl-configure-option.patch
> > > 
> > > Signed-off-by: Alexander Kanavin 
> > > ---
> > >  ...-Add-disable-opengl-configure-option.patch | 41 ++---
> > > --
> > > --
> > > --
> > >  .../gtk+/{gtk+3_3.24.5.bb => gtk+3_3.24.8.bb} |  4 +-
> > >  2 files changed, 23 insertions(+), 22 deletions(-)
> > >  rename meta/recipes-gnome/gtk+/{gtk+3_3.24.5.bb =>
> > > gtk+3_3.24.8.bb}
> > > (84%)
> > 
> > I retested with the date/time on the workers fixed and this series
> > present. We saw:
> > 
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/47/builds/693
> > 
> > so I think there might be something not quite right with opengl
> > disabled (the main difference to nodistro I can think of?)
> 
> Its now in master:
> 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/76/builds/687
> 
> so I think there is some kind of parallel make race in the new gtk+?
> 
> The autobuilder is proving very tricky to read at the moment and
> intermittent bugs are making it into master :(

I've realised the error wasn't:

Failed to open file “./gdk.gresource.xml”: No such file or directory

but

| glib-compile-resources --target=bloatpad-gresources.c --
sourcedir=../../../gtk+-3.24.5/examples/bp --generate-source
../../../gtk+-3.24.5/examples/bp/bloatpad.gresources.xml
| 
| (glib-compile-resources:91029): GLib-ERROR **: 02:42:13.583: creating
thread 'gmain': Error creating thread: Resource temporarily unavailable
| make[3]: *** [bloatpad-gresources.c] Trace/breakpoint trap

which sounds like a parallelism issue :/. Question is which resource
we're running out of...

Cheers,

Richard


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

[OE-core] ✗ patchtest: failure for "efivar: add..." and 1 more

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

Series: "efivar: add..." and 1 more
Revision: 1
URL   : https://patchwork.openembedded.org/series/18066/
State : failure

== Summary ==


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



* Issue Added patch file is missing Upstream-Status in the header 
[test_upstream_status_presence_format] 
  Suggested fixAdd Upstream-Status:  to the header of 
meta/recipes-bsp/efivar/efivar/0004-fix-unknow-option-for-gold-linker.patch
  Standard format  Upstream-Status: 
  Valid status Pending, Accepted, Backport, Denied, Inappropriate [reason], 
Submitted [where]



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

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

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

[OE-core] [PATCH 2/2] efibootmgr: add

2019-06-10 Thread Ross Burton 
This was in meta-oe but EFI is sufficiently wide spread now that we need it in
core.

Signed-off-by: Ross Burton 
---
 meta/recipes-bsp/efibootmgr/efibootmgr_17.bb   | 28 +++
 .../efibootmgr/files/0001-remove-extra-decl.patch  | 31 ++
 2 files changed, 59 insertions(+)
 create mode 100644 meta/recipes-bsp/efibootmgr/efibootmgr_17.bb
 create mode 100644 
meta/recipes-bsp/efibootmgr/files/0001-remove-extra-decl.patch

diff --git a/meta/recipes-bsp/efibootmgr/efibootmgr_17.bb 
b/meta/recipes-bsp/efibootmgr/efibootmgr_17.bb
new file mode 100644
index 000..4edb2e6644f
--- /dev/null
+++ b/meta/recipes-bsp/efibootmgr/efibootmgr_17.bb
@@ -0,0 +1,28 @@
+DESCRIPTION = "Linux user-space application to modify the EFI Boot Manager."
+SUMMARY = "EFI Boot Manager"
+HOMEPAGE = "https://github.com/rhinstaller/efibootmgr;
+SECTION = "base"
+
+LICENSE = "GPLv2+"
+LIC_FILES_CHKSUM = "file://COPYING;md5=0636e73ff0215e8d672dc4c32c317bb3"
+
+DEPENDS = "pciutils zlib efivar"
+
+COMPATIBLE_HOST = "(i.86|x86_64|arm|aarch64).*-linux"
+
+SRCREV = "e067160ecef8208e1944002e5d50b275733211fb"
+SRC_URI = "git://github.com/rhinstaller/efibootmgr.git;protocol=https \
+   file://0001-remove-extra-decl.patch \
+  "
+S = "${WORKDIR}/git"
+
+inherit pkgconfig
+
+EXTRA_OEMAKE = "'EFIDIR=/' 'CC=${CC}' 'CFLAGS=${CFLAGS} -I${S}/src/include 
`pkg-config --cflags efivar`'"
+
+CFLAGS_append_toolchain-clang = " -Wno-error"
+do_install () {
+install -D -p -m0755 ${B}/src/efibootmgr ${D}/${sbindir}/efibootmgr
+}
+
+CLEANBROKEN = "1"
diff --git a/meta/recipes-bsp/efibootmgr/files/0001-remove-extra-decl.patch 
b/meta/recipes-bsp/efibootmgr/files/0001-remove-extra-decl.patch
new file mode 100644
index 000..42f3a8182df
--- /dev/null
+++ b/meta/recipes-bsp/efibootmgr/files/0001-remove-extra-decl.patch
@@ -0,0 +1,31 @@
+From 99b578501643377e0b1994b2a068b790d189d5ad Mon Sep 17 00:00:00 2001
+From: Peter Jones 
+Date: Wed, 13 Jun 2018 09:41:01 -0400
+Subject: [PATCH] remove extra decl
+
+Signed-off-by: Peter Jones 
+
+Upstream-Status: Backport [git://github.com/rhinstaller/efibootmgr.git]
+Signed-off-by: Hongxu Jia 
+
+---
+ src/efibootmgr.c | 3 ---
+ 1 file changed, 3 deletions(-)
+
+diff --git a/src/efibootmgr.c b/src/efibootmgr.c
+index de38f01..4e1a680 100644
+--- a/src/efibootmgr.c
 b/src/efibootmgr.c
+@@ -1536,9 +1536,6 @@ parse_opts(int argc, char **argv)
+  "invalid numeric value %s\n",
+  optarg);
+   }
+-/* XXX efivar-36 accidentally doesn't have a public
+- * header for this */
+-  extern int efi_set_verbose(int verbosity, FILE *errlog);
+   efi_set_verbose(opts.verbose - 2, stderr);
+   break;
+   case 'V':
+-- 
+2.7.4
+
-- 
2.11.0

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

[OE-core] [PATCH 1/2] efivar: add

2019-06-10 Thread Ross Burton 
This was in meta-oe but EFI is sufficiently wide spread now that we need it in
core.

Signed-off-by: Ross Burton 
---
 .../efivar/0001-efivar-fix-for-cross-compile.patch | 32 
 .../0004-fix-unknow-option-for-gold-linker.patch   | 35 ++
 .../allow-multi-definitions-for-native.patch   | 36 ++
 meta/recipes-bsp/efivar/efivar_37.bb   | 43 ++
 4 files changed, 146 insertions(+)
 create mode 100644 
meta/recipes-bsp/efivar/efivar/0001-efivar-fix-for-cross-compile.patch
 create mode 100644 
meta/recipes-bsp/efivar/efivar/0004-fix-unknow-option-for-gold-linker.patch
 create mode 100644 
meta/recipes-bsp/efivar/efivar/allow-multi-definitions-for-native.patch
 create mode 100644 meta/recipes-bsp/efivar/efivar_37.bb

diff --git 
a/meta/recipes-bsp/efivar/efivar/0001-efivar-fix-for-cross-compile.patch 
b/meta/recipes-bsp/efivar/efivar/0001-efivar-fix-for-cross-compile.patch
new file mode 100644
index 000..251e50c902c
--- /dev/null
+++ b/meta/recipes-bsp/efivar/efivar/0001-efivar-fix-for-cross-compile.patch
@@ -0,0 +1,32 @@
+From a9115d9e6f0f62d6bb735ce3698858d1f89f8d73 Mon Sep 17 00:00:00 2001
+From: Kai Kang 
+Date: Fri, 25 Sep 2015 18:14:31 +0800
+Subject: [PATCH] efivar: fix for cross compile
+
+It builds and calls elf file makeguids to generate a header file which
+doesn't work for cross compile. Fix it.
+
+Signed-off-by: Kai Kang 
+
+Upstream-Status: Pending
+Signed-off-by: Hongxu Jia 
+
+---
+ src/Makefile | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/src/Makefile b/src/Makefile
+index 0c16597..dcc7fc8 100644
+--- a/src/Makefile
 b/src/Makefile
+@@ -40,8 +40,8 @@ abicheck : $(patsubst %.so,%.abicheck,$(LIBTARGETS))
+ ./guid-symbols.c : include/efivar/efivar-guids.h
+ ./guids.bin : include/efivar/efivar-guids.h
+ ./names.bin : include/efivar/efivar-guids.h
+-include/efivar/efivar-guids.h : makeguids guids.txt
+-  ./makeguids guids.txt guids.bin names.bin \
++include/efivar/efivar-guids.h : guids.txt
++  makeguids guids.txt guids.bin names.bin \
+   guid-symbols.c include/efivar/efivar-guids.h
+ 
+ makeguids : CPPFLAGS+=-DEFIVAR_BUILD_ENVIRONMENT
diff --git 
a/meta/recipes-bsp/efivar/efivar/0004-fix-unknow-option-for-gold-linker.patch 
b/meta/recipes-bsp/efivar/efivar/0004-fix-unknow-option-for-gold-linker.patch
new file mode 100644
index 000..96d0c6b3b28
--- /dev/null
+++ 
b/meta/recipes-bsp/efivar/efivar/0004-fix-unknow-option-for-gold-linker.patch
@@ -0,0 +1,35 @@
+From b3d35e7dd27a755df5acbe050837885914dbb28b Mon Sep 17 00:00:00 2001
+From: Hongxu Jia 
+Date: Tue, 10 May 2016 11:34:50 -0400
+Subject: [PATCH]  fix unknow option for gold linker
+
+- Revert the following patch, since oe-core work with gcc 5
+...
+commit 3055a3797f16693dfdd855fa68bc57fd900dc408
+Author: Peter Jones 
+Date:   Mon Feb 15 14:15:40 2016 -0500
+
+Make gcc.specs work with gcc 6 / binutils 2.26
+
+Apparently binutils 2.26 gets real picky about "ld -PIC" vs "ld -fPIC".
+
+Signed-off-by: Peter Jones 
+...
+
+- Remove unknown option '--add-needed'
+
+Signed-off-by: Hongxu Jia 
+---
+ gcc.specs | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+Index: git/gcc.specs
+===
+--- git.orig/gcc.specs
 git/gcc.specs
+@@ -14,4 +14,4 @@
+ + %{!shared:%{!static:%{!r:-pie}}} %{static:-Wl,-no-fatal-warnings 
-Wl,-static -static -Wl,-z,relro,-z,now}
+ 
+ *link:
+-+ %{!static:--fatal-warnings} --no-undefined-version 
--no-allow-shlib-undefined --add-needed -z now --build-id 
%{!static:%{!shared:-pie}} %{shared:-z relro} %{static:%
+Date: Tue, 31 Jul 2018 14:18:35 +0800
+Subject: [PATCH] allow multi definitions for native
+
+Upstream-Status: Pending
+
+It fails to create .so file when build efivar-native:
+
+| lib.o:(*IND*+0x0): multiple definition of `efi_set_variable'
+| lib.o:lib.c:(.text+0xa0): first defined here
+
+Add link option '-z muldefs' to fix it.
+
+Signed-off-by: Kai Kang 
+
+Signed-off-by: Hongxu Jia 
+---
+ Make.rules | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/Make.rules b/Make.rules
+index 042585b..257ba45 100644
+--- a/Make.rules
 b/Make.rules
+@@ -20,6 +20,7 @@ include $(TOPDIR)/Make.version
+   $(CCLD) $(ccldflags) $(CPPFLAGS) $(SOFLAGS) \
+ -Wl,-soname,$@.1 \
+ -Wl,--version-script=$(MAP) \
++-Wl,-z,muldefs \
+ -o $@ $^ $(LDLIBS)
+   ln -vfs $@ $@.1
+ 
+-- 
+2.7.4
+
diff --git a/meta/recipes-bsp/efivar/efivar_37.bb 
b/meta/recipes-bsp/efivar/efivar_37.bb
new file mode 100644
index 000..4b458dedd50
--- /dev/null
+++ b/meta/recipes-bsp/efivar/efivar_37.bb
@@ -0,0 +1,43 @@
+SUMMARY = "Tools to manipulate UEFI variables"
+DESCRIPTION = "efivar provides a simple command line interface to the UEFI 
variable facility"
+HOMEPAGE = "https://github.com/rhinstaller/efivar;
+
+LICENSE = "LGPLv2.1"
+LIC_FILES_CHKSUM =

[OE-core] Fwd: [yocto] Yocto Project DevDay NA 2019 - Extend your Embedded Linux Conference Experience

2019-06-10 Thread Philip Balister 
FYI

 Forwarded Message 
Subject: [yocto] Yocto Project DevDay NA 2019 - Extend your Embedded
Linux Conference Experience
Date: Tue, 4 Jun 2019 19:39:08 +
From: Volosincu, Andreea S 
To: Yocto list discussion 

Hello Everybody,

The registration for the Yocto Project DevDay NA 2019 is now open. Join
our knowledgeable and engaging instructors to learn about creating
custom-build Linux distributions using the Yocto Project infrastructure
and tools, across multiple architectures.

Date: Tuesday, August 20, 2019
Time: 9:00 am - 5:00 pm
Location: Hilton San Diego Bayfront

There are two ways to register - by adding it your ELC registration or
on the separate registration page.

Register now.


Best regards,
Yocto Project Advocacy Team


-- 
___
yocto mailing list
yo...@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

Re: [OE-core] [PATCH 3/3] gtk+3: update 3.24.5 -> 3.24.8

2019-06-10 Thread Richard Purdie 
On Sat, 2019-06-08 at 10:05 +0100, Richard Purdie wrote:
> On Fri, 2019-06-07 at 14:19 +0200, Alexander Kanavin wrote:
> > Rebase 0003-Add-disable-opengl-configure-option.patch
> > 
> > Signed-off-by: Alexander Kanavin 
> > ---
> >  ...-Add-disable-opengl-configure-option.patch | 41 ++-
> > --
> > --
> >  .../gtk+/{gtk+3_3.24.5.bb => gtk+3_3.24.8.bb} |  4 +-
> >  2 files changed, 23 insertions(+), 22 deletions(-)
> >  rename meta/recipes-gnome/gtk+/{gtk+3_3.24.5.bb =>
> > gtk+3_3.24.8.bb}
> > (84%)
> 
> I retested with the date/time on the workers fixed and this series
> present. We saw:
> 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/47/builds/693
> 
> so I think there might be something not quite right with opengl
> disabled (the main difference to nodistro I can think of?)

Its now in master:

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

so I think there is some kind of parallel make race in the new gtk+?

The autobuilder is proving very tricky to read at the moment and
intermittent bugs are making it into master :(

Cheers,

Richard

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