From: Martin Jansa <martin.jansa@gmail.com>
To: Ross Burton <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [oe-commits] Ross Burton : glib-2.0: upgrade to latest stable, 2.34.1.
Date: Mon, 3 Dec 2012 16:13:31 +0100 [thread overview]
Message-ID: <20121203151331.GD3354@jama.jama.net> (raw)
In-Reply-To: <20121112132247.3BB7D102EC@opal>
[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]
On Mon, Nov 12, 2012 at 01:22:47PM +0000, git@git.openembedded.org wrote:
> Module: openembedded-core.git
> Branch: master
> Commit: ce5fcad59fff19dbffc2d7b49c0c8bf3701d17ed
> URL: http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=ce5fcad59fff19dbffc2d7b49c0c8bf3701d17ed
>
> Author: Ross Burton <ross.burton@intel.com>
> Date: Mon Nov 5 16:22:48 2012 +0000
>
> glib-2.0: upgrade to latest stable, 2.34.1.
>
> Also explicitly disable the test suite (as we can't run it), subsequently
> dropping 60_wait-longer-for-threads-to-die.patch and nodbus.patch.
>
> nolibelf.patch has been merged upstream, drop.
>
> Upstream has dropped the pre-generated man pages, to generate them again we'd
> need libxslt and the DocBook infrastructure. We can live without the man pages
> as those build-dependencies are non-trivial.
openembedded-core/meta/recipes-multimedia/gstreamer/gst-openmax_0.10.1.bb
is not compatible with this glib version
gstomx_base_filter.c:846:3: error: 'g_mutex_new' is deprecated
(declared at
/OE/jansa-test/shr-core/tmp-eglibc/sysroots/tuna/usr/include/glib-2.0/glib/deprecated/gthread.h:271)
[-Werror=deprecated-declarations]
Can you check that?
Cheers,
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next parent reply other threads:[~2012-12-03 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121112132247.3BB7D102EC@opal>
2012-12-03 15:13 ` Martin Jansa [this message]
2012-12-03 15:23 ` [oe-commits] Ross Burton : glib-2.0: upgrade to latest stable, 2.34.1 Burton, Ross
2012-12-04 7:36 ` Henning Heinold
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121203151331.GD3354@jama.jama.net \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox