toolchain/crostool-NG: mark as deprecated
PATCH 1/1 toolchain/crostool-NG: mark as deprecated
From: "Yann E. MORIN" <[email protected]>
For the following reasons:
- it used to be broken without anyone noticing for a long time,
- it is still not fully integrated within the Buildroot set of options,
- it has not gained much traction (not even I use it),
- I've always argued that sustained development should use an external toolchain, and not rely on building one with Buildroot,
- I did not submit any of the enhancements requested during the last developpers' day in Brussels,
- I have neither the incentive nor the time to maintain and enhance it,
it is time to deprecate the crosstool-NG backend for the 2013.05 release.
Then, it will be entirely removed early in the 2013.08 cycle, to let some time for those that rely on it to voice their opinions. ;-)
--- toolchain/Config.in | 1 + 1 file changed, 1 insertion(+)
toolchain/Config.in +1 -0
@@ -22,6 +22,7 @@ config BR2_TOOLCHAIN_EXTERNAL config BR2_TOOLCHAIN_CTNG bool "Crosstool-NG toolchain" + depends on BR2_DEPRECATED depends on !BR2_microblaze && !BR2_aarch64 && !BR2_xtensa && !BR2_arc select BR2_TOOLCHAIN_HAS_SHADOW_PASSWORDS help
Signature · 1 line
1.8.1.2
PATCH 1/1 toolchain/crostool-NG: mark as deprecated
Dear Yann E. MORIN,
Quoted 12 lines · Yann E. MORIN
From: "Yann E. MORIN" <[email protected]>
For the following reasons:
- it used to be broken without anyone noticing for a long time,
- it is still not fully integrated within the Buildroot set of options,
- it has not gained much traction (not even I use it),
- I've always argued that sustained development should use an external toolchain, and not rely on building one with Buildroot,
- I did not submit any of the enhancements requested during the last developpers' day in Brussels,
- I have neither the incentive nor the time to maintain and enhance it,
Quoted 4 lines
it is time to deprecate the crosstool-NG backend for the 2013.05 release.
Then, it will be entirely removed early in the 2013.08 cycle, to let some time for those that rely on it to voice their opinions. ;-)
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.
(1) and (2) represent a significant amount of work, so don't expect those things to be ready overnight.
Best regards,
Thomas
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com
PATCH 1/1 toolchain/crostool-NG: mark as deprecated
Quoted 15 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).
Quoted 9 lines
(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.(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)
PATCH 1/1 toolchain/crostool-NG: mark as deprecated
In reply to Yann E. MORINQuoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Yann" == Yann E MORIN <[email protected]> writes:
Yann> From: "Yann E. MORIN" <[email protected]> Yann> For the following reasons:
Yann> - it used to be broken without anyone noticing for a long time, Yann> - it is still not fully integrated within the Buildroot set of options, Yann> - it has not gained much traction (not even I use it), Yann> - I've always argued that sustained development should use an external
Yann> toolchain, and not rely on building one with Buildroot,
Yann> - I did not submit any of the enhancements requested during the last
Yann> developpers' day in Brussels,
Yann> - I have neither the incentive nor the time to maintain and enhance it,
Yann> it is time to deprecate the crosstool-NG backend for the 2013.05 release.
Yann> Then, it will be entirely removed early in the 2013.08 cycle, to let some Yann> time for those that rely on it to voice their opinions. ;-)
Committed, thanks.
Signature · 1 line
Bye, Peter Korsgaard