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

[Xen-devel] Problems Building Xen 4.0.x on ia64 (various releases)


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Julio C. Ortega" <jortega@xxxxxxxxx>
  • Date: Sun, 19 Dec 2010 10:08:16 -0430
  • Delivery-date: Sun, 19 Dec 2010 06:40:37 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Good morning

Sorry to post this problem in this list, i wasn't sure that posting to xen-users got me a reply


I've faced a couple of problems building Xen 4.0.0, 4.0.1 and 4.0.2rc1
from sources on an itanium2 machine running debian 6.0

I'll describe the problems i've faced with all three releases.

XEN 4.0.0:

Downloaded with hg:

hg clone -r RELEASE-4.0.0 http://xenbits.xen.org/xen-4.0-testing.hg
xen-4.0.0

Almost everything compiles, the problem i'm facing it's when make world
it's building the xen tools:

gcc  -O2 -fomit-frame-pointer -fno-strict-aliasing -std=gnu99 -Wall
-Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement
-D__XEN_TOOLS__ -MMD -MF .xc_dom_ia64.o.d  -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -D_GNU_SOURCE -I../../xen/common/libelf -Iia64
-Werror -Wmissing-prototypes  -I. -I../xenstore -I../include -c -o
xc_dom_ia64.o xc_dom_ia64.c
In file included from xc_dom_ia64.c:26:
ia64/asm/dom_fw_common.h:47:23: error: asm/fpswa.h: No such file or
directory
In file included from xc_dom_ia64.c:26:
ia64/asm/dom_fw_common.h:65: error: expected specifier-qualifier-list
before ?fpswa_interface_t?
make[5]: *** [xc_dom_ia64.o] Error 1
make[5]: exiting `/root/xen-4.0.0/tools/libxc'
make[4]: *** [build] Error 2
make[4]: exiting `/root/xen-4.0.0/tools/libxc'
make[3]: *** [subdir-install-libxc] Error 2
make[3]: exiting `/root/xen-4.0.0/tools'
make[2]: *** [subdirs-install] Error 2
make[2]: exiting `/root/xen-4.0.0/tools'

This particular problem also occurs in 4.0.1 and 4.0.2rc1 (testing) when
issuing: "make tools"

It must be something i'm missing, but i can't see what it could be (all
the build dependencies are met), i'm using gcc-4.4.5

XEN 4.0.1 & XEN 4.0.2rc1 (testing)

This two releases were downloaded also cloning with mercurial.

In addition to the problem compiling "tools" that i've described above
,this happens when making core xen or issuing "make world":

4.0.1:

d -g  -T xen.lds.s -N -Map /root/xen-4.0.1/xen/.xen-syms.0.map
linux-xen/head.o /root/xen-4.0.1/xen/common/built_in.o
/root/xen-4.0.1/xen/drivers/built_in.o
/root/xen-4.0.1/xen/xsm/built_in.o
/root/xen-4.0.1/xen/arch/ia64/built_in.o \
                /root/xen-4.0.1/xen/common/symbols-dummy.o -o
/root/xen-4.0.1/xen/.xen-syms.0
/root/xen-4.0.1/xen/common/built_in.o: In function `kexec_exec':
/root/xen-4.0.1/xen/common/kexec.c:493: undefined reference to
`continue_hypercall_on_cpu'
make[3]: *** [/root/xen-4.0.1/xen/xen-syms] Error 1

4.0.2rc1:

ld -g  -T xen.lds.s -N -Map /root/xen-4.0.2rc1/xen/.xen-syms.0.map
linux-xen/head.o /root/xen-4.0.2rc1/xen/common/built_in.o
/root/xen-4.0.2rc1/xen/drivers/built_in.o
/root/xen-4.0.2rc1/xen/xsm/built_in.o
/root/xen-4.0.2rc1/xen/arch/ia64/built_in.o \
                /root/xen-4.0.2rc1/xen/common/symbols-dummy.o -o
/root/xen-4.0.2rc1/xen/.xen-syms.0
/root/xen-4.0.2rc1/xen/common/built_in.o: In function `kexec_exec':
/root/xen-4.0.2rc1/xen/common/kexec.c:493: undefined reference to
`continue_hypercall_on_cpu'
make[3]: *** [/root/xen-4.0.2rc1/xen/xen-syms] Error 1


Digging up and googling i've found out nothing, but seems weird that
particularly continue_hypercall_on_cpu() it's only present in
architecture specific include files.

Any help would be greatly appreciated, even if it's pointing me to the
right direction for a successfull build.


Have a nice day.

--
------------------------------------
Julio C. Ortega
Technical Coordinator
Infrastructure
ONUVA
http://www.onuva.com


_______________________________________________
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®.