From: Rick Gonzalez <rcgneo@us.ibm.com>
To: Xen Developers <xen-devel@lists.xensource.com>
Subject: Latest Xen src 64bit: cannot compile
Date: Thu, 04 May 2006 14:19:16 -0500 [thread overview]
Message-ID: <445A53B4.3070702@us.ibm.com> (raw)
Anybody having problems compiling latest changeset?
This is what I'm seeing:
-o intercept.o
gcc -O2 -fomit-frame-pointer -DNDEBUG -m64 -Wall -Wstrict-prototypes
-nostdinc -fno-builtin -fno-common -fno-strict-aliasing -iwithprefix
include -Werror -Wno-pointer-arith -pipe
-I/usr/xen/xen-unstable.hg/xen/include
-I/usr/xen/xen-unstable.hg/xen/include/asm-x86/mach-generic
-I/usr/xen/xen-unstable.hg/xen/include/asm-x86/mach-default -msoft-float
-mno-red-zone -fpic -fno-reorder-blocks -fno-asynchronous-unwind-tables
-g -D__XEN__ -c io.c -o io.o
make[6]: *** No rule to make target `instrlen.o', needed by
`built_in.o'. Stop.
make[6]: Leaving directory `/usr/xen/xen-unstable.hg/xen/arch/x86/hvm'
make[5]: *** [hvm/built_in.o] Error 2
make[5]: Leaving directory `/usr/xen/xen-unstable.hg/xen/arch/x86'
make[4]: *** [/usr/xen/xen-unstable.hg/xen/arch/x86/built_in.o] Error 2
make[4]: Leaving directory `/usr/xen/xen-unstable.hg/xen/arch/x86'
make[3]: *** [/usr/xen/xen-unstable.hg/xen/xen] Error 2
make[3]: Leaving directory `/usr/xen/xen-unstable.hg/xen'
make[2]: *** [install] Error 2
make[2]: Leaving directory `/usr/xen/xen-unstable.hg/xen'
make[1]: *** [install-xen] Error 2
make[1]: Leaving directory `/usr/xen/xen-unstable.hg'
make: *** [world] Error 2
regards,
------------------------
Rick Gonzalez
Linux Technology Center
IBM Corporation
Phone#: 512-838-0623
next reply other threads:[~2006-05-04 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 19:19 Rick Gonzalez [this message]
2006-05-04 21:59 ` Latest Xen src 64bit: cannot compile Keir Fraser
2006-05-05 4:59 ` Rick Gonzalez
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=445A53B4.3070702@us.ibm.com \
--to=rcgneo@us.ibm.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.