Steps to reproduce the problem:
-------------------------------
1. Download and untar monotone 1.0 source.
2. ./configure
3. make; make -j2
Expected result:
----------------
First make causes monotone to build. Second call to make does almost
nothing.
Actual results:
---------------
First make invocation builds monotone. Second make call does not
complete, consumes 100% CPU indefinitely.
---------------
This issue was discovered while debugging build failures of Monotone
under Debian. It seemed like it only affected the make check target,
but it appears to affect multiple successive make invocations when
using the -j option to Make.
Reported by Francis Russell, Apr 25, 2011