lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 3 Nov 2017 11:36:33 -0700
From:   Nick Desaulniers <>
To:     Mark Rutland <>
Cc:     Sami Tolvanen <>,
        LKML <>,,
        Matthias Kaehlcke <>,
        Kees Cook <>,
        Greg Hackmann <>,
        George Burgess <>,
        Stephen Hines <>,
        Pirama Arumuga Nainar <>,
        Manoj Gupta <>
Subject: Re: [PATCH 00/15] Add support for clang LTO

On Fri, Nov 3, 2017 at 11:29 AM, Mark Rutland <> wrote:
> On Fri, Nov 03, 2017 at 11:07:04AM -0700, Nick Desaulniers wrote:
>> On Fri, Nov 3, 2017 at 10:51 AM, Mark Rutland <> wrote:
>> > I had to create an aarch64-linux-gnu-clang wrapper, too. I'm not sure if
>> > there's build system help to avoid needing that?
>> Gah!  So a BIG difference with Clang vs GCC for cross compiling is
>> that Clang by default ships with all backends enabled, and uses a
>> `-target <triple>` CFLAG to determine the arch to cross compile for,
>> while GCC is configured at compile time to support one back end, IIUC.
> Yup.
> I initally tried passing CC=clang\ --target=aarch64-linux-gnu
> ... but since that conflicts with CROSS_COMPILE, you then have to
> override AS, LD, OBJCOPY, etc, separately too.

make CC=clang CROSS_COMPILE=aarch64-linux-gnu-

I think you may need a trailing hyphen on your target as it gets
prefixed onto as and ld:


 348 # Make variables (CC, etc...)
 349 AS    = $(CROSS_COMPILE)as
 350 LD    = $(CROSS_COMPILE)ld

Powered by blists - more mailing lists