Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot] No hash found for gcc-5.4.0.tar.bz2.
Date: Tue, 17 Oct 2017 08:51:39 +0200	[thread overview]
Message-ID: <20171017085139.2f48ba78@windsurf.lan> (raw)
In-Reply-To: <52863a95f7d742d4a1a754e66954e9d3@draper.com>

Hello,

On Mon, 16 Oct 2017 20:02:26 +0000, Lim, Sungyung wrote:

> I downloaded the buildroot from the mathworks git website
> [https://github.com/mathworks/buildroot] because of familiarity with mathworks tools such as matlab.

This not the official Buildroot, so it's a bit difficult to provide
support for something we are not the author of. You should ask the
authors of this Buildroot fork, and encourage them to contribute
upstream instead.

> The .config file says
> 
> 1. buildroot 2017.02 configuration
> 2. buildroot .config was generated for zynq_zed_defconfig

From a quick look at this Buildroot, I don't see why you would get this
failure. package/gcc/gcc-initial/gcc-initial.hash is properly a symlink
to ../gcc.hash, and package/gcc/gcc.hash does contain the hash for
gcc-5.4.0.tar.bz2. So everything looks correct to me here.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

      reply	other threads:[~2017-10-17  6:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16 19:07 [Buildroot] [buildroot] No hash found for gcc-5.4.0.tar.bz2 Lim, Sungyung
2017-10-16 19:25 ` Thomas Petazzoni
2017-10-16 20:02   ` Lim, Sungyung
2017-10-17  6:51     ` Thomas Petazzoni [this message]

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=20171017085139.2f48ba78@windsurf.lan \
    --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