From: Peter Maydell <peter.maydell@linaro.org>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
"BALATON Zoltan" <balaton@eik.bme.hu>,
"Lluís Vilanova" <vilanova@ac.upc.edu>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Patch Tracking" <patches@linaro.org>
Subject: Re: [Qemu-devel] [PATCH] disas: Fix ATTRIBUTE_UNUSED define clash with ALSA headers
Date: Tue, 19 Jul 2016 17:50:03 +0100 [thread overview]
Message-ID: <CAFEAcA8BSa8OTxH-PyB0rAY3hTrBnX5C2SmpLdyw=fMELn=ysw@mail.gmail.com> (raw)
In-Reply-To: <20160719141714.GA23779@stefanha-x1.localdomain>
On 19 July 2016 at 15:17, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> On Tue, Jul 19, 2016 at 03:04:36PM +0100, Peter Maydell wrote:
>> disas/bfd.h defines ATTRIBUTE_UNUSED, but unfortunately the
>> ALSA system headers also define this macro, which means that
>> you can get a compilation failure if building with ALSA and
>> any files happen to include the alsa headers before bfd.h
>> rather than the other way around.
>>
>> This is unfortunate namespace pollution by the ALSA headers but
>> we can work around it. Add an #ifndef guard to bfd.h and remove
>> the unnecessary extra definition in disas/arm.c to fix this.
>>
>> Reported-by: BALATON Zoltan <balaton@eik.bme.hu>
>> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
>> ---
>> disas/arm.c | 1 -
>> include/disas/bfd.h | 2 ++
>> 2 files changed, 2 insertions(+), 1 deletion(-)
>
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Thanks; applied to master as a buildfix.
-- PMM
prev parent reply other threads:[~2016-07-19 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 14:04 [Qemu-devel] [PATCH] disas: Fix ATTRIBUTE_UNUSED define clash with ALSA headers Peter Maydell
2016-07-19 14:17 ` Stefan Hajnoczi
2016-07-19 16:50 ` Peter Maydell [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='CAFEAcA8BSa8OTxH-PyB0rAY3hTrBnX5C2SmpLdyw=fMELn=ysw@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=balaton@eik.bme.hu \
--cc=patches@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@redhat.com \
--cc=vilanova@ac.upc.edu \
/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).