From: Trevor Woerner <twoerner@gmail.com>
To: Robert Yang <liezhi.yang@windriver.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: invoking a native compiler (gcc)
Date: Thu, 7 Jan 2016 10:40:31 -0500 [thread overview]
Message-ID: <568E86EF.5050408@gmail.com> (raw)
In-Reply-To: <568E1CB6.708@windriver.com>
Hi Robert,
On 01/07/16 03:07, Robert Yang wrote:
>
>
> On 01/07/2016 01:21 PM, Trevor Woerner wrote:
>> If a recipe needs to build some tool on the build machine which it later
>> wants to invoke, my understanding is that BUILD_CC should be used?
>
> Yes, you're right, use ${BUILD_CC}.
>
Ok, thanks. That's what I thought.
I was surprised to find that BUILD_CC is being set to whatever comes up
first in our build computer's PATH. But I guess the alternative would be
to make our builds longer by compiling our own native compiler for such
cases.
next prev parent reply other threads:[~2016-01-07 15:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 5:21 invoking a native compiler (gcc) Trevor Woerner
2016-01-07 8:07 ` Robert Yang
2016-01-07 15:40 ` Trevor Woerner [this message]
2016-01-07 15:46 ` Burton, Ross
2016-01-07 16:37 ` Richard Purdie
2016-01-07 18:01 ` Trevor Woerner
2016-01-12 0:35 ` 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=568E86EF.5050408@gmail.com \
--to=twoerner@gmail.com \
--cc=liezhi.yang@windriver.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 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.