From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] external toolchain question
Date: Thu, 16 Sep 2010 14:14:49 +0200 [thread overview]
Message-ID: <20100916141449.27016940@surf> (raw)
In-Reply-To: <4C920255.80602@carallon.com>
On Thu, 16 Sep 2010 12:41:09 +0100
William Wagner <will_wagner@carallon.com> wrote:
> We could change copy_toolchain_lib_root so that it puts the libraries
> in the corresponding location it finds them in rather than currently
> searching in three locations but always copying to the specified one.
Absolutely. That's what the code was doing prior to
ecb7642cce36bc68d93f0eee677adc7da538228d.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2010-09-16 12:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 18:17 [Buildroot] external toolchain question William Wagner
2010-09-15 18:40 ` Marcus Osdoba
2010-09-15 18:50 ` Yann E. MORIN
2010-09-15 19:33 ` Marcus Osdoba
2010-09-15 20:46 ` Yann E. MORIN
2010-09-15 19:19 ` Thomas Petazzoni
2010-09-16 8:03 ` William Wagner
2010-09-16 9:04 ` Thomas Petazzoni
2010-09-16 11:41 ` William Wagner
2010-09-16 12:14 ` Thomas Petazzoni [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=20100916141449.27016940@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