Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lim, Sungyung <slim@draper.com>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot] No hash found for gcc-5.4.0.tar.bz2.
Date: Mon, 16 Oct 2017 19:07:53 +0000	[thread overview]
Message-ID: <e953736f09ba4dd6a73358abf69f44aa@draper.com> (raw)

Dear Buildroot developers

As a beginner, I'm looking for some advices on the issue : No hash found for gcc-5.4.0.tar.bz2.

Here is a copy of the log from running buildroot make command:

>>> host-gcc-initial 5.4.0 Downloading
Saving to ~output/build/.gcc-5.4.-.tar.bz2.aYTUOP/output
~output/build/.gcc-5.4.0.tar.bz2.aYTUOP/output' saved
ERROR: No hash found for gcc-5.4.0.tar.bz2
Make[1]: *** [~output/build/host-gcc-initial-5.4.0/.stamp_downloaded] Error 1
Make: *** [_all] Error 2


Thank you for your consideration in advance.

Thanks - Sungyung


________________________________
Notice: This email and any attachments may contain proprietary (Draper non-public) and/or export-controlled information of Draper. If you are not the intended recipient of this email, please immediately notify the sender by replying to this email and immediately destroy all copies of this email.
________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20171016/174d664f/attachment.html>

             reply	other threads:[~2017-10-16 19:07 UTC|newest]

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

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=e953736f09ba4dd6a73358abf69f44aa@draper.com \
    --to=slim@draper.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