Re: [Xen-devel] [lersek@xxxxxxxxxx: Re: [PATCH v3] OvmfPkg/build.sh: Make GCC5 the default toolchain, catch GCC43 and earlier]

[Wei Liu <wei.liu2@xxxxxxxxxx>]

On Fri, Nov 25, 2016 at 12:04:05PM -0500, Konrad Rzeszutek Wilk wrote:
> On Fri, Nov 25, 2016 at 01:51:56PM +0000, Wei Liu wrote:
> > On Fri, Nov 25, 2016 at 08:24:00AM -0500, Konrad Rzeszutek Wilk wrote:
> > > Hey Wei, Anthony,
> > > 
> > > Are you guys OK pushing this commit: 2667ad40919a in the
> > > git://xenbits.xen.org/ovmf.git     
> > > 
> > > tree? Without this I cannot build Xen 4.8 with TianoCore
> > > (--enable-ovmf).
> > > 
> > 
> > We normally don't deviate from upstream. We would need to wait for this
> > to pass osstest pushgate, and then update Config.mk.
> 
> I see. We seem to be 791 commits behind upstream? Oh, and 770
> to catch up with 2667ad40919a. Yikes.
> 

I see that commit has passed our pushgate. I will see what I can do.

In any case, because OVMF is still experimental and disabled by default,
we used to update the commit id in stable branches as well. So they will
get the latest commit at the end.

Or you can provide a custom tree when building Xen. There isn't really
anything that would tie OVMF to a specific version of Xen -- at least
not for now.

What is even better is that you can provide a OVMF binary direct via
toolstack in this release.

Wei.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel