buildman: README: add links for toolchains not available on kernel.org
PATCH 1/1 buildman: README: add links for toolchains not available on kernel.org
Add links for toolchains not available on kernel.org.
The sh4 toolchains from kernel.org dose not work for some boards, so use the sh from Sourcery.
--- tools/buildman/README | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-)
tools/buildman/README +17 -1
@@ -156,7 +156,6 @@ aarch64: /opt/linaro/gcc-linaro-aarch64-none-elf-4.8-2013.10_linux [toolchain-alias] x86: i386 blackfin: bfin -sh: sh4 nds32: nds32le openrisc: or32
@@ -341,6 +340,23 @@ Testing - found '/home/sjg/.buildman-toolchains/gcc-4.5.1-nolibc/or32-linux/bin/or32-linux-gcc' Tool chain test: OK +Or download them all from kernel.org and move them to /toolchains directory, + +$ for i in aarch64 arm avr32 i386 m68k microblaze mips or32 powerpc sparc + do + ./tools/buildman/buildman --fetch-arch $i + done +$ mkdir -p /toolchains +$ mv ~/.buildman-toolchains/*/* /toolchains/ + +For those not available from kernel.org, download from the following links, + +arc: https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/releases/ +blackfin: http://sourceforge.net/projects/adi-toolchain/files/ +nds32: http://osdk.andestech.com/packages/nds32le-linux-glibc-v1.tgz +nios2: http://sourcery.mentor.com/public/gnu_toolchain/nios2-linux-gnu/ +sh: http://sourcery.mentor.com/public/gnu_toolchain/sh-linux-gnu/ + Buildman should now be set up to use your new toolchain. At the time of writing, U-Boot has these architectures:
Signature · 1 line
2.5.0
PATCH 1/1 buildman: README: add links for toolchains not available on kernel.org
Quoted 6 lines · Thomas Chou
Add links for toolchains not available on kernel.org.
The sh4 toolchains from kernel.org dose not work for some boards, so use the sh from Sourcery.
Signed-off-by Thomas Chou <[email protected]>
Wouldn't it instead make more sense to get kernel.org to mirror those toolchains ? The links might not last forever, but I think kernel.org is not gonna go belly-up any soon.
Quoted 36 lines
--- tools/buildman/README | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-)tools/buildman/README +0
-0@@ -156,7 +156,6 @@ aarch64:
/opt/linaro/gcc-linaro-aarch64-none-elf-4.8-2013.10_linux[toolchain-alias]
x86: i386
blackfin: bfintools/buildman/README +0
-1-sh: sh4 nds32: nds32le openrisc: or32@@ -341,6 +340,23 @@ Testing - found'
/home/sjg/.buildman-toolchains/gcc-4.5.1-nolibc/or32-linux/bin/or32-linuxtools/buildman/README +1
-1-gcc' Tool chain test: OK +Or download them all from kernel.org and move them to /toolchainsdirectory, +
+$ for i in aarch64 arm avr32 i386 m68k microblaze mips or32 powerpc sparctools/buildman/README +7
-0+ do + ./tools/buildman/buildman --fetch-arch $i + done +$ mkdir -p /toolchains +$ mv ~/.buildman-toolchains/*/* /toolchains/ + +For those not available from kernel.org, download from the followinglinks, +
+arc:
https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/releases
/ +blackfin: http://sourceforge.net/projects/adi-toolchain/files/
tools/buildman/README Testing · line 362
Quoted 7 lines
tools/buildman/README +4
-0+nds32: http://osdk.andestech.com/packages/nds32le-linux-glibc-v1.tgz +nios2: http://sourcery.mentor.com/public/gnu_toolchain/nios2-linux-gnu/ +sh: http://sourcery.mentor.com/public/gnu_toolchain/sh-linux-gnu/ + Buildman should now be set up to use your new toolchain. At the time of writing, U-Boot has these architectures:
Best regards,
Marek Vasut
PATCH 1/1 buildman: README: add links for toolchains not available on kernel.org
Hi Marek,
Quoted 12 lines · Marek Vasut
Quoted 6 lines · Thomas Chou
Add links for toolchains not available on kernel.org.
The sh4 toolchains from kernel.org dose not work for some boards, so use the sh from Sourcery.
Signed-off-by Thomas Chou <[email protected]>Wouldn't it instead make more sense to get kernel.org to mirror those toolchains ? The links might not last forever, but I think kernel.org is not gonna go belly-up any soon.
Agree. But I think it will be helpful to offer these links when it is missing or not working on kernel.org.
I realized now that buildman is an effective and must-have tool. Every developer should run buildman before submitting patches, though it does take hours to run. The problem is that some toolchains are not easily found until looking into tools/moveconfig.py. So we should make it available.
Best regards,
Thomas
PATCH 1/1 buildman: README: add links for toolchains not available on kernel.org
Quoted 1 line · Thomas Chou
Hi Marek,
Hi!
Quoted 7 lines · Marek Vasut
Quoted 6 lines · Thomas Chou
Quoted 5 lines
Add links for toolchains not available on kernel.org.
The sh4 toolchains from kernel.org dose not work for some boards, so use the sh from Sourcery.
Quoted 8 lines
Quoted 5 lines
Quoted 1 line
Signed-off-by Thomas Chou <[email protected]>Wouldn't it instead make more sense to get kernel.org to mirror those toolchains ? The links might not last forever, but I think kernel.org is not gonna go belly-up any soon.
Agree. But I think it will be helpful to offer these links when it is missing or not working on kernel.org.
Sure, but if it's missing on k.org, it should just be added there too.
Quoted 5 lines
I realized now that buildman is an effective and must-have tool. Every developer should run buildman before submitting patches, though it does take hours to run. The problem is that some toolchains are not easily found until looking into
tools/moveconfig.py. So we should make it available.
Yeah.
Best regards,
Marek Vasut
PATCH 1/1 buildman: README: add links for toolchains not available on kernel.org
Quoted 14 lines · Marek Vasut
Quoted 1 line · Thomas Chou
Hi Marek,
Hi!
Quoted 9 lines · Marek Vasut
Quoted 8 lines · Thomas Chou
Quoted 6 lines
Add links for toolchains not available on kernel.org.
The sh4 toolchains from kernel.org dose not work for some boards, so use the sh from Sourcery.
Signed-off-by Thomas Chou <[email protected]>
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines
Wouldn't it instead make more sense to get kernel.org to mirror those toolchains ? The links might not last forever, but I think kernel.org is not gonna go belly-up any soon.
Agree. But I think it will be helpful to offer these links when it is missing or not working on kernel.org.
Sure, but if it's missing on k.org, it should just be added there too.
Adding Tony who is maintaining the kernel.org toolchains
(https://www.kernel.org/pub/tools/crosstool/)
Quoted 11 lines
Quoted 6 lines
I realized now that buildman is an effective and must-have tool. Every developer should run buildman before submitting patches, though it does take hours to run. The problem is that some toolchains are not easily found until looking into
tools/moveconfig.py. So we should make it available.Yeah.
Best regards,
Marek Vasut
Regards,
Bin
PATCH 1/1 buildman: README: add links for toolchains not available on kernel.org
Quoted 19 lines · Bin Meng
Quoted 18 lines · Marek Vasut
Quoted 1 line · Thomas Chou
Hi Marek,
Hi!
Quoted 13 lines · Marek Vasut
Quoted 11 lines · Thomas Chou
Quoted 6 lines
Add links for toolchains not available on kernel.org.
The sh4 toolchains from kernel.org dose not work for some boards, so use the sh from Sourcery.
Signed-off-by Thomas Chou <[email protected]>Wouldn't it instead make more sense to get kernel.org to mirror those toolchains ? The links might not last forever, but I think kernel.org is not gonna go belly-up any soon.
Quoted 19 lines
Quoted 4 lines
Quoted 2 lines
Agree. But I think it will be helpful to offer these links when it is missing or not working on kernel.org.
Sure, but if it's missing on k.org, it should just be added there too.
Adding Tony who is maintaining the kernel.org toolchains
(https://www.kernel.org/pub/tools/crosstool/)Quoted 11 lines
Quoted 6 lines
I realized now that buildman is an effective and must-have tool. Every developer should run buildman before submitting patches, though it does take hours to run. The problem is that some toolchains are not easily found until looking into
tools/moveconfig.py. So we should make it available.Yeah.
Best regards,
Marek Vasut
PATCH 1/1 buildman: README: add links for toolchains not available on kernel.org
Applied to u-boot-dm, thanks!
PATCH v2 1/1 buildman: README: add links for toolchains not available on kernel.org
In reply to Thomas ChouAdd links for toolchains not available on kernel.org.
The sh4 toolchains from kernel.org dose not work for some boards, so use the sh from Sourcery.
---
v2
add toolchain file links.
add sudo to write /toolchains.
tools/buildman/README | 23 ++++++++++++++++++++++- 1 file changed, 22 insertions(+), 1 deletion(-)
tools/buildman/README +22 -1
@@ -156,7 +156,6 @@ aarch64: /opt/linaro/gcc-linaro-aarch64-none-elf-4.8-2013.10_linux [toolchain-alias] x86: i386 blackfin: bfin -sh: sh4 nds32: nds32le openrisc: or32
@@ -341,6 +340,28 @@ Testing - found '/home/sjg/.buildman-toolchains/gcc-4.5.1-nolibc/or32-linux/bin/or32-linux-gcc' Tool chain test: OK +Or download them all from kernel.org and move them to /toolchains directory, + +$ for i in aarch64 arm avr32 i386 m68k microblaze mips or32 powerpc sparc + do + ./tools/buildman/buildman --fetch-arch $i + done +$ sudo mkdir -p /toolchains +$ sudo mv ~/.buildman-toolchains/*/* /toolchains/ + +For those not available from kernel.org, download from the following links. + +arc: https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/releases/ + arc_gnu_2015.06_prebuilt_uclibc_le_archs_linux_install.tar.gz +blackfin: http://sourceforge.net/projects/adi-toolchain/files/ + blackfin-toolchain-elf-gcc-4.5-2014R1_45-RC2.x86_64.tar.bz2 +nds32: http://osdk.andestech.com/packages/ + nds32le-linux-glibc-v1.tgz +nios2: http://sourcery.mentor.com/public/gnu_toolchain/nios2-linux-gnu/ + sourceryg++-2015.11-27-nios2-linux-gnu-i686-pc-linux-gnu.tar.bz2 +sh: http://sourcery.mentor.com/public/gnu_toolchain/sh-linux-gnu/ + renesas-4.4-200-sh-linux-gnu-i686-pc-linux-gnu.tar.bz2 + Buildman should now be set up to use your new toolchain. At the time of writing, U-Boot has these architectures:
Signature · 1 line
2.5.0
PATCH v2 1/1 buildman: README: add links for toolchains not available on kernel.org
Quoted 7 lines · Thomas Chou
Add links for toolchains not available on kernel.org.
The sh4 toolchains from kernel.org dose not work for some boards, so use the sh from Sourcery.
Signed-off-by Thomas Chou <[email protected]>---
Quoted 39 lines
v2
add toolchain file links.
add sudo to write /toolchains.tools/buildman/README | 23 ++++++++++++++++++++++- 1 file changed, 22 insertions(+), 1 deletion(-)tools/buildman/README +16
-1@@ -156,7 +156,6 @@ aarch64: /opt/linaro/gcc-linaro-aarch64-none-elf-4.8-2013.10_linux [toolchain-alias] x86: i386 blackfin: bfin -sh: sh4 nds32: nds32le openrisc: or32@@ -341,6 +340,28 @@ Testing - found '/home/sjg/.buildman-toolchains/gcc-4.5.1-nolibc/or32-linux/bin/or32-linux-gcc' Tool chain test: OK +Or download them all from kernel.org and move them to /toolchains directory, + +$ for i in aarch64 arm avr32 i386 m68k microblaze mips or32 powerpc sparc + do + ./tools/buildman/buildman --fetch-arch $i + done +$ sudo mkdir -p /toolchains +$ sudo mv ~/.buildman-toolchains/*/* /toolchains/ + +For those not available from kernel.org, download from the following links. + +arc: https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/releases/ + arc_gnu_2015.06_prebuilt_uclibc_le_archs_linux_install.tar.gz +blackfin: http://sourceforge.net/projects/adi-toolchain/files/ + blackfin-toolchain-elf-gcc-4.5-2014R1_45-RC2.x86_64.tar.bz2 +nds32: http://osdk.andestech.com/packages/
tools/buildman/README Testing
Quoted 10 lines
tools/buildman/README +6
-1+ nds32le-linux-glibc-v1.tgz +nios2: http://sourcery.mentor.com/public/gnu_toolchain/nios2-linux-gnu/ + sourceryg++-2015.11-27-nios2-linux-gnu-i686-pc-linux-gnu.tar.bz2 +sh: http://sourcery.mentor.com/public/gnu_toolchain/sh-linux-gnu/ + renesas-4.4-200-sh-linux-gnu-i686-pc-linux-gnu.tar.bz2 + Buildman should now be set up to use your new toolchain. At the time of writing, U-Boot has these architectures: --
Regards,
Bin