linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Taylor <rob.taylor@codethink.co.uk>
To: Josh Triplett <josh@freedesktop.org>
Cc: Josh Triplett <josht@linux.vnet.ibm.com>, linux-sparse@vger.kernel.org
Subject: Re: [PATCH] c2xml
Date: Sun, 15 Jul 2007 00:54:01 +0100	[thread overview]
Message-ID: <46996219.8030602@codethink.co.uk> (raw)
In-Reply-To: <46986C26.9040804@freedesktop.org>

Josh Triplett wrote:
> Josh Triplett wrote:
>> On Fri, 2007-07-13 at 16:50 +0100, Rob Taylor wrote:
>>> Any followups on this?
>> I actually committed the first three patches this morning, before you
>> sent this.  I would like to commit the fourth patch this evening.  I
>> want to think a bit about how to address one issue: I'd really love to
>> avoid constructs specific to GNU make, such as ifeq and $(shell).  I
>> managed to find a way to do that for the patch adding clean kernel-style
>> build output, by using the text substitution feature of make variable
>> expansion.  However, I haven't yet figured out a way to avoid $(shell)
>> with this patch.  The c2xml target can just always exist, so no
>> conditionals needed there.  However, without $(shell), I don't see any
>> way to handle adding c2xml to PROGRAMS and INST_PROGRAMS without
>> $(shell); backquotes will only work in the commands of a target, not the
>> prerequisites.  (Obviously, just leaving c2xml out of the all and
>> install targets would solve the problem, but that seems quite
>> suboptimal.)  I want to think about this problem for a bit, and if I
>> don't come up with anything and don't get any good suggestions, I may
>> just go ahead and require GNU make.
> 
> OK, forget it.  Anyone who wants Sparse to work with non-GNU make gets to rack
> *their* brain thinking about how to do without useful GNU make features.
> Patch applied...

Heh, I think that's a fair enough stance now-a-days :)

>> Also, you didn't update the dtd for the changes to the position
>> handling; it doesn't have end-file, and it still has start and end
>> rather than {start,end}-{line,col}.
> 
> ... and I fixed this myself.

Brilliant!

> Thanks again for some most impressive work.

Thanks for putting the time in on it yourself!

Now to go and write interesting things using c2xml :)

Thanks,
Rob

      reply	other threads:[~2007-07-14 23:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-27 13:51 [PATCH] c2xml Rob Taylor
2007-06-27 18:49 ` Josh Triplett
2007-06-28  5:45   ` Josh Triplett
2007-06-28 11:00     ` Rob Taylor
2007-07-02 12:32   ` Rob Taylor
2007-07-13 15:50     ` Rob Taylor
2007-07-13 17:55       ` Josh Triplett
2007-07-14  6:24         ` Josh Triplett
2007-07-14 23:54           ` Rob Taylor [this message]

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=46996219.8030602@codethink.co.uk \
    --to=rob.taylor@codethink.co.uk \
    --cc=josh@freedesktop.org \
    --cc=josht@linux.vnet.ibm.com \
    --cc=linux-sparse@vger.kernel.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).