From: Gary Thomas <gary@mlbassoc.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: "poky@pokylinux.org" <poky@pokylinux.org>
Subject: Re: about ${KERNEL_CC} and ${CC}
Date: Thu, 30 Dec 2010 11:02:40 -0700 [thread overview]
Message-ID: <4D1CC940.5080202@mlbassoc.com> (raw)
In-Reply-To: <1293704461.17519.9998.camel@rex>
On 12/30/2010 03:21 AM, Richard Purdie wrote:
> On Thu, 2010-12-23 at 05:27 -0700, Gary Thomas wrote:
>> On 12/23/2010 02:44 AM, Richard Purdie wrote:
>>> Perf should be compiled with the userspace toolchain, not the kernel
>>> one. I'd say this fix is therefore correct.
>>>
>>> Adding TOOLCHAIN_OPTIONS to KERNEL_CC would also probably be a good idea
>>> too.
>>
>> Perfect idea! I added this and I'm now able to rebuild my
>> kernel package using a sstate-cache based toolchain. This
>> should close bug #605
>>
>> Patch attached for review.
>
> There is no need to set TOOLCHAIN_OPTIONS and we need to alter both
> KERNEL_CC and KERNEL_LD which both have this problem or
> TOOLCHAIN_OPTIONS being missing. I've pushed a patch into master which
> does this.
>
> I've also pushed a patch to ensure the userspace compiler if used to
> build perf.
>
> Let me know if there are any more problems in this area.
Thanks, this all seems to be working well now.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2010-12-30 18:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 6:11 about ${KERNEL_CC} and ${CC} Tian, Kevin
2010-12-23 9:44 ` Richard Purdie
2010-12-23 12:27 ` Gary Thomas
2010-12-24 1:01 ` Tian, Kevin
2010-12-30 10:21 ` Richard Purdie
2010-12-30 18:02 ` Gary Thomas [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=4D1CC940.5080202@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=poky@pokylinux.org \
--cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.