From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Christian Tramnitz <chris.ace@gmx.net>
Cc: xen-devel@lists.xensource.com
Subject: Re: problem compiling current pvops xen/master on x86
Date: Mon, 25 Jan 2010 09:48:58 -0500 [thread overview]
Message-ID: <20100125144858.GA29533@phenom.dumpdata.com> (raw)
In-Reply-To: <hjk5pq$3ph$1@ger.gmane.org>
On Mon, Jan 25, 2010 at 02:19:44PM +0100, Christian Tramnitz wrote:
> Hi,
>
> I have been running my systems on 2.6.29-xen-r4 (based on Andrew Lyon's
> ebuild) for some time but with Xen 4.0.0 around the corner I wanted to
> give the latest pvops a quick glance.
>
> However I'm not even able to compile it:
>
> CC arch/x86/kernel/acpi/boot.o
> In file included from arch/x86/kernel/acpi/boot.c:45:
> /usr/src/linux-pvops/arch/x86/include/asm/xen/pci.h:37: error: expected
> declaration specifiers or '...' before 'domid_t'
> make[3]: *** [arch/x86/kernel/acpi/boot.o] Error 1
> make[2]: *** [arch/x86/kernel/acpi] Error 2
> make[1]: *** [arch/x86/kernel] Error 2
> make: *** [arch/x86] Error 2
>
> This build was meant for a x86 domU (dom0 support is disabled), I have
> nothing special in my kernel config (basically created with make
> oldconfig from my running config), maybe except for pcifront support
> (which is primary reason for not using a vanilla linux kernel).
>
>
> Any ideas?
Yeah, I've a patch for that in the my tree and as well to get the pv-ops kernel
to compile on PPC and IA64 (and MIPS/StrongARM).
The solutions for the most part are unfortunatly hacks.
Here is the git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git rpm-draft-3
I am going to ask Jeremy to pull in a patch for that specific issue in
his tree.
next prev parent reply other threads:[~2010-01-25 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 13:19 problem compiling current pvops xen/master on x86 Christian Tramnitz
2010-01-25 14:48 ` Konrad Rzeszutek Wilk [this message]
2010-01-25 15:18 ` Christian Tramnitz
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=20100125144858.GA29533@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=chris.ace@gmx.net \
--cc=xen-devel@lists.xensource.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.