From: Juan Quintela <quintela@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: lvivier@redhat.com, peterx@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] migration: Move check_migratable() into qdev.c
Date: Thu, 11 May 2017 17:37:37 +0200 [thread overview]
Message-ID: <87inl7h0am.fsf@secure.mitica> (raw)
In-Reply-To: <20170511152710.GI2078@work-vm> (David Alan Gilbert's message of "Thu, 11 May 2017 16:27:11 +0100")
"Dr. David Alan Gilbert" <dgilbert@redhat.com> wrote:
> * no-reply@patchew.org (no-reply@patchew.org) wrote:
>> Hi,
>>
>> CC armeb-linux-user/gdbstub-xml.o
>> CC armeb-linux-user/trace/generated-helpers.o
>> LINK armeb-linux-user/qemu-armeb
>> ../hw/core/qdev.o: In function `check_only_migratable':
>> /var/tmp/patchew-tester-tmp-uf2ealih/src/hw/core/qdev.c:869:
>> undefined reference to `only_migratable'
>> collect2: error: ld returned 1 exit status
>> Makefile:201: recipe for target 'qemu-armeb' failed
>> make[1]: *** [qemu-armeb] Error 1
>> Makefile:327: recipe for target 'subdir-armeb-linux-user' failed
>> make: *** [subdir-armeb-linux-user] Error 2
>> === OUTPUT END ===
>
> Right, you see why I suggested testing for the user only build!
grrrr,
ok, thanks. So trivial change, what could have failed ...
>
> Dave
>
>>
>> Test command exited with code: 2
>>
>>
>> ---
>> Email generated automatically by Patchew [http://patchew.org/].
>> Please send your feedback to patchew-devel@freelists.org
> --
> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
prev parent reply other threads:[~2017-05-11 15:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 14:39 [Qemu-devel] [PATCH] migration: Move check_migratable() into qdev.c Juan Quintela
2017-05-11 14:46 ` Juan Quintela
2017-05-11 15:09 ` Dr. David Alan Gilbert
2017-05-11 15:24 ` no-reply
2017-05-11 15:27 ` Dr. David Alan Gilbert
2017-05-11 15:37 ` Juan Quintela [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=87inl7h0am.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lvivier@redhat.com \
--cc=peterx@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).