toolchain/crostool-NG: mark as deprecated
PATCH 1/1 toolchain/crostool-NG: mark as deprecated
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.
Thanks,
Soochon
Quoted 21 lines
Quoted 21 lines
I don't have real comments about the proposal to deprecate the Crosstool-NG support, but I'd like to take this opportunity to unveil my plans about the internal toolchain support (I hate unveiling plans before the code is ready, but it seems like a good idea in this particular case) :
(1) I am currently converting the existing internal toolchain logic to
use the package infrastructure. I've already done it for 'gdb' (merged for 2013.05), I have patches that seem to work for elf2flt and linux-headers, and I've started working on converting
gcc (which is the most complicated piece of the puzzle).(2) Once this conversion is done, I intend to work on adding (e)glibc
support to the internal toolchain backend, so that regardless of what happens with the Crosstool-NG backend, Buildroot will continue to have the possibility to build a (e)glibc toolchain.
Quoted 8 lines
Quoted 3 lines
(1) and (2) represent a significant amount of work, so don't expect those things to be ready overnight.
ok, thanks for the news, I was a bit worried that we had would have no support for self-compiled glibc toolchain at some point (that was the main reason I was using ct-ng)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130614/0c5d0ac4/attachment.html>
PATCH 1/1 toolchain/crostool-NG: mark as deprecated
Soochaon, All,
On 2013-06-14 16:24 -0400, soochon radee spake thusly:
Quoted 3 lines
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.
I have always thought that te best course of action in this respect was to have a toolchain pre-built once and for all, and that this toolchain be used by Buildroot as an external toolchain.
I do not understand why people insist on building the toolchain everytime from within Buildroot. Even on my fast machine, it takes almost as much time as it takes to build the packages, if not more.
That the possibility exists (in its current, not-so-limited uClibc-based incarnation) for beginners I understand. But not for sustained work.
This means that I won't push updates to the Buildroot ct-ng backend anymore.
But, by popular demand, I'll also refrain from posting a patch that removes it entirely! ;-)
Regards,
Yann E. MORIN.
Signature · 6 lines
.-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------'
PATCH 1/1 toolchain/crostool-NG: mark as deprecated
Hello,
Am 15.06.2013 00:55, schrieb Yann E. MORIN:
Quoted 9 lines
Soochaon, All,
On 2013-06-14 16:24 -0400, soochon radee spake thusly:
Quoted 3 lines
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