This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Problems compiling Xen for ia64

To: <ricardost@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Problems compiling Xen for ia64
From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
Date: Tue, 19 Apr 2005 15:18:46 -0700
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 19 Apr 2005 22:19:16 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcVFLcEpQ6+D2h7/QgWYyt/nJLTwJA==
Thread-topic: Re: [Xen-devel] Problems compiling Xen for ia64
Hi Ricardo --

I'm not sure from your message, but I suspect that you
are using a very old distribution of Xen/ia64, perhaps
the one from the HP Labs ftp site?  The current
README.xenia64 does not refer to install.sh.

Xen/ia64 is now available as part of the standard Xen
"unstable" distribution, at xen.bkbits.net/xeno-unstable.bk.
If you obtain this on an ia64 box, change to
the xeno-unstable.bk directory, then cd to the xen
subdirectory.  Then read arch/ia64/tools/README.xenia64.

Note that the unstable tree is, well, unstable.  Because
development continues on the x86 and x86-64 branches,
sometimes the unstable tree is inconsistent with the
latest arch/ia64 files and will not compile.  (That is
the case right now until the Cambridge Xen team pulls
the latest from the xen-ia64.bkbits.net tree.)

In particular Xen/ia64 has a dependency on a copy of
Linux (as described in README.xenia64) and this has just
been rebased to 2.6.11.  You might want to wait a day or
two until this all works through the bk system.

Also, I should point you to the new xen-ia64 distribution
list.  See http://lists.xensource.com/xen-ia64 to sign up

Dan Magenheimer
HP Labs Fort Collins


Date: Tue, 19 Apr 2005 15:04:55 -0800
From: Ricardo Staudt <ricardost@xxxxxxxxxxxxx>
Subject: [Xen-devel] Problems compiling Xen for ia64
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Message-ID: <42658E97.40506@xxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hello everyone,

I'm having trouble compiling Xen for ia64, I'm using Red Hat AS update 3

with the build-in kernel (2.4 series) on a Itanium RX 5670.

Following the steps specified int the "README.xenia64" file, when I try 
to run "sh install.sh" I get this message:

"ERROR: Could not find a valid distribution directory.
      If this is a source-only release, try 'make dist'."

if I run "made dist" it starts the compilation process but I get the 
error below:
__  __            ____    ___ 
 \ \/ /___ _ __   |___ \  / _ \
  \  // _ \ '_ \    __) || | | |
  /  \  __/ | | |  / __/ | |_| |
 /_/\_\___|_| |_| |_____(_)___/
make[2]: Leaving directory `/root/pacotaopronto/xen-2.0/xen'
make -C common
make[2]: Entering directory `/root/pacotaopronto/xen-2.0/xen/common'
gcc -nostdinc -fno-builtin -fno-common -fno-strict-aliasing -iwithprefix

include -Wall -Werror -pipe -I/root/pacotaopronto/xen-2.0/xen/include 
-Wno-pointer-arith -Wredundant-decls -O3 -fomit-frame-pointer 
-msoft-float -DNDEBUG -c kernel.c -o kernel.o
cc1: invalid option `soft-float'
make[2]: *** [kernel.o] Error 1
make[2]: Leaving directory `/root/pacotaopronto/xen-2.0/xen/common'
make[1]: *** [/root/pacotaopronto/xen-2.0/xen/xen] Error 2
make[1]: Leaving directory `/root/pacotaopronto/xen-2.0/xen'
make: *** [xen] Error 2

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>