All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark T <mtl1nuxd3v@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Which Toolchain is being used to build Yocto ?
Date: Wed, 3 Feb 2016 18:15:31 +0000	[thread overview]
Message-ID: <CALf_N3bW91zwfebcdvfseHFKQrnykSdAsvodjchVKGr2eym-2w@mail.gmail.com> (raw)
In-Reply-To: <CAJTo0LbiKF0w=NeNFRYmh_fc73HYH-1Zg6p1-8r46-oexFt6-A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 840 bytes --]

Thanks. That makes sense; all the cross compile tools are built using the
Host machines native toolchain on the host then the cross-toolchain used to
cross compile yocto for the target.



On 3 February 2016 at 17:13, Burton, Ross <ross.burton@intel.com> wrote:

>
> On 3 February 2016 at 15:07, Mark T <mtl1nuxd3v@gmail.com> wrote:
>
>> I notice there is a meta/recipes-devtools  -  I assume this pulls in from
>> build/downloads - so gcc-5.2.0.tar.bz2 for example. Does the tool-chain
>> comprised of these recipes get built by /usr/bin/gcc before being used to
>> compile Yocto ?
>>
>
> The host's gcc (typically /usr/bin/gcc) is used to build gcc-cross, which
> is then used to compile everything that needs to be cross-compiled.  We
> don't build our own native compiler to replace the host compiler.
>
> Ross
>

[-- Attachment #2: Type: text/html, Size: 1557 bytes --]

  reply	other threads:[~2016-02-03 18:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-03 15:07 Which Toolchain is being used to build Yocto ? Mark T
2016-02-03 16:52 ` Kosta  Zertsekel
2016-02-03 17:13 ` Burton, Ross
2016-02-03 18:15   ` Mark T [this message]
2016-02-03 18:43     ` Burton, Ross
2016-02-03 19:58     ` 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=CALf_N3bW91zwfebcdvfseHFKQrnykSdAsvodjchVKGr2eym-2w@mail.gmail.com \
    --to=mtl1nuxd3v@gmail.com \
    --cc=ross.burton@intel.com \
    --cc=yocto@yoctoproject.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.