http://bugs.winehq.org/show_bug.cgi?id=15377
--- Comment #15 from Ben Trusty ben.trusty@gmail.com 2008-09-23 18:45:10 --- (In reply to comment #14)
Have you compiled 1.1.5 from git and made sure that the game is broken with that build? At any point during the regression test did you issue a git bisect bad? If it says 'first bad commit', then the test is done.
is a compile from git 1.1.5 different from a 1.1.5 install?
the reason this whole thing started was b/c i did an update from 1.1.4 to 1.1.5 and then the game did not work. so i did the regression testing and started this bug post.
if i have done 1. $ git bisect reset 2. $ git bisect start 3. $ git bisect good wine-1.1.4 4. $ git bisect bad wine-1.1.5 5. $ CC="ccache gcc" ./configure && make clean && make depend && make 6. $ ~/wine-git/wine your_program.exe 7. If good A) $ git bisect good If bad B) $ git bisect bad
till it got to the point that it gave the same output (previous post), and hasnt said "Bisecting: 0 revisions left to test after this" during the last three times of doing processes 5-7.
what do i need to do now? 1. bisect reset (so i am using 1.1.5 code base) 2. CC="ccache gcc" ./configure && make clean && make depend && make 3. $ ~/wine-git/wine your_program.exe
and make sure that the game fails on 1.1.5 ?
then what?