From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH] ipxe: fix compilation issues with some gcc versions Date: Sun, 18 Dec 2011 14:56:02 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Roger Pau =?ISO-8859-1?B?TW9ubuk=?= Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 18/12/2011 13:26, "Roger Pau Monn=E9" wrote: > 2011/12/16 Keir Fraser : >> Perhaps we should pick a recent commit hash to clone, then? There's plen= ty >> going on in there development-wise, which would surely have warranted a >> release or two; it just looks like they couldn't be arsed to tag release= s. >> Hanging on to a two-year-old version and building up a backport queue >> doesn't make sense. At the very least we should do this in xen-unstable,= and >> get some testing done of recent ipxe upstream. > = > That's fine, I agree that we should pick a most recent ipxe version > for unstable, if not things like this are going to happen every now > and then and we will end up with a massive queue of patches. But in > the meantime, is it possible to apply this patch to xen-4.1 and > possibly xen-4.0? Done for 4.1. In 4.0 it looks like we have the generated code checked in, so this fix is not necessary there. -- Keir > Thanks, Roger.