From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fabio Fantoni Subject: Re: Stable backport request for new OVMF version Date: Thu, 23 Jul 2015 17:04:14 +0200 Message-ID: <55B1026E.8000703@m2r.biz> References: <1437659800.19412.104.camel@citrix.com> <55B115D00200007800094AA8@prv-mh.provo.novell.com> <1437662602.24746.6.camel@citrix.com> <55B11B920200007800094B13@prv-mh.provo.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" 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 1ZII2d-0002FP-Jc for xen-devel@lists.xenproject.org; Thu, 23 Jul 2015 15:04:11 +0000 Received: by wibud3 with SMTP id ud3so223533951wib.0 for ; Thu, 23 Jul 2015 08:04:09 -0700 (PDT) In-Reply-To: <55B11B920200007800094B13@prv-mh.provo.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich , Ian Campbell Cc: Anthony Perard , Wei Liu , Ian Jackson , xen-devel List-Id: xen-devel@lists.xenproject.org Il 23/07/2015 16:51, Jan Beulich ha scritto: >>>> On 23.07.15 at 16:43, wrote: >> On Thu, 2015-07-23 at 08:26 -0600, Jan Beulich wrote: >>>>>> 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? >> It was present in 4.3. I don't think we build it by default since its >> toolchain is a bit picky, but we turn it on and test it in osstest from >> 4.4 onwards. >> >> You can ask for it with bios="ovmf" in your hvm guest's config. > Well, that means it can be used by the adventurous, but it doesn't > mean we consider it supported. > > Jan > > Even if used only by the adventurous left it unable to build with newer gcc don't seems very good, even if the adventurous should be able to change Config.mk to use update ovmf git that don't fail the build.