From: Mark Brown <broonie@kernel.org>
To: Kevin Brodsky <kevin.brodsky@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>
Cc: kernel-build-reports@lists.linaro.org,
linaro-kernel@lists.linaro.org, linux-next@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: next-20160711 build: 3 failures 10 warnings (next-20160711)
Date: Mon, 11 Jul 2016 19:31:13 +0100 [thread overview]
Message-ID: <20160711183113.GH3701@sirena.org.uk> (raw)
In-Reply-To: <E1bMZki-0001u7-VI@optimist>
[-- Attachment #1: Type: text/plain, Size: 720 bytes --]
On Mon, Jul 11, 2016 at 12:51:57PM +0100, Build bot for Mark Brown wrote:
Today's -next fails to build on all arm64 configs with:
> ../arch/arm64/include/asm/vdso.h:30:36: fatal error: generated/vdso-offsets.h: No such file or directory
> ../arch/arm64/include/asm/vdso.h:30:36: fatal error: generated/vdso-offsets.h: No such file or directory
due to 90f777beb788 (arm64: Fix vdso-offsets.h dependency) when built
from a completely clean tree (eg, after make distconfig). Building from
a non-clean environment does work, as does reverting that commit. The
dependencies required to ensure that the header gets generated before
it's used aren't present so make doesn't figure out the ordering
correctly.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2016-07-11 18:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 11:51 next-20160711 build: 3 failures 10 warnings (next-20160711) Build bot for Mark Brown
2016-07-11 18:31 ` Mark Brown [this message]
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=20160711183113.GH3701@sirena.org.uk \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=kevin.brodsky@arm.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=will.deacon@arm.com \
/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