* [PATCH] python-3.5-manifest: Add http module to the netclient package
From: Derek Straka @ 2016-12-23 23:20 UTC (permalink / raw)
To: openembedded-core; +Cc: Derek Straka
Adding http module from Python's standard library. This allow use
of the http module without installing all python-misc modules.
Signed-off-by: Derek Straka <derek@asterius.io>
---
meta/recipes-devtools/python/python-3.5-manifest.inc | 2 +-
scripts/contrib/python/generate-manifest-3.5.py | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-devtools/python/python-3.5-manifest.inc b/meta/recipes-devtools/python/python-3.5-manifest.inc
index 7fcd871..b92048f 100644
--- a/meta/recipes-devtools/python/python-3.5-manifest.inc
+++ b/meta/recipes-devtools/python/python-3.5-manifest.inc
@@ -155,7 +155,7 @@ FILES_${PN}-multiprocessing="${libdir}/python3.5/lib-dynload/_multiprocessing.*.
SUMMARY_${PN}-netclient="Python Internet Protocol clients"
RDEPENDS_${PN}-netclient="${PN}-core ${PN}-crypt ${PN}-datetime ${PN}-io ${PN}-lang ${PN}-logging ${PN}-mime"
-FILES_${PN}-netclient="${libdir}/python3.5/*Cookie*.* ${libdir}/python3.5/__pycache__/*Cookie*.* ${libdir}/python3.5/base64.* ${libdir}/python3.5/__pycache__/base64.* ${libdir}/python3.5/cookielib.* ${libdir}/python3.5/__pycache__/cookielib.* ${libdir}/python3.5/ftplib.* ${libdir}/python3.5/__pycache__/ftplib.* ${libdir}/python3.5/gopherlib.* ${libdir}/python3.5/__pycache__/gopherlib.* ${libdir}/python3.5/hmac.* ${libdir}/python3.5/__pycache__/hmac.* ${libdir}/python3.5/httplib.* ${libdir}/python3.5/__pycache__/httplib.* ${libdir}/python3.5/mimetypes.* ${libdir}/python3.5/__pycache__/mimetypes.* ${libdir}/python3.5/nntplib.* ${libdir}/python3.5/__pycache__/nntplib.* ${libdir}/python3.5/poplib.* ${libdir}/python3.5/__pycache__/poplib.* ${libdir}/python3.5/smtplib.* ${libdir}/python3.5/__pycache__/smtplib.* ${libdir}/python3.5/telnetlib.* ${libdir}/python3.5/__pycache__/telnetlib.* ${libdir}/python3.5/urllib ${libdir}/python3.5/urllib/__pycache__ ${libdir}/python3.5/uuid.* ${libdir}/python3.5/__pycache__/uuid.* ${libdir}/python3.5/rfc822.* ${libdir}/python3.5/__pycache__/rfc822.* ${libdir}/python3.5/mimetools.* ${libdir}/python3.5/__pycache__/mimetools.* "
+FILES_${PN}-netclient="${libdir}/python3.5/*Cookie*.* ${libdir}/python3.5/__pycache__/*Cookie*.* ${libdir}/python3.5/base64.* ${libdir}/python3.5/__pycache__/base64.* ${libdir}/python3.5/cookielib.* ${libdir}/python3.5/__pycache__/cookielib.* ${libdir}/python3.5/ftplib.* ${libdir}/python3.5/__pycache__/ftplib.* ${libdir}/python3.5/gopherlib.* ${libdir}/python3.5/__pycache__/gopherlib.* ${libdir}/python3.5/hmac.* ${libdir}/python3.5/__pycache__/hmac.* ${libdir}/python3.5/http* ${libdir}/python3.5/http*/__pycache__ ${libdir}/python3.5/httplib.* ${libdir}/python3.5/__pycache__/httplib.* ${libdir}/python3.5/mimetypes.* ${libdir}/python3.5/__pycache__/mimetypes.* ${libdir}/python3.5/nntplib.* ${libdir}/python3.5/__pycache__/nntplib.* ${libdir}/python3.5/poplib.* ${libdir}/python3.5/__pycache__/poplib.* ${libdir}/python3.5/smtplib.* ${libdir}/python3.5/__pycache__/smtplib.* ${libdir}/python3.5/telnetlib.* ${libdir}/python3.5/__pycache__/telnetlib.* ${libdir}/python3.5/urllib ${libdir}/python3.5/urllib/__pycache__ ${libdir}/python3.5/uuid.* ${libdir}/python3.5/__pycache__/uuid.* ${libdir}/python3.5/rfc822.* ${libdir}/python3.5/__pycache__/rfc822.* ${libdir}/python3.5/mimetools.* ${libdir}/python3.5/__pycache__/mimetools.* "
SUMMARY_${PN}-netserver="Python Internet Protocol servers"
RDEPENDS_${PN}-netserver="${PN}-core ${PN}-netclient ${PN}-shell ${PN}-threading"
diff --git a/scripts/contrib/python/generate-manifest-3.5.py b/scripts/contrib/python/generate-manifest-3.5.py
index 897768f..7259543 100755
--- a/scripts/contrib/python/generate-manifest-3.5.py
+++ b/scripts/contrib/python/generate-manifest-3.5.py
@@ -320,7 +320,7 @@ if __name__ == "__main__":
m.addPackage( "${PN}-netclient", "Python Internet Protocol clients", "${PN}-core ${PN}-crypt ${PN}-datetime ${PN}-io ${PN}-lang ${PN}-logging ${PN}-mime",
"*Cookie*.* " +
- "base64.* cookielib.* ftplib.* gopherlib.* hmac.* httplib.* mimetypes.* nntplib.* poplib.* smtplib.* telnetlib.* urllib uuid.* rfc822.* mimetools.*" )
+ "base64.* cookielib.* ftplib.* gopherlib.* hmac.* http* httplib.* mimetypes.* nntplib.* poplib.* smtplib.* telnetlib.* urllib uuid.* rfc822.* mimetools.*" )
m.addPackage( "${PN}-netserver", "Python Internet Protocol servers", "${PN}-core ${PN}-netclient ${PN}-shell ${PN}-threading",
"cgi.* *HTTPServer.* SocketServer.*" )
--
2.7.4
^ permalink raw reply related
* Re: [PATCH 1/2] linux-libc-headers: introduce 4.9 headers
From: Bruce Ashfield @ 2016-12-25 3:33 UTC (permalink / raw)
To: Jussi Kukkonen; +Cc: Patches and discussions about the oe-core layer
In-Reply-To: <CAHiDW_E+G1JAEODj3w6Xda4CJkjHGOnBB0h035p093ZGP7WTqA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2424 bytes --]
On Fri, Dec 23, 2016 at 5:23 AM, Jussi Kukkonen <jussi.kukkonen@intel.com>
wrote:
> On 22 December 2016 at 16:49, Bruce Ashfield <bruce.ashfield@windriver.com>
> wrote:
> >
> > Bumping the linux-libc-headers to the 4.9 kernel variant. Since 4.9
> > will be a LTSI kernel, and there will be an associated linux-yocto
> > it is worth moving to these headers sooner rather than later.
> >
> > This commit also drops the 4.8 headers and sets 4.9 to be the default.
>
> The autobuilder run (ross/mut 1dc1894e05) with this had a couple of issues:
>
> *** ppp fails to build on musl: https://bugzilla.yoctoproject.
> org/show_bug.cgi?id=10853
>
Thanks for the update. Not knowing much about musl, others have jumped in
on these
in the past. I'll loop around and have a look at it if one of the musl
users doesn't have an
idea as to what is up with ppp.
>
>
> *** ncurses fails in several builds, all gnu/stubs.h related:
> ncurses was also upgraded in this AB run (CCing Huang Qiyu) but the
> failures seem more like libc related...
>
> x32:
> | nightly-x32/build/build/tmp/sysroots/qemux86-64/usr/include/gnu/stubs.h:10:27:
> fatal error: gnu/stubs-64.h: No such file or directory
> | # include <gnu/stubs-64.h>
>
> arm:
> | nightly-arm/build/build/tmp/sysroots/beaglebone/usr/include/gnu/stubs.h:7:29:
> fatal error: gnu/stubs-soft.h: No such file or directory
> | # include <gnu/stubs-soft.h>
>
> multilib:
> | nightly-multilib/build/build/tmp/sysroots/qemumips64/usr/include/gnu/stubs.h:35:33:
> fatal error: gnu/stubs-n64_hard.h: No such file or directory
> | # include <gnu/stubs-n64_hard.h>
>
> The full build log links can be found in "nightly 1121" section here:
> https://wiki.yoctoproject.org/wiki/BuildLog#nightly_1121_-_r
> oss.2Fmut_1dc1894e05ef0f3aeeefa61ed89613f17bba2e83
>
>
I'll have a look at these when I'm back in the office in January. x32 isn't
something that I build, but I did build sato, so this is something specific
to that config. Should be easy enough to reproduce on my builder.
Cheers,
Bruce
>
> Cheers,
> Jussi
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"
[-- Attachment #2: Type: text/html, Size: 3908 bytes --]
^ permalink raw reply
* Re: [PATCH 1/2] linux-libc-headers: introduce 4.9 headers
From: Bruce Ashfield @ 2016-12-26 2:34 UTC (permalink / raw)
To: Jussi Kukkonen; +Cc: Patches and discussions about the oe-core layer
In-Reply-To: <CAHiDW_E+G1JAEODj3w6Xda4CJkjHGOnBB0h035p093ZGP7WTqA@mail.gmail.com>
On 16-12-23 5:23 AM, Jussi Kukkonen wrote:
> On 22 December 2016 at 16:49, Bruce Ashfield
> <bruce.ashfield@windriver.com <mailto:bruce.ashfield@windriver.com>> wrote:
> >
> > Bumping the linux-libc-headers to the 4.9 kernel variant. Since 4.9
> > will be a LTSI kernel, and there will be an associated linux-yocto
> > it is worth moving to these headers sooner rather than later.
> >
> > This commit also drops the 4.8 headers and sets 4.9 to be the default.
>
> The autobuilder run (ross/mut 1dc1894e05) with this had a couple of issues:
>
> *** ppp fails to build on musl:
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=10853
>
> *** ncurses fails in several builds, all gnu/stubs.h related:
> ncurses was also upgraded in this AB run (CCing Huang Qiyu) but the
> failures seem more like libc related...
>
> x32:
> |
> nightly-x32/build/build/tmp/sysroots/qemux86-64/usr/include/gnu/stubs.h:10:27:
> fatal error: gnu/stubs-64.h: No such file or directory
> | # include <gnu/stubs-64.h>
>
> arm:
> |
> nightly-arm/build/build/tmp/sysroots/beaglebone/usr/include/gnu/stubs.h:7:29:
> fatal error: gnu/stubs-soft.h: No such file or directory
> | # include <gnu/stubs-soft.h>
FYI: I was just able to build all variants on ncurses on the branches
I have available.
I'm going to need a bit more direction on what branch/config to build
to see this breakage.
Bruce
>
> multilib:
> |
> nightly-multilib/build/build/tmp/sysroots/qemumips64/usr/include/gnu/stubs.h:35:33:
> fatal error: gnu/stubs-n64_hard.h: No such file or directory
> | # include <gnu/stubs-n64_hard.h>
>
> The full build log links can be found in "nightly 1121" section here:
> https://wiki.yoctoproject.org/wiki/BuildLog#nightly_1121_-_ross.2Fmut_1dc1894e05ef0f3aeeefa61ed89613f17bba2e83
>
>
> Cheers,
> Jussi
^ permalink raw reply
* [PATCH] iproute2 4.7.0 -> 4.9.0
From: Zheng Ruoqin @ 2016-12-26 6:15 UTC (permalink / raw)
To: openembedded-core
1) Upgrade iproute2 from 4.7.0 to 4.9.0
2) Add iproute2-4.9.0-musl.patch to fix musl compile problem
Signed-off-by: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com>
---
.../iproute2/iproute2/iproute2-4.9.0-musl.patch | 39 ++++++++++++++++++++++
.../{iproute2_4.7.0.bb => iproute2_4.9.0.bb} | 6 ++--
2 files changed, 43 insertions(+), 2 deletions(-)
create mode 100644 meta/recipes-connectivity/iproute2/iproute2/iproute2-4.9.0-musl.patch
rename meta/recipes-connectivity/iproute2/{iproute2_4.7.0.bb => iproute2_4.9.0.bb} (64%)
diff --git a/meta/recipes-connectivity/iproute2/iproute2/iproute2-4.9.0-musl.patch b/meta/recipes-connectivity/iproute2/iproute2/iproute2-4.9.0-musl.patch
new file mode 100644
index 0000000..241869b
--- /dev/null
+++ b/meta/recipes-connectivity/iproute2/iproute2/iproute2-4.9.0-musl.patch
@@ -0,0 +1,39 @@
+Subject: [PATCH] fix 4.9.0 musl compile problem
+
+Avoid in6_addr redefinition
+
+Signed-off-by: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com>
+---
+ include/linux/if_tunnel.h | 2 --
+ ip/ip6tunnel.c | 1 -
+ 2 files changed, 3 deletions(-)
+
+diff --git a/include/linux/if_tunnel.h b/include/linux/if_tunnel.h
+index 4f975f5..2680646 100644
+--- a/include/linux/if_tunnel.h
++++ b/include/linux/if_tunnel.h
+@@ -2,9 +2,7 @@
+ #define _IF_TUNNEL_H_
+
+ #include <linux/types.h>
+-#include <linux/if.h>
+ #include <linux/ip.h>
+-#include <linux/in6.h>
+ #include <asm/byteorder.h>
+
+
+diff --git a/ip/ip6tunnel.c b/ip/ip6tunnel.c
+index b1c0ae6..8fa4eb2 100644
+--- a/ip/ip6tunnel.c
++++ b/ip/ip6tunnel.c
+@@ -28,7 +28,6 @@
+ #include <arpa/inet.h>
+ #include <sys/ioctl.h>
+ #include <linux/ip.h>
+-#include <linux/if.h>
+ #include <linux/if_arp.h>
+ #include <linux/if_tunnel.h>
+ #include <linux/ip6_tunnel.h>
+--
+2.7.4
+
diff --git a/meta/recipes-connectivity/iproute2/iproute2_4.7.0.bb b/meta/recipes-connectivity/iproute2/iproute2_4.9.0.bb
similarity index 64%
rename from meta/recipes-connectivity/iproute2/iproute2_4.7.0.bb
rename to meta/recipes-connectivity/iproute2/iproute2_4.9.0.bb
index 426f989..389728d 100644
--- a/meta/recipes-connectivity/iproute2/iproute2_4.7.0.bb
+++ b/meta/recipes-connectivity/iproute2/iproute2_4.9.0.bb
@@ -4,9 +4,11 @@ SRC_URI = "${KERNELORG_MIRROR}/linux/utils/net/${BPN}/${BP}.tar.xz \
file://configure-cross.patch \
file://0001-iproute2-de-bash-scripts.patch \
file://iproute2-4.3.0-musl.patch \
+ file://iproute2-4.9.0-musl.patch \
"
-SRC_URI[md5sum] = "d4b205830cdc2702f8a0cbd6232129cd"
-SRC_URI[sha256sum] = "8f60dbcfb33a79daae0638f53bdcaa4310c0aa59ae39af8a234020dc69bb7b92"
+
+SRC_URI[md5sum] = "44a8371a4b2c40e48e4c9f98cbd41391"
+SRC_URI[sha256sum] = "c0f30f043f7767cc1b2cd2197b08d4e9b2392c95823fabe30bbce308c30116c4"
# CFLAGS are computed in Makefile and reference CCOPTS
#
--
2.7.4
^ permalink raw reply related
* State of bitbake world, Failed tasks 2016-12-24
From: Martin Jansa @ 2016-12-26 7:02 UTC (permalink / raw)
To: openembedded-core, openembedded-devel
[-- Attachment #1: Type: text/plain, Size: 32119 bytes --]
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks !!colspan='6'|Failed depencencies !!|Signatures !!colspan='12'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64 ||qemuarm||max||min ||qemux86||max||min ||all ||already-stripped ||libdir ||textrel ||build-deps ||file-rdeps ||version-going-backwards ||host-user-contaminated ||installed-vs-shipped ||unknown-configure-option ||symlink-to-sysroot ||invalid-pkgconfig ||pkgname ||
|-
||2016-12-24 ||6 ||9 ||7 ||13 ||6 ||6 ||19 ||9 ||9 ||0 ||0 ||0 ||0 ||9 ||0 ||0 ||0 ||2 ||2 ||0 ||0 ||0 ||
|}
http://www.openembedded.org/wiki/Bitbake_World_Status
== Failed tasks 2016-12-24 ==
INFO: jenkins-job.sh-1.8.12 Complete log available at http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.report.20161225_135809.log
=== common (5) ===
* meta-openembedded/meta-filesystems/recipes-utils/xfsprogs/xfsprogs_4.8.0.bb:do_compile
* meta-openembedded/meta-multimedia/recipes-mediacenter/kodi/kodi_16.bb:do_configure
* meta-openembedded/meta-oe/recipes-graphics/xorg-driver/xf86-video-glamo_git.bb:do_compile
* meta-openembedded/meta-webserver/recipes-php/xdebug/xdebug_2.2.6.bb:do_compile
* meta-qt5/recipes-qt/qt5/qtwayland_git.bb:do_configure
=== common-x86 (2) ===
* meta-openembedded/meta-oe/recipes-graphics/xorg-driver/xf86-video-ati_7.6.1.bb:do_compile
* meta-openembedded/meta-oe/recipes-graphics/xorg-driver/xf86-video-nouveau_1.0.12.bb:do_compile
=== qemuarm (1) ===
* meta-openembedded/meta-oe/recipes-benchmark/pmbw/pmbw_git.bb:do_compile
=== qemux86 (2) ===
* meta-browser/recipes-browser/chromium/chromium_52.0.2743.76.bb:do_compile
* meta-qt5/recipes-qt/qt5/qtwebengine_git.bb:do_compile
=== qemux86_64 (0) ===
=== Number of failed tasks (22) ===
{| class=wikitable
|-
|| qemuarm || 6 || http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.world.qemuarm.20161223_231203.log/ || http://errors.yoctoproject.org/Errors/Build/27711/
|-
|| qemux86 || 9 || http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.world.qemux86.20161224_182155.log/ || http://errors.yoctoproject.org/Errors/Build/27752/
|-
|| qemux86_64 || 7 || http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.world.qemux86-64.20161224_201438.log/ || http://errors.yoctoproject.org/Errors/Build/27759/
|}
=== PNBLACKLISTs (115) ===
=== QA issues (13) ===
{| class=wikitable
!| Count ||Issue
|-
||0 ||already-stripped
|-
||0 ||file-rdeps
|-
||0 ||host-user-contaminated
|-
||0 ||invalid-pkgconfig
|-
||0 ||libdir
|-
||0 ||pkgname
|-
||0 ||symlink-to-sysroot
|-
||0 ||textrel
|-
||0 ||version-going-backwards
|-
||2 ||installed-vs-shipped
|-
||2 ||unknown-configure-option
|-
||9 ||build-deps
|}
=== Failed dependencies for qemuarm (13) ===
Complete log: http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemuarm.20161224_015208.log/
Found differences:
Found errors:
* ERROR: 13 issues were found in these recipes: kodi pmbw qtwayland xdebug xf86-video-glamo xfsprogs
=== Recipes failing with maximal dependencies for qemuarm (6) ===
* kodi -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemuarm.20161224_015208.log//2_max/failed/kodi.log
* pmbw -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemuarm.20161224_015208.log//2_max/failed/pmbw.log
* qtwayland -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemuarm.20161224_015208.log//2_max/failed/qtwayland.log
* xdebug -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemuarm.20161224_015208.log//2_max/failed/xdebug.log
* xf86-video-glamo -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemuarm.20161224_015208.log//2_max/failed/xf86-video-glamo.log
* xfsprogs -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemuarm.20161224_015208.log//2_max/failed/xfsprogs.log
=== Recipes failing with minimal dependencies for qemuarm (6) ===
* kodi -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemuarm.20161224_015208.log//3_min/failed/kodi.log
* pmbw -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemuarm.20161224_015208.log//3_min/failed/pmbw.log
* qtwayland -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemuarm.20161224_015208.log//3_min/failed/qtwayland.log
* xdebug -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemuarm.20161224_015208.log//3_min/failed/xdebug.log
* xf86-video-glamo -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemuarm.20161224_015208.log//3_min/failed/xf86-video-glamo.log
* xfsprogs -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemuarm.20161224_015208.log//3_min/failed/xfsprogs.log
=== Failed dependencies for qemux86 (19) ===
Complete log: http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemux86.20161224_225749.log/
Found differences:
Found errors:
* ERROR: 19 issues were found in these recipes: chromium kodi qtwayland qtwebengine xdebug xf86-video-ati xf86-video-glamo xf86-video-nouveau xfsprogs
=== Recipes failing with maximal dependencies for qemux86 (9) ===
* chromium -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemux86.20161224_225749.log//2_max/failed/chromium.log
* kodi -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemux86.20161224_225749.log//2_max/failed/kodi.log
* qtwayland -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemux86.20161224_225749.log//2_max/failed/qtwayland.log
* qtwebengine -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemux86.20161224_225749.log//2_max/failed/qtwebengine.log
* xdebug -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemux86.20161224_225749.log//2_max/failed/xdebug.log
* xf86-video-ati -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemux86.20161224_225749.log//2_max/failed/xf86-video-ati.log
* xf86-video-glamo -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemux86.20161224_225749.log//2_max/failed/xf86-video-glamo.log
* xf86-video-nouveau -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemux86.20161224_225749.log//2_max/failed/xf86-video-nouveau.log
* xfsprogs -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemux86.20161224_225749.log//2_max/failed/xfsprogs.log
=== Recipes failing with minimal dependencies for qemux86 (9) ===
* chromium -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemux86.20161224_225749.log//3_min/failed/chromium.log
* kodi -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemux86.20161224_225749.log//3_min/failed/kodi.log
* qtwayland -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemux86.20161224_225749.log//3_min/failed/qtwayland.log
* qtwebengine -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemux86.20161224_225749.log//3_min/failed/qtwebengine.log
* xdebug -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemux86.20161224_225749.log//3_min/failed/xdebug.log
* xf86-video-ati -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemux86.20161224_225749.log//3_min/failed/xf86-video-ati.log
* xf86-video-glamo -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemux86.20161224_225749.log//3_min/failed/xf86-video-glamo.log
* xf86-video-nouveau -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemux86.20161224_225749.log//3_min/failed/xf86-video-nouveau.log
* xfsprogs -- http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.dependencies.qemux86.20161224_225749.log//3_min/failed/xfsprogs.log
=== Incorrect PACKAGE_ARCH or sstate signatures (0) ===
Complete log: http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.signatures.20161224_050112.log/
No issues detected
PNBLACKLISTs:
openembedded-core/:
meta-browser:
recipes-browser/chromium/cef3_280796.bb:PNBLACKLIST[cef3] ?= "BROKEN: fails to build with gcc-6"
meta-openembedded:
meta-efl/recipes-efl/e17/diskio_svn.bb:PNBLACKLIST[diskio] ?= "broken: switch to https://git.enlightenment.org/enlightenment/modules/diskio.git/ and fix 0.0.1+svnr82070-r0.0/E-MODULES-EXTRA/diskio/e-module-diskio.edc:58. invalid state name: 'off'. "default" state must always be first."
meta-efl/recipes-efl/e17/elbow_git.bb:PNBLACKLIST[elbow] ?= "Depends on blacklisted webkit-efl"
meta-efl/recipes-efl/e17/elmdentica_svn.bb:PNBLACKLIST[elmdentica] ?= "OLD and depends on broken azy"
meta-efl/recipes-efl/e17/emprint_svn.bb:PNBLACKLIST[emprint] ?= "if you want to use these modules with E18, then you need to update it to git recipe fetching newer sources from http://git.enlightenment.org/apps/emprint.git/"
meta-efl/recipes-efl/e17/news_svn.bb:PNBLACKLIST[news] ?= "if you want to use these modules with E18, then you need to update it to git recipe fetching newer sources from http://git.enlightenment.org/enlightenment/modules/news.git/"
meta-efl/recipes-efl/e17/rage_svn.bb:PNBLACKLIST[rage] ?= "if you want to use these modules with E18, then you need to update it to git recipe fetching newer sources from http://git.enlightenment.org/apps/rage.git/"
meta-efl/recipes-efl/e17/screenshot_svn.bb:PNBLACKLIST[screenshot] ?= "depends on blacklisted emprint"
meta-efl/recipes-efl/efl/azy_svn.bb:PNBLACKLIST[azy] ?= "OLD and doesn't build with gcc-5"
meta-efl/recipes-efl/efl/engrave_svn.bb:PNBLACKLIST[engrave] ?= "BROKEN: fails to build with latest oe-core"
meta-efl/recipes-efl/efl/entrance_svn.bb:PNBLACKLIST[entrance] ?= "broken: switch to https://git.enlightenment.org/misc/entrance.git and fix 0.0.4+svnr82070-r7/entrance/data/themes/old/default.edc:678. invalid state name: 'defaault'. "default" state must always be first."
meta-efl/recipes-efl/webkit/webkit-efl.inc:PNBLACKLIST[webkit-efl] ?= "Old and unmaintaned fork with many security issues"
meta-efl/recipes-navigation/mcnavi/mcnavi_0.3.4.bb:PNBLACKLIST[mcnavi] ?= "BROKEN: latest version 0.3.4 is 3 years old and now broken with more strict ejde_cc from efl-1.13"
meta-filesystems/recipes-utils/dmapi/dmapi_2.2.12.bb:PNBLACKLIST[dmapi] ?= "Depends on broken xfsprogs"
meta-filesystems/recipes-utils/xfsdump/xfsdump_3.1.4.bb:PNBLACKLIST[xfsdump] ?= "Depends on broken xfsprogs"
meta-gnome/recipes-apps/epdfview/epdfview_0.1.8.bb:PNBLACKLIST[epdfview] ?= "BROKEN: images are not displayed anymore"
meta-gnome/recipes-apps/gnome-mplayer/gnome-mplayer_1.0.5.bb:PNBLACKLIST[gnome-mplayer] ?= "rdepends on blacklisted mplayer"
meta-gnome/recipes-extended/gtk-theme-torturer/gtk-theme-torturer_git.bb:PNBLACKLIST[gtk-theme-torturer] ?= "BROKEN: gmacros.h:182:53: error: size of array '_GStaticAssertCompileTimeAssertion_2' is negative"
meta-gnome/recipes-gnome/gcalctool/gcalctool_5.32.0.bb:PNBLACKLIST[gcalctool] ?= "broken at least since April 2013 http://permalink.gmane.org/gmane.comp.handhelds.openembedded/57920 and nobody complained, it's also replaced by gnome calculator"
meta-gnome/recipes-gnome/gdm/gdm_2.32.2.bb:PNBLACKLIST[gdm] ?= "Depends on broken gnome-panel"
meta-gnome/recipes-gnome/gnome-control-center/gnome-control-center_2.32.1.bb:PNBLACKLIST[gnome-control-center] ?= "Depends on broken gnome-menus"
meta-gnome/recipes-gnome/gnome-keyring/gnome-keyring_2.32.1.bb:PNBLACKLIST[gnome-keyring] ?= "This version conflicts with gcr from oe-core"
meta-gnome/recipes-gnome/gnome-menus/gnome-menus_2.30.5.bb:PNBLACKLIST[gnome-menus] ?= "BROKEN: fails to build because of python + conflicts with gnome-menu3"
meta-gnome/recipes-gnome/gnome-panel/gnome-panel3_3.0.2.bb:PNBLACKLIST[gnome-panel3] ?= "CONFLICT: depends on libgweather3 which conflicts with libgweather"
meta-gnome/recipes-gnome/gnome-panel/gnome-panel3_3.0.2.bb:PNBLACKLIST[gnome-panel3] ?= "Depends on broken gnome-menus"
meta-gnome/recipes-gnome/gnome-panel/gnome-panel_2.32.1.bb:PNBLACKLIST[gnome-panel] ?= "Depends on broken libgweather"
meta-gnome/recipes-gnome/gnome-power-manager/gnome-power-manager_2.32.0.bb:PNBLACKLIST[gnome-power-manager] ?= "BROKEN: not compatible with current libnotify"
meta-gnome/recipes-gnome/gnome-session/gnome-session_2.32.1.bb:PNBLACKLIST[gnome-session] ?= "BROKEN: fails to build with gcc-6"
meta-gnome/recipes-gnome/gnome/gnome-terminal_2.30.2.bb:PNBLACKLIST[gnome-terminal] ?= "BROKEN: fails to build with gcc-6"
meta-gnome/recipes-gnome/gnome/libgnomecups_0.2.3.bb:PNBLACKLIST[libgnomecups] ?= "Depends on broken libgnomeui"
meta-gnome/recipes-gnome/gnome/libgnomeprint_2.18.8.bb:PNBLACKLIST[libgnomeprint] ?= "Depends on broken libgnomecups"
meta-gnome/recipes-gnome/gnumeric/gnumeric_1.12.0.bb:PNBLACKLIST[gnumeric] ?= "Depends on broken libgnomeprint"
meta-gnome/recipes-gnome/gweather/libgweather3_3.0.2.bb:PNBLACKLIST[libgweather3] ?= "CONFLICT: 876 files are conflicting with libgweather"
meta-gnome/recipes-gnome/gweather/libgweather_2.30.3.bb:PNBLACKLIST[libgweather] ?= "BROKEN: fails to build with gcc-6"
meta-gnome/recipes-gnome/nautilus/nautilus3_3.2.1.bb:PNBLACKLIST[nautilus3] ?= "BROKEN: fails to build, maybe missing dependency on gnome-desktop-utils.h provider"
meta-gnome/recipes-gnome/pimlico/tasks_0.19.bb:PNBLACKLIST[tasks] ?= "Fails to build with gcc-6"
meta-gnome/recipes-gnome/pimlico/tasks_git.bb:PNBLACKLIST[tasks] ?= "Fails to build with gcc-6"
meta-gnome/recipes-gnome/system-tools/system-tools-backends_2.10.2.bb:PNBLACKLIST[system-tools-backends] ?= "does not build with distroless qemuarm as reported in 'State of bitbake world' thread, nobody volunteered to fix them"
meta-gnome/recipes-gnome/zenity/zenity_2.32.1.bb:PNBLACKLIST[zenity] ?= "BROKEN: doesn't build with B!=S"
meta-gnome/recipes-support/goffice/goffice_0.10.1.bb:PNBLACKLIST[goffice] ?= "BROKEN: fails to build with gcc-6"
meta-gnome/recipes-support/tracker/tracker_0.14.2.bb:PNBLACKLIST[tracker] ?= "BROKEN: fails to build with new binutils-2.27"
meta-gpe/recipes-support/fbreader/fbreader_git.bb:PNBLACKLIST[fbreader] ?= "BROKEN: fails to build with gcc-6"
meta-multimedia/recipes-mkv/mkvtoolnix/mkvtoolnix_git.bb:PNBLACKLIST[mkvtoolnix] ?= "BROKEN: Failx to build with gcc-5"
meta-multimedia/recipes-multimedia/coriander/coriander_2.0.2.bb:PNBLACKLIST[coriander] ?= "BROKEN: fails to use SDL probably because libsdl-config was removed, error: unknown type name 'SDL_Overlay'"
meta-multimedia/recipes-multimedia/dleyna/renderer-service-upnp_0.3.0.bb:PNBLACKLIST[renderer-service-upnp] ?= "BROKEN: doesn't build with B!=S (trying to install rendererconsole.py from ${B} instead of ${S})"
meta-multimedia/recipes-multimedia/gstreamer-0.10/gst-ffmpeg_0.10.13.bb:PNBLACKLIST[gst-ffmpeg] ?= "Not compatible with currently used ffmpeg 3"
meta-multimedia/recipes-multimedia/gstreamer/gst123_0.3.1.bb:PNBLACKLIST[gst123] ?= "gst123 is still "sometimes" using wrong sysroot"
meta-networking/recipes-daemons/dnrd/dnrd_2.20.3.bb:PNBLACKLIST[dnrd] ?= "BROKEN: dnrd-2.20.3-r0 do_package: QA Issue: dnrd: Files/directories were installed but not shipped in any package:"
meta-networking/recipes-kernel/netmap/netmap-modules_git.bb:PNBLACKLIST[netmap-modules] ?= "BROKEN: not compatible with default kernel version 4.8"
meta-networking/recipes-kernel/netmap/netmap_git.bb:PNBLACKLIST[netmap] ?= "BROKEN: Tries to build kernel module and fails, either it should be disabled or there should be dependency on kernel like in netmap-modules"
meta-networking/recipes-protocols/accel-ppp/accel-ppp_git.bb:PNBLACKLIST[accel-ppp] ?= "BROKEN: fails to build with new binutils-2.27"
meta-networking/recipes-support/lksctp-tools/lksctp-tools_1.0.17.bb:PNBLACKLIST[lksctp-tools] ?= "${@bb.utils.contains('DISTRO_FEATURES', 'ld-is-gold', "BROKEN: fails to link against sctp_connectx symbol", '', d)}"
meta-networking/recipes-support/nis/ypbind-mt_2.2.bb:PNBLACKLIST[ypbind-mt] ?= "BROKEN: Depends on broken yp-tools"
meta-oe/recipes-connectivity/bluez/bluez-hcidump_2.5.bb:PNBLACKLIST[bluez-hcidump] ?= "${@bb.utils.contains('DISTRO_FEATURES', 'bluez5', 'bluez5 conflicts with bluez4 and bluez5 is selected in DISTRO_FEATURES', '', d)}"
meta-oe/recipes-connectivity/bluez/bluez4_4.101.bb:PNBLACKLIST[bluez4] ?= "${@bb.utils.contains('DISTRO_FEATURES', 'bluez5', 'bluez5 conflicts with bluez4 and bluez5 is selected in DISTRO_FEATURES', '', d)}"
meta-oe/recipes-connectivity/bluez/gst-plugin-bluetooth_4.101.bb:PNBLACKLIST[gst-plugin-bluetooth] ?= "${@bb.utils.contains('DISTRO_FEATURES', 'bluez5', 'bluez5 conflicts with bluez4 and bluez5 is selected in DISTRO_FEATURES', '', d)}"
meta-oe/recipes-connectivity/soft66/soft66_git.bb:PNBLACKLIST[soft66] ?= "BROKEN: depends on broken libftdi"
meta-oe/recipes-connectivity/wvdial/wvdial_1.61.bb:PNBLACKLIST[wvdial] ?= "Depends on broken wvstreams"
meta-oe/recipes-connectivity/wvdial/wvstreams_4.6.1.bb:PNBLACKLIST[wvstreams] ?= "BROKEN: fails to build with gcc-6"
meta-oe/recipes-connectivity/zeroc-ice/zeroc-ice_3.5.1.bb:PNBLACKLIST[zeroc-ice] ?= "BROKEN: not compatible with default db version"
meta-oe/recipes-core/fakeroot/fakeroot_1.18.4.bb:PNBLACKLIST[fakeroot] ?= "BROKEN: QA Issue: -dev package contains non-symlink .so"
meta-oe/recipes-devtools/cloud9/cloud9_0.6.bb:PNBLACKLIST[cloud9] ?= "Not comatible with current nodejs 0.12, but upstream is working on it for v3"
meta-oe/recipes-devtools/ltp-ddt/ltp-ddt_1.0.0.bb:PNBLACKLIST[ltp-ddt] ?= "BROKEN: fails since last autotools.bbclass changes"
meta-oe/recipes-devtools/packagekit/packagekit_0.5.6.bb:PNBLACKLIST[packagekit] ?= "BROKEN: depends on old deprecated libopkg which is currently disabled and will be removed soon"
meta-oe/recipes-extended/subsurface/subsurface_git.bb:PNBLACKLIST[subsurface] ?= "Needs to be upgraded for compatibility with new libdivecomputer"
meta-oe/recipes-gnome/gtkextra/gtkextra_3.0.5.bb:PNBLACKLIST[gtkextra] ?= "BROKEN: Fails to build with gcc-5"
meta-oe/recipes-graphics/clutter/clutter-box2d_git.bb:PNBLACKLIST[clutter-box2d] ?= "BROKEN: doesn't build with B!=S"
meta-oe/recipes-graphics/fim/fim_0.4-rc1.bb:PNBLACKLIST[fim] ?= "BROKEN: doesn't build with B!=S (flex: can't open lex.lex)"
meta-oe/recipes-graphics/slim/slim_1.3.2.bb:PNBLACKLIST[slim] ?= "does not build with distroless qemuarm as reported in 'State of bitbake world' thread, nobody volunteered to fix them"
meta-oe/recipes-graphics/xorg-driver/xf86-input-mtev_git.bb:PNBLACKLIST[xf86-input-mtev] ?= "BROKEN: doesn't build with B!=S (Makefile without ${S} in sed call)"
meta-oe/recipes-graphics/xorg-driver/xf86-video-geode_2.11.16.bb:PNBLACKLIST[xf86-video-geode] ?= "BROKEN, fails to build"
meta-oe/recipes-kernel/ktap/ktap-module_git.bb:PNBLACKLIST[ktap-module] ?= "Not compatible with 3.19 kernel"
meta-oe/recipes-kernel/ktap/ktap_git.bb:PNBLACKLIST[ktap] ?= "Depends on blacklisted kernel-module-ktapvm"
meta-oe/recipes-multimedia/mplayer/mplayer2_git.bb:PNBLACKLIST[mplayer2] ?= "Not compatible with currently used ffmpeg 3"
meta-oe/recipes-navigation/foxtrotgps/foxtrotgps_1.1.1.bb:PNBLACKLIST[foxtrotgps] ?= "${@bb.utils.contains('DISTRO_FEATURES', 'bluez5', 'bluez5 conflicts with bluez4 and bluez5 is selected in DISTRO_FEATURES', '', d)}"
meta-oe/recipes-navigation/gdal/gdal_1.11.1.bb:PNBLACKLIST[gdal] ?= "BROKEN: fails to build with gcc-5"
meta-oe/recipes-navigation/gypsy/gypsy.inc:PNBLACKLIST[gypsy] ?= "${@bb.utils.contains('DISTRO_FEATURES', 'bluez5', 'bluez5 conflicts with bluez4 and bluez5 is selected in DISTRO_FEATURES', '', d)}"
meta-oe/recipes-navigation/navit/navit.inc:PNBLACKLIST[navit] ?= "${@bb.utils.contains('DISTRO_FEATURES', 'bluez5', 'bluez5 conflicts with bluez4 and bluez5 is selected in DISTRO_FEATURES', '', d)}"
meta-oe/recipes-sato/claws-mail/claws-mail_3.9.0.bb:PNBLACKLIST[claws-mail] ?= "depends on blacklisted libetpan"
meta-oe/recipes-sato/claws-mail/claws-plugin-gtkhtml2-viewer_0.31.bb:PNBLACKLIST[claws-plugin-gtkhtml2-viewer] ?= "depends on blacklisted claws-mail"
meta-oe/recipes-sato/claws-mail/claws-plugin-mailmbox_1.15.bb:PNBLACKLIST[claws-plugin-mailmbox] ?= "depends on blacklisted claws-mail"
meta-oe/recipes-sato/claws-mail/claws-plugin-rssyl_0.34.bb:PNBLACKLIST[claws-plugin-rssyl] ?= "depends on blacklisted claws-mail"
meta-oe/recipes-support/apcupsd/apcupsd_3.14.10.bb:PNBLACKLIST[apcupsd] ?= "BROKEN: doesn't build with B!=S"
meta-oe/recipes-support/emacs/emacs_23.4.bb:PNBLACKLIST[emacs] ?= "qemu: uncaught target signal 11 (Segmentation fault) - core dumped"
meta-oe/recipes-support/fftw/benchfft_3.1.bb:PNBLACKLIST[benchfft] ?= "does not build with distroless qemuarm as reported in 'State of bitbake world' thread, nobody volunteered to fix them"
meta-oe/recipes-support/iksemel/iksemel_1.4.bb:PNBLACKLIST[iksemel] ?= "Not compatible with gnutls version 3.4 currently in oe-core"
meta-oe/recipes-support/libdbi/libdbi-drivers_0.8.3-1.bb:PNBLACKLIST[libdbi-drivers] ?= "BROKEN: fails to build with gcc-5"
meta-oe/recipes-support/libetpan/libetpan_0.57.bb:PNBLACKLIST[libetpan] ?= "Not compatible with gnutls version 3.4 currently in oe-core"
meta-oe/recipes-support/open-vcdiff/open-vcdiff_0.8.4.bb:PNBLACKLIST[open-vcdiff] ?= "BROKEN: fails to build with gcc-6"
meta-oe/recipes-support/opencv/opencv-samples_2.4.bb:PNBLACKLIST[opencv-samples] ?= "Depends on blacklisted opencv"
meta-oe/recipes-support/opencv/opencv_2.4.bb:PNBLACKLIST[opencv] ?= "Not compatible with currently used ffmpeg 3"
meta-oe/recipes-support/openmotif/openmotif_2.3.3.bb:PNBLACKLIST[openmotif] ?= "BROKEN: doesn't build with B!=S"
meta-oe/recipes-support/opensync/libsyncml_0.5.4.bb:PNBLACKLIST[libsyncml] ?= "${@bb.utils.contains('DISTRO_FEATURES', 'bluez5', 'bluez5 conflicts with bluez4 and bluez5 is selected in DISTRO_FEATURES', '', d)}"
meta-oe/recipes-support/openwbem/openwbem_3.2.3.bb:PNBLACKLIST[openwbem] ?= "BROKEN: fails to build with gcc-6"
meta-oe/recipes-support/pidgin/pidgin-otr_4.0.0.bb:PNBLACKLIST[pidgin-otr] ?= "depends on blacklisted pidgin"
meta-oe/recipes-support/vala-terminal/vala-terminal_git.bb:PNBLACKLIST[vala-terminal] ?= "BROKEN: Doesn't work with B!=S, touch: cannot touch `src/.stamp': No such file or directory"
meta-oe/recipes-support/vboxguestdrivers/vboxguestdrivers_4.3.36.bb:PNBLACKLIST[vboxguestdrivers] ?= "BROKEN: not compatible with default kernel version 4.8"
meta-qt5:
meta-smartphone:
meta-fso/recipes-freesmartphone/freesmartphone/libframeworkd-glib_git.bb:PNBLACKLIST[libframeworkd-glib] ?= "BROKEN: many errors when building with gcc-6"
meta-fso/recipes-freesmartphone/freesmartphone/zhone_git.bb:PNBLACKLIST[zhone] ?= "rdepends on python-pycairo which was removed"
meta-shr/recipes-shr/3rdparty/advancedcaching_git.bb:PNBLACKLIST[advancedcaching] ?= "RDEPENDS on python-pygtk was removed from oe-core"
meta-shr/recipes-shr/3rdparty/emtooth2_svn.bb:PNBLACKLIST[emtooth2] ?= "${@bb.utils.contains('DISTRO_FEATURES', 'bluez5', 'bluez5 conflicts with bluez4 and bluez5 is selected in DISTRO_FEATURES', '', d)}"
meta-shr/recipes-shr/3rdparty/ffalarms_git.bb:PNBLACKLIST[ffalarms] = "Doesn't build after vala upgrade from 0.24.0 to 0.26.1"
meta-shr/recipes-shr/3rdparty/gwaterpas_0.3.bb:PNBLACKLIST[gwaterpas] ?= "broken: depends on blacklisted fltk"
meta-shr/recipes-shr/3rdparty/iliwi_git.bb:PNBLACKLIST[iliwi] = "Doesn't build after vala upgrade from 0.24.0 to 0.26.1"
meta-shr/recipes-shr/3rdparty/intone_git.bb:PNBLACKLIST[intone] = "rdepends on blacklisted mplayer2"
meta-shr/recipes-shr/3rdparty/jefliks_git.bb:PNBLACKLIST[jefliks] ?= "depends on blacklisted iksemel"
meta-shr/recipes-shr/3rdparty/openmoko-gps_svn.bb:PNBLACKLIST[openmoko-gps] ?= "RDEPENDS on python-pygtk which was removed from oe-core"
meta-shr/recipes-shr/3rdparty/pisi_0.5.3.bb:PNBLACKLIST[pisi] ?= "RDEPENDS on python-pygtk which was removed from oe-core"
meta-shr/recipes-shr/3rdparty/podboy_svn.bb:PNBLACKLIST[podboy] ?= "${@bb.utils.contains('DISTRO_FEATURES', 'bluez5', 'bluez5 ger.bb:PNBLACKLIST[luna-webappmanager] ?= "BROKEN: needs to be adapted to new qt-5.7"
meta-luneui/recipes-luneui/luna-next/luna-next.bb:PNBLACKLIST[luna-next] ?= "BROKEN: needs to be adapted to new qtwayland-5.7"
PNBLACKLIST[android-system] = "depends on lxc from meta-virtualiazation which isn't included in my world builds"
PNBLACKLIST[bigbuckbunny-1080p] = "big and doesn't really need to be tested so much"
PNBLACKLIST[bigbuckbunny-480p] = "big and doesn't really need to be tested so much"
PNBLACKLIST[bigbuckbunny-720p] = "big and doesn't really need to be tested so much"
PNBLACKLIST[bigbuckbunny-720p] = "big and doesn't really need to be tested so much"
PNBLACKLIST[tearsofsteel-1080p] = "big and doesn't really need to be tested so much"
PNBLACKLIST[build-appliance-image] = "tries to include whole downloads directory in /home/builder/poky :/"
PNBLACKLIST[linux-yocto-tiny-kexecboot] = "does weird sh!t breaking other kernels and modules - broken for years"
PNBLACKLIST[linux-yocto-tiny] = "does weird sh!t breaking other kernels and modules - broken for years"
QA issues by type:
count: 0 issue: already-stripped
count: 0 issue: libdir
count: 0 issue: textrel
count: 9 issue: build-deps
hwloc-1.11.5: hwloc rdepends on cairo, but it isn't a build dependency, missing cairo in DEPENDS or PACKAGECONFIG? [build-deps]
hwloc-1.11.5: hwloc rdepends on libcap, but it isn't a build dependency, missing libcap in DEPENDS or PACKAGECONFIG? [build-deps]
hwloc-1.11.5: hwloc rdepends on libpciaccess, but it isn't a build dependency, missing libpciaccess in DEPENDS or PACKAGECONFIG? [build-deps]
hwloc-1.11.5: hwloc rdepends on libudev, but it isn't a build dependency, missing systemd in DEPENDS or PACKAGECONFIG? [build-deps]
hwloc-1.11.5: hwloc rdepends on libx11, but it isn't a build dependency, missing libx11 in DEPENDS or PACKAGECONFIG? [build-deps]
hwloc-1.11.5: hwloc rdepends on libxml2, but it isn't a build dependency, missing libxml2 in DEPENDS or PACKAGECONFIG? [build-deps]
hwloc-1.11.5: hwloc rdepends on ncurses-libtinfo, but it isn't a build dependency, missing ncurses in DEPENDS or PACKAGECONFIG? [build-deps]
hwloc-1.11.5: hwloc rdepends on numactl, but it isn't a build dependency, missing numactl in DEPENDS or PACKAGECONFIG? [build-deps]
hwloc-1.11.5: hwloc rdepends on zlib, but it isn't a build dependency, missing zlib in DEPENDS or PACKAGECONFIG? [build-deps]
count: 0 issue: file-rdeps
count: 0 issue: version-going-backwards
count: 0 issue: host-user-contaminated
count: 2 issue: installed-vs-shipped
hwloc: 71 installed and not shipped files. [installed-vs-shipped]
hwloc: 75 installed and not shipped files. [installed-vs-shipped]
count: 2 issue: unknown-configure-option
php-7.1.0: php: configure was passed unrecognised options: --with-mysql [unknown-configure-option]
php-native-7.1.0: php-native: configure was passed unrecognised options: --without-mysql [unknown-configure-option]
count: 0 issue: symlink-to-sysroot
count: 0 issue: invalid-pkgconfig
count: 0 issue: pkgname
== Tested changes (not included in master yet) - bitbake ==
latest upstream commit:
518b901 cookerdata: Convert multiconfig to use BB_CURRENT_MC
not included in master yet:
2cb8091 world-image: add extra target
== Tested changes (not included in master yet) - openembedded-core ==
latest upstream commit:
425afe2 lib/oe/utils: Drop python2 compatibility code
not included in master yet:
be963df qemux86: Add identical qemux86copy variant for tests
788c84b sstate-sysroot-cruft.sh: Extend the whitelist
5346d16 recipes: Replace "cp -a" wund access in create_url_list() (CVE-2016-8863)
c20e42a protobuf: switch from mips16 to mips32 due to in-line assembler
a43fd54 php: add 7.1.0 remove 5.5.38
233520e opencv: Update repository location
b2349d6 opencv: Metapkg should not rdepend on -staticdev
a9e59cb opencv: Add missing depends
88e8255 opencv: Add support for OpenJDK
eb626dc opencv: Add support for python3
dc83100 opencv: Add missing DEPEND for opencl PKGCFG
340b5df opencv: Add new PACKAGECONFIG dnn
6c2db38 opencv: Merge dbg packages and Fix QA Issues
3c0427f tinymembench: fix QA warning for GNU_HASH
3e2a164 libmng: Add recipe
5b9895d zbar: Add recipe
0bd5590 avro: Add recipe
00712a8 liboop: Add recipe
79c0c20 gimp: Enable libmng plugins
b8f1c0b gtest, gmock: update 1.7.0 -> 1.8.0
9a86b8a dibbler: add initial recipe, dibbler 1.0.1
7bdd54f zlog: Add recipe
2b89622 usrsctp: Add recipe
d61410d poppler: Disable PIE, it does not compile
bf68f19 audiofile: update to 0.3.6
7856f0c esound: fix build after update of audiofile
790de05 hplip: Fix build with clang
7860ff4 xfsprogs: Fix parallel install and Make dependencies
e8c9a01 rapidjson: add initial recipe
fed7fa1 gst-plugins-bad_0.10.23.bb: Add packageconfig for zbar plugin
d07aadd directfb: Disable vdpau x11 spport
6f7e56a python-pygobject: 3.20.1 -> 3.22.0
6bc5fd6 cxxtest: Add CxxTest framework to recipe-devtools.
c1199fd pmbw: add recipe for ram benchmarks
e3d0cef python-urllib3: update to version 1.19.1
0572182 yajl_1.0.12: Add recipe for yajl1
81f614b opensaf: 5.0.0 -> 5.1.0
919a209 python-lxml: update to version 3.7.0
4a904a7 python-dominate: update to version 2.3.1
ee90133 apache2: update to version 2.4.25
0c7bc57 python-passlib: update to version 1.7.0
2b3cddf python-webcolors: update to version 1.7
83b915d python-dateutil: update to version 2.6.0
66581ab python-zopeinterface: update to version 4.3.3
122207f python-wrapt: update RDEPENDS to work with minimal python install
c9074c0 python-astroid: update to version 1.4.9
24c481a fwts: upgrade to 16.12.00 release
c2ab89e openl2tp: update SRC_URI
53c1880 ctdb: update SRC_URI
137abcf pimd: update SRC_URI
50ca421 cryptsetup: Add kernel-module-xts to RRECOMMENDS
c54c744 python-cffi: update to version 1.9.1
fe08774 python-cython: update to version 0.25.2
cf3fb15 python-bcrypt: update to version 3.1.2
ea9a823 python-pysocks: update to version 1.6.5 and fix RDEPENDS
096789b python3-wekzeug: update RDEPENDS to pull in http module
af1039d python-flask-login: update to version 0.4.0
d012e59 hwloc: Add
76b6a58 poppler: update to 0.50.0
c3bfb7b xfce4-whiskermenu-plugin: update to 2.0.3
d6d5777 geany: update to 1.29
2576263 geany-plugins: update to 1.29
d96d367 mpd: add PACKAGECONFIG for audiofile
2df9b3c mpd: update to 0.19.21
b190005 mpd: add PACKAGECONFIG for libcdio-paranoia
10acfd4 waf-samba.bbclass: fix build error with PARALLEL_MAKE="-j X -l Y"
01094e1 samba: conditionalize sed call for onnode
bf243e2 linuxptp: fix cross compilation not using host headers
4ffddd5 apache2: always use the archive.apache.org to ensure older releases are always available
== Tested changes (not included in master yet) - meta-qt5 ==
latest upstream commit:
c0ba8ab qtbase: Remove comments about ICU and QtWebKit
not included in master yet:
8aa8260 Upgrade to Qt 5.8
== Tested changes (not included in master yet) - meta-browser ==
latest upstream commit:
5d155da Merge pull request #24 from ashie/firefox-45.6.0-2
not included in master yet:
319fe89 firefox: fix configure with oe-core master - there is no nss-config
3c74e38 firefox: use pkg-config to find nspr
3d896d5 firefox: do not link against crmf library - it is not there
== Tested changes (not included in master yet) - meta-webos-ports ==
latest upstream commit:
922bf4b libqofono: use the recipe from meta-qt5
not included in master yet:
== Tested changes (not included in master yet) - meta-smartphone ==
latest upstream commit:
176f337 linux-hp-tenderloin: Update kernel
not included in master yet:
0ad046f meta-fso: replace deprecated bb.data.getVar('PV',d,1) with d.getVar('PV', True)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
^ permalink raw reply
* [PATCH 0/7] Package Upgrade: systemd-bootchart, dbus, dus-test, sysstat, flex, grep, byacc, coreutils
From: Chen Qi @ 2016-12-26 8:10 UTC (permalink / raw)
To: openembedded-core
The following changes since commit dbb247cac5fbf7b037e4955f9793828451723924:
bitbake: cookerdata: Convert multiconfig to use BB_CURRENT_MC (2016-12-22 12:36:40 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib ChenQi/PU-20161226
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=ChenQi/PU-20161226
Chen Qi (7):
systemd-bootchart: upgrade to 231
dbus/dbus-test: upgrade to 1.10.14
sysstat: upgrade to 11.5.3
flex: upgrade to 2.6.2
grep: upgrade to 2.27
byacc: upgrade to 20161202
coreutils: upgrade to 8.26
...need_charset_alias-when-building-for-musl.patch | 0
...0001-local.mk-fix-cross-compiling-problem.patch | 26 +++++++++
...e-report-processor-and-hardware-correctly.patch | 0
.../disable-ls-output-quoting.patch | 0
.../fix-selinux-flask.patch | 0
.../man-decouple-manpages-from-build.patch | 0
.../remove-usr-local-lib-from-m4.patch | 0
.../{coreutils_8.25.bb => coreutils_8.26.bb} | 9 +--
.../{dbus-test_1.10.10.bb => dbus-test_1.10.14.bb} | 4 +-
.../dbus/{dbus_1.10.10.bb => dbus_1.10.14.bb} | 4 +-
...lex-from-flex-native-to-fix-cross-compili.patch | 51 +++++++++++++++++
...oid-c-comments-in-c-code-fails-with-gcc-6.patch | 64 ----------------------
.../recipes-devtools/flex/flex/CVE-2016-6354.patch | 59 --------------------
.../flex/flex/do_not_create_pdf_doc.patch | 17 ------
.../flex/{flex_2.6.0.bb => flex_2.6.2.bb} | 16 +++---
...d-bootchart_230.bb => systemd-bootchart_231.bb} | 4 +-
.../byacc/{byacc_20160606.bb => byacc_20161202.bb} | 4 +-
.../grep/{grep_2.26.bb => grep_2.27.bb} | 4 +-
.../{sysstat_11.4.0.bb => sysstat_11.5.3.bb} | 4 +-
19 files changed, 103 insertions(+), 163 deletions(-)
rename meta/recipes-core/coreutils/{coreutils-8.25 => coreutils-8.26}/0001-Unset-need_charset_alias-when-building-for-musl.patch (100%)
create mode 100644 meta/recipes-core/coreutils/coreutils-8.26/0001-local.mk-fix-cross-compiling-problem.patch
rename meta/recipes-core/coreutils/{coreutils-8.25 => coreutils-8.26}/0001-uname-report-processor-and-hardware-correctly.patch (100%)
rename meta/recipes-core/coreutils/{coreutils-8.25 => coreutils-8.26}/disable-ls-output-quoting.patch (100%)
rename meta/recipes-core/coreutils/{coreutils-8.25 => coreutils-8.26}/fix-selinux-flask.patch (100%)
rename meta/recipes-core/coreutils/{coreutils-8.25 => coreutils-8.26}/man-decouple-manpages-from-build.patch (100%)
rename meta/recipes-core/coreutils/{coreutils-8.25 => coreutils-8.26}/remove-usr-local-lib-from-m4.patch (100%)
rename meta/recipes-core/coreutils/{coreutils_8.25.bb => coreutils_8.26.bb} (93%)
rename meta/recipes-core/dbus/{dbus-test_1.10.10.bb => dbus-test_1.10.14.bb} (93%)
rename meta/recipes-core/dbus/{dbus_1.10.10.bb => dbus_1.10.14.bb} (98%)
create mode 100644 meta/recipes-devtools/flex/flex/0001-use-stage1flex-from-flex-native-to-fix-cross-compili.patch
delete mode 100644 meta/recipes-devtools/flex/flex/0002-avoid-c-comments-in-c-code-fails-with-gcc-6.patch
delete mode 100644 meta/recipes-devtools/flex/flex/CVE-2016-6354.patch
delete mode 100644 meta/recipes-devtools/flex/flex/do_not_create_pdf_doc.patch
rename meta/recipes-devtools/flex/{flex_2.6.0.bb => flex_2.6.2.bb} (79%)
rename meta/recipes-devtools/systemd-bootchart/{systemd-bootchart_230.bb => systemd-bootchart_231.bb} (92%)
rename meta/recipes-extended/byacc/{byacc_20160606.bb => byacc_20161202.bb} (74%)
rename meta/recipes-extended/grep/{grep_2.26.bb => grep_2.27.bb} (88%)
rename meta/recipes-extended/sysstat/{sysstat_11.4.0.bb => sysstat_11.5.3.bb} (53%)
--
1.9.1
^ permalink raw reply
* [PATCH 1/7] systemd-bootchart: upgrade to 231
From: Chen Qi @ 2016-12-26 8:10 UTC (permalink / raw)
To: openembedded-core
In-Reply-To: <cover.1482739038.git.Qi.Chen@windriver.com>
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
---
.../{systemd-bootchart_230.bb => systemd-bootchart_231.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-devtools/systemd-bootchart/{systemd-bootchart_230.bb => systemd-bootchart_231.bb} (92%)
diff --git a/meta/recipes-devtools/systemd-bootchart/systemd-bootchart_230.bb b/meta/recipes-devtools/systemd-bootchart/systemd-bootchart_231.bb
similarity index 92%
rename from meta/recipes-devtools/systemd-bootchart/systemd-bootchart_230.bb
rename to meta/recipes-devtools/systemd-bootchart/systemd-bootchart_231.bb
index 9ce629a..1d88036 100644
--- a/meta/recipes-devtools/systemd-bootchart/systemd-bootchart_230.bb
+++ b/meta/recipes-devtools/systemd-bootchart/systemd-bootchart_231.bb
@@ -5,8 +5,8 @@ LIC_FILES_CHKSUM = "file://LICENSE.LGPL2.1;md5=4fbd65380cdd255951079008b364516c
SRC_URI = "git://github.com/systemd/systemd-bootchart.git;protocol=https"
# Modify these as desired
-PV = "230+git${SRCPV}"
-SRCREV = "dcb246b46239259ec99b3c6e6ab7d27e1a5a8a84"
+PV = "231+git${SRCPV}"
+SRCREV = "9ee2ffc1dc6c8209725e625954bbd89f96cb7139"
S = "${WORKDIR}/git"
--
1.9.1
^ permalink raw reply related
* [PATCH 2/7] dbus/dbus-test: upgrade to 1.10.14
From: Chen Qi @ 2016-12-26 8:10 UTC (permalink / raw)
To: openembedded-core
In-Reply-To: <cover.1482739038.git.Qi.Chen@windriver.com>
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
---
meta/recipes-core/dbus/{dbus-test_1.10.10.bb => dbus-test_1.10.14.bb} | 4 ++--
meta/recipes-core/dbus/{dbus_1.10.10.bb => dbus_1.10.14.bb} | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
rename meta/recipes-core/dbus/{dbus-test_1.10.10.bb => dbus-test_1.10.14.bb} (93%)
rename meta/recipes-core/dbus/{dbus_1.10.10.bb => dbus_1.10.14.bb} (98%)
diff --git a/meta/recipes-core/dbus/dbus-test_1.10.10.bb b/meta/recipes-core/dbus/dbus-test_1.10.14.bb
similarity index 93%
rename from meta/recipes-core/dbus/dbus-test_1.10.10.bb
rename to meta/recipes-core/dbus/dbus-test_1.10.14.bb
index 650b7ab..5394814 100644
--- a/meta/recipes-core/dbus/dbus-test_1.10.10.bb
+++ b/meta/recipes-core/dbus/dbus-test_1.10.14.bb
@@ -17,8 +17,8 @@ SRC_URI = "http://dbus.freedesktop.org/releases/dbus/dbus-${PV}.tar.gz \
file://clear-guid_from_server-if-send_negotiate_unix_f.patch \
"
-SRC_URI[md5sum] = "495676d240eb982921b3ad1343526849"
-SRC_URI[sha256sum] = "9d8f1d069ab4d1a0255d7b400ea3bcef4430c42e729b1012abb2890e3f739a43"
+SRC_URI[md5sum] = "3f7b013ce8f641cd4c897acda0ef3467"
+SRC_URI[sha256sum] = "23238f70353e38ce5ca183ebc9525c0d97ac00ef640ad29cf794782af6e6a083"
S="${WORKDIR}/dbus-${PV}"
FILESEXTRAPATHS =. "${FILE_DIRNAME}/dbus:"
diff --git a/meta/recipes-core/dbus/dbus_1.10.10.bb b/meta/recipes-core/dbus/dbus_1.10.14.bb
similarity index 98%
rename from meta/recipes-core/dbus/dbus_1.10.10.bb
rename to meta/recipes-core/dbus/dbus_1.10.14.bb
index 4db0b9b..2ffd8b0 100644
--- a/meta/recipes-core/dbus/dbus_1.10.10.bb
+++ b/meta/recipes-core/dbus/dbus_1.10.14.bb
@@ -20,8 +20,8 @@ SRC_URI = "http://dbus.freedesktop.org/releases/dbus/dbus-${PV}.tar.gz \
file://0001-configure.ac-explicitely-check-stdint.h.patch \
"
-SRC_URI[md5sum] = "495676d240eb982921b3ad1343526849"
-SRC_URI[sha256sum] = "9d8f1d069ab4d1a0255d7b400ea3bcef4430c42e729b1012abb2890e3f739a43"
+SRC_URI[md5sum] = "3f7b013ce8f641cd4c897acda0ef3467"
+SRC_URI[sha256sum] = "23238f70353e38ce5ca183ebc9525c0d97ac00ef640ad29cf794782af6e6a083"
inherit useradd autotools pkgconfig gettext update-rc.d upstream-version-is-even
--
1.9.1
^ permalink raw reply related
* [PATCH 3/7] sysstat: upgrade to 11.5.3
From: Chen Qi @ 2016-12-26 8:10 UTC (permalink / raw)
To: openembedded-core
In-Reply-To: <cover.1482739038.git.Qi.Chen@windriver.com>
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
---
.../recipes-extended/sysstat/{sysstat_11.4.0.bb => sysstat_11.5.3.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-extended/sysstat/{sysstat_11.4.0.bb => sysstat_11.5.3.bb} (53%)
diff --git a/meta/recipes-extended/sysstat/sysstat_11.4.0.bb b/meta/recipes-extended/sysstat/sysstat_11.5.3.bb
similarity index 53%
rename from meta/recipes-extended/sysstat/sysstat_11.4.0.bb
rename to meta/recipes-extended/sysstat/sysstat_11.5.3.bb
index 69f83fc..bb6a671 100644
--- a/meta/recipes-extended/sysstat/sysstat_11.4.0.bb
+++ b/meta/recipes-extended/sysstat/sysstat_11.5.3.bb
@@ -4,5 +4,5 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=a23a74b3f4caf9616230789d94217acb"
SRC_URI += "file://0001-Include-needed-headers-explicitly.patch"
-SRC_URI[md5sum] = "ee7b8c0b139a11a7a3418dc0658ca1be"
-SRC_URI[sha256sum] = "b8518ca88acfcbc474a406022ee9c0c3210ccef4f0ec80e5b3e8c41dda8c16f2"
+SRC_URI[md5sum] = "5986da64af934d8cecc7bca7ebe43752"
+SRC_URI[sha256sum] = "f8229d14819e2d461ede83894648e03c8a2ad14a1ba200d68cda9816c42f41ea"
--
1.9.1
^ permalink raw reply related
* [PATCH 4/7] flex: upgrade to 2.6.2
From: Chen Qi @ 2016-12-26 8:10 UTC (permalink / raw)
To: openembedded-core
In-Reply-To: <cover.1482739038.git.Qi.Chen@windriver.com>
Upgrade flex to 2.6.2.
The following two patches are removed as they have been merged.
0002-avoid-c-comments-in-c-code-fails-with-gcc-6.patch
CVE-2016-6354.patch
do_not_create_pdf_doc.patch is removed as it's not suitable for the new
version.
0001-use-stage1flex-from-flex-native-to-fix-cross-compili.patch is added
to fix cross compiling problem.
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
---
...lex-from-flex-native-to-fix-cross-compili.patch | 51 +++++++++++++++++
| 64 ----------------------
.../recipes-devtools/flex/flex/CVE-2016-6354.patch | 59 --------------------
.../flex/flex/do_not_create_pdf_doc.patch | 17 ------
.../flex/{flex_2.6.0.bb => flex_2.6.2.bb} | 16 +++---
5 files changed, 60 insertions(+), 147 deletions(-)
create mode 100644 meta/recipes-devtools/flex/flex/0001-use-stage1flex-from-flex-native-to-fix-cross-compili.patch
delete mode 100644 meta/recipes-devtools/flex/flex/0002-avoid-c-comments-in-c-code-fails-with-gcc-6.patch
delete mode 100644 meta/recipes-devtools/flex/flex/CVE-2016-6354.patch
delete mode 100644 meta/recipes-devtools/flex/flex/do_not_create_pdf_doc.patch
rename meta/recipes-devtools/flex/{flex_2.6.0.bb => flex_2.6.2.bb} (79%)
diff --git a/meta/recipes-devtools/flex/flex/0001-use-stage1flex-from-flex-native-to-fix-cross-compili.patch b/meta/recipes-devtools/flex/flex/0001-use-stage1flex-from-flex-native-to-fix-cross-compili.patch
new file mode 100644
index 0000000..08f7688
--- /dev/null
+++ b/meta/recipes-devtools/flex/flex/0001-use-stage1flex-from-flex-native-to-fix-cross-compili.patch
@@ -0,0 +1,51 @@
+Subject: use stage1flex from flex-native to fix cross compiling
+
+When cross compiling, we would have failure because stage1flex cannot run on host.
+Use stage1flex from flex-native to fix this problem.
+
+This patch is OE specific as upstream may have other way to fix this cross compilation
+problem.
+
+Upstream-Status: Inappropriate [OE specific]
+
+Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
+---
+ src/Makefile.am | 11 ++---------
+ 1 file changed, 2 insertions(+), 9 deletions(-)
+
+diff --git a/src/Makefile.am b/src/Makefile.am
+index 77ddf4b..09ffddb 100644
+--- a/src/Makefile.am
++++ b/src/Makefile.am
+@@ -6,17 +6,10 @@ LIBS = @LIBS@
+ m4 = @M4@
+
+ bin_PROGRAMS = flex
+-noinst_PROGRAMS = stage1flex
+ lib_LTLIBRARIES = \
+ libfl.la \
+ libfl_pic.la
+
+-stage1flex_SOURCES = \
+- scan.l \
+- $(COMMON_SOURCES)
+-
+-stage1flex_CFLAGS = $(AM_CFLAGS)
+-
+ flex_SOURCES = \
+ $(COMMON_SOURCES)
+
+@@ -89,8 +82,8 @@ skel.c: flex.skl mkskel.sh flexint.h tables_shared.h tables_shared.c
+ $(SHELL) $(srcdir)/mkskel.sh > $@.tmp
+ mv $@.tmp $@
+
+-stage1scan.c: scan.l stage1flex$(EXEEXT)
+- ./stage1flex$(EXEEXT) -o $@ $<
++stage1scan.c: scan.l
++ stage1flex$(EXEEXT) -o $@ $<
+
+ # make needs to be told to make parse.h so that parallelized runs will
+ # not fail.
+--
+2.1.0
+
diff --git a/meta/recipes-devtools/flex/flex/0002-avoid-c-comments-in-c-code-fails-with-gcc-6.patch b/meta/recipes-devtools/flex/flex/0002-avoid-c-comments-in-c-code-fails-with-gcc-6.patch
deleted file mode 100644
index 438ca5f..0000000
--- a/meta/recipes-devtools/flex/flex/0002-avoid-c-comments-in-c-code-fails-with-gcc-6.patch
+++ /dev/null
@@ -1,64 +0,0 @@
-From 7072befe1397af4eb01c3ff7edf99f0cd5076089 Mon Sep 17 00:00:00 2001
-From: =?UTF-8?q?Andreas=20M=C3=BCller?= <schnitzeltony@googlemail.com>
-Date: Tue, 30 Aug 2016 14:25:32 +0200
-Subject: [PATCH] avoid c++ comments in c-code - fails with gcc-6
-MIME-Version: 1.0
-Content-Type: text/plain; charset=UTF-8
-Content-Transfer-Encoding: 8bit
-
-fixes:
-
-| error: C++ style comments are not allowed in ISO C90
-| num_to_alloc = 1; // After all that talk, this was set to 1 anyways...
-
-Upstream-Status: Pending
-
-Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com>
----
- src/flex.skl | 2 +-
- src/scan.c | 2 +-
- src/skel.c | 2 +-
- 3 files changed, 3 insertions(+), 3 deletions(-)
-
-diff --git a/src/flex.skl b/src/flex.skl
-index 73a0b9e..ed71627 100644
---- a/src/flex.skl
-+++ b/src/flex.skl
-@@ -2350,7 +2350,7 @@ void yyFlexLexer::yyensure_buffer_stack(void)
- * scanner will even need a stack. We use 2 instead of 1 to avoid an
- * immediate realloc on the next call.
- */
-- num_to_alloc = 1; // After all that talk, this was set to 1 anyways...
-+ num_to_alloc = 1; /* After all that talk, this was set to 1 anyways... */
- YY_G(yy_buffer_stack) = (struct yy_buffer_state**)yyalloc
- (num_to_alloc * sizeof(struct yy_buffer_state*)
- M4_YY_CALL_LAST_ARG);
-diff --git a/src/scan.c b/src/scan.c
-index b55df2d..f1dce75 100644
---- a/src/scan.c
-+++ b/src/scan.c
-@@ -4672,7 +4672,7 @@ static void yyensure_buffer_stack (void)
- * scanner will even need a stack. We use 2 instead of 1 to avoid an
- * immediate realloc on the next call.
- */
-- num_to_alloc = 1; // After all that talk, this was set to 1 anyways...
-+ num_to_alloc = 1; /* After all that talk, this was set to 1 anyways...*/
- (yy_buffer_stack) = (struct yy_buffer_state**)yyalloc
- (num_to_alloc * sizeof(struct yy_buffer_state*)
- );
-diff --git a/src/skel.c b/src/skel.c
-index ef657d3..26cc889 100644
---- a/src/skel.c
-+++ b/src/skel.c
-@@ -2561,7 +2561,7 @@ const char *skel[] = {
- " * scanner will even need a stack. We use 2 instead of 1 to avoid an",
- " * immediate realloc on the next call.",
- " */",
-- " num_to_alloc = 1; // After all that talk, this was set to 1 anyways...",
-+ " num_to_alloc = 1; /* After all that talk, this was set to 1 anyways... */",
- " YY_G(yy_buffer_stack) = (struct yy_buffer_state**)yyalloc",
- " (num_to_alloc * sizeof(struct yy_buffer_state*)",
- " M4_YY_CALL_LAST_ARG);",
---
-2.5.5
-
diff --git a/meta/recipes-devtools/flex/flex/CVE-2016-6354.patch b/meta/recipes-devtools/flex/flex/CVE-2016-6354.patch
deleted file mode 100644
index 216ac7a..0000000
--- a/meta/recipes-devtools/flex/flex/CVE-2016-6354.patch
+++ /dev/null
@@ -1,59 +0,0 @@
-From 3939eccdff598f47e5b37b05d58bf1b44d3796e7 Mon Sep 17 00:00:00 2001
-From: Jussi Kukkonen <jussi.kukkonen@intel.com>
-Date: Fri, 7 Oct 2016 14:15:38 +0300
-Subject: [PATCH] Prevent buffer overflow in yy_get_next_buffer
-
-This is upstream commit a5cbe929ac3255d371e698f62dc256afe7006466
-with some additional backporting to make binutils build again.
-
-Upstream-Status: Backport
-CVE: CVE-2016-6354
-Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com>
----
- src/flex.skl | 2 +-
- src/scan.c | 2 +-
- src/skel.c | 2 +-
- 3 files changed, 3 insertions(+), 3 deletions(-)
-
-diff --git a/src/flex.skl b/src/flex.skl
-index ed71627..814d562 100644
---- a/src/flex.skl
-+++ b/src/flex.skl
-@@ -1718,7 +1718,7 @@ int yyFlexLexer::yy_get_next_buffer()
-
- else
- {
-- yy_size_t num_to_read =
-+ int num_to_read =
- YY_CURRENT_BUFFER_LVALUE->yy_buf_size - number_to_move - 1;
-
- while ( num_to_read <= 0 )
-diff --git a/src/scan.c b/src/scan.c
-index f1dce75..1949872 100644
---- a/src/scan.c
-+++ b/src/scan.c
-@@ -4181,7 +4181,7 @@ static int yy_get_next_buffer (void)
-
- else
- {
-- yy_size_t num_to_read =
-+ int num_to_read =
- YY_CURRENT_BUFFER_LVALUE->yy_buf_size - number_to_move - 1;
-
- while ( num_to_read <= 0 )
-diff --git a/src/skel.c b/src/skel.c
-index 26cc889..0344d18 100644
---- a/src/skel.c
-+++ b/src/skel.c
-@@ -1929,7 +1929,7 @@ const char *skel[] = {
- "",
- " else",
- " {",
-- " yy_size_t num_to_read =",
-+ " int num_to_read =",
- " YY_CURRENT_BUFFER_LVALUE->yy_buf_size - number_to_move - 1;",
- "",
- " while ( num_to_read <= 0 )",
---
-2.1.4
-
diff --git a/meta/recipes-devtools/flex/flex/do_not_create_pdf_doc.patch b/meta/recipes-devtools/flex/flex/do_not_create_pdf_doc.patch
deleted file mode 100644
index 032833ae..0000000
--- a/meta/recipes-devtools/flex/flex/do_not_create_pdf_doc.patch
+++ /dev/null
@@ -1,17 +0,0 @@
-Upstream-Status: Inappropriate (embedded specific)
-
-Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
-
-Index: flex-2.5.37/doc/Makefile.am
-===================================================================
---- flex-2.5.37.orig/doc/Makefile.am 2012-07-21 04:18:27.000000000 +0300
-+++ flex-2.5.37/doc/Makefile.am 2013-07-30 17:57:09.834834531 +0300
-@@ -2,7 +2,7 @@
-
- info_TEXINFOS = flex.texi
- dist_man_MANS = flex.1
--dist_doc_DATA= flex.pdf
-+EXTRA_DIST= flex.pdf
-
- CLEANFILES = \
- flex.hks \
diff --git a/meta/recipes-devtools/flex/flex_2.6.0.bb b/meta/recipes-devtools/flex/flex_2.6.2.bb
similarity index 79%
rename from meta/recipes-devtools/flex/flex_2.6.0.bb
rename to meta/recipes-devtools/flex/flex_2.6.2.bb
index ab35b09..e723124 100644
--- a/meta/recipes-devtools/flex/flex_2.6.0.bb
+++ b/meta/recipes-devtools/flex/flex_2.6.2.bb
@@ -5,22 +5,23 @@ HOMEPAGE = "http://sourceforge.net/projects/flex/"
SECTION = "devel"
LICENSE = "BSD"
-DEPENDS = "${@bb.utils.contains('PTEST_ENABLED', '1', 'bison-native flex-native', '', d)}"
+DEPENDS = "flex-native ${@bb.utils.contains('PTEST_ENABLED', '1', 'bison-native', '', d)}"
BBCLASSEXTEND = "native nativesdk"
LIC_FILES_CHKSUM = "file://COPYING;md5=e4742cf92e89040b39486a6219b68067"
-SRC_URI = "${SOURCEFORGE_MIRROR}/flex/flex-${PV}.tar.bz2 \
+SRC_URI = "https://github.com/westes/flex/releases/download/v${PV}/flex-${PV}.tar.gz \
file://run-ptest \
- file://do_not_create_pdf_doc.patch \
file://0001-tests-add-a-target-for-building-tests-without-runnin.patch \
- file://0002-avoid-c-comments-in-c-code-fails-with-gcc-6.patch \
- file://CVE-2016-6354.patch \
${@bb.utils.contains('PTEST_ENABLED', '1', '', 'file://disable-tests.patch', d)} \
"
-SRC_URI[md5sum] = "266270f13c48ed043d95648075084d59"
-SRC_URI[sha256sum] = "24e611ef5a4703a191012f80c1027dc9d12555183ce0ecd46f3636e587e9b8e9"
+SRC_URI_append_class-target = " \
+ file://0001-use-stage1flex-from-flex-native-to-fix-cross-compili.patch \
+ "
+
+SRC_URI[md5sum] = "cc6d76c333db7653d5caf423a3335239"
+SRC_URI[sha256sum] = "9a01437a1155c799b7dc2508620564ef806ba66250c36bf5f9034b1c207cb2c9"
# Flex has moved to github from 2.6.1 onwards
UPSTREAM_CHECK_URI = "https://github.com/westes/flex/releases"
@@ -37,6 +38,7 @@ EXTRA_OEMAKE += "${@bb.utils.contains('PTEST_ENABLED', '1', 'FLEX=${STAGING_BIND
do_install_append_class-native() {
create_wrapper ${D}/${bindir}/flex M4=${M4}
+ cp ${B}/src/stage1flex ${D}/${bindir}
}
do_install_append_class-nativesdk() {
--
1.9.1
^ permalink raw reply related
* [PATCH 5/7] grep: upgrade to 2.27
From: Chen Qi @ 2016-12-26 8:10 UTC (permalink / raw)
To: openembedded-core
In-Reply-To: <cover.1482739038.git.Qi.Chen@windriver.com>
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
---
meta/recipes-extended/grep/{grep_2.26.bb => grep_2.27.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-extended/grep/{grep_2.26.bb => grep_2.27.bb} (88%)
diff --git a/meta/recipes-extended/grep/grep_2.26.bb b/meta/recipes-extended/grep/grep_2.27.bb
similarity index 88%
rename from meta/recipes-extended/grep/grep_2.26.bb
rename to meta/recipes-extended/grep/grep_2.27.bb
index 9e6f05e..7d0a73b 100644
--- a/meta/recipes-extended/grep/grep_2.26.bb
+++ b/meta/recipes-extended/grep/grep_2.27.bb
@@ -9,8 +9,8 @@ SRC_URI = "${GNU_MIRROR}/grep/grep-${PV}.tar.xz \
file://0001-Unset-need_charset_alias-when-building-for-musl.patch \
"
-SRC_URI[md5sum] = "afdd61c7221434722671baf002ac9267"
-SRC_URI[sha256sum] = "246a8fb37e82aa33d495b07c22fdab994c039ab0f818538eac81b01e78636870"
+SRC_URI[md5sum] = "6138dd227c39d4a25f81eea76a44d4cb"
+SRC_URI[sha256sum] = "ad4cc44d23074a1c3a8baae8fbafff2a8c60f38a9a6108f985eef6fbee6dcaeb"
inherit autotools gettext texinfo
--
1.9.1
^ permalink raw reply related
* [PATCH 6/7] byacc: upgrade to 20161202
From: Chen Qi @ 2016-12-26 8:10 UTC (permalink / raw)
To: openembedded-core
In-Reply-To: <cover.1482739038.git.Qi.Chen@windriver.com>
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
---
meta/recipes-extended/byacc/{byacc_20160606.bb => byacc_20161202.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-extended/byacc/{byacc_20160606.bb => byacc_20161202.bb} (74%)
diff --git a/meta/recipes-extended/byacc/byacc_20160606.bb b/meta/recipes-extended/byacc/byacc_20161202.bb
similarity index 74%
rename from meta/recipes-extended/byacc/byacc_20160606.bb
rename to meta/recipes-extended/byacc/byacc_20161202.bb
index 98129d0..755f8ab 100644
--- a/meta/recipes-extended/byacc/byacc_20160606.bb
+++ b/meta/recipes-extended/byacc/byacc_20161202.bb
@@ -8,5 +8,5 @@ LIC_FILES_CHKSUM = "file://package/debian/copyright;md5=74533d32ffd38bca4cbf1f13
require byacc.inc
-SRC_URI[md5sum] = "d527c811b360f04a8c5f5a0a90625966"
-SRC_URI[sha256sum] = "cc8fdced486cb70cec7a7c9358de836bfd267d19d6456760bb4721ccfea5ac91"
+SRC_URI[md5sum] = "48ef38447f2cc864c70ef864b26cf817"
+SRC_URI[sha256sum] = "30dc58cfcdb708eea7ba022db29b41d2d392f20727491b956954366f2f2117f0"
--
1.9.1
^ permalink raw reply related
* [PATCH 7/7] coreutils: upgrade to 8.26
From: Chen Qi @ 2016-12-26 8:10 UTC (permalink / raw)
To: openembedded-core
In-Reply-To: <cover.1482739038.git.Qi.Chen@windriver.com>
Add 0001-local.mk-fix-cross-compiling-problem.patch to fix the following
cross compiling problem.
| Makefile:3418: *** Recursive variable 'INSTALL' references itself (eventually). Stop.
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
---
...need_charset_alias-when-building-for-musl.patch | 0
...0001-local.mk-fix-cross-compiling-problem.patch | 26 ++++++++++++++++++++++
...e-report-processor-and-hardware-correctly.patch | 0
.../disable-ls-output-quoting.patch | 0
.../fix-selinux-flask.patch | 0
.../man-decouple-manpages-from-build.patch | 0
.../remove-usr-local-lib-from-m4.patch | 0
.../{coreutils_8.25.bb => coreutils_8.26.bb} | 9 ++++----
8 files changed, 31 insertions(+), 4 deletions(-)
rename meta/recipes-core/coreutils/{coreutils-8.25 => coreutils-8.26}/0001-Unset-need_charset_alias-when-building-for-musl.patch (100%)
create mode 100644 meta/recipes-core/coreutils/coreutils-8.26/0001-local.mk-fix-cross-compiling-problem.patch
rename meta/recipes-core/coreutils/{coreutils-8.25 => coreutils-8.26}/0001-uname-report-processor-and-hardware-correctly.patch (100%)
rename meta/recipes-core/coreutils/{coreutils-8.25 => coreutils-8.26}/disable-ls-output-quoting.patch (100%)
rename meta/recipes-core/coreutils/{coreutils-8.25 => coreutils-8.26}/fix-selinux-flask.patch (100%)
rename meta/recipes-core/coreutils/{coreutils-8.25 => coreutils-8.26}/man-decouple-manpages-from-build.patch (100%)
rename meta/recipes-core/coreutils/{coreutils-8.25 => coreutils-8.26}/remove-usr-local-lib-from-m4.patch (100%)
rename meta/recipes-core/coreutils/{coreutils_8.25.bb => coreutils_8.26.bb} (93%)
diff --git a/meta/recipes-core/coreutils/coreutils-8.25/0001-Unset-need_charset_alias-when-building-for-musl.patch b/meta/recipes-core/coreutils/coreutils-8.26/0001-Unset-need_charset_alias-when-building-for-musl.patch
similarity index 100%
rename from meta/recipes-core/coreutils/coreutils-8.25/0001-Unset-need_charset_alias-when-building-for-musl.patch
rename to meta/recipes-core/coreutils/coreutils-8.26/0001-Unset-need_charset_alias-when-building-for-musl.patch
diff --git a/meta/recipes-core/coreutils/coreutils-8.26/0001-local.mk-fix-cross-compiling-problem.patch b/meta/recipes-core/coreutils/coreutils-8.26/0001-local.mk-fix-cross-compiling-problem.patch
new file mode 100644
index 0000000..66f9a71
--- /dev/null
+++ b/meta/recipes-core/coreutils/coreutils-8.26/0001-local.mk-fix-cross-compiling-problem.patch
@@ -0,0 +1,26 @@
+Subject: local.mk: fix cross compiling problem
+
+We meet the following error when cross compiling.
+| Makefile:3418: *** Recursive variable 'INSTALL' references itself (eventually). Stop.
+This patch fixes this problem.
+
+Upstream-Status: Pending
+
+Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
+---
+ src/local.mk | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/local.mk b/src/local.mk
+index 36dfa4e..c5898cc 100644
+--- a/src/local.mk
++++ b/src/local.mk
+@@ -649,4 +649,4 @@ cu_install_program = @INSTALL_PROGRAM@
+ else
+ cu_install_program = src/ginstall
+ endif
+-INSTALL = $(cu_install_program) -c
++INSTALL_PROGRAM = $(cu_install_program)
+--
+2.1.0
+
diff --git a/meta/recipes-core/coreutils/coreutils-8.25/0001-uname-report-processor-and-hardware-correctly.patch b/meta/recipes-core/coreutils/coreutils-8.26/0001-uname-report-processor-and-hardware-correctly.patch
similarity index 100%
rename from meta/recipes-core/coreutils/coreutils-8.25/0001-uname-report-processor-and-hardware-correctly.patch
rename to meta/recipes-core/coreutils/coreutils-8.26/0001-uname-report-processor-and-hardware-correctly.patch
diff --git a/meta/recipes-core/coreutils/coreutils-8.25/disable-ls-output-quoting.patch b/meta/recipes-core/coreutils/coreutils-8.26/disable-ls-output-quoting.patch
similarity index 100%
rename from meta/recipes-core/coreutils/coreutils-8.25/disable-ls-output-quoting.patch
rename to meta/recipes-core/coreutils/coreutils-8.26/disable-ls-output-quoting.patch
diff --git a/meta/recipes-core/coreutils/coreutils-8.25/fix-selinux-flask.patch b/meta/recipes-core/coreutils/coreutils-8.26/fix-selinux-flask.patch
similarity index 100%
rename from meta/recipes-core/coreutils/coreutils-8.25/fix-selinux-flask.patch
rename to meta/recipes-core/coreutils/coreutils-8.26/fix-selinux-flask.patch
diff --git a/meta/recipes-core/coreutils/coreutils-8.25/man-decouple-manpages-from-build.patch b/meta/recipes-core/coreutils/coreutils-8.26/man-decouple-manpages-from-build.patch
similarity index 100%
rename from meta/recipes-core/coreutils/coreutils-8.25/man-decouple-manpages-from-build.patch
rename to meta/recipes-core/coreutils/coreutils-8.26/man-decouple-manpages-from-build.patch
diff --git a/meta/recipes-core/coreutils/coreutils-8.25/remove-usr-local-lib-from-m4.patch b/meta/recipes-core/coreutils/coreutils-8.26/remove-usr-local-lib-from-m4.patch
similarity index 100%
rename from meta/recipes-core/coreutils/coreutils-8.25/remove-usr-local-lib-from-m4.patch
rename to meta/recipes-core/coreutils/coreutils-8.26/remove-usr-local-lib-from-m4.patch
diff --git a/meta/recipes-core/coreutils/coreutils_8.25.bb b/meta/recipes-core/coreutils/coreutils_8.26.bb
similarity index 93%
rename from meta/recipes-core/coreutils/coreutils_8.25.bb
rename to meta/recipes-core/coreutils/coreutils_8.26.bb
index 6d6f7bc..caa6d96 100644
--- a/meta/recipes-core/coreutils/coreutils_8.25.bb
+++ b/meta/recipes-core/coreutils/coreutils_8.26.bb
@@ -20,12 +20,13 @@ SRC_URI = "${GNU_MIRROR}/coreutils/${BP}.tar.xz;name=tarball \
file://0001-Unset-need_charset_alias-when-building-for-musl.patch \
file://0001-uname-report-processor-and-hardware-correctly.patch \
file://disable-ls-output-quoting.patch \
+ file://0001-local.mk-fix-cross-compiling-problem.patch \
"
-SRC_URI[tarball.md5sum] = "070e43ba7f618d747414ef56ab248a48"
-SRC_URI[tarball.sha256sum] = "31e67c057a5b32a582f26408c789e11c2e8d676593324849dcf5779296cdce87"
-SRC_URI[manpages.md5sum] = "415cc0552bc4e480b27ce8b2aebfdeb5"
-SRC_URI[manpages.sha256sum] = "2ee31c3a6d2276f49c5515375d4a0c1047580da6ac10536898e0f0de81707f29"
+SRC_URI[tarball.md5sum] = "d5aa2072f662d4118b9f4c63b94601a6"
+SRC_URI[tarball.sha256sum] = "155e94d748f8e2bc327c66e0cbebdb8d6ab265d2f37c3c928f7bf6c3beba9a8e"
+SRC_URI[manpages.md5sum] = "b58107f532f7beffcb2f38e2ac1f2da3"
+SRC_URI[manpages.sha256sum] = "9324ec412ffca3b0431e6299720c33ac98e749e430f72a7c6e65f3635c86aa29"
EXTRA_OECONF_class-native = "--without-gmp"
EXTRA_OECONF_class-target = "--enable-install-program=arch --libexecdir=${libdir}"
--
1.9.1
^ permalink raw reply related
* Yocto-2.2 build failures on Ubuntu 14.04.5 & 16.04.x hosts due to crash of unity-settings-daemon followed by restart of lightdm
From: srikanth krishnakar @ 2016-12-26 9:41 UTC (permalink / raw)
To: openembedded-core
[-- Attachment #1: Type: text/plain, Size: 2328 bytes --]
Hello,
Environment: Ubuntu-14.04.5/16.04.1 (64-bit)
Yocto build: qemuarm
Target image: core-image-sato
Error nature: The lightdm restarts on its own and logs out by killing
processes running and brings up a login UI.
We have been observing yocto-2.2 build failures on Ubuntu 14.04.5 and
Ubuntu-16.04.1 hosts due to restart of "lightdm" (Light Desktop Manager)
that is triggered by crash of "unity-settings-daemon", we couldn't figure
out any workaround so far to overcome the issue. The build goes fine in the
beginning but eventually the unity desktop logs out and kills all the
processes running in the user session (including bitbake) and lands us into
"Login screen" and when we login its a new session where as the bitbake
running in previous session is killed and we need to continue the build.
This is happening consistently when the user logs into desktop via lightdm
and triggers a build.
Another interesting thing to notice is the build goes fine if we connect to
host via. SSH session and invoke a bitbake build. We are suspecting on
unity-settings-daemon that is crashing consistently and is evident from the
".xsession-errors" log file as shown below:
builder@ubuntu:~$ cat .xsession-errors.old
Script for ibus started at run_im.
Script for auto started at run_im.
Script for default started at run_im.
init: Disconnected from notified D-Bus bus
init:"unity-settings-daemon main process (2076) terminated with status 1"
init: indicator-bluetooth main process (2212) killed by TERM signal
init: indicator-power main process (2214) killed by TERM signal
init: indicator-datetime main process (2215) killed by TERM signal
init: indicator-printers main process (2222) killed by TERM signal
init: indicator-session main process (2245) killed by TERM signal
init: indicator-application main process (2270) killed by TERM signal
Corresponding unity-settings-daemon bug reported in Launchpad:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1546641
Would anyone kindly confirm the logout behaviour during bitbake process on
Ubuntu-14.04.5 & Ubuntu-16.04.1 ? Since Yocto 2.2 mentions both
Ubuntu-14.04 & 16.04 as supported distributions this blocker issue must be
resolved at earliest.
Appreciate your Inputs !
Thanks in Advance.
-Srikant
[-- Attachment #2: Type: text/html, Size: 4498 bytes --]
^ permalink raw reply
* Re: Yocto-2.2 build failures on Ubuntu 14.04.5 & 16.04.x hosts due to crash of unity-settings-daemon followed by restart of lightdm
From: Richard Purdie @ 2016-12-26 10:36 UTC (permalink / raw)
To: srikanth krishnakar, openembedded-core
In-Reply-To: <CALDxG5gxGqHP7S1fK-NmFrvQt9KRgjH+u4t+xHF=3m=UvUY=bQ@mail.gmail.com>
On Mon, 2016-12-26 at 15:11 +0530, srikanth krishnakar wrote:
> Environment: Ubuntu-14.04.5/16.04.1 (64-bit)
> Yocto build: qemuarm
> Target image: core-image-sato
> Error nature: The lightdm restarts on its own and logs out by killing
> processes running and brings up a login UI.
>
>
> We have been observing yocto-2.2 build failures on Ubuntu 14.04.5 and
> Ubuntu-16.04.1 hosts due to restart of "lightdm" (Light Desktop
> Manager) that is triggered by crash of "unity-settings-daemon", we
> couldn't figure out any workaround so far to overcome the issue. The
> build goes fine in the beginning but eventually the unity desktop
> logs out and kills all the processes running in the user session
> (including bitbake) and lands us into "Login screen" and when we
> login its a new session where as the bitbake running in previous
> session is killed and we need to continue the build. This is
> happening consistently when the user logs into desktop via lightdm
> and triggers a build.
>
> Another interesting thing to notice is the build goes fine if we
> connect to host via. SSH session and invoke a bitbake build. We are
> suspecting on unity-settings-daemon that is crashing consistently and
> is evident from the ".xsession-errors" log file as shown below:
>
> builder@ubuntu:~$ cat .xsession-errors.old
> Script for ibus started at run_im.
> Script for auto started at run_im.
> Script for default started at run_im.
> init: Disconnected from notified D-Bus bus
> init:"unity-settings-daemon main process (2076) terminated with
> status 1"
> init: indicator-bluetooth main process (2212) killed by TERM signal
> init: indicator-power main process (2214) killed by TERM signal
> init: indicator-datetime main process (2215) killed by TERM signal
> init: indicator-printers main process (2222) killed by TERM signal
> init: indicator-session main process (2245) killed by TERM signal
> init: indicator-application main process (2270) killed by TERM signal
>
> Corresponding unity-settings-daemon bug reported in Launchpad:
>
> https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/
> 1546641
>
> Would anyone kindly confirm the logout behaviour during bitbake
> process on Ubuntu-14.04.5 & Ubuntu-16.04.1 ? Since Yocto 2.2 mentions
> both Ubuntu-14.04 & 16.04 as supported distributions this blocker
> issue must be resolved at earliest.
>
> Appreciate your Inputs !
What would really help is knowing what recipe is being built when this
happens. There are a few ways you might be able to figure this out:
a) Watching the screen to see which recipes were building when it
happens
b) Perhaps using some kind of screen recorder to automate this, you'd
be able to review the recording to see when it breaks
c) Looking at the bitbake/build logs to see what it was doing when the
build broke (assuming bitbake stops when the session dies).
"bitbake | cat" can provide better output for this since it will
produce a scrolling log rather than the more interactive UI.
Once you find the problematic recipe, a "bitbake XXX -c clean; bitbake
XXX" should hopefully reproduce this more easily.
Cheers,
Richard
^ permalink raw reply
* Re: Yocto-2.2 build failures on Ubuntu 14.04.5 & 16.04.x hosts due to crash of unity-settings-daemon followed by restart of lightdm
From: srikanth krishnakar @ 2016-12-26 10:58 UTC (permalink / raw)
To: Richard Purdie; +Cc: openembedded-core
In-Reply-To: <1482748609.9843.136.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 3961 bytes --]
Hello Richard,
Sure, watching is best thing we can do, but it happens somewhere after 2900
tasks i.e just after linux-yocto.
Screen recorders usually ask for file name and destination folder for
saving the file, will try to see if it works as you said.
"bitbake | cat" is the best method that we can get info from.
The issue is noticeable only in ubuntu (unity) desktop's and not in Kubuntu
(KDE), Ubuntu-gnome (Gnome-3) or Xubuntu (XFCE) desktops.
Will fetch more details as per your suggestion.
Thank you !
On Mon, Dec 26, 2016 at 4:06 PM, Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:
> On Mon, 2016-12-26 at 15:11 +0530, srikanth krishnakar wrote:
> > Environment: Ubuntu-14.04.5/16.04.1 (64-bit)
> > Yocto build: qemuarm
> > Target image: core-image-sato
> > Error nature: The lightdm restarts on its own and logs out by killing
> > processes running and brings up a login UI.
> >
> >
> > We have been observing yocto-2.2 build failures on Ubuntu 14.04.5 and
> > Ubuntu-16.04.1 hosts due to restart of "lightdm" (Light Desktop
> > Manager) that is triggered by crash of "unity-settings-daemon", we
> > couldn't figure out any workaround so far to overcome the issue. The
> > build goes fine in the beginning but eventually the unity desktop
> > logs out and kills all the processes running in the user session
> > (including bitbake) and lands us into "Login screen" and when we
> > login its a new session where as the bitbake running in previous
> > session is killed and we need to continue the build. This is
> > happening consistently when the user logs into desktop via lightdm
> > and triggers a build.
> >
> > Another interesting thing to notice is the build goes fine if we
> > connect to host via. SSH session and invoke a bitbake build. We are
> > suspecting on unity-settings-daemon that is crashing consistently and
> > is evident from the ".xsession-errors" log file as shown below:
> >
> > builder@ubuntu:~$ cat .xsession-errors.old
> > Script for ibus started at run_im.
> > Script for auto started at run_im.
> > Script for default started at run_im.
> > init: Disconnected from notified D-Bus bus
> > init:"unity-settings-daemon main process (2076) terminated with
> > status 1"
> > init: indicator-bluetooth main process (2212) killed by TERM signal
> > init: indicator-power main process (2214) killed by TERM signal
> > init: indicator-datetime main process (2215) killed by TERM signal
> > init: indicator-printers main process (2222) killed by TERM signal
> > init: indicator-session main process (2245) killed by TERM signal
> > init: indicator-application main process (2270) killed by TERM signal
> >
> > Corresponding unity-settings-daemon bug reported in Launchpad:
> >
> > https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/
> > 1546641
> >
> > Would anyone kindly confirm the logout behaviour during bitbake
> > process on Ubuntu-14.04.5 & Ubuntu-16.04.1 ? Since Yocto 2.2 mentions
> > both Ubuntu-14.04 & 16.04 as supported distributions this blocker
> > issue must be resolved at earliest.
> >
> > Appreciate your Inputs !
>
> What would really help is knowing what recipe is being built when this
> happens. There are a few ways you might be able to figure this out:
>
> a) Watching the screen to see which recipes were building when it
> happens
> b) Perhaps using some kind of screen recorder to automate this, you'd
> be able to review the recording to see when it breaks
> c) Looking at the bitbake/build logs to see what it was doing when the
> build broke (assuming bitbake stops when the session dies).
>
> "bitbake | cat" can provide better output for this since it will
> produce a scrolling log rather than the more interactive UI.
>
> Once you find the problematic recipe, a "bitbake XXX -c clean; bitbake
> XXX" should hopefully reproduce this more easily.
>
> Cheers,
>
> Richard
>
[-- Attachment #2: Type: text/html, Size: 5401 bytes --]
^ permalink raw reply
* Re: Yocto-2.2 build failures on Ubuntu 14.04.5 & 16.04.x hosts due to crash of unity-settings-daemon followed by restart of lightdm
From: srikanth krishnakar @ 2016-12-26 13:29 UTC (permalink / raw)
To: Richard Purdie; +Cc: openembedded-core
In-Reply-To: <CALDxG5h=3iZTJp=d_4RKGs6pOC=W6MJeFeJ6_-ykayqWv1i3nw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 9413 bytes --]
Hello Richard,
bitbake | cat shows that when this logout happened during build, log file
captured below packages in process:
--------------------------------------------------------------------------------------------
NOTE: Running task 1886 of 4212
(/home/builder/poky/meta/recipes-graphics/xorg-proto/kbproto_1.0.7.bb:
do_packagedata)
NOTE: recipe kbproto-1_1.0.7-r0: task do_packagedata: Started
NOTE: recipe kbproto-1_1.0.7-r0: task do_packagedata: Succeeded
NOTE: Running task 1887 of 4212
(/home/builder/poky/meta/recipes-support/libffi/libffi_3.2.1.bb:do_package)
NOTE: recipe ncurses-6.0+20160625-r0: task do_package: Started
NOTE: recipe libffi-3.2.1-r0: task do_package: Started
NOTE: recipe libffi-3.2.1-r0: task do_package: Succeeded
NOTE: Running task 1888 of 4212
(/home/builder/poky/meta/recipes-support/libffi/libffi_3.2.1.bb:
do_packagedata)
NOTE: recipe libffi-3.2.1-r0: task do_packagedata: Started
NOTE: recipe libffi-3.2.1-r0: task do_packagedata: Succeeded
NOTE: Running task 1889 of 4212
(/home/builder/poky/meta/recipes-extended/bzip2/bzip2_1.0.6.bb:do_package)
NOTE: recipe bzip2-1.0.6-r5: task do_package: Started
-----------------------------------------------------------------------------------------------
Also there was a crash file generated in "/var/crash" folder:
/var/crash/_usr_lib_accountsservice_accounts-daemon.0.crash
That has following information in it:
-------------------------------------------------------------------------------------------------
ProblemType: Crash
Architecture: amd64
Date: Mon Dec 26 18:23:22 2016
DistroRelease: Ubuntu 14.04
ExecutablePath: /usr/lib/accountsservice/accounts-daemon
ExecutableTimestamp: 1478200365
ProcCmdline: /usr/lib/accountsservice/accounts-daemon
ProcCwd: /
ProcEnviron:
ProcMaps:
00400000-00426000 r-xp 00000000 08:01 2626520
/usr/lib/accountsservice/accounts-daemon
00625000-00628000 r--p 00025000 08:01 2626520
/usr/lib/accountsservice/accounts-daemon
00628000-00629000 rw-p 00028000 08:01 2626520
/usr/lib/accountsservice/accounts-daemon
024aa000-0252a000 rw-p 00000000 00:00 0
[heap]
7fe460000000-7fe460022000 rw-p 00000000 00:00 0
7fe460022000-7fe464000000 ---p 00000000 00:00 0
7fe464000000-7fe464021000 rw-p 00000000 00:00 0
7fe464021000-7fe468000000 ---p 00000000 00:00 0
7fe469f56000-7fe469f60000 r-xp 00000000 08:01 1839849
/lib/x86_64-linux-gnu/libnss_files-2.19.so
7fe469f60000-7fe46a15f000 ---p 0000a000 08:01 1839849
/lib/x86_64-linux-gnu/libnss_files-2.19.so
7fe46a15f000-7fe46a160000 r--p 00009000 08:01 1839849
/lib/x86_64-linux-gnu/libnss_files-2.19.so
...
...
7fe474b3e000-7fe474b40000 rw-p 00000000 00:00 0
7fe474b40000-7fe474b41000 r--p 00022000 08:01 1839750
/lib/x86_64-linux-gnu/ld-2.19.so
7fe474b41000-7fe474b42000 rw-p 00023000 08:01 1839750
/lib/x86_64-linux-gnu/ld-2.19.so
7fe474b42000-7fe474b43000 rw-p 00000000 00:00 0
7ffcaca64000-7ffcaca85000 rw-p 00000000 00:00 0
[stack]
7ffcacaf5000-7ffcacaf7000 r--p 00000000 00:00 0
[vvar]
7ffcacaf7000-7ffcacaf9000 r-xp 00000000 00:00 0
[vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0
[vsyscall]
ProcStatus:
Name: accounts-daemon
State: D (disk sleep)
Tgid: 1248
Ngid: 0
Pid: 1248
PPid: 1
TracerPid: 0
Uid: 0 0 0 0
Gid: 0 0 0 0
FDSize: 64
Groups: 0
NStgid: 1248
NSpid: 1248
NSpgid: 795
NSsid: 795
VmPeak: 302404 kB
VmSize: 302368 kB
VmPin: 0 kB
VmHWM: 10128 kB
VmRSS: 4464 kB
VmData: 221944 kB
VmStk: 136 kB
VmExe: 152 kB
VmLib: 10140 kB
VmPTE: 200 kB
VmPMD: 12 kB
VmSwap: 2976 kB
HugetlbPages: 0 kB
Threads: 3
SigQ: 0/31670
SigPnd: 0000000000000000
ShdPnd: 0000000000000000
SigBlk: 0000000000000000
SigIgn: 0000000000001000
SigCgt: 0000000180004002
CapInh: 0000000000000000
CapPrm: 0000003fffffffff
CapEff: 0000003fffffffff
CapBnd: 0000003fffffffff
CapAmb: 0000000000000000
Seccomp: 0
Cpus_allowed: ff
Cpus_allowed_list: 0-7
Mems_allowed: 00000000,00000001
Mems_allowed_list: 0
voluntary_ctxt_switches: 152
nonvoluntary_ctxt_switches: 2
Signal: 7
Uname: Linux 4.4.0-57-generic x86_64
UserGroups:
CoreDump: base64
-------------------------------------------------------------------------------------------------
My machine is:
*Quad-Core:* (0-8)
---------------------------------------
$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 42
model name : Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
-----
$ cat /proc/meminfo
MemTotal: 8132472 kB
----------------------------------------
When I checked free memory just before the logout was about "125MB" out of
8GB RAM.
NOTE: The Ubuntu-14.04.4 that had older graphics stack seem to work
normally without any issue. The "ubuntu-14.04.5" & "16.04" came with latest
graphics stack & kernel with removal of non-opensource fglrx drivers.
Thanks for your patience!
--
Regards,
Srikant
On Mon, Dec 26, 2016 at 4:28 PM, srikanth krishnakar <skrishnakar@gmail.com>
wrote:
> Hello Richard,
>
> Sure, watching is best thing we can do, but it happens somewhere after
> 2900 tasks i.e just after linux-yocto.
> Screen recorders usually ask for file name and destination folder for
> saving the file, will try to see if it works as you said.
> "bitbake | cat" is the best method that we can get info from.
>
> The issue is noticeable only in ubuntu (unity) desktop's and not in
> Kubuntu (KDE), Ubuntu-gnome (Gnome-3) or Xubuntu (XFCE) desktops.
>
> Will fetch more details as per your suggestion.
>
> Thank you !
>
> On Mon, Dec 26, 2016 at 4:06 PM, Richard Purdie <richard.purdie@
> linuxfoundation.org> wrote:
>
>> On Mon, 2016-12-26 at 15:11 +0530, srikanth krishnakar wrote:
>> > Environment: Ubuntu-14.04.5/16.04.1 (64-bit)
>> > Yocto build: qemuarm
>> > Target image: core-image-sato
>> > Error nature: The lightdm restarts on its own and logs out by killing
>> > processes running and brings up a login UI.
>> >
>> >
>> > We have been observing yocto-2.2 build failures on Ubuntu 14.04.5 and
>> > Ubuntu-16.04.1 hosts due to restart of "lightdm" (Light Desktop
>> > Manager) that is triggered by crash of "unity-settings-daemon", we
>> > couldn't figure out any workaround so far to overcome the issue. The
>> > build goes fine in the beginning but eventually the unity desktop
>> > logs out and kills all the processes running in the user session
>> > (including bitbake) and lands us into "Login screen" and when we
>> > login its a new session where as the bitbake running in previous
>> > session is killed and we need to continue the build. This is
>> > happening consistently when the user logs into desktop via lightdm
>> > and triggers a build.
>> >
>> > Another interesting thing to notice is the build goes fine if we
>> > connect to host via. SSH session and invoke a bitbake build. We are
>> > suspecting on unity-settings-daemon that is crashing consistently and
>> > is evident from the ".xsession-errors" log file as shown below:
>> >
>> > builder@ubuntu:~$ cat .xsession-errors.old
>> > Script for ibus started at run_im.
>> > Script for auto started at run_im.
>> > Script for default started at run_im.
>> > init: Disconnected from notified D-Bus bus
>> > init:"unity-settings-daemon main process (2076) terminated with
>> > status 1"
>> > init: indicator-bluetooth main process (2212) killed by TERM signal
>> > init: indicator-power main process (2214) killed by TERM signal
>> > init: indicator-datetime main process (2215) killed by TERM signal
>> > init: indicator-printers main process (2222) killed by TERM signal
>> > init: indicator-session main process (2245) killed by TERM signal
>> > init: indicator-application main process (2270) killed by TERM signal
>> >
>> > Corresponding unity-settings-daemon bug reported in Launchpad:
>> >
>> > https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/
>> > 1546641
>> >
>> > Would anyone kindly confirm the logout behaviour during bitbake
>> > process on Ubuntu-14.04.5 & Ubuntu-16.04.1 ? Since Yocto 2.2 mentions
>> > both Ubuntu-14.04 & 16.04 as supported distributions this blocker
>> > issue must be resolved at earliest.
>> >
>> > Appreciate your Inputs !
>>
>> What would really help is knowing what recipe is being built when this
>> happens. There are a few ways you might be able to figure this out:
>>
>> a) Watching the screen to see which recipes were building when it
>> happens
>> b) Perhaps using some kind of screen recorder to automate this, you'd
>> be able to review the recording to see when it breaks
>> c) Looking at the bitbake/build logs to see what it was doing when the
>> build broke (assuming bitbake stops when the session dies).
>>
>> "bitbake | cat" can provide better output for this since it will
>> produce a scrolling log rather than the more interactive UI.
>>
>> Once you find the problematic recipe, a "bitbake XXX -c clean; bitbake
>> XXX" should hopefully reproduce this more easily.
>>
>> Cheers,
>>
>> Richard
>>
>
>
[-- Attachment #2: Type: text/html, Size: 13360 bytes --]
^ permalink raw reply
* [PATCH v2 0/1] kexec-tools: Upgrade to 2.0.14
From: zhe.he @ 2016-12-27 6:43 UTC (permalink / raw)
To: openembedded-core
From: He Zhe <zhe.he@windriver.com>
Remove kexec-aarch64.patch since it has been merged upstream
Remove kexec-x32.patch since it has been reverted upstream
Backport patches for kdump arm64 from:
https://git.linaro.org/people/takahiro.akashi/kexec-tools.git
v1 to v2: Remove redundant tarball link in SRC_URI
He Zhe (1):
kexec-tools: Upgrade to 2.0.14
...nd-the-semantics-of-kexec_iomem_for_each_.patch | 78 ++++++++
...eneralize-and-rename-get_kernel_stext_sym.patch | 194 ++++++++++++++++++++
...0003-arm64-identify-PHYS_OFFSET-correctly.patch | 76 ++++++++
.../0004-arm64-kdump-identify-memory-regions.patch | 202 +++++++++++++++++++++
...5-arm64-kdump-add-elf-core-header-segment.patch | 191 +++++++++++++++++++
...6-arm64-kdump-set-up-kernel-image-segment.patch | 137 ++++++++++++++
.../0007-arm64-kdump-set-up-other-segments.patch | 35 ++++
...-add-DT-properties-to-crash-dump-kernel-s.patch | 150 +++++++++++++++
...-kdump-Add-support-for-binary-image-files.patch | 52 ++++++
meta/recipes-kernel/kexec/kexec-tools_2.0.12.bb | 37 ----
meta/recipes-kernel/kexec/kexec-tools_2.0.14.bb | 44 +++++
11 files changed, 1159 insertions(+), 37 deletions(-)
create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0001-kexec-exntend-the-semantics-of-kexec_iomem_for_each_.patch
create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0002-kexec-generalize-and-rename-get_kernel_stext_sym.patch
create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0003-arm64-identify-PHYS_OFFSET-correctly.patch
create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0004-arm64-kdump-identify-memory-regions.patch
create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0005-arm64-kdump-add-elf-core-header-segment.patch
create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0006-arm64-kdump-set-up-kernel-image-segment.patch
create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0007-arm64-kdump-set-up-other-segments.patch
create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0008-arm64-kdump-add-DT-properties-to-crash-dump-kernel-s.patch
create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0009-arm64-kdump-Add-support-for-binary-image-files.patch
delete mode 100644 meta/recipes-kernel/kexec/kexec-tools_2.0.12.bb
create mode 100644 meta/recipes-kernel/kexec/kexec-tools_2.0.14.bb
--
2.8.3
^ permalink raw reply
* [PATCH] sysvinit-inittab: Make sure new shell from start_getty gets a controlling tty
From: Yong, Jonathan @ 2016-12-27 6:47 UTC (permalink / raw)
To: openembedded-core; +Cc: kim.tatt.chuah
Without exec, the processes from the new shell do not get a ctty:
root@intel-corei7-64:~# ps -x | grep getty
755 tty1 Ss+ 0:00 /sbin/getty 38400 tty1
791 ? Ss 0:00 /bin/sh /bin/start_getty 115200 ttyS0
804 ? S 0:00 grep getty
In particular, the openssh client fails:
root@intel-corei7-64:~# ssh -v <target>
<truncated>
debug1: read_passphrase: can't open /dev/tty: No such device or address
Host key verification failed.
This patch fixes those errors.
Signed-off-by: Yong, Jonathan <jonathan.yong@intel.com>
---
meta/recipes-core/sysvinit/sysvinit-inittab/start_getty | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-core/sysvinit/sysvinit-inittab/start_getty b/meta/recipes-core/sysvinit/sysvinit-inittab/start_getty
index e3d052a..ab238f6 100644
--- a/meta/recipes-core/sysvinit/sysvinit-inittab/start_getty
+++ b/meta/recipes-core/sysvinit/sysvinit-inittab/start_getty
@@ -1,5 +1,5 @@
#!/bin/sh
if [ -c /dev/$2 ]
then
- /sbin/getty -L $1 $2 $3
+ exec /sbin/getty -L $1 $2 $3
fi
--
2.10.2
^ permalink raw reply related
* [PATCH v2 1/1] kexec-tools: Upgrade to 2.0.14
From: zhe.he @ 2016-12-27 6:43 UTC (permalink / raw)
To: openembedded-core
In-Reply-To: <cover.1482820529.git.zhe.he@windriver.com>
From: He Zhe <zhe.he@windriver.com>
Remove kexec-aarch64.patch since it has been merged upstream
Remove kexec-x32.patch since it has been reverted upstream
Backport patches for kdump arm64 from:
https://git.linaro.org/people/takahiro.akashi/kexec-tools.git
Signed-off-by: He Zhe <zhe.he@windriver.com>
---
...nd-the-semantics-of-kexec_iomem_for_each_.patch | 78 ++++++++
...eneralize-and-rename-get_kernel_stext_sym.patch | 194 ++++++++++++++++++++
...0003-arm64-identify-PHYS_OFFSET-correctly.patch | 76 ++++++++
.../0004-arm64-kdump-identify-memory-regions.patch | 202 +++++++++++++++++++++
| 191 +++++++++++++++++++
...6-arm64-kdump-set-up-kernel-image-segment.patch | 137 ++++++++++++++
.../0007-arm64-kdump-set-up-other-segments.patch | 35 ++++
...-add-DT-properties-to-crash-dump-kernel-s.patch | 150 +++++++++++++++
...-kdump-Add-support-for-binary-image-files.patch | 52 ++++++
meta/recipes-kernel/kexec/kexec-tools_2.0.12.bb | 37 ----
meta/recipes-kernel/kexec/kexec-tools_2.0.14.bb | 44 +++++
11 files changed, 1159 insertions(+), 37 deletions(-)
create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0001-kexec-exntend-the-semantics-of-kexec_iomem_for_each_.patch
create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0002-kexec-generalize-and-rename-get_kernel_stext_sym.patch
create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0003-arm64-identify-PHYS_OFFSET-correctly.patch
create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0004-arm64-kdump-identify-memory-regions.patch
create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0005-arm64-kdump-add-elf-core-header-segment.patch
create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0006-arm64-kdump-set-up-kernel-image-segment.patch
create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0007-arm64-kdump-set-up-other-segments.patch
create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0008-arm64-kdump-add-DT-properties-to-crash-dump-kernel-s.patch
create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0009-arm64-kdump-Add-support-for-binary-image-files.patch
delete mode 100644 meta/recipes-kernel/kexec/kexec-tools_2.0.12.bb
create mode 100644 meta/recipes-kernel/kexec/kexec-tools_2.0.14.bb
diff --git a/meta/recipes-kernel/kexec/kexec-tools/0001-kexec-exntend-the-semantics-of-kexec_iomem_for_each_.patch b/meta/recipes-kernel/kexec/kexec-tools/0001-kexec-exntend-the-semantics-of-kexec_iomem_for_each_.patch
new file mode 100644
index 0000000..822f28c
--- /dev/null
+++ b/meta/recipes-kernel/kexec/kexec-tools/0001-kexec-exntend-the-semantics-of-kexec_iomem_for_each_.patch
@@ -0,0 +1,78 @@
+From 02eed0f8f2748fd7579f69e5373445b52b2b8754 Mon Sep 17 00:00:00 2001
+From: AKASHI Takahiro <takahiro.akashi@linaro.org>
+Date: Mon, 17 Oct 2016 13:56:58 +0900
+Subject: [PATCH 1/9] kexec: exntend the semantics of kexec_iomem_for_each_line
+
+The current kexec_iomem_for_each_line() counts up all the lines for which
+a callback function returns zero(0) or positive, and otherwise it stops
+further scanning.
+This behavior is incovenient in some cases. For instance, on arm64, we want
+to count up "System RAM" entries, but need to skip "reserved" entries.
+
+So this patch extends the semantics so that we will continue to scan
+succeeding entries but not count lines for which a callback function
+returns positive.
+
+The current users of kexec_iomem_for_each_line(), arm, sh and x86, will not
+be affected by this change because
+* arm
+ The callback function only returns -1 or 0, and the return value of
+ kexec_iomem_for_each_line() will never be used.
+* sh, x86
+ The callback function may return (-1 for sh,) 0 or 1, but always returns
+ 1 once we have reached the maximum number of entries allowed.
+ Even so the current kexec_iomem_for_each_line() counts them up.
+ This change actually fixes this bug.
+
+Upstream-Status: Backport [https://git.linaro.org/people/takahiro.akashi/kexec-tools.git]
+
+Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
+Signed-off-by: He Zhe <zhe.he@windriver.com>
+---
+ kexec/kexec-iomem.c | 15 ++++++++++-----
+ 1 file changed, 10 insertions(+), 5 deletions(-)
+
+diff --git a/kexec/kexec-iomem.c b/kexec/kexec-iomem.c
+index 485a2e8..0a0277a 100644
+--- a/kexec/kexec-iomem.c
++++ b/kexec/kexec-iomem.c
+@@ -18,6 +18,9 @@
+ * Iterate over each line in the file returned by proc_iomem(). If match is
+ * NULL or if the line matches with our match-pattern then call the
+ * callback if non-NULL.
++ * If match is NULL, callback should return a negative if error.
++ * Otherwise the interation goes on, incrementing nr but only if callback
++ * returns 0 (matched).
+ *
+ * Return the number of lines matched.
+ */
+@@ -37,7 +40,7 @@ int kexec_iomem_for_each_line(char *match,
+ char *str;
+ int consumed;
+ int count;
+- int nr = 0;
++ int nr = 0, ret;
+
+ fp = fopen(iomem, "r");
+ if (!fp)
+@@ -50,11 +53,13 @@ int kexec_iomem_for_each_line(char *match,
+ str = line + consumed;
+ size = end - start + 1;
+ if (!match || memcmp(str, match, strlen(match)) == 0) {
+- if (callback
+- && callback(data, nr, str, start, size) < 0) {
+- break;
++ if (callback) {
++ ret = callback(data, nr, str, start, size);
++ if (ret < 0)
++ break;
++ else if (ret == 0)
++ nr++;
+ }
+- nr++;
+ }
+ }
+
+--
+1.9.1
+
diff --git a/meta/recipes-kernel/kexec/kexec-tools/0002-kexec-generalize-and-rename-get_kernel_stext_sym.patch b/meta/recipes-kernel/kexec/kexec-tools/0002-kexec-generalize-and-rename-get_kernel_stext_sym.patch
new file mode 100644
index 0000000..953f13b
--- /dev/null
+++ b/meta/recipes-kernel/kexec/kexec-tools/0002-kexec-generalize-and-rename-get_kernel_stext_sym.patch
@@ -0,0 +1,194 @@
+From d29f37bb6e9114aba96c606103b110f511bee9a1 Mon Sep 17 00:00:00 2001
+From: Pratyush Anand <panand@redhat.com>
+Date: Wed, 2 Nov 2016 15:05:25 +0530
+Subject: [PATCH 2/9] kexec: generalize and rename get_kernel_stext_sym()
+
+get_kernel_stext_sym() has been defined for both arm and i386. Other
+architecture might need some other kernel symbol address. Therefore rewrite
+this function as generic function to get any kernel symbol address.
+
+More over, kallsyms is not arch specific representation, therefore have
+common function for all arches.
+
+Upstream-Status: Backport [https://git.linaro.org/people/takahiro.akashi/kexec-tools.git]
+
+Signed-off-by: Pratyush Anand <panand@redhat.com>
+[created symbols.c]
+Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
+Signed-off-by: He Zhe <zhe.he@windriver.com>
+---
+ kexec/Makefile | 1 +
+ kexec/arch/arm/crashdump-arm.c | 40 +---------------------------------------
+ kexec/arch/i386/crashdump-x86.c | 29 -----------------------------
+ kexec/kexec.h | 2 ++
+ kexec/symbols.c | 41 +++++++++++++++++++++++++++++++++++++++++
+ 5 files changed, 45 insertions(+), 68 deletions(-)
+ create mode 100644 kexec/symbols.c
+
+diff --git a/kexec/Makefile b/kexec/Makefile
+index 39f365f..2b4fb3d 100644
+--- a/kexec/Makefile
++++ b/kexec/Makefile
+@@ -26,6 +26,7 @@ KEXEC_SRCS_base += kexec/kernel_version.c
+ KEXEC_SRCS_base += kexec/lzma.c
+ KEXEC_SRCS_base += kexec/zlib.c
+ KEXEC_SRCS_base += kexec/kexec-xen.c
++KEXEC_SRCS_base += kexec/symbols.c
+
+ KEXEC_GENERATED_SRCS += $(PURGATORY_HEX_C)
+
+diff --git a/kexec/arch/arm/crashdump-arm.c b/kexec/arch/arm/crashdump-arm.c
+index 4a89b5e..245c21a 100644
+--- a/kexec/arch/arm/crashdump-arm.c
++++ b/kexec/arch/arm/crashdump-arm.c
+@@ -73,48 +73,10 @@ static struct crash_elf_info elf_info = {
+
+ extern unsigned long long user_page_offset;
+
+-/* Retrieve kernel _stext symbol virtual address from /proc/kallsyms */
+-static unsigned long long get_kernel_stext_sym(void)
+-{
+- const char *kallsyms = "/proc/kallsyms";
+- const char *stext = "_stext";
+- char sym[128];
+- char line[128];
+- FILE *fp;
+- unsigned long long vaddr = 0;
+- char type;
+-
+- fp = fopen(kallsyms, "r");
+- if (!fp) {
+- fprintf(stderr, "Cannot open %s\n", kallsyms);
+- return 0;
+- }
+-
+- while(fgets(line, sizeof(line), fp) != NULL) {
+- unsigned long long addr;
+-
+- if (sscanf(line, "%Lx %c %s", &addr, &type, sym) != 3)
+- continue;
+-
+- if (strcmp(sym, stext) == 0) {
+- dbgprintf("kernel symbol %s vaddr = %#llx\n", stext, addr);
+- vaddr = addr;
+- break;
+- }
+- }
+-
+- fclose(fp);
+-
+- if (vaddr == 0)
+- fprintf(stderr, "Cannot get kernel %s symbol address\n", stext);
+-
+- return vaddr;
+-}
+-
+ static int get_kernel_page_offset(struct kexec_info *info,
+ struct crash_elf_info *elf_info)
+ {
+- unsigned long long stext_sym_addr = get_kernel_stext_sym();
++ unsigned long long stext_sym_addr = get_kernel_sym("_stext");
+ if (stext_sym_addr == 0) {
+ if (user_page_offset != (-1ULL)) {
+ elf_info->page_offset = user_page_offset;
+diff --git a/kexec/arch/i386/crashdump-x86.c b/kexec/arch/i386/crashdump-x86.c
+index ab833d4..abf82a5 100644
+--- a/kexec/arch/i386/crashdump-x86.c
++++ b/kexec/arch/i386/crashdump-x86.c
+@@ -102,35 +102,6 @@ static int get_kernel_paddr(struct kexec_info *UNUSED(info),
+ return -1;
+ }
+
+-/* Retrieve kernel symbol virtual address from /proc/kallsyms */
+-static unsigned long long get_kernel_sym(const char *symbol)
+-{
+- const char *kallsyms = "/proc/kallsyms";
+- char sym[128];
+- char line[128];
+- FILE *fp;
+- unsigned long long vaddr;
+- char type;
+-
+- fp = fopen(kallsyms, "r");
+- if (!fp) {
+- fprintf(stderr, "Cannot open %s\n", kallsyms);
+- return 0;
+- }
+-
+- while(fgets(line, sizeof(line), fp) != NULL) {
+- if (sscanf(line, "%Lx %c %s", &vaddr, &type, sym) != 3)
+- continue;
+- if (strcmp(sym, symbol) == 0) {
+- dbgprintf("kernel symbol %s vaddr = %16llx\n", symbol, vaddr);
+- return vaddr;
+- }
+- }
+-
+- fprintf(stderr, "Cannot get kernel %s symbol address\n", symbol);
+- return 0;
+-}
+-
+ /* Retrieve info regarding virtual address kernel has been compiled for and
+ * size of the kernel from /proc/kcore. Current /proc/kcore parsing from
+ * from kexec-tools fails because of malformed elf notes. A kernel patch has
+diff --git a/kexec/kexec.h b/kexec/kexec.h
+index 9194f1c..b4fafad 100644
+--- a/kexec/kexec.h
++++ b/kexec/kexec.h
+@@ -312,4 +312,6 @@ int xen_kexec_load(struct kexec_info *info);
+ int xen_kexec_unload(uint64_t kexec_flags);
+ void xen_kexec_exec(void);
+
++extern unsigned long long get_kernel_sym(const char *text);
++
+ #endif /* KEXEC_H */
+diff --git a/kexec/symbols.c b/kexec/symbols.c
+new file mode 100644
+index 0000000..ea6e327
+--- /dev/null
++++ b/kexec/symbols.c
+@@ -0,0 +1,41 @@
++#include <stdio.h>
++#include <string.h>
++#include "kexec.h"
++
++/* Retrieve kernel symbol virtual address from /proc/kallsyms */
++unsigned long long get_kernel_sym(const char *text)
++{
++ const char *kallsyms = "/proc/kallsyms";
++ char sym[128];
++ char line[128];
++ FILE *fp;
++ unsigned long long vaddr = 0;
++ char type;
++
++ fp = fopen(kallsyms, "r");
++ if (!fp) {
++ fprintf(stderr, "Cannot open %s\n", kallsyms);
++ return 0;
++ }
++
++ while (fgets(line, sizeof(line), fp) != NULL) {
++ unsigned long long addr;
++
++ if (sscanf(line, "%Lx %c %s", &addr, &type, sym) != 3)
++ continue;
++
++ if (strcmp(sym, text) == 0) {
++ dbgprintf("kernel symbol %s vaddr = %#llx\n",
++ text, addr);
++ vaddr = addr;
++ break;
++ }
++ }
++
++ fclose(fp);
++
++ if (vaddr == 0)
++ fprintf(stderr, "Cannot get kernel %s symbol address\n", text);
++
++ return vaddr;
++}
+--
+1.9.1
+
diff --git a/meta/recipes-kernel/kexec/kexec-tools/0003-arm64-identify-PHYS_OFFSET-correctly.patch b/meta/recipes-kernel/kexec/kexec-tools/0003-arm64-identify-PHYS_OFFSET-correctly.patch
new file mode 100644
index 0000000..1a1c317
--- /dev/null
+++ b/meta/recipes-kernel/kexec/kexec-tools/0003-arm64-identify-PHYS_OFFSET-correctly.patch
@@ -0,0 +1,76 @@
+From 16df170ad4808d12acd5e919ac4f6e7f33a247b3 Mon Sep 17 00:00:00 2001
+From: AKASHI Takahiro <takahiro.akashi@linaro.org>
+Date: Thu, 1 Sep 2016 10:57:42 +0900
+Subject: [PATCH 3/9] arm64: identify PHYS_OFFSET correctly
+
+Due to the kernel patch, commit e7cd190385d1 ("arm64: mark reserved
+memblock regions explicitly in iomem"), the current code will not be able
+to identify the correct value of PHYS_OFFSET if some "reserved" memory
+region, which is likely to be UEFI runtime services code/data, exists at
+an address below the first "System RAM" regions.
+
+This patch fixes this issue.
+
+Upstream-Status: Backport [https://git.linaro.org/people/takahiro.akashi/kexec-tools.git]
+
+Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
+Signed-off-by: He Zhe <zhe.he@windriver.com>
+---
+ kexec/arch/arm64/iomem.h | 7 +++++++
+ kexec/arch/arm64/kexec-arm64.c | 12 ++++++++++--
+ 2 files changed, 17 insertions(+), 2 deletions(-)
+ create mode 100644 kexec/arch/arm64/iomem.h
+
+diff --git a/kexec/arch/arm64/iomem.h b/kexec/arch/arm64/iomem.h
+new file mode 100644
+index 0000000..7fd66eb
+--- /dev/null
++++ b/kexec/arch/arm64/iomem.h
+@@ -0,0 +1,7 @@
++#ifndef IOMEM_H
++#define IOMEM_H
++
++#define SYSTEM_RAM "System RAM\n"
++#define IOMEM_RESERVED "reserved\n"
++
++#endif
+diff --git a/kexec/arch/arm64/kexec-arm64.c b/kexec/arch/arm64/kexec-arm64.c
+index 2e8839a..8ac811d 100644
+--- a/kexec/arch/arm64/kexec-arm64.c
++++ b/kexec/arch/arm64/kexec-arm64.c
+@@ -21,6 +21,7 @@
+ #include "crashdump-arm64.h"
+ #include "dt-ops.h"
+ #include "fs2dt.h"
++#include "iomem.h"
+ #include "kexec-syscall.h"
+ #include "arch/options.h"
+
+@@ -475,7 +476,14 @@ static int get_memory_ranges_iomem_cb(void *data, int nr, char *str,
+ return -1;
+
+ r = (struct memory_range *)data + nr;
+- r->type = RANGE_RAM;
++
++ if (!strncmp(str, SYSTEM_RAM, strlen(SYSTEM_RAM)))
++ r->type = RANGE_RAM;
++ else if (!strncmp(str, IOMEM_RESERVED, strlen(IOMEM_RESERVED)))
++ r->type = RANGE_RESERVED;
++ else
++ return 1;
++
+ r->start = base;
+ r->end = base + length - 1;
+
+@@ -494,7 +502,7 @@ static int get_memory_ranges_iomem_cb(void *data, int nr, char *str,
+ static int get_memory_ranges_iomem(struct memory_range *array,
+ unsigned int *count)
+ {
+- *count = kexec_iomem_for_each_line("System RAM\n",
++ *count = kexec_iomem_for_each_line(NULL,
+ get_memory_ranges_iomem_cb, array);
+
+ if (!*count) {
+--
+1.9.1
+
diff --git a/meta/recipes-kernel/kexec/kexec-tools/0004-arm64-kdump-identify-memory-regions.patch b/meta/recipes-kernel/kexec/kexec-tools/0004-arm64-kdump-identify-memory-regions.patch
new file mode 100644
index 0000000..66600f3
--- /dev/null
+++ b/meta/recipes-kernel/kexec/kexec-tools/0004-arm64-kdump-identify-memory-regions.patch
@@ -0,0 +1,202 @@
+From 48a4c7874d8264ddbfaec2e9858d7866a2d2eb60 Mon Sep 17 00:00:00 2001
+From: AKASHI Takahiro <takahiro.akashi@linaro.org>
+Date: Wed, 5 Aug 2015 13:16:30 +0900
+Subject: [PATCH 4/9] arm64: kdump: identify memory regions
+
+The following regions need to be identified for later use:
+ a) memory regions which belong to the 1st kernel
+ b) usable memory reserved for crash dump kernel
+
+We go through /proc/iomem to find out a) and b) which are marked
+as "System RAM" and "Crash kernel", respectively.
+
+Upstream-Status: Backport [https://git.linaro.org/people/takahiro.akashi/kexec-tools.git]
+
+Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
+Signed-off-by: He Zhe <zhe.he@windriver.com>
+---
+ kexec/arch/arm64/Makefile | 2 +
+ kexec/arch/arm64/crashdump-arm64.c | 100 ++++++++++++++++++++++++++++++++++++-
+ kexec/arch/arm64/crashdump-arm64.h | 14 +++++-
+ kexec/arch/arm64/iomem.h | 1 +
+ 4 files changed, 114 insertions(+), 3 deletions(-)
+
+diff --git a/kexec/arch/arm64/Makefile b/kexec/arch/arm64/Makefile
+index 74b677f..2d4ae0e 100644
+--- a/kexec/arch/arm64/Makefile
++++ b/kexec/arch/arm64/Makefile
+@@ -6,6 +6,8 @@ arm64_FS2DT_INCLUDE += \
+
+ arm64_DT_OPS += kexec/dt-ops.c
+
++arm64_MEM_REGIONS = kexec/mem_regions.c
++
+ arm64_CPPFLAGS += -I $(srcdir)/kexec/
+
+ arm64_KEXEC_SRCS += \
+diff --git a/kexec/arch/arm64/crashdump-arm64.c b/kexec/arch/arm64/crashdump-arm64.c
+index d2272c8..dcaca43 100644
+--- a/kexec/arch/arm64/crashdump-arm64.c
++++ b/kexec/arch/arm64/crashdump-arm64.c
+@@ -1,5 +1,13 @@
+ /*
+ * ARM64 crashdump.
++ * partly derived from arm implementation
++ *
++ * Copyright (c) 2014-2016 Linaro Limited
++ * Author: AKASHI Takahiro <takahiro.akashi@linaro.org>
++ *
++ * This program is free software; you can redistribute it and/or modify
++ * it under the terms of the GNU General Public License version 2 as
++ * published by the Free Software Foundation.
+ */
+
+ #define _GNU_SOURCE
+@@ -10,12 +18,102 @@
+ #include "kexec.h"
+ #include "crashdump.h"
+ #include "crashdump-arm64.h"
++#include "iomem.h"
+ #include "kexec-arm64.h"
+ #include "kexec-elf.h"
++#include "mem_regions.h"
+
+-struct memory_ranges usablemem_rgns = {};
++/* memory ranges on crashed kernel */
++static struct memory_range crash_memory_ranges[CRASH_MAX_MEMORY_RANGES];
++static struct memory_ranges crash_memory_rgns = {
++ .size = 0,
++ .max_size = CRASH_MAX_MEMORY_RANGES,
++ .ranges = crash_memory_ranges,
++};
++
++/* memory range reserved for crashkernel */
++struct memory_range crash_reserved_mem;
++struct memory_ranges usablemem_rgns = {
++ .size = 0,
++ .max_size = 1,
++ .ranges = &crash_reserved_mem,
++};
++
++/*
++ * iomem_range_callback() - callback called for each iomem region
++ * @data: not used
++ * @nr: not used
++ * @str: name of the memory region
++ * @base: start address of the memory region
++ * @length: size of the memory region
++ *
++ * This function is called once for each memory region found in /proc/iomem.
++ * It locates system RAM and crashkernel reserved memory and places these to
++ * variables, respectively, crash_memory_ranges and crash_reserved_mem.
++ */
++
++static int iomem_range_callback(void *UNUSED(data), int UNUSED(nr),
++ char *str, unsigned long long base,
++ unsigned long long length)
++{
++ if (strncmp(str, CRASH_KERNEL, strlen(CRASH_KERNEL)) == 0)
++ return mem_regions_add(&usablemem_rgns,
++ base, length, RANGE_RAM);
++ else if (strncmp(str, SYSTEM_RAM, strlen(SYSTEM_RAM)) == 0)
++ return mem_regions_add(&crash_memory_rgns,
++ base, length, RANGE_RAM);
++
++ return 0;
++}
+
+ int is_crashkernel_mem_reserved(void)
+ {
++ if (!crash_reserved_mem.end)
++ kexec_iomem_for_each_line(NULL, iomem_range_callback, NULL);
++
++ return crash_reserved_mem.start != crash_reserved_mem.end;
++}
++
++/*
++ * crash_get_memory_ranges() - read system physical memory
++ *
++ * Function reads through system physical memory and stores found memory
++ * regions in crash_memory_ranges.
++ * Regions are sorted in ascending order.
++ *
++ * Returns 0 in case of success and -1 otherwise (errno is set).
++ */
++static int crash_get_memory_ranges(void)
++{
++ /*
++ * First read all memory regions that can be considered as
++ * system memory including the crash area.
++ */
++ if (!usablemem_rgns.size)
++ kexec_iomem_for_each_line(NULL, iomem_range_callback, NULL);
++
++ /* allow only a single region for crash dump kernel */
++ if (usablemem_rgns.size != 1) {
++ errno = EINVAL;
++ return -1;
++ }
++
++ dbgprint_mem_range("Reserved memory range", &crash_reserved_mem, 1);
++
++ if (mem_regions_exclude(&crash_memory_rgns, &crash_reserved_mem)) {
++ fprintf(stderr,
++ "Error: Number of crash memory ranges excedeed the max limit\n");
++ errno = ENOMEM;
++ return -1;
++ }
++
++ /*
++ * Make sure that the memory regions are sorted.
++ */
++ mem_regions_sort(&crash_memory_rgns);
++
++ dbgprint_mem_range("Coredump memory ranges",
++ crash_memory_rgns.ranges, crash_memory_rgns.size);
++
+ return 0;
+ }
+diff --git a/kexec/arch/arm64/crashdump-arm64.h b/kexec/arch/arm64/crashdump-arm64.h
+index f33c7a2..07a0ed0 100644
+--- a/kexec/arch/arm64/crashdump-arm64.h
++++ b/kexec/arch/arm64/crashdump-arm64.h
+@@ -1,12 +1,22 @@
+ /*
+ * ARM64 crashdump.
++ *
++ * Copyright (c) 2014-2016 Linaro Limited
++ * Author: AKASHI Takahiro <takahiro.akashi@linaro.org>
++ *
++ * This program is free software; you can redistribute it and/or modify
++ * it under the terms of the GNU General Public License version 2 as
++ * published by the Free Software Foundation.
+ */
+
+-#if !defined(CRASHDUMP_ARM64_H)
++#ifndef CRASHDUMP_ARM64_H
+ #define CRASHDUMP_ARM64_H
+
+ #include "kexec.h"
+
++#define CRASH_MAX_MEMORY_RANGES 32
++
+ extern struct memory_ranges usablemem_rgns;
++extern struct memory_range crash_reserved_mem;
+
+-#endif
++#endif /* CRASHDUMP_ARM64_H */
+diff --git a/kexec/arch/arm64/iomem.h b/kexec/arch/arm64/iomem.h
+index 7fd66eb..20cda87 100644
+--- a/kexec/arch/arm64/iomem.h
++++ b/kexec/arch/arm64/iomem.h
+@@ -2,6 +2,7 @@
+ #define IOMEM_H
+
+ #define SYSTEM_RAM "System RAM\n"
++#define CRASH_KERNEL "Crash kernel\n"
+ #define IOMEM_RESERVED "reserved\n"
+
+ #endif
+--
+1.9.1
+
--git a/meta/recipes-kernel/kexec/kexec-tools/0005-arm64-kdump-add-elf-core-header-segment.patch b/meta/recipes-kernel/kexec/kexec-tools/0005-arm64-kdump-add-elf-core-header-segment.patch
new file mode 100644
index 0000000..fe535b6
--- /dev/null
+++ b/meta/recipes-kernel/kexec/kexec-tools/0005-arm64-kdump-add-elf-core-header-segment.patch
@@ -0,0 +1,191 @@
+From 769da25627cebb2a53caee5d5be78a32d376adc1 Mon Sep 17 00:00:00 2001
+From: AKASHI Takahiro <takahiro.akashi@linaro.org>
+Date: Wed, 5 Aug 2015 13:45:15 +0900
+Subject: [PATCH 5/9] arm64: kdump: add elf core header segment
+
+Elf core header contains the information necessary for the coredump of
+the 1st kernel, including its physcal memory layout as well as cpu register
+states at the panic.
+The segment is allocated inside the reserved memory of crash dump kernel.
+
+Upstream-Status: Backport [https://git.linaro.org/people/takahiro.akashi/kexec-tools.git]
+
+Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
+Signed-off-by: He Zhe <zhe.he@windriver.com>
+---
+ kexec/arch/arm64/crashdump-arm64.c | 96 ++++++++++++++++++++++++++++++++++++++
+ kexec/arch/arm64/crashdump-arm64.h | 3 ++
+ kexec/arch/arm64/iomem.h | 2 +
+ kexec/arch/arm64/kexec-elf-arm64.c | 10 ++++
+ 4 files changed, 111 insertions(+)
+
+diff --git a/kexec/arch/arm64/crashdump-arm64.c b/kexec/arch/arm64/crashdump-arm64.c
+index dcaca43..8346131 100644
+--- a/kexec/arch/arm64/crashdump-arm64.c
++++ b/kexec/arch/arm64/crashdump-arm64.c
+@@ -39,6 +39,39 @@ struct memory_ranges usablemem_rgns = {
+ .ranges = &crash_reserved_mem,
+ };
+
++struct memory_range elfcorehdr_mem;
++
++static struct crash_elf_info elf_info = {
++ .class = ELFCLASS64,
++#if (__BYTE_ORDER == __LITTLE_ENDIAN)
++ .data = ELFDATA2LSB,
++#else
++ .data = ELFDATA2MSB,
++#endif
++ .machine = EM_AARCH64,
++};
++
++/*
++ * Note: The returned value is correct only if !CONFIG_RANDOMIZE_BASE.
++ */
++static uint64_t get_kernel_page_offset(void)
++{
++ int i;
++
++ if (elf_info.kern_vaddr_start == UINT64_MAX)
++ return UINT64_MAX;
++
++ /* Current max virtual memory range is 48-bits. */
++ for (i = 48; i > 0; i--)
++ if (!(elf_info.kern_vaddr_start & (1UL << i)))
++ break;
++
++ if (i <= 0)
++ return UINT64_MAX;
++ else
++ return UINT64_MAX << i;
++}
++
+ /*
+ * iomem_range_callback() - callback called for each iomem region
+ * @data: not used
+@@ -62,6 +95,10 @@ static int iomem_range_callback(void *UNUSED(data), int UNUSED(nr),
+ else if (strncmp(str, SYSTEM_RAM, strlen(SYSTEM_RAM)) == 0)
+ return mem_regions_add(&crash_memory_rgns,
+ base, length, RANGE_RAM);
++ else if (strncmp(str, KERNEL_CODE, strlen(KERNEL_CODE)) == 0)
++ elf_info.kern_paddr_start = base;
++ else if (strncmp(str, KERNEL_DATA, strlen(KERNEL_DATA)) == 0)
++ elf_info.kern_size = base + length - elf_info.kern_paddr_start;
+
+ return 0;
+ }
+@@ -115,5 +152,64 @@ static int crash_get_memory_ranges(void)
+ dbgprint_mem_range("Coredump memory ranges",
+ crash_memory_rgns.ranges, crash_memory_rgns.size);
+
++ /*
++ * For additional kernel code/data segment.
++ * kern_paddr_start/kern_size are determined in iomem_range_callback
++ */
++ elf_info.kern_vaddr_start = get_kernel_sym("_text");
++ if (!elf_info.kern_vaddr_start)
++ elf_info.kern_vaddr_start = UINT64_MAX;
++
++ return 0;
++}
++
++/*
++ * load_crashdump_segments() - load the elf core header
++ * @info: kexec info structure
++ *
++ * This function creates and loads an additional segment of elf core header
++ : which is used to construct /proc/vmcore on crash dump kernel.
++ *
++ * Return 0 in case of success and -1 in case of error.
++ */
++
++int load_crashdump_segments(struct kexec_info *info)
++{
++ unsigned long elfcorehdr;
++ unsigned long bufsz;
++ void *buf;
++ int err;
++
++ /*
++ * First fetch all the memory (RAM) ranges that we are going to
++ * pass to the crash dump kernel during panic.
++ */
++
++ err = crash_get_memory_ranges();
++
++ if (err)
++ return err;
++
++ elf_info.page_offset = get_kernel_page_offset();
++ dbgprintf("%s: page_offset: %016llx\n", __func__,
++ elf_info.page_offset);
++
++ err = crash_create_elf64_headers(info, &elf_info,
++ crash_memory_rgns.ranges, crash_memory_rgns.size,
++ &buf, &bufsz, ELF_CORE_HEADER_ALIGN);
++
++ if (err)
++ return err;
++
++ elfcorehdr = add_buffer_phys_virt(info, buf, bufsz, bufsz, 0,
++ crash_reserved_mem.start, crash_reserved_mem.end,
++ -1, 0);
++
++ elfcorehdr_mem.start = elfcorehdr;
++ elfcorehdr_mem.end = elfcorehdr + bufsz - 1;
++
++ dbgprintf("%s: elfcorehdr 0x%llx-0x%llx\n", __func__,
++ elfcorehdr_mem.start, elfcorehdr_mem.end);
++
+ return 0;
+ }
+diff --git a/kexec/arch/arm64/crashdump-arm64.h b/kexec/arch/arm64/crashdump-arm64.h
+index 07a0ed0..da75a2d 100644
+--- a/kexec/arch/arm64/crashdump-arm64.h
++++ b/kexec/arch/arm64/crashdump-arm64.h
+@@ -18,5 +18,8 @@
+
+ extern struct memory_ranges usablemem_rgns;
+ extern struct memory_range crash_reserved_mem;
++extern struct memory_range elfcorehdr_mem;
++
++extern int load_crashdump_segments(struct kexec_info *info);
+
+ #endif /* CRASHDUMP_ARM64_H */
+diff --git a/kexec/arch/arm64/iomem.h b/kexec/arch/arm64/iomem.h
+index 20cda87..d4864bb 100644
+--- a/kexec/arch/arm64/iomem.h
++++ b/kexec/arch/arm64/iomem.h
+@@ -2,6 +2,8 @@
+ #define IOMEM_H
+
+ #define SYSTEM_RAM "System RAM\n"
++#define KERNEL_CODE "Kernel code\n"
++#define KERNEL_DATA "Kernel data\n"
+ #define CRASH_KERNEL "Crash kernel\n"
+ #define IOMEM_RESERVED "reserved\n"
+
+diff --git a/kexec/arch/arm64/kexec-elf-arm64.c b/kexec/arch/arm64/kexec-elf-arm64.c
+index daf8bf0..c70a37a 100644
+--- a/kexec/arch/arm64/kexec-elf-arm64.c
++++ b/kexec/arch/arm64/kexec-elf-arm64.c
+@@ -119,6 +119,16 @@ int elf_arm64_load(int argc, char **argv, const char *kernel_buf,
+ dbgprintf("%s: PE format: %s\n", __func__,
+ (arm64_header_check_pe_sig(header) ? "yes" : "no"));
+
++ if (info->kexec_flags & KEXEC_ON_CRASH) {
++ /* create and initialize elf core header segment */
++ result = load_crashdump_segments(info);
++ if (result) {
++ dbgprintf("%s: Creating eflcorehdr failed.\n",
++ __func__);
++ goto exit;
++ }
++ }
++
+ /* load the kernel */
+ result = elf_exec_load(&ehdr, info);
+
+--
+1.9.1
+
diff --git a/meta/recipes-kernel/kexec/kexec-tools/0006-arm64-kdump-set-up-kernel-image-segment.patch b/meta/recipes-kernel/kexec/kexec-tools/0006-arm64-kdump-set-up-kernel-image-segment.patch
new file mode 100644
index 0000000..4149551
--- /dev/null
+++ b/meta/recipes-kernel/kexec/kexec-tools/0006-arm64-kdump-set-up-kernel-image-segment.patch
@@ -0,0 +1,137 @@
+From 4079c93ac5453ef5f7889ab64920c1e9427690ef Mon Sep 17 00:00:00 2001
+From: AKASHI Takahiro <takahiro.akashi@linaro.org>
+Date: Tue, 17 Feb 2015 16:06:55 +0900
+Subject: [PATCH 6/9] arm64: kdump: set up kernel image segment
+
+On arm64, we can use the same kernel image as 1st kernel, but
+we have to modify the entry point as well as segments' addresses
+in the kernel's elf header in order to load them into correct places.
+
+Upstream-Status: Backport [https://git.linaro.org/people/takahiro.akashi/kexec-tools.git]
+
+Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
+Signed-off-by: He Zhe <zhe.he@windriver.com>
+---
+ kexec/arch/arm64/crashdump-arm64.c | 23 +++++++++++++++++++++++
+ kexec/arch/arm64/crashdump-arm64.h | 1 +
+ kexec/arch/arm64/kexec-arm64.c | 25 ++++++++++++++++++++-----
+ kexec/arch/arm64/kexec-elf-arm64.c | 10 +++++++++-
+ 4 files changed, 53 insertions(+), 6 deletions(-)
+
+diff --git a/kexec/arch/arm64/crashdump-arm64.c b/kexec/arch/arm64/crashdump-arm64.c
+index 8346131..9517329 100644
+--- a/kexec/arch/arm64/crashdump-arm64.c
++++ b/kexec/arch/arm64/crashdump-arm64.c
+@@ -213,3 +213,26 @@ int load_crashdump_segments(struct kexec_info *info)
+
+ return 0;
+ }
++
++/*
++ * e_entry and p_paddr are actually in virtual address space.
++ * Those values will be translated to physcal addresses by
++ * using virt_to_phys().
++ * So let's get ready for later use so the memory base (phys_offset)
++ * will be correctly replaced with crash_reserved_mem.start.
++ */
++void modify_ehdr_for_crashdump(struct mem_ehdr *ehdr)
++{
++ struct mem_phdr *phdr;
++ int i;
++
++ ehdr->e_entry += - arm64_mem.phys_offset + crash_reserved_mem.start;
++
++ for (i = 0; i < ehdr->e_phnum; i++) {
++ phdr = &ehdr->e_phdr[i];
++ if (phdr->p_type != PT_LOAD)
++ continue;
++ phdr->p_paddr +=
++ (-arm64_mem.phys_offset + crash_reserved_mem.start);
++ }
++}
+diff --git a/kexec/arch/arm64/crashdump-arm64.h b/kexec/arch/arm64/crashdump-arm64.h
+index da75a2d..382f571 100644
+--- a/kexec/arch/arm64/crashdump-arm64.h
++++ b/kexec/arch/arm64/crashdump-arm64.h
+@@ -21,5 +21,6 @@ extern struct memory_range crash_reserved_mem;
+ extern struct memory_range elfcorehdr_mem;
+
+ extern int load_crashdump_segments(struct kexec_info *info);
++extern void modify_ehdr_for_crashdump(struct mem_ehdr *ehdr);
+
+ #endif /* CRASHDUMP_ARM64_H */
+diff --git a/kexec/arch/arm64/kexec-arm64.c b/kexec/arch/arm64/kexec-arm64.c
+index 8ac811d..cec4e41 100644
+--- a/kexec/arch/arm64/kexec-arm64.c
++++ b/kexec/arch/arm64/kexec-arm64.c
+@@ -307,12 +307,27 @@ unsigned long arm64_locate_kernel_segment(struct kexec_info *info)
+ {
+ unsigned long hole;
+
+- hole = locate_hole(info,
+- arm64_mem.text_offset + arm64_mem.image_size,
+- MiB(2), 0, ULONG_MAX, 1);
++ if (info->kexec_flags & KEXEC_ON_CRASH) {
++ unsigned long hole_end;
++
++ hole = (crash_reserved_mem.start < mem_min ?
++ mem_min : crash_reserved_mem.start);
++ hole = _ALIGN_UP(hole, MiB(2));
++ hole_end = hole + arm64_mem.text_offset + arm64_mem.image_size;
++
++ if ((hole_end > mem_max) ||
++ (hole_end > crash_reserved_mem.end)) {
++ dbgprintf("%s: Crash kernel out of range\n", __func__);
++ hole = ULONG_MAX;
++ }
++ } else {
++ hole = locate_hole(info,
++ arm64_mem.text_offset + arm64_mem.image_size,
++ MiB(2), 0, ULONG_MAX, 1);
+
+- if (hole == ULONG_MAX)
+- dbgprintf("%s: locate_hole failed\n", __func__);
++ if (hole == ULONG_MAX)
++ dbgprintf("%s: locate_hole failed\n", __func__);
++ }
+
+ return hole;
+ }
+diff --git a/kexec/arch/arm64/kexec-elf-arm64.c b/kexec/arch/arm64/kexec-elf-arm64.c
+index c70a37a..842ce21 100644
+--- a/kexec/arch/arm64/kexec-elf-arm64.c
++++ b/kexec/arch/arm64/kexec-elf-arm64.c
+@@ -9,6 +9,7 @@
+ #include <stdlib.h>
+ #include <linux/elf.h>
+
++#include "crashdump-arm64.h"
+ #include "kexec-arm64.h"
+ #include "kexec-elf.h"
+ #include "kexec-syscall.h"
+@@ -105,7 +106,8 @@ int elf_arm64_load(int argc, char **argv, const char *kernel_buf,
+ }
+
+ arm64_mem.vp_offset = _ALIGN_DOWN(ehdr.e_entry, MiB(2));
+- arm64_mem.vp_offset -= kernel_segment - get_phys_offset();
++ if (!(info->kexec_flags & KEXEC_ON_CRASH))
++ arm64_mem.vp_offset -= kernel_segment - get_phys_offset();
+
+ dbgprintf("%s: kernel_segment: %016lx\n", __func__, kernel_segment);
+ dbgprintf("%s: text_offset: %016lx\n", __func__,
+@@ -127,6 +129,12 @@ int elf_arm64_load(int argc, char **argv, const char *kernel_buf,
+ __func__);
+ goto exit;
+ }
++
++ /*
++ * offset addresses in order to fit vmlinux
++ * (elf_exec) into crash kernel's memory
++ */
++ modify_ehdr_for_crashdump(&ehdr);
+ }
+
+ /* load the kernel */
+--
+1.9.1
+
diff --git a/meta/recipes-kernel/kexec/kexec-tools/0007-arm64-kdump-set-up-other-segments.patch b/meta/recipes-kernel/kexec/kexec-tools/0007-arm64-kdump-set-up-other-segments.patch
new file mode 100644
index 0000000..2745466
--- /dev/null
+++ b/meta/recipes-kernel/kexec/kexec-tools/0007-arm64-kdump-set-up-other-segments.patch
@@ -0,0 +1,35 @@
+From 07ad14e12665221d754fde8e47c32ac18c24586a Mon Sep 17 00:00:00 2001
+From: AKASHI Takahiro <takahiro.akashi@linaro.org>
+Date: Fri, 31 Jul 2015 20:01:39 +0900
+Subject: [PATCH 7/9] arm64: kdump: set up other segments
+
+We make sure that all the other segments, initrd and device-tree blob,
+also be loaded into the reserved memory of crash dump kernel.
+
+Upstream-Status: Backport [https://git.linaro.org/people/takahiro.akashi/kexec-tools.git]
+
+Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
+Signed-off-by: He Zhe <zhe.he@windriver.com>
+---
+ kexec/arch/arm64/kexec-arm64.c | 5 ++++-
+ 1 file changed, 4 insertions(+), 1 deletion(-)
+
+diff --git a/kexec/arch/arm64/kexec-arm64.c b/kexec/arch/arm64/kexec-arm64.c
+index cec4e41..78a0035 100644
+--- a/kexec/arch/arm64/kexec-arm64.c
++++ b/kexec/arch/arm64/kexec-arm64.c
+@@ -374,7 +374,10 @@ int arm64_load_other_segments(struct kexec_info *info,
+ /* Put the other segments after the image. */
+
+ hole_min = image_base + arm64_mem.image_size;
+- hole_max = ULONG_MAX;
++ if (info->kexec_flags & KEXEC_ON_CRASH)
++ hole_max = crash_reserved_mem.end;
++ else
++ hole_max = ULONG_MAX;
+
+ if (arm64_opts.initrd) {
+ initrd_buf = slurp_file(arm64_opts.initrd, &initrd_size);
+--
+1.9.1
+
diff --git a/meta/recipes-kernel/kexec/kexec-tools/0008-arm64-kdump-add-DT-properties-to-crash-dump-kernel-s.patch b/meta/recipes-kernel/kexec/kexec-tools/0008-arm64-kdump-add-DT-properties-to-crash-dump-kernel-s.patch
new file mode 100644
index 0000000..31c3d85
--- /dev/null
+++ b/meta/recipes-kernel/kexec/kexec-tools/0008-arm64-kdump-add-DT-properties-to-crash-dump-kernel-s.patch
@@ -0,0 +1,150 @@
+From 23bf7ac189cc3b87ceb9d1d3b69b5c4815354add Mon Sep 17 00:00:00 2001
+From: AKASHI Takahiro <takahiro.akashi@linaro.org>
+Date: Wed, 27 Jan 2016 13:38:39 +0900
+Subject: [PATCH 8/9] arm64: kdump: add DT properties to crash dump kernel's
+ dtb
+
+We pass the following properties to crash dump kernel:
+linux,elfcorehdr: elf core header segment,
+ same as "elfcorehdr=" kernel parameter on other archs
+linux,usable-memory-range: usable memory reserved for crash dump kernel
+
+Upstream-Status: Backport [https://git.linaro.org/people/takahiro.akashi/kexec-tools.git]
+
+Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
+Signed-off-by: He Zhe <zhe.he@windriver.com>
+---
+ kexec/arch/arm64/kexec-arm64.c | 76 +++++++++++++++++++++++++++++++++++---
+ kexec/arch/arm64/kexec-elf-arm64.c | 5 ---
+ 2 files changed, 71 insertions(+), 10 deletions(-)
+
+diff --git a/kexec/arch/arm64/kexec-arm64.c b/kexec/arch/arm64/kexec-arm64.c
+index 78a0035..a8fb64f 100644
+--- a/kexec/arch/arm64/kexec-arm64.c
++++ b/kexec/arch/arm64/kexec-arm64.c
+@@ -128,9 +128,6 @@ int arch_process_options(int argc, char **argv)
+ case OPT_INITRD:
+ arm64_opts.initrd = optarg;
+ break;
+- case OPT_PANIC:
+- die("load-panic (-p) not supported");
+- break;
+ default:
+ break; /* Ignore core and unknown options. */
+ }
+@@ -285,8 +282,12 @@ on_success:
+ * setup_2nd_dtb - Setup the 2nd stage kernel's dtb.
+ */
+
+-static int setup_2nd_dtb(struct dtb *dtb, char *command_line)
++static int setup_2nd_dtb(struct dtb *dtb, char *command_line, int on_crash)
+ {
++ char *new_buf;
++ int new_size;
++ int nodeoffset;
++ uint64_t range[2];
+ int result;
+
+ result = fdt_check_header(dtb->buf);
+@@ -298,8 +299,72 @@ static int setup_2nd_dtb(struct dtb *dtb, char *command_line)
+
+ result = set_bootargs(dtb, command_line);
+
++ /* remove those anyway */
++ nodeoffset = fdt_path_offset(dtb->buf, "/chosen");
++ fdt_delprop(dtb->buf, nodeoffset, "linux,crashkernel-base");
++ fdt_delprop(dtb->buf, nodeoffset, "linux,crashkernel-size");
++
++ if (on_crash) {
++ nodeoffset = fdt_path_offset(dtb->buf, "/chosen");
++ fdt_delprop(dtb->buf, nodeoffset, "linux,elfcorehdr");
++ fdt_delprop(dtb->buf, nodeoffset, "linux,usable-memory-range");
++ new_size = fdt_totalsize(dtb->buf)
++ + 2 * (sizeof(struct fdt_property)
++ + FDT_TAGALIGN(sizeof(range)))
++ + strlen("linux,elfcorehdr") + 1
++ + strlen("linux,usable-memory-range") + 1;
++
++ new_buf = xmalloc(new_size);
++ result = fdt_open_into(dtb->buf, new_buf, new_size);
++ if (result) {
++ dbgprintf("%s: fdt_open_into failed: %s\n", __func__,
++ fdt_strerror(result));
++ result = -ENOSPC;
++ goto on_error;
++ }
++
++ range[0] = cpu_to_be64(elfcorehdr_mem.start);
++ range[1] = cpu_to_be64(elfcorehdr_mem.end
++ - elfcorehdr_mem.start + 1);
++ nodeoffset = fdt_path_offset(new_buf, "/chosen");
++ result = fdt_setprop(new_buf, nodeoffset, "linux,elfcorehdr",
++ (void *)range, sizeof(range));
++ if (result) {
++ dbgprintf("%s: fdt_setprop failed: %s\n", __func__,
++ fdt_strerror(result));
++ result = -EINVAL;
++ goto on_error;
++ }
++
++ range[0] = cpu_to_be64(crash_reserved_mem.start);
++ range[1] = cpu_to_be64(crash_reserved_mem.end
++ - crash_reserved_mem.start + 1);
++ nodeoffset = fdt_path_offset(new_buf, "/chosen");
++ result = fdt_setprop(new_buf, nodeoffset,
++ "linux,usable-memory-range",
++ (void *)range, sizeof(range));
++ if (result) {
++ dbgprintf("%s: fdt_setprop failed: %s\n", __func__,
++ fdt_strerror(result));
++ result = -EINVAL;
++ goto on_error;
++ }
++
++ fdt_pack(new_buf);
++ dtb->buf = new_buf;
++ dtb->size = fdt_totalsize(new_buf);
++ }
++
+ dump_reservemap(dtb);
+
++
++ return result;
++
++on_error:
++ fprintf(stderr, "kexec: %s failed.\n", __func__);
++ if (new_buf)
++ free(new_buf);
++
+ return result;
+ }
+
+@@ -366,7 +431,8 @@ int arm64_load_other_segments(struct kexec_info *info,
+ }
+ }
+
+- result = setup_2nd_dtb(&dtb, command_line);
++ result = setup_2nd_dtb(&dtb, command_line,
++ info->kexec_flags & KEXEC_ON_CRASH);
+
+ if (result)
+ return -EFAILED;
+diff --git a/kexec/arch/arm64/kexec-elf-arm64.c b/kexec/arch/arm64/kexec-elf-arm64.c
+index 842ce21..b17a31a 100644
+--- a/kexec/arch/arm64/kexec-elf-arm64.c
++++ b/kexec/arch/arm64/kexec-elf-arm64.c
+@@ -47,11 +47,6 @@ int elf_arm64_load(int argc, char **argv, const char *kernel_buf,
+ int result;
+ int i;
+
+- if (info->kexec_flags & KEXEC_ON_CRASH) {
+- fprintf(stderr, "kexec: kdump not yet supported on arm64\n");
+- return -EFAILED;
+- }
+-
+ result = build_elf_exec_info(kernel_buf, kernel_size, &ehdr, 0);
+
+ if (result < 0) {
+--
+1.9.1
+
diff --git a/meta/recipes-kernel/kexec/kexec-tools/0009-arm64-kdump-Add-support-for-binary-image-files.patch b/meta/recipes-kernel/kexec/kexec-tools/0009-arm64-kdump-Add-support-for-binary-image-files.patch
new file mode 100644
index 0000000..8b1c018
--- /dev/null
+++ b/meta/recipes-kernel/kexec/kexec-tools/0009-arm64-kdump-Add-support-for-binary-image-files.patch
@@ -0,0 +1,52 @@
+From 5a4958f01a793c3e7f440f5bae75666a4349cc50 Mon Sep 17 00:00:00 2001
+From: Pratyush Anand <panand@redhat.com>
+Date: Thu, 14 May 2015 11:25:37 +0530
+Subject: [PATCH 9/9] arm64: kdump: Add support for binary image files
+
+This patch adds support to use binary image ie arch/arm64/boot/Image with
+kdump.
+
+Upstream-Status: Backport [https://git.linaro.org/people/takahiro.akashi/kexec-tools.git]
+
+Signed-off-by: Pratyush Anand <panand@redhat.com>
+[takahiro.akashi@linaro.org: a bit reworked]
+Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
+Signed-off-by: He Zhe <zhe.he@windriver.com>
+---
+ kexec/arch/arm64/kexec-image-arm64.c | 12 ++++++++++++
+ 1 file changed, 12 insertions(+)
+
+diff --git a/kexec/arch/arm64/kexec-image-arm64.c b/kexec/arch/arm64/kexec-image-arm64.c
+index 960ed96..982e431 100644
+--- a/kexec/arch/arm64/kexec-image-arm64.c
++++ b/kexec/arch/arm64/kexec-image-arm64.c
+@@ -4,7 +4,9 @@
+
+ #define _GNU_SOURCE
+
++#include "crashdump-arm64.h"
+ #include "kexec-arm64.h"
++#include "kexec-syscall.h"
+ #include <limits.h>
+
+ int image_arm64_probe(const char *kernel_buf, off_t kernel_size)
+@@ -58,6 +60,16 @@ int image_arm64_load(int argc, char **argv, const char *kernel_buf,
+ dbgprintf("%s: PE format: %s\n", __func__,
+ (arm64_header_check_pe_sig(header) ? "yes" : "no"));
+
++ if (info->kexec_flags & KEXEC_ON_CRASH) {
++ /* create and initialize elf core header segment */
++ result = load_crashdump_segments(info);
++ if (result) {
++ dbgprintf("%s: Creating eflcorehdr failed.\n",
++ __func__);
++ goto exit;
++ }
++ }
++
+ /* load the kernel */
+ add_segment_phys_virt(info, kernel_buf, kernel_size,
+ kernel_segment + arm64_mem.text_offset,
+--
+1.9.1
+
diff --git a/meta/recipes-kernel/kexec/kexec-tools_2.0.12.bb b/meta/recipes-kernel/kexec/kexec-tools_2.0.12.bb
deleted file mode 100644
index 59376c8..0000000
--- a/meta/recipes-kernel/kexec/kexec-tools_2.0.12.bb
+++ /dev/null
@@ -1,37 +0,0 @@
-require kexec-tools.inc
-export LDFLAGS = "-L${STAGING_LIBDIR}"
-EXTRA_OECONF = " --with-zlib=yes"
-
-SRC_URI += " \
- file://kexec-aarch64.patch \
- file://kexec-x32.patch \
- file://0002-powerpc-change-the-memory-size-limit.patch \
- file://0001-purgatory-Pass-r-directly-to-linker.patch \
- file://0001-vmcore-dmesg-Define-_GNU_SOURCE.patch \
- "
-
-SRC_URI[md5sum] = "10ddaae0e86af54407b164a1f5a39cc3"
-SRC_URI[sha256sum] = "cc7b60dad0da202004048a6179d8a53606943062dd627a2edba45a8ea3a85135"
-
-PACKAGES =+ "kexec kdump vmcore-dmesg"
-
-ALLOW_EMPTY_${PN} = "1"
-RRECOMMENDS_${PN} = "kexec kdump vmcore-dmesg"
-
-FILES_kexec = "${sbindir}/kexec"
-FILES_kdump = "${sbindir}/kdump ${sysconfdir}/init.d/kdump \
- ${sysconfdir}/sysconfig/kdump.conf"
-FILES_vmcore-dmesg = "${sbindir}/vmcore-dmesg"
-
-inherit update-rc.d
-
-INITSCRIPT_PACKAGES = "kdump"
-INITSCRIPT_NAME_kdump = "kdump"
-INITSCRIPT_PARAMS_kdump = "start 56 2 3 4 5 . stop 56 0 1 6 ."
-
-do_install_append () {
- install -d ${D}${sysconfdir}/init.d
- install -m 0755 ${WORKDIR}/kdump ${D}${sysconfdir}/init.d/kdump
- install -d ${D}${sysconfdir}/sysconfig
- install -m 0644 ${WORKDIR}/kdump.conf ${D}${sysconfdir}/sysconfig
-}
diff --git a/meta/recipes-kernel/kexec/kexec-tools_2.0.14.bb b/meta/recipes-kernel/kexec/kexec-tools_2.0.14.bb
new file mode 100644
index 0000000..de5ce44
--- /dev/null
+++ b/meta/recipes-kernel/kexec/kexec-tools_2.0.14.bb
@@ -0,0 +1,44 @@
+require kexec-tools.inc
+export LDFLAGS = "-L${STAGING_LIBDIR}"
+EXTRA_OECONF = " --with-zlib=yes"
+
+SRC_URI += " \
+ file://0002-powerpc-change-the-memory-size-limit.patch \
+ file://0001-purgatory-Pass-r-directly-to-linker.patch \
+ file://0001-vmcore-dmesg-Define-_GNU_SOURCE.patch \
+ file://0001-kexec-exntend-the-semantics-of-kexec_iomem_for_each_.patch \
+ file://0002-kexec-generalize-and-rename-get_kernel_stext_sym.patch \
+ file://0003-arm64-identify-PHYS_OFFSET-correctly.patch \
+ file://0004-arm64-kdump-identify-memory-regions.patch \
+ file://0005-arm64-kdump-add-elf-core-header-segment.patch \
+ file://0006-arm64-kdump-set-up-kernel-image-segment.patch \
+ file://0007-arm64-kdump-set-up-other-segments.patch \
+ file://0008-arm64-kdump-add-DT-properties-to-crash-dump-kernel-s.patch \
+ file://0009-arm64-kdump-Add-support-for-binary-image-files.patch \
+ "
+
+SRC_URI[md5sum] = "b2b2c5e6b29d467d6e99d587fb6b7cf5"
+SRC_URI[sha256sum] = "b3e69519d2acced256843b1e8f1ecfa00d9b54fa07449ed78f05b9193f239370"
+
+PACKAGES =+ "kexec kdump vmcore-dmesg"
+
+ALLOW_EMPTY_${PN} = "1"
+RRECOMMENDS_${PN} = "kexec kdump vmcore-dmesg"
+
+FILES_kexec = "${sbindir}/kexec"
+FILES_kdump = "${sbindir}/kdump ${sysconfdir}/init.d/kdump \
+ ${sysconfdir}/sysconfig/kdump.conf"
+FILES_vmcore-dmesg = "${sbindir}/vmcore-dmesg"
+
+inherit update-rc.d
+
+INITSCRIPT_PACKAGES = "kdump"
+INITSCRIPT_NAME_kdump = "kdump"
+INITSCRIPT_PARAMS_kdump = "start 56 2 3 4 5 . stop 56 0 1 6 ."
+
+do_install_append () {
+ install -d ${D}${sysconfdir}/init.d
+ install -m 0755 ${WORKDIR}/kdump ${D}${sysconfdir}/init.d/kdump
+ install -d ${D}${sysconfdir}/sysconfig
+ install -m 0644 ${WORKDIR}/kdump.conf ${D}${sysconfdir}/sysconfig
+}
--
2.8.3
^ permalink raw reply related
* Re: Yocto-2.2 build failures on Ubuntu 14.04.5 & 16.04.x hosts due to crash of unity-settings-daemon followed by restart of lightdm
From: srikanth krishnakar @ 2016-12-27 9:48 UTC (permalink / raw)
To: Richard Purdie; +Cc: openembedded-core
In-Reply-To: <CALDxG5hjMaUwmRTR9GLoYb7nmvMUKi08ZMNog5jviJrnJ42naw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 12807 bytes --]
Hello Richard,
I was under impression that installing Ubuntu-14.04.4 (+lastest updates)
would give me stable build environment, unfortunately that is not the case
! I could see the logout issue on this installation too. So I believe that
issue should be reproducible on any 14.04.x installation including 16.04.x
with all latest updates installed. The second attempt of build on
"Ubuntu-14.04.4" shows the status of bitbake as halted at libvorbis when
logout happened:
---------------------------------------------------------
NOTE: Running task 2460 of 4212
(/home/poky/meta/recipes-core/ncurses/ncurses_6.0+20160625.bb:
do_packagedata)
NOTE: recipe ncurses-6.0+20160625-r0: task do_packagedata: Started
NOTE: recipe ncurses-6.0+20160625-r0: task do_packagedata: Succeeded
NOTE: Running task 2461 of 4212
(/home/poky/meta/recipes-core/readline/readline_6.3.bb:do_package)
NOTE: recipe libjpeg-turbo-1_1.5.0-r0: task do_package: Succeeded
NOTE: Running task 2462 of 4212
(/home/poky/meta/recipes-graphics/jpeg/libjpeg-turbo_1.5.0.bb:
do_packagedata)
NOTE: recipe libjpeg-turbo-1_1.5.0-r0: task do_packagedata: Started
NOTE: recipe libjpeg-turbo-1_1.5.0-r0: task do_packagedata: Succeeded
NOTE: Running task 2463 of 4212
(/home/poky/meta/recipes-multimedia/libvorbis/libvorbis_1.3.5.bb:do_package)
NOTE: recipe readline-6.3-r0: task do_package: Started
NOTE: recipe libvorbis-1.3.5-r0: task do_package: Started
---------------------------------------------------------
The "$HOME/.xsession-errors.old" file shows the message:
---------------------------------------------------------
Script for ibus started at run_im.
Script for auto started at run_im.
Script for default started at run_im.
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd respawning too fast, stopped
init: indicator-messages main process (17542) killed by SEGV signal
init: indicator-messages main process ended, respawning
init: update-notifier-crash
(/var/crash/_usr_lib_x86_64-linux-gnu_indicator-messages_indicator-messages-service.1000.crash)
main process (18792) terminated with status 1
init: update-notifier-crash
(/var/crash/_usr_share_apport_apport-gtk.1000.crash) main process (21151)
terminated with status 1
init: unity-panel-service-lockscreen main process (29904) killed by KILL
signal
---------------------------------------------------------
It appears that lightdm is unable the handle the SIGNAL and restarting when
it receives them. Some of the most anticipated bugfixes patches for lightdm
yet to arrive in ubuntu-14.04.6 which are not released yet can be found
here:
https://launchpad.net/lightdm/+milestone/1.10.7
Current version of lightdm in ubuntu-14.04.4/5 -> 1.10.6
Thanks,
Srikant
On Mon, Dec 26, 2016 at 6:59 PM, srikanth krishnakar <skrishnakar@gmail.com>
wrote:
> Hello Richard,
>
> bitbake | cat shows that when this logout happened during build, log file
> captured below packages in process:
>
> ------------------------------------------------------------
> --------------------------------
> NOTE: Running task 1886 of 4212 (/home/builder/poky/meta/
> recipes-graphics/xorg-proto/kbproto_1.0.7.bb:do_packagedata)
> NOTE: recipe kbproto-1_1.0.7-r0: task do_packagedata: Started
> NOTE: recipe kbproto-1_1.0.7-r0: task do_packagedata: Succeeded
> NOTE: Running task 1887 of 4212 (/home/builder/poky/meta/
> recipes-support/libffi/libffi_3.2.1.bb:do_package)
> NOTE: recipe ncurses-6.0+20160625-r0: task do_package: Started
> NOTE: recipe libffi-3.2.1-r0: task do_package: Started
> NOTE: recipe libffi-3.2.1-r0: task do_package: Succeeded
> NOTE: Running task 1888 of 4212 (/home/builder/poky/meta/
> recipes-support/libffi/libffi_3.2.1.bb:do_packagedata)
> NOTE: recipe libffi-3.2.1-r0: task do_packagedata: Started
> NOTE: recipe libffi-3.2.1-r0: task do_packagedata: Succeeded
> NOTE: Running task 1889 of 4212 (/home/builder/poky/meta/
> recipes-extended/bzip2/bzip2_1.0.6.bb:do_package)
> NOTE: recipe bzip2-1.0.6-r5: task do_package: Started
> ------------------------------------------------------------
> -----------------------------------
>
> Also there was a crash file generated in "/var/crash" folder:
> /var/crash/_usr_lib_accountsservice_accounts-daemon.0.crash
>
> That has following information in it:
> ------------------------------------------------------------
> -------------------------------------
> ProblemType: Crash
> Architecture: amd64
> Date: Mon Dec 26 18:23:22 2016
> DistroRelease: Ubuntu 14.04
> ExecutablePath: /usr/lib/accountsservice/accounts-daemon
> ExecutableTimestamp: 1478200365
> ProcCmdline: /usr/lib/accountsservice/accounts-daemon
> ProcCwd: /
> ProcEnviron:
> ProcMaps:
> 00400000-00426000 r-xp 00000000 08:01 2626520
> /usr/lib/accountsservice/accounts-daemon
> 00625000-00628000 r--p 00025000 08:01 2626520
> /usr/lib/accountsservice/accounts-daemon
> 00628000-00629000 rw-p 00028000 08:01 2626520
> /usr/lib/accountsservice/accounts-daemon
> 024aa000-0252a000 rw-p 00000000 00:00 0
> [heap]
> 7fe460000000-7fe460022000 rw-p 00000000 00:00 0
> 7fe460022000-7fe464000000 ---p 00000000 00:00 0
> 7fe464000000-7fe464021000 rw-p 00000000 00:00 0
> 7fe464021000-7fe468000000 ---p 00000000 00:00 0
> 7fe469f56000-7fe469f60000 r-xp 00000000 08:01 1839849
> /lib/x86_64-linux-gnu/libnss_files-2.19.so
> 7fe469f60000-7fe46a15f000 ---p 0000a000 08:01 1839849
> /lib/x86_64-linux-gnu/libnss_files-2.19.so
> 7fe46a15f000-7fe46a160000 r--p 00009000 08:01 1839849
> /lib/x86_64-linux-gnu/libnss_files-2.19.so
> ...
> ...
> 7fe474b3e000-7fe474b40000 rw-p 00000000 00:00 0
> 7fe474b40000-7fe474b41000 r--p 00022000 08:01 1839750
> /lib/x86_64-linux-gnu/ld-2.19.so
> 7fe474b41000-7fe474b42000 rw-p 00023000 08:01 1839750
> /lib/x86_64-linux-gnu/ld-2.19.so
> 7fe474b42000-7fe474b43000 rw-p 00000000 00:00 0
> 7ffcaca64000-7ffcaca85000 rw-p 00000000 00:00 0
> [stack]
> 7ffcacaf5000-7ffcacaf7000 r--p 00000000 00:00 0
> [vvar]
> 7ffcacaf7000-7ffcacaf9000 r-xp 00000000 00:00 0
> [vdso]
> ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0
> [vsyscall]
> ProcStatus:
> Name: accounts-daemon
> State: D (disk sleep)
> Tgid: 1248
> Ngid: 0
> Pid: 1248
> PPid: 1
> TracerPid: 0
> Uid: 0 0 0 0
> Gid: 0 0 0 0
> FDSize: 64
> Groups: 0
> NStgid: 1248
> NSpid: 1248
> NSpgid: 795
> NSsid: 795
> VmPeak: 302404 kB
> VmSize: 302368 kB
> VmPin: 0 kB
> VmHWM: 10128 kB
> VmRSS: 4464 kB
> VmData: 221944 kB
> VmStk: 136 kB
> VmExe: 152 kB
> VmLib: 10140 kB
> VmPTE: 200 kB
> VmPMD: 12 kB
> VmSwap: 2976 kB
> HugetlbPages: 0 kB
> Threads: 3
> SigQ: 0/31670
> SigPnd: 0000000000000000
> ShdPnd: 0000000000000000
> SigBlk: 0000000000000000
> SigIgn: 0000000000001000
> SigCgt: 0000000180004002
> CapInh: 0000000000000000
> CapPrm: 0000003fffffffff
> CapEff: 0000003fffffffff
> CapBnd: 0000003fffffffff
> CapAmb: 0000000000000000
> Seccomp: 0
> Cpus_allowed: ff
> Cpus_allowed_list: 0-7
> Mems_allowed: 00000000,00000001
> Mems_allowed_list: 0
> voluntary_ctxt_switches: 152
> nonvoluntary_ctxt_switches: 2
> Signal: 7
> Uname: Linux 4.4.0-57-generic x86_64
> UserGroups:
> CoreDump: base64
> ------------------------------------------------------------
> -------------------------------------
>
> My machine is:
>
> *Quad-Core:* (0-8)
> ---------------------------------------
> $ cat /proc/cpuinfo
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 42
> model name : Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
> -----
> $ cat /proc/meminfo
> MemTotal: 8132472 kB
> ----------------------------------------
>
> When I checked free memory just before the logout was about "125MB" out of
> 8GB RAM.
>
> NOTE: The Ubuntu-14.04.4 that had older graphics stack seem to work
> normally without any issue. The "ubuntu-14.04.5" & "16.04" came with latest
> graphics stack & kernel with removal of non-opensource fglrx drivers.
>
> Thanks for your patience!
>
> --
> Regards,
> Srikant
>
>
> On Mon, Dec 26, 2016 at 4:28 PM, srikanth krishnakar <
> skrishnakar@gmail.com> wrote:
>
>> Hello Richard,
>>
>> Sure, watching is best thing we can do, but it happens somewhere after
>> 2900 tasks i.e just after linux-yocto.
>> Screen recorders usually ask for file name and destination folder for
>> saving the file, will try to see if it works as you said.
>> "bitbake | cat" is the best method that we can get info from.
>>
>> The issue is noticeable only in ubuntu (unity) desktop's and not in
>> Kubuntu (KDE), Ubuntu-gnome (Gnome-3) or Xubuntu (XFCE) desktops.
>>
>> Will fetch more details as per your suggestion.
>>
>> Thank you !
>>
>> On Mon, Dec 26, 2016 at 4:06 PM, Richard Purdie <
>> richard.purdie@linuxfoundation.org> wrote:
>>
>>> On Mon, 2016-12-26 at 15:11 +0530, srikanth krishnakar wrote:
>>> > Environment: Ubuntu-14.04.5/16.04.1 (64-bit)
>>> > Yocto build: qemuarm
>>> > Target image: core-image-sato
>>> > Error nature: The lightdm restarts on its own and logs out by killing
>>> > processes running and brings up a login UI.
>>> >
>>> >
>>> > We have been observing yocto-2.2 build failures on Ubuntu 14.04.5 and
>>> > Ubuntu-16.04.1 hosts due to restart of "lightdm" (Light Desktop
>>> > Manager) that is triggered by crash of "unity-settings-daemon", we
>>> > couldn't figure out any workaround so far to overcome the issue. The
>>> > build goes fine in the beginning but eventually the unity desktop
>>> > logs out and kills all the processes running in the user session
>>> > (including bitbake) and lands us into "Login screen" and when we
>>> > login its a new session where as the bitbake running in previous
>>> > session is killed and we need to continue the build. This is
>>> > happening consistently when the user logs into desktop via lightdm
>>> > and triggers a build.
>>> >
>>> > Another interesting thing to notice is the build goes fine if we
>>> > connect to host via. SSH session and invoke a bitbake build. We are
>>> > suspecting on unity-settings-daemon that is crashing consistently and
>>> > is evident from the ".xsession-errors" log file as shown below:
>>> >
>>> > builder@ubuntu:~$ cat .xsession-errors.old
>>> > Script for ibus started at run_im.
>>> > Script for auto started at run_im.
>>> > Script for default started at run_im.
>>> > init: Disconnected from notified D-Bus bus
>>> > init:"unity-settings-daemon main process (2076) terminated with
>>> > status 1"
>>> > init: indicator-bluetooth main process (2212) killed by TERM signal
>>> > init: indicator-power main process (2214) killed by TERM signal
>>> > init: indicator-datetime main process (2215) killed by TERM signal
>>> > init: indicator-printers main process (2222) killed by TERM signal
>>> > init: indicator-session main process (2245) killed by TERM signal
>>> > init: indicator-application main process (2270) killed by TERM signal
>>> >
>>> > Corresponding unity-settings-daemon bug reported in Launchpad:
>>> >
>>> > https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/
>>> > 1546641
>>> >
>>> > Would anyone kindly confirm the logout behaviour during bitbake
>>> > process on Ubuntu-14.04.5 & Ubuntu-16.04.1 ? Since Yocto 2.2 mentions
>>> > both Ubuntu-14.04 & 16.04 as supported distributions this blocker
>>> > issue must be resolved at earliest.
>>> >
>>> > Appreciate your Inputs !
>>>
>>> What would really help is knowing what recipe is being built when this
>>> happens. There are a few ways you might be able to figure this out:
>>>
>>> a) Watching the screen to see which recipes were building when it
>>> happens
>>> b) Perhaps using some kind of screen recorder to automate this, you'd
>>> be able to review the recording to see when it breaks
>>> c) Looking at the bitbake/build logs to see what it was doing when the
>>> build broke (assuming bitbake stops when the session dies).
>>>
>>> "bitbake | cat" can provide better output for this since it will
>>> produce a scrolling log rather than the more interactive UI.
>>>
>>> Once you find the problematic recipe, a "bitbake XXX -c clean; bitbake
>>> XXX" should hopefully reproduce this more easily.
>>>
>>> Cheers,
>>>
>>> Richard
>>>
>>
>>
>
[-- Attachment #2: Type: text/html, Size: 17689 bytes --]
^ permalink raw reply
* Re: [PATCH v2 1/2] grub_git: extend recipe for proper target deployment
From: Belal, Awais @ 2016-12-27 12:15 UTC (permalink / raw)
To: openembedded-core@lists.openembedded.org
In-Reply-To: <1481890756-18807-1-git-send-email-awais_belal@mentor.com>
ping!
BR,
Awais
________________________________________
From: openembedded-core-bounces@lists.openembedded.org <openembedded-core-bounces@lists.openembedded.org> on behalf of Belal, Awais
Sent: Friday, December 16, 2016 5:19 PM
To: openembedded-core@lists.openembedded.org
Subject: [OE-core] [PATCH v2 1/2] grub_git: extend recipe for proper target deployment
This extends the grub_git recipe so it can deploy grub
on the target boot disk just like grub-efi. Mainly
this copies stuff from the grub-efi recipe and then
adjusts some bits accordingly. This would allow
using the latest and greatest versions of grub
on the target.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
---
meta/recipes-bsp/grub/grub_git.bb | 60 +++++++++++++++++++++++++++++++++++----
1 file changed, 54 insertions(+), 6 deletions(-)
diff --git a/meta/recipes-bsp/grub/grub_git.bb b/meta/recipes-bsp/grub/grub_git.bb
index eb824cc..13c48c7 100644
--- a/meta/recipes-bsp/grub/grub_git.bb
+++ b/meta/recipes-bsp/grub/grub_git.bb
@@ -3,11 +3,15 @@ require grub2.inc
DEFAULT_PREFERENCE = "-1"
DEFAULT_PREFERENCE_arm = "1"
+DEPENDS += "grub-native"
+RDEPENDS_${PN}_class-target = "diffutils freetype"
+
FILESEXTRAPATHS =. "${FILE_DIRNAME}/grub-git:"
PV = "2.00+${SRCPV}"
SRCREV = "7a5b301e3adb8e054288518a325135a1883c1c6c"
SRC_URI = "git://git.savannah.gnu.org/grub.git \
+ file://cfg \
file://0001-Disable-mfpmath-sse-as-well-when-SSE-is-disabled.patch \
file://autogen.sh-exclude-pc.patch \
file://0001-grub.d-10_linux.in-add-oe-s-kernel-name.patch \
@@ -19,29 +23,73 @@ COMPATIBLE_HOST = '(x86_64.*|i.86.*|arm.*|aarch64.*)-(linux.*|freebsd.*)'
COMPATIBLE_HOST_armv7a = 'null'
COMPATIBLE_HOST_armv7ve = 'null'
-inherit autotools gettext texinfo
+inherit autotools gettext texinfo deploy
# configure.ac has code to set this automagically from the target tuple
# but the OE freeform one (core2-foo-bar-linux) don't work with that.
-
GRUBPLATFORM_arm = "uboot"
GRUBPLATFORM_aarch64 = "efi"
GRUBPLATFORM ??= "pc"
+CACHED_CONFIGUREVARS += "ac_cv_path_HELP2MAN="
EXTRA_OECONF = "--with-platform=${GRUBPLATFORM} --disable-grub-mkfont --program-prefix="" \
--enable-liblzma=no --enable-device-mapper=no --enable-libzfs=no"
-
+EXTRA_OECONF += "${@bb.utils.contains('GRUBPLATFORM', 'efi', '--enable-efiemu=no', '', d)}"
EXTRA_OECONF += "${@bb.utils.contains('DISTRO_FEATURES', 'largefile', '--enable-largefile', '--disable-largefile', d)}"
-do_install_append () {
+# Determine the target arch for the grub modules
+python __anonymous () {
+ import re
+ target = d.getVar('TARGET_ARCH', True)
+ platform = d.getVar('GRUBPLATFORM', True)
+ if target == "x86_64":
+ grubtarget = 'x86_64'
+ grubimage = "bootx64." + platform
+ elif re.match('i.86', target):
+ grubtarget = 'i386'
+ grubimage = "bootia32." + platform
+ elif re.match('arm', target):
+ grubtarget = 'arm'
+ grubimage = "bootarm." + platform
+ elif re.match('aarch64', target):
+ grubtarget = 'arm64'
+ grubimage = "bootaa64." + platform
+ else:
+ raise bb.parse.SkipPackage("grub is incompatible with target %s" % target)
+ d.setVar("GRUB_TARGET", grubtarget)
+ d.setVar("GRUB_IMAGE", grubimage)
+}
+
+do_install_class-native() {
+ install -d ${D}${bindir}
+ install -m 755 grub-mkimage ${D}${bindir}
+}
+
+do_install_append() {
install -d ${D}${sysconfdir}/grub.d
rm -rf ${D}${libdir}/charset.alias
}
+GRUB_BUILDIN ?= "boot linux ext2 fat serial part_msdos part_gpt normal efi_gop iso9660 search"
+do_deploy() {
+ # Search for the grub.cfg on the local boot media by using the
+ # built in cfg file provided via this recipe
+ grub-mkimage -c ../cfg -p /EFI/BOOT -d ./grub-core/ \
+ -O ${GRUB_TARGET}-${GRUBPLATFORM} -o ./${GRUB_IMAGE} \
+ ${GRUB_BUILDIN}
+ install -m 644 ${B}/${GRUB_IMAGE} ${DEPLOYDIR}
+}
+
+do_deploy_class-native() {
+ :
+}
+
+addtask deploy after do_install before do_build
+
# debugedit chokes on bare metal binaries
INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
-RDEPENDS_${PN} = "diffutils freetype"
-
INSANE_SKIP_${PN} = "arch"
INSANE_SKIP_${PN}-dbg = "arch"
+
+BBCLASSEXTEND = "native"
--
1.9.1
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
^ permalink raw reply related
* Re: [PATCH v2 2/2] grub-efi/live-vm-common: allow grub as EFI_PROVIDER
From: Belal, Awais @ 2016-12-27 12:15 UTC (permalink / raw)
To: openembedded-core@lists.openembedded.org
In-Reply-To: <1481890756-18807-2-git-send-email-awais_belal@mentor.com>
Ping!
BR,
Awais
________________________________________
From: openembedded-core-bounces@lists.openembedded.org <openembedded-core-bounces@lists.openembedded.org> on behalf of Belal, Awais
Sent: Friday, December 16, 2016 5:19 PM
To: openembedded-core@lists.openembedded.org
Subject: [OE-core] [PATCH v2 2/2] grub-efi/live-vm-common: allow grub as EFI_PROVIDER
This allows grub to be used as EFI_PROVIDER and
extends the grub-efi class so it can be used as is
when EFI_PROVIDER is grub.
Currently this can only be leveraged if you are
using the grub_git recipe and GRUBPLATFORM plus
EFI_PROVIDER are set correctly.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
---
meta/classes/grub-efi.bbclass | 23 +++++++++++++++++------
meta/classes/live-vm-common.bbclass | 2 +-
2 files changed, 18 insertions(+), 7 deletions(-)
diff --git a/meta/classes/grub-efi.bbclass b/meta/classes/grub-efi.bbclass
index 17417ba..c847645 100644
--- a/meta/classes/grub-efi.bbclass
+++ b/meta/classes/grub-efi.bbclass
@@ -16,8 +16,8 @@
# ${GRUB_TIMEOUT} - timeout before executing the deault label (optional)
# ${GRUB_ROOT} - grub's root device.
-do_bootimg[depends] += "${MLPREFIX}grub-efi:do_deploy"
-do_bootdirectdisk[depends] += "${MLPREFIX}grub-efi:do_deploy"
+do_bootimg[depends] += "${MLPREFIX}${EFI_PROVIDER}:do_deploy"
+do_bootdirectdisk[depends] += "${MLPREFIX}${EFI_PROVIDER}:do_deploy"
GRUB_SERIAL ?= "console=ttyS0,115200"
GRUB_CFG_VM = "${S}/grub_vm.cfg"
@@ -40,10 +40,21 @@ efi_populate() {
install -d ${DEST}${EFIDIR}
- GRUB_IMAGE="bootia32.efi"
- if [ "${TARGET_ARCH}" = "x86_64" ]; then
- GRUB_IMAGE="bootx64.efi"
- fi
+ if [ "${EFI_PROVIDER}" = "grub" ]; then
+ GRUB_IMAGE="bootia32.${GRUBPLATFORM}"
+ if [ "${TARGET_ARCH}" = "x86_64" ]; then
+ GRUB_IMAGE="bootx64.${GRUBPLATFORM}"
+ elif [ "${TARGET_ARCH}" = "arm" ]; then
+ grubimage = "bootarm.${GRUBPLATFORM}"
+ elif [ "${TARGET_ARCH}" = "aarch64" ]; then
+ grubimage = "bootaa64.${GRUBPLATFORM}"
+ fi
+ else
+ GRUB_IMAGE="bootia32.efi"
+ if [ "${TARGET_ARCH}" = "x86_64" ]; then
+ GRUB_IMAGE="bootx64.efi"
+ fi
+ fi
install -m 0644 ${DEPLOY_DIR_IMAGE}/${GRUB_IMAGE} ${DEST}${EFIDIR}
EFIPATH=$(echo "${EFIDIR}" | sed 's/\//\\/g')
printf 'fs0:%s\%s\n' "$EFIPATH" "$GRUB_IMAGE" >${DEST}/startup.nsh
diff --git a/meta/classes/live-vm-common.bbclass b/meta/classes/live-vm-common.bbclass
index 734697f..0af228b 100644
--- a/meta/classes/live-vm-common.bbclass
+++ b/meta/classes/live-vm-common.bbclass
@@ -13,7 +13,7 @@ def set_live_vm_vars(d, suffix):
EFI = "${@bb.utils.contains("MACHINE_FEATURES", "efi", "1", "0", d)}"
EFI_PROVIDER ?= "grub-efi"
-EFI_CLASS = "${@bb.utils.contains("MACHINE_FEATURES", "efi", "${EFI_PROVIDER}", "", d)}"
+EFI_CLASS = "${@bb.utils.contains("EFI_PROVIDER", "grub", "grub-efi", "${EFI_PROVIDER}", d)}"
# Include legacy boot if MACHINE_FEATURES includes "pcbios" or if it does not
# contain "efi". This way legacy is supported by default if neither is
--
1.9.1
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
^ permalink raw reply related
* Re: [PATCH] ncurses: 6.0+20160625 -> 6.0+20161126
From: Maxin B. John @ 2016-12-27 14:33 UTC (permalink / raw)
To: Huang Qiyu; +Cc: openembedded-core
In-Reply-To: <1482382494-2614-1-git-send-email-huangqy.fnst@cn.fujitsu.com>
Hi,
On Thu, Dec 22, 2016 at 12:54:54PM +0800, Huang Qiyu wrote:
> Upgrade ncurses from 6.0+20160625 to 6.0+20161126.
This causes build failures for beaglebone and qemumips64 targets:
http://errors.yoctoproject.org/Errors/Details/115740/
http://errors.yoctoproject.org/Errors/Details/115738/
Please look into that.
> Signed-off-by: Huang Qiyu <huangqy.fnst@cn.fujitsu.com>
> ---
> .../ncurses/{ncurses_6.0+20160625.bb => ncurses_6.0+20161126.bb} | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> rename meta/recipes-core/ncurses/{ncurses_6.0+20160625.bb => ncurses_6.0+20161126.bb} (84%)
>
> diff --git a/meta/recipes-core/ncurses/ncurses_6.0+20160625.bb b/meta/recipes-core/ncurses/ncurses_6.0+20161126.bb
> similarity index 84%
> rename from meta/recipes-core/ncurses/ncurses_6.0+20160625.bb
> rename to meta/recipes-core/ncurses/ncurses_6.0+20161126.bb
> index 6514613..7328e78 100644
> --- a/meta/recipes-core/ncurses/ncurses_6.0+20160625.bb
> +++ b/meta/recipes-core/ncurses/ncurses_6.0+20161126.bb
> @@ -4,7 +4,7 @@ SRC_URI += "file://tic-hang.patch \
> file://config.cache \
> "
> # commit id corresponds to the revision in package version
> -SRCREV = "63dd558cb8e888d6fab5f00bbf7842736a2356b9"
> +SRCREV = "3db0bd19cb50e3d9b4f2cf15b7a102fe11302068"
> S = "${WORKDIR}/git"
> EXTRA_OECONF += "--with-abi-version=5"
> UPSTREAM_CHECK_GITTAGREGEX = "(?P<pver>\d+(\.\d+)+(\+\d+)*)"
> --
Best Regards,
Maxin
^ permalink raw reply
* Re: Yocto-2.2 build failures on Ubuntu 14.04.5 & 16.04.x hosts due to crash of unity-settings-daemon followed by restart of lightdm
From: Richard Purdie @ 2016-12-27 16:49 UTC (permalink / raw)
To: srikanth krishnakar; +Cc: openembedded-core
In-Reply-To: <CALDxG5ihGZU3f4ipau1nm19_p-C+XRTGxq71OvapTC6J4-8yMQ@mail.gmail.com>
On Tue, 2016-12-27 at 15:18 +0530, srikanth krishnakar wrote:
> Hello Richard,
>
> I was under impression that installing Ubuntu-14.04.4 (+lastest
> updates) would give me stable build environment, unfortunately that
> is not the case ! I could see the logout issue on this installation
> too. So I believe that issue should be reproducible on any 14.04.x
> installation including 16.04.x with all latest updates installed. The
> second attempt of build on "Ubuntu-14.04.4" shows the status of
> bitbake as halted at libvorbis when logout happened:
>
> ---------------------------------------------------------
> NOTE: Running task 2460 of 4212 (/home/poky/meta/recipes-
> core/ncurses/ncurses_6.0+20160625.bb:do_packagedata)
> NOTE: recipe ncurses-6.0+20160625-r0: task do_packagedata: Started
> NOTE: recipe ncurses-6.0+20160625-r0: task do_packagedata: Succeeded
> NOTE: Running task 2461 of 4212 (/home/poky/meta/recipes-
> core/readline/readline_6.3.bb:do_package)
> NOTE: recipe libjpeg-turbo-1_1.5.0-r0: task do_package: Succeeded
> NOTE: Running task 2462 of 4212 (/home/poky/meta/recipes-
> graphics/jpeg/libjpeg-turbo_1.5.0.bb:do_packagedata)
> NOTE: recipe libjpeg-turbo-1_1.5.0-r0: task do_packagedata: Started
> NOTE: recipe libjpeg-turbo-1_1.5.0-r0: task do_packagedata: Succeeded
> NOTE: Running task 2463 of 4212 (/home/poky/meta/recipes-
> multimedia/libvorbis/libvorbis_1.3.5.bb:do_package)
> NOTE: recipe readline-6.3-r0: task do_package: Started
> NOTE: recipe libvorbis-1.3.5-r0: task do_package: Started
None of these look particularly suspicios for causing your X session to
die.
Some further questions:
a) Is anything showing in the dmesg logs? Is the OOM killer the thing
which is killing processes?
b) How are you measuring free memory? You mentioned it was low, it
would depend on the disk cache size and swap status too.
c) Have you tried a lower BB_NUMBER_THREADS and lower PARALLEL_MAKE
values to rule out resource problems and perhaps identify more
specifically which task is causing your problem?
As I mentioned previously, this problem should reduce to a specific
recipe+task causing the problem, unless its a general resource issue in
which case the threads/parallel make will stop the problem occurring.
We have autobuilders running various versions of Ubuntu and we don't
notice problems with processes dying, admittedly we don't run X
desktops on them in general though.
Cheers,
Richard
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox