On Fri, Sep 30, 2011 at 12:43 PM, David Lichteblau <firstname.lastname@example.org> wrote:
perhaps you've seen it; I've pushed fixes earlier today.
Quoting David Lichteblau (email@example.com):
> Quoting Elliott Slaughter (firstname.lastname@example.org):
> > Hm, nope same error in 4aad6e46. The relevant section of the build log is
> > the same other than the error in coreparse moving down two lines.
> The build is broken on Windows in several respects. I will take care of
> these issues today.
Can you test on your Windows to double-check? Please note that there's
still the test output directory cleanup issue; sorry about that.