Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] "no hash found" error for host-gcc-initial-4.9.3 package verification
Date: Mon, 1 Aug 2016 06:22:38 +0300	[thread overview]
Message-ID: <20160801032238.GM3620@tarshish> (raw)
In-Reply-To: <CAJe0E3e22wsz_+x9ztXOS7aZaMPuP4L0PXRoavpwCRJy9VJCww@mail.gmail.com>

Hi Guillaume

On Sun, Jul 31, 2016 at 04:39:40PM -0600, Guillaume William Bres wrote:
> I want one of my coworkers to build a custom linux image using some default
> buildroot stuff. The system builds fine on my machine but it fails on his:
> 
> 
>    - Buildroot downloads host-gcc-initial-4.9.3,
>    - tries a file verification with either md5sum or sha-sum: error: "ho
>    hash found"
>    - Buildroot downloads host-gcc initial-4.9.3 from a mirror
>    - same problem.
> 
> 
> Where does this problem come from? His machine does have md5sum and all
> sha-x-sum tools installed, I was able to build the system on mine in the
> meantime without any problems.
> 
> File verifications should give an error message but not actually cause the
> build to stop right?

Which version of Buildroot do you use?

Please post your .config file, and the last few lines of the build log.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

      reply	other threads:[~2016-08-01  3:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-31 22:39 [Buildroot] "no hash found" error for host-gcc-initial-4.9.3 package verification Guillaume William Bres
2016-08-01  3:22 ` Baruch Siach [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=20160801032238.GM3620@tarshish \
    --to=baruch@tkos.co.il \
    --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