On 26 May 2013 08:35, Michael S. Tsirkin <m...@redhat.com> wrote: > On Sat, May 25, 2013 at 05:32:24PM +0000, Blue Swirl wrote: >> Another way to handle this would be to enhance GCC and linker to use >> atomic operations when producing or combining object files. The tools >> could also print a SHA of the object which the next user should >> verify. Even better, the object files should include a robust checksum >> to ensure integrity. > > I think we can make the makefile more robust. It can create a temporary > file in same directory and rename when ready. This will prevent > corrupted files from appearing in the first place.
I definitely think individual project makefiles are the wrong place to fix this. If create-as-temp-and-rename is useful functionality it needs to go in the compiler so that everybody benefits. Or you could write yourself a cc wrapper that did the renaming and use configure's --cc= flag. thanks -- PMM
