From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3 v2] toolchain: add hashes for all remaining external toolchains
Date: Sun, 28 Dec 2014 13:58:10 +0100 [thread overview]
Message-ID: <20141228135810.763ae357@free-electrons.com> (raw)
In-Reply-To: <f924e745902fb357ec83221b28fb8a0f9a38a311.1419768498.git.yann.morin.1998@free.fr>
Dear Yann E. MORIN,
On Sun, 28 Dec 2014 13:19:31 +0100, Yann E. MORIN wrote:
> +# Buildroot (?)
> +sha256 3e1c7c53fadfd3346ab60386c573f07f0617ab119546ec8cb93bc20c23cff2b3 lin32-microblazeel-unknown-linux-gnu_14.3_early.tar.xz
> +sha256 b72f7be654a75bb643372f3909de7b8739f0f56bdf8bea98fea41dcecefe6b6b microblazeel-unknown-linux-gnu.tgz
> +sha256 ed2fea022f2def257ca6db09911b73c7102aaa1792d2da2d81371a763e5c2eff lin32-microblaze-unknown-linux-gnu_14.3_early.tar.xz
> +sha256 53ee0b1ad50e651eb14d0b53044b90e7bf7e3cb341ee57fe575bc4c4e142ea37 microblaze-unknown-linux-gnu.tgz
These are not Buildroot toolchains. They are provided by Xilinx, but
hosted on sources.buildroot.net since the official site was not working
anymore, or something like that.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-12-28 12:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-28 12:19 [Buildroot] [PATCH 0/3 v2] Add a lot of hashes (branch yem/sf-hash) Yann E. MORIN
2014-12-28 12:19 ` [Buildroot] [PATCH 1/3 v2] package: add hashes for SourceForge-hosted packages Yann E. MORIN
2014-12-28 21:34 ` Thomas Petazzoni
2014-12-28 12:19 ` [Buildroot] [PATCH 2/3 v2] toolchain-external: add hashes for Blackfin toolchains Yann E. MORIN
2014-12-28 21:41 ` Thomas Petazzoni
2014-12-28 12:19 ` [Buildroot] [PATCH 3/3 v2] toolchain: add hashes for all remaining external toolchains Yann E. MORIN
2014-12-28 12:58 ` Thomas Petazzoni [this message]
2014-12-28 13:31 ` Yann E. MORIN
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=20141228135810.763ae357@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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