[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Trouble with dom0 and domU compilation


  • To: James Rhett Aultman <jaultman@xxxxxxxxxxxx>
  • From: Kip Macy <kip.macy@xxxxxxxxx>
  • Date: Sun, 4 Dec 2005 16:09:22 -0600
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Sun, 04 Dec 2005 22:09:25 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Zx3vh3i9pocb9S2AOX7vj/Ywx6B2R4fqzx/iLRZa/7MXjcknYo80PHzC01kogGIsvGgtYZCIvsqZi5in2+1ThL+jDLoKAFE67e6y3bIR0CSRLeGh/QhVfxOTMadSXJuRPvNX/+lbfeLObaW+MbDnpT9TzMjHGeBJWYT8fnXmmn0=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Did you do a make config of some sort?

On 12/4/05, James Rhett Aultman <jaultman@xxxxxxxxxxxx> wrote:
Keir Fraser wrote:

>
> On 4 Dec 2005, at 17:59, James Rhett Aultman wrote:
>
>> I've been trying to compile the source for xen Linux dom0 and domU
>> kernel images from source, and I'm getting a compile time error I don't
>> know how to fix:
>>
>> arch/i386/kernel/process.c: In function `cpu_idle':
>> arch/i386/kernel/process.c:195: error: `cpu' undeclared (first use in
>> this function)
>>
>> this is for the xen0 and xenU of linux-2.6.12
>>
>> Advice appreciated
>
>
> Specify ARCH=xen (ARCH=xen make <target>).


Hm...that gets around one problem, but now I seem to have another build
failure:

/bin/sh: line 1: arch//kernel/asm-offsets.s: No such file or directory
  UPD   include/asm-xen/asm_offsets.h
Mv: cannot stat `include/asm-xen/asm_offsets.h.tmp': No such file or
directory
make: *** [include/asm-xen/asm_offsets.h.tmp] Error 1

--
Rhett.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.