qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PULL 00/12] EDK2 Firmware roms


From: Philippe Mathieu-Daudé
Subject: Re: [Qemu-devel] [PULL 00/12] EDK2 Firmware roms
Date: Mon, 18 Mar 2019 22:21:37 +0100

Hi Peter,

Le dim. 17 mars 2019 23:02, Peter Maydell <address@hidden> a
écrit :

> On Sun, 17 Mar 2019 at 20:29, Peter Maydell <address@hidden>
> wrote:
> >
> > On Sat, 16 Mar 2019 at 22:25, Philippe Mathieu-Daudé <address@hidden>
> wrote:
> > >
> > > The following changes since commit
> 8b088d3f8ab5642020d28fa0c2a8d938bc5f3592:
> > >
> > >   Merge remote-tracking branch
> 'remotes/pmaydell/tags/pull-target-arm-20190315' into staging (2019-03-15
> 11:39:42 +0000)
> > >
> > > are available in the Git repository at:
> > >
> > >   https://github.com/philmd/qemu.git tags/edk2_build-pull-request
> > >
> > > for you to fetch changes up to
> e487994c19ddca0e6340f72ddafc5b410877bbed:
> > >
> > >   MAINTAINERS: add the "EDK2 Firmware" subsystem (2019-03-16 16:09:29
> +0100)
> > >
> > > ----------------------------------------------------------------
> > >
> > > Advance the roms/edk2 submodule to the "edk2-stable201903" release,
> > > build and capture platform firmware binaries from that release.
> > >
> > > ----------------------------------------------------------------
> >
> > Hi; this fails to build on OSX and OpenBSD:
> >
> >   UNXZ    pc-bios/edk2-aarch64-code.fd.xz
> > /bin/sh: xz: command not found
>

I checked Travis builds for OSX. I suppose the Travis image has xz
pulled/pre-installed and yours doesn't.

I used to check on OpenBSD until realizing you are the only one doing that.
After having spent quite some time on it I removed it from my list, thus
missed this failure. EDK2 doesn't build on OpenBSD but still this OS should
be able to decompress the ROMs.
Thanks for carefully noticing that.
So this series won't make it to the next release.

>
> > (NetBSD barfed for a different reason -- the tests/vm setup
> > seems to occasionally simply fail the initial 600s timeout
> > for being able to ssh into the VM for reasons that I've
> > never been able to track down. So it might be OK or might
> > also not have xz.)
>
> NetBSD was OK on the second try.
>

Thanks for keeping trying there, even when 2 other OS failed.

Regards,

Phil.


> thanks
> -- PMM
>
>


reply via email to

[Prev in Thread] Current Thread [Next in Thread]