Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Braun <rbraun@sceen.net>
To: buildroot@busybox.net
Subject: [Buildroot] external toolchains and sysroot
Date: Fri, 19 Oct 2012 13:26:11 +0200	[thread overview]
Message-ID: <20121019112611.GA21369@mail.sceen.net> (raw)
In-Reply-To: <50813429.3010107@6wind.com>

On Fri, Oct 19, 2012 at 01:06:17PM +0200, Jean-Mickael Guerin wrote:
> Not exactly: let the toolchain use its own sysroot, and use -I /-L
> to look up in the staging directory. Original sysroot is read-only &
> shared, staging belongs to your build directory.
> 
> In another words my point is that the copy of sysroot is useless,
> using --sysroot=<my copy of built-in sysroot path, computed from the
> toolchain's compiler> cannot be safer than let it use the built-in
> syroot.
> Removing this copy will save time, space, and compatible whatever
> the directory layout of the toolchain.

Right, this should work just fine. I understand your point now, but then
I can't answer you.

-- 
Richard Braun

  reply	other threads:[~2012-10-19 11:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-19  9:10 [Buildroot] external toolchains and sysroot Jean-Mickael Guerin
2012-10-19  9:38 ` Richard Braun
2012-10-19  9:46   ` Jean-Mickael Guerin
2012-10-19  9:57     ` Richard Braun
2012-10-19 10:02       ` Richard Braun
2012-10-19 11:06         ` Jean-Mickael Guerin
2012-10-19 11:26           ` Richard Braun [this message]
2012-10-21  9:41           ` Thomas Petazzoni
2012-10-23  6:45             ` Jean-Mickael Guerin
2012-10-23  7:28               ` Thomas Petazzoni
2012-10-23  8:46                 ` Arnout Vandecappelle

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=20121019112611.GA21369@mail.sceen.net \
    --to=rbraun@sceen.net \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox