public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Burton, Ross" <ross.burton@intel.com>,
	Trevor Woerner <twoerner@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: invoking a native compiler (gcc)
Date: Thu, 07 Jan 2016 16:37:07 +0000	[thread overview]
Message-ID: <1452184627.7598.132.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAJTo0LaDS4+ETDGLc+Ja8Q+TjCOJ=xn6dSvO4UsNMnLUPhzkcw@mail.gmail.com>

On Thu, 2016-01-07 at 15:46 +0000, Burton, Ross wrote:
> 
> On 7 January 2016 at 15:40, Trevor Woerner <twoerner@gmail.com>
> wrote:
> > 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.
> > 
> You could always set BUILD_CC to explicitly point to the right
> compiler on your machine.  When I was trying to make OE work on
> Darwin I had to set BUILD_CC to point at brew's gcc binaries.

Or you setup PATH to include things in the right order as we do with
other native tools...

Cheers,

Richard


  reply	other threads:[~2016-01-07 16:37 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
2016-01-07 15:46     ` Burton, Ross
2016-01-07 16:37       ` Richard Purdie [this message]
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=1452184627.7598.132.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    --cc=twoerner@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