From: Iain Paton <ilp@lkml.darkvoyage.org.uk>
To: kvm@vger.kernel.org
Subject: Re: [ANNOUNCE] kvm-74 release
Date: Fri, 29 Aug 2008 01:05:09 +0100 [thread overview]
Message-ID: <48B73D35.4090402@lkml.darkvoyage.org.uk> (raw)
In-Reply-To: <48B677A6.5000307@qumranet.com>
Hi,
Given a kernel tree originally built using the O= method, what's the suggested
way to build the external modules ?
I've tried giving configure a --kerneldir of both the original tree and the
O= tree, along with passing the O= option to make and/or configure. So far
without success.
qemu parts all seem to build fine, errors start with:
make -C /home/ilp/kernels/v2.6/linux-2.6.26-org M=`pwd` \
LINUXINCLUDE="-I`pwd`/include -Iinclude -Iarch/x86/include -I`pwd`/include-compat \
-include include/linux/autoconf.h \
-include `pwd`/x86/external-module-compat.h"
make[2]: Entering directory `/home/ilp/kernels/v2.6/linux-2.6.26-org'
LD /home/ilp/kvm/kvm-74/kernel/x86/built-in.o
CC [M] /home/ilp/kvm/kvm-74/kernel/x86/svm.o
In file included from <command-line>:0:
/home/ilp/kvm/kvm-74/kernel/x86/external-module-compat.h:6:28: error: linux/compiler.h: No such file or directory
In file included from /home/ilp/kvm/kvm-74/kernel/x86/external-module-compat.h:9,
from <command-line>:0:
/home/ilp/kvm/kvm-74/kernel/x86/../external-module-compat-comm.h:12:26: error: linux/string.h: No such file or directory
quickly followed by several screenfuls of stuff due to not being able to
find some of the kernel include files.
I don't have enough understanding of kernel makefile magic to see what I'm
missing, so any help would be appreciated.
Thanks,
Iain
next prev parent reply other threads:[~2008-08-29 0:11 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 [this message]
2008-09-01 10:35 ` Avi Kivity
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=48B73D35.4090402@lkml.darkvoyage.org.uk \
--to=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