All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] configure: ignore spice libraries on 32 bit.
Date: Wed, 07 Mar 2012 12:38:43 +0100	[thread overview]
Message-ID: <4F5748C3.9010708@redhat.com> (raw)
In-Reply-To: <CAFEAcA-VEou3Cc5xd3wodTrrfFv3q87uWwkxBhsr0qx7xxs0fA@mail.gmail.com>

On 03/07/12 11:30, Peter Maydell wrote:
> On 8 February 2012 15:22, Gerd Hoffmann <kraxel@redhat.com> wrote:
>> On 02/08/12 01:17, Rusty Russell wrote:
>>> As featured on:
>>>         https://bugs.launchpad.net/qemu-linaro/+bug/928432
>>>
>>> Since we compile with -Werror, the presence of spice headers breaks
>>> compile.  Yet except for x86-64, it doesn't compile, doesn't work, isn't
>>> supported.  See: http://spice-space.org/faq.html
>>
>> Outdated.  64bit restrictions are gone, spice server works on 32bit too.
>>  Thats why 32bit spice packages exist in the first place ;)
>>
>> Attached patch fixes the warnings.
> 
> Ping -- there seem to have been a couple of spice patch queue
> pulls since but did this warning fix patch get lost?

commit f4a8a424fceb0f79bbd9f7ae4285c8a58eb5598e

But it still doesn't build indeed.
Looks like new warnings sneaked in ...

cheers,
  Gerd

  reply	other threads:[~2012-03-07 11:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-08  0:17 [Qemu-devel] [PATCH] configure: ignore spice libraries on 32 bit Rusty Russell
2012-02-08 15:22 ` Gerd Hoffmann
2012-03-07 10:30   ` Peter Maydell
2012-03-07 11:38     ` Gerd Hoffmann [this message]
2012-03-07 11:45       ` Peter Maydell
2012-03-07 12:33       ` Peter Maydell
2012-03-07 12:43         ` Gerd Hoffmann
2012-03-07 13:01           ` Alon Levy
2012-03-07 13:54             ` Peter Maydell
2012-03-07 14:19               ` [Qemu-devel] [PATCH] spice: require spice-protocol >= 0.8.1 Alon Levy

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=4F5748C3.9010708@redhat.com \
    --to=kraxel@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rusty@rustcorp.com.au \
    /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.