On Sunday 26 April 2009, Andreas Metzler wrote: > This looks similar to #525494. Do you perhaps have set the > environment variable MAKEFLAGS=-jX? (Witch X > 1, check with > printenv).
Yes, Andreas, you're bang on - it looks like the same bug, and I do indeed have -j set - mostly for the benefits it gives, even on this rinky Atom 1.6GHz. I'm loathe to disable the -j setting, however, for that reason. I see in #525494 that you suggest the hugin Makefiles may be the causal factor - is this something you guys are taking upstream to the hugin developers? It seems that it's not a Debian problem, of course, so I'd be surprised if only us two Debian users have struck the problem. Even more so given that multi-core CPUs are now the norm rather than the exception. What do you recommend (other than either what I'm doing now - temporarily renaming rm - or going back to a single make thread via MAKEFILES) for the long term? cheers, Jedd. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org