I'm not familiar with that feature of autoconf. The check in make puts a
dependency between spec.gmk and all the files in common/autoconf. If
spec.gmk isn't touched, make won't budge. Running config.status isn't
working on my machine though, so I will need to investigate this a bit
more and see if we can get it working.
/Erik
On 2013-06-27 20:23, David DeHaven wrote:
Am I wrong in thinking that running "build/<target>/config.status --recheck" should
alleviate the "you need to re-run configure" condition that happens when you pull in new
sources? I think it needs to touch some config files if they are unchanged or whatever test is blocking
the build needs to consider that it may have been re-run and nothing changed.
-DrD-
