https://bugs.kde.org/show_bug.cgi?id=472402
--- Comment #8 from John Reiser <jrei...@bitwagon.com> --- (In reply to Paul Floyd from comment #7) > Here is what GCC's Makefile contains Yes, valgrind should use essentially the same setup. In ancient times (pre-git) there was a conceptual barrier that Makefile.am and files that depend on it directly, would be changed only by Team members making a new release; and the consumers of the release would perform the "autogen; configure". Now "git pull" removes that barrier, so ALL dependencies must be recorded explicitly. > Makefile: $(srcdir)/Makefile.in config.status > CONFIG_FILES=$@ CONFIG_HEADERS= $(SHELL) ./config.status Yes, I had figured out yesterday that Makefile would need to be re-generated by running config.status. > config.status: configure > CONFIG_SHELL="$(SHELL)" $(SHELL) ./config.status --recheck This is a cicularity that logically might require two passes to stabilize: running ./configure changes ./config.status, and running ./config.status changes ./configure. Perhaps the --recheck does that? -- You are receiving this mail because: You are watching all bug changes.
