Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain-external: check sysroot *after* copying
Date: Mon, 13 Dec 2010 12:27:08 -0500	[thread overview]
Message-ID: <201012131227.08896.vapier@gentoo.org> (raw)
In-Reply-To: <20101213175244.72901d85@surf>

On Monday, December 13, 2010 11:52:44 Thomas Petazzoni wrote:
> On Sun, 12 Dec 2010 11:25:23 -0500 Mike Frysinger wrote:
> > The current toolchain checking code will probe the files in the
> > sysroot to make sure things are sane, but it does this *before* it
> > actually copies the files in question over.  Thus from a clean build,
> > it's impossible to actually use the external toolchain option.
> > 
> > So re-order things so we initialize the local sysroot first and then
> > check the result.
> 
> SYSROOT_DIR points to the original sysroot of the toolchain, not the
> one we copy locally for Buildroot. So the original sysroot of the
> toolchain is already available when starting a new build.

ok, so i misinterpreted the errors fixed by the other toolchain patches ive 
posted around the same time as this one.  for more details, consult those.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20101213/0472f868/attachment.pgp>

      reply	other threads:[~2010-12-13 17:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-12 16:25 [Buildroot] [PATCH] toolchain-external: check sysroot *after* copying Mike Frysinger
2010-12-13 16:52 ` Thomas Petazzoni
2010-12-13 17:27   ` Mike Frysinger [this message]

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=201012131227.08896.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --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