All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerone Young <jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Hollis Blanchard <hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: building kvm-userspace with separate kernel object	directory?
Date: Mon, 07 Jan 2008 15:44:35 -0600	[thread overview]
Message-ID: <1199742275.5855.1.camel@thinkpad> (raw)
In-Reply-To: <1199740378.5741.8.camel@basalt>

oh your problem is you must first build your kernel that you are
pointing too. Or you can cheat and point "include/asm" where you need to
point it. That solves the issue. It's all that userspace including
kernel headers :-)

On Mon, 2008-01-07 at 15:12 -0600, Hollis Blanchard wrote:
> I always build my kernels with the O= option, since it allows me to
> build multiple architectures from the same sources.
> 
> However, it looks like the kvm-userspace configure script can't handle
> this. It says --kerneldir should be the kernel *build* directory, but
> when I do that I get
>         libkvm.c:21:23: warning: linux/kvm.h: No such file or directory
> because the build directory does not contain an include/linux symlink.
> 
> When I specify the kernel *source* directory for --kerneldir, I get
>         /home/hollisb/source/kvmppc.hg/include/linux/kvm.h:12:21: warning: asm/kvm.h: No such file or directory
> because the source directory doesn't contain an include/asm symlink.
> 
> How can this work?
> 


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace

      parent reply	other threads:[~2008-01-07 21:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-07 21:12 building kvm-userspace with separate kernel object directory? Hollis Blanchard
2008-01-07 21:29 ` Hollis Blanchard
2008-01-07 21:50   ` Jerone Young
2008-01-07 22:07     ` Hollis Blanchard
2008-01-07 22:52       ` Jerone Young
2008-01-08 13:50   ` Avi Kivity
2008-01-07 21:44 ` Jerone Young [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=1199742275.5855.1.camel@thinkpad \
    --to=jyoung5-r/jw6+rmf7hqt0dzr+alfa@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 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.