md5sum broken?

[J]

On Sat, May 29, 2010 at 09:05, Robert P. J. Day <rpjday at crashcourse.ca> wrote:
> p.s.  speculating wildly (as i am wont to do), i'm going to *guess*
> that your build system is doing an MD5 check, the sums don't match for
> one reason or another, and your build system is then producing that
> diagnostic.  because nothing else seems to make sense.

I'm going to put my money on the OPs comment about having path
information in the md5 checksum files...

at least, I'm hoping that's it.

As a point of contention, it's generally considered good practice (as
far as I know) to md5sum things in the directory they sit in, so the
checksum file does not have path information in it.  This is
especially important if you're distributing software, since an md5sum
that is correct on your system like this:

abcdef1233567890 /path/to/my/files/and/filename.ext

won't work on someone else's system that does not have /path/to/my/files/and...

then again, though, if the path exists on his computer, it SHOULD
still work, at least in his environment.