All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain-external: check sysroot *after* copying
Date: Mon, 13 Dec 2010 17:52:44 +0100	[thread overview]
Message-ID: <20101213175244.72901d85@surf> (raw)
In-Reply-To: <1292171123-32551-1-git-send-email-vapier@gentoo.org>

On Sun, 12 Dec 2010 11:25:23 -0500
Mike Frysinger <vapier@gentoo.org> 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.

See the definition of SYSROOT_DIR:

TARGET_CC_NO_SYSROOT=$(filter-out --sysroot=%,$(TARGET_CC_NOCCACHE))
SYSROOT_DIR=$(shell $(TARGET_CC_NO_SYSROOT) -print-sysroot 2>/dev/null)

Could you point the specific problem you're having ?

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2010-12-13 16:52 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 [this message]
2010-12-13 17:27   ` Mike Frysinger

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=20101213175244.72901d85@surf \
    --to=thomas.petazzoni@free-electrons.com \
    --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 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.