Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Jussi Kukkonen <jussi.kukkonen@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] Fix GLib 2.48.1 upgrade breakage
Date: Tue, 17 May 2016 15:17:44 +0300	[thread overview]
Message-ID: <cover.1463486899.git.jussi.kukkonen@intel.com> (raw)
In-Reply-To: <1463470541.4578.7.camel@linuxfoundation.org>

Two patches to fix configure failures that resulted from the glib-2.0
2.48.1 update. In both cases the AM_GLIB_GNU_GETTEXT macro is updated to
match the one provided by glib (the change is that the macro is now
marked deprecated).

I've pushed these on top of the original branch since these patches
should only be used with new GLib.

 - Jussi


The following changes since commit cb405da51da0413d5ac5999330a4e49cb7be262f:

  weston: Upgrade 1.9.0 -> 1.10.0 (2016-05-16 14:20:26 +0300)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib jku/upgrades
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=jku/upgrades

Jussi Kukkonen (2):
  gnome-doc-utils: Update AM_GLIB_GNU_GETTEXT macro
  pkgconfig: Update AM_GLIB_GNU_GETTEXT macro

 ...t.m4-Update-AM_GLIB_GNU_GETTEXT-to-match-.patch | 41 ++++++++++++++++++++++
 meta/recipes-devtools/pkgconfig/pkgconfig_git.bb   |  1 +
 ...t.m4-Update-AM_GLIB_GNU_GETTEXT-to-match-.patch | 40 +++++++++++++++++++++
 .../recipes-gnome/gnome/gnome-doc-utils_0.20.10.bb |  1 +
 4 files changed, 83 insertions(+)
 create mode 100644 meta/recipes-devtools/pkgconfig/pkgconfig/0001-glib-gettext.m4-Update-AM_GLIB_GNU_GETTEXT-to-match-.patch
 create mode 100644 meta/recipes-gnome/gnome/gnome-doc-utils/0001-glib-gettext.m4-Update-AM_GLIB_GNU_GETTEXT-to-match-.patch

-- 
2.1.4



  parent reply	other threads:[~2016-05-17 12:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-16 13:22 [PATCH 00/13] wayland V2 and misc upgrades Jussi Kukkonen
2016-05-16 13:22 ` [PATCH 01/13] glib-2.0: Upgrade 2.46.2 -> 2.48.1 Jussi Kukkonen
2016-05-17  7:35   ` Richard Purdie
2016-05-17 10:35     ` Jussi Kukkonen
2016-05-17 12:17     ` Jussi Kukkonen [this message]
2016-05-17 12:18       ` [PATCH 1/2] gnome-doc-utils: Update AM_GLIB_GNU_GETTEXT macro Jussi Kukkonen
2016-05-17 12:18       ` [PATCH 2/2] pkgconfig: " Jussi Kukkonen
2016-05-16 13:22 ` [PATCH 02/13] glib-networking: Upgrade 2.46.1 -> 2.48.2 Jussi Kukkonen
2016-05-16 13:22 ` [PATCH 03/13] pango: Upgrade 1.38.1 -> 1.40.1 Jussi Kukkonen
2016-05-16 13:22 ` [PATCH 04/13] gdk-pixbuf: Upgrade 2.32.3 -> 2.34.0 Jussi Kukkonen
2016-05-16 13:22 ` [PATCH 05/13] gsettings-desktop-schemas: Upgrade 3.19.3 -> 3.20.0 Jussi Kukkonen
2016-05-16 13:22 ` [PATCH 06/13] inputproto: Upgrade 2.3.1 -> 2.3.2 Jussi Kukkonen
2016-05-16 13:22 ` [PATCH 07/13] json-glib: Upgrade 1.0.4 -> 1.2.0 Jussi Kukkonen
2016-05-16 13:22 ` [PATCH 08/13] libsoup-2.4: Upgrade 2.52.2 -> 2.54.1 Jussi Kukkonen
2016-05-16 13:22 ` [PATCH 09/13] expat: Upgrade 2.1.0 -> 2.1.1 Jussi Kukkonen
2016-05-16 13:22 ` [PATCH 10/13] xproto: Upgrade 7.0.28 -> 7.0.29 Jussi Kukkonen
2016-05-16 13:22 ` [PATCH 11/13] wayland: Upgrade 1.9.0 -> 1.10.0 Jussi Kukkonen
2016-05-16 13:22 ` [PATCH 12/13] wayland-protocols: Add recipe Jussi Kukkonen
2016-05-16 13:22 ` [PATCH 13/13] weston: Upgrade 1.9.0 -> 1.10.0 Jussi Kukkonen
2016-05-16 15:37   ` Denys Dmytriyenko

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=cover.1463486899.git.jussi.kukkonen@intel.com \
    --to=jussi.kukkonen@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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