From: William Mills <wmills@ti.com>
To: "Paul D. DeRocco" <pderocco@ix.netcom.com>
Cc: 'Paul Eggleton' <paul.eggleton@linux.intel.com>, yocto@yoctoproject.org
Subject: Re: Need clarification on some terms
Date: Wed, 12 Jun 2013 17:32:53 -0400 [thread overview]
Message-ID: <51B8E905.3090405@ti.com> (raw)
In-Reply-To: <58DC6CADE1A5492E9E712C310E6C9019@PAULD>
On 06/12/2013 03:51 PM, Paul D. DeRocco wrote:
> For now, I really just need to know if I'm interested in the SDK, since I
> have no intention of ever running compilations on my target system.
>
Trevor's answer has a lot of great background.
My short answer is gcc-cross is for use inside bitbake (in the host) and
gcc-crosssdk is for use outside of bitbake (still on the host). This
outside bitbake use case is the SDK Trevor described.
Why does gcc need to get built differently between these two use cases?
I gave up asking this many years ago and accepted it as "something I
can not change" for my own serenity. I am sure Paul or Khem could give
the detail. The sdk version does have extra stuff to make it
relocatable etc that is not needed inside of bitbake. However I don't
know why we don't always build the sdk-able version.
next prev parent reply other threads:[~2013-06-12 21:33 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
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 [this message]
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=51B8E905.3090405@ti.com \
--to=wmills@ti.com \
--cc=paul.eggleton@linux.intel.com \
--cc=pderocco@ix.netcom.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.