From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Cc: kvm-devel
<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
Laurent Vivier <Laurent.Vivier-6ktuUTfB/bM@public.gmane.org>
Subject: Re: kvm-userspace fails to compile
Date: Tue, 15 Jan 2008 19:44:09 +0200 [thread overview]
Message-ID: <478CF0E9.2050905@qumranet.com> (raw)
In-Reply-To: <20080115170549.GA19485-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Christoph Hellwig wrote:
> On Tue, Jan 15, 2008 at 05:55:20PM +0200, Avi Kivity wrote:
>
>> That's the plan, but since things work for most people that area is not
>> seeing much attention. The problem areas are compiling userspace against
>> older kernels, and that's not something we do often.
>>
>
> Well, the point is there should be no compiling against older kernels or
> kernels in general. A userspace tarball should be entirely
> self-contained and not care about any kind of kerneldir or similar.
>
>
Yes, you're right. My confusion arose because we have two distinct
needs for a "kernel directory":
1. A build directory for the external module (which really needs to be a
kernel directory)
2. A directory with the exported userspace headers (like /usr/include)
We are using one directory for both. Once we separate this, the mess
should be cleared up.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-01-15 17:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 13:14 kvm-userspace fails to compile Laurent Vivier
2008-01-07 13:26 ` Dor Laor
[not found] ` <1199712415.4234.2.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-01-07 13:35 ` Laurent Vivier
2008-01-07 13:57 ` Avi Kivity
[not found] ` <47822FBA.8090004-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-07 14:25 ` Laurent Vivier
2008-01-15 15:49 ` Christoph Hellwig
[not found] ` <20080115154952.GA15974-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2008-01-15 15:55 ` Avi Kivity
[not found] ` <478CD768.7030003-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-15 17:05 ` Christoph Hellwig
[not found] ` <20080115170549.GA19485-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2008-01-15 17:44 ` Avi Kivity [this message]
[not found] ` <478CF0E9.2050905-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-15 17:49 ` Christoph Hellwig
2008-01-15 16:03 ` Laurent Vivier
-- strict thread matches above, loose matches on Subject: below --
2008-01-07 13:14 Laurent Vivier
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=478CF0E9.2050905@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=Laurent.Vivier-6ktuUTfB/bM@public.gmane.org \
--cc=hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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