From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-kbuild@vger.kernel.org, sam@ravnborg.org
Subject: Re: unifdef problem (xen)
Date: Thu, 22 Oct 2009 12:54:57 -0700 [thread overview]
Message-ID: <4AE0B891.1010100@goop.org> (raw)
In-Reply-To: <20091022125223.66610093.rdunlap@xenotime.net>
On 10/22/09 12:52, Randy Dunlap wrote:
> Hi,
>
> I'm using xen.git
> <git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git>.
>
> When I build allmodconfig on x86_64 (with O=xx64), I see this warning:
>
>
> unifdef: /xen/xx64/usr/include/xen/privcmd.h.tmp: 79: Premature EOF (#if line 33 depth 1)
> unifdef: output may be truncated
>
>
> The original file contains:
> #ifndef __user
> #define __user
> #endif
>
> and the generated/unifdef output file contains:
> #ifndef #define #endif
>
> all on one line.
>
> Is this expected/normal? Is this a problem with unifdef or with something
> in xen.git?
>
I'd say its a bug in unifdef, but I'm not precisely sure what its trying
to do.
That said, there's no reason for those lines to be in privcmd.h, I think.
J
next prev parent reply other threads:[~2009-10-22 19:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 19:52 unifdef problem (xen) Randy Dunlap
2009-10-22 19:54 ` Jeremy Fitzhardinge [this message]
2009-10-22 20:29 ` Sam Ravnborg
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=4AE0B891.1010100@goop.org \
--to=jeremy@goop.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sam@ravnborg.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.