From: Christoph Egger <Christoph.Egger@amd.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] header include order causes build failure
Date: Thu, 26 May 2011 10:07:18 +0200 [thread overview]
Message-ID: <4DDE0A36.2050407@amd.com> (raw)
Hi,
qemu build system includes third party headers before
qemu headers which is wrong. It should be the other
way around.
When 'nas' (Network Audio System,
http://www.pdl.cmu.edu/NASD/Downloads/NASDcode.html)
is installed then there is an external "audio/audio.h".
Due to the wrong header include order this one is used instead of
qemu's one and causes a build error saying that
QEMUSoundCard is not defined.
gcc error message:
hw/wm8750.c:30:error: expected specifier-qualifier-list before
'QEMUSoundCard'
Christoph
--
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Einsteinring 24, 85689 Dornach b. Muenchen
Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
reply other threads:[~2011-05-26 8:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4DDE0A36.2050407@amd.com \
--to=christoph.egger@amd.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).