From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: jeremy.fitzhardinge@citrix.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: redefinition of typedef '__guest_handle_uint64_t'
Date: Mon, 8 Aug 2011 10:37:23 -0400 [thread overview]
Message-ID: <20110808143723.GB7213@dumpdata.com> (raw)
In-Reply-To: <alpine.DEB.2.01.1108080146000.9183@trent.utfs.org>
On Mon, Aug 08, 2011 at 01:54:39AM -0700, Christian Kujau wrote:
> Hi,
>
> when trying to compile xen/next-3.0 from Jeremy's tree, this happens:
Ugh, just use the released 3.0 stock kernel.
>
> ---------------------------------------------------
> /usr/local/src/linux-xen-next-3-git/arch/x86/kernel/asm-offsets.c:8:
> /usr/local/src/linux-xen-next-3-git/include/xen/interface/xen.h:527:1:
> error: redefinition of typedef '__guest_handle_uint64_t'
> /usr/local/src/linux-xen-next-3-git/arch/x86/include/asm/xen/interface.h:58:1:
> note: previous declaration of '__guest_handle_uint64_t' was here
> ---------------------------------------------------
>
> The .config is here: http://nerdbynature.de/bits/3.0-rc7/
> The following makes it compile again, but it may not be the Right Thing
> to do:
>
> diff --git a/include/xen/interface/xen.h b/include/xen/interface/xen.h
> index 3c072c8..5a91c66 100644
> --- a/include/xen/interface/xen.h
> +++ b/include/xen/interface/xen.h
> @@ -524,8 +524,6 @@ struct tmem_op {
> } u;
> };
>
> -DEFINE_GUEST_HANDLE(uint64_t);
> -
> #else /* __ASSEMBLY__ */
>
> /* In assembly code we cannot use C numeric constant suffixes. */
>
>
> Thanks,
> Christian.
> --
> BOFH excuse #100:
>
> IRQ dropout
next prev parent reply other threads:[~2011-08-08 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 8:54 redefinition of typedef '__guest_handle_uint64_t' Christian Kujau
2011-08-08 14:37 ` Konrad Rzeszutek Wilk [this message]
2011-08-08 22:13 ` Jeremy Fitzhardinge
2011-08-09 4:28 ` Christian Kujau
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=20110808143723.GB7213@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
/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.