All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jslaby@suse.cz>
To: 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 09:49:00 +0200	[thread overview]
Message-ID: <54378F6C.80409@suse.cz> (raw)
In-Reply-To: <CAFEAcA_mPuh6BnMnF8cS9mUbpK0pVJ_1MaFCR2ASvr6uS7S8bw@mail.gmail.com>

On 10/09/2014, 06:05 PM, 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??

Don't ask me, /me wonders too. I am thinking of one of
* --enable-vte=2.91: we would have to do rpm -q vte-devel in .spec, but
that should work
* for ver in `seq 0 9`; do
    if pkg-config --exists vte-2.9$ver; then
      vteversion="vte-2.9$ver"
    fi
  done
* yell at the author of the versioning to retract and rethink!

thanks,
-- 
js
suse labs

      parent reply	other threads:[~2014-10-10  7:49 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
2014-10-10  7:49   ` Jiri Slaby [this message]

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=54378F6C.80409@suse.cz \
    --to=jslaby@suse.cz \
    --cc=AFaerber@suse.com \
    --cc=agraf@suse.de \
    --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.