From: Bill Davidsen <davidsen-sQDSfeB7uhw@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: public-kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f-8ByrlEUxsivZ+VzJOa5vwg@public.gmane.org
Subject: Re: compiler problem in Read Hat ES 4
Date: Tue, 23 Jan 2007 19:20:06 -0500 [thread overview]
Message-ID: <45B6A636.1030502@tmr.com> (raw)
In-Reply-To: <64F9B87B6B770947A9F8391472E0321603496B09-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
Uri Lublin wrote:
> Hi Frank,
>
> It seems it would be easier if you'd build kvm on a more recent linux
> kernel (version 2.6.16 or later).
It wouldn't be ES 4 then. The way the enterprise releases work is that
no software is upgraded, therefore you don't find new and exciting
changes in the way things work. Instead, any bug fixes or security
patches are backported to the original software.
> You could not make the kvm modules because 2.6.9 kernel does not use
> Kbuild, but expects that information to be in the Makefile.
> So... I typed "cd kernel; mv Makefile Makefile.orig; cat Kbuild
> Makefile.orig > Makefile; make".
> That started building the modules, but include file <linux/mutex.h> was
> not found.
> linux/mutex.h was introduced in version 2.6.16
>
> If you insist on 2.6.9, try to replace the mutex with a semaphore
> (kvm_main.c and kvm.h).
>
ES is intended to provide extremely stable platforms for production
servers, which normally doesn't make it a good candidate for building
new kernel modules.
I assume that's why ES is being used.
--
Bill Davidsen <davidsen-sQDSfeB7uhw@public.gmane.org>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-01-24 0:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-16 10:02 compiler problem in Read Hat ES 4 Francesc
2007-01-17 10:44 ` Uri Lublin
[not found] ` <64F9B87B6B770947A9F8391472E0321603496B05-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-01-17 12:31 ` Francesc
2007-01-17 12:44 ` Uri Lublin
[not found] ` <64F9B87B6B770947A9F8391472E0321603496B06-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-01-18 8:32 ` Francesc
2007-01-18 12:06 ` Uri Lublin
[not found] ` <64F9B87B6B770947A9F8391472E0321603496B09-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-01-24 0:20 ` Bill Davidsen [this message]
2007-01-24 13:41 ` Uri Lublin
2007-01-24 10:53 ` Francesc
[not found] ` <45B73AB5.1000000-VfcrZIqfQH54piUD7e9S/g@public.gmane.org>
2007-01-24 12:21 ` Michael Riepe
[not found] ` <45B74F3B.5080508-0QoEqw4nQxo@public.gmane.org>
2007-01-25 7:28 ` Francesc
[not found] ` <45B85C39.6040707-VfcrZIqfQH54piUD7e9S/g@public.gmane.org>
2007-01-25 7:44 ` Michael Riepe
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=45B6A636.1030502@tmr.com \
--to=davidsen-sqdsfeb7uhw@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=public-kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f-8ByrlEUxsivZ+VzJOa5vwg@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