From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] External toolchain built by buildroot no longer supported.
Date: Tue, 6 Apr 2010 20:12:25 +0200 [thread overview]
Message-ID: <20100406201225.2b24b255@surf> (raw)
In-Reply-To: <hpfh61$drp$1@dough.gmane.org>
Hi Grant,
On Tue, 6 Apr 2010 14:41:05 +0000 (UTC)
Grant Edwards <grant.b.edwards@gmail.com> wrote:
> Are we to assume that crosstool-NG is now the "officially supported"
> source for external toolchains?
No. Yann (the author of the commit) and I have started discussing the
issue yesterday evening, and tried to find a satisfying solution. We
hope to get such a solution integrated before 2010.05.
> When I asked a few months ago if there was any reason I shouldn't use
> external toolchains built by buildroot, I was told there were none.
>
> Has that changed?
No, it hasn't changed. But there are bugs, and we need to fix them.
External toolchain support is still in its early ages, and it needs to
be improved. Your current feedback and comments are therefore very
welcome.
Regards,
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-04-06 18:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 14:41 [Buildroot] External toolchain built by buildroot no longer supported Grant Edwards
2010-04-06 15:02 ` Peter Korsgaard
2010-04-06 15:15 ` Grant Edwards
2010-04-06 16:42 ` Yann E. MORIN
2010-04-06 18:19 ` Grant Edwards
2010-04-06 16:42 ` Yann E. MORIN
2010-04-06 18:10 ` Grant Edwards
2010-04-06 18:12 ` 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=20100406201225.2b24b255@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