WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: Kernel module compilation

To: "Kieran Mansley" <kmansley@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: Kernel module compilation
From: "David Pilger" <pilger.david@xxxxxxxxx>
Date: Thu, 5 Apr 2007 18:08:12 +0300
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 05 Apr 2007 08:07:00 -0700
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=MCNY0dw0qG++MsWHfrxLJPKaVdAUV+r7XWV/FmU/OxsmMyoWedo+et4VQ3EvYu+b0HS5sHnZlbxpIz+pFtCTb/T5s+LqLOkVNGMs2gETHeh1qquy5DzV41N0Vninwpo1WorT0/j/fzqn/HFAsz1MvzBfDvUmjpPXMkDOIrRjpeE=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=HJIII/Ew7NWPhijgsZ6ZNRu8oF5sSjbOJv7LcU5ESijleH3qjU4b+O42N06ncuhi32CFTkj+U/84JS38ABRC+sp6MuASwcpq5yO0ouKwtZhG6OqTbhtqeBUBQAcveWFCh8Wthhx4LVybfK0W8MNac28w/aFDlcnx+0hgAQHv8OA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1175765549.4124.6.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <280848580703290454o407cf95amdad3741d7bf358e@xxxxxxxxxxxxxx> <280848580704040911h4a803038j5dbad2c0d6ca1e09@xxxxxxxxxxxxxx> <1175703640.25237.354.camel@xxxxxxxxxxxxxxxxxxxxx> <280848580704041107m7bdf0a64r6f3d77923822bc23@xxxxxxxxxxxxxx> <1175710418.8760.4.camel@xxxxxxxxxxxxxxxxxxxxxx> <1175765549.4124.6.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 4/5/07, Kieran Mansley <kmansley@xxxxxxxxxxxxxx> wrote:
On Wed, 2007-04-04 at 19:13 +0100, Ian Campbell wrote:
> On Wed, 2007-04-04 at 21:07 +0300, David Pilger wrote:
> > Thanks for your help,
> > It didn't work...
> >
> > This is the error I got ->
> > ----
> > Makefile:107: *** output directory
> > "../../../build-linux-2.6.18-xen_x86_32/" does not exist.  Stop.
>
> I presume that path does exist.

It would only exist if you're building the unified kernel.  If you're
building separate domU and dom0 kernels you'll have slightly differently
named build directories.

To just rebuild a couple of modules that I've changed I do:

 cd /path/to/your/xen-unstable.hg
 make -C build-linux-<whatever>_x86_32 modules

where <whatever> should match the kernel you want to build for.

This doesn't result in the compiled modules being copied to
dist/install/lib/modules/ in the xen-unstable.hg as it would if I'd done
a normal "make dist", but copying them over is easy enough with a
script.

Kieran


Thanks everyone!
Kieran, I just added "M=driver/path/to/driver" and it worked!
The final line looks like this ->

make -C build-linux-2.6.18-xen_x86_32 modules M=drivers/char/mydriver
CONFIG_MYDRIVER=m


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>