From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Alessandro Sardo <sandro.sardo-8RLafaVCWuNeoWH0uzbU5w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: KVM-21 on RHEL4: cannot build kernel module
Date: Sun, 29 Apr 2007 18:19:15 +0300 [thread overview]
Message-ID: <4634B773.7030800@qumranet.com> (raw)
In-Reply-To: <web-1190004-6YcMZAkROE/Yr5vRfC5HMw@public.gmane.org>
Alessandro Sardo wrote:
> Hello list,
>
> I am trying to compile KVM-21 on RHEL4 U4 (kernel version
> is 2.6.9-42.0.10.EL SMP). While I do not have any problem
> compiling the 'user' and 'qemu' targets, I cannot seem to
> be able to build the kernel module. I would like to point
> out that:
>
> 1) kernel-devel packages are installed
> 2) the same problem happens with KVM-13/15/16/17/18/19/20
> 2) the same problem happens with the 2.6.9-42.0.10.EL
> non-SMP kernel
>
>
There are several issues here:
- 2.6.9 appears to predate some Kbuild changes (like looking for the
Kbuild file in the external module directory, and instead going for
Makefile). Presumably this is easy to fix.
- RHEL 4's kernel is some mix of 2.6.9 and features from future kernels;
this may defeat our compatibility detection.
This is all fixable, but will require someone with time and determination.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-04-29 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-29 13:41 KVM-21 on RHEL4: cannot build kernel module Alessandro Sardo
[not found] ` <web-1190004-6YcMZAkROE/Yr5vRfC5HMw@public.gmane.org>
2007-04-29 15:19 ` Avi Kivity [this message]
[not found] ` <4634B773.7030800-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-04-29 15:22 ` David Brown
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=4634B773.7030800@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=sandro.sardo-8RLafaVCWuNeoWH0uzbU5w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox