Fix confusing smart console output from concurrent builds

Developers tend to blame the last printed line when a build takes too
long. Unfortunately, when building concurrently, the last printed line
may have actually finished a long time ago. Under the current system,
ninja does not update the status line to reflect what jobs are still
running. This change makes ninja always print the oldest still running job
instead. In other words, the likely build bottlenecks.

Patch from David Zarzycki, originally uploaded at #1320.

0 files changed, 0 insertions, 0 deletions