From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] tclibc-uclibc, tclibc-eglibc: Prefer nativesdk-eglibc to provide libintl
Date: Tue, 04 Sep 2012 13:38:59 +0100 [thread overview]
Message-ID: <1346762339.30964.40.camel@ted> (raw)
In-Reply-To: <1346735783-30393-1-git-send-email-raj.khem@gmail.com>
On Mon, 2012-09-03 at 22:16 -0700, Khem Raj wrote:
> Currently gettext and eglibc compete to provide for libintl on
> nativesdk. So make choices to select eglibc nativesdk to provide
> for both eglibc as well as uclibc based systems.
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> meta/conf/distro/include/tclibc-eglibc.inc | 1 +
> meta/conf/distro/include/tclibc-uclibc.inc | 2 ++
> 2 files changed, 3 insertions(+)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-09-04 12:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 5:16 [PATCH] tclibc-uclibc, tclibc-eglibc: Prefer nativesdk-eglibc to provide libintl Khem Raj
2012-09-04 12:38 ` Richard Purdie [this message]
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=1346762339.30964.40.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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