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

Re: [PATCH] perl bindings fix compilation errors

From
Junio C Hamano <junkio@cox.net>
Date
Sep 26, 2006, 04:54 UTC
Message-ID
<7vfyeftehf.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<4517BEBC.4000002@shadowen.org>
Andy Whitcroft <apw@shadowen.org> writes:
> I am somewhat unhappy that a make clean at the top level and remake was
> not sufficient to get a working tree.

Sympathetic I am (since I was bitten by it too), but I am not sure what the right thing to do.

It is certainly incorrect to say that it is a driver error to git-pull (or git-checkout to switch branches) without running "make clean" first to get rid of perl/Git.c while your Makefile still knows it is a generated file. Our Makefile should be more helpful.

But the question is Makefile in which branch?

Ideally, if Makefile of each and every branch head currently alive knew that perl/Git.c is problematic and removed it, then we would not suffer from this problem. But it's obviously not practical.

Previous: Johannes SchindelinNext: Johannes Schindelin
Message 5 of 8 in “perl bindings fix compilation errors”
  1. perl bindings fix compilation errorsAndy Whitcroft, Sep 25, 2006
  2. Johannes SchindelinSep 25, 2006
  3. Andy WhitcroftSep 25, 2006
  4. Johannes SchindelinSep 25, 2006
  5. Junio C HamanoSep 26, 2006
  6. Johannes SchindelinSep 26, 2006
  7. Junio C HamanoSep 27, 2006
  8. Johannes SchindelinSep 27, 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.