From: Robert Berger <gmane@reliableembeddedsystems.com>
To: poky@pokylinux.org
Subject: No rootfs for beagleboard after bernard 5.0
Date: Wed, 11 May 2011 23:51:30 +0300 [thread overview]
Message-ID: <iqessi$mok$1@dough.gmane.org> (raw)
Hi,
I'm trying to build poky-image-sato-sdk branch bernard-5.0.1 for the
beagleboard. It has the following error:
ERROR: Function 'File:
'/work/rber/poky-bernard-5.0.1-arm-beagle/downloads/distcc-2.18.3.tar.bz2'
has md5 checksum 2279f50fe7b688c8d6762a3e095a302a when
0d6b80a1efc3a3d816c4f4175f63eaa2 was expected (from URL:
'http://distcc.samba.org/ftp/distcc/distcc-2.18.3.tar.bz2')' failed
... and no rootfs ...
rber@yocto-vm-1:/work/rber/poky-bernard-5.0.1-arm-beagle/tmp/deploy/images$
ls
licenses
MLO-beagleboard
MLO-beagleboard-1.42+r13+git1+6f3a26101303051e0f91b6213735b68ce804e94e-r13
modules-2.6.37.3-yocto-standard+-r16-beagleboard.tgz
u-boot-beagleboard.bin
u-boot-beagleboard-v2010.12+r1+git1+264eaa0ea967bac32214b87d60cfc86c8b22cac6-r1.bin
uImage-2.6.37+git1+212cae404e57ff9dc58c808035770d51325c3512_1+2b2ef940457f0bb40e0fb76937c921c2962364ca-r16-beagleboard-20110511114121.bin
uImage-beagleboard.bin
x-load-beagleboard-1.42+r13+git1+6f3a26101303051e0f91b6213735b68ce804e94e-r13.bin.ift
x-load-beagleboard.bin.ift
Something similar happened with the latest and greatest from git (that's
why I was trying this)
Am I missing something or is poky-image-sato-sdk for the beagleboard broken?
Regards,
Robert
...If the code and the comments disagree, both are probably wrong.
My public pgp key is available at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
next reply other threads:[~2011-05-11 20:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 20:51 Robert Berger [this message]
2011-05-11 23:07 ` No rootfs for beagleboard after bernard 5.0 Darren Hart
2011-05-12 9:23 ` Richard Purdie
2011-05-12 21:38 ` Robert Berger
2011-05-12 21:44 ` Gary Thomas
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='iqessi$mok$1@dough.gmane.org' \
--to=gmane@reliableembeddedsystems.com \
--cc=poky@pokylinux.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.