git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Linus Torvalds <torvalds@osdl.org>
Date
Oct 1, 2006, 19:56 UTC
Message-ID
<Pine.LNX.4.64.0610011255030.3952@g5.osdl.org>
In-Reply-To
<7vlknz27qm.fsf@assigned-by-dhcp.cox.net>
On Sun, 1 Oct 2006, Junio C Hamano wrote:
Show 7 quoted lines
> 
> 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?
Nope.
Then I just get
	make[1]: Entering directory `/home/torvalds/git/perl'
	Running Mkbootstrap for Git ()
	chmod 644 Git.bs
	rm -f blib/arch/auto/Git/Git.so
	gcc  -shared -L/usr/local/lib Git.o  -o blib/arch/auto/Git/Git.so       \
	        \
	  
	gcc: Git.o: No such file or directory
	gcc: no input files
instead.

If that file isn't even supposed to _exist_, then why do we have build rules etc crap to do all this? It sounds like the makefiles are broken.

		Linus
Previous: Junio C HamanoNext: Johannes Schindelin
Message 9 of 13 in “What will happen to git.git in the near future”
  1. Junio C HamanoSep 24, 2006
  2. Petr BaudisSep 24, 2006
  3. Rene ScharfeSep 24, 2006
  4. Johannes SchindelinSep 24, 2006
  5. A Large Angry SCMSep 24, 2006
  6. Junio C HamanoOct 1, 2006
  7. Linus TorvaldsOct 1, 2006
  8. Junio C HamanoOct 1, 2006
  9. Linus TorvaldsOct 1, 2006
  10. Johannes SchindelinOct 1, 2006
  11. Linus TorvaldsOct 1, 2006
  12. Johannes SchindelinOct 1, 2006
  13. Linus TorvaldsOct 1, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.