Jonathan Nieder <jrnieder@xxxxxxxxx> writes: > The "gmake clean" undoes the effect of "./configure". > > Hope that helps. > > Signed-off-by: Jonathan Nieder <jrnieder@xxxxxxxxx> You diagnosed the problem correctly, but I do not think the patch is correct. Why should the generated file *.autogen be kept around across "clean"? I do understand why we keep "configure" around (it is common for everybody once it is generated), though. > --- > diff --git a/Makefile b/Makefile > index d3dcfb1..c693652 100644 > --- a/Makefile > +++ b/Makefile > @@ -2229,7 +2229,7 @@ dist-doc: > ### Cleaning rules > > distclean: clean > - $(RM) configure > + $(RM) configure config.mak.autogen > > clean: > $(RM) *.o block-sha1/*.o ppc/*.o compat/*.o compat/*/*.o xdiff/*.o vcs-svn/*.o \ > @@ -2240,7 +2240,7 @@ clean: > $(RM) -r $(dep_dirs) > $(RM) *.spec *.pyc *.pyo */*.pyc */*.pyo common-cmds.h $(ETAGS_TARGET) tags cscope* > $(RM) -r autom4te.cache > - $(RM) config.log config.mak.autogen config.mak.append config.status config.cache > + $(RM) config.log config.mak.append config.status config.cache > $(RM) -r $(GIT_TARNAME) .doc-tmp-dir > $(RM) $(GIT_TARNAME).tar.gz git-core_$(GIT_VERSION)-*.tar.gz > $(RM) $(htmldocs).tar.gz $(manpages).tar.gz -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html