From: Pranith Kumar <bobby.prani@gmail.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, alex.bennee@linaro.org
Subject: [Qemu-devel] aarch64-linux-user compilation error
Date: Sun, 11 Dec 2016 14:09:36 -0500 [thread overview]
Message-ID: <87lgvm1dvz.fsf@gmail.com> (raw)
Hi,
I am getting a strange compilation error lately for aarch64-linux-user. I
think it is somehow related to TYPE_PTRVOID handling but my investigation has
not led to anything concrete. I think this is a compiler error since the build
passes on an other system with gcc-6.
Info: ubuntu 16.04 x86_64 system
$ gcc --version
gcc (Ubuntu 5.4.1-2ubuntu1~16.04) 5.4.1 20160904
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)))
^
/home/pranith/devops/code/qemu/linux-user/syscall.c:5453:23: note: in definition of macro ‘IOCTL’
{ TARGET_ ## cmd, cmd, #cmd, access, 0, { __VA_ARGS__ } },
^
/home/pranith/devops/code/qemu/linux-user/ioctls.h:225:9: error: ‘SNDCTL_DSP_MAPOUTBUF’ undeclared here (not in a function)
IOCTL(SNDCTL_DSP_MAPOUTBUF, IOC_R, MK_PTR(MK_STRUCT(STRUCT_buffmem_desc)))
^
/home/pranith/devops/code/qemu/linux-user/syscall.c:5453:23: note: in definition of macro ‘IOCTL’
{ TARGET_ ## cmd, cmd, #cmd, access, 0, { __VA_ARGS__ } },
^
/home/pranith/devops/code/qemu/linux-user/ioctls.h:280:9: error: ‘SOUND_MIXER_ACCESS’ undeclared here (not in a function)
IOCTL(SOUND_MIXER_ACCESS, 0, TYPE_PTRVOID)
^
/home/pranith/devops/code/qemu/linux-user/syscall.c:5453:23: note: in definition of macro ‘IOCTL’
{ TARGET_ ## cmd, cmd, #cmd, access, 0, { __VA_ARGS__ } },
^
/home/pranith/devops/code/qemu/rules.mak:60: recipe for target 'linux-user/syscall.o' failed
--
Pranith
next reply other threads:[~2016-12-11 19:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-11 19:09 Pranith Kumar [this message]
2016-12-11 19:32 ` [Qemu-devel] aarch64-linux-user compilation error Pranith Kumar
2016-12-11 22:59 ` Peter Maydell
2016-12-12 1:36 ` Pranith Kumar
2016-12-12 11:39 ` Alex Bennée
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=87lgvm1dvz.fsf@gmail.com \
--to=bobby.prani@gmail.com \
--cc=alex.bennee@linaro.org \
--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 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).