From: Michal Privoznik <mprivozn@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, victork@redhat.com, cota@braap.org
Subject: Re: [Qemu-devel] [PATCH] vhost-user-bridge: fix "unknown type name" compilation error
Date: Wed, 31 Oct 2018 12:25:19 +0100 [thread overview]
Message-ID: <761c7de1-2e95-b657-e6bb-7190aa8813e4@redhat.com> (raw)
In-Reply-To: <20181031104136.9953-1-marcandre.lureau@redhat.com>
On 10/31/2018 11:41 AM, Marc-André Lureau wrote:
> osdep.h should be included first:
>
> CC tests/vhost-user-bridge.o
> In file included from /home/elmarco/src/qemu/tests/vhost-user-bridge.c:32:
> /home/elmarco/src/qemu/include/qemu/atomic.h:480:1: error: unknown type name ‘int64_t’
> int64_t atomic_read_i64(const int64_t *ptr);
> ^~~~~~~
> /home/elmarco/src/qemu/include/qemu/atomic.h:480:32: error: unknown type name ‘int64_t’
> int64_t atomic_read_i64(const int64_t *ptr);
> ^~~~~~~
> /home/elmarco/src/qemu/include/qemu/atomic.h:481:1: error: unknown type name ‘uint64_t’
> uint64_t atomic_read_u64(const uint64_t *ptr);
> ^~~~~~~~
> /home/elmarco/src/qemu/include/qemu/atomic.h:481:32: error: unknown type name ‘uint64_t’
> uint64_t atomic_read_u64(const uint64_t *ptr);
> ^~~~~~~~
> /home/elmarco/src/qemu/include/qemu/atomic.h:482:21: error: unknown type name ‘int64_t’
> void atomic_set_i64(int64_t *ptr, int64_t val);
> ^~~~~~~
> /home/elmarco/src/qemu/include/qemu/atomic.h:482:35: error: unknown type name ‘int64_t’
> void atomic_set_i64(int64_t *ptr, int64_t val);
> ^~~~~~~
> /home/elmarco/src/qemu/include/qemu/atomic.h:483:21: error: unknown type name ‘uint64_t’
> void atomic_set_u64(uint64_t *ptr, uint64_t val);
> ^~~~~~~~
> /home/elmarco/src/qemu/include/qemu/atomic.h:483:36: error: unknown type name ‘uint64_t’
> void atomic_set_u64(uint64_t *ptr, uint64_t val);
> ^~~~~~~~
>
> (regression from 782da5b2921c4d18777d5d5bd9385b9f7beae360)
>
> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> ---
> tests/vhost-user-bridge.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Funny, I was just looking into this right now :-)
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
Michal
next prev parent reply other threads:[~2018-10-31 11:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 10:41 [Qemu-devel] [PATCH] vhost-user-bridge: fix "unknown type name" compilation error Marc-André Lureau
2018-10-31 11:25 ` Michal Privoznik [this message]
2018-10-31 15:59 ` Emilio G. Cota
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=761c7de1-2e95-b657-e6bb-7190aa8813e4@redhat.com \
--to=mprivozn@redhat.com \
--cc=cota@braap.org \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=victork@redhat.com \
/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).