make error after git bisect

[fcmartins]

Hi,
I'm trying to spot the patch that caused recently a regression in Spellforce, but after a couple of iterations I'm getting an error in make:

Code: Select all

checking whether we need to define __i386__... no
configure: creating ./config.status
config.status: creating Make.rules
config.status: error: invalid argument: `Make.tmp'
make: *** [Makefile] Error 1
nando@megaman:~/wine-git$ 

What could I do?

[Addys]

Try make clean. if that still doesn't work, try make distclean.

[fcmartins]

Try make clean. if that still doesn't work, try make distclean.

nope, gives the same error in both cases.

It looks like git bisect chooses a set of patches which is not consistent on itself.

Alternatively, how can I use git to specify that I want a specific wine version (not in the FAQ, neither in the two main git wiki pages).

[fcmartins]

Alternatively, how can I use git to specify that I want a specific wine version (not in the FAQ, neither in the two main git wiki pages).

so, checkout seems to be the command to extract a tagged revision.

Doing

git checkout wine-1.1.43

is fine, but

git checkout wine-1.1.42 (or 41)

results in the same error

Code: Select all

configure: creating ./config.status
config.status: creating Make.rules
config.status: error: invalid argument: `Make.tmp'
make: *** [Makefile] Error 1

Is there a problem in doing successive checkouts or does it need some sort of resetting in between?

[fcmartins]

Is there a problem in doing successive checkouts or does it need some sort of resetting in between?

ok, I was running merely make and that alone only works for the first time.

[walt]

On 04/30/2010 08:14 AM, fcmartins wrote:

Hi,
I'm trying to spot the patch that caused recently a regression in Spellforce,
but after a couple of iterations I'm getting an error in make...

IIUC you've solved your problem already but I'll just mention anyway that when
you are git-bisecting you may occasionally land on an intermediate commit that
won't compile.

At that point you can try "git bisect skip" to tell git to move forward or back
one commit (to avoid the non-compiling commit) and then try compiling again.

Frankly, I don't recall this has ever worked for me, but it takes two minutes
to try it, so what the heck.