From: Paolo Bonzini <pbonzini@redhat.com>
To: "Zhanghaoyu (A)" <haoyu.zhang@huawei.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
Luonengjun <luonengjun@huawei.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Huangweidong (C)" <weidong.huang@huawei.com>
Subject: Re: [Qemu-devel] latest version qemu compile error
Date: Wed, 10 Apr 2013 13:13:35 +0200 [thread overview]
Message-ID: <5165495F.40805@redhat.com> (raw)
In-Reply-To: <D3E216785288A145B7BC975F83A2ED103FE16FB5@szxeml556-mbx.china.huawei.com>
Il 10/04/2013 13:03, Zhanghaoyu (A) ha scritto:
>>> The log of "make V=1" is identical with that of "make", shown as below,
>>> > >
>>> > > hw/virtio/dataplane/vring.c: In function 'vring_enable_notification':
>>> > > hw/virtio/dataplane/vring.c:72: warning: implicit declaration of function 'vring_avail_event'
>>> > > hw/virtio/dataplane/vring.c:72: warning: nested extern declaration of 'vring_avail_event'
>>> > > hw/virtio/dataplane/vring.c:72: error: lvalue required as left operand of assignment
>>> > > hw/virtio/dataplane/vring.c: In function 'vring_should_notify':
>>> > > hw/virtio/dataplane/vring.c:107: warning: implicit declaration of function 'vring_need_event'
>>> > > hw/virtio/dataplane/vring.c:107: warning: nested extern declaration of 'vring_need_event'
>>> > > hw/virtio/dataplane/vring.c:107: warning: implicit declaration of function 'vring_used_event'
>>> > > hw/virtio/dataplane/vring.c:107: warning: nested extern declaration of 'vring_used_event'
>>> > > hw/virtio/dataplane/vring.c: In function 'vring_pop':
>>> > > hw/virtio/dataplane/vring.c:262: error: lvalue required as left operand of assignment
>>> > > make: *** [hw/virtio/dataplane/vring.o] Error 1
>> >
>> > I don't need the errors, I need the compiler command line.
>> >
>> > Paolo
> The gcc command line,
> cc -I. -I/home/zhanghaoyu/qemu_201304091521 -I/home/zhanghaoyu/qemu_201304091521/include -fPIE -DPIE -m64 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fstack-protector-all -Wendif-labels -Wmissing-include-dirs -Wempty-body -Wnested-externs -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wold-style-declaration -Wold-style-definition -Wtype-limits -I/usr/include/pixman-1 -Ihw/virtio/dataplane -Ihw/virtio/dataplane -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -MMD -MP -MT hw/virtio/dataplane/vring.o -MF hw/virtio/dataplane/vring.d -O2 -D_FORTIFY_SOURCE=2 -g -c -o hw/virtio/dataplane/vring.o hw/virtio/dataplane/vring.c
Thanks, Jan Kiszka has sent a patch for this issue.
Paolo
prev parent reply other threads:[~2013-04-10 11:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 8:22 [Qemu-devel] latest version qemu compile error Zhanghaoyu (A)
2013-04-09 8:40 ` Paolo Bonzini
2013-04-10 3:24 ` Zhanghaoyu (A)
2013-04-10 4:23 ` Bruce Rogers
2013-04-10 8:04 ` Paolo Bonzini
2013-04-10 11:03 ` Zhanghaoyu (A)
2013-04-10 11:13 ` 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=5165495F.40805@redhat.com \
--to=pbonzini@redhat.com \
--cc=haoyu.zhang@huawei.com \
--cc=luonengjun@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=weidong.huang@huawei.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).