Re: [OE-core] [PATCH 0/2] [master][dizzy] Enable Marvel 8897 Wifi feature

[Ng, Wei Tee]

Hi,

I've sent 2 patches regarding to enable Marvel 8897 Wifi feature 2 weeks ago 
and would like to follow up the status.
I am wondering is there any issue on the patches that I submitted because I 
don't receive any response from anyone.
These 2 patches are targeting to merge in Master branch and port it over to 
Dizzy branch as well. 
Any helps will be appreciated. Thanks.

Regards,
Wei Tee

> -Original Message-
> From: Ng, Wei Tee
> Sent: Thursday, July 9, 2015 1:10 PM
> To: openembedded-core@lists.openembedded.org
> Cc: Ng, Wei Tee
> Subject: [PATCH 0/2] [OE-core][master][dizzy] Enable Marvel 8897 Wifi feature
> 
> From: Ng Wei Tee 
> 
> Hi all,
> 
> I would like to add hostapd and iw configuration for enabling Marvell 8897 
> Wifi
> feature. Hostapd and iw configuration were created in the recipes-connectivity
> layer to enable Marvell 8897 module function in AP mode and STA mode.
> 
> Please review and provide feedback if any.
> 
> This patch is target to merge in openembedded-core master and dizzy branch.
> Thanks.
> 
> Regards,
> Wei Tee
> 
> Ng Shui Lei (2):
>   recipes-connectivity: Add hostapd configuration for enabling Marvell
> 8897 WiFi feature
>   recipes-connectivity: Add iw configuration for enabling Marvell 8897
> WiFi feature
> 
>  .../hostapd/hostapd-2.2/defconfig  |  145 
> 
>  .../hostapd/hostapd-2.2/hostapd.service|   11 ++
>  meta/recipes-connectivity/hostapd/hostapd-2.2/init |   58 
>  meta/recipes-connectivity/hostapd/hostapd_2.2.bb   |   48 +++
>  sh-don-t-use-git-describe-for-versioning.patch |   40 ++
>  meta/recipes-connectivity/iw/iw_3.8.bb |   27 
>  6 files changed, 329 insertions(+)
>  create mode 100644 meta/recipes-connectivity/hostapd/hostapd-
> 2.2/defconfig
>  create mode 100644 meta/recipes-connectivity/hostapd/hostapd-
> 2.2/hostapd.service
>  create mode 100644 meta/recipes-connectivity/hostapd/hostapd-2.2/init
>  create mode 100644 meta/recipes-connectivity/hostapd/hostapd_2.2.bb
>  create mode 100644 meta/recipes-connectivity/iw/iw-3.8/0001-iw-version.sh-
> don-t-use-git-describe-for-versioning.patch
>  create mode 100644 meta/recipes-connectivity/iw/iw_3.8.bb
> 
> --
> 1.7.9.5

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

[OE-core] [poky][PATCH v2 1/2] gstreamer1.0: Add inputselector related patch

[Yuqing Zhu]

Fix: ticky events haven't send out when active track reach EOS

EOS event hasn't been send to down-element. The resolution is block EOS event
of inactive pad, send the event after the pad actived.

Signed-off-by: Yuqing Zhu 
---
 ...cky-events-haven-t-send-out-when-ac-1-4-1.patch | 167 +
 .../gstreamer/gstreamer1.0_1.4.5.bb|   1 +
 2 files changed, 168 insertions(+)
 create mode 100755 
meta/recipes-multimedia/gstreamer/gstreamer1.0/inputselector-sticky-events-haven-t-send-out-when-ac-1-4-1.patch

diff --git 
a/meta/recipes-multimedia/gstreamer/gstreamer1.0/inputselector-sticky-events-haven-t-send-out-when-ac-1-4-1.patch
 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0/inputselector-sticky-events-haven-t-send-out-when-ac-1-4-1.patch
new file mode 100755
index 000..30d8a10
--- /dev/null
+++ 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0/inputselector-sticky-events-haven-t-send-out-when-ac-1-4-1.patch
@@ -0,0 +1,167 @@
+From 83bed90c306ed3185d48febf6441177d638f7341 Mon Sep 17 00:00:00 2001
+From: Song Bing 
+Date: Wed, 24 Dec 2014 10:13:51 +0800
+Subject: [PATCH] inputselector: sticky events haven't send out when active
+ track reach EOS
+
+EOS event hasn't been send to down-element. The resolution is block EOS event
+of inactive pad, send the event after the pad actived.
+
+https://bugzilla.gnome.org/show_bug.cgi?id=740949
+
+Upstream Status: Backport-GStreamer 1.5.1
+
+Signed-off-by: Song Bing 
+---
+ plugins/elements/gstinputselector.c |   58 ++-
+ plugins/elements/gstinputselector.h |1 +
+ 2 files changed, 45 insertions(+), 14 deletions(-)
+
+diff --git a/plugins/elements/gstinputselector.c 
b/plugins/elements/gstinputselector.c
+index fb50802..4461f7c 100644
+--- a/plugins/elements/gstinputselector.c
 b/plugins/elements/gstinputselector.c
+@@ -440,6 +440,17 @@ gst_selector_pad_iterate_linked_pads (GstPad * pad, 
GstObject * parent)
+ }
+ 
+ static gboolean
++gst_input_selector_eos_wait (GstInputSelector * self, GstSelectorPad * pad)
++{
++  while (!self->eos && !self->flushing && !pad->flushing) {
++/* we can be unlocked here when we are shutting down (flushing) or when we
++ * get unblocked */
++GST_INPUT_SELECTOR_WAIT (self);
++  }
++  return self->flushing;
++}
++
++static gboolean
+ gst_selector_pad_event (GstPad * pad, GstObject * parent, GstEvent * event)
+ {
+   gboolean res = TRUE;
+@@ -486,6 +497,7 @@ gst_selector_pad_event (GstPad * pad, GstObject * parent, 
GstEvent * event)
+ case GST_EVENT_FLUSH_START:
+   /* Unblock the pad if it's waiting */
+   selpad->flushing = TRUE;
++  sel->eos = FALSE;
+   GST_INPUT_SELECTOR_BROADCAST (sel);
+   break;
+ case GST_EVENT_FLUSH_STOP:
+@@ -523,21 +535,12 @@ gst_selector_pad_event (GstPad * pad, GstObject * 
parent, GstEvent * event)
+ case GST_EVENT_EOS:
+   selpad->eos = TRUE;
+ 
+-  if (forward) {
+-selpad->eos_sent = TRUE;
+-  } else {
+-GstSelectorPad *active_selpad;
+-
+-/* If the active sinkpad is in EOS state but EOS
+- * was not sent downstream this means that the pad
+- * got EOS before it was set as active pad and that
+- * the previously active pad got EOS after it was
+- * active
+- */
+-active_selpad = GST_SELECTOR_PAD (active_sinkpad);
+-forward = (active_selpad->eos && !active_selpad->eos_sent);
+-active_selpad->eos_sent = TRUE;
++  if (!forward) {
++/* blocked until active the sind pad or flush */
++gst_input_selector_eos_wait (sel, selpad);
++forward = TRUE;
+   }
++  selpad->eos_sent = TRUE;
+   GST_DEBUG_OBJECT (pad, "received EOS");
+   break;
+ case GST_EVENT_GAP:{
+@@ -676,6 +679,12 @@ gst_input_selector_wait_running_time (GstInputSelector * 
sel,
+ gst_input_selector_activate_sinkpad (sel, GST_PAD_CAST (selpad));
+ active_selpad = GST_SELECTOR_PAD_CAST (active_sinkpad);
+ 
++if (sel->eos) {
++  GST_DEBUG_OBJECT (sel, "Not waiting because inputselector reach EOS.");
++  GST_INPUT_SELECTOR_UNLOCK (sel);
++  return FALSE;
++}
++
+ if (seg->format != GST_FORMAT_TIME) {
+   GST_DEBUG_OBJECT (selpad,
+   "Not waiting because we don't have a TIME segment");
+@@ -971,6 +980,12 @@ gst_selector_pad_chain (GstPad * pad, GstObject * parent, 
GstBuffer * buf)
+   GST_TIME_ARGS (GST_BUFFER_TIMESTAMP (buf)));
+ 
+   GST_INPUT_SELECTOR_LOCK (sel);
++  if (sel->eos) {
++GST_DEBUG_OBJECT (pad, "inputselector eos.");
++GST_INPUT_SELECTOR_UNLOCK (sel);
++goto eos;
++  }
++
+   /* wait or check for flushing */
+   if (gst_input_selector_wait (sel, selpad)) {
+ GST_INPUT_SELECTOR_UNLOCK (sel);
+@@ -1151,6 +1166,13 @@ flushing:
+ res = GST_FLOW_FLUSHING;
+ goto done;
+   }
++eos:
++  {
++GST_DEBUG_OBJECT (pad, "We are eos, discard buffer %p", buf);
++gst_buffer_unref (buf);
++res = GST_FLOW_EOS;

[OE-core] [poky][PATCH v2 5/6] gstreamer1.0-plugins-base: Add videofilter related patch

[Yuqing Zhu]

Use new GST_VIDEO_FRAME_MAP_FLAG_NO_REF

Signed-off-by: Yuqing Zhu 
---
 ...r-Use-new-GST_VIDEO_FRAME_MAP_FLAG_NO_REF.patch | 69 ++
 .../gstreamer/gstreamer1.0-plugins-base_1.4.5.bb   |  3 +
 2 files changed, 72 insertions(+)
 create mode 100644 
meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/0003-videofilter-Use-new-GST_VIDEO_FRAME_MAP_FLAG_NO_REF.patch

diff --git 
a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/0003-videofilter-Use-new-GST_VIDEO_FRAME_MAP_FLAG_NO_REF.patch
 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/0003-videofilter-Use-new-GST_VIDEO_FRAME_MAP_FLAG_NO_REF.patch
new file mode 100644
index 000..91beb90
--- /dev/null
+++ 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/0003-videofilter-Use-new-GST_VIDEO_FRAME_MAP_FLAG_NO_REF.patch
@@ -0,0 +1,69 @@
+From 3a7cdcdfc9c5b0d20394fe51b3b8cda23931ca6d Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Sebastian=20Dr=C3=B6ge?= 
+Date: Fri, 12 Sep 2014 14:41:01 +0300
+Subject: [PATCH 3/3] videofilter: Use new GST_VIDEO_FRAME_MAP_FLAG_NO_REF
+
+Upstream Status: Accepted
+https://bugzilla.gnome.org/show_bug.cgi?id=736118
+---
+ gst-libs/gst/video/gstvideofilter.c |   23 ---
+ 1 file changed, 4 insertions(+), 19 deletions(-)
+
+diff --git a/gst-libs/gst/video/gstvideofilter.c 
b/gst-libs/gst/video/gstvideofilter.c
+index e1fa2c1..874b2e8 100644
+--- a/gst-libs/gst/video/gstvideofilter.c
 b/gst-libs/gst/video/gstvideofilter.c
+@@ -260,23 +260,15 @@ gst_video_filter_transform (GstBaseTransform * trans, 
GstBuffer * inbuf,
+   if (fclass->transform_frame) {
+ GstVideoFrame in_frame, out_frame;
+ 
+-if (!gst_video_frame_map (&in_frame, &filter->in_info, inbuf, 
GST_MAP_READ))
++if (!gst_video_frame_map (&in_frame, &filter->in_info, inbuf,
++GST_MAP_READ | GST_VIDEO_FRAME_MAP_FLAG_NO_REF))
+   goto invalid_buffer;
+ 
+ if (!gst_video_frame_map (&out_frame, &filter->out_info, outbuf,
+-GST_MAP_WRITE))
++GST_MAP_WRITE | GST_VIDEO_FRAME_MAP_FLAG_NO_REF))
+   goto invalid_buffer;
+ 
+-/* GstVideoFrame has another reference, so the buffer looks unwriteable,
+- * meaning that we can't attach any metas or anything to it. Other
+- * map() functions like gst_buffer_map() don't get another reference
+- * of the buffer and expect the buffer reference to be kept until
+- * the buffer is unmapped again. */
+-gst_buffer_unref (inbuf);
+-gst_buffer_unref (outbuf);
+ res = fclass->transform_frame (filter, &in_frame, &out_frame);
+-gst_buffer_ref (inbuf);
+-gst_buffer_ref (outbuf);
+ 
+ gst_video_frame_unmap (&out_frame);
+ gst_video_frame_unmap (&in_frame);
+@@ -317,7 +309,7 @@ gst_video_filter_transform_ip (GstBaseTransform * trans, 
GstBuffer * buf)
+ GstVideoFrame frame;
+ GstMapFlags flags;
+ 
+-flags = GST_MAP_READ;
++flags = GST_MAP_READ | GST_VIDEO_FRAME_MAP_FLAG_NO_REF;
+ 
+ if (!gst_base_transform_is_passthrough (trans))
+   flags |= GST_MAP_WRITE;
+@@ -325,14 +317,7 @@ gst_video_filter_transform_ip (GstBaseTransform * trans, 
GstBuffer * buf)
+ if (!gst_video_frame_map (&frame, &filter->in_info, buf, flags))
+   goto invalid_buffer;
+ 
+-/* GstVideoFrame has another reference, so the buffer looks unwriteable,
+- * meaning that we can't attach any metas or anything to it. Other
+- * map() functions like gst_buffer_map() don't get another reference
+- * of the buffer and expect the buffer reference to be kept until
+- * the buffer is unmapped again. */
+-gst_buffer_unref (buf);
+ res = fclass->transform_frame_ip (filter, &frame);
+-gst_buffer_ref (buf);
+ 
+ gst_video_frame_unmap (&frame);
+   } else {
+-- 
+1.7.9.5
+
diff --git 
a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.4.5.bb 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.4.5.bb
index 88c3254..9c31391 100644
--- a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.4.5.bb
+++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.4.5.bb
@@ -11,6 +11,9 @@ SRC_URI += 
"file://do-not-change-eos-event-to-gap-event-if.patch \
 file://fix-id3demux-utf16-to-utf8-issue.patch \
 file://handle-audio-video-decoder-error.patch \
 file://videobuffer_updata_alignment_update.patch \
+file://0002-video-frame-Add-GST_VIDEO_FRAME_MAP_FLAG_NO_REF.patch \
+file://0001-video-frame-Don-t-ref-buffers-twice-when-mapping.patch 
\
+
file://0003-videofilter-Use-new-GST_VIDEO_FRAME_MAP_FLAG_NO_REF.patch \
 "
 
 SRC_URI[md5sum] = "357165af625c0ca353ab47c5d843920e"
-- 
1.9.1

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

[OE-core] [poky][PATCH v2 1/6] gstreamer1.0-plugins-base: Bug fix for id3demux issue

[Yuqing Zhu]

Use g_utf16_to_utf8() instead of g_convert to fix the issue that
id3 tags utf16 charaters cannot be extreacted in id3demux when try
to get the id3v2 tag such as TIT2, TALB etc.

Signed-off-by: Yuqing Zhu 
---
 .../fix-id3demux-utf16-to-utf8-issue.patch | 54 ++
 .../gstreamer/gstreamer1.0-plugins-base_1.4.5.bb   |  1 +
 2 files changed, 55 insertions(+)
 create mode 100755 
meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/fix-id3demux-utf16-to-utf8-issue.patch

diff --git 
a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/fix-id3demux-utf16-to-utf8-issue.patch
 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/fix-id3demux-utf16-to-utf8-issue.patch
new file mode 100755
index 000..458d153
--- /dev/null
+++ 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/fix-id3demux-utf16-to-utf8-issue.patch
@@ -0,0 +1,54 @@
+Author: Lyon Wang 
+Date:   Thu Oct 9 17:37:43 2014 +0800
+
+[id3v2frames] Bug fix for id3demux issue
+
+Fix the issue that id3 tags utf16 charaters cannot be extreacted in id3demux
+when I tried to get the id3v2 tag such as TIT2, TALB etc. it will return extrac
+failed.
+
+Checked in id3v2frame.c,  When parse the UTF-16 streams, it used g_convert() to
+convert the buffer from UTF-16 to UTF-8, however it will return err that this
+conversion is not supported which cause the extraction failed with these UTF-16
+characters.
+
+In the patch, use g_utf16_to_utf8() instead of g_convert, which can convert the
+character format successfully.
+
+https://bugzilla.gnome.org/show_bug.cgi?id=741144
+
+Upstream Status: Pending
+
+Signed-off-by: Lyon Wang 
+
+diff --git a/gst-libs/gst/tag/id3v2frames.c b/gst-libs/gst/tag/id3v2frames.c
+old mode 100644
+new mode 100755
+index 3785c2a..7b9d8ac
+--- a/gst-libs/gst/tag/id3v2frames.c
 b/gst-libs/gst/tag/id3v2frames.c
+@@ -1057,14 +1057,17 @@ parse_insert_string_field (guint8 encoding, gchar * 
data, gint data_size,
+ data_size -= 2;
+   }
+ 
+-  field = g_convert (data, data_size, "UTF-8", in_encode, NULL, NULL, 
NULL);
+-
+-  if (field == NULL || g_utf8_validate (field, -1, NULL) == FALSE) {
+-/* As a fallback, try interpreting UTF-16 in the other endianness */
+-if (in_encode == utf16beenc)
+-  field = g_convert (data, data_size, "UTF-8", utf16leenc,
+-  NULL, NULL, NULL);
++  if (in_encode == utf16beenc) {
++   gunichar2 *data_utf16;
++   guint i;
++   data_utf16 =  (gunichar2 *) data;
++  for (i=0; i<(data_size>>1); i++) {
++data_utf16[i] = GUINT16_TO_LE (data_utf16[i]);
++  }
+   }
++  //field = g_convert (data, data_size, "UTF-8", in_encode, NULL, NULL, 
NULL);
++   field = g_utf16_to_utf8((gunichar2 *)data, (glong)(data_size>>1), 
NULL, NULL, NULL);
++
+ }
+ 
+   break;
diff --git 
a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.4.5.bb 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.4.5.bb
index 11cf8b4..aaa1ecb 100644
--- a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.4.5.bb
+++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.4.5.bb
@@ -8,6 +8,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=c54ce9345727175ff66d17b67ff51f58 \
 SRC_URI += "file://do-not-change-eos-event-to-gap-event-if.patch \
 file://get-caps-from-src-pad-when-query-caps.patch \
 file://taglist-not-send-to-down-stream-if-all-the-frame-cor.patch \
+file://fix-id3demux-utf16-to-utf8-issue.patch \
 "
 
 SRC_URI[md5sum] = "357165af625c0ca353ab47c5d843920e"
-- 
1.9.1

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

[OE-core] [poky][PATCH v2 2/6] gstreamer1.0-plugins-base: handle audio/video decoder error

[Yuqing Zhu]

When there is input data and no output data to the end of the stream, it will
send GST_ELEMENT_ERROR and quit from playing.
The patch comments the GST_ELEMENT_ERROR() and just add GST_ERROR_OBJECT()
information instead.

Signed-off-by: Yuqing Zhu 
---
 .../handle-audio-video-decoder-error.patch | 66 ++
 .../gstreamer/gstreamer1.0-plugins-base_1.4.5.bb   |  1 +
 2 files changed, 67 insertions(+)
 create mode 100755 
meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/handle-audio-video-decoder-error.patch

diff --git 
a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/handle-audio-video-decoder-error.patch
 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/handle-audio-video-decoder-error.patch
new file mode 100755
index 000..4451eaa
--- /dev/null
+++ 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/handle-audio-video-decoder-error.patch
@@ -0,0 +1,66 @@
+From bcb2b8b6f49e7c66124a4f5e07dea829d5ebfe59 Mon Sep 17 00:00:00 2001
+From: Lyon Wang 
+Date: Mon, 15 Dec 2014 16:52:07 +0800
+Subject: [PATCH] handle audio/video decoder error
+
+When there is input data and no output data to the end of the stream, it will
+send GST_ELEMENT_ERROR, So the clips playing will quit.
+However, if only one of the tracks is corrupt, there is no need to quit other
+tracks playing.
+
+The patch comments the GST_ELEMENT_ERROR() and just add GST_ERROR_OBJECT()
+information instead.
+
+https://bugzilla.gnome.org/show_bug.cgi?id=741542
+
+Upstream Status: Pending
+
+Signed-off-by: Lyon Wang 
+---
+ gst-libs/gst/audio/gstaudiodecoder.c |5 +++--
+ gst-libs/gst/video/gstvideodecoder.c |5 +++--
+ 2 files changed, 6 insertions(+), 4 deletions(-)
+ mode change 100644 => 100755 gst-libs/gst/audio/gstaudiodecoder.c
+ mode change 100644 => 100755 gst-libs/gst/video/gstvideodecoder.c
+
+diff --git a/gst-libs/gst/audio/gstaudiodecoder.c 
b/gst-libs/gst/audio/gstaudiodecoder.c
+old mode 100644
+new mode 100755
+index c2e7a28..891df0a
+--- a/gst-libs/gst/audio/gstaudiodecoder.c
 b/gst-libs/gst/audio/gstaudiodecoder.c
+@@ -2123,9 +2123,10 @@ gst_audio_decoder_sink_eventfunc (GstAudioDecoder * 
dec, GstEvent * event)
+   GST_AUDIO_DECODER_STREAM_UNLOCK (dec);
+ 
+   if (dec->priv->ctx.had_input_data && !dec->priv->ctx.had_output_data) {
+-GST_ELEMENT_ERROR (dec, STREAM, DECODE,
++/* GST_ELEMENT_ERROR (dec, STREAM, DECODE,
+ ("No valid frames decoded before end of stream"),
+-("no valid frames found"));
++("no valid frames found")); */
++GST_ERROR_OBJECT(dec, "No valid frames decoded before end of stream");
+   }
+ 
+   /* send taglist if no valid frame is decoded util EOS */
+diff --git a/gst-libs/gst/video/gstvideodecoder.c 
b/gst-libs/gst/video/gstvideodecoder.c
+old mode 100644
+new mode 100755
+index ac581e1..4278bcd
+--- a/gst-libs/gst/video/gstvideodecoder.c
 b/gst-libs/gst/video/gstvideodecoder.c
+@@ -1068,9 +1068,10 @@ gst_video_decoder_sink_event_default (GstVideoDecoder * 
decoder,
+ 
+   /* Error out even if EOS was ok when we had input, but no output */
+   if (ret && priv->had_input_data && !priv->had_output_data) {
+-GST_ELEMENT_ERROR (decoder, STREAM, DECODE,
++/* GST_ELEMENT_ERROR (decoder, STREAM, DECODE,
+ ("No valid frames decoded before end of stream"),
+-("no valid frames found"));
++("no valid frames found")); */
++GST_ERROR_OBJECT(decoder, "No valid frames decoded before end of 
stream");
+   }
+ 
+   /* Forward EOS immediately. This is required because no
+-- 
+1.7.9.5
+
diff --git 
a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.4.5.bb 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.4.5.bb
index aaa1ecb..aa90179 100644
--- a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.4.5.bb
+++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.4.5.bb
@@ -9,6 +9,7 @@ SRC_URI += 
"file://do-not-change-eos-event-to-gap-event-if.patch \
 file://get-caps-from-src-pad-when-query-caps.patch \
 file://taglist-not-send-to-down-stream-if-all-the-frame-cor.patch \
 file://fix-id3demux-utf16-to-utf8-issue.patch \
+file://handle-audio-video-decoder-error.patch \
 "
 
 SRC_URI[md5sum] = "357165af625c0ca353ab47c5d843920e"
-- 
1.9.1

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

[OE-core] [poky][PATCH v2 6/6] gstreamer1.0-plugins-base: Add videoencoder related patch

[Yuqing Zhu]

Keep sticky events around when doing a soft reset.
The current code will first discard all frames, and then tries to copy
all sticky events from the (now discarded) frames. So change the order.

Signed-off-by: Yuqing Zhu 
---
 ...p-sticky-events-around-when-doing-a-soft-.patch | 46 ++
 .../gstreamer/gstreamer1.0-plugins-base_1.4.5.bb   |  1 +
 2 files changed, 47 insertions(+)
 create mode 100644 
meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/videoencoder-Keep-sticky-events-around-when-doing-a-soft-.patch

diff --git 
a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/videoencoder-Keep-sticky-events-around-when-doing-a-soft-.patch
 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/videoencoder-Keep-sticky-events-around-when-doing-a-soft-.patch
new file mode 100644
index 000..fc1cbed
--- /dev/null
+++ 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/videoencoder-Keep-sticky-events-around-when-doing-a-soft-.patch
@@ -0,0 +1,46 @@
+From c3f7d36b992a3cbcee3386dea85720f3cb04e1ff Mon Sep 17 00:00:00 2001
+From: Song Bing 
+Date: Fri, 27 Mar 2015 13:39:43 +0800
+Subject: [PATCH] videoencoder: Keep sticky events around when doing a soft
+ reset
+
+The current code will first discard all frames, and then tries to copy
+all sticky events from the (now discarded) frames. Let's change the order.
+
+https://bugzilla.gnome.org/show_bug.cgi?id=746865
+
+Upstream Status: Accepted 
+
+---
+ gst-libs/gst/video/gstvideoencoder.c |8 
+ 1 file changed, 4 insertions(+), 4 deletions(-)
+
+diff --git a/gst-libs/gst/video/gstvideoencoder.c 
b/gst-libs/gst/video/gstvideoencoder.c
+index 614ba2d..4c5b111 100644
+--- a/gst-libs/gst/video/gstvideoencoder.c
 b/gst-libs/gst/video/gstvideoencoder.c
+@@ -340,10 +340,6 @@ gst_video_encoder_reset (GstVideoEncoder * encoder, 
gboolean hard)
+ 
+   priv->drained = TRUE;
+ 
+-  g_list_foreach (priv->frames, (GFunc) gst_video_codec_frame_unref, NULL);
+-  g_list_free (priv->frames);
+-  priv->frames = NULL;
+-
+   priv->bytes = 0;
+   priv->time = 0;
+ 
+@@ -392,6 +388,10 @@ gst_video_encoder_reset (GstVideoEncoder * encoder, 
gboolean hard)
+ encoder->priv->current_frame_events);
+   }
+ 
++  g_list_foreach (priv->frames, (GFunc) gst_video_codec_frame_unref, NULL);
++  g_list_free (priv->frames);
++  priv->frames = NULL;
++
+   GST_VIDEO_ENCODER_STREAM_UNLOCK (encoder);
+ 
+   return ret;
+-- 
+1.7.9.5
+
diff --git 
a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.4.5.bb 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.4.5.bb
index 9c31391..8daf5af 100644
--- a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.4.5.bb
+++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.4.5.bb
@@ -14,6 +14,7 @@ SRC_URI += 
"file://do-not-change-eos-event-to-gap-event-if.patch \
 file://0002-video-frame-Add-GST_VIDEO_FRAME_MAP_FLAG_NO_REF.patch \
 file://0001-video-frame-Don-t-ref-buffers-twice-when-mapping.patch 
\
 
file://0003-videofilter-Use-new-GST_VIDEO_FRAME_MAP_FLAG_NO_REF.patch \
+
file://videoencoder-Keep-sticky-events-around-when-doing-a-soft-.patch \
 "
 
 SRC_URI[md5sum] = "357165af625c0ca353ab47c5d843920e"
-- 
1.9.1

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

Re: [OE-core] [PATCH V2 3/3] sudo: upgrade to 1.8.14p2

[ChenQi]

On 07/25/2015 04:38 AM, Burton, Ross wrote:


On 24 July 2015 at 10:08, Chen Qi > wrote:


The licence checksum is modified according to the change of
doc/LICENCE.
In specific, file://lib/util/reallocarray.c is added to
LIC_FILES_CHECKSUM.


This fails to build in systemd builds and in fixing it I discovered 
that there's a p3 released now, which I submitted to the list earlier.


Ross


Oh, Thanks Ross!

Best Regards,
Chen Qi
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [poky][PATCH v2 2/2] gstreamer1.0: Add basesink related patch

[Yuqing Zhu]

Fix QoS/lateness checking if subclass implements
prepare/prepare_list vfuncs

Signed-off-by: Yuqing Zhu 
---
 ...x-QoS-lateness-checking-if-subclass-imple.patch | 70 ++
 .../gstreamer/gstreamer1.0_1.4.5.bb|  1 +
 2 files changed, 71 insertions(+)
 create mode 100644 
meta/recipes-multimedia/gstreamer/gstreamer1.0/0002-basesink-Fix-QoS-lateness-checking-if-subclass-imple.patch

diff --git 
a/meta/recipes-multimedia/gstreamer/gstreamer1.0/0002-basesink-Fix-QoS-lateness-checking-if-subclass-imple.patch
 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0/0002-basesink-Fix-QoS-lateness-checking-if-subclass-imple.patch
new file mode 100644
index 000..2adfadc
--- /dev/null
+++ 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0/0002-basesink-Fix-QoS-lateness-checking-if-subclass-imple.patch
@@ -0,0 +1,70 @@
+From 6914566ed6a89c96973a578aa5ecd01ee68cdcfd Mon Sep 17 00:00:00 2001
+From: Jian 
+Date: Thu, 14 May 2015 15:49:43 +0800
+Subject: [PATCH] basesink: Fix QoS/lateness checking if subclass implements
+ prepare/prepare_list vfuncs
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+In basesink functions gst_base_sink_chain_unlocked(), below code is used to
+checking if buffer is late before doing prepare call to save some effort:
+if (syncable && do_sync)
+  late =
+  gst_base_sink_is_too_late (basesink, obj, rstart, rstop,
+  GST_CLOCK_EARLY, 0, FALSE);
+
+if (G_UNLIKELY (late))
+  goto dropped;
+
+But this code has problem, it should calculate jitter based on current media
+clock, rather than just passing 0. I found it will drop all the frames when
+rewind in slow speed, such as -2X.
+
+https://bugzilla.gnome.org/show_bug.cgi?id=749258
+
+Upstream Status: Backport-GST 1.5.1
+---
+ libs/gst/base/gstbasesink.c |   26 ++
+ 1 file changed, 22 insertions(+), 4 deletions(-)
+
+diff --git a/libs/gst/base/gstbasesink.c b/libs/gst/base/gstbasesink.c
+index a505695..5fb2d6a 100644
+--- a/libs/gst/base/gstbasesink.c
 b/libs/gst/base/gstbasesink.c
+@@ -3369,10 +3369,28 @@ gst_base_sink_chain_unlocked (GstBaseSink * basesink, 
GstPad * pad,
+ if (G_UNLIKELY (stepped))
+   goto dropped;
+ 
+-if (syncable && do_sync)
+-  late =
+-  gst_base_sink_is_too_late (basesink, obj, rstart, rstop,
+-  GST_CLOCK_EARLY, 0, FALSE);
++if (syncable && do_sync) {
++  GstClock *clock;
++
++  GST_OBJECT_LOCK (basesink);
++  clock = GST_ELEMENT_CLOCK (basesink);
++  if (clock && GST_STATE (basesink) == GST_STATE_PLAYING) {
++GstClockTime base_time;
++GstClockTime stime;
++GstClockTime now;
++
++base_time = GST_ELEMENT_CAST (basesink)->base_time;
++stime = base_time + gst_base_sink_adjust_time (basesink, rstart);
++now = gst_clock_get_time (clock);
++GST_OBJECT_UNLOCK (basesink);
++
++late =
++gst_base_sink_is_too_late (basesink, obj, rstart, rstop,
++GST_CLOCK_EARLY, GST_CLOCK_DIFF (stime, now), FALSE);
++  } else {
++GST_OBJECT_UNLOCK (basesink);
++  }
++}
+ 
+ if (G_UNLIKELY (late))
+   goto dropped;
+-- 
+1.7.9.5
+
diff --git a/meta/recipes-multimedia/gstreamer/gstreamer1.0_1.4.5.bb 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0_1.4.5.bb
index 902f79d..db58754 100644
--- a/meta/recipes-multimedia/gstreamer/gstreamer1.0_1.4.5.bb
+++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0_1.4.5.bb
@@ -8,6 +8,7 @@ SRC_URI = " \
 file://0001-Fix-crash-with-gst-inspect.patch \
 file://0001-gstinfo-Shorten-__FILE__-on-all-platforms.patch \
 file://inputselector-sticky-events-haven-t-send-out-when-ac-1-4-1.patch \
+file://0002-basesink-Fix-QoS-lateness-checking-if-subclass-imple.patch \
 "
 SRC_URI[md5sum] = "88a9289c64a4950ebb4f544980234289"
 SRC_URI[sha256sum] = 
"40801aa7f979024526258a0e94707ba42b8ab6f7d2206e56adbc4433155cb0ae"
-- 
1.9.1

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

[OE-core] [poky][PATCH v2 0/2] Upgrade to 3.14.38-6QP_Beta release

[Yuqing Zhu]

Fix sticky events haven't send out when active track reach EOS

Fix QoS/lateness checking if subclass implements prepare/prepare_list vfuncs

Yuqing Zhu (2):
  gstreamer1.0: Add inputselector related patch
  gstreamer1.0: Add basesink related patch

 ...x-QoS-lateness-checking-if-subclass-imple.patch |  70 +
 ...cky-events-haven-t-send-out-when-ac-1-4-1.patch | 167 +
 .../gstreamer/gstreamer1.0_1.4.5.bb|   2 +
 3 files changed, 239 insertions(+)
 create mode 100644 
meta/recipes-multimedia/gstreamer/gstreamer1.0/0002-basesink-Fix-QoS-lateness-checking-if-subclass-imple.patch
 create mode 100755 
meta/recipes-multimedia/gstreamer/gstreamer1.0/inputselector-sticky-events-haven-t-send-out-when-ac-1-4-1.patch

-- 
1.9.1

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

[OE-core] [poky][PATCH v2 4/6] gstreamer1.0-plugins-base: Add video-frame related patch

[Yuqing Zhu]

-Add GST_VIDEO_FRAME_MAP_FLAG_NO_REF
 This makes sure that the buffer is not reffed another time when
 storing it in the GstVideoFrame, keeping it writable if it was writable.

-Don't ref buffers twice when mapping

Signed-off-by: Yuqing Zhu 
---
 ...rame-Don-t-ref-buffers-twice-when-mapping.patch | 25 +++
 ...frame-Add-GST_VIDEO_FRAME_MAP_FLAG_NO_REF.patch | 87 ++
 2 files changed, 112 insertions(+)
 create mode 100644 
meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/0001-video-frame-Don-t-ref-buffers-twice-when-mapping.patch
 create mode 100644 
meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/0002-video-frame-Add-GST_VIDEO_FRAME_MAP_FLAG_NO_REF.patch

diff --git 
a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/0001-video-frame-Don-t-ref-buffers-twice-when-mapping.patch
 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/0001-video-frame-Don-t-ref-buffers-twice-when-mapping.patch
new file mode 100644
index 000..c4eef00
--- /dev/null
+++ 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/0001-video-frame-Don-t-ref-buffers-twice-when-mapping.patch
@@ -0,0 +1,25 @@
+From 269f642c45d85cfd630ed490478e6bd6b71a767f Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Sebastian=20Dr=C3=B6ge?= 
+Date: Tue, 16 Sep 2014 01:07:18 +0300
+Subject: [PATCH] video-frame: Don't ref buffers twice when mapping
+
+---
+ gst-libs/gst/video/video-frame.c |2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/gst-libs/gst/video/video-frame.c 
b/gst-libs/gst/video/video-frame.c
+index 01f23c0..8a9ae96 100644
+--- a/gst-libs/gst/video/video-frame.c
 b/gst-libs/gst/video/video-frame.c
+@@ -105,7 +105,7 @@ gst_video_frame_map_id (GstVideoFrame * frame, 
GstVideoInfo * info,
+   frame->data[i] = frame->map[0].data + info->offset[i];
+ }
+   }
+-  frame->buffer = gst_buffer_ref (buffer);
++  frame->buffer = buffer;
+   if ((flags & GST_VIDEO_FRAME_MAP_FLAG_NO_REF) == 0)
+ gst_buffer_ref (frame->buffer);
+ 
+-- 
+1.7.9.5
+
diff --git 
a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/0002-video-frame-Add-GST_VIDEO_FRAME_MAP_FLAG_NO_REF.patch
 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/0002-video-frame-Add-GST_VIDEO_FRAME_MAP_FLAG_NO_REF.patch
new file mode 100644
index 000..554b8ac
--- /dev/null
+++ 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/0002-video-frame-Add-GST_VIDEO_FRAME_MAP_FLAG_NO_REF.patch
@@ -0,0 +1,87 @@
+From 40a293d44d1aeccf5eb8e86f23a0b13666111c5c Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Sebastian=20Dr=C3=B6ge?= 
+Date: Fri, 12 Sep 2014 14:39:16 +0300
+Subject: [PATCH 2/3] video-frame: Add GST_VIDEO_FRAME_MAP_FLAG_NO_REF
+
+This makes sure that the buffer is not reffed another time when
+storing it in the GstVideoFrame, keeping it writable if it was
+writable.
+
+Upstream Status: Accepted
+https://bugzilla.gnome.org/show_bug.cgi?id=736118
+---
+ gst-libs/gst/video/video-frame.c |9 -
+ gst-libs/gst/video/video-frame.h |   18 ++
+ 2 files changed, 26 insertions(+), 1 deletion(-)
+
+diff --git a/gst-libs/gst/video/video-frame.c 
b/gst-libs/gst/video/video-frame.c
+index 537cf70..01f23c0 100644
+--- a/gst-libs/gst/video/video-frame.c
 b/gst-libs/gst/video/video-frame.c
+@@ -106,6 +106,9 @@ gst_video_frame_map_id (GstVideoFrame * frame, 
GstVideoInfo * info,
+ }
+   }
+   frame->buffer = gst_buffer_ref (buffer);
++  if ((flags & GST_VIDEO_FRAME_MAP_FLAG_NO_REF) == 0)
++gst_buffer_ref (frame->buffer);
++
+   frame->meta = meta;
+ 
+   /* buffer flags enhance the frame flags */
+@@ -189,11 +192,13 @@ gst_video_frame_unmap (GstVideoFrame * frame)
+   GstBuffer *buffer;
+   GstVideoMeta *meta;
+   gint i;
++  GstMapFlags flags;
+ 
+   g_return_if_fail (frame != NULL);
+ 
+   buffer = frame->buffer;
+   meta = frame->meta;
++  flags = frame->map[0].flags;
+ 
+   if (meta) {
+ for (i = 0; i < frame->info.finfo->n_planes; i++) {
+@@ -202,7 +207,9 @@ gst_video_frame_unmap (GstVideoFrame * frame)
+   } else {
+ gst_buffer_unmap (buffer, &frame->map[0]);
+   }
+-  gst_buffer_unref (buffer);
++
++  if ((flags & GST_VIDEO_FRAME_MAP_FLAG_NO_REF) == 0)
++gst_buffer_unref (frame->buffer);
+ }
+ 
+ /**
+diff --git a/gst-libs/gst/video/video-frame.h 
b/gst-libs/gst/video/video-frame.h
+index 627fab0..f8e6304 100644
+--- a/gst-libs/gst/video/video-frame.h
 b/gst-libs/gst/video/video-frame.h
+@@ -149,6 +149,24 @@ typedef enum {
+   GST_VIDEO_BUFFER_FLAG_LAST= (GST_BUFFER_FLAG_LAST << 8)
+ } GstVideoBufferFlags;
+ 
++/**
++ * GstVideoBufferFlags:
++ * @GST_VIDEO_FRAME_MAP_FLAG_NO_REF:  Don't take another reference of the 
buffer and store it in
++ *the GstVideoFrame. This makes sure that 
the buffer stays
++ *writable while the frame is mapped, but 
requires that the
++ *buffer reference stays valid until the

[OE-core] [poky][PATCH v2 0/6] Upgrade to 3.14.38-6QP_Beta release

[Yuqing Zhu]

Fix id3demux issue

Handle audio/video decoder error

Update video alignment after video alignment

Add GST_VIDEO_FRAME_MAP_FLAG_NO_REF, keeping buffer writable

Gstvideofilter use new GST_VIDEO_FRAME_MAP_FLAG_NO_REF

Don't ref buffers twice when mapping

Keep sticky events around when doing a soft reset

Yuqing Zhu (6):
  gstreamer1.0-plugins-base: Bug fix for id3demux issue
  gstreamer1.0-plugins-base: handle audio/video decoder error
  gstreamer1.0-plugins-base: update video alignment after video
alignment
  gstreamer1.0-plugins-base: Add video-frame related patch
  gstreamer1.0-plugins-base: Add videofilter related patch
  gstreamer1.0-plugins-base: Add videoencoder related patch

 ...rame-Don-t-ref-buffers-twice-when-mapping.patch | 25 +++
 ...frame-Add-GST_VIDEO_FRAME_MAP_FLAG_NO_REF.patch | 87 ++
 ...r-Use-new-GST_VIDEO_FRAME_MAP_FLAG_NO_REF.patch | 69 +
 .../fix-id3demux-utf16-to-utf8-issue.patch | 54 ++
 .../handle-audio-video-decoder-error.patch | 66 
 .../videobuffer_updata_alignment_update.patch  | 53 +
 ...p-sticky-events-around-when-doing-a-soft-.patch | 46 
 .../gstreamer/gstreamer1.0-plugins-base_1.4.5.bb   |  7 ++
 8 files changed, 407 insertions(+)
 create mode 100644 
meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/0001-video-frame-Don-t-ref-buffers-twice-when-mapping.patch
 create mode 100644 
meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/0002-video-frame-Add-GST_VIDEO_FRAME_MAP_FLAG_NO_REF.patch
 create mode 100644 
meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/0003-videofilter-Use-new-GST_VIDEO_FRAME_MAP_FLAG_NO_REF.patch
 create mode 100755 
meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/fix-id3demux-utf16-to-utf8-issue.patch
 create mode 100755 
meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/handle-audio-video-decoder-error.patch
 create mode 100755 
meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/videobuffer_updata_alignment_update.patch
 create mode 100644 
meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/videoencoder-Keep-sticky-events-around-when-doing-a-soft-.patch

-- 
1.9.1

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

[OE-core] [poky][PATCH v2 3/6] gstreamer1.0-plugins-base: update video alignment after video alignment

[Yuqing Zhu]

Video buffer pool will update video alignment to respect stride alignment
requirement. But haven't update it to video alignment in configure.
Which will cause user get wrong video alignment.

Signed-off-by: Yuqing Zhu 
---
 .../videobuffer_updata_alignment_update.patch  | 53 ++
 .../gstreamer/gstreamer1.0-plugins-base_1.4.5.bb   |  1 +
 2 files changed, 54 insertions(+)
 create mode 100755 
meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/videobuffer_updata_alignment_update.patch

diff --git 
a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/videobuffer_updata_alignment_update.patch
 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/videobuffer_updata_alignment_update.patch
new file mode 100755
index 000..57edd8b
--- /dev/null
+++ 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/videobuffer_updata_alignment_update.patch
@@ -0,0 +1,53 @@
+commit 88d253ea23b06289df40401160b606323f16c910
+Author: Song Bing 
+Date:   Mon Dec 15 09:34:35 2014 +0800
+
+videopool: update video alignment after video alignment
+
+Video buffer pool will update video alignment to respect stride alignment
+requirement. But haven't update it to video alignment in configure.
+Which will cause user get wrong video alignment.
+
+https://bugzilla.gnome.org/show_bug.cgi?id=741501
+
+Upstream Status: Backport
+
+Signed-off-by: Song Bing 
+diff --git a/gst-libs/gst/video/gstvideopool.c 
b/gst-libs/gst/video/gstvideopool.c
+index 4475f45..acef594 100644
+--- a/gst-libs/gst/video/gstvideopool.c
 b/gst-libs/gst/video/gstvideopool.c
+@@ -167,6 +167,7 @@ video_buffer_pool_set_config (GstBufferPool * pool, 
GstStructure * config)
+ /* get an apply the alignment to the info */
+ gst_buffer_pool_config_get_video_alignment (config, &priv->video_align);
+ gst_video_info_align (&info, &priv->video_align);
++gst_buffer_pool_config_set_video_alignment (config, &priv->video_align);
+   }
+   priv->info = info;
+
+diff --git a/sys/ximage/ximagepool.c b/sys/ximage/ximagepool.c
+index 6cc2cfa..6a1cbc9 100644
+--- a/sys/ximage/ximagepool.c
 b/sys/ximage/ximagepool.c
+@@ -597,6 +597,8 @@ ximage_buffer_pool_set_config (GstBufferPool * pool, 
GstStructure * config)
+ /* do padding and alignment */
+ gst_video_info_align (&info, &priv->align);
+
++gst_buffer_pool_config_set_video_alignment (config, &priv->align);
++
+ /* we need the video metadata too now */
+ priv->add_metavideo = TRUE;
+   } else {
+diff --git a/sys/xvimage/xvimagepool.c b/sys/xvimage/xvimagepool.c
+index 244a51a..34b1ab2 100644
+--- a/sys/xvimage/xvimagepool.c
 b/sys/xvimage/xvimagepool.c
+@@ -124,6 +124,8 @@ xvimage_buffer_pool_set_config (GstBufferPool * pool, 
GstStructure * config)
+ /* do padding and alignment */
+ gst_video_info_align (&info, &priv->align);
+
++gst_buffer_pool_config_set_video_alignment (config, &priv->align);
++
+ /* we need the video metadata too now */
+ priv->add_metavideo = TRUE;
+   } else {
diff --git 
a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.4.5.bb 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.4.5.bb
index aa90179..88c3254 100644
--- a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.4.5.bb
+++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.4.5.bb
@@ -10,6 +10,7 @@ SRC_URI += 
"file://do-not-change-eos-event-to-gap-event-if.patch \
 file://taglist-not-send-to-down-stream-if-all-the-frame-cor.patch \
 file://fix-id3demux-utf16-to-utf8-issue.patch \
 file://handle-audio-video-decoder-error.patch \
+file://videobuffer_updata_alignment_update.patch \
 "
 
 SRC_URI[md5sum] = "357165af625c0ca353ab47c5d843920e"
-- 
1.9.1

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

Re: [OE-core] [PATCH v2 0/2] Yocto Bug #6945

[He Zhe]

Ping.

On 07/23/2015 03:48 PM, He Zhe wrote:
> Ping.
>
> On 07/21/2015 03:23 PM, zhe...@windriver.com wrote:
>> From: He Zhe 
>>
>>  - To support building packaging and installing multi types of kernel
>>images, such as zImage uImage, at one time define KERNEL_IMAGETYPE
>>as a list.
>>  - Modify wherever reference KERNEL_IMAGETYPE accordingly.
>>  - Pass mkimage in sysroot to kernel makefile by NATIVE_MKIMAGE to avoid
>>depending on build machine's, when KEEPUIMAGE is "yes".
>>  - v2: update with the latest oe-core
>>
>> He Zhe (2):
>>   kernel: Define KERNEL_IMAGETYPE as a list
>>   kernel: Pass sysroot mkimage to kernel makefile
>>
>>  meta/classes/image_types.bbclass |   6 +-
>>  meta/classes/kernel-fitimage.bbclass |  22 +++---
>>  meta/classes/kernel-grub.bbclass |  47 
>>  meta/classes/kernel-uimage.bbclass   |  31 +---
>>  meta/classes/kernel.bbclass  | 127 
>> ++-
>>  meta/conf/documentation.conf |   2 +-
>>  meta/lib/oeqa/controllers/masterimage.py |   2 +-
>>  meta/lib/oeqa/targetcontrol.py   |   2 +-
>>  meta/recipes-kernel/linux/linux-dtb.inc  |  15 ++--
>>  scripts/test-remote-image|   2 +-
>>  10 files changed, 175 insertions(+), 81 deletions(-)
>>

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

[OE-core] [PATCH] bind: upgrade to 9.10.2-P2

[rongqing.li]

From: Roy Li 

upgrade to fix CVE-2015-4620:
name.c in named in ISC BIND 9.7.x through 9.9.x before 9.9.7-P1 and 9.10.x
before 9.10.2-P2, when configured as a recursive resolver with DNSSEC
validation, allows remote attackers to cause a denial of service (REQUIRE
assertion failure and daemon exit) by constructing crafted zone data and
then making a query for a name in that zone.

Signed-off-by: Roy Li 
---
 meta/recipes-connectivity/bind/bind_9.10.2-P2.bb | 103 +++
 meta/recipes-connectivity/bind/bind_9.10.2.bb| 103 ---
 2 files changed, 103 insertions(+), 103 deletions(-)
 create mode 100644 meta/recipes-connectivity/bind/bind_9.10.2-P2.bb
 delete mode 100644 meta/recipes-connectivity/bind/bind_9.10.2.bb

diff --git a/meta/recipes-connectivity/bind/bind_9.10.2-P2.bb 
b/meta/recipes-connectivity/bind/bind_9.10.2-P2.bb
new file mode 100644
index 000..0d2af55
--- /dev/null
+++ b/meta/recipes-connectivity/bind/bind_9.10.2-P2.bb
@@ -0,0 +1,103 @@
+SUMMARY = "ISC Internet Domain Name Server"
+HOMEPAGE = "http://www.isc.org/sw/bind/";
+SECTION = "console/network"
+
+LICENSE = "ISC & BSD"
+LIC_FILES_CHKSUM = "file://COPYRIGHT;md5=0a95f52a0ab6c5f52dedc9a45e7abb3f"
+
+DEPENDS = "openssl libcap"
+
+SRC_URI = "ftp://ftp.isc.org/isc/bind9/${PV}/${BPN}-${PV}.tar.gz \
+   file://conf.patch \
+   file://make-etc-initd-bind-stop-work.patch \
+   file://mips1-not-support-opcode.diff \
+   file://dont-test-on-host.patch \
+   file://generate-rndc-key.sh \
+   file://named.service \
+   file://bind9 \
+   file://init.d-add-support-for-read-only-rootfs.patch \
+   file://bind-confgen-build-unix.o-once.patch \
+   file://0001-build-use-pkg-config-to-find-libxml2.patch \
+   file://bind-ensure-searching-for-json-headers-searches-sysr.patch \
+   "
+
+SRC_URI[md5sum] = "55d8f094bc10baae0e23e5e9100ba320"
+SRC_URI[sha256sum] = 
"b1e6f0af88634aaf48fb9d06bbf82968264f49b8e2685f061dd3fd4c1ab76c5f"
+
+# --enable-exportlib is necessary for building dhcp
+ENABLE_IPV6 = "--enable-ipv6=${@bb.utils.contains('DISTRO_FEATURES', 'ipv6', 
'yes', 'no', d)}"
+EXTRA_OECONF = " ${ENABLE_IPV6} --with-randomdev=/dev/random --disable-threads 
\
+ --disable-devpoll --disable-epoll --with-gost=no \
+ --with-gssapi=no --with-ecdsa=yes \
+ --sysconfdir=${sysconfdir}/bind \
+ --with-openssl=${STAGING_LIBDIR}/.. \
+   "
+inherit autotools update-rc.d systemd useradd pkgconfig
+
+PR = "r1"
+
+PACKAGECONFIG ?= ""
+PACKAGECONFIG[httpstats] = "--with-libxml2,--without-libxml2,libxml2"
+
+USERADD_PACKAGES = "${PN}"
+USERADD_PARAM_${PN} = "--system --home /var/cache/bind --no-create-home \
+   --user-group bind"
+
+INITSCRIPT_NAME = "bind"
+INITSCRIPT_PARAMS = "defaults"
+
+SYSTEMD_SERVICE_${PN} = "named.service"
+
+PARALLEL_MAKE = ""
+
+RDEPENDS_${PN} = "python-core"
+
+PACKAGE_BEFORE_PN += "${PN}-utils"
+FILES_${PN}-utils = "${bindir}/host ${bindir}/dig"
+FILES_${PN}-dev += "${bindir}/isc-config.h"
+FILES_${PN} += "${sbindir}/generate-rndc-key.sh"
+
+do_install_prepend() {
+   # clean host path in isc-config.sh before the hardlink created
+   # by "make install":
+   #   bind9-config -> isc-config.sh
+   sed -i -e "s,${STAGING_LIBDIR},${libdir}," ${B}/isc-config.sh
+}
+
+do_install_append() {
+   rm "${D}${bindir}/nslookup"
+   rm "${D}${mandir}/man1/nslookup.1"
+   rmdir "${D}${localstatedir}/run"
+   rmdir --ignore-fail-on-non-empty "${D}${localstatedir}"
+   install -d "${D}${localstatedir}/cache/bind"
+   install -d "${D}${sysconfdir}/bind"
+   install -d "${D}${sysconfdir}/init.d"
+   install -m 644 ${S}/conf/* "${D}${sysconfdir}/bind/"
+   install -m 755 "${S}/init.d" "${D}${sysconfdir}/init.d/bind"
+   sed -i -e '1s,#!.*python,#! /usr/bin/env python,' 
${D}${sbindir}/dnssec-coverage ${D}${sbindir}/dnssec-checkds
+
+   # Install systemd related files
+   install -d ${D}${localstatedir}/cache/bind
+   install -d ${D}${sbindir}
+   install -m 755 ${WORKDIR}/generate-rndc-key.sh ${D}${sbindir}
+   install -d ${D}${systemd_unitdir}/system
+   install -m 0644 ${WORKDIR}/named.service ${D}${systemd_unitdir}/system
+   sed -i -e 's,@BASE_BINDIR@,${base_bindir},g' \
+  -e 's,@SBINDIR@,${sbindir},g' \
+  ${D}${systemd_unitdir}/system/named.service
+
+   install -d ${D}${sysconfdir}/default
+   install -m 0644 ${WORKDIR}/bind9 ${D}${sysconfdir}/default
+}
+
+CONFFILES_${PN} = " \
+   ${sysconfdir}/bind/named.conf \
+   ${sysconfdir}/bind/named.conf.local \
+   ${sysconfdir}/bind/named.conf.options \
+   ${sysconfdir}/bind/db.0 \
+   ${sysconfdir}/bind/db.127 \
+   ${sysconfdir}/bind/db.empty \
+   ${sysconfdir}/bind/db.local \
+   ${sysconfdir}/bind/db.root \
+

Re: [OE-core] [PATCH 4/5] git: 2.4.4 -> 2.4.5

[Robert Yang]

On 07/17/2015 07:34 PM, Burton, Ross wrote:


On 17 July 2015 at 03:31, Robert Yang mailto:liezhi.y...@windriver.com>> wrote:

* Use git repo rathar then tarball.


For this and the file upgrade, why?

Tarballs are easily cached, and can be checksummed.  What's the reason to switch
to a git clone?


Hi Ross,

I just came back from vacation, I thought that git repo is preferred than
tarball, but seems not, so let's drop the 2 upgrades.

// Robert



Ross

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

Re: [OE-core] [PATCH][resend] perl: fix build failure if building dir has the "blib" string

[Rongqing Li]

On 2015年07月10日 17:39, Jussi Kukkonen wrote:

On 10 July 2015 at 11:54,   wrote:

From: Wenzong Fan 

If build dir includes the string "blib", filter it out from @INC may empty
the @INC and cause build errors like:

   Can't locate ExtUtils/MakeMaker.pm in @INC \
   (you may need to install the ExtUtils::MakeMaker module) \
   (@INC contains: .) at Makefile.PL


The grep certainly looks overly zealous, but surely upstream has a
reason for having this code... If you're going to remove the code
altogether, you should mention why those original reasons do not apply
here.

Jussi



I think we can merge this patch.

I open a defect and submit this patch, as a result, noone knows
what this line can fix.


https://rt.perl.org/Public/Bug/Display.html?id=125603

-Roy






Signed-off-by: Roy Li 
Signed-off-by: Wenzong Fan 
---
  meta/recipes-devtools/perl/perl-native_5.22.0.bb   |  1 +
  ...-PathTools-don-t-filter-out-blib-from-INC.patch | 33 ++
  meta/recipes-devtools/perl/perl_5.22.0.bb  |  1 +
  3 files changed, 35 insertions(+)
  create mode 100644 
meta/recipes-devtools/perl/perl/perl-PathTools-don-t-filter-out-blib-from-INC.patch

diff --git a/meta/recipes-devtools/perl/perl-native_5.22.0.bb 
b/meta/recipes-devtools/perl/perl-native_5.22.0.bb
index dbcf2a6..a9a1cab 100644
--- a/meta/recipes-devtools/perl/perl-native_5.22.0.bb
+++ b/meta/recipes-devtools/perl/perl-native_5.22.0.bb
@@ -8,6 +8,7 @@ SRC_URI += "\
 file://MM_Unix.pm.patch \
 file://debian/errno_ver.diff \
 file://dynaloaderhack.patch \
+   file://perl-PathTools-don-t-filter-out-blib-from-INC.patch \
"

  SRC_URI[md5sum] = "ff0f09b17de426eff323426cb140ee79"
diff --git 
a/meta/recipes-devtools/perl/perl/perl-PathTools-don-t-filter-out-blib-from-INC.patch
 
b/meta/recipes-devtools/perl/perl/perl-PathTools-don-t-filter-out-blib-from-INC.patch
new file mode 100644
index 000..7dd9041
--- /dev/null
+++ 
b/meta/recipes-devtools/perl/perl/perl-PathTools-don-t-filter-out-blib-from-INC.patch
@@ -0,0 +1,33 @@
+From 90c252cecc38aed5d5faedb30485dd6eee2e54eb Mon Sep 17 00:00:00 2001
+From: Wenzong Fan 
+Date: Wed, 11 Feb 2015 15:14:40 +0800
+Subject: [PATCH] perl / PathTools: don't filter out blib from @INC
+
+If $TOPDIR includes the string "blib", filter it out from @INC may empty
+the @INC and cause build errors like:
+
+  Can't locate ExtUtils/MakeMaker.pm in @INC \
+  (you may need to install the ExtUtils::MakeMaker module) \
+  (@INC contains: .) at Makefile.PL
+
+Upstream-Status: Pending
+
+Signed-off-by: Wenzong Fan 
+---
+ dist/PathTools/Makefile.PL | 3 ---
+ 1 file changed, 3 deletions(-)
+
+diff --git a/dist/PathTools/Makefile.PL b/dist/PathTools/Makefile.PL
+index 1b21de4..f562cb2 100644
+--- a/dist/PathTools/Makefile.PL
 b/dist/PathTools/Makefile.PL
+@@ -1,6 +1,3 @@
+-
+-BEGIN { @INC = grep {!/blib/} @INC }
+-
+ require 5.005;
+ use ExtUtils::MakeMaker;
+ WriteMakefile
+--
+1.9.1
+
diff --git a/meta/recipes-devtools/perl/perl_5.22.0.bb 
b/meta/recipes-devtools/perl/perl_5.22.0.bb
index 050a98c..7f78998 100644
--- a/meta/recipes-devtools/perl/perl_5.22.0.bb
+++ b/meta/recipes-devtools/perl/perl_5.22.0.bb
@@ -61,6 +61,7 @@ SRC_URI += " \
  file://t-run-switches.t-perl5-perl.patch \
  file://ext-ODBM_File-hints-linux.pl-link-libgdbm_compat.patch \
  file://ext-ODBM_File-t-odbm.t-fix-the-path-of-dbmt_common.p.patch \
+file://perl-PathTools-don-t-filter-out-blib-from-INC.patch \
  "

  # Fix test case issues
--
1.9.1

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





--
Best Reagrds,
Roy | RongQing Li
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH][resend][v2] dhcp: make dhclient to get configuration for other programs

[Rongqing Li]

ping

-Roy

On 2015年07月17日 14:31, rongqing...@windriver.com wrote:

From: Li Wang 

Make dhclient to run /etc/dhcp/dhclient.d/*.sh, and get the configuration
for ntp, nis or other programes

These codes are from redhat rpm package.

Signed-off-by: Li Wang 
Signed-off-by: Roy Li 
---
  .../dhcp/dhcp/dhcp-add-exec-script-function.patch  | 101 +
  meta/recipes-connectivity/dhcp/dhcp_4.3.2.bb   |   1 +
  meta/recipes-connectivity/dhcp/files/dhclient.conf |   1 +
  3 files changed, 103 insertions(+)
  create mode 100644 
meta/recipes-connectivity/dhcp/dhcp/dhcp-add-exec-script-function.patch

diff --git 
a/meta/recipes-connectivity/dhcp/dhcp/dhcp-add-exec-script-function.patch 
b/meta/recipes-connectivity/dhcp/dhcp/dhcp-add-exec-script-function.patch
new file mode 100644
index 000..73b3ce4
--- /dev/null
+++ b/meta/recipes-connectivity/dhcp/dhcp/dhcp-add-exec-script-function.patch
@@ -0,0 +1,101 @@
+[PATCH] dhcp: add exec script function
+
+Upstream-Statue: Pending
+
+Make dhclient to run /etc/dhcp/dhclient.d/*.sh, and get the configuration
+for ntp, nis or other programes
+
+These codes are from redhat rpm packages.
+
+Signed-off-by: Li Wang 
+Signed-off-by: Roy Li 
+---
+ client/scripts/linux | 25 -
+ 1 file changed, 24 insertions(+), 1 deletion(-)
+
+diff --git a/client/scripts/linux b/client/scripts/linux
+index 232a0aa..bdb5e22 100755
+--- a/client/scripts/linux
 b/client/scripts/linux
+@@ -24,6 +24,8 @@
+
+ # 'ip' just looks too weird.  /sbin/ip looks less weird.
+ ip=/sbin/ip
++ETCDIR="/etc/dhcp"
++export SAVEDIR=/var/lib/dhclient
+
+ make_resolv_conf() {
+   if [ x"$new_domain_name_servers" != x ]; then
+@@ -80,6 +82,20 @@ exit_with_hooks() {
+   exit $exit_status
+ }
+
++execute_client_side_configuration_scripts() {
++# execute any additional client side configuration scripts we have
++if [ "${1}" == "config" ] || [ "${1}" == "restore" ]; then
++for f in ${ETCDIR}/dhclient.d/*.sh ; do
++if [ -x ${f} ]; then
++subsystem="${f%.sh}"
++subsystem="${subsystem##*/}"
++. ${f}
++"${subsystem}_${1}"
++fi
++done
++fi
++}
++
+ # Invoke the local dhcp client enter hooks, if they exist.
+ if [ -f /etc/dhclient-enter-hooks ]; then
+   exit_status=0
+@@ -198,11 +214,14 @@ if [ x$reason = xBOUND ] || [ x$reason = xRENEW ] || \
+ ${ip} -4 route add ${alias_ip_address} dev ${interface} >/dev/null 2>&1
+   fi
+   make_resolv_conf
++  execute_client_side_configuration_scripts "config"
+   exit_with_hooks 0
+ fi
+
+ if [ x$reason = xEXPIRE ] || [ x$reason = xFAIL ] || [ x$reason = xRELEASE ] \
+|| [ x$reason = xSTOP ]; then
++  execute_client_side_configuration_scripts "restore"
++
+   if [ x$alias_ip_address != x ]; then
+ # Turn off alias interface.
+ ${ip} -4 addr flush dev ${interface} label ${interface}:0
+@@ -281,7 +300,7 @@ if [ x$reason = xBOUND6 ] ; then
+
+   # Check for nameserver options.
+   make_resolv_conf
+-
++  execute_client_side_configuration_scripts "config"
+   exit_with_hooks 0
+ fi
+
+@@ -299,6 +318,7 @@ if [ x$reason = xRENEW6 ] || [ x$reason = xREBIND6 ] ; then
+ make_resolv_conf
+   fi
+
++  execute_client_side_configuration_scripts "config"
+   exit_with_hooks 0
+ fi
+
+@@ -310,6 +330,7 @@ if [ x$reason = xDEPREF6 ] ; then
+   ${ip} -f inet6 addr change ${new_ip6_address}/${new_ip6_prefixlen} \
+dev ${interface} scope global preferred_lft 0
+
++  execute_client_side_configuration_scripts "config"
+   exit_with_hooks 0
+ fi
+
+@@ -318,6 +339,8 @@ if [ x$reason = xEXPIRE6 -o x$reason = xRELEASE6 -o 
x$reason = xSTOP6 ] ; then
+ exit_with_hooks 2;
+   fi
+
++  execute_client_side_configuration_scripts "restore"
++
+   ${ip} -f inet6 addr del ${old_ip6_address}/${old_ip6_prefixlen} \
+   dev ${interface}
+
+--
+1.9.1
+
diff --git a/meta/recipes-connectivity/dhcp/dhcp_4.3.2.bb 
b/meta/recipes-connectivity/dhcp/dhcp_4.3.2.bb
index b4a05fc..a73d31f 100644
--- a/meta/recipes-connectivity/dhcp/dhcp_4.3.2.bb
+++ b/meta/recipes-connectivity/dhcp/dhcp_4.3.2.bb
@@ -6,6 +6,7 @@ SRC_URI += "file://dhcp-3.0.3-dhclient-dbus.patch;striplevel=0 \
  file://fixsepbuild.patch \
  file://dhclient-script-drop-resolv.conf.dhclient.patch \
  file://replace-ifconfig-route.patch \
+file://dhcp-add-exec-script-function.patch \
 "

  SRC_URI[md5sum] = "5a284875dd2c12ddd388416d69156a67"
diff --git a/meta/recipes-connectivity/dhcp/files/dhclient.conf 
b/meta/recipes-connectivity/dhcp/files/dhclient.conf
index 0e6dcf9..0f7d42f 100644
--- a/meta/recipes-connectivity/dhcp/files/dhclient.conf
+++ b/meta/recipes-connectivity/dhcp/files/dhclient.conf
@@ -17,6 +17,7 @@
  #supersede domain-name "fugue.com home.vix.com";
  #prepend domain-name-servers 127.0.0.1;
  request subnet-mask, broadcast-address, time-offset, routers,
+   nis-domain, nis-servers, domain-search, ntp-s

Re: [OE-core] [PATCH][resend] elfutils: fix stack usage warning

[Rongqing Li]

ping

-R

On 2015年07月13日 09:52, rongqing...@windriver.com wrote:

From: Roy Li 

Signed-off-by: Roy Li 
---
  .../0001-fix-a-stack-usage-warning.patch   | 28 ++
  meta/recipes-devtools/elfutils/elfutils_0.163.bb   |  1 +
  2 files changed, 29 insertions(+)
  create mode 100644 
meta/recipes-devtools/elfutils/elfutils-0.163/0001-fix-a-stack-usage-warning.patch

diff --git 
a/meta/recipes-devtools/elfutils/elfutils-0.163/0001-fix-a-stack-usage-warning.patch
 
b/meta/recipes-devtools/elfutils/elfutils-0.163/0001-fix-a-stack-usage-warning.patch
new file mode 100644
index 000..6923bf7
--- /dev/null
+++ 
b/meta/recipes-devtools/elfutils/elfutils-0.163/0001-fix-a-stack-usage-warning.patch
@@ -0,0 +1,28 @@
+[PATCH] fix a stack-usage warning
+
+Upstream-Status: Pending
+
+not use a variable to as a array size, otherwise the warning to error that
+stack usage might be unbounded [-Werror=stack-usage=] will happen
+
+Signed-off-by: Roy Li 
+---
+ backends/ppc_initreg.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/backends/ppc_initreg.c b/backends/ppc_initreg.c
+index 64f5379..52dde3e 100644
+--- a/backends/ppc_initreg.c
 b/backends/ppc_initreg.c
+@@ -93,7 +93,7 @@ ppc_set_initial_registers_tid (pid_t tid __attribute__ 
((unused)),
+   return false;
+ }
+   const size_t gprs = sizeof (user_regs.r.gpr) / sizeof (*user_regs.r.gpr);
+-  Dwarf_Word dwarf_regs[gprs];
++  Dwarf_Word dwarf_regs[sizeof (user_regs.r.gpr) / sizeof (*user_regs.r.gpr)];
+   for (unsigned gpr = 0; gpr < gprs; gpr++)
+ dwarf_regs[gpr] = user_regs.r.gpr[gpr];
+   if (! setfunc (0, gprs, dwarf_regs, arg))
+--
+1.9.1
+
diff --git a/meta/recipes-devtools/elfutils/elfutils_0.163.bb 
b/meta/recipes-devtools/elfutils/elfutils_0.163.bb
index c4fdabd..e391813 100644
--- a/meta/recipes-devtools/elfutils/elfutils_0.163.bb
+++ b/meta/recipes-devtools/elfutils/elfutils_0.163.bb
@@ -17,6 +17,7 @@ SRC_URI += "\
  file://fixheadercheck.patch \
  
file://0001-elf_getarsym-Silence-Werror-maybe-uninitialized-fals.patch \
  file://0001-remove-the-unneed-checking.patch \
+file://0001-fix-a-stack-usage-warning.patch \
  "

  # pick the patch from debian



--
Best Reagrds,
Roy | RongQing Li
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] Weekend build status (master, fido, dizzy and -next)

[Flanagan, Elizabeth]

On 26 July 2015 at 22:08, Richard Purdie
 wrote:
> On Sun, 2015-07-26 at 13:11 -0700, akuster808 wrote:
>> On 07/26/2015 09:14 AM, Richard Purdie wrote:
>> > Dizzy - Last Build showed ? failures:
>> > =
>> >
>> > Managed to push most gcc5 fixes to the branch which has things building
>> > much better than the first time.
>> >
>> > https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/97/steps/Running%20oe-selftest/logs/stdio
>> > two different selftest sanity failures
>>
>> Why does the log show 1.8+snapshot? I would have expected 1.7+.
>
> That autobuilder appears to be running a buildtools-tarball which was
> built using 1.8 and installed in /opt/xxx. The build does appear to be a
> 1.7 build and those paths are safe to ignore.
>
>> > https://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/407/steps/Running%20Sanity%20Tests/logs/stdio
>> > Systemd login prompt failure issue (Ross also has open bug for this in
>> > master)
>> >
>> > https://autobuilder.yoctoproject.org/main/builders/nightly-non-gpl3/builds/413/steps/CheckForGPLv3/logs/stdio
>> > GPLv3 check failing?
>>
>> Was this run for 1.7.2 ? I don't see any license changes in the 1.7.3
>> patches.
>
> Beth?

The nightly-non-gpl3 target was run for 1.7.2. However the
"CheckForGPLv3" build step is new and is there to catch exactly this.
So something is wrong with the non-gplv3 builds for 1.7.x that this
caught.

-b

>
>> I am  confused by the logs. It references
>> "TERMINFO_DIRS=/opt/poky/1.8+snapshot" and other places is references
>> 'master'. is this representative of Dizzy?
>
> See above, same issue, its from buildtools-tarball the system is using.
>
>> >
>> > https://autobuilder.yoctoproject.org/main/builders/nightly-mips64/builds/60/steps/Running%20Sanity%20Tests/logs/stdio
>> > mips64 sanity test failed - do we support this on dizzy?
>>
>> Don't think so. It was not tested in the previews point releases either.
>>
>> >
>> > https://autobuilder.yoctoproject.org/main/builders/nightly-arm64/builds/68
>> > arm64 build failed - do we support this on dizzy? (machine doesn't exist
>> > so no?)
>>
>> Arm64 is not support in Dizzy.
>
> Agreed, Beth will disable these to make things look a little cleaner.
> Which just leaves the other issues :/.
>
> Cheers,
>
> Richard
>



-- 
Elizabeth Flanagan
Yocto Project
Build and Release
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] Weekend build status (master, fido, dizzy and -next)

[Richard Purdie]

On Sun, 2015-07-26 at 13:11 -0700, akuster808 wrote:
> On 07/26/2015 09:14 AM, Richard Purdie wrote:
> > Dizzy - Last Build showed ? failures:
> > =
> >
> > Managed to push most gcc5 fixes to the branch which has things building
> > much better than the first time.
> >
> > https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/97/steps/Running%20oe-selftest/logs/stdio
> > two different selftest sanity failures
> 
> Why does the log show 1.8+snapshot? I would have expected 1.7+.

That autobuilder appears to be running a buildtools-tarball which was
built using 1.8 and installed in /opt/xxx. The build does appear to be a
1.7 build and those paths are safe to ignore.

> > https://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/407/steps/Running%20Sanity%20Tests/logs/stdio
> > Systemd login prompt failure issue (Ross also has open bug for this in
> > master)
> >
> > https://autobuilder.yoctoproject.org/main/builders/nightly-non-gpl3/builds/413/steps/CheckForGPLv3/logs/stdio
> > GPLv3 check failing?
> 
> Was this run for 1.7.2 ? I don't see any license changes in the 1.7.3 
> patches.

Beth?

> I am  confused by the logs. It references 
> "TERMINFO_DIRS=/opt/poky/1.8+snapshot" and other places is references 
> 'master'. is this representative of Dizzy?

See above, same issue, its from buildtools-tarball the system is using.

> >
> > https://autobuilder.yoctoproject.org/main/builders/nightly-mips64/builds/60/steps/Running%20Sanity%20Tests/logs/stdio
> > mips64 sanity test failed - do we support this on dizzy?
> 
> Don't think so. It was not tested in the previews point releases either.
> 
> >
> > https://autobuilder.yoctoproject.org/main/builders/nightly-arm64/builds/68
> > arm64 build failed - do we support this on dizzy? (machine doesn't exist
> > so no?)
> 
> Arm64 is not support in Dizzy.

Agreed, Beth will disable these to make things look a little cleaner.
Which just leaves the other issues :/.

Cheers,

Richard

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

Re: [OE-core] Weekend build status (master, fido, dizzy and -next)

[Flanagan, Elizabeth]

On 26 July 2015 at 21:11, akuster808  wrote:
>
>
> On 07/26/2015 09:14 AM, Richard Purdie wrote:
>>
>> Over the weekend I've tried to establish where we're at with the various
>> branches. I've run builds of master, fido and dizzy. I have fixed
>> various things:
>>
>> * dizzy gcc5 backports
>> * mysterious updated-rc.d license file missing failure
>> * linux-yocto 4.1 perf issues
>>
>> Despite these, sadly the builds were not very successful :(.
>>
>> Master - Last build showed 4 failures:
>> ==
>>
>>
>> https://autobuilder.yoctoproject.org/main/builders/build-appliance/builds/402/steps/BuildImages/logs/stdio
>> nativesdk-update-rc.d missing, fix pushed
>>
>>
>> https://autobuilder.yoctoproject.org/main/builders/nightly-intel-gpl/builds/400/steps/BuildImages/logs/stdio
>>
>> https://autobuilder.yoctoproject.org/main/builders/nightly-intel-gpl/builds/400/steps/BuildImages_1/logs/stdio
>> meta-intel linux-yocto issue (fix pending merging)
>> nativesdk-update-rc.d missing, fix pushed
>>
>>
>> https://autobuilder.yoctoproject.org/main/builders/nightly-mips/builds/413/steps/Running%20Sanity%20Tests/logs/stdio
>> mips sanity test failure, unknown cause
>>
>>
>> https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/96/steps/Running%20oe-selftest/logs/stdio
>> 3 failures from runqemu issues (Paul working on this)
>> 2 failures from meta-intel linux-yocto issues (fix pending merging)
>>
>> Fido - Last build showed 5 failures:
>> 
>>
>>
>> https://autobuilder.yoctoproject.org/main/builders/nightly-arm/builds/409/steps/Running%20Sanity%20Tests/logs/stdio
>> qemuarm kernel panic during sanity tests
>>
>>
>> https://autobuilder.yoctoproject.org/main/builders/nightly-deb/builds/394/steps/BuildImages/logs/stdio
>>
>> https://autobuilder.yoctoproject.org/main/builders/nightly-deb-non-deb/builds/68/steps/BuildImages/logs/stdio
>> looks like
>> http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=ba07a69f3dc8fb798e372130bf665d059fed9d42,
>> backport needed?
>>
>>
>> https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/94/steps/Running%20oe-selftest/logs/stdio
>> "Only one copy of bitbake should be run against a build directory" -
>> Bitbake shutdown race. Fix in master but risky backport, torn on this.
>>
>>
>> https://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/405/steps/Running%20Sanity%20Tests/logs/stdio
>> xorg/vnc systemd issue - Ross has open bug for master
>>
>> Dizzy - Last Build showed ? failures:
>> =
>>
>> Managed to push most gcc5 fixes to the branch which has things building
>> much better than the first time.
>>
>>
>> https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/97/steps/Running%20oe-selftest/logs/stdio
>> two different selftest sanity failures
>
>
> Why does the log show 1.8+snapshot? I would have expected 1.7+.
>
>
>>
>>
>> https://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/407/steps/Running%20Sanity%20Tests/logs/stdio
>> Systemd login prompt failure issue (Ross also has open bug for this in
>> master)
>>
>>
>> https://autobuilder.yoctoproject.org/main/builders/nightly-non-gpl3/builds/413/steps/CheckForGPLv3/logs/stdio
>> GPLv3 check failing?
>
>
> Was this run for 1.7.2 ? I don't see any license changes in the 1.7.3
> patches.
>

No, the check was not run. My guess is that it was broken in 1.7.2.

> I am  confused by the logs. It references
> "TERMINFO_DIRS=/opt/poky/1.8+snapshot" and other places is references
> 'master'. is this representative of Dizzy?

We use the buildtools tarball on the builders. That is probably where
that is coming from.

>
>>
>>
>> https://autobuilder.yoctoproject.org/main/builders/nightly-mips64/builds/60/steps/Running%20Sanity%20Tests/logs/stdio
>> mips64 sanity test failed - do we support this on dizzy?
>
>
> Don't think so. It was not tested in the previews point releases either.
>
>>
>> https://autobuilder.yoctoproject.org/main/builders/nightly-arm64/builds/68
>> arm64 build failed - do we support this on dizzy? (machine doesn't exist
>> so no?)
>
>
> Arm64 is not support in Dizzy.
>
> - Armin
>>
>>
>> grub-efi gcc5 issue:
>> http://errors.yoctoproject.org/Errors/Details/13781/
>>
>> [build is still ongoing so this is not a complete list]
>>
>> So all things considered we're not in a good way for the point releases
>> or M2 :(.
>>
>> With regard to master-next, my experimental SDK toolchain fixes are
>> causing issues on armeabi and x32. Whenever I add in Chris' recipetool
>> changes, the selftest gives odd results too :(. Build is also ongoing.
>>
>> Cheers,
>>
>> Richard
>>
>>
>



-- 
Elizabeth Flanagan
Yocto Project
Build and Release
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] Weekend build status (master, fido, dizzy and -next)

[akuster808]

On 07/26/2015 09:14 AM, Richard Purdie wrote:

Over the weekend I've tried to establish where we're at with the various
branches. I've run builds of master, fido and dizzy. I have fixed
various things:

* dizzy gcc5 backports
* mysterious updated-rc.d license file missing failure
* linux-yocto 4.1 perf issues

Despite these, sadly the builds were not very successful :(.

Master - Last build showed 4 failures:
==

https://autobuilder.yoctoproject.org/main/builders/build-appliance/builds/402/steps/BuildImages/logs/stdio
nativesdk-update-rc.d missing, fix pushed

https://autobuilder.yoctoproject.org/main/builders/nightly-intel-gpl/builds/400/steps/BuildImages/logs/stdio
https://autobuilder.yoctoproject.org/main/builders/nightly-intel-gpl/builds/400/steps/BuildImages_1/logs/stdio
meta-intel linux-yocto issue (fix pending merging)
nativesdk-update-rc.d missing, fix pushed

https://autobuilder.yoctoproject.org/main/builders/nightly-mips/builds/413/steps/Running%20Sanity%20Tests/logs/stdio
mips sanity test failure, unknown cause

https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/96/steps/Running%20oe-selftest/logs/stdio
3 failures from runqemu issues (Paul working on this)
2 failures from meta-intel linux-yocto issues (fix pending merging)

Fido - Last build showed 5 failures:


https://autobuilder.yoctoproject.org/main/builders/nightly-arm/builds/409/steps/Running%20Sanity%20Tests/logs/stdio
qemuarm kernel panic during sanity tests

https://autobuilder.yoctoproject.org/main/builders/nightly-deb/builds/394/steps/BuildImages/logs/stdio
https://autobuilder.yoctoproject.org/main/builders/nightly-deb-non-deb/builds/68/steps/BuildImages/logs/stdio
looks like 
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=ba07a69f3dc8fb798e372130bf665d059fed9d42,
 backport needed?

https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/94/steps/Running%20oe-selftest/logs/stdio
"Only one copy of bitbake should be run against a build directory" -
Bitbake shutdown race. Fix in master but risky backport, torn on this.

https://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/405/steps/Running%20Sanity%20Tests/logs/stdio
xorg/vnc systemd issue - Ross has open bug for master

Dizzy - Last Build showed ? failures:
=

Managed to push most gcc5 fixes to the branch which has things building
much better than the first time.

https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/97/steps/Running%20oe-selftest/logs/stdio
two different selftest sanity failures


Why does the log show 1.8+snapshot? I would have expected 1.7+.




https://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/407/steps/Running%20Sanity%20Tests/logs/stdio
Systemd login prompt failure issue (Ross also has open bug for this in
master)

https://autobuilder.yoctoproject.org/main/builders/nightly-non-gpl3/builds/413/steps/CheckForGPLv3/logs/stdio
GPLv3 check failing?


Was this run for 1.7.2 ? I don't see any license changes in the 1.7.3 
patches.


I am  confused by the logs. It references 
"TERMINFO_DIRS=/opt/poky/1.8+snapshot" and other places is references 
'master'. is this representative of Dizzy?




https://autobuilder.yoctoproject.org/main/builders/nightly-mips64/builds/60/steps/Running%20Sanity%20Tests/logs/stdio
mips64 sanity test failed - do we support this on dizzy?


Don't think so. It was not tested in the previews point releases either.



https://autobuilder.yoctoproject.org/main/builders/nightly-arm64/builds/68
arm64 build failed - do we support this on dizzy? (machine doesn't exist
so no?)


Arm64 is not support in Dizzy.

- Armin


grub-efi gcc5 issue:
http://errors.yoctoproject.org/Errors/Details/13781/

[build is still ongoing so this is not a complete list]

So all things considered we're not in a good way for the point releases
or M2 :(.

With regard to master-next, my experimental SDK toolchain fixes are
causing issues on armeabi and x32. Whenever I add in Chris' recipetool
changes, the selftest gives odd results too :(. Build is also ongoing.

Cheers,

Richard



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

Re: [OE-core] Weekend build status (master, fido, dizzy and -next)

[Flanagan, Elizabeth]

On 26 July 2015 at 17:14, Richard Purdie
 wrote:
> Over the weekend I've tried to establish where we're at with the various
> branches. I've run builds of master, fido and dizzy. I have fixed
> various things:
>
> * dizzy gcc5 backports
> * mysterious updated-rc.d license file missing failure
> * linux-yocto 4.1 perf issues
>
> Despite these, sadly the builds were not very successful :(.
>
> Master - Last build showed 4 failures:
> ==
>
> https://autobuilder.yoctoproject.org/main/builders/build-appliance/builds/402/steps/BuildImages/logs/stdio
> nativesdk-update-rc.d missing, fix pushed
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-intel-gpl/builds/400/steps/BuildImages/logs/stdio
> https://autobuilder.yoctoproject.org/main/builders/nightly-intel-gpl/builds/400/steps/BuildImages_1/logs/stdio
> meta-intel linux-yocto issue (fix pending merging)
> nativesdk-update-rc.d missing, fix pushed
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-mips/builds/413/steps/Running%20Sanity%20Tests/logs/stdio
> mips sanity test failure, unknown cause
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/96/steps/Running%20oe-selftest/logs/stdio
> 3 failures from runqemu issues (Paul working on this)
> 2 failures from meta-intel linux-yocto issues (fix pending merging)
>
> Fido - Last build showed 5 failures:
> 
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-arm/builds/409/steps/Running%20Sanity%20Tests/logs/stdio
> qemuarm kernel panic during sanity tests
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-deb/builds/394/steps/BuildImages/logs/stdio
> https://autobuilder.yoctoproject.org/main/builders/nightly-deb-non-deb/builds/68/steps/BuildImages/logs/stdio
> looks like 
> http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=ba07a69f3dc8fb798e372130bf665d059fed9d42,
>  backport needed?
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/94/steps/Running%20oe-selftest/logs/stdio
> "Only one copy of bitbake should be run against a build directory" -
> Bitbake shutdown race. Fix in master but risky backport, torn on this.
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/405/steps/Running%20Sanity%20Tests/logs/stdio
> xorg/vnc systemd issue - Ross has open bug for master
>
> Dizzy - Last Build showed ? failures:
> =
>
> Managed to push most gcc5 fixes to the branch which has things building
> much better than the first time.
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/97/steps/Running%20oe-selftest/logs/stdio
> two different selftest sanity failures
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/407/steps/Running%20Sanity%20Tests/logs/stdio
> Systemd login prompt failure issue (Ross also has open bug for this in
> master)
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-non-gpl3/builds/413/steps/CheckForGPLv3/logs/stdio
> GPLv3 check failing?
>

This shows that we have GPLv3+ within the license.manifest which is a
problem. I'll take a look at this tomorrow as it's concerning that
GPLv3 packages are getting in.

LICENSE: GPLv3+ BSD-2-Clause
LICENSE: GPLv2 LGPLv3
LICENSE: GPLv3+

> https://autobuilder.yoctoproject.org/main/builders/nightly-mips64/builds/60/steps/Running%20Sanity%20Tests/logs/stdio
> mips64 sanity test failed - do we support this on dizzy?
>

No, I don't believe so. I'll toss a skip patch into the AB to make
sure we don't hit this again.

> https://autobuilder.yoctoproject.org/main/builders/nightly-arm64/builds/68
> arm64 build failed - do we support this on dizzy? (machine doesn't exist
> so no?)

Same, don't believe this is in dizzy. Just fido and master.

>
> grub-efi gcc5 issue:
> http://errors.yoctoproject.org/Errors/Details/13781/
>
> [build is still ongoing so this is not a complete list]
>
> So all things considered we're not in a good way for the point releases
> or M2 :(.
>
> With regard to master-next, my experimental SDK toolchain fixes are
> causing issues on armeabi and x32. Whenever I add in Chris' recipetool
> changes, the selftest gives odd results too :(. Build is also ongoing.
>
> Cheers,
>
> Richard
>
>

-b

-- 
Elizabeth Flanagan
Yocto Project
Build and Release
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] Weekend build status (master, fido, dizzy and -next)

[Richard Purdie]

Over the weekend I've tried to establish where we're at with the various
branches. I've run builds of master, fido and dizzy. I have fixed
various things:

* dizzy gcc5 backports
* mysterious updated-rc.d license file missing failure
* linux-yocto 4.1 perf issues

Despite these, sadly the builds were not very successful :(.

Master - Last build showed 4 failures:
==

https://autobuilder.yoctoproject.org/main/builders/build-appliance/builds/402/steps/BuildImages/logs/stdio
nativesdk-update-rc.d missing, fix pushed

https://autobuilder.yoctoproject.org/main/builders/nightly-intel-gpl/builds/400/steps/BuildImages/logs/stdio
https://autobuilder.yoctoproject.org/main/builders/nightly-intel-gpl/builds/400/steps/BuildImages_1/logs/stdio
meta-intel linux-yocto issue (fix pending merging)
nativesdk-update-rc.d missing, fix pushed

https://autobuilder.yoctoproject.org/main/builders/nightly-mips/builds/413/steps/Running%20Sanity%20Tests/logs/stdio
mips sanity test failure, unknown cause

https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/96/steps/Running%20oe-selftest/logs/stdio
3 failures from runqemu issues (Paul working on this)
2 failures from meta-intel linux-yocto issues (fix pending merging)

Fido - Last build showed 5 failures:


https://autobuilder.yoctoproject.org/main/builders/nightly-arm/builds/409/steps/Running%20Sanity%20Tests/logs/stdio
qemuarm kernel panic during sanity tests

https://autobuilder.yoctoproject.org/main/builders/nightly-deb/builds/394/steps/BuildImages/logs/stdio
https://autobuilder.yoctoproject.org/main/builders/nightly-deb-non-deb/builds/68/steps/BuildImages/logs/stdio
looks like 
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=ba07a69f3dc8fb798e372130bf665d059fed9d42,
 backport needed?

https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/94/steps/Running%20oe-selftest/logs/stdio
"Only one copy of bitbake should be run against a build directory" -
Bitbake shutdown race. Fix in master but risky backport, torn on this.

https://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/405/steps/Running%20Sanity%20Tests/logs/stdio
xorg/vnc systemd issue - Ross has open bug for master

Dizzy - Last Build showed ? failures:
=

Managed to push most gcc5 fixes to the branch which has things building
much better than the first time.

https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/97/steps/Running%20oe-selftest/logs/stdio
two different selftest sanity failures

https://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/407/steps/Running%20Sanity%20Tests/logs/stdio
Systemd login prompt failure issue (Ross also has open bug for this in
master)

https://autobuilder.yoctoproject.org/main/builders/nightly-non-gpl3/builds/413/steps/CheckForGPLv3/logs/stdio
GPLv3 check failing?

https://autobuilder.yoctoproject.org/main/builders/nightly-mips64/builds/60/steps/Running%20Sanity%20Tests/logs/stdio
mips64 sanity test failed - do we support this on dizzy?

https://autobuilder.yoctoproject.org/main/builders/nightly-arm64/builds/68
arm64 build failed - do we support this on dizzy? (machine doesn't exist
so no?)

grub-efi gcc5 issue:
http://errors.yoctoproject.org/Errors/Details/13781/

[build is still ongoing so this is not a complete list]

So all things considered we're not in a good way for the point releases
or M2 :(.

With regard to master-next, my experimental SDK toolchain fixes are
causing issues on armeabi and x32. Whenever I add in Chris' recipetool
changes, the selftest gives odd results too :(. Build is also ongoing.

Cheers,

Richard


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