From: Andreas Schwab <schwab@linux-m68k.org>
To: occitan@esperanto.org
Cc: Jonathan Nieder <jrnieder@gmail.com>, git@vger.kernel.org
Subject: Re: Compiling git with makepp patch
Date: Wed, 25 Aug 2010 23:56:11 +0200 [thread overview]
Message-ID: <m262yyuzk4.fsf@igel.home> (raw)
In-Reply-To: <4C758016.8070104@t-online.de> (Daniel Pfeiffer's message of "Wed, 25 Aug 2010 22:41:58 +0200")
Daniel Pfeiffer <occitan@t-online.de> writes:
> la 08/24/2010 06:32 AM Jonathan Nieder skribis:
>> Hi,
>>
>> Daniel Pfeiffer wrote:
>>> 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.
> While that is not the usual use-case for -include, the file might very
> well define some macros, and the rest of the makefile, indeed the foo-rule
> itself might depend on those macros.
GNU make will restart reading all makefiles when any of them was remade.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2010-08-25 21:56 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
2010-08-25 20:41 ` Daniel Pfeiffer
2010-08-25 21:56 ` Andreas Schwab [this message]
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=m262yyuzk4.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.