From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] classes, conf: Exclude native and nativesdk recipes from libc specific override
Date: Thu, 01 Dec 2011 12:53:05 +0000 [thread overview]
Message-ID: <1322743985.17484.122.camel@ted> (raw)
In-Reply-To: <1322708827-27449-1-git-send-email-raj.khem@gmail.com>
On Wed, 2011-11-30 at 19:07 -0800, Khem Raj wrote:
> Based on suggestions from RP
>
> libc-uclibc and libc-glibc overrides are for denoting
> system C library in use on the target and not for the
> host therefore we make sure that the override only takes
> effect for target recipes only.
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> meta/classes/native.bbclass | 3 +++
> meta/classes/nativesdk.bbclass | 3 +++
> meta/conf/distro/include/tclibc-eglibc.inc | 3 ++-
> meta/conf/distro/include/tclibc-uclibc.inc | 3 ++-
> 4 files changed, 10 insertions(+), 2 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-12-01 12:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 3:07 [PATCH] classes, conf: Exclude native and nativesdk recipes from libc specific override Khem Raj
2011-12-01 12:53 ` 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=1322743985.17484.122.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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