From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Compiling qemu with nas installed
Date: Tue, 10 Mar 2009 13:22:32 -0500 [thread overview]
Message-ID: <49B6AFE8.9000600@codemonkey.ws> (raw)
In-Reply-To: <f43fc5580903100922u4e718ccepa7039a4be192cbfc@mail.gmail.com>
Blue Swirl wrote:
> On 3/8/09, Hasso Tepper <hasso@estpak.ee> wrote:
>
>> If user has packages installed in "nonstandard" paths (like pkgsrc package
>> system used by NetBSD and DragonFly - /usr/pkg), CPPFLAGS and LDFLAGS are
>> used normally by users to help configure scripts etc to find headers and
>> libraries.
>>
>> $ export CPPFLAGS=-I/usr/pkg/include
>> $ export LDFLAGS=-L/usr/pkg/lib
>>
>> This causes the problem if user has the nas software package installed:
>>
You should use --extra-cflags and --extra-ldflags. If we're not already
making these come before our -I$(srcdir), then we should change that.
Basically, we need to ensure that any of our headers have include
priority over system headers in the search path.
Regards,
Anthony Liguori
>> CC wm8750.o
>> /tmp/q/wm8750.c:24: error: expected specifier-qualifier-list
>> before 'QEMUSoundCard'
>> /tmp/q/hw/wm8750.c: In function 'wm8750_in_load':
>> /tmp/q/hw/wm8750.c:59: error: 'struct wm8750_s' has no member
>> named 'idx_in'
>> /tmp/q/hw/wm8750.c:59: error: 'struct wm8750_s' has no member
>> named 'req_in'
>> etc etc etc
>>
>> The problem comes from fact that the nas package has also audio/audio.h
>> file and it's included in wm8750.c if user or package system defines
>> CPPFLAGS which happen to include the path to the audio/audio.h from nas.
>>
>> I don't how to fix it correctly, but I think that local paths should be
>> always before system or user specified ones.
>>
>
> Rename audio/audio.h to audio/qemu_audio.h?
>
>
>
next prev parent reply other threads:[~2009-03-10 18:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-08 21:21 [Qemu-devel] Compiling qemu with nas installed Hasso Tepper
2009-03-10 16:22 ` Blue Swirl
2009-03-10 18:22 ` Anthony Liguori [this message]
2009-03-10 19:22 ` malc
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=49B6AFE8.9000600@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).