From: "Alex Bennée" <alex.bennee@linaro.org>
To: Bug 1658120 <1658120@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1658120] [NEW] building with gcc-aarch64-linux-gnu
Date: Fri, 20 Jan 2017 15:50:46 +0000 [thread overview]
Message-ID: <87o9z1enmx.fsf@linaro.org> (raw)
In-Reply-To: <20170120152141.14276.42073.malonedeb@soybean.canonical.com>
Bilal Amarni <1658120@bugs.launchpad.net> writes:
> Public bug reported:
>
> Hi, while trying to build qemu v2.8.0 with gcc-aarch64-linux-gnu cross-
> compiler I'm getting the following :
>
>
> In file included from /usr/include/x86_64-linux-gnu/sys/syscall.h:31:0,
> from /root/qemu/util/compatfd.c:21:
> /root/qemu/util/compatfd.c: In function 'qemu_signalfd':
> /root/qemu/util/compatfd.c:103:19: error: '__NR_signalfd' undeclared (first use in this function)
> ret = syscall(SYS_signalfd, -1, mask, _NSIG / 8);
> ^
> /root/qemu/util/compatfd.c:103:19: note: each undeclared identifier is reported only once for each function it appears in
> /root/qemu/rules.mak:59: recipe for target 'util/compatfd.o' failed
> make: *** [util/compatfd.o] Error 1
>
>
> I had configured it with :
>
> ../configure --target-list=x86_64-linux-user --static --cpu=aarch64
>
> And I'm on :
>
> Linux ubuntu-512mb-fra1-01 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6
> 17:47:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Do you have:
/usr/include/aarch64-linux-gnu/bits/syscall.h
In your system?
When cross compiling it is these sort of problems come from not having
the architecture specific development files. On Ubuntu you want
something like:
apt-get build-dep -a arm64 qemu
--
Alex Bennée
next prev parent reply other threads:[~2017-01-20 15:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 15:21 [Qemu-devel] [Bug 1658120] [NEW] building with gcc-aarch64-linux-gnu Bilal Amarni
2017-01-20 15:47 ` Peter Maydell
2017-01-20 15:50 ` Alex Bennée [this message]
2017-01-21 13:14 ` [Qemu-devel] [Bug 1658120] " Bilal Amarni
2017-01-21 13:15 ` Bilal Amarni
2018-03-07 8:51 ` Cao Van Dong
2018-03-07 9:51 ` Alex Bennée
2018-03-07 9:37 ` philmd
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=87o9z1enmx.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=1658120@bugs.launchpad.net \
--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).