-
Nicolas Pitre authored
Some filesystems have timestamps with coarse precision that may allow for a recently built object file to have the same timestamp as the updated time on one of its dependency files. When that happens, the object file doesn't get rebuilt as it should. This is especially the case on filesystems that don't have sub-second time precision, such as ext3 or Ext4 with 128B inodes. Let's prevent that by making sure updated dependency files have a newer timestamp than the first file we created (i.e. autoksyms.h.tmpnew). Reported-by:
Thomas Lindroth <thomas.lindroth@gmail.com> Signed-off-by:
Nicolas Pitre <nico@linaro.org> Tested-by:
Thomas Lindroth <thomas.lindroth@gmail.com> Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com>
Nicolas Pitre authoredSome filesystems have timestamps with coarse precision that may allow for a recently built object file to have the same timestamp as the updated time on one of its dependency files. When that happens, the object file doesn't get rebuilt as it should. This is especially the case on filesystems that don't have sub-second time precision, such as ext3 or Ext4 with 128B inodes. Let's prevent that by making sure updated dependency files have a newer timestamp than the first file we created (i.e. autoksyms.h.tmpnew). Reported-by:
Thomas Lindroth <thomas.lindroth@gmail.com> Signed-off-by:
Nicolas Pitre <nico@linaro.org> Tested-by:
Thomas Lindroth <thomas.lindroth@gmail.com> Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com>
Code owners
Assign users and groups as approvers for specific file changes. Learn more.