Something in xmame 0.80 parallel build or crc handling seems messed up. Some roms work, some don't. for example: magdrop3: 233-c1.bin WRONG CHECKSUMS: EXPECTED: CRC(65e3f4c4) SHA1(a6deb75d802225327f8f1c2733a7f2b47e722e59) FOUND: CRC(734db3d6) SHA1(6d12b3ef34aae066f8c5cae5f6a272c8f482bdd0) 233-c2.bin WRONG CHECKSUMS: EXPECTED: CRC(35dea6c9) SHA1(ea133bf947f950236f49d0ae0d1a9af3bc1a9a50) FOUND: CRC(d78f50e5) SHA1(102526982596a9d3052d3f3181a98558c596c907) 233-c3.bin WRONG CHECKSUMS: EXPECTED: CRC(0ba2c502) SHA1(8e0f1e553aef04758aaaa14d5115f0ecace4391e) FOUND: CRC(ec65f472) SHA1(23271ca8617d08f23417dd071333c91ef90715b5) 233-c4.bin WRONG CHECKSUMS: EXPECTED: CRC(70dbbd6d) SHA1(32dd6a04c6329e89f4878e7a56f0d172a6388eea) FOUND: CRC(f55dddf3) SHA1(fec0930e5cb26be4d73bfa8c76ef37eb4bbec60a) when trying the same roms with the 0.79.1 build, there is no such problem ! Reproducible: Always Steps to Reproduce: 1. emerge xmame 0.80.1 2. try some roms 3. see crc failures 4. emerge xmame 0.79.1 5. try same roms 6. everything is fine Actual Results: some games are broken due to "wrong checksum calculation" Expected Results: crc checksums should be correct building was done using distcc and j6 with latest version of gcc and binutils
Look in the whatsnew.txt for 0.80 on mame.net - it's very likely the roms changed (I believe there were a whole bunch of neogeo redumps, for instance) so the roms you have are likely incorrect. Unless it happens with all of them, this probably isn't a program bug. (Note: I have the correct CRC for your example).
Indeed. The faq at http://x.mame.net/ mentions this condition and what to do about it. Not a program bug, compile bug or Gentoo bug as far as I can tell.
