From: Marcus Osdoba <marcus.osdoba@googlemail.com>
To: buildroot@busybox.net
Subject: [Buildroot] external toolchain question
Date: Wed, 15 Sep 2010 21:33:08 +0200 [thread overview]
Message-ID: <4C911F74.7040506@googlemail.com> (raw)
In-Reply-To: <201009152050.27019.yann.morin.1998@anciens.enib.fr>
Am 15.09.2010 20:50, schrieb Yann E. MORIN:
> Marcus, All,
>
> On Wednesday 15 September 2010 20:40:54 Marcus Osdoba wrote:
>> Personally I didn't yet try out crosstool-ng because the current
>> patchlevel of buildroot is a higher one (e.g. gcc 4.3.4 vs 4.3.5).
> Hmmm... crosstool-NG has gcc-4.4.3, and even 4.4.4 and 4.5.x in
> experimental status.
>
>
Sorry, I didn't want to dispraise your work. Crosstool-ng is amazing!
But I had a quick look into it and figured out:
BR has 4.3.5 since June 2010 and 4.4.4 since May 2010.
The crosstool-ng version 1.8.1 provides 4.3.4 and 4.4.3 as default. With
experimental activated no 4.3.5 either.
The eglibc points to 2.10 (2.11stable/2.12exp) and glibc to 2.9
(2.11.2stable/2.12exp).
So my overall (subjective) impression was that br has currently a higher
patchlevel.
By the way, I completely agree with Peters opinion that crosstool-ng
could provide "better" toolchains while br focusses on it's maintask.
Crosstool-ng is designed to generate toolchains as a specialised tool -
really great. I saw that integration of ct-ng in br (or more intuitive
config wrapper) is quite a long time on the agenda. I think it would be
very eligible to see it in br.
What is the current status of this idea?
Thanks for your great work.
Regards,
Marcus
next prev parent reply other threads:[~2010-09-15 19:33 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 [this message]
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
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=4C911F74.7040506@googlemail.com \
--to=marcus.osdoba@googlemail.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