Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: OE core <openembedded-core@lists.openembedded.org>
Cc: Chris Larson <chris_larson@mentor.com>
Subject: [PATCH 0/6] Fix recipes for uclibc and others
Date: Mon,  9 May 2011 11:40:25 -0700	[thread overview]
Message-ID: <cover.1304966147.git.raj.khem@gmail.com> (raw)

These patches address build failures when using uclibc
oe/patch.py fix is a backport from oe, we need to fix
BBFILES for oe-core since some class code expects it
to be first entry in BBFILES. gconf-dbus to dbus is needed
for SDKs to compile for angstrom

Pull URL: git://git.openembedded.org/openembedded-core-contrib
  Branch: kraj/misc-fixes
  Browse: http://git.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kraj/misc-fixes

Thanks,
    Khem Raj <raj.khem@gmail.com>
---


Khem Raj (6):
  recipes: Replace gconf-dbus with gconf
  conf/layer.conf: Use .= to append to BBPATH and =+ for BBFILES
  libgalago_0.5.2.bb: Fix compile for uclibc
  liburcu_0.5.4.bb: Let it build on uclibc targets
  lttng-ust_0.12.bb: Fix compilation on uclibc
  oe/patch.py: Remove series file during Clean()

 .../recipes-gnome/gnome/libgnomekbd_2.26.0.bb      |    2 +-
 meta/conf/layer.conf                               |   10 ++++-
 meta/lib/oe/patch.py                               |    1 +
 .../recipes-connectivity/galago/libgalago_0.5.2.bb |    4 ++
 meta/recipes-gnome/gnome/gnome-desktop.inc         |    2 +-
 meta/recipes-gnome/gthumb/gthumb_2.12.2.bb         |    2 +-
 meta/recipes-gnome/tasks/task-sdk-gmae.inc         |    2 +-
 .../lttng/lttng-ust/uclibc-sched_getcpu.patch      |   50 ++++++++++++++++++++
 meta/recipes-kernel/lttng/lttng-ust_0.12.bb        |    4 +-
 meta/recipes-support/libproxy/libproxy_0.4.6.bb    |    2 +-
 meta/recipes-support/liburcu/liburcu_0.5.4.bb      |    2 +-
 11 files changed, 73 insertions(+), 8 deletions(-)
 create mode 100644 meta/recipes-kernel/lttng/lttng-ust/uclibc-sched_getcpu.patch

-- 
1.7.4.1




             reply	other threads:[~2011-05-09 18:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-09 18:40 Khem Raj [this message]
2011-05-09 18:40 ` [PATCH 1/6] recipes: Replace gconf-dbus with gconf Khem Raj
2011-05-09 18:40 ` [PATCH 2/6] conf/layer.conf: Use .= to append to BBPATH and =+ for BBFILES Khem Raj
2011-05-09 18:40 ` [PATCH 3/6] libgalago_0.5.2.bb: Fix compile for uclibc Khem Raj
2011-05-09 18:40 ` [PATCH 4/6] liburcu_0.5.4.bb: Let it build on uclibc targets Khem Raj
2011-05-09 18:40 ` [PATCH 5/6] lttng-ust_0.12.bb: Fix compilation on uclibc Khem Raj
2011-05-09 18:40 ` [PATCH 6/6] oe/patch.py: Remove series file during Clean() Khem Raj
2011-05-10 17:54 ` [PATCH 0/6] Fix recipes for uclibc and others Saul Wold

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.1304966147.git.raj.khem@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=chris_larson@mentor.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