From: Will Deacon <will.deacon@arm.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
linux-kernel@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
ryan.arnold@linaro.org
Subject: Re: lkp: make.cross: old aarch64-gcc has been removed
Date: Thu, 12 Jan 2017 12:00:07 +0000 [thread overview]
Message-ID: <20170112120006.GD1771@arm.com> (raw)
In-Reply-To: <20170112033157.dzajofmuapjmhxdh@wfg-t540p.sh.intel.com>
Hi Fengguang, Masami,
On Thu, Jan 12, 2017 at 11:31:57AM +0800, Fengguang Wu wrote:
> On Wed, Jan 11, 2017 at 07:08:40PM +0900, Masami Hiramatsu wrote:
> >BTW, I found that the old toolchain is archived in release.linaro.org.
> >So I made a patch for that.
>
> So there are gcc 4.9, 5, 6 versions available for aarch64. Since the
> build robot nowadays uses debian's packaged gcc-6-aarch64-linux-gnu,
> it should be better to use gcc-6 in make.coss to better reproduce
> reported regressions:
>
> http://releases.linaro.org/components/toolchain/binaries/latest/aarch64-linux-gnu/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu.tar.xz
>
> There are some other files there and I'm not quite sure if that's the
> right URL to use. CC aarch64 maintainers for possible inputs.
If you're looking for a stable url to grab the latest Linaro binary
toolchains, then it's probably best to ask somebody from the Linaro
Toolchain Working Group. I've added Ryan Arnold to cc, since he should
be able to help.
Ryan: the background is that the Make.cross script [1] hardcodes a path
to a Linaro binary toolchain that no longer exists, so it would be good
to replace it with a stable link pointing to the latest build. Is the one
suggested above correct?
Will
[1] https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross
next prev parent reply other threads:[~2017-01-12 12:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 22:43 lkp: make.cross: old aarch64-gcc has been removed Masami Hiramatsu
2017-01-11 10:08 ` Masami Hiramatsu
2017-01-12 3:31 ` Fengguang Wu
2017-01-12 12:00 ` Will Deacon [this message]
2017-01-12 14:11 ` Fengguang Wu
2017-01-13 3:28 ` Masami Hiramatsu
2017-01-12 3:33 ` Fengguang Wu
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=20170112120006.GD1771@arm.com \
--to=will.deacon@arm.com \
--cc=catalin.marinas@arm.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=ryan.arnold@linaro.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