public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] buildman: README: add links for toolchains not available on kernel.org
Date: Wed, 11 Nov 2015 16:54:03 +0100	[thread overview]
Message-ID: <201511111654.04024.marex@denx.de> (raw)
In-Reply-To: <1447249028-29795-1-git-send-email-thomas@wytron.com.tw>

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

  reply	other threads:[~2015-11-11 15:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-11 13:37 [U-Boot] [PATCH] buildman: README: add links for toolchains not available on kernel.org Thomas Chou
2015-11-11 15:54 ` Marek Vasut [this message]
2015-11-12  1:16   ` Thomas Chou
2015-11-12  2:19     ` Marek Vasut
2015-11-12  2:23       ` Bin Meng
2015-11-13 18:14         ` Simon Glass
2015-12-11 13:24           ` Simon Glass
2015-11-12  1:29 ` [U-Boot] [PATCH v2] " Thomas Chou
2015-11-12  2:13   ` Bin Meng

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201511111654.04024.marex@denx.de \
    --to=marex@denx.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox