From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] [PATCH 0/5] Buildroot cleanup
Date: Wed, 9 Sep 2009 08:24:47 +0200 [thread overview]
Message-ID: <20090909082447.7a230c8f@surf> (raw)
In-Reply-To: <87vdjt160i.fsf@macbook.be.48ers.dk>
Le Tue, 08 Sep 2009 23:27:41 +0200,
Peter Korsgaard <jacmet@uclibc.org> a ?crit :
> I have been thinking about it myself. *REALLY* supporting toolchains
> for all the different architectures / variants, uclibc and (e)glibc
> and following up on compiler bugs takes quite some effort (and noone
> seems willing to do it for buildroot), so maybe the best long term
> solution is simply to deprecate the toolchain building stuff and just
> recommend crosstool-ng instead?
That was my plan...
> This would make BR less selfcontained / one-stop-shop though.
until I met Buildroot users (I mean not end-users but organizations
using Buildroot as the build system they ship with their devices) who
told me that the selfcontained nature of BR was something they really
liked.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2009-09-09 6:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4AA62DD20200000D00128C56@gwia.alliedtelesyn.co.nz>
2009-09-08 19:54 ` [Buildroot] [RFC] [PATCH 0/5] Buildroot cleanup angus salkeld
2009-09-08 20:15 ` Sven Neumann
2009-09-08 21:27 ` Peter Korsgaard
2009-09-09 6:24 ` Thomas Petazzoni [this message]
2009-09-09 7:06 ` Peter Korsgaard
2009-09-09 6:32 ` Thomas Petazzoni
[not found] <4AA775760200006C0000A21D@gwia.alliedtelesyn.co.nz>
2009-09-08 21:51 ` angus salkeld
2009-09-09 6:26 ` Thomas Petazzoni
2009-09-09 7:03 ` Peter Korsgaard
2009-09-07 22:09 Thomas Petazzoni
2009-09-08 17:03 ` Will Newton
2009-09-08 19:13 ` Jonathan dumaresq
2009-09-08 21:20 ` Peter Korsgaard
2009-09-09 9:36 ` Will Newton
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=20090909082447.7a230c8f@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.