From: szabolcs.nagy@arm.com (Szabolcs Nagy)
To: linux-arm-kernel@lists.infradead.org
Subject: build failure with VDSO on non-glibc based systems
Date: Tue, 23 Jun 2015 11:35:05 +0100 [thread overview]
Message-ID: <55893659.80607@arm.com> (raw)
if the host toolchain is not glibc based then the arm kernel build fails with
arch/arm/vdso/vdsomunge.c:53:19: fatal error: error.h: No such file or directory
error.h is a glibc only header (ie not available in musl, newlib and bsd libcs).
i attached a patch that fixes the build failure for me.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-fix-arm-vdsomunge-not-to-depend-on-glibc-specific-er.patch
Type: text/x-patch
Size: 4168 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150623/81f37be6/attachment.bin>
next reply other threads:[~2015-06-23 10:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 10:35 Szabolcs Nagy [this message]
2015-06-23 15:16 ` build failure with VDSO on non-glibc based systems Nathan Lynch
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=55893659.80607@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).