From: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
To: Junio C Hamano <gitster@pobox.com>
Cc: GIT Mailing-list <git@vger.kernel.org>, bebarino@gmail.com
Subject: Re: [PATCH v2 7/9] sparse: Fix errors due to missing target-specific variables
Date: Thu, 21 Apr 2011 20:06:52 +0100 [thread overview]
Message-ID: <4DB0804C.10908@ramsay1.demon.co.uk> (raw)
In-Reply-To: <7vbp025clq.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> Ramsay Jones <ramsay@ramsay1.demon.co.uk> writes:
>
>> I decided not to mark the $(SP_OBJ) as .PHONY targets; after some
>> testing, it seems that it is not necessary, even if users do
>> something like:
>> make git.sp 2>git.sp
[...]
>> -help.o: common-cmds.h
>> +help.sp help.o: common-cmds.h
>
> I am not sure if you even want any dependency listed for any %.sp target
> to begin with.
without these common-cmds.h dependencies, I get something like:
$ make clean
...
$ make help.sp
GIT_VERSION = 1.7.5.rc2.10.g4d94
* new build flags or prefix
SP help.c
help.c:6:10: error: unable to open 'common-cmds.h'
make: *** [help.sp] Error 1
whereas, with them:
$ make clean
...
$ make help.sp
GIT_VERSION = 1.7.5.rc2.10.g937d2
* new build flags or prefix
GEN common-cmds.h
SP help.c
[...]
> So why list any dependency? If it is sensible to treat "sparse" target
> just like "clean" target, it would make sense not to give it any
> dependencies and mark it as .PHONY, no?
After some experiments, looking through the output of "make -d ...", I think
I have a solution which (hopefully) addresses your concerns ...
Version 3 of the patch coming up ...
ATB,
Ramsay Jones
next prev parent reply other threads:[~2011-04-21 19:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 17:32 [PATCH v2 7/9] sparse: Fix errors due to missing target-specific variables Ramsay Jones
2011-04-19 18:18 ` Junio C Hamano
2011-04-21 19:06 ` Ramsay Jones [this message]
2011-04-21 20:35 ` Junio C Hamano
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=4DB0804C.10908@ramsay1.demon.co.uk \
--to=ramsay@ramsay1.demon.co.uk \
--cc=bebarino@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.