From: Rick Gonzalez <rcgneo@us.ibm.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Xen Developers <xen-devel@lists.xensource.com>
Subject: Re: Latest Xen src 64bit: cannot compile
Date: Thu, 04 May 2006 23:59:22 -0500 [thread overview]
Message-ID: <445ADBAA.4080604@us.ibm.com> (raw)
In-Reply-To: <6df21879b8e34eb635446da4f713ab22@cl.cam.ac.uk>
Keir Fraser wrote:
>
> On 4 May 2006, at 20:19, Rick Gonzalez wrote:
>
>> 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.
>
> Does your xen/arch/x86/hvm/Makefile contain a reference to instrlen.o?
> That would be a problem, and no such reference is present in the main
> repositories (instrlen.c lives in xen/arch/x86/hvm/svm, and it's that
> directory's Makefile that references it).
>
> Maybe you need to clone a fresh repository.
Keir,
Thanks for the info and advise. :) I just got a fresh repository
and it is working now. I'm not sure how it actually got bad.
Anyway thanks,
>
> -- Keir
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
prev parent reply other threads:[~2006-05-05 4:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 19:19 Latest Xen src 64bit: cannot compile Rick Gonzalez
2006-05-04 21:59 ` Keir Fraser
2006-05-05 4:59 ` Rick Gonzalez [this message]
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=445ADBAA.4080604@us.ibm.com \
--to=rcgneo@us.ibm.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--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.