From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Peter Foley <pefoley2@pefoley.com>
Subject: linux-next: build failure after merge of the rd-docs tree
Date: Tue, 16 Sep 2014 17:11:02 +1000 [thread overview]
Message-ID: <20140916171102.61509be5@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 421 bytes --]
Hi Randy,
After merging the rd-docs tree, today's linux-next build (powerpc
allyesconfig) failed like this:
Documentation/vDSO/vdso_test.c:15:22: fatal error: sys/auxv.h: No such file or directory
Caused by commit e9cb990eff15 ("Documentation: update vDSO makefile to
build portable examples").
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2014-09-16 7:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 7:11 Stephen Rothwell [this message]
2014-09-16 17:19 ` linux-next: build failure after merge of the rd-docs tree Peter Foley
2014-09-16 23:00 ` Stephen Rothwell
2014-09-16 23:18 ` Peter Foley
2014-09-16 23:38 ` Randy Dunlap
2014-09-17 0:02 ` Peter Foley
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=20140916171102.61509be5@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pefoley2@pefoley.com \
--cc=rdunlap@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).