summaryrefslogtreecommitdiff
path: root/dts/Makefile
diff options
context:
space:
mode:
authorMasahiro Yamada <yamada.masahiro@socionext.com>2019-01-11 19:42:26 +0900
committerTom Rini <trini@konsulko.com>2019-01-15 15:28:52 -0500
commit368a0dfbf8ab283f792f5aabf436463254a8f577 (patch)
treea1be680457835281f65d2089c96fe04d8ec996d2 /dts/Makefile
parentf75977303d64bc346c34a0bb8a6d9c7eaa67b00b (diff)
downloadu-boot-368a0dfbf8ab283f792f5aabf436463254a8f577.tar.gz
kbuild: add .DELETE_ON_ERROR special target
Linux commit 9c2af1c7377a8a6ef86e5cabf80978f3dbbb25c0 If Make gets a fatal signal while a shell is executing, it may delete the target file that the recipe was supposed to update. This is needed to make sure that it is remade from scratch when Make is next run; if Make is interrupted after the recipe has begun to write the target file, it results in an incomplete file whose time stamp is newer than that of the prerequisites files. Make automatically deletes the incomplete file on interrupt unless the target is marked .PRECIOUS. The situation is just the same as when the shell fails for some reasons. Usually when a recipe line fails, if it has changed the target file at all, the file is corrupted, or at least it is not completely updated. Yet the file’s time stamp says that it is now up to date, so the next time Make runs, it will not try to update that file. However, Make does not cater to delete the incomplete target file in this case. We need to add .DELETE_ON_ERROR somewhere in the Makefile to request it. scripts/Kbuild.include seems a suitable place to add it because it is included from almost all sub-makes. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Diffstat (limited to 'dts/Makefile')
0 files changed, 0 insertions, 0 deletions