From: Trevor Woerner <twoerner@gmail.com>
To: OE-core <openembedded-core@lists.openembedded.org>
Subject: invoking a native compiler (gcc)
Date: Thu, 7 Jan 2016 00:21:10 -0500 [thread overview]
Message-ID: <568DF5C6.90509@gmail.com> (raw)
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?
next reply other threads:[~2016-01-07 5:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 5:21 Trevor Woerner [this message]
2016-01-07 8:07 ` invoking a native compiler (gcc) Robert Yang
2016-01-07 15:40 ` Trevor Woerner
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=568DF5C6.90509@gmail.com \
--to=twoerner@gmail.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.