Our product is used in a safety-critical situation. We want to make sure that the product we released is exactly the one we tested in our labs. Because our product is released in a checkout-build-release process, it is impossible to just give out the binary file we tested.
Maybe there is a workaround to solve this problem. 2011/6/12 Mike Frysinger <vap...@gentoo.org>: > On Saturday, June 11, 2011 02:55:41 Wolfgang Denk wrote: >> Peter Pan wrote: >> > I found out that even with the same source code, the final u-boot.bin >> > has a different MD5sum each time I build. >> > Is that possible to get an identical u-boot.bin for the same source >> > code, no matter when I build? >> >> No, as the image contains a time stamp that changes each time you >> build a new image. > > i wonder if we should make this a config tweak. some people (not really > myself) would like to be able to confirm the same result every time and the > timestamp is an acceptable loss ... > -mike > _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
