From: Chengyuan Li <chengyuanli@gmail.com>
To: xen-devel@lists.sourceforge.net
Subject: xen compile failed on em64t machine
Date: Fri, 24 Dec 2004 10:10:20 +0800 [thread overview]
Message-ID: <d2ab7650041223181015bf76f5@mail.gmail.com> (raw)
Hi,
I checked out the latest unstable version of xen from bk repository
and tried to compile it on em64t machine. However I received the
following error message. I learn that the xen x86_64 is still in
testing stage, but my question is that can it boot both xen0 and xenU
on em64t ia32e mode?
make[3]: Entering directory `/root/lcy/xeno-unstable.bk/tools/libxutil'
gcc -Wl,-soname -Wl,libxutil.so.2.0 -shared -o libxutil.so.2.0.0
allocate.o enum.o file_stream.o gzip_stream.o hash_table.o iostream.o
lexis.o string_stream.o sxpr.o sxpr_parser.o sys_net.o sys_string.o
util.o
/usr/bin/ld: file_stream.o: relocation R_X86_64_32S against `a local
symbol' can not be used when making a shared object; recompile with
-fPIC
file_stream.o: could not read symbols: Bad value
collect2: ld returned 1 exit status
make[3]: *** [libxutil.so.2.0.0] Error 1
make[3]: Leaving directory `/root/lcy/xeno-unstable.bk/tools/libxutil'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/root/lcy/xeno-unstable.bk/tools/libxutil'
make[1]: *** [install] Error 2
make[1]: Leaving directory `/root/lcy/xeno-unstable.bk/tools'
make: *** [tools] Error 2
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next reply other threads:[~2004-12-24 2:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-24 2:10 Chengyuan Li [this message]
2004-12-24 8:47 ` xen compile failed on em64t machine Keir Fraser
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=d2ab7650041223181015bf76f5@mail.gmail.com \
--to=chengyuanli@gmail.com \
--cc=xen-devel@lists.sourceforge.net \
/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.