All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Holger Hans Peter Freyther <holger@freyther.de>
Cc: poky@yoctoproject.org
Subject: Re: gcc 4.9.1 and stdint.h
Date: Mon, 03 Nov 2014 15:37:09 +0000	[thread overview]
Message-ID: <1415029029.5111.21.camel@ted> (raw)
In-Reply-To: <20141103151218.GD6154@xiaoyu.lan>

On Mon, 2014-11-03 at 16:12 +0100, Holger Hans Peter Freyther wrote:
> On Mon, Nov 03, 2014 at 08:04:59AM +0000, Richard Purdie wrote:
> 
> Dear Richard,
> 
> > http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=678e8798ebe0f4fd1bd347db136f1499b8fe00c9
> 
> thanks a lot for explaining. I see how using the default sysroot
> with external toolchains is going to cause issues. What is the
> reasoning to have it for the canadian cross (hence meta-toolchain)?

The reasoning is that we have one canadian-cross compiler targeting
multiple sysroots (one arm compiler targets all arm machines). The
compiled in sysroot may not be the final installation path anyway,
depending on where you install meta-toolchain.

We prefer deterministic builds rather than some toolchain installations
that work and some that don't.

Cheers,

Richard



  reply	other threads:[~2014-11-03 15:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-02 20:05 gcc 4.9.1 and stdint.h Holger Hans Peter Freyther
2014-11-02 22:03 ` Richard Purdie
2014-11-03  7:22   ` Holger Hans Peter Freyther
2014-11-03  8:04     ` Richard Purdie
2014-11-03 15:12       ` Holger Hans Peter Freyther
2014-11-03 15:37         ` Richard Purdie [this message]
2014-11-07 16:58           ` Holger Hans Peter Freyther
2014-11-12 13:21             ` Richard Purdie
2014-11-12 13:50               ` Holger Hans Peter Freyther

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=1415029029.5111.21.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=holger@freyther.de \
    --cc=poky@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.