Hi Bram, 2014/5/18 Sun 0:24:51 UTC+9 Bram Moolenaar wrote: > Ken Takata wrote: > > > I found two issues with configure. > > > > 1. After 7.3.1221, 'make config' removes auto/config.cache everytime. > > Thus the cached result of configure was not used at all. > > I think that's intentional. Using the cache is not reliable, if > something changed in the environment it may result in a half-cooked > config.
No, I didn't intend that, at least when I posted the patch in this thread https://groups.google.com/d/topic/vim_dev/L7-eXk0Slds/discussion . But I agree that sometimes the cache is not reliable. If we don't trust the cache at all, maybe it's better to remove the cache explicitly: --- a/src/Makefile +++ b/src/Makefile @@ -1665,11 +1665,7 @@ # sure configure is run when it's needed. # config auto/config.mk: auto/configure config.mk.in config.h.in - if test -f auto/config.cache && \ - grep '^ac_cv_env_CFLAGS_value=' auto/config.cache > /dev/null && \ - ! grep -x -F 'ac_cv_env_CFLAGS_value=$(CFLAGS)' auto/config.cache > /dev/null; then \ - rm auto/config.cache; \ - fi + -rm -f auto/config.cache if test "X$(MAKECMDGOALS)" != "Xclean" \ -a "X$(MAKECMDGOALS)" != "Xdistclean" \ -a "X$(MAKECMDGOALS)" != "Xautoconf" \ But actually I think it's better to fix configure.in rather than the above patch, when something weird happen with the cache. Regards, Ken Takata -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
