ERROR: Function 'File: ... checksum error'

-
If you get:


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


better:

1)

bitbake distcc -c cleanall


2) 

bitbake distcc -c fetch


as this will force a clean out of any existing "bad" state that might
exist. The -f option means rerun the task even if bitbake doesn't think
it needs to run but it will not wipe out files in DL_DIR.

or (not so good) ...

1) refetch distcc

  $ bitbake -c fetch -f distcc

If that still fails:

2) update the MD5 in the distcc recipe and try to rebuild.

If that works, we need a patch to update the MD5.

or ...

check if the file you want to fetch still exists at the URL you try to fetch it from;)

Comments

  1. MaximMay 17, 2011 at 10:50 PM

    Seems like http://distcc.samba.org/ftp/distcc/distcc-2.18.3.tar.bz2 is no longer valid

    ReplyDelete
  2. robert.bergerMay 17, 2011 at 11:31 PM

    Yes that's right. You should use this location:

    http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/?id=43607eb1c6cd189eab21b297318aaab40029318c

    ReplyDelete

Post a Comment

Popular posts from this blog

Yocto: BitBake and Dependencies - e.g. One recipe to use output of another recipe

-
Image
It feels weird to help some get their working build to fail and then for them to be happy about it... (RP) Introduction This work is sponsored by Reliable Embedded Systems . You can find more information about our training/consulting services here . Objectives The goal of this blog post is to look into BitBake dependencies. As an example let's take recipe A ( u-boot-phytex-imx ) which needs the output of recipe B ( firmware-imx-8m ) for a successful compilation. (Please don't ask why.) To be more precise here is an excerpt of recipe A ( u-boot-phytex-imx ): # --> this funny u-boot from Phytec needs the ddr_firmware binaries in ${S} # Note: here we copy deployed stuff from another recipe # to the source dir of this recipe! # # DEPENDS deals with build-time depenencies # Read my blog post to find out why DEPENDS does not work here # # DEPENDS += " \ # firmware-imx-8m \ # " # RDEPENDS is wrong anyhow for what I want
Read more

Yocto: kernel modules not showing up in the rootfs

-
Image
Introduction This work is sponsored by Reliable Embedded Systems . You can find more information about our training/consulting services here . Objectives The goal of this blog post is to point out a well known and documented issue with kernel modules not ending up on the root file system which is likely overseen by people until they stumble over it.   Kernel module(s) So you created a brand new kernel module, or you just wanted to include all the kernel modules in the root file system, or just one of them. You reach out to the community mailing list or chat with something like this: I have MACHINE_EXTRA_RRECOMMENDS + = "kernel-modules" in my machine configuration. When I look into the rootfs I see no modules installed in /lib/modules/ $( uname -r ) . I get only a modules tarball in the deploy directory. I also tried MACHINE_EXTRA_RDEPENDS + = "kernel-modules" and it still does not work. What am I doing wrong? Check the Mega Manual If things d
Read more

Yocto/Qt5: hello-qt part2 - Licensing

-
Image
Introduction This work is sponsored by Reliable Embedded Systems . You can find more information about our training/consulting services here . Objectives The goal of this blog post is to show my journey trying to build a hello-qt application and reasons why I don't like Qt . As far as I can tell this is going to be a multi part blog post. You might want to have a look at part one as well. Disclaimer: I am not a lawyer, so I can not give legal advice. GPL and LGPL licenses LGPL v2.x Typically libraries are licensed with this license You need to provide the source code (including modifications) and instructions on how to build the LGPL v2.1 licensed code In case your application links statically against LGPL licensed code you need to provide the object files of your applications to be able to replace the LGPL'ed code with different versions In case your application links dynamically against LGPL licensed code you can replace the LGPL'ed libraries without the objec
Read more