http://bugs.winehq.org/show_bug.cgi?id=13335
--- Comment #30 from Rich Rincebrain@gmail.com 2008-05-25 04:13:51 --- I'd have to recommend doing git bisect to find out where, exactly, this goes terribly wrong.
There's a howto on the wiki (http://wiki.winehq.org/RegressionTesting), but the important parts are to start a bisect (git bisect start), tag 0.9.56 as good (git reset --hard wine-0.9.56;git bisect good), then tag 0.9.57 as bad (git reset --hard wine-0.9.57;git bisect bad), and then repeat. You'll only have to do log(N) (rounded up) compiles, where N is the number of commits it tells you are left. Conveniently, since it's just between one revision of wine, it's only about 2 weeks of commits, and ccache will probably be very helpful to you. :)