I can confirm that I just saw this bug reproduced this morning. But then when I retried it almost immediately, with the same environment, the build succeeded. From the difference between the two build logs, it appears that in the failed build it was doing automatic runs of aclocal-1.7, config.status --recheck, etc.
Maybe there's a timestamp skew problem in one of the patches that sometimes, if a second boundary happens just in the wrong place, causes those things to be rerun? -- Daniel Schepler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
