Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] coreutils-native and gettext fixes
Date: Tue, 22 Mar 2011 11:21:50 -0700	[thread overview]
Message-ID: <cover.1300817337.git.tom_rini@mentor.com> (raw)

They following changes do two things.  First up, this re-syncs
coreutils-native with the changes I just made in openembedded.master
to opt out of gmp-native rather than DEPEND on it (oe.master had neither
previously).  The second change was that in testing the above I ran into
gettext.bbclass + BBCLASSEXTEND breakage that I had fixed in oe.master
previously.  I've extended what I did slightly to also cover crosssdk
here.  After talking with Khem there's further cleanups that we can do
but are separate.

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

Thanks,
    Tom Rini <tom_rini@mentor.com>
---


Tom Rini (2):
  coreutils: Switch to disabling gmp support
  gettext.bbclass: Fix cases where we lost DEPENDS_GETTEXT

 meta/classes/gettext.bbclass                 |    8 ++++++--
 meta/recipes-core/coreutils/coreutils_8.9.bb |    6 ++++--
 2 files changed, 10 insertions(+), 4 deletions(-)




             reply	other threads:[~2011-03-22 18:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-22 18:21 Tom Rini [this message]
2011-03-22 18:21 ` [PATCH 1/2] coreutils: Switch to disabling gmp support Tom Rini
2011-03-22 18:32   ` Khem Raj
2011-03-22 18:21 ` [PATCH 2/2] gettext.bbclass: Fix cases where we lost DEPENDS_GETTEXT Tom Rini
2011-03-22 18:33   ` Khem Raj
2011-03-23 16:39 ` [PATCH 0/2] coreutils-native and gettext fixes Richard Purdie

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.1300817337.git.tom_rini@mentor.com \
    --to=tom_rini@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