From: Wen Congyang <ghostwcy@gmail.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Wen Congyang <wency@cn.fujitsu.com>
Cc: xen-devl <xen-devel@lists.xen.org>
Subject: Re: building error
Date: Sat, 19 Jul 2014 00:27:30 +0800 [thread overview]
Message-ID: <53C94AF2.2090402@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1407181652500.2295@kaball.uk.xensource.com>
At 2014/7/18 23:55, Stefano Stabellini Wrote:
> On Mon, 14 Jul 2014, Wen Congyang wrote:
>> I update qemu-xen-dir, and find this problem:
>>
>> In file included from /usr/include/spice-server/spice.h:25:0,
>> from /work/src/xen/tools/qemu-xen-dir/include/ui/qemu-spice.h:25,
>> from qemu-char.c:84:
>> /usr/include/spice-1/spice/macros.h:105:0: error: "INLINE" redefined [-Werror]
>> #define INLINE inline
>> ^
>> In file included from /work/src/xen/tools/qemu-xen-dir/include/qemu/bswap.h:8:0,
>> from /work/src/xen/tools/qemu-xen-dir/include/qemu-common.h:112,
>> from qemu-char.c:24:
>> /work/src/xen/tools/qemu-xen-dir/include/fpu/softfloat.h:66:0: note: this is the location of the previous definition
>> #define INLINE static inline
>> ^
>> cc1: all warnings being treated as errors
>> CC page_cache.o
>>
>> This problem has been fixed in upstream qemu:
>> http://git.qemu.org/?p=qemu.git;a=commitdiff;h=a49db98d1f85ada0c4e5bb22bd93d541e7159c43
>>
>
> Thanks for the pointer. I cannot see this failure on my systems but the
> backport should be harmless. I guess you would like a backport of both:
I build it on two systems: fc20 and rhel6. I only see this failure on fc20.
>
> commit 37f6be977aefb5de8afe3ba62a95e88918381305
> Author: Luiz Capitulino <lcapitulino@redhat.com>
> Date: Thu Jun 19 10:19:32 2014 -0400
>
> audio: fmopl: drop INLINE macro
>
> and:
>
> commit a49db98d1f85ada0c4e5bb22bd93d541e7159c43
> Author: Luiz Capitulino <lcapitulino@redhat.com>
> Date: Thu Jun 19 10:13:43 2014 -0400
>
> fpu: softfloat: drop INLINE macro
>
> correct?
Hmm, I only see the second failure. I guess it depends
on the builidng enviroment. But backporting both of them
is fine to me.
Thanks
Wen Congyang
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
next prev parent reply other threads:[~2014-07-18 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 7:00 building error Wen Congyang
2014-07-18 15:55 ` Stefano Stabellini
2014-07-18 16:27 ` Wen Congyang [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-06-17 9:21 Wen Congyang
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=53C94AF2.2090402@gmail.com \
--to=ghostwcy@gmail.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wency@cn.fujitsu.com \
--cc=xen-devel@lists.xen.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).