Re: What will happen to git.git in the near future

From: Junio C Hamano <junkio@cox.net>
Date: Oct 1, 2006, 18:47 UTC
Message-ID: <7vlknz27qm.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <Pine.LNX.4.64.0610011132040.3952@g5.osdl.org>

Linus Torvalds <torvalds@osdl.org> writes:

Show 20 quoted lines

> On Sun, 1 Oct 2006, Junio C Hamano wrote:
>>
>> I've tagged the tip of the master as v1.4.3-rc1 tonight, after
>> merging things that I listed in the message last week to be
>> merged from "next".
>> 
>> Have fun.
>
> I hate that perl crud.
>...
> 	Git.xs: In function 'XS_Git_xs_version':
> 	Git.xs:62: error: 'GIT_VERSION' undeclared (first use in this function)
> 	Git.xs:62: error: (Each undeclared identifier is reported only once
> 	Git.xs:62: error: for each function it appears in.)
> 	make[1]: *** [Git.o] Error 1
> 	make[1]: Leaving directory `/home/torvalds/git/perl'
> 	make: *** [all] Error 2
>
> I don't like how git now doesn't compile just out of the box on a 
> perfectly regular FC5 box.

Everybody hated the perl crud, so we removed Git.xs and is not even part of the source anymore.

This is a symptom that Git.c leftover from an earlier build was in the working tree. Could you try running "rm -f perl/Git.c" before building and see if it helps?

The sad thing is that we do not ship Git.xs nor generate Git.c from our Makefile, and while it is nicer to have an entry to remove leftover perl/Git.c in our Makefile, it does not really help in all cases. We discussed this exact issue a few days ago:

http://thread.gmane.org/gmane.comp.version-control.git/27730/focus=27853