From: Stefan Weil <weil@mail.berlios.de>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH] configure: Send error message from spice check to /dev/null
Date: Thu, 07 Oct 2010 21:11:36 +0200 [thread overview]
Message-ID: <4CAE1B68.8030701@mail.berlios.de> (raw)
In-Reply-To: <4CAE1A0D.7000704@redhat.com>
Am 07.10.2010 21:05, schrieb Gerd Hoffmann:
> On 10/07/10 17:58, Stefan Weil wrote:
>> pkg-config is not always available (e.g. on win32 hosts),
>> but we don't want to see the 'command not found' error message.
>
>> compile_object() {
>> + echo>>config.log
>> + cat $TMPC>>config.log
>> + echo>>config.log
>
> This looks unrelated.
Ups, that was the wrong patch (some test code).
Sorry - I'll fix that immediately.
Thanks for your feedback.
>
>> @@ -28,6 +31,9 @@ compile_object() {
>> compile_prog() {
>> local_cflags="$1"
>> local_ldflags="$2"
>> + echo>>config.log
>> + cat $TMPC>>config.log
>> + echo>>config.log
>
> This too.
>
>> spice_cflags=$($pkgconfig --cflags spice-protocol spice-server
>> 2>/dev/null)
>> spice_libs=$($pkgconfig --libs spice-protocol spice-server
>> 2>/dev/null)
>> - if $pkgconfig --atleast-version=0.5.3 spice-server&&\
>> + if $pkgconfig --atleast-version=0.5.3 spice-server>/dev/null
>> 2>&1&& \
>
> Fine with me, the other pkgconfig calls are covered already, the third
> missing is just an oversight and the fix is ObliviouslyCorrect[tm].
>
> cheers,
> Gerd
>
>
next prev parent reply other threads:[~2010-10-07 19:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 15:58 [Qemu-devel] [PATCH] configure: Send error message from spice check to /dev/null Stefan Weil
2010-10-07 19:05 ` [Qemu-devel] " Gerd Hoffmann
2010-10-07 19:11 ` Stefan Weil [this message]
2010-10-07 19:15 ` [Qemu-devel] [PATCH v2] " Stefan Weil
2010-10-09 9:44 ` Blue Swirl
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=4CAE1B68.8030701@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=kraxel@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).