git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: occitan@esperanto.org
Cc: git@vger.kernel.org
Subject: Re: Compiling git with makepp patch
Date: Mon, 23 Aug 2010 23:32:20 -0500	[thread overview]
Message-ID: <20100824043220.GA20037@burratino> (raw)
In-Reply-To: <4C71A53F.2020108@t-online.de>

Hi,

Daniel Pfeiffer wrote:

> .PHONY: FORCE
> 
> I don't know why you depend on a phony that has no rule — I also had
> to make that possible.

Surely the name explains it. :)

> The file needs to be built immediately so
> that it can be included, before reading the rest of the makefile.
> But the dependency is only known to be phony after running the rule.
> Here you have a hen-egg problem, where I have no clue how Gnu make
> can cope (this is the one case where it requires .PHONY).

GNU make, unlike, say, pmake, reads all the rules before it runs
anything iirc.  So you can have

 -include foo

 foo:
	echo bar: >foo
	echo '	echo hi' >>foo

and it will cope okay.

Anyway, the git makefile is very far from topologically sorted; if
you are suggesting we change that, that's fine with me, as long as
the new rule is somehow justified and consistent.

Hope that helps,
Jonathan

  parent reply	other threads:[~2010-08-24  4:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <84FD9808A65CDF4C959FDB41FC3D134CBCF306D6@MSSRVS4.atlas.de>
2010-08-22 22:31 ` Compiling git with makepp patch Daniel Pfeiffer
2010-08-23  7:47   ` Thomas Rast
2010-08-23  9:00     ` Jakub Narebski
2010-08-25 21:08     ` Daniel Pfeiffer
2010-08-23 20:27   ` Ævar Arnfjörð Bjarmason
2010-08-25 20:58     ` Daniel Pfeiffer
2010-08-24  4:32   ` Jonathan Nieder [this message]
2010-08-25 20:41     ` Daniel Pfeiffer
2010-08-25 21:56       ` Andreas Schwab
2010-08-25 22:53         ` Junio C Hamano
2010-08-26  0:20           ` Jonathan Nieder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100824043220.GA20037@burratino \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=occitan@esperanto.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).