| |
|
 |
|
 |
|
|
|
| |
|
|
xen-ia64-devel
[Xen-ia64-devel] RE: Problems in building xen/ia64
Hi Shen --
Did you create a linux-2.6.11 tree and run
'bash arch/ia64/tools/mkbuildtree' as described
in the README? Also, "make" should be run from within
the xen directory (not xeno-unstable.bk) as none of the
other tools work for ia64 yet.
Yes, Xen/ia64 can utilize memory over 4GB (though I'm not sure
this has been tested recently so it wouldn't surprise me if
it doesn't work right now).
Dan
P.S. Postings should be sent to xen-ia64-devel, not
xen-ia64-devel-request.
> -----Original Message-----
> From: shenyl@xxxxxxxxx [mailto:shenyl@xxxxxxxxx]
> Sent: Wednesday, May 11, 2005 10:03 AM
> To: xen-ia64-devel-request
> Cc: Magenheimer, Dan (HP Labs Fort Collins)
> Subject: Problems in building xen/ia64
>
> dan,
> Thanks for your and the Xen developer's harding working
> i am a newbie of Xen. i have some problems in compiling
> the xen/ia64
> i want to trying xen/ia64 on a 4 x Itanium 2 HP server
> with 16G memory (Can Xen/ia64 utilise memory over 4G now?), OS rhel 3.
> The gcc info:
> gcc -v
> Reading specs from /usr/lib/gcc/ia64-redhat-linux/3.4.3/specs
> Configured with: ../configure --prefix=/usr
> --mandir=/usr/share/man --infodir=/usr/share/info
> --enable-shared --enable-threads=posix --disable-checking
> --with-system-zlib --enable-__cxa_atexit
> --disable-libunwind-exceptions
> --enable-languages=c,c++,objc,java,f77 --enable-java-awt=gtk
> --host=ia64-redhat-linux
> Thread model: posix
> gcc version 3.4.3 20041212 (Red Hat 3.4.3-9.EL4)
>
>
> I'm trying to compile the xeno-unstable.bk
> <http://xen.bkbits.net/xeno-unstable.bk> repository
> and follow the steps in README.ia64
> is some mistake i made or the platform?
> what should i do next for building and install Xen/ia64? Any
> suggestion will be helpful
>
>
> re-Type 'make' and get the error:
>
> rm -f include/xen/banner.h include/xen/compile.h
> drivers/char/console.o
> make -C arch/ia64 delete-unfresh-files
> make[1]: Entering directory `/home/Xen/xeno-unstable.bk/xen/arch/ia64'
> echo any unfresh-files to delete for ia64\?
> any unfresh-files to delete for ia64?
> make[1]: Leaving directory `/home/Xen/xeno-unstable.bk/xen/arch/ia64'
> make include/xen/compile.h
> make[1]: Entering directory `/home/Xen/xeno-unstable.bk/xen'
> tools/figlet/figlet -d tools/figlet Xen 3.0"-devel" >
> include/xen/banner.h.new
> __ __ _____ ___ _ _
> \ \/ /___ _ __ |___ / / _ \ __| | _____ _____| |
> \ // _ \ '_ \ |_ \| | | |__ / _` |/ _ \ \ / / _ \ |
> / \ __/ | | | ___) | |_| |__| (_| | __/\ V / __/ |
> /_/\_\___|_| |_| |____(_)___/ \__,_|\___| \_/ \___|_|
>
> make[1]: Leaving directory `/home/Xen/xeno-unstable.bk/xen'
> [ -e include/asm ] || ln -sf asm-ia64 include/asm
> make -C arch/ia64 asm-offsets.s
> make[1]: Entering directory `/home/Xen/xeno-unstable.bk/xen/arch/ia64'
> make[1]: `asm-offsets.s' is up to date.
> make[1]: Leaving directory `/home/Xen/xeno-unstable.bk/xen/arch/ia64'
> make include/asm-ia64/asm-offsets.h
> make[1]: Entering directory `/home/Xen/xeno-unstable.bk/xen'
> make[1]: `include/asm-ia64/asm-offsets.h' is up to date.
> make[1]: Leaving directory `/home/Xen/xeno-unstable.bk/xen'
> make -C common
> make[1]: Entering directory `/home/Xen/xeno-unstable.bk/xen/common'
> make[1]: Nothing to be done for `default'.
> make[1]: Leaving directory `/home/Xen/xeno-unstable.bk/xen/common'
> make -C drivers
> make[1]: Entering directory `/home/Xen/xeno-unstable.bk/xen/drivers'
> make -C char
> make[2]: Entering directory
> `/home/Xen/xeno-unstable.bk/xen/drivers/char'
> gcc -nostdinc -fno-builtin -fno-common -fno-strict-aliasing
> -O2 -iwithprefix include -Wall -fomit-frame-pointer
> -I/home/Xen/xeno-unstable.bk/xen/include -D__KERNEL__
> -I/home/Xen/xeno-unstable.bk/xen/include/asm-ia64
> -Wno-pointer-arith -Wredundant-decls -DIA64 -DXEN -DLINUX_2_6
> -ffixed-r13 -mfixed-range=f12-f15,f32-f127 -w -g -DNDEBUG -c
> console.c -o console.o
> ld -g -r -o driver.o console.o serial.o
> make[2]: Leaving directory
> `/home/Xen/xeno-unstable.bk/xen/drivers/char'
> make -C acpi
> make[2]: Entering directory
> `/home/Xen/xeno-unstable.bk/xen/drivers/acpi'
> make[2]: Nothing to be done for `default'.
> make[2]: Leaving directory
> `/home/Xen/xeno-unstable.bk/xen/drivers/acpi'
> make[1]: Leaving directory `/home/Xen/xeno-unstable.bk/xen/drivers'
> make -C arch/ia64
> make[1]: Entering directory `/home/Xen/xeno-unstable.bk/xen/arch/ia64'
> gcc -nostdinc -fno-builtin -fno-common -fno-strict-aliasing
> -O2 -iwithprefix include -Wall -fomit-frame-pointer
> -I/home/Xen/xeno-unstable.bk/xen/include -D__KERNEL__
> -I/home/Xen/xeno-unstable.bk/xen/include/asm-ia64
> -Wno-pointer-arith -Wredundant-decls -DIA64 -DXEN -DLINUX_2_6
> -ffixed-r13 -mfixed-range=f12-f15,f32-f127 -w -g -DNDEBUG -c
> setup.c -o setup.o
> In file included from setup.c:36:
> /home/Xen/xeno-unstable.bk/xen/include/asm-ia64/linux/efi.h:20
> :26: linux/ioport.h: No such file or directory
> setup.c:637: error: conflicting types for 'cpu_init'
> setup.c:396: error: previous implicit declaration of
> 'cpu_init' was here
> make[1]: *** [setup.o] Error 1
> make[1]: Leaving directory `/home/Xen/xeno-unstable.bk/xen/arch/ia64'
> make: *** [/home/Xen/xeno-unstable.bk/xen/xen] Error 2
>
>
>
> Shen Yuliang
> Best regards!
>
>
>
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
| <Prev in Thread] |
Current Thread |
[Next in Thread> |
- [Xen-ia64-devel] RE: Problems in building xen/ia64,
Magenheimer, Dan (HP Labs Fort Collins) <=
|
|
|
| |
|
Home