From: Avi Kivity <avi@qumranet.com>
To: Iain Paton <ilp@lkml.darkvoyage.org.uk>
Cc: kvm@vger.kernel.org
Subject: Re: [ANNOUNCE] kvm-74 release
Date: Mon, 01 Sep 2008 13:35:12 +0300 [thread overview]
Message-ID: <48BBC560.2090508@qumranet.com> (raw)
In-Reply-To: <48B73D35.4090402@lkml.darkvoyage.org.uk>
Iain Paton wrote:
> Hi,
>
> Given a kernel tree originally built using the O= method, what's the
> suggested
> way to build the external modules ?
>
If the kernel was built, installed, and is now running, ./configure;
make should suffice. I've never tested this though. Have you tried this?
>
> I don't have enough understanding of kernel makefile magic to see what
> I'm
> missing, so any help would be appreciated.
Me neither.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-09-01 10:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 10:02 [ANNOUNCE] kvm-74 release Avi Kivity
2008-08-29 0:05 ` Iain Paton
2008-09-01 10:35 ` Avi Kivity [this message]
2008-09-01 18:21 ` Iain Paton
2008-08-29 6:46 ` Charles Duffy
2008-09-01 10:36 ` Avi Kivity
2008-09-02 10:24 ` Henrik Holst
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=48BBC560.2090508@qumranet.com \
--to=avi@qumranet.com \
--cc=ilp@lkml.darkvoyage.org.uk \
--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