From: David F Barrera <dfbp@us.ibm.com>
To: Pat Huntington <pat_huntington@yahoo.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: building xen for x86_64
Date: Mon, 17 Oct 2005 15:21:00 -0500 [thread overview]
Message-ID: <1129580460.6253.30.camel@dbarrera_tp> (raw)
In-Reply-To: <20051017200947.90651.qmail@web35914.mail.mud.yahoo.com>
On Mon, 2005-10-17 at 13:09 -0700, Pat Huntington wrote:
> Are there any special options I need to pass to make
> to get Xen to build correctly for x86_64 or will it
> automagically work? I ask because I'm getting 'DOM0
> image is not a Xen-compatible Elf image' on bootup
> which I guess means I'm probably doing something wrong
> in the compile. I'm using a 64 bit toolchain, build
> enviroment is FC4 using GCC version 4.0.1, binutils
> version 2.1 so I'm guessing it's not my tools. Xen is
> compiling but I get that Elf message on reboot. I
> figure it's because I'm not compiling for 64 bit
> correctly.
>
> Do I have to pass XEN_TARGET_ARCH=x86_64 or something
> like that?
It is automatic. I build it everyday on x86_64 by using 'make world', as
I do on x86.
>
> Sorry if this is documented somewhere, I tried in vain
> to find it but to no avail.
>
> Thanks!
>
>
>
>
> __________________________________
> Yahoo! Mail - PC Magazine Editors' Choice 2005
> http://mail.yahoo.com
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
next prev parent reply other threads:[~2005-10-17 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 20:09 building xen for x86_64 Pat Huntington
2005-10-17 20:21 ` David F Barrera [this message]
2005-10-17 20:41 ` Alexander Charbonnet
-- strict thread matches above, loose matches on Subject: below --
2005-10-17 20:16 Kamble, Nitin A
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=1129580460.6253.30.camel@dbarrera_tp \
--to=dfbp@us.ibm.com \
--cc=pat_huntington@yahoo.com \
--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.