public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Cam Macdonell <cam-edFDblaTWIyXbbII50Afww@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	Hollis Blanchard
	<hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] [RESEND] Move libkvm (v2)
Date: Thu, 01 Nov 2007 00:13:13 +0200	[thread overview]
Message-ID: <4728FDF9.8060907@qumranet.com> (raw)
In-Reply-To: <4728A8C0.6030807-edFDblaTWIyXbbII50Afww@public.gmane.org>

Cam Macdonell wrote:
>
> Hi Hollis and Avi,
>
> I run into a compile problem with libkvm when compiling kvm-49.   It 
> caused the compile problem mentioned in my email yesterday.
>
> It has to with the line in libkvm/Makefile
>
> CFLAGS += -I $(KERNELDIR)/include
>
> when compiling kvm-49 (git or snapshot), this include points to my 
> resident kernel's version of kvm.h instead of the local one copied 
> with "make sync LINUX=<kvm git repo>").
>
> in kvm-48, KERNELDIR points to the kvm-userspace/kernel/ directory 
> (under the git repo), but in the more recent versions it changes to 
> /lib/modules/2.6.22.9-61.fc6/build/include.
>
> Here are the compiles from kvm-48 (kvmctl.c) and 49 (libkvm.c) 
> respectively,
>
> kvm-48:
> gcc  -m64 -I /home/cam/research/KVM/Sakwatamau/kvm-48/kernel/include 
> -MMD -MF ./.kvmctl.d -g -fomit-frame-pointer -Wall  
> -fno-stack-protector     -c -o kvmctl.o kvmctl.c
>
> kvm-49:
> cc -MMD -MF ./.libkvm.d -g -fomit-frame-pointer -Wall 
> -fno-stack-protector   -I /lib/modules/2.6.22.9-61.fc6/build/include 
> -c -o libkvm.o libkvm.c
>
> what is KERNELDIR supposed to point to - the install location for the 
> modules or the location of kernel source?
>

I committed a patch from Uri that fixes this.

-- 
Any sufficiently difficult bug is indistinguishable from a feature.


-------------------------------------------------------------------------
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/

      parent reply	other threads:[~2007-10-31 22:13 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
2007-10-31 22:13     ` Avi Kivity [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=4728FDF9.8060907@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=cam-edFDblaTWIyXbbII50Afww@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