| Message ID | 1447249028-29795-1-git-send-email-thomas@wytron.com.tw |
|---|---|
| State | Superseded |
| Headers | show |
On Wednesday, November 11, 2015 at 02:37:08 PM, Thomas Chou wrote: > 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 <thomas@wytron.com.tw> 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. > --- > tools/buildman/README | 18 +++++++++++++++++- > 1 file changed, 17 insertions(+), 1 deletion(-) > > diff --git a/tools/buildman/README b/tools/buildman/README > index 10c7135..e205278 100644 > --- a/tools/buildman/README > +++ b/tools/buildman/README > @@ -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: Best regards, Marek Vasut
Hi Marek, On 2015年11月11日 23:54, Marek Vasut wrote: > On Wednesday, November 11, 2015 at 02:37:08 PM, Thomas Chou wrote: >> 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 <thomas@wytron.com.tw> > > 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
On Thursday, November 12, 2015 at 02:16:05 AM, Thomas Chou wrote: > Hi Marek, Hi! > On 2015年11月11日 23:54, Marek Vasut wrote: > > On Wednesday, November 11, 2015 at 02:37:08 PM, Thomas Chou wrote: > >> 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 <thomas@wytron.com.tw> > > > > 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. > 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
On Thu, Nov 12, 2015 at 10:19 AM, Marek Vasut <marex@denx.de> wrote: > On Thursday, November 12, 2015 at 02:16:05 AM, Thomas Chou wrote: >> Hi Marek, > > Hi! > >> On 2015年11月11日 23:54, Marek Vasut wrote: >> > On Wednesday, November 11, 2015 at 02:37:08 PM, Thomas Chou wrote: >> >> 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 <thomas@wytron.com.tw> >> > >> > 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/) > >> 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
On 11 November 2015 at 19:23, Bin Meng <bmeng.cn@gmail.com> wrote: > On Thu, Nov 12, 2015 at 10:19 AM, Marek Vasut <marex@denx.de> wrote: >> On Thursday, November 12, 2015 at 02:16:05 AM, Thomas Chou wrote: >>> Hi Marek, >> >> Hi! >> >>> On 2015年11月11日 23:54, Marek Vasut wrote: >>> > On Wednesday, November 11, 2015 at 02:37:08 PM, Thomas Chou wrote: >>> >> 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 <thomas@wytron.com.tw> >>> > >>> > 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/) > >> >>> 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 Acked-by: Simon Glass <sjg@chromium.org>
Applied to u-boot-dm, thanks!
diff --git a/tools/buildman/README b/tools/buildman/README index 10c7135..e205278 100644 --- a/tools/buildman/README +++ b/tools/buildman/README @@ -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:
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 <thomas@wytron.com.tw> --- tools/buildman/README | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-)