On Fri, 7 Jan 2011 10:51:56 +0100 Ciprian Dorin Craciun <ciprian.crac...@gmail.com> wrote:
> :) I've kind of feared that this is the reason... :) > > But still how do people handle the issue? I guess in most cases it is ok to ignore the slight waste of CPU-time. And i guess people just ignore it. After all it costs less than a second for each of these targets. If your project it full of them and they are deps for bigger targets you may want to add "sleep x.y" to the rules. That way it will maybe take more time but will idle instead of wasting CPU-time. When using the sleeps adjusting NPROC might help to do something useful while sleeping. Another way i could think of is adjusting the mtimes using touch. So touch the sources -1s or the target +1s after creation of the target. Depending on the graph that might cause other trouble i guess. Henning
