That's one of the places I downloaded both the zip and the md5 check from. Using both cygwin's md5sum as well as the md5 validater that is part of ExactFile (available at www.exactfile.com), I get a validation fail. Oddly, when I go the reverse route md5sum generates the exact same md5 signature as is in the .md5 file, but the one from ExactFile generates a different value.
Regenerating the .md5 file using md5sum and the -b option for binary mode yields the odd result of having a new md5 file, with the exact same md5 signature that passes using either md5sum or ExactFile - the only difference in the .md5 file is an asterisk preceding the filename, which must indicate that the file should be read in binary mode. Can you verify for me that when the md5 file is generated that it is done in binary mode (as I think it should for a zip formatted file)? BTW, building everything in VC 9.0 seems to be OK, although there are many warnings that will need cleaning before it will pass our software build requirements. Should I submit deltas as I fix these? Bill Howell Senior Software Engineer FLIR Systems, Inc. -----Original Message----- From: Boris Kolpackov [mailto:[email protected]] Sent: Thursday, August 19, 2010 2:05 PM To: [email protected] Subject: Re: Can't find zip with valid MD5 checksum Hi Bill, Howell, Bill <[email protected]> writes: > Anyone else see this? I just downloaded that file from http://www.apache.org/dist and the checksum matches. Can you try that? If it's still doesn't work, then there must be something wrong on your side. Boris -- Boris Kolpackov, Code Synthesis http://codesynthesis.com/~boris/blog Open-source XML data binding for C++ http://codesynthesis.com/products/xsd XML data binding for embedded systems http://codesynthesis.com/products/xsde Command line interface to C++ compiler http://codesynthesis.com/projects/cli Notice to recipient: This email is meant for only the intended recipient of the transmission, and may be a communication privileged by law, subject to export control restrictions or that otherwise contains proprietary information. If you receive this email by mistake, please notify us immediately by replying to this message and then destroy it and do not review, disclose, copy or distribute it. Thank you in advance for your cooperation.
