Herold Heiko <[EMAIL PROTECTED]> writes: >> would insert `make distclean' before the second configure, or *at >> least* `rm config.cache'. > > Exactly my point - shouldn't either everything handled gracefully, or > cleaned up automatically when necessary (in ./configure ?),
I don't think so. Dependency information is reliably (or "reliably") handled for source files. But for example, if you touch a `Makefile', noone guarantees that things will recompile. Rerunning configure is sort of like touching the Makefiles, a gray area. For me, rerunning configure without doing a `make distclean' or at least `rm config.cache' is calling for trouble. > or at least pointed out in the installation instructions ? > After all wget will be compiled not only by competent programmers, > but also by, say, people touching unix for their first time (linux, > bsd ?) ... Maybe. Or maybe Wget will be a good lesson that they should always start from the clean sources and not trust build systems. They'll thank me for that when they grow up. :-) Seriously, I don't think it matters that much. Starting with Autoconf 2.50, caching is turned off by default anyway, so the whole point will be moot.
