Hello again to James and "vitamin", This is still giving trouble. This time I kept a log of precisely what I did. Here it is > > alan@Ubuntu:~$ git clone git://source.winehq.org/git/wine.git wine-git > fatal: destination path 'wine-git' already exists and is not an empty directory. > alan@Ubuntu:~$ rm -r wine-git > rm: remove write-protected regular file `wine-git/.git/objects/pack/pack-71326c4a91beddaf9d67d504ac85dd8eedf2efae.idx'? y > rm: remove write-protected regular file `wine-git/.git/objects/pack/pack-71326c4a91beddaf9d67d504ac85dd8eedf2efae.pack'? y > alan@Ubuntu:~$ git clone git://source.winehq.org/git/wine.git wine-git > Initialized empty Git repository in /home/alan/wine-git/.git/ > remote: Counting objects: 573251, done. > remote: Compressing objects: 100% (104597/104597), done. > remote: Total 573251 (delta 466963), reused 573251 (delta 466963) > Receiving objects: 100% (573251/573251), 139.83 MiB | 645 KiB/s, done. > Resolving deltas: 100% (466963/466963), done. > alan@Ubuntu:~$ git bisect start > fatal: Not a git repository (or any of the parent directories): .git > alan@Ubuntu:~$ cd wine-git > alan@Ubuntu:~/wine-git$ git bisect start > alan@Ubuntu:~/wine-git$ git bisect good 1.0.1 > fatal: Needed a single revision > Bad rev input: 1.0.1 > alan@Ubuntu:~/wine-git$ git bisect good wine-1.0.1 > alan@Ubuntu:~/wine-git$ git bisect bad wine-1.2 > Bisecting: a merge base must be tested > [36def4af0ca85a1d0e66b5207056775bcb3b09ff] Release 1.0. > alan@ubuntu:~/wine-git$ ./configure > <hundred or so lines snipped> > configure: Finished. Do 'make depend && make' to compile Wine. > > alan@Ubuntu:~/wine-git$ make depend > <hundred or so lines snipped. 2 or 3 minutes. No evidence of error> > alan@ubuntu:~/wine-git$ make > <seversl hundred lines snipped. 20 minutes or so. ended with this> > ... > freetype.c:5031: error: called object ?pFT_MulFix? is not a function > freetype.c:5032: error: called object ?pFT_MulFix? is not a function > make[2]: *** [freetype.o] Error 1 > make[2]: Leaving directory `/home/alan/wine-git/dlls/gdi32' > make[1]: *** [gdi32] Error 2 > make[1]: Leaving directory `/home/alan/wine-git/dlls' > make: *** [dlls] Error 2 > alan@Ubuntu:~/wine-git$ At this point I logged in to post the update, and found the reply from "vitamin". I logged off and tried the suggestion, with this result > alan@Ubuntu:~$ cd wine-git > alan@Ubuntu:~/wine-git$ git clean -x > fatal: clean.requireForce defaults to true and neither -n nor -f given; refusing to clean > alan@Ubuntu:~/wine-git$ > As you can see this isn't going well. I appreciate it must be frustrating for you as well as me. I really am trying to be as independent as possible, and I do appreciate the help. And yes, I have read (and re-read several times) the Regression Testing guide you linked. Unfortunately it still isn't clear (at least to me) what steps should be included under the "repeat" instruction. For example, it says to repeat "make", but the "make" is under a "./configure" command as a multiple list of commands including "make depend" and "make". Also, these are under a different section than the instruction to repeat. How much of the intervening sequence has to be repeated? Subsequent attempts to clarify this don't seem to be working either. This is complicated even farther by not being able to get back to a starting point that is error free. To move on: It looks to me like I'm going to have to try to clean at least some of the utilities being used but, again, I'm not sure how far back to go. The clone of wine-git (seems to have failed above)? Git itself (it's included with the OS...I'm loathe to even try)? Are there "reset" commands like the "clean" that will deal with the indicated error states? Alan
