From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: kvm-userspace fails to compile Date: Tue, 15 Jan 2008 19:44:09 +0200 Message-ID: <478CF0E9.2050905@qumranet.com> References: <1199711682.23380.7.camel@frecb07144> <1199712415.4234.2.camel@localhost.localdomain> <1199712901.23380.12.camel@frecb07144> <47822FBA.8090004@qumranet.com> <1199715950.23380.18.camel@frecb07144> <20080115154952.GA15974@infradead.org> <478CD768.7030003@qumranet.com> <20080115170549.GA19485@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel , Laurent Vivier To: Christoph Hellwig Return-path: In-Reply-To: <20080115170549.GA19485-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.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/