linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: r.schwebel@pengutronix.de (Robert Schwebel)
To: linux-arm-kernel@lists.infradead.org
Subject: Announce: rmk's nightly builder gets ARM64 support
Date: Fri, 20 Feb 2015 20:03:05 +0100	[thread overview]
Message-ID: <20150220190305.GO15673@pengutronix.de> (raw)
In-Reply-To: <20150220102009.GF8656@n2100.arm.linux.org.uk>

On Fri, Feb 20, 2015 at 10:20:09AM +0000, Russell King - ARM Linux wrote:
> On Fri, Feb 20, 2015 at 09:40:35AM +0000, Russell King - ARM Linux wrote:
> > On Fri, Feb 20, 2015 at 09:24:39AM +0000, Ard Biesheuvel wrote:
> > > Yes, this looks like a GCC problem, not binutils, since there are
> > > other .S files in the same folder that contain crypto instructions
> > > that build fine. This particular one is a .c file with AES
> > > instructions in inline asm() (and we pass -march=armv8-a+crypto)
> > 
> > Maybe we need to get jk's blog post updated - it's currently on of
> > the top hits in google, so this is probably going to trip up a lot of
> > people if they follow the instructions there.
> > 
> > http://jk.ozlabs.org/docs/arm64-toolchain/
> > 
> > So it sounds like possibly the binutils part of those instructions is
> > fine, it's the gcc part which isn't.
> 
> Note that it would also be useful to know where to get a working gcc
> from (preferably in source form - I doubt there's any Fedora 14
> binaries around.)

We have an arm 64 bit toolchain in OSELAS.Toolchain:
http://git.pengutronix.de/?p=OSELAS.Toolchain.git

with this ptxconfig:
http://git.pengutronix.de/?p=OSELAS.Toolchain.git;a=blob;f=ptxconfigs/aarch64-v8a-linux-gnu_gcc-4.9.2_glibc-2.20_binutils-2.24_kernel-3.16-sanitized.ptxconfig

rsc
-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  parent reply	other threads:[~2015-02-20 19:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-19 17:12 Announce: rmk's nightly builder gets ARM64 support Russell King - ARM Linux
2015-02-19 18:34 ` Russell King - ARM Linux
2015-02-20  9:20   ` Will Deacon
2015-02-20  9:24     ` Ard Biesheuvel
2015-02-20  9:40       ` Russell King - ARM Linux
2015-02-20 10:20         ` Russell King - ARM Linux
2015-02-20 10:35           ` Fabio Estevam
2015-02-20 13:38             ` Russell King - ARM Linux
2015-02-20 13:49               ` Fabio Estevam
2015-02-20 14:03                 ` Ard Biesheuvel
2015-02-20 14:04                 ` Will Deacon
2015-02-20 17:59                   ` Russell King - ARM Linux
2015-02-20 18:02                     ` Fabio Estevam
2015-02-20 18:08                     ` Marc Zyngier
2015-02-20 18:32                     ` Will Deacon
2015-02-20 22:12                     ` Rob Herring
2015-02-20 19:03           ` Robert Schwebel [this message]
2015-02-20 11:45         ` Jeremy Kerr

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=20150220190305.GO15673@pengutronix.de \
    --to=r.schwebel@pengutronix.de \
    --cc=linux-arm-kernel@lists.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).