http://bugs.winehq.org/show_bug.cgi?id=15377
--- Comment #16 from James Hawkins truiken@gmail.com 2008-09-23 19:24:15 --- (In reply to comment #15)
is a compile from git 1.1.5 different from a 1.1.5 install?
Technically, yes, if by a 1.1.5 install, you mean an installed package from your distribution.
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.
As I said before, a distro-packaged 1.1.5 can potentially be different from a compiled git at 1.1.5.
if i have done
- $ git bisect reset
- $ git bisect start
- $ git bisect good wine-1.1.4
- $ git bisect bad wine-1.1.5
- $ CC="ccache gcc" ./configure && make clean && make depend && make
- $ ~/wine-git/wine your_program.exe
- 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?
- bisect reset (so i am using 1.1.5 code base)
- CC="ccache gcc" ./configure && make clean && make depend && make
- $ ~/wine-git/wine your_program.exe
No, if your git is up to date, then you're past the 1.1.5 release. To get back to the 1.1.5 release,
$ echo d381c7cbf4d463189f479a0b3986f6767aeb8dba > .git/refs/heads/master $ git checkout -f master
and make sure that the game fails on 1.1.5 ?
Yes we need to know if it fails. Please run it a couple times if it doesn't fail, as the failure may be nondeterministic. This may also be the reason why the regression test failed, though I have my doubts, because you keep landing on the same commit. Please respond to the question, "Did you ever get a chance to run a 'git bisect bad' command?"