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

[Xen-devel] Building and Configuring with a Patch


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Luke <secureboot@xxxxxxxxx>
  • Date: Sat, 27 Jan 2007 23:16:30 -0500
  • Delivery-date: Sat, 27 Jan 2007 20:16:07 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=INZcEjlMJz3KXKfgbAVYPzGjdcBqdpB9WxDmBgIlQkQJqJMtGlsa8/dFfB7/8CSahnH3Zrf46rxQ05aU22tTfJLyfZ1bz307okCfMtmcfvgJuT3j/alkmrtn5M33mXyvvjlICf0SNxDziHnZFlQvL3lWGpRIynQ4D+Lv9eCgVIs=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

I'm trying to build Xen with an external patch applied.  I've put this patch in patches/linux-2.6.18/, and added its name to the series file.

However, when I run the make linux-2.6-xen-config CONFIGMODE=menuconfig (not at my Xen terminal now, but whatever commands are in the bottom of README in xen-unstable), I go through the menuconfig, and everything seems fine.  However, when I run the make linux-2.6-xen-build, and config file that gets put into dist/ isn't the what I menuconfiged - it seems to be the .config before the menuconfig.  The kernel that gets installed, in the next step, obviously is missing the menuconfig changes as well.

So my question - how am I supposed to patch and config a custom Xen kernel?  Are the steps in the bottom of the README actually correct?

Also - I used to just cd to linux-2.6.18, and make menuconfig from there, and do the normal Xen installation.  Why doesn't that work now?

What is the recommended way to patch AND config the xen-unstable branch nowadays?  I haven't built a custom Xen kernel in 2-3 months now, and it seems things have changed...
_______________________________________________
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®.