From: David Woodhouse <dwmw2@infradead.org>
To: Dennis Heuer <dh@triple-media.com>
Cc: linux-kernel@vger.kernel.org, dot@dotat.at
Subject: Re: sunifdef instead of unifdef
Date: Thu, 05 Oct 2006 15:40:53 +0100 [thread overview]
Message-ID: <1160059253.26064.69.camel@pmac.infradead.org> (raw)
In-Reply-To: <20061005150816.76ca18c2.dh@triple-media.com>
On Thu, 2006-10-05 at 15:08 +0200, Dennis Heuer wrote:
> unifdef is not only very old and unmaintained, the binary does not work
> and the source does not compile on a pure x86_64 system.
It works for me. Describe your problem more coherently.
I wouldn't describe it as 'very old' -- the last commit seems to have
been last March, which isn't _so_ recent but perhaps it just hasn't
_needed_ an update?
Neither would I describe it as unmaintained. Tony was quite quickly
responsive when I asked him if it would be OK to include unifdef in the
kernel source tree.
> There is another tool that worked for me--though it 'closed with
> remarks'--and that was updated recently (several times this year). It
> is called sunifdef, is under an equal (new) BSD license, and is
> proposed to be the successor of unifdef. See the project page:
>
> http://www.sunifdef.strudl.org/
I don't see a huge point in changing, unless it lets us get rid of stuff
like
#if defined(__KERNEL__ && ....
when used with -U__KERNEL__.
--
dwmw2
next prev parent reply other threads:[~2006-10-05 14:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 13:08 Dennis Heuer
2006-10-05 13:47 ` Alexey Dobriyan
2006-10-05 14:40 ` David Woodhouse [this message]
2006-10-05 16:05 ` Tony Finch
2006-10-05 16:07 ` David Woodhouse
2006-10-05 16:12 ` Sam Ravnborg
2006-10-09 1:58 ` Valdis.Kletnieks
2006-10-05 16:38 Dennis Heuer
2006-10-05 19:26 ` Sam Ravnborg
2006-10-05 20:37 ` Jan Engelhardt
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=1160059253.26064.69.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=dh@triple-media.com \
--cc=dot@dotat.at \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®