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

[Xen-users] Xen 3.1.0 build question.

  • To: "Xen users mailing list" <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: TMC <tmciolek@xxxxxxxxx>
  • Date: Tue, 11 Dec 2007 23:58:27 +1100
  • Delivery-date: Tue, 11 Dec 2007 04:58:55 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=Hb4AluZCYW4OC9srfAjls0C8qsq3G6POo2ZyBq12XAzT8XJhqotr8pFtUeX52yEPaHpD7sRX4FrLPw+AGdHcAZSmhou00LqDZ5vi0L/SRKKdRtTFeshTuguB34SG+RqNxgkwO9tEK6Yrgk+k/uLsJMjBzCVm44aY3G2M0M0FwLE=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Under xen 3.0.x I used to do:

make linux-2.6-xen0-config CONFIGMODE=menuconfig
make linux-2.6-xenU-config CONFIGMODE=menuconfig
make all KERNELS="linux-2.6-xen0 linux-2.6-xenU"

and that would build xen + Linux dom0 and somU kernels

with a new, clean xen 3.1.0 tree this appears to break and the make
attempts to build linux-2.6-xen instead of separate xen0 and xenU

has the behaviour of the build system changed?
Is the new process documented somewhere?


GPG key fingerprint: 3883 B308 8256 2246 D3ED  A1FF 3A1D 0EAD 41C4 C2F0
GPG public key availabe on pgp.mit .edu keyserver

Xen-users mailing list



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