Hi, I'm following the WineGit instructions to try and discover why Money 2004 doesn't run with 0.9.12 or later. This is the first time I have tried to do regression testing, so I need some help. Is this the correct group to ask? I have installed git 1.1.4, copied the GIT repository to my PC, installed g++, yacc and bison, bisected the source tree and compiled. I then ran Money and just get this message: ./wine: could not locate Wine source tree FYI I installed the GIT repository in ~/tony/bin/wine-git and I am running Money in that folder with the following shell script: #!/bin/bash pwd ./wine ~/.wine/drive_c/Program\ Files/Microsoft\ Money/System/msmoney.exe ~/.wine/drive_c/My\ Documents/Money/MyMoney.mny> /var/log/scripts/tstmoney.log 2>&1(note: from ./wine onwards, this is on a single line) I suspect this is something simple. Any help will be much appreciated. Tony Ubuntu Dapper Drake user
Tony Pursell <ajp@princeswalk.fsnet.co.uk> wrote:> tried to do regression testing, so I need some help. Is this the > correct group to ask?Yes.> I have installed git 1.1.4, copied the GIT repository to my PC, > installed g++, yacc and bison, bisected the source tree and compiled. I > then ran Money and just get this message: > > ./wine: could not locate Wine source tree > > FYI I installed the GIT repository in ~/tony/bin/wine-git and I am > running Money in that folder with the following shell script:So the whole source tree is in ~/tony/bin/wine-git? In that case, it should work and I cannot see why it doesn't. Did you maybe get any errors during './configure' or 'make depend && make'? Daniel
Tony Pursell <ajp@princeswalk.fsnet.co.uk> wrote:>> So the whole source tree is in ~/tony/bin/wine-git? In that case, it >> should work and I cannot see why it doesn't. Did you maybe get any >> errors during './configure' or 'make depend && make'? > > I think there were some errors. I have been looking at the winewrapper > script and see that a file winerserver should be in the server folder. > Well, it isn't. So something must have gone wrong. Is the output from > the compile logged anywhere? There is a lot of stuff in config.log.Not by default; config.log is only for './configure'. Have a look at 'man script'.> Any ideas what I should do next. Compile again?Yes. Daniel
Tony Pursell <ajp@princeswalk.fsnet.co.uk> wrote:> Any suggestions with where I go from here? I suppose there is always a > chance that if you bisect the repository at an arbitrary point between x > and y there is always likely to be a couple of broken modules.Yes, indeed. Bisection should always start with known good sources, i.e. the starting and ending point should be released wine versions. Daniel
Hi all My attempts at regression testing Money 2004 continue. The problem I have is that git bisect good doesn't move on. Here is the bisect log after some compiles: git-bisect start # bad: [10affb33aa90f949dca5ea0e3bf168f993edb9d6] Release 0.9.12. git-bisect bad 10affb33aa90f949dca5ea0e3bf168f993edb9d6 # good: [af1714c70a8e138c4200c7840bdc4913c97b7767] Release 0.9.9. git-bisect good af1714c70a8e138c4200c7840bdc4913c97b7767 # good: [ff0d10983c9ae7c6b225c7b81f2cb56e738cded7] imaadp32: Renamed the dlls/msacm/imaadp32 directory to dlls/imaadp32.acm. git-bisect good ff0d10983c9ae7c6b225c7b81f2cb56e738cded7 # good: [ff0d10983c9ae7c6b225c7b81f2cb56e738cded7] imaadp32: Renamed the dlls/msacm/imaadp32 directory to dlls/imaadp32.acm. git-bisect good ff0d10983c9ae7c6b225c7b81f2cb56e738cded7 # good: [ff0d10983c9ae7c6b225c7b81f2cb56e738cded7] imaadp32: Renamed the dlls/msacm/imaadp32 directory to dlls/imaadp32.acm. git-bisect good ff0d10983c9ae7c6b225c7b81f2cb56e738cded7 # good: [ff0d10983c9ae7c6b225c7b81f2cb56e738cded7] imaadp32: Renamed the dlls/msacm/imaadp32 directory to dlls/imaadp32.acm. git-bisect good ff0d10983c9ae7c6b225c7b81f2cb56e738cded7 The instructions say I should only need to do git bisect good (or bad) each time after the compile and test. Is that right? It has reported Bisecting: 204 revisions left to test after this and repeated the same compile for the last three runs. There is an error message after 'git bisect good': fatal: Entry 'tools/winewrapper' not uptodate. Cannot merge. Does this have something to do with it? Tony