From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] Deprecate the support for the toolchain on target
Date: Sat, 17 Nov 2012 09:22:02 +0100 [thread overview]
Message-ID: <87d2zcwset.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <4afe9c298939f3701caa09c2cc5c4bc04f6d4408.1352586949.git.thomas.petazzoni@free-electrons.com> (Thomas Petazzoni's message of "Sat, 10 Nov 2012 23:36:02 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Thomas> As discussed during the ELCE 2012 Buildroot Developers Meeting, we no
Thomas> longer want to support the possibility of building a toolchain for the
Thomas> target. None of the core developers have any use for this, it has been
Thomas> known to be broken or cause problems for a long time without anyone
Thomas> providing fixes for it.
Thomas> In addition to this, Buildroot is inherently a cross-compilation tool,
Thomas> so the usage of a native toolchain on the target is not really
Thomas> useful. Many newcomers are tempted to use this possibility even though
Thomas> it is clearly not the intended usage of Buildroot.
Committed, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-11-17 8:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-10 22:36 [Buildroot] Deprecate the support for toolchain on the target Thomas Petazzoni
2012-11-10 22:36 ` [Buildroot] [PATCH 1/2] Deprecate the support for the toolchain on target Thomas Petazzoni
2012-11-10 23:26 ` Alex Bradbury
2012-11-11 22:09 ` Thomas Petazzoni
2012-11-11 22:53 ` Arnout Vandecappelle
2012-11-11 22:59 ` Thomas Petazzoni
2012-11-11 23:52 ` Arnout Vandecappelle
2012-11-17 8:21 ` Peter Korsgaard
2012-11-17 10:42 ` Gustavo Zacarias
2012-11-17 11:06 ` Thomas Petazzoni
2012-11-17 8:22 ` Peter Korsgaard [this message]
2012-11-10 22:36 ` [Buildroot] [PATCH 2/2] Mark a number of development related packages as deprecated Thomas Petazzoni
2012-11-11 22:54 ` Arnout Vandecappelle
2012-11-17 8:26 ` Peter Korsgaard
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=87d2zcwset.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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