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

Re: [Xen-devel] Re: Attempt to backport changeset-23088, changeset-23089 to Xen 4.1.1


  • To: Keir Fraser <keir.xen@xxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
  • From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
  • Date: Thu, 28 Jul 2011 14:50:29 -0700 (PDT)
  • Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
  • Delivery-date: Thu, 28 Jul 2011 14:51:23 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=TQCqpFCm5lABLFz3K9Vl3+NgRUCcw83uKJt6WCPGFq+Ess9Z4nWfru6dYGzy4wLd6ExZG4FoZiYn0H45Rg6FHTDJr//F6FeF0DBiZSg//iLTGW6SyUD4X6AgyBQwEnCZeOcbANiM8SEWCJ2bw4q6gToaXTT8ZCLDVGlrGxY+7vc=;
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

>Is that 23089:8ec7808f9c23 and 23088:49728fe8dd6a? There is zero chance of
>  either of those being the cause of a build failure under tools/firmware

It was  23089:0300d7f10d42  and  23088:37ba0319e2cf  from http://xenbits.xen.org/hg/staging/xen-4.1-testing.hg/.   Build was on Ubuntu 11.10 .  There was notice
of Ian Campbell regarding Ubuntu's  patching ipxe  on xen-4.1.0/debian/patches .   He wrote that it was worth to look into that. I will try to find his message.

Boris.


--- On Thu, 7/28/11, Keir Fraser <keir.xen@xxxxxxxxx> wrote:

From: Keir Fraser <keir.xen@xxxxxxxxx>
Subject: Re: [Xen-devel] Re: Attempt to backport changeset-23088, changeset-23089 to Xen 4.1.1
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
Cc: "Ian Campbell" <Ian.Campbell@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Konrad Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx>
Date: Thursday, July 28, 2011, 3:53 PM

On 28/07/2011 20:41, "Boris Derzhavets" <bderzhavets@xxxxxxxxx> wrote:

> Only 3 CSs backported :-
> changeset 23104  - No problems . HVM fix
> Next step =>  23088 and 23089 .  This step causes build failure.

Is that 23089:8ec7808f9c23 and 23088:49728fe8dd6a? There is zero chance of
either of those being the cause of a build failure under tools/firmware.

-- Keir

> Boris.
>
> --- On Thu, 7/28/11, Keir Fraser <keir.xen@xxxxxxxxx> wrote:
>>
>> From: Keir Fraser <keir.xen@xxxxxxxxx>
>> Subject: [Xen-devel] Re: Attempt to backport changeset-23088, changeset-23089
>> to Xen 4.1.1
>> To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
>> Cc: "Ian Campbell" <Ian.Campbell@xxxxxxxxxxxxx>,
>> "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Konrad
>> Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx>
>> Date: Thursday, July 28, 2011, 3:04 PM
>>
>> On 28/07/2011 18:58, "Boris Derzhavets" <bderzhavets@xxxxxxxxx
>> </mc/compose?to=bderzhavets@xxxxxxxxx> > wrote:
>>
>>> Build  error :-
>>
>> The stated changesets don't touch tools/firmware. They're unlikely to be
>> causing your build failure.
>>
>>  -- Keir
>>
>>> Calculated checksum:  0x44  Setting checksum.
>>> ls -l VGABIOS-lgpl-latest.cirrus.debug.bin
>>> -rw-rw-r-- 1 buildd buildd 35840 Jul 28 17:27
>>> VGABIOS-lgpl-latest.cirrus.debug.bin
>>> make[8]: Leaving directory
>>>
>> `/build/buildd/xen-4.1.1/debian/build/build-utils_amd64/tools/firmware/vgabio
>> s>
>> '
>>> make[7]: Leaving directory
>>> `/build/buildd/xen-4.1.1/debian/build/build-utils_amd64/tools/firmware'
>>> make[7]: Entering directory
>>> `/build/buildd/xen-4.1.1/debian/build/build-utils_amd64/tools/firmware'
>>> /usr/bin/make -C etherboot all
>>> make[8]: Entering directory
>>> `/build/buildd/xen-4.1.1/debian/build/build-utils_amd64/tools/firmware/ether
>>> bo
>>> ot'
>>> make[8]: *** No rule to make target `/usr/lib/ipxe/rtl8139.rom', needed by
>>> `eb-roms.h'.  Stop.
>>> make[8]: Leaving directory
>>> `/build/buildd/xen-4.1.1/debian/build/build-utils_amd64/tools/firmware/ether
>>> bo
>>> ot'
>>> make[7]: *** [subdir-all-etherboot] Error 2
>>> make[7]: Leaving directory
>>> `/build/buildd/xen-4.1.1/debian/build/build-utils_amd64/tools/firmware'
>>> make[6]: *** [subdirs-all] Error 2
>>> make[6]: Leaving directory
>>> `/build/buildd/xen-4.1.1/debian/build/build-utils_amd64/tools/firmware'
>>> make[5]: *** [all] Error 2
>>> make[5]: Leaving directory
>>> `/build/buildd/xen-4.1.1/debian/build/build-utils_amd64/tools/firmware'
>>> make[4]: *** [subdir-all-firmware] Error 2
>>> make[4]: Leaving directory
>>> `/build/buildd/xen-4.1.1/debian/build/build-utils_amd64/tools'
>>> make[3]: *** [subdirs-all] Error 2
>>> make[3]: Leaving directory
>>> `/build/buildd/xen-4.1.1/debian/build/build-utils_amd64/tools'
>>> make[2]: *** [debian/stamps/build-utils_amd64] Error 2
>>> make[2]: Leaving directory `/build/buildd/xen-4.1.1'
>>> make[1]: *** [build_amd64_real] Error 2
>>> make[1]: Leaving directory `/build/buildd/xen-4.1.1'
>>> make: *** [debian/stamps/build-base] Error 2
>>> dpkg-buildpackage: error: debian/rules build gave error exit status 2
>>>
>>> Boris.
>>>
>>>
>>
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx </mc/compose?to=Xen-devel@xxxxxxxxxxxxxxxxxxx>
>> http://lists.xensource.com/xen-devel
>



_______________________________________________
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

 


Rackspace

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