aboutsummaryrefslogtreecommitdiff
path: root/arch
diff options
context:
space:
mode:
authorJohannes Schindelin <johannes.schindelin@gmx.de>2017-02-01 22:30:40 +0100
committerRon Yorston <rmy@pobox.com>2017-07-14 15:14:37 +0100
commit02958a6ee4050f75188df371a4118efb89685c8c (patch)
tree8717eb3d2abeb4c088ecf7ca9e9abb37b34d861d /arch
parentc56f1e06c4c470a023b02c7019112eb852f08d44 (diff)
downloadbusybox-w32-02958a6ee4050f75188df371a4118efb89685c8c.tar.gz
busybox-w32-02958a6ee4050f75188df371a4118efb89685c8c.tar.bz2
busybox-w32-02958a6ee4050f75188df371a4118efb89685c8c.zip
kbuild: simulate force-renaming on Windows
Calling rename() when a file with the target name exists already fails on Windows. Let's simply delete the target file, if it exists. This is usually a dangerous thing as it leaves time between deleting and renaming, during which (theoretically) another thread or process could have created the same file, and the rename() would fail again. Practically, we are talking about the kbuild system used to configure the build, where it does not matter, as we do not expect any other thread or process to interfere with the configuration files. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions