From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] External toolchain built by buildroot no longer supported.
Date: Tue, 6 Apr 2010 14:41:05 +0000 (UTC) [thread overview]
Message-ID: <hpfh61$drp$1@dough.gmane.org> (raw)
As of this commit
http://git.buildroot.org/buildroot/commit/?id=3b7aee23f2ab732f06b8a090ca002fb102d547ee
use of of external toolchains built by buildroot is no longer
possible.
Are we to assume that crosstool-NG is now the "officially supported"
source for external toolchains?
I've been using external toolchains built by buildroot since it's so
much simpler than using crosstool-NG: you don't have to build and
install buildroot like you do crosstool-NG, and I already have
buildroot under source control. Now I'll also have to place
crosstool-NG (both sources and installed files) under version control.
I'd just as soon stick with using buildroot toolchains, but it's
starting to feel like swimming against the tide.
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?
--
Grant Edwards grant.b.edwards Yow! Will it improve my
at CASH FLOW?
gmail.com
next reply other threads:[~2010-04-06 14:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 14:41 Grant Edwards [this message]
2010-04-06 15:02 ` [Buildroot] External toolchain built by buildroot no longer supported 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
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='hpfh61$drp$1@dough.gmane.org' \
--to=grant.b.edwards@gmail.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