Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] SYSROOT_DIR issue with external toolchains
Date: Mon, 14 Dec 2009 23:43:40 +0100	[thread overview]
Message-ID: <20091214234340.714eb09b@surf> (raw)
In-Reply-To: <5f2b60912141113n33fa36f1mdd45dc55313301c3@mail.gmail.com>

Le Mon, 14 Dec 2009 20:13:44 +0100,
Bj?rn Forsman <bjorn.forsman@gmail.com> a ?crit :

> SYSROOT_DIR=$(shell $(TARGET_CC) -print-sysroot)
> 
> Is there any problem with this change?

Yes, it doesn't work with all gcc versions.

I have
http://git.buildroot.net/~tpetazzoni/git/buildroot/commit/?h=multilib-toolchain-fix&id=2907415d82b7d306ca3f1f1ead0bbb0c7f1505c3
in my patch queue. Something I should clean up, test and submit.

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

  reply	other threads:[~2009-12-14 22:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-14 19:13 [Buildroot] SYSROOT_DIR issue with external toolchains Bjørn Forsman
2009-12-14 22:43 ` Thomas Petazzoni [this message]
2009-12-15  8:31   ` Bjørn Forsman

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=20091214234340.714eb09b@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox