dri: use mv -f instead of mv to ensure no prompting occurs
Using just mv may cause prompts on some systems/configurations.
This commit is contained in:
parent
2689dd304c
commit
fff86eb0aa
2 changed files with 2 additions and 2 deletions
|
|
@ -71,7 +71,7 @@ $(LIBNAME): $(OBJECTS) $(MESA_MODULES) $(PIPE_DRIVERS) Makefile \
|
|||
$(DRI_LIB_DEPS) $(DRIVER_EXTRAS)
|
||||
$(CC) -o $@.test $(TOP)/src/mesa/drivers/dri/common/dri_test.o $@.tmp -L$(TOP)/lib -lGL
|
||||
@rm -f $@.test
|
||||
mv $@.tmp $@
|
||||
mv -f $@.tmp $@
|
||||
|
||||
$(TOP)/$(LIB_DIR)/gallium:
|
||||
mkdir -p $@
|
||||
|
|
|
|||
|
|
@ -56,7 +56,7 @@ $(LIBNAME): $(OBJECTS) $(MESA_MODULES) $(EXTRA_MODULES) Makefile \
|
|||
$(OBJECTS) $(MESA_MODULES) $(EXTRA_MODULES) $(DRI_LIB_DEPS)
|
||||
$(CC) -o $@.test $(TOP)/src/mesa/drivers/dri/common/dri_test.o $@.tmp -L$(TOP)/lib -lGL
|
||||
@rm -f $@.test
|
||||
mv $@.tmp $@
|
||||
mv -f $@.tmp $@
|
||||
|
||||
|
||||
$(TOP)/$(LIB_DIR)/$(LIBNAME): $(LIBNAME)
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue