All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb@us.ibm.com>
To: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
Cc: kvm <kvm@vger.kernel.org>, Avi Kivity <avi@redhat.com>
Subject: Re: kvm-userspace requires kvm capable kernel headers in default search path of the compiler
Date: Thu, 11 Dec 2008 18:35:28 -0600	[thread overview]
Message-ID: <1229042128.26586.61.camel@localhost.localdomain> (raw)
In-Reply-To: <493FBB32.8000507@linux.vnet.ibm.com>

On Wed, 2008-12-10 at 13:50 +0100, Christian Ehrhardt wrote:
> Hi everyone,
> while running a test when updating kvm-userspace for powerpc I found 
> that the current kvm userspace requires kvm kernel headers in the 
> default search path of the used compilers.

You lost me with this mail, but after hitting the problem myself, I
think I can summarize:

% ./configure
KVM support       no
% cd kernel; make sync LINUX=/home/hollisb/source/kvm.git; cd ..
% ./configure
KVM support       yes

This is building x86 kvm-userspace.git on an x86 host; no
cross-compiling or PowerPC involved.

This seems wrong to me, and also contradicts the "building an external
module with older kernels" directions at
http://kvm.qumranet.com/kvmwiki/Code .

Avi, did something in the build procedure break recently?

-- 
Hollis Blanchard
IBM Linux Technology Center


  reply	other threads:[~2008-12-12  0:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-10 12:50 kvm-userspace requires kvm capable kernel headers in default search Christian Ehrhardt
2008-12-10 12:50 ` kvm-userspace requires kvm capable kernel headers in default search path of the compiler Christian Ehrhardt
2008-12-12  0:35 ` Hollis Blanchard [this message]
2008-12-14  7:57   ` 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=1229042128.26586.61.camel@localhost.localdomain \
    --to=hollisb@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=ehrhardt@linux.vnet.ibm.com \
    --cc=kvm@vger.kernel.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 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.