From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gcc-4.6: Some small performance tweaks
Date: Fri, 10 Feb 2012 13:40:54 +0000 [thread overview]
Message-ID: <1328881254.13434.10.camel@ted> (raw)
In-Reply-To: <CAMKF1soksEad4TP5upRjW2vG6_OjeQjyYTAL88PH_qgy9yyiug@mail.gmail.com>
On Thu, 2012-02-09 at 16:39 -0800, Khem Raj wrote:
> On Thu, Feb 9, 2012 at 4:06 PM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> >
> > +NATIVEDEPS = "mpfr-native gmp-native libmpc-native zlib-native"
>
>
> note that we will need to ship zlib-nativesdk as well if we do this
> so hopefully that case is covered by this.
Yes, zlib has a BBCLASSEXTEND on zlib-nativesdk so this should be fine.
Cheers,
Richard
next prev parent reply other threads:[~2012-02-10 13:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 0:06 [PATCH] gcc-4.6: Some small performance tweaks Richard Purdie
2012-02-10 0:39 ` Khem Raj
2012-02-10 13:40 ` Richard Purdie [this message]
2012-02-11 1:58 ` Khem Raj
2012-02-11 16:24 ` Richard Purdie
2012-02-14 12:16 ` Martin Jansa
2012-02-14 18:55 ` Khem Raj
2012-02-14 19:08 ` Martin Jansa
2012-02-14 19:13 ` Khem Raj
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=1328881254.13434.10.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