From: George Dunlap <dunlapg@umich.edu>
To: lei yang <yanglei.fage@gmail.com>
Cc: xen-devel@lists.xensource.com,
Xen Mailing List <xen-users@lists.xensource.com>
Subject: Re: Re: How to build a 64 bit xen
Date: Tue, 18 May 2010 10:13:22 -0500 [thread overview]
Message-ID: <AANLkTil9HtVDqn9bKWnSCuvTWUQuCBv3kdldAox3ZFRd@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinVB-d6Wdmo2fks3acxYBH95FsXRo7M7oOg6yvv@mail.gmail.com>
I've cross-compiled 64-bit xen exclusively since I've worked for
XenSource basically. Here's what I get:
$ file xen/xen
xen/xen: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
statically linked, stripped
$ file xen/xen-syms
xen/xen-syms: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
statically linked, not stripped
So I think 'file' is just making a mistake.
-George
On Tue, May 18, 2010 at 9:40 AM, lei yang <yanglei.fage@gmail.com> wrote:
> Is there some body to help see your "$file xen-4.0.0" if your xen is 64 bit
>
> Thanks
> Lei
>
> On Tue, May 18, 2010 at 9:11 PM, lei yang <yanglei.fage@gmail.com> wrote:
>>
>> Hi experts,'
>>
>> I build xen on my 64 bit redhat with "make xen", I got the image
>> xen-4.0.0.gz
>> then
>> $gunzip xen-4.0.0.gz
>> $file xen-4.0.0
>> it tells me it's 32 bit,but I saw it link the 64 bit lib
>>
>> Thanks
>> Lei
>> --
>> "We learn from failure, not from success!"
>
>
>
> --
> "We learn from failure, not from success!"
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
next prev parent reply other threads:[~2010-05-18 15:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 13:11 How to build a 64 bit xen lei yang
2010-05-18 14:40 ` lei yang
2010-05-18 15:13 ` George Dunlap [this message]
2010-05-18 15:20 ` Ian Campbell
2010-05-18 15:25 ` [Xen-devel] " Keir Fraser
2010-05-18 15:26 ` lei yang
2010-05-18 15:30 ` Tim Deegan
2010-06-01 16:07 ` Mike Viau
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=AANLkTil9HtVDqn9bKWnSCuvTWUQuCBv3kdldAox3ZFRd@mail.gmail.com \
--to=dunlapg@umich.edu \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
--cc=yanglei.fage@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).