From: Jiri Slaby <jslaby@suse.cz>
To: Gerd Hoffmann <kraxel@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: Andreas Faerber <AFaerber@suse.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] qemu is missing monitor
Date: Fri, 10 Oct 2014 12:31:16 +0200 [thread overview]
Message-ID: <5437B574.20101@suse.cz> (raw)
In-Reply-To: <1412926708.11084.1.camel@nilsson.home.kraxel.org>
On 10/10/2014, 09:38 AM, Gerd Hoffmann wrote:
> On Do, 2014-10-09 at 17:05 +0100, Peter Maydell wrote:
>> On 9 October 2014 14:37, Jiri Slaby <jslaby@suse.cz> wrote:
>>> Hi guys,
>>>
>>> qemu in opensuse latest (factory) does not have monitor. Despite
>>> libvte-devel is installed, it is not detected by qemu. The problem is
>>> that configure looks for vte-2.90, but we have vte-2.91 in factory. The
>>> attached patch fixes that for factory, but it's dirty, of course.
>>
>> Why the heck have the GTK folk made point releases end up
>> needing their own pkg-config library name??
>
> Good question. They should not do that in the first place unless they
> have a ABI change (i.e. gtk2 -> gtk3 switch was a good reason). The
> point release doesn't look like that though ...
Note, that qemu is terribly broken with 2.91. The monitor window is over
30 000 pixels in height. So there is perhaps some weird API/ABI change.
Built against 2.90, it works fine.
> I'd suggest to try sort that with vte upstream before trying to hack
> around this in qemu (and if we have to we'll need to check for both 2.90
> and 2.91 because you don't know what version the user has installed).
Ok, could you take care of that and sort that out?
--
js
suse labs
next prev parent reply other threads:[~2014-10-10 10:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-09 13:37 [Qemu-devel] qemu is missing monitor Jiri Slaby
2014-10-09 16:05 ` Peter Maydell
2014-10-10 7:38 ` Gerd Hoffmann
2014-10-10 10:31 ` Jiri Slaby [this message]
2014-10-10 7:49 ` Jiri Slaby
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=5437B574.20101@suse.cz \
--to=jslaby@suse.cz \
--cc=AFaerber@suse.com \
--cc=agraf@suse.de \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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.