From: "Alex Bennée" <alex.bennee@linaro.org>
To: Pranith Kumar <bobby.prani@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] aarch64-linux-user compilation error
Date: Mon, 12 Dec 2016 11:39:49 +0000 [thread overview]
Message-ID: <87k2b5tlyy.fsf@linaro.org> (raw)
In-Reply-To: <CAJhHMCAvd0+PNFF-PfMVP2aSpN2V9B7XbV59qh-FaXtLGemQmg@mail.gmail.com>
Pranith Kumar <bobby.prani@gmail.com> writes:
> On Sun, Dec 11, 2016 at 5:59 PM, Peter Maydell <peter.maydell@linaro.org> wrote:
>>
>>> Error:
>>> /home/pranith/devops/code/qemu/linux-user/ioctls.h:224:9: error: ‘SNDCTL_DSP_MAPINBUF’ undeclared here (not in a function)
>>> IOCTL(SNDCTL_DSP_MAPINBUF, IOC_R, MK_PTR(MK_STRUCT(STRUCT_buffmem_desc)))
>>> ^
>>
>> SNDCTL_DSP_MAPINBUF is supposed to be defined by your system
>> headers (/usr/include/linux/soundcard.h or equivalent).
>> Similarly for SNDCTL_DSP_MAPOUTBUF and SOUND_MIXER_ACCESS.
>>
>> Looking at QEMU's git history we've used these symbols
>> for years. I would check whether your system headers
>> are actually providing these symbols (and that the
>> compiler is really putting the right headers on the
>> include path).
>
> So soundcard.h header is provided by two packages:
>
> $ apt-file search /usr/include/linux/soundcard.h
> linux-libc-dev: /usr/include/linux/soundcard.h
> oss4-dev: /usr/include/linux/soundcard.h
>
> I had oss4-dev installed. After removing that and reinstalling
> linux-libc-dev, it compiles fine. Not sure why this file differs. May
> be a packaging issue.
Sounds like it. How did you ensure you had your QEMU build dependencies
installed on your system?
--
Alex Bennée
next prev parent reply other threads:[~2016-12-12 11:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-11 19:09 [Qemu-devel] aarch64-linux-user compilation error Pranith Kumar
2016-12-11 19:32 ` Pranith Kumar
2016-12-11 22:59 ` Peter Maydell
2016-12-12 1:36 ` Pranith Kumar
2016-12-12 11:39 ` Alex Bennée [this message]
2016-12-13 2:17 ` Pranith Kumar
2016-12-13 7:25 ` Alex Bennée
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=87k2b5tlyy.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=bobby.prani@gmail.com \
--cc=peter.maydell@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.