From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:42735)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1XcUmd-0006i9-Ry
	for qemu-devel@nongnu.org; Fri, 10 Oct 2014 03:38:44 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1XcUmY-00011U-UG
	for qemu-devel@nongnu.org; Fri, 10 Oct 2014 03:38:39 -0400
Received: from mx1.redhat.com ([209.132.183.28]:18565)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1XcUmY-00011E-NA
	for qemu-devel@nongnu.org; Fri, 10 Oct 2014 03:38:34 -0400
Message-ID: <1412926708.11084.1.camel@nilsson.home.kraxel.org>
From: Gerd Hoffmann <kraxel@redhat.com>
Date: Fri, 10 Oct 2014 09:38:28 +0200
In-Reply-To: <CAFEAcA_mPuh6BnMnF8cS9mUbpK0pVJ_1MaFCR2ASvr6uS7S8bw@mail.gmail.com>
References: <54368FAA.9080906@suse.cz>
	<CAFEAcA_mPuh6BnMnF8cS9mUbpK0pVJ_1MaFCR2ASvr6uS7S8bw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] qemu is missing monitor
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Andreas Faerber <AFaerber@suse.com>, Jiri Slaby <jslaby@suse.cz>, QEMU Developers <qemu-devel@nongnu.org>, Alexander Graf <agraf@suse.de>

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 ...

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).

cheers,
  Gerd