Running "make clean" also requires a run of "./configure ..." again
because it deletes auto-generated files, which I found a little
unexpected. I figured I'd mention it as I'm not sure if this is
confusing for other users or intended functionality of "make clean"
vs. "make distclean", I would assume that the first would not revert
configuration changes.
Signed-off-by: Brian Shire <shire@xxxxxxxxxx>
---
Makefile | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Makefile b/Makefile
index b003e3e..f868b0b 100644
--- a/Makefile
+++ b/Makefile
@@ -1346,6 +1346,7 @@ dist-doc:
### Cleaning rules
distclean: clean
+ $(RM) config.log config.mak.autogen config.mak.append config.status
config.cache
$(RM) configure
clean:
@@ -1355,7 +1356,6 @@ clean:
$(RM) $(TEST_PROGRAMS)
$(RM) *.spec *.pyc *.pyo */*.pyc */*.pyo common-cmds.h TAGS tags
cscope*
$(RM) -r autom4te.cache
- $(RM) config.log config.mak.autogen 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
--
1.5.6.dirty
--
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
