public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: linux-kernel@vger.kernel.org,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>
Subject: Re: lkp: make.cross: old aarch64-gcc has been removed
Date: Fri, 13 Jan 2017 12:28:01 +0900	[thread overview]
Message-ID: <20170113122801.b4a36f3f1518e73c0796ef9a@kernel.org> (raw)
In-Reply-To: <20170112033157.dzajofmuapjmhxdh@wfg-t540p.sh.intel.com>

On Thu, 12 Jan 2017 11:31:57 +0800
Fengguang Wu <fengguang.wu@intel.com> wrote:

> Hi Masami,
> 
> On Wed, Jan 11, 2017 at 07:08:40PM +0900, Masami Hiramatsu wrote:
> >Ping?
> 
> Oops, sorry for overlooking your previous email!
> 
> >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:

OK, that'll be good too. Would it use debian cross-arch gcc for other
architectures too? I would like to make similar environment for build
test internally.

Thank you,

> 
> 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.
> 
> Thanks,
> Fengguang
> 
> >On Fri, 30 Dec 2016 07:43:45 +0900
> >Masami Hiramatsu <mhiramat@kernel.org> wrote:
> >
> >> Hi Fengguang,
> >>
> >> Recently I tried to build a cross-build environment ( https://github.com/mhiramat/linux-cross ) by using your make.cross ( https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross ).
> >> And I've found that it failed to setup cross gcc for aarch64, because it is no more provided by linaro.
> >>
> >> Could you update the url to the newer one from linaro or use crosstool
> >> as like as other archs?
> >>
> >> The latest stable version (gcc-5) can be found here.
> >> http://releases.linaro.org/components/toolchain/binaries/latest-5/
> >>
> >> There are also gcc-6 series for development, and you can find 4.9 binaries
> >> too. But I would like to recommend you to use stable one for testing.
> >>
> >> Thank you,
> >>
> >> --
> >> Masami Hiramatsu <mhiramat@kernel.org>
> >
> >
> >-- 
> >Masami Hiramatsu <mhiramat@kernel.org>
> 
> 


-- 
Masami Hiramatsu <mhiramat@kernel.org>

  parent reply	other threads:[~2017-01-13  3:28 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
2017-01-12 14:11       ` Fengguang Wu
2017-01-13  3:28     ` Masami Hiramatsu [this message]
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=20170113122801.b4a36f3f1518e73c0796ef9a@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=fengguang.wu@intel.com \
    --cc=linux-kernel@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