From: Cam Macdonell <cam-edFDblaTWIyXbbII50Afww@public.gmane.org>
To: Hollis Blanchard <hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org
Subject: Re: [PATCH] [RESEND] Move libkvm (v2)
Date: Wed, 31 Oct 2007 11:10:05 -0600 [thread overview]
Message-ID: <4728B6ED.8080502@cs.ualberta.ca> (raw)
In-Reply-To: <1193849820.31610.17.camel@basalt>
Hollis Blanchard wrote:
> I think the KERNELDIR change is a red herring: you probably ran
> configure with different arguments.
Hi Hollis,
The only one I run with is --prefix. It seems Avi latest patches fix
the problem (although I'm not sure how):
With Avi's latest changes, this now the compile line for libkvm.o.
gcc -MMD -MF ./.libkvm.d -g -fomit-frame-pointer -Wall
-fno-stack-protector -I
/compsci/brule7/cshome/cam/research/KVM/kvm-userspace/kernel/include
-c -o libkvm.o libkvm.c
Thanks for your reply,
Cam
> I notice that the kvm-49 build line below is missing -m64. Try this:
>
> diff --git a/libkvm/config-x86_64.mak b/libkvm/config-x86_64.mak
> --- a/libkvm/config-x86_64.mak
> +++ b/libkvm/config-x86_64.mak
> @@ -1,2 +1,5 @@
>
> LIBDIR := /lib64
> +
> +CFLAGS += -m64
> +CFLAGS += -D__x86_64__
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-10-31 17:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 4:43 [PATCH] [RESEND] Move libkvm (v2) Hollis Blanchard
2007-10-30 11:19 ` Avi Kivity
2007-10-31 16:09 ` Cam Macdonell
[not found] ` <4728A8C0.6030807-edFDblaTWIyXbbII50Afww@public.gmane.org>
2007-10-31 16:56 ` Hollis Blanchard
2007-10-31 17:10 ` Cam Macdonell [this message]
2007-10-31 22:13 ` Avi Kivity
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=4728B6ED.8080502@cs.ualberta.ca \
--to=cam-edfdblatwiyxbbii50afww@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/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