From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: Stable backport request for new OVMF version Date: Thu, 23 Jul 2015 08:26:56 -0600 Message-ID: <55B115D00200007800094AA8@prv-mh.provo.novell.com> References: <1437659800.19412.104.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1ZIHSf-0005Zd-AX for xen-devel@lists.xenproject.org; Thu, 23 Jul 2015 14:27:01 +0000 In-Reply-To: <1437659800.19412.104.camel@citrix.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: Anthony Perard , Ian Jackson , Wei Liu , xen-devel List-Id: xen-devel@lists.xenproject.org >>> On 23.07.15 at 15:56, wrote: > The version of OVMF in 4.5 (and presumably earlier) doesn't build with > the gcc in modern Linux distros (I noticed it with 4.9 from > Debian/Jessie). > > I think we should update Config.mk:OVMF_UPSTREAM_REVISION to > cb9a7ebabcd6b8a49dc0854b2f9592d732b5afbd in all stable branches. That > version is the one currently in master. To be honest I didn't even know we support use of OVMF in any released version (nor in unstable). When did this change? Jan > One aspect of the specific failure I've tripped over (Debian Jessie) is > that it will be a blocker for updating osstest to using the new version > of Debian on the test hosts, which in turn is a prerequisite for arm64 > support. > > Ian.