qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 00/18] Record/replay core for QEMU 2.4-rc1
Date: Thu, 5 Nov 2015 12:18:19 +0100	[thread overview]
Message-ID: <563B3AFB.9020001@redhat.com> (raw)
In-Reply-To: <CAFEAcA_6vCqkuSnF7+gvyeEGKB=MsRgmJjSGSTXQi023BM8T+Q@mail.gmail.com>



On 05/11/2015 11:52, Peter Maydell wrote:
> On 4 November 2015 at 16:17, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> The following changes since commit 7bc8e0c967a4ef77657174d28af775691e18b4ce:
>>
>>   Merge remote-tracking branch 'remotes/mst/tags/for_upstream' into staging (2015-10-29 09:49:52 +0000)
>>
>> are available in the git repository at:
>>
>>
>>   git://github.com/bonzini/qemu.git tags/for-upstream-replay
>>
>> for you to fetch changes up to e02cf7f4de91174dc322e235da6e1a1198601920:
>>
>>   replay: recording of the user input (2015-11-04 15:09:54 +0100)
>>
>> ----------------------------------------------------------------
>> So here it is, let's see what happens.
>>
>> ----------------------------------------------------------------
> 
> Fails to build on all platforms, I'm afraid:
> 
> /home/pm215/qemu/replay/replay-input.c: In function ‘replay_save_input_event’:
> /home/pm215/qemu/replay/replay-input.c:49:25: error: ‘InputEvent’ has
> no member named ‘kind’
>      replay_put_dword(evt->kind);
>                          ^
> /home/pm215/qemu/replay/replay-input.c:51:16: error: ‘InputEvent’ has
> no member named ‘kind’
>      switch (evt->kind) {
>                 ^
> /home/pm215/qemu/replay/replay-input.c:53:29: error: ‘InputEvent’ has
> no member named ‘key’
>          replay_put_dword(evt->key->key->kind);
>                              ^
> /home/pm215/qemu/replay/replay-input.c:55:20: error: ‘InputEvent’ has
> no member named ‘key’
>          switch (evt->key->key->kind) {
>                     ^
> /home/pm215/qemu/replay/replay-input.c:57:33: error: ‘InputEvent’ has
> no member named ‘key’
>              replay_put_qword(evt->key->key->number);
>                                  ^
> /home/pm215/qemu/replay/replay-input.c:58:32: error: ‘InputEvent’ has
> no member named ‘key’
>              replay_put_byte(evt->key->down);
>                                 ^
> /home/pm215/qemu/replay/replay-input.c:61:33: error: ‘InputEvent’ has
> no member named ‘key’
>              replay_put_dword(evt->key->key->qcode);
>                                  ^
> /home/pm215/qemu/replay/replay-input.c:62:32: error: ‘InputEvent’ has
> no member named ‘key’
>              replay_put_byte(evt->key->down);
>                                 ^
> /home/pm215/qemu/replay/replay-input.c:70:29: error: ‘InputEvent’ has
> no member named ‘btn’
>          replay_put_dword(evt->btn->button);
>                              ^
> /home/pm215/qemu/replay/replay-input.c:71:28: error: ‘InputEvent’ has
> no member named ‘btn’
>          replay_put_byte(evt->btn->down);
>                             ^

Hmm, will have to rebase.

Thanks,

Paolo

      reply	other threads:[~2015-11-05 11:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-04 16:17 [Qemu-devel] [PULL 00/18] Record/replay core for QEMU 2.4-rc1 Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 01/18] replay: global variables and function stubs Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 02/18] replay: internal functions for replay log Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 03/18] replay: introduce mutex to protect the " Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 04/18] replay: introduce icount event Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 05/18] cpu-exec: allow temporary disabling icount Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 06/18] cpu: replay instructions sequence Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 07/18] replay: interrupts and exceptions Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 08/18] replay: asynchronous events infrastructure Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 09/18] replay: recording and replaying clock ticks Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 10/18] replay: shutdown event Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 11/18] icount: improve counting for record/replay Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 12/18] replay: checkpoints Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 13/18] bottom halves: introduce bh call function Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 14/18] replay: ptimer Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 15/18] replay: initialization and deinitialization Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 16/18] replay: replay blockers for devices Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 17/18] replay: command line options Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 18/18] replay: recording of the user input Paolo Bonzini
2015-11-04 18:11 ` [Qemu-devel] [PULL 00/18] Record/replay core for QEMU 2.4-rc1 Alex Bennée
2015-11-05 10:52 ` Peter Maydell
2015-11-05 11:18   ` Paolo Bonzini [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=563B3AFB.9020001@redhat.com \
    --to=pbonzini@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 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).