From: Carsten Schoenert <c.schoenert@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain/crostool-NG: mark as deprecated
Date: Sat, 15 Jun 2013 10:23:21 +0200 [thread overview]
Message-ID: <51BC2479.2060500@googlemail.com> (raw)
In-Reply-To: <20130614225556.GA3417@free.fr>
Hello,
Am 15.06.2013 00:55, schrieb Yann E. MORIN:
> Soochaon, All,
>
> On 2013-06-14 16:24 -0400, soochon radee spake thusly:
>> I know I'm chiming in late here, but I actively use ctng to build an eglibc
>> toolchain within buildroot. I hope that you can retain it until Thomas's
>> successor is in and running.
>
> I understand your, and other's, concern, and that's why the support for
> the ct-ng backend was not removed, and only marked deprecated.
In the first I was also a little bit unhappy with this advertising of
deprecation for crosstool-NG support inside buildroot. But in the end it
is really much easier to include a external toolchain into buildroot
then keep the crosstool-NG backend running. And, as Yann wrote, it saves
a lot of time while collecting things. :-)
I pushed my current used ARM1176 Toolchain config to github and wrote
(mostly for me) some lines how to use.
https://github.com/tijuca/ct-ng/blob/arm/howto-build.README
The resulting archive can be used as external toolchain inside buildroot
(as local file or via http URL).
Regards
Carsten
next prev parent reply other threads:[~2013-06-15 8:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 20:24 [Buildroot] [PATCH] toolchain/crostool-NG: mark as deprecated soochon radee
2013-06-14 22:55 ` Yann E. MORIN
2013-06-15 8:23 ` Carsten Schoenert [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-05-06 22:47 Yann E. MORIN
2013-05-07 8:02 ` Thomas Petazzoni
2013-05-07 8:20 ` Jeremy Rosen
2013-05-07 21:02 ` 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=51BC2479.2060500@googlemail.com \
--to=c.schoenert@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 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.