Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio@ossystems.com.br>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] Fix build failure of openjade using newer host
Date: Sat,  2 Jun 2012 14:34:56 -0300	[thread overview]
Message-ID: <cover.1338658338.git.otavio@ossystems.com.br> (raw)

This has been catch when building denzil on a Debian sid host; the fix
and build failure are documented on the patch. Please evaluate this
patch for inclusion on denzil 1.2.1 release as this will be catch by
users later.

The following changes since commit e3113827810e98eb1b012f0b280fb917199704c1:

  webkit-gtk: Use glib as unicode backend to avoid browser crash (2012-05-30 17:37:58 +0100)

are available in the git repository at:
  git://github.com/OSSystems/oe-core master
  https://github.com/OSSystems/oe-core/tree/HEAD

Otavio Salvador (1):
  openjade: autoreconf to fix building on newer host systems

 .../openjade/openjade-1.3.2/autoreconf.patch       |21657 ++++++++++++++++++++
 .../openjade/openjade-native_1.3.2.bb              |    3 +-
 2 files changed, 21659 insertions(+), 1 deletions(-)
 create mode 100644 meta/recipes-devtools/openjade/openjade-1.3.2/autoreconf.patch

-- 
1.7.2.5




             reply	other threads:[~2012-06-02 17:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-02 17:34 Otavio Salvador [this message]
2012-06-02 17:34 ` [PATCH 1/1] openjade: autoreconf to fix building on newer host systems Otavio Salvador
2012-06-11 17:34   ` Flanagan, Elizabeth
2012-06-12  0:23     ` Scott Garman
2012-06-12 13:14       ` Richard Purdie
2012-06-08 10:33 ` [PATCH 0/1] Fix build failure of openjade using newer host Richard Purdie
2012-06-08 11:52   ` Otavio Salvador
2012-06-12 13:13     ` Richard Purdie
2012-06-12 13:16       ` Otavio Salvador

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.1338658338.git.otavio@ossystems.com.br \
    --to=otavio@ossystems.com.br \
    --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