From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Fam Zheng <fam@euphon.net>
Cc: "Fam Zheng" <famz@redhat.com>,
"Samuel Thibault" <samuel.thibault@ens-lyon.org>,
"Brad Smith" <brad@comstyle.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4] tests: vm: auto_install OpenBSD
Date: Mon, 14 Jan 2019 10:15:15 +0000 [thread overview]
Message-ID: <20190114101515.GA3686@redhat.com> (raw)
In-Reply-To: <A3EA5405-A5EE-4E77-8C77-A67398756B96@euphon.net>
On Mon, Jan 14, 2019 at 11:50:08AM +0800, Fam Zheng wrote:
>
>
> > On Jan 9, 2019, at 21:59, Daniel P. Berrangé <berrange@redhat.com> wrote:
> >
> > On Wed, Jan 09, 2019 at 01:55:04PM +0000, Daniel P. Berrangé wrote:
> >> On Wed, Nov 14, 2018 at 05:58:07PM +0800, Fam Zheng wrote:
> >>> On Sun, 11/11 18:20, Brad Smith wrote:
> >>>> ping.
> >>>
> >>> Queued. Will send a pull request soon.
> >>
> >> ping, this seems to have got lost, and is blocking us deleting SDL 1.2
> >> support from QEMU.
> >
> > Sigh, never mind, I found the PR is here:
> >
> > https://lists.gnu.org/archive/html/qemu-devel/2019-01/msg00732.html
>
> I had to drop it from the queue because Peter didn’t like the QEMU version
> requirement (for the slirp tftp parameters). :(
IIUC, currently we're just downloading
http://download.patchew.org/openbsd-6.1-amd64.img.xz
can't you just refresh that pre-built image to have SDL 2, based on your
auto-install patches, so we don't have to wait for that to merge.
> What is the blocker for delete SDL 1.2? Is it breaking tests/vm/openbsd?
> If so maybe we can add —disable-sdl to its configure command.
If you don't have SDL then there's no audio driver impl available for
QEMU, so configure fails with:
ERROR: sdl not found or disabled, can not use sdl audio driver
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2019-01-14 10:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 2:57 [Qemu-devel] [PATCH v4] tests: vm: auto_install OpenBSD Fam Zheng
2018-11-11 23:20 ` Brad Smith
2018-11-14 9:58 ` Fam Zheng
2019-01-09 13:55 ` Daniel P. Berrangé
2019-01-09 13:59 ` Daniel P. Berrangé
2019-01-14 3:50 ` Fam Zheng
2019-01-14 10:15 ` Daniel P. Berrangé [this message]
2019-01-14 10:34 ` Peter Maydell
2019-01-22 16:12 ` Daniel P. Berrangé
2019-02-27 13:33 ` Fam Zheng
2019-02-27 13:35 ` Fam Zheng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190114101515.GA3686@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=brad@comstyle.com \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=famz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@ens-lyon.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.