Hi Keir, I got build failure in both IA32 and IA32e platform. The changeset is #15961 The failure log is like: cp build-linux-2.6.18-xen_x86_64/arch/x86_64/boot/vmlinuz /home/nightly/builds_xen_unstable/xen-3.0-hg-xen_unstable-15961-20070926 /dist/install/boot/vmlinuz-2.6.18-xen cp: cannot stat `build-linux-2.6.18-xen_x86_64/arch/x86_64/boot/vmlinuz'': No such file or directory make[2]: *** [build] Error 1 make[2]: Leaving directory `/home/nightly/builds_xen_unstable/xen-3.0-hg-xen_unstable-15961-2007092 6'' make[1]: *** [linux-2.6-xen-install] Error 2 Best Regards, Yongkang You _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Wed, 2007-09-26 at 23:53 +0800, You, Yongkang wrote:> Hi Keir, > > I got build failure in both IA32 and IA32e platform. The changeset is > #15961 > The failure log is like: > > cp build-linux-2.6.18-xen_x86_64/arch/x86_64/boot/vmlinuz > /home/nightly/builds_xen_unstable/xen-3.0-hg-xen_unstable-15961-20070926 > /dist/install/boot/vmlinuz-2.6.18-xen > cp: cannot stat > `build-linux-2.6.18-xen_x86_64/arch/x86_64/boot/vmlinuz'': No such file > or directory > make[2]: *** [build] Error 1 > make[2]: Leaving directory > `/home/nightly/builds_xen_unstable/xen-3.0-hg-xen_unstable-15961-2007092 > 6'' > make[1]: *** [linux-2.6-xen-install] Error 2 >I think you need to update your linux-2.6.18-xen.hg subtree. This is not done automatically to avoid blowing away developer changes but you can add XEN_LINUX_UPDATE=y to your make command line, or just do the pull manually. The actual reason behind the failure is that xen-unstable.hg 15909:202153d094d8 and linux-2.6.18-xen.hg 211:c1f5d027adf7 are mutually dependant. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
You, Yongkang
2007-Sep-26 16:09 UTC
RE: [Xen-devel] Does latest xen-unstable build failed?
Hi Ian, Thanks for the reply. I do manually pull linux-2.6.18-xen.hg tree. But it is already the latest one for xen-unstable. http://xenbits.xensource.com/linux-2.6.18-xen.hg hg tip changeset: 208:d2bd9af846b5 tag: tip user: Christian Limpach <Christian.Limpach@xensource.com> date: Tue Sep 11 16:38:13 2007 +0100 summary: Add the CDROM_GET_CAPABILITY ioctl to blkfront. Maybe forget to pull from staging tree? Best Regards, Yongkang You>-----Original Message----- >From: Ian Campbell [mailto:Ian.Campbell@XenSource.com] >Sent: Thursday, September 27, 2007 12:02 AM >To: You, Yongkang >Cc: Keir Fraser; xen-devel >Subject: Re: [Xen-devel] Does latest xen-unstable build failed? > >On Wed, 2007-09-26 at 23:53 +0800, You, Yongkang wrote: >> Hi Keir, >> >> I got build failure in both IA32 and IA32e platform. The changeset is >> #15961 >> The failure log is like: >> >> cp build-linux-2.6.18-xen_x86_64/arch/x86_64/boot/vmlinuz >> >/home/nightly/builds_xen_unstable/xen-3.0-hg-xen_unstable-15961 >-20070926 >> /dist/install/boot/vmlinuz-2.6.18-xen >> cp: cannot stat >> `build-linux-2.6.18-xen_x86_64/arch/x86_64/boot/vmlinuz'': No >such file >> or directory >> make[2]: *** [build] Error 1 >> make[2]: Leaving directory >> >`/home/nightly/builds_xen_unstable/xen-3.0-hg-xen_unstable-1596 >1-2007092 >> 6'' >> make[1]: *** [linux-2.6-xen-install] Error 2 >> > >I think you need to update your linux-2.6.18-xen.hg subtree. >This is not >done automatically to avoid blowing away developer changes but you can >add XEN_LINUX_UPDATE=y to your make command line, or just do the pull >manually. > >The actual reason behind the failure is that xen-unstable.hg >15909:202153d094d8 and linux-2.6.18-xen.hg 211:c1f5d027adf7 >are mutually >dependant. > >Ian. >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Thu, 2007-09-27 at 00:09 +0800, You, Yongkang wrote:> Hi Ian, > > Thanks for the reply. > I do manually pull linux-2.6.18-xen.hg tree. But it is already the > latest one for xen-unstable. > http://xenbits.xensource.com/linux-2.6.18-xen.hg > > hg tip > changeset: 208:d2bd9af846b5 > tag: tip > user: Christian Limpach <Christian.Limpach@xensource.com> > date: Tue Sep 11 16:38:13 2007 +0100 > summary: Add the CDROM_GET_CAPABILITY ioctl to blkfront. > > Maybe forget to pull from staging tree?Yes, it looks like the xen-unstable staging tree has been flowing through but the linux-2.6.18-xen one hasn''t. I think the automated systems do this right so I suspect that someone manually pushed through xen-unstable and forgot the Linux tree. I''d pull from the Linux staging tree for now if I were you, regression tests should pass quite soon at which point both staging trees should sync out to the main ones. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel