Don't force remove config.cache on reconfiguration.
config.cache will be used by the person who specifies '-C' to configure. config.cache's inconsistency should be responsible to him. Re-configuration would spend so much on cygming without '-C', esp. cygwin. llvm-svn: 133252
This commit is contained in:
parent
e11f467dda
commit
b2507b3926
|
@ -123,9 +123,6 @@ $(BUILT_SOURCES) : $(ObjMakefiles)
|
|||
reconfigure:
|
||||
$(Echo) Reconfiguring $(PROJ_OBJ_ROOT)
|
||||
$(Verb) cd $(PROJ_OBJ_ROOT) && \
|
||||
if test -w $(PROJ_OBJ_ROOT)/config.cache ; then \
|
||||
$(RM) $(PROJ_OBJ_ROOT)/config.cache ; \
|
||||
fi ; \
|
||||
$(ConfigStatusScript) --recheck $(ConfigureScriptFLAGS) && \
|
||||
$(ConfigStatusScript)
|
||||
|
||||
|
@ -133,9 +130,6 @@ reconfigure:
|
|||
$(ConfigStatusScript): $(ConfigureScript)
|
||||
$(Echo) Reconfiguring with $<
|
||||
$(Verb) cd $(PROJ_OBJ_ROOT) && \
|
||||
if test -w $(PROJ_OBJ_ROOT)/config.cache ; then \
|
||||
$(RM) $(PROJ_OBJ_ROOT)/config.cache ; \
|
||||
fi ; \
|
||||
$(ConfigStatusScript) --recheck $(ConfigureScriptFLAGS) && \
|
||||
$(ConfigStatusScript)
|
||||
|
||||
|
|
Loading…
Reference in New Issue