From: Mark Brown <broonie@kernel•org>
To: Catalin Marinas <catalin.marinas@arm•com>,
Will Deacon <will.deacon@arm•com>
Cc: linaro-kernel@lists•linaro.org, khilman@kernel•org,
kernel-build-reports@lists•linaro.org,
linux-next@vger•kernel.org, matthew.hart@linaro•org,
linux-arm-kernel@lists•infradead.org
Subject: Re: next-20180723 build: 2 failures 11 warnings (next-20180723)
Date: Mon, 23 Jul 2018 19:11:50 +0100 [thread overview]
Message-ID: <20180723181150.GF13981@sirena.org.uk> (raw)
In-Reply-To: <E1fheAy-0003tU-Dq@optimist>
[-- Attachment #1.1: Type: text/plain, Size: 779 bytes --]
On Mon, Jul 23, 2018 at 05:59:12PM +0100, Build bot for Mark Brown wrote:
Today's -next fails to build an arm64 allmodconfig with:
> arm64-allmodconfig
> ERROR: "__sync_icache_dcache" [drivers/xen/xen-privcmd.ko] undefined!
using
aarch64-linux-gnu-gcc (Linaro GCC 5.3-2016.05) 5.3.1 20160412
however it builds perfectly fine with
aarch64-linux-gnu-gcc (Linaro GCC 6.2-2016.11) 6.2.1 20161016
which honestly seems like a sensible and worthwhile upgrade at this
point anyway given that it's a year and a half old so I'm going to do
that for my builder (perhaps even jump on a newer version) but it seemed
worth highlighting in case this is considered undesirable. A similar
issue is hitting on KernelCI, we should probably look at upgrading the
toolchain there too.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next parent reply other threads:[~2018-07-23 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1fheAy-0003tU-Dq@optimist>
2018-07-23 18:11 ` Mark Brown [this message]
2018-07-24 9:16 ` next-20180723 build: 2 failures 11 warnings (next-20180723) Will Deacon
[not found] ` <CAH+k93GQRKO8s+0qkSH+d_2GkapMAp8C776Q4bZZnL37M5MBCw@mail.gmail.com>
2018-07-24 9:34 ` Matt Hart
2018-07-23 18:25 ` Mark Brown
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=20180723181150.GF13981@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=catalin.marinas@arm$(echo .)com \
--cc=kernel-build-reports@lists$(echo .)linaro.org \
--cc=khilman@kernel$(echo .)org \
--cc=linaro-kernel@lists$(echo .)linaro.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=matthew.hart@linaro$(echo .)org \
--cc=will.deacon@arm$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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