Various external toolchain updates
cover Various external toolchain updates
Hello,
Here is a round of misc external toolchain updates: Sourcery ARM, Sourcery MIPS, Linaro ARM, Linaro AArch64, Blackfin, and deprecation of Microblaze toolchains.
Thomas
Thomas Petazzoni (6):
toolchain-external: add Sourcery ARM 2013.11, remove Sourcery ARM
2011.09
toolchain-external: add Sourcery MIPS 2013.11, remove Sourcery MIPS
2012.03 toolchain-external: update Linaro ARM toolchains
toolchain-external: update Linaro AArch64 toolchains
toolchain-external: mark Microblaze external toolchains as deprecated
toolchain-external: add support for the Blackfin 2013R1 toolchain
toolchain/toolchain-external/Config.in | 133 ++++++++++++--------- toolchain/toolchain-external/toolchain-external.mk | 48 ++++---- 2 files changed, 104 insertions(+), 77 deletions(-)
Signature · 1 line
1.8.3.2
PATCH 1/6 toolchain-external: add Sourcery ARM 2013.11, remove Sourcery ARM 2011.09
This commit adds the support for the recently release Sourcery ARM 2013.11 toolchain (gcc 4.8, gdb 7.6, glibc 2.18, gdb 7.6), and consequently removes the support for the Sourcery ARM 2011.09 toolchain.
--- toolchain/toolchain-external/Config.in | 26 +++++++++++----------- toolchain/toolchain-external/toolchain-external.mk | 8 +++---- 2 files changed, 17 insertions(+), 17 deletions(-)
toolchain/toolchain-external/Config.in +13 -13
@@ -77,8 +77,8 @@ comment "Linaro toolchains available for Cortex-A + EABIhf" depends on BR2_GCC_TARGET_ARCH != "armv7-a" || !BR2_ARM_EABIHF depends on !BR2_PREFER_STATIC_LIB -config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201305 - bool "Sourcery CodeBench ARM 2013.05" +config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201311 + bool "Sourcery CodeBench ARM 2013.11" depends on BR2_arm depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86" depends on BR2_ARM_EABI
@@ -89,8 +89,8 @@ config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201305 select BR2_HOSTARCH_NEEDS_IA32_LIBS help Sourcery CodeBench toolchain for the ARM architecture, from - Mentor Graphics. It uses gcc 4.7.3, binutils 2.23.52, glibc - 2.17 and gdb 7.4.50, kernel headers 3.8.2. It has support + Mentor Graphics. It uses gcc 4.8.1, binutils 2.23.52, glibc + 2.18 and gdb 7.6.50, kernel headers 3.11. It has support for the following variants: - ARMv5TE, little endian, soft-float, glibc Select ARM926T, ARM10T, XScale or another ARMv5 core
@@ -103,8 +103,8 @@ config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201305 Select BR2_SOFT_FLOAT Set BR2_TARGET_OPTIMIZATION to -mthumb -config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201203 - bool "Sourcery CodeBench ARM 2012.03" +config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201305 + bool "Sourcery CodeBench ARM 2013.05" depends on BR2_arm depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86" depends on BR2_ARM_EABI
@@ -115,8 +115,8 @@ config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201203 select BR2_HOSTARCH_NEEDS_IA32_LIBS help Sourcery CodeBench toolchain for the ARM architecture, from - Mentor Graphics. It uses gcc 4.6.3, binutils 2.21.53, glibc - 2.15 and gdb 7.2.50, kernel headers 3.2.10. It has support + Mentor Graphics. It uses gcc 4.7.3, binutils 2.23.52, glibc + 2.17 and gdb 7.4.50, kernel headers 3.8.2. It has support for the following variants: - ARMv5TE, little endian, soft-float, glibc Select ARM926T, ARM10T, XScale or another ARMv5 core
@@ -129,8 +129,8 @@ config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201203 Select BR2_SOFT_FLOAT Set BR2_TARGET_OPTIMIZATION to -mthumb -config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201109 - bool "Sourcery CodeBench ARM 2011.09" +config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201203 + bool "Sourcery CodeBench ARM 2012.03" depends on BR2_arm depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86" depends on BR2_ARM_EABI
@@ -141,8 +141,8 @@ config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201109 select BR2_HOSTARCH_NEEDS_IA32_LIBS help Sourcery CodeBench toolchain for the ARM architecture, from - Mentor Graphics. It uses gcc 4.6.1, binutils 2.21.53, glibc - 2.13 and gdb 7.2.50, kernel headers 3.0.1. It has support + Mentor Graphics. It uses gcc 4.6.3, binutils 2.21.53, glibc + 2.15 and gdb 7.2.50, kernel headers 3.2.10. It has support for the following variants: - ARMv5TE, little endian, soft-float, glibc Select ARM926T, ARM10T, XScale or another ARMv5 core
@@ -839,9 +839,9 @@ config BR2_TOOLCHAIN_EXTERNAL_PREFIX default "arm-linux-gnueabihf" if BR2_TOOLCHAIN_EXTERNAL_LINARO_2013_09 default "arm-linux-gnueabihf" if BR2_TOOLCHAIN_EXTERNAL_LINARO_2013_08 default "arm-linux-gnueabihf" if BR2_TOOLCHAIN_EXTERNAL_LINARO_2013_07 - default "arm-none-linux-gnueabi" if BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201109 default "arm-none-linux-gnueabi" if BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201203 default "arm-none-linux-gnueabi" if BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201305 + default "arm-none-linux-gnueabi" if BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201311 default "arm-arago-linux-gnueabi" if BR2_TOOLCHAIN_EXTERNAL_ARAGO_ARMV7A_201109 default "arm-arago-linux-gnueabi" if BR2_TOOLCHAIN_EXTERNAL_ARAGO_ARMV5TE_201109 default "aarch64-linux-gnu" if BR2_TOOLCHAIN_EXTERNAL_LINARO_AARCH64_13_09
toolchain/toolchain-external/toolchain-external.mk +4 -4
@@ -242,15 +242,15 @@ define TOOLCHAIN_EXTERNAL_LINARO_ARMHF_SYMLINK ln -sf . $(TARGET_DIR)/usr/lib/arm-linux-gnueabihf endef -ifeq ($(BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201109),y) -TOOLCHAIN_EXTERNAL_SITE = http://sourcery.mentor.com/public/gnu_toolchain/arm-none-linux-gnueabi/ -TOOLCHAIN_EXTERNAL_SOURCE = arm-2011.09-70-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 -else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201203),y) +ifeq ($(BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201203),y) TOOLCHAIN_EXTERNAL_SITE = http://sourcery.mentor.com/public/gnu_toolchain/arm-none-linux-gnueabi/ TOOLCHAIN_EXTERNAL_SOURCE = arm-2012.03-57-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201305),y) TOOLCHAIN_EXTERNAL_SITE = http://sourcery.mentor.com/public/gnu_toolchain/arm-none-linux-gnueabi/ TOOLCHAIN_EXTERNAL_SOURCE = arm-2013.05-24-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 +else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201311),y) +TOOLCHAIN_EXTERNAL_SITE = http://sourcery.mentor.com/public/gnu_toolchain/arm-none-linux-gnueabi/ +TOOLCHAIN_EXTERNAL_SOURCE = arm-2013.11-33-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_ARAGO_ARMV7A_201109),y) TOOLCHAIN_EXTERNAL_SITE = http://software-dl.ti.com/sdoemb/sdoemb_public_sw/arago_toolchain/2011_09/exports/ TOOLCHAIN_EXTERNAL_SOURCE = arago-2011.09-armv7a-linux-gnueabi-sdk.tar.bz2
Signature · 1 line
1.8.3.2
PATCH 1/6 toolchain-external: add Sourcery ARM 2013.11, remove Sourcery ARM 2011.09
Thomas, All,
On 2013-12-27 12:32 +0100, Thomas Petazzoni spake thusly:
Quoted 2 lines
This commit adds the support for the recently release Sourcery ARM 2013.11 toolchain (gcc 4.8, gdb 7.6, glibc 2.18, gdb 7.6), and
As Baruch pointed out: duplicate 'gdb'.
Quoted 4 lines
consequently removes the support for the Sourcery ARM 2011.09 toolchain.
Signed-off-by Thomas Petazzoni <[email protected]>
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 2/6 toolchain-external: add Sourcery MIPS 2013.11, remove Sourcery MIPS 2012.03
In reply to Thomas PetazzoniThis commit adds the support for the recently release Sourcery MIPS 2013.11 toolchain (gcc 4.8, gdb 7.6, glibc 2.18, gdb 7.6), and consequently removes the support for the Sourcery MIPS 2012.03 toolchain.
--- toolchain/toolchain-external/Config.in | 42 +++++++++++----------- toolchain/toolchain-external/toolchain-external.mk | 6 ++-- 2 files changed, 24 insertions(+), 24 deletions(-)
toolchain/toolchain-external/Config.in +21 -21
@@ -201,8 +201,8 @@ config BR2_TOOLCHAIN_EXTERNAL_ARAGO_ARMV5TE_201109 This toolchain uses software-floating point. -config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS201305 - bool "Sourcery CodeBench MIPS 2013.05" +config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS201311 + bool "Sourcery CodeBench MIPS 2013.11" depends on BR2_mips || BR2_mipsel || BR2_mips64 || BR2_mips64el depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86" depends on !BR2_MIPS_NABI32
@@ -213,9 +213,9 @@ config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS201305 select BR2_HOSTARCH_NEEDS_IA32_LIBS help Sourcery CodeBench toolchain for the MIPS architecture, from - Mentor Graphics. It uses gcc 4.7.3, binutils 2.23.52, glibc - 2.17, uClibc 0.9.30 and gdb 7.4.50, kernel headers - 3.8.2. It has support for the following variants: + Mentor Graphics. It uses gcc 4.8.1, binutils 2.23.52, glibc + 2.18, uClibc 0.9.30 and gdb 7.6.50, kernel headers + 3.11. It has support for the following variants: - MIPS32 O32 big endian glibc Select a MIPS generic core Disable BR2_SOFT_FLOAT
@@ -269,9 +269,9 @@ config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS201305 - MIPS32 little endian soft float uclibc Not usable in Buildroot yet. -config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS201209 - bool "Sourcery CodeBench MIPS 2012.09" - depends on BR2_mips || BR2_mipsel +config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS201305 + bool "Sourcery CodeBench MIPS 2013.05" + depends on BR2_mips || BR2_mipsel || BR2_mips64 || BR2_mips64el depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86" depends on !BR2_MIPS_NABI32 depends on !BR2_PREFER_STATIC_LIB
@@ -281,35 +281,35 @@ config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS201209 select BR2_HOSTARCH_NEEDS_IA32_LIBS help Sourcery CodeBench toolchain for the MIPS architecture, from - Mentor Graphics. It uses gcc 4.7.2, binutils 2.23.51, glibc - 2.16, uClibc 0.9.30 and gdb 7.4.50, kernel headers - 3.5.4. It has support for the following variants: + Mentor Graphics. It uses gcc 4.7.3, binutils 2.23.52, glibc + 2.17, uClibc 0.9.30 and gdb 7.4.50, kernel headers + 3.8.2. It has support for the following variants: - MIPS32 O32 big endian glibc Select a MIPS generic core Disable BR2_SOFT_FLOAT - MIPS64 big endian glibc - Select a MIPS generic core + Select a MIPS64 generic core Select the n64 ABI Disable BR2_SOFT_FLOAT - MIPS32 O32 little endian glibc Select a MIPS generic core Disable BR2_SOFT_FLOAT - MIPS64 little endian glibc - Select a MIPS generic core + Select a MIPS64 generic core Select the n64 ABI Disable BR2_SOFT_FLOAT - MIPS32 big endian soft float glibc Select a MIPS generic core Select BR2_SOFT_FLOAT - MIPS64 big endian soft float glibc - Select a MIPS generic core + Select a MIPS64 generic core Select the n64 ABI Select BR2_SOFT_FLOAT - MIPS32 little endian soft float glibc Select a MIPS generic core Select BR2_SOFT_FLOAT - MIPS64 little endian soft float glibc - Select a MIPS generic core + Select a MIPS64 generic core Select the n64 ABI Select BR2_SOFT_FLOAT - MIPS32 big endian microMIPS glibc
@@ -337,8 +337,8 @@ config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS201209 - MIPS32 little endian soft float uclibc Not usable in Buildroot yet. -config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS201203 - bool "Sourcery CodeBench MIPS 2012.03" +config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS201209 + bool "Sourcery CodeBench MIPS 2012.09" depends on BR2_mips || BR2_mipsel depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86" depends on !BR2_MIPS_NABI32
@@ -349,9 +349,9 @@ config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS201203 select BR2_HOSTARCH_NEEDS_IA32_LIBS help Sourcery CodeBench toolchain for the MIPS architecture, from - Mentor Graphics. It uses gcc 4.6.3, binutils 2.21.53, glibc - 2.15, uClibc 0.9.30 and gdb 7.2.50, kernel headers - 3.2.10. It has support for the following variants: + Mentor Graphics. It uses gcc 4.7.2, binutils 2.23.51, glibc + 2.16, uClibc 0.9.30 and gdb 7.4.50, kernel headers + 3.5.4. It has support for the following variants: - MIPS32 O32 big endian glibc Select a MIPS generic core Disable BR2_SOFT_FLOAT
@@ -851,9 +851,9 @@ config BR2_TOOLCHAIN_EXTERNAL_PREFIX default "microblazeel-unknown-linux-gnu" if BR2_TOOLCHAIN_EXTERNAL_XILINX_MICROBLAZEEL_V2 default "microblaze-unknown-linux-gnu" if BR2_TOOLCHAIN_EXTERNAL_XILINX_MICROBLAZEBE_14_3 default "microblaze-unknown-linux-gnu" if BR2_TOOLCHAIN_EXTERNAL_XILINX_MICROBLAZEBE_V2 - default "mips-linux-gnu" if BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS201203 default "mips-linux-gnu" if BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS201209 default "mips-linux-gnu" if BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS201305 + default "mips-linux-gnu" if BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS201311 default "nios2-linux-gnu" if BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_NIOSII201305 default "powerpc-linux-gnu" if BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_POWERPC201009 default "powerpc-linux-gnu" if BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_POWERPC201103
toolchain/toolchain-external/toolchain-external.mk +3 -3
@@ -277,15 +277,15 @@ else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_2013_09),y) TOOLCHAIN_EXTERNAL_SITE = http://releases.linaro.org/13.09/components/toolchain/binaries/ TOOLCHAIN_EXTERNAL_SOURCE = gcc-linaro-arm-linux-gnueabihf-4.8-2013.09_linux.tar.xz TOOLCHAIN_EXTERNAL_POST_INSTALL_STAGING_HOOKS += TOOLCHAIN_EXTERNAL_LINARO_ARMHF_SYMLINK -else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS201203),y) -TOOLCHAIN_EXTERNAL_SITE = http://sourcery.mentor.com/public/gnu_toolchain/mips-linux-gnu/ -TOOLCHAIN_EXTERNAL_SOURCE = mips-2012.03-63-mips-linux-gnu-i686-pc-linux-gnu.tar.bz2 else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS201209),y) TOOLCHAIN_EXTERNAL_SITE = http://sourcery.mentor.com/public/gnu_toolchain/mips-linux-gnu/ TOOLCHAIN_EXTERNAL_SOURCE = mips-2012.09-99-mips-linux-gnu-i686-pc-linux-gnu.tar.bz2 else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS201305),y) TOOLCHAIN_EXTERNAL_SITE = http://sourcery.mentor.com/public/gnu_toolchain/mips-linux-gnu/ TOOLCHAIN_EXTERNAL_SOURCE = mips-2013.05-66-mips-linux-gnu-i686-pc-linux-gnu.tar.bz2 +else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS201311),y) +TOOLCHAIN_EXTERNAL_SITE = http://sourcery.mentor.com/public/gnu_toolchain/mips-linux-gnu/ +TOOLCHAIN_EXTERNAL_SOURCE = mips-2013.11-36-mips-linux-gnu-i686-pc-linux-gnu.tar.bz2 else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_NIOSII201305),y) TOOLCHAIN_EXTERNAL_SITE = http://sourcery.mentor.com/public/gnu_toolchain/nios2-linux-gnu/ TOOLCHAIN_EXTERNAL_SOURCE = sourceryg++-2013.05-43-nios2-linux-gnu-i686-pc-linux-gnu.tar.bz2
Signature · 1 line
1.8.3.2
PATCH 2/6 toolchain-external: add Sourcery MIPS 2013.11, remove Sourcery MIPS 2012.03
Hi Thomas,
A small nit.
Quoted 2 lines · Thomas Petazzoni
This commit adds the support for the recently release Sourcery MIPS 2013.11 toolchain (gcc 4.8, gdb 7.6, glibc 2.18, gdb 7.6), and
You mention gdb twice. The same goes for the previous patch.
baruch
Quoted 4 lines
consequently removes the support for the Sourcery MIPS 2012.03 toolchain.
Signed-off-by Thomas Petazzoni <[email protected]>
Signature · 3 lines
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -PATCH 2/6 toolchain-external: add Sourcery MIPS 2013.11, remove Sourcery MIPS 2012.03
In reply to Thomas PetazzoniThomas, All,
On 2013-12-27 12:32 +0100, Thomas Petazzoni spake thusly:
Quoted 6 lines
This commit adds the support for the recently release Sourcery MIPS 2013.11 toolchain (gcc 4.8, gdb 7.6, glibc 2.18, gdb 7.6), and consequently removes the support for the Sourcery MIPS 2012.03 toolchain.
Signed-off-by Thomas Petazzoni <[email protected]>
But see below...
toolchain/toolchain-external/Config.in
Quoted 4 lines
toolchain/toolchain-external/Config.in +0
-0
[--SNIP--]
Quoted 6 lines
toolchain/toolchain-external/Config.in +0
-2@@ -281,35 +281,35 @@ config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS201209 select BR2_HOSTARCH_NEEDS_IA32_LIBS help Sourcery CodeBench toolchain for the MIPS architecture, from - Mentor Graphics. It uses gcc 4.7.2, binutils 2.23.51, glibc - 2.16, uClibc 0.9.30 and gdb 7.4.50, kernel headers
toolchain/toolchain-external/Config.in config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS201209 · line 291
Quoted 10 lines
toolchain/toolchain-external/Config.in +4
-2- 3.5.4. It has support for the following variants: + Mentor Graphics. It uses gcc 4.7.3, binutils 2.23.52, glibc + 2.17, uClibc 0.9.30 and gdb 7.4.50, kernel headers + 3.8.2. It has support for the following variants: - MIPS32 O32 big endian glibc Select a MIPS generic core Disable BR2_SOFT_FLOAT - MIPS64 big endian glibc - Select a MIPS generic core + Select a MIPS64 generic core
Looks like you're fixing help at the same time, too. Maybe jsut add a small sentence to the commit log:
Fix help texts about MIPS64 inconsistencies.
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 3/6 toolchain-external: update Linaro ARM toolchains
In reply to Thomas PetazzoniAdd Linaro ARM 2013.10 and Linaro ARM 2013.11, and remove Linaro ARM 2013.07 and Linaro ARM 2013.08.
The main change for those versions is the switch to eglibc 2.18.
--- toolchain/toolchain-external/Config.in | 26 +++++++++++----------- toolchain/toolchain-external/toolchain-external.mk | 16 ++++++------- 2 files changed, 21 insertions(+), 21 deletions(-)
toolchain/toolchain-external/Config.in +13 -13
@@ -6,8 +6,8 @@ choice comment "(e)glibc toolchains only available with shared lib support" depends on BR2_PREFER_STATIC_LIB -config BR2_TOOLCHAIN_EXTERNAL_LINARO_2013_09 - bool "Linaro 2013.09" +config BR2_TOOLCHAIN_EXTERNAL_LINARO_2013_11 + bool "Linaro 2013.11" depends on BR2_arm depends on BR2_GCC_TARGET_ARCH = "armv7-a" depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86"
@@ -19,8 +19,8 @@ config BR2_TOOLCHAIN_EXTERNAL_LINARO_2013_09 select BR2_HOSTARCH_NEEDS_IA32_LIBS help Linaro toolchain for the ARM architecture. It uses Linaro - GCC 2013.09 (based on gcc 4.8), Linaro GDB 2013.05 (based on - GDB 7.6), eglibc 2.17, Binutils 2013.06 (based on 2.23). It + GCC 2013.11 (based on gcc 4.8), Linaro GDB 2013.10 (based on + GDB 7.6), eglibc 2.18, Binutils 2013.10 (based on 2.23). It generates code that runs on all Cortex-A profile devices, but tuned for the Cortex-A9. The code generated is Thumb 2, with the hard floating point calling convention, and uses
@@ -28,8 +28,8 @@ config BR2_TOOLCHAIN_EXTERNAL_LINARO_2013_09 To use this toolchain, you must disable soft float usage. -config BR2_TOOLCHAIN_EXTERNAL_LINARO_2013_08 - bool "Linaro 2013.08" +config BR2_TOOLCHAIN_EXTERNAL_LINARO_2013_10 + bool "Linaro 2013.10" depends on BR2_arm depends on BR2_GCC_TARGET_ARCH = "armv7-a" depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86"
@@ -41,8 +41,8 @@ config BR2_TOOLCHAIN_EXTERNAL_LINARO_2013_08 select BR2_HOSTARCH_NEEDS_IA32_LIBS help Linaro toolchain for the ARM architecture. It uses Linaro - GCC 2013.08 (based on gcc 4.8), Linaro GDB 2013.05 (based on - GDB 7.6), eglibc 2.17, Binutils 2013.06 (based on 2.23). It + GCC 2013.10 (based on gcc 4.8), Linaro GDB 2013.10 (based on + GDB 7.6), eglibc 2.18, Binutils 2013.10 (based on 2.23). It generates code that runs on all Cortex-A profile devices, but tuned for the Cortex-A9. The code generated is Thumb 2, with the hard floating point calling convention, and uses
@@ -50,8 +50,8 @@ config BR2_TOOLCHAIN_EXTERNAL_LINARO_2013_08 To use this toolchain, you must disable soft float usage. -config BR2_TOOLCHAIN_EXTERNAL_LINARO_2013_07 - bool "Linaro 2013.07" +config BR2_TOOLCHAIN_EXTERNAL_LINARO_2013_09 + bool "Linaro 2013.09" depends on BR2_arm depends on BR2_GCC_TARGET_ARCH = "armv7-a" depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86"
@@ -63,7 +63,7 @@ config BR2_TOOLCHAIN_EXTERNAL_LINARO_2013_07 select BR2_HOSTARCH_NEEDS_IA32_LIBS help Linaro toolchain for the ARM architecture. It uses Linaro - GCC 2013.07 (based on gcc 4.8), Linaro GDB 2013.05 (based on + GCC 2013.09 (based on gcc 4.8), Linaro GDB 2013.05 (based on GDB 7.6), eglibc 2.17, Binutils 2013.06 (based on 2.23). It generates code that runs on all Cortex-A profile devices, but tuned for the Cortex-A9. The code generated is Thumb 2,
@@ -836,9 +836,9 @@ config BR2_TOOLCHAIN_EXTERNAL_CUSTOM_PREFIX config BR2_TOOLCHAIN_EXTERNAL_PREFIX string + default "arm-linux-gnueabihf" if BR2_TOOLCHAIN_EXTERNAL_LINARO_2013_11 + default "arm-linux-gnueabihf" if BR2_TOOLCHAIN_EXTERNAL_LINARO_2013_10 default "arm-linux-gnueabihf" if BR2_TOOLCHAIN_EXTERNAL_LINARO_2013_09 - default "arm-linux-gnueabihf" if BR2_TOOLCHAIN_EXTERNAL_LINARO_2013_08 - default "arm-linux-gnueabihf" if BR2_TOOLCHAIN_EXTERNAL_LINARO_2013_07 default "arm-none-linux-gnueabi" if BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201203 default "arm-none-linux-gnueabi" if BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201305 default "arm-none-linux-gnueabi" if BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201311
toolchain/toolchain-external/toolchain-external.mk +8 -8
@@ -265,18 +265,18 @@ define TOOLCHAIN_EXTERNAL_FIXUP_CMDS mv $(TOOLCHAIN_EXTERNAL_INSTALL_DIR)/arago-2011.09/armv5te/* $(TOOLCHAIN_EXTERNAL_INSTALL_DIR)/ rm -rf $(TOOLCHAIN_EXTERNAL_INSTALL_DIR)/arago-2011.09/ endef -else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_2013_07),y) -TOOLCHAIN_EXTERNAL_SITE = http://releases.linaro.org/13.07/components/toolchain/binaries/ -TOOLCHAIN_EXTERNAL_SOURCE = gcc-linaro-arm-linux-gnueabihf-4.8-2013.07-1_linux.tar.xz -TOOLCHAIN_EXTERNAL_POST_INSTALL_STAGING_HOOKS += TOOLCHAIN_EXTERNAL_LINARO_ARMHF_SYMLINK -else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_2013_08),y) -TOOLCHAIN_EXTERNAL_SITE = http://releases.linaro.org/13.08/components/toolchain/binaries/ -TOOLCHAIN_EXTERNAL_SOURCE = gcc-linaro-arm-linux-gnueabihf-4.8-2013.08_linux.tar.xz -TOOLCHAIN_EXTERNAL_POST_INSTALL_STAGING_HOOKS += TOOLCHAIN_EXTERNAL_LINARO_ARMHF_SYMLINK else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_2013_09),y) TOOLCHAIN_EXTERNAL_SITE = http://releases.linaro.org/13.09/components/toolchain/binaries/ TOOLCHAIN_EXTERNAL_SOURCE = gcc-linaro-arm-linux-gnueabihf-4.8-2013.09_linux.tar.xz TOOLCHAIN_EXTERNAL_POST_INSTALL_STAGING_HOOKS += TOOLCHAIN_EXTERNAL_LINARO_ARMHF_SYMLINK +else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_2013_10),y) +TOOLCHAIN_EXTERNAL_SITE = http://releases.linaro.org/13.10/components/toolchain/binaries/ +TOOLCHAIN_EXTERNAL_SOURCE = gcc-linaro-arm-linux-gnueabihf-4.8-2013.10_linux.tar.xz +TOOLCHAIN_EXTERNAL_POST_INSTALL_STAGING_HOOKS += TOOLCHAIN_EXTERNAL_LINARO_ARMHF_SYMLINK +else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_2013_11),y) +TOOLCHAIN_EXTERNAL_SITE = http://releases.linaro.org/13.11/components/toolchain/binaries/ +TOOLCHAIN_EXTERNAL_SOURCE = gcc-linaro-arm-linux-gnueabihf-4.8-2013.11_linux.tar.xz +TOOLCHAIN_EXTERNAL_POST_INSTALL_STAGING_HOOKS += TOOLCHAIN_EXTERNAL_LINARO_ARMHF_SYMLINK else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS201209),y) TOOLCHAIN_EXTERNAL_SITE = http://sourcery.mentor.com/public/gnu_toolchain/mips-linux-gnu/ TOOLCHAIN_EXTERNAL_SOURCE = mips-2012.09-99-mips-linux-gnu-i686-pc-linux-gnu.tar.bz2
Signature · 1 line
1.8.3.2
PATCH 4/6 toolchain-external: update Linaro AArch64 toolchains
In reply to Thomas PetazzoniAdd Linaro AArch64 2013.10 and Linaro AArch64 2013.11, and remove Linaro AArch64 2013.07 and Linaro AArch64 2013.08.
--- toolchain/toolchain-external/Config.in | 16 ++++++++-------- toolchain/toolchain-external/toolchain-external.mk | 12 ++++++------ 2 files changed, 14 insertions(+), 14 deletions(-)
toolchain/toolchain-external/Config.in +8 -8
@@ -747,8 +747,8 @@ config BR2_TOOLCHAIN_EXTERNAL_XILINX_MICROBLAZEBE_V2 Toolchain for the Microblaze architecture, from http://wiki.xilinx.com/mb-gnu-tools -config BR2_TOOLCHAIN_EXTERNAL_LINARO_AARCH64_13_09 - bool "Linaro AArch64 13.09" +config BR2_TOOLCHAIN_EXTERNAL_LINARO_AARCH64_13_11 + bool "Linaro AArch64 13.11" depends on BR2_aarch64 depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86" depends on !BR2_PREFER_STATIC_LIB
@@ -760,8 +760,8 @@ config BR2_TOOLCHAIN_EXTERNAL_LINARO_AARCH64_13_09 Toolchain for the AArch64 architecture, from http://www.linaro.org/engineering/armv8/ -config BR2_TOOLCHAIN_EXTERNAL_LINARO_AARCH64_13_08 - bool "Linaro AArch64 13.08" +config BR2_TOOLCHAIN_EXTERNAL_LINARO_AARCH64_13_10 + bool "Linaro AArch64 13.10" depends on BR2_aarch64 depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86" depends on !BR2_PREFER_STATIC_LIB
@@ -773,8 +773,8 @@ config BR2_TOOLCHAIN_EXTERNAL_LINARO_AARCH64_13_08 Toolchain for the AArch64 architecture, from http://www.linaro.org/engineering/armv8/ -config BR2_TOOLCHAIN_EXTERNAL_LINARO_AARCH64_13_07 - bool "Linaro AArch64 13.07" +config BR2_TOOLCHAIN_EXTERNAL_LINARO_AARCH64_13_09 + bool "Linaro AArch64 13.09" depends on BR2_aarch64 depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86" depends on !BR2_PREFER_STATIC_LIB
@@ -844,9 +844,9 @@ config BR2_TOOLCHAIN_EXTERNAL_PREFIX default "arm-none-linux-gnueabi" if BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201311 default "arm-arago-linux-gnueabi" if BR2_TOOLCHAIN_EXTERNAL_ARAGO_ARMV7A_201109 default "arm-arago-linux-gnueabi" if BR2_TOOLCHAIN_EXTERNAL_ARAGO_ARMV5TE_201109 + default "aarch64-linux-gnu" if BR2_TOOLCHAIN_EXTERNAL_LINARO_AARCH64_13_11 + default "aarch64-linux-gnu" if BR2_TOOLCHAIN_EXTERNAL_LINARO_AARCH64_13_10 default "aarch64-linux-gnu" if BR2_TOOLCHAIN_EXTERNAL_LINARO_AARCH64_13_09 - default "aarch64-linux-gnu" if BR2_TOOLCHAIN_EXTERNAL_LINARO_AARCH64_13_08 - default "aarch64-linux-gnu" if BR2_TOOLCHAIN_EXTERNAL_LINARO_AARCH64_13_07 default "microblazeel-unknown-linux-gnu" if BR2_TOOLCHAIN_EXTERNAL_XILINX_MICROBLAZEEL_14_3 default "microblazeel-unknown-linux-gnu" if BR2_TOOLCHAIN_EXTERNAL_XILINX_MICROBLAZEEL_V2 default "microblaze-unknown-linux-gnu" if BR2_TOOLCHAIN_EXTERNAL_XILINX_MICROBLAZEBE_14_3
toolchain/toolchain-external/toolchain-external.mk +6 -6
@@ -339,15 +339,15 @@ TOOLCHAIN_EXTERNAL_SOURCE = lin32-microblaze-unknown-linux-gnu_14.3_early.tar.xz else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_XILINX_MICROBLAZEBE_V2),y) TOOLCHAIN_EXTERNAL_SITE = http://sources.buildroot.net/ TOOLCHAIN_EXTERNAL_SOURCE = microblaze-unknown-linux-gnu.tgz -else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_AARCH64_13_07),y) -TOOLCHAIN_EXTERNAL_SITE = http://releases.linaro.org/13.07/components/toolchain/binaries/ -TOOLCHAIN_EXTERNAL_SOURCE = gcc-linaro-aarch64-linux-gnu-4.8-2013.07-1_linux.tar.xz -else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_AARCH64_13_08),y) -TOOLCHAIN_EXTERNAL_SITE = http://releases.linaro.org/13.08/components/toolchain/binaries/ -TOOLCHAIN_EXTERNAL_SOURCE = gcc-linaro-aarch64-linux-gnu-4.8-2013.08_linux.tar.xz else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_AARCH64_13_09),y) TOOLCHAIN_EXTERNAL_SITE = http://releases.linaro.org/13.09/components/toolchain/binaries/ TOOLCHAIN_EXTERNAL_SOURCE = gcc-linaro-aarch64-linux-gnu-4.8-2013.09_linux.tar.xz +else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_AARCH64_13_10),y) +TOOLCHAIN_EXTERNAL_SITE = http://releases.linaro.org/13.10/components/toolchain/binaries/ +TOOLCHAIN_EXTERNAL_SOURCE = gcc-linaro-aarch64-linux-gnu-4.8-2013.10-1_linux.tar.xz +else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_AARCH64_13_11),y) +TOOLCHAIN_EXTERNAL_SITE = http://releases.linaro.org/13.11/components/toolchain/binaries/ +TOOLCHAIN_EXTERNAL_SOURCE = gcc-linaro-aarch64-linux-gnu-4.8-2013.11_linux.tar.xz else # Custom toolchain TOOLCHAIN_EXTERNAL_SITE = $(dir $(call qstrip,$(BR2_TOOLCHAIN_EXTERNAL_URL)))
Signature · 1 line
1.8.3.2
PATCH 4/6 toolchain-external: update Linaro AArch64 toolchains
Thomas, All,
On 2013-12-27 12:32 +0100, Thomas Petazzoni spake thusly:
Quoted 4 lines
Add Linaro AArch64 2013.10 and Linaro AArch64 2013.11, and remove Linaro AArch64 2013.07 and Linaro AArch64 2013.08.
Signed-off-by Thomas Petazzoni <[email protected]>
But see below, unrelated comment...
[--SNIP--]
Quoted 16 lines
toolchain/toolchain-external/toolchain-external.mk +0
-6@@ -339,15 +339,15 @@ TOOLCHAIN_EXTERNAL_SOURCE = lin32-microblaze-unknown-linux-gnu_14.3_early.tar.xz else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_XILINX_MICROBLAZEBE_V2),y) TOOLCHAIN_EXTERNAL_SITE = http://sources.buildroot.net/ TOOLCHAIN_EXTERNAL_SOURCE = microblaze-unknown-linux-gnu.tgz -else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_AARCH64_13_07),y) -TOOLCHAIN_EXTERNAL_SITE = http://releases.linaro.org/13.07/components/toolchain/binaries/ -TOOLCHAIN_EXTERNAL_SOURCE = gcc-linaro-aarch64-linux-gnu-4.8-2013.07-1_linux.tar.xz -else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_AARCH64_13_08),y) -TOOLCHAIN_EXTERNAL_SITE = http://releases.linaro.org/13.08/components/toolchain/binaries/ -TOOLCHAIN_EXTERNAL_SOURCE = gcc-linaro-aarch64-linux-gnu-4.8-2013.08_linux.tar.xz else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_AARCH64_13_09),y) TOOLCHAIN_EXTERNAL_SITE = http://releases.linaro.org/13.09/components/toolchain/binaries/
toolchain/toolchain-external/toolchain-external.mk TOOLCHAIN_EXTERNAL_SOURCE = lin32-microblaze-unknown-linux-gnu_14.3_early.tar.xz · line 353
Quoted 10 lines
toolchain/toolchain-external/toolchain-external.mk +6
-0TOOLCHAIN_EXTERNAL_SOURCE = gcc-linaro-aarch64-linux-gnu-4.8-2013.09_linux.tar.xz +else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_AARCH64_13_10),y) +TOOLCHAIN_EXTERNAL_SITE = http://releases.linaro.org/13.10/components/toolchain/binaries/ +TOOLCHAIN_EXTERNAL_SOURCE = gcc-linaro-aarch64-linux-gnu-4.8-2013.10-1_linux.tar.xz +else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_AARCH64_13_11),y) +TOOLCHAIN_EXTERNAL_SITE = http://releases.linaro.org/13.11/components/toolchain/binaries/ +TOOLCHAIN_EXTERNAL_SOURCE = gcc-linaro-aarch64-linux-gnu-4.8-2013.11_linux.tar.xz else # Custom toolchain TOOLCHAIN_EXTERNAL_SITE = $(dir $(call qstrip,$(BR2_TOOLCHAIN_EXTERNAL_URL)))
I find it odd that the menu are listed with reverse order, most recent first, while the Makefiles are listed in order, oldest first. This applies to all toolchains, not only the Linaro ones.
Of course, this is not the fault of this patch, as you kept the previous order. So it does not bar you from applying it.
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 4/6 toolchain-external: update Linaro AArch64 toolchains
In reply to Thomas PetazzoniHi Thomas,
Quoted 4 lines · Thomas Petazzoni
Add Linaro AArch64 2013.10 and Linaro AArch64 2013.11, and remove Linaro AArch64 2013.07 and Linaro AArch64 2013.08.
Signed-off-by Thomas Petazzoni <[email protected]>
A while back we discussed the desirability of having so many subsequent versions of the same toolchain type (in this case Linaro). IIRC (but I did not cross-check with the actual discussion yet) the conclusion was that it'd be good to use the gcc version as milestone, and keep e.g. a 4.4, 4.6, 4.8 gcc based Linaro toolchain, but not keep multiple 4.8-based versions.
Until now this has not yet been implemented. We could do this in a one-shot approach, or gradually as new toolchains are added. If we opt for the second option, your current patchset could be revised to align with the new strategy.
What do you think about that?
Best regards,
Thomas
PATCH 4/6 toolchain-external: update Linaro AArch64 toolchains
Dear Thomas De Schampheleire,
Quoted 14 lines · Thomas De Schampheleire
Quoted 4 lines · Thomas Petazzoni
Add Linaro AArch64 2013.10 and Linaro AArch64 2013.11, and remove Linaro AArch64 2013.07 and Linaro AArch64 2013.08.
Signed-off-by Thomas Petazzoni <[email protected]>A while back we discussed the desirability of having so many subsequent versions of the same toolchain type (in this case Linaro). IIRC (but I did not cross-check with the actual discussion yet) the conclusion was that it'd be good to use the gcc version as milestone, and keep e.g. a 4.4, 4.6, 4.8 gcc based Linaro toolchain, but not keep multiple 4.8-based versions.
Quoted 6 lines
Until now this has not yet been implemented. We could do this in a one-shot approach, or gradually as new toolchains are added. If we opt for the second option, your current patchset could be revised to align with the new strategy.
What do you think about that?
I continue to think that it doesn't work, as I already expressed originally. Using the gcc version as a way of keeping different generations of toolchain is, in my opinion, broken: in the present update of the ARM Linaro toolchain, we continue to have only gcc 4.8 based toolchains, but the newer ones are based on eglibc 2.18, while the previous ones are based on eglibc 2.17. This is a fairly significant difference, but if we use only the gcc version as the way of distinguishing generations of toolchain, then we would get rid of gcc 4.8/eglibc 2.17 toolchains today.
Why would we keep a very old gcc 4.7.x toolchain, but immediately get rid of a more recent gcc 4.8 toolchain that is based on eglibc 2.17 ?
As we never managed to come up with a reasonable model to handle this, I believe we should in the mean time continue to update the toolchains as we used to do in the past.
Thanks!
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
PATCH 4/6 toolchain-external: update Linaro AArch64 toolchains
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Thomas" == Thomas Petazzoni <[email protected]> writes:
Hi,
Quoted 6 lines
Why would we keep a very old gcc 4.7.x toolchain, but immediately get rid of a more recent gcc 4.8 toolchain that is based on eglibc 2.17 ?
As we never managed to come up with a reasonable model to handle this, I believe we should in the mean time continue to update the toolchains as we used to do in the past.
Agreed.
Signature · 1 line
Bye, Peter Korsgaard
PATCH 4/6 toolchain-external: update Linaro AArch64 toolchains
Hi,
Quoted 4 lines · Peter Korsgaard
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Thomas" == Thomas Petazzoni <[email protected]> writes:
Hi,
Quoted 8 lines
Quoted 6 lines
Why would we keep a very old gcc 4.7.x toolchain, but immediately get rid of a more recent gcc 4.8 toolchain that is based on eglibc 2.17 ?
As we never managed to come up with a reasonable model to handle this, I believe we should in the mean time continue to update the toolchains as we used to do in the past.
Agreed.
While I agree that the existing patchset could continue in the meanwhile, I think it is worth revisiting the core discussion. For reference, here is the previous discussion:
http://lists.busybox.net/pipermail/buildroot/2013-October/080119.html
Back then (October) there was not much debate about the idea of only providing sufficiently-different versions of the Linaro toolchains. The biggest problem was how to identify the toolchains so that 'minor' updates can keep the same config symbol (and thus be transparent to users). This boils down to the question: which parts of the toolchain may change to continue considering it as 'the same' toolchain. I think everyone will agree that a new gcc version or a new C library version means a different toolchain.
However, what about the other parts? If Linaro updates binutils, do we consider it the same toolchain or not?
Based on this we could devise some logical names of the config symbols. Note that this does not mean we can't change our minds later. Suppose we start with the gcc/libc combination as key, and we'd have symbols LINARO_GCC_4_8_GLIBC_2_17LINARO_GCC_4_8_GLIBC_2_18LINARO_GCC_5_0_GLIBC_2_18
and suddenly Linaro releases a toolchain with the same gcc and glibc version, but some other change that we consider as significant. Then at that point we can simply introduce a new symbol and keep both, for example:LINARO_GCC_4_8_GLIBC_2_17LINARO_GCC_4_8_GLIBC_2_18LINARO_GCC_5_0_GLIBC_2_18 LINARO_GCC_5_0_GLIBC_2_18_OTHER_FEATURE
Does this make sense? Did I overlook something?
Thanks,
Thomas
PATCH 4/6 toolchain-external: update Linaro AArch64 toolchains
Dear Thomas De Schampheleire,
Happy new year!
Quoted 32 lines · Thomas De Schampheleire
While I agree that the existing patchset could continue in the meanwhile, I think it is worth revisiting the core discussion. For reference, here is the previous discussion:
http://lists.busybox.net/pipermail/buildroot/2013-October/080119.htmlBack then (October) there was not much debate about the idea of only providing sufficiently-different versions of the Linaro toolchains. The biggest problem was how to identify the toolchains so that 'minor' updates can keep the same config symbol (and thus be transparent to users). This boils down to the question: which parts of the toolchain may change to continue considering it as 'the same' toolchain. I think everyone will agree that a new gcc version or a new C library version means a different toolchain.
However, what about the other parts? If Linaro updates binutils, do we consider it the same toolchain or not?Based on this we could devise some logical names of the config symbols. Note that this does not mean we can't change our minds later. Suppose we start with the gcc/libc combination as key, and we'd have symbols
LINARO_GCC_4_8_GLIBC_2_17LINARO_GCC_4_8_GLIBC_2_18LINARO_GCC_5_0_GLIBC_2_18and suddenly Linaro releases a toolchain with the same gcc and glibc version, but some other change that we consider as significant. Then at that point we can simply introduce a new symbol and keep both, for example:
LINARO_GCC_4_8_GLIBC_2_17LINARO_GCC_4_8_GLIBC_2_18LINARO_GCC_5_0_GLIBC_2_18LINARO_GCC_5_0_GLIBC_2_18_OTHER_FEATURE
Quoted 1 line
Does this make sense? Did I overlook something?
My personal view on this is that I still don't really understand what is the problem with the current naming scheme. If an user upgrades from one Buildroot version to another then the version of all components *are* changing, without changes to the corresponding Config.in symbol. You update Buildroot, then suddenly you get Qt 5.2 instead of Qt 5.1, without being notified. At the next Buildroot upgrade, you may still be using Qt 5.2, or Qt 5.2.1, or Qt 5.3, or 5.4. You have to verify it.
With Linaro toolchains, if you use Linaro 2013.02 in your Buildroot configuration, then update to a new Buildroot version that still has Linaro 2013.02, then you will continue to use this toolchain. However, if Buildroot has updated a number of Linaro toolchains, and 2013.02 is no longer available, you will automatically default to the latest Linaro toolchain that exists for your architecture, maybe 2013.06 or 2013.07.
What's the difference with Qt? I don't see any, to be honest.
Best regards,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
PATCH 4/6 toolchain-external: update Linaro AArch64 toolchains
Hi Thomas,
Quoted 3 lines · Thomas Petazzoni
Dear Thomas De Schampheleire,
Happy new year!
I should have started with that :)
Thanks, same to you and to all buildroot users/developers!
Quoted 53 lines · Thomas De Schampheleire
Quoted 33 lines
While I agree that the existing patchset could continue in the meanwhile, I think it is worth revisiting the core discussion. For reference, here is the previous discussion:
http://lists.busybox.net/pipermail/buildroot/2013-October/080119.htmlBack then (October) there was not much debate about the idea of only providing sufficiently-different versions of the Linaro toolchains. The biggest problem was how to identify the toolchains so that 'minor' updates can keep the same config symbol (and thus be transparent to users). This boils down to the question: which parts of the toolchain may change to continue considering it as 'the same' toolchain. I think everyone will agree that a new gcc version or a new C library version means a different toolchain.
However, what about the other parts? If Linaro updates binutils, do we consider it the same toolchain or not?Based on this we could devise some logical names of the config symbols. Note that this does not mean we can't change our minds later. Suppose we start with the gcc/libc combination as key, and we'd have symbols
LINARO_GCC_4_8_GLIBC_2_17LINARO_GCC_4_8_GLIBC_2_18LINARO_GCC_5_0_GLIBC_2_18and suddenly Linaro releases a toolchain with the same gcc and glibc version, but some other change that we consider as significant. Then at that point we can simply introduce a new symbol and keep both, for example:
LINARO_GCC_4_8_GLIBC_2_17LINARO_GCC_4_8_GLIBC_2_18LINARO_GCC_5_0_GLIBC_2_18LINARO_GCC_5_0_GLIBC_2_18_OTHER_FEATUREQuoted 1 line
Does this make sense? Did I overlook something?
My personal view on this is that I still don't really understand what is the problem with the current naming scheme. If an user upgrades from one Buildroot version to another then the version of all components *are* changing, without changes to the corresponding Config.in symbol. You update Buildroot, then suddenly you get Qt 5.2 instead of Qt 5.1, without being notified. At the next Buildroot upgrade, you may still be using Qt 5.2, or Qt 5.2.1, or Qt 5.3, or 5.4. You have to verify it.
With Linaro toolchains, if you use Linaro 2013.02 in your Buildroot configuration, then update to a new Buildroot version that still has Linaro 2013.02, then you will continue to use this toolchain. However, if Buildroot has updated a number of Linaro toolchains, and 2013.02 is no longer available, you will automatically default to the latest Linaro toolchain that exists for your architecture, maybe 2013.06 or 2013.07.
Quoted 1 line
What's the difference with Qt? I don't see any, to be honest.
One big difference is that for qt5 you cannot select the version, you just say "I want qt5".
For the external toolchains, you specify a particular version, out of a set of provided versions.
The problem arises when we introduce support for a newer version. For qt5 (and most packages) we simply replace the old version with the new one. No notification. No migration.
For toolchains (and some other packages) we add the new version, and typically remove one or more old versions. The question is now: which toolchains to remove?
- The oldest one? This is the approach taken currently for Linaro toolchains.
- The latest, most similar one?
For Sourcery toolchains, there are versions and patch levels. The introduction of a toolchain version 2013.11 patchlevel 50 will overwrite the previous toolchain 2013.11 patchlevel 40 (just an example). We don't keep two patchlevels of the same toolchain version. For Linaro, there are no real patchlevels (as far as I understood, I'm no expert there) but they call everything a new 'version'. Thus, the Linaro toolchains are released much more frequently than for Sourcery toolchains. This blend of the version and patchlevel is the cause of this discussion, I believe.
Two subsequent Linaro releases could be considered as two different versions, or as one version but different patchlevel (in Sourcery terminology). The classification used would determine what to do with the buildroot config symbols (which ones to add and which to remove).
If it's a new 'version' we'd remove the oldest existing version and add the new one.
If it's a new 'patchlevel', we'd remove the most recent toolchain of the same 'version' (same combination of most important components) but different 'patchlevel'.
This approach more or less requires different names of the config symbols, unless we'd accept that config symbol LINARO_2013.11 could actually install Linaro 2013.12 (example only).
Best regards,
Thomas
PATCH 5/6 toolchain-external: mark Microblaze external toolchains as deprecated
In reply to Thomas PetazzoniThe Xilinx Microblaze external toolchains that we had support for are very old, and are causing a huge number of build issues. Thanks to Spenser Gilliland, we now have support for Microblaze in the internal toolchain backend, and the autobuilders have been using the internal toolchain backend since then. Therefore, it's time to deprecate those old and unusable external toolchains.
--- toolchain/toolchain-external/Config.in | 4 ++++ 1 file changed, 4 insertions(+)
toolchain/toolchain-external/Config.in +4 -0
@@ -704,6 +704,7 @@ config BR2_TOOLCHAIN_EXTERNAL_XILINX_MICROBLAZEEL_14_3 depends on BR2_microblazeel depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86" depends on !BR2_PREFER_STATIC_LIB + depends on BR2_DEPRECATED select BR2_TOOLCHAIN_EXTERNAL_GLIBC select BR2_TOOLCHAIN_HAS_NATIVE_RPC select BR2_HOSTARCH_NEEDS_IA32_LIBS
@@ -717,6 +718,7 @@ config BR2_TOOLCHAIN_EXTERNAL_XILINX_MICROBLAZEEL_V2 depends on BR2_microblazeel depends on BR2_HOSTARCH = "x86_64" depends on !BR2_PREFER_STATIC_LIB + depends on BR2_DEPRECATED select BR2_TOOLCHAIN_EXTERNAL_GLIBC select BR2_TOOLCHAIN_HAS_NATIVE_RPC help
@@ -728,6 +730,7 @@ config BR2_TOOLCHAIN_EXTERNAL_XILINX_MICROBLAZEBE_14_3 depends on BR2_microblazebe depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86" depends on !BR2_PREFER_STATIC_LIB + depends on BR2_DEPRECATED select BR2_TOOLCHAIN_EXTERNAL_GLIBC select BR2_TOOLCHAIN_HAS_NATIVE_RPC select BR2_HOSTARCH_NEEDS_IA32_LIBS
@@ -741,6 +744,7 @@ config BR2_TOOLCHAIN_EXTERNAL_XILINX_MICROBLAZEBE_V2 depends on BR2_microblazebe depends on BR2_HOSTARCH = "x86_64" depends on !BR2_PREFER_STATIC_LIB + depends on BR2_DEPRECATED select BR2_TOOLCHAIN_EXTERNAL_GLIBC select BR2_TOOLCHAIN_HAS_NATIVE_RPC help
Signature · 1 line
1.8.3.2
PATCH 5/6 toolchain-external: mark Microblaze external toolchains as deprecated
Thomas, All,
On 2013-12-27 12:32 +0100, Thomas Petazzoni spake thusly:
Quoted 8 lines
The Xilinx Microblaze external toolchains that we had support for are very old, and are causing a huge number of build issues. Thanks to Spenser Gilliland, we now have support for Microblaze in the internal toolchain backend, and the autobuilders have been using the internal toolchain backend since then. Therefore, it's time to deprecate those old and unusable external toolchains.
Signed-off-by Thomas Petazzoni <[email protected]>
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 6/6 toolchain-external: add support for the Blackfin 2013R1 toolchain
In reply to Thomas Petazzoni--- toolchain/toolchain-external/Config.in | 19 +++++++++++++++++++ toolchain/toolchain-external/toolchain-external.mk | 6 +++++- 2 files changed, 24 insertions(+), 1 deletion(-)
toolchain/toolchain-external/Config.in +19 -0
@@ -665,6 +665,23 @@ config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_X86_201109 Other architecture variants (beyond Pentium-4/Xeon) are supported as well, but glibc is not optimised for it. +config BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2013R1 + bool "Blackfin.uclinux.org 2013R1" + depends on BR2_bfin + depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86" + select BR2_TOOLCHAIN_EXTERNAL_UCLIBC + select BR2_INSTALL_LIBSTDCPP + select BR2_LARGEFILE + select BR2_INET_IPV6 + select BR2_TOOLCHAIN_HAS_NATIVE_RPC + select BR2_USE_WCHAR + select BR2_TOOLCHAIN_HAS_THREADS + select BR2_TOOLCHAIN_HAS_THREADS_DEBUG + select BR2_HOSTARCH_NEEDS_IA32_LIBS + help + Toolchain for the Blackfin architecture, from + http://blackfin.uclinux.org. + config BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2012R2 bool "Blackfin.uclinux.org 2012R2-RC2" depends on BR2_bfin
@@ -873,6 +890,8 @@ config BR2_TOOLCHAIN_EXTERNAL_PREFIX default "bfin-linux-uclibc" if BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2012R1 && BR2_BINFMT_FDPIC default "bfin-uclinux" if BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2012R2 && BR2_BINFMT_FLAT default "bfin-linux-uclibc" if BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2012R2 && BR2_BINFMT_FDPIC + default "bfin-uclinux" if BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2013R1 && BR2_BINFMT_FLAT + default "bfin-linux-uclibc" if BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2013R1 && BR2_BINFMT_FDPIC default BR2_TOOLCHAIN_EXTERNAL_CUSTOM_PREFIX \ if BR2_TOOLCHAIN_EXTERNAL_CUSTOM
toolchain/toolchain-external/toolchain-external.mk +5 -1
@@ -327,6 +327,10 @@ else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2012R2),y) TOOLCHAIN_EXTERNAL_SITE = http://downloads.sourceforge.net/project/adi-toolchain/2012R2/2012R2-RC2/i386/ TOOLCHAIN_EXTERNAL_SOURCE = blackfin-toolchain-2012R2-RC2.i386.tar.bz2 TOOLCHAIN_EXTERNAL_EXTRA_DOWNLOADS = blackfin-toolchain-uclibc-full-2012R2-RC2.i386.tar.bz2 +else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2013R1),y) +TOOLCHAIN_EXTERNAL_SITE = http://downloads.sourceforge.net/project/adi-toolchain/2013R1/2013R1-RC1/i386/ +TOOLCHAIN_EXTERNAL_SOURCE = blackfin-toolchain-2013R1-RC1.i386.tar.bz2 +TOOLCHAIN_EXTERNAL_EXTRA_DOWNLOADS = blackfin-toolchain-uclibc-full-2013R1-RC1.i386.tar.bz2 else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_XILINX_MICROBLAZEEL_14_3),y) TOOLCHAIN_EXTERNAL_SITE = http://sources.buildroot.net/ TOOLCHAIN_EXTERNAL_SOURCE = lin32-microblazeel-unknown-linux-gnu_14.3_early.tar.xz
@@ -364,7 +368,7 @@ endif TOOLCHAIN_EXTERNAL_INSTALL_STAGING = YES -ifeq ($(BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2012R1)$(BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2012R2),y) +ifeq ($(BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2012R1)$(BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2012R2)$(BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2013R1),y) # Special handling for Blackfin toolchain, because of the split in two # tarballs, and the organization of tarball contents. The tarballs # contain ./opt/uClinux/{bfin-uclinux,bfin-linux-uclibc} directories,
Signature · 1 line
1.8.3.2
PATCH 6/6 toolchain-external: add support for the Blackfin 2013R1 toolchain
Thomas, All,
On 2013-12-27 12:32 +0100, Thomas Petazzoni spake thusly:
Quoted 1 line
Signed-off-by Thomas Petazzoni <[email protected]>
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. | '------------------------------^-------^------------------^--------------------'