From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: yocto@yoctoproject.org
Subject: Re: Need clarification on some terms
Date: Wed, 12 Jun 2013 12:59:33 +0100 [thread overview]
Message-ID: <1875741.cStO1T6C1g@helios> (raw)
In-Reply-To: <bc6dfda22fdcefeb7de188e29b2ad887.squirrel@mail.cubic.org>
On Wednesday 12 June 2013 04:16:30 michael@cubic.org wrote:
> Paul D. DeRocco wrote on Tuesday, June 11, 2013 at 9:07 PM:
> > "Following is a list of toolchain recipes..." This is followed by
> > gcc-cross-initial, gcc-cross-intermediate, gcc-cross. All three of these
> > things say that the toolchain runs on the host and is used to build
> > software
> > for the target. So why are there three of them? What are the differences
> > among them?
>
> The gcc must be build multiple times when you bootstrap it.
> For building the gcc you need to build the libc and therefor you need to
> build the linux kernel headers and therefor you need the gcc. Oops.
>
> Thats why you first build a gcc only with c support and no libc first.
> Use that to generate the kernel headers, then build the initial libc and
> then another gcc with libc support and all the frontends you need
> (c,c++,java,fortran,..). Why there is the gcc-cross-intermediate I am not
> shure, but there will be a reason and another one can clarify that.
gcc-cross-intermediate is gone as of 1.3; as I understand it current versions
of glibc can be compiled using gcc-cross-initial so the intermediate step is
no longer required. We should remove mention of this from the documentation
(other than in the migration section that is).
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-06-12 11:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 4:07 Need clarification on some terms Paul D. DeRocco
2013-06-12 5:58 ` Rifenbark, Scott M
2013-06-12 11:16 ` michael
2013-06-12 11:32 ` Bill Traynor
2013-06-12 11:36 ` Rifenbark, Scott M
2013-06-12 11:59 ` Paul Eggleton [this message]
2013-06-12 12:24 ` Rifenbark, Scott M
2013-06-12 12:27 ` Rifenbark, Scott M
2013-06-12 12:31 ` Paul Eggleton
2013-06-12 19:51 ` Paul D. DeRocco
2013-06-12 19:53 ` Rifenbark, Scott M
2013-06-12 20:51 ` Trevor Woerner
2013-06-12 21:04 ` Trevor Woerner
2013-06-12 21:58 ` Paul D. DeRocco
2013-06-12 22:10 ` Paul D. DeRocco
2013-06-12 22:26 ` Zhang, Jessica
2013-06-12 21:32 ` William Mills
2013-06-13 7:10 ` Khem Raj
2013-06-13 7:54 ` Paul D. DeRocco
2013-06-12 12:24 ` Rifenbark, Scott M
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=1875741.cStO1T6C1g@helios \
--to=paul.eggleton@linux.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.