[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: "Ian Campbell" <Ian.Campbell@xxxxxxxxxxxxx>
  • From: "David Pilger" <pilger.david@xxxxxxxxx>
  • Date: Thu, 5 Apr 2007 10:25:11 +0300
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 05 Apr 2007 00:23:56 -0700
  • 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=cw+DGiWQHuL4AYHWyrCMzp5uuJX44vyR8L5DxEUPFq+2t1qgKF9nz+csRPWqdU1hG+e//KJvl327Fbh8YAOeps6+P5TNmOuVBTJzA5bL62WvTT2/qSEVpCNTARTUzLO4EDao85xMrwAsNpPpwEW+k2fEzUnfvpggmKyTh3eijAw=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On 4/4/07, Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx> wrote:

I presume that path does exist. It's possible that it needs to be
relative to the kernel source directory rather than the module source
directory. It would be worth trying an absolute path rather than a
relative one.

The only other thing I can suggest is to have a read through
Documentation/kbuild/* (esp. modules.txt) in the kernel source and see
if it has any hints.


Thanks again,
I guess it's something with the Xen Makefile, in the way that Xen
builds the kernels. autoconf.h is present but in the build-...x86
directory.


Ian.



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.