public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: walt <w41ter@gmail.com>
To: kvm@vger.kernel.org
Subject: Re: 'make' is no longer producing *.ko files?
Date: Tue, 30 Dec 2008 17:34:01 -0800	[thread overview]
Message-ID: <gjei69$ldk$1@ger.gmane.org> (raw)
In-Reply-To: <50ebac890812301715g4a13645cmd95dc076ef45be8f@mail.gmail.com>

Michael Park wrote:
> Hi there,
>
>> Just curious -- have you not been using the kvm modules included with
>> the linux kernel?  (I'm assuming you mean kvm.ko and friends?)
>
> I started out with Fedora's packaged kvm module, but at some point I
> went the upstream route (thinking back now, I don't remember the
> reason why I wanted the newer stuff).
>
> ...and yes, there are no *.ko files to be found, currently, despite
> 'make' exiting with 0.

This may be of no help to you whatever, but I use the 
--With-patched-kernel flag for configure or the compile of kvm-userspace 
fails with
errors caused by out-of-date headers in /usr/include/linux.

I track the git repository of kvm-userspace along with Linus's git
kernel repository, which is much more recent than the kernel that
Fedora is shipping, so my experience may be quite irrelevant to yours.
Just another data point for your reference.


  reply	other threads:[~2008-12-31  1:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-30 21:25 'make' is no longer producing *.ko files? Michael Park
2008-12-31  0:16 ` walt
2008-12-31  1:15   ` Michael Park
2008-12-31  1:34     ` walt [this message]
2008-12-31 10:15 ` Avi Kivity
     [not found]   ` <50ebac890901022112x5834970x4d46e77cef2e7e2c@mail.gmail.com>
2009-01-04 12: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='gjei69$ldk$1@ger.gmane.org' \
    --to=w41ter@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox