linux-kernel - Re: Crosstool/kbuild-all toolchain updates

lists.openwall.net		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 linux-cve-announce 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:   Sun, 19 Feb 2017 11:49:23 -0600
From:   Segher Boessenkool <segher@...nel.crashing.org>
To:     Fengguang Wu <fengguang.wu@...el.com>
Cc:     Stafford Horne <shorne@...il.com>,
        Openrisc <openrisc@...ts.librecores.org>,
        linux-kernel@...r.kernel.org, Guenter Roeck <linux@...ck-us.net>,
        Tony Breeds <tony@...eyournoodle.com>
Subject: Re: Crosstool/kbuild-all toolchain updates

Hi!

On Sun, Feb 19, 2017 at 09:26:37PM +0800, Fengguang Wu wrote:
> An uptodate crosstool and reasonable active maintainer would be very
> welcome. I'll sure be a heavy user. In the past year when crosstool is
> not updated to gcc-6, we've resorted to using debian packages for some
> ARCHs and building our own cross compliers for the other ARCHs. The
> latter are based on Segher's buildall tools (CCed). The private builds
> may work for us in short term, however is obvious not a satisfactory
> solution.

Buildall supports GCC only, and this is not likely to change.

The primary usecase for buildall is for my own GCC testing.  All patches
are welcome, but I'm not likely to apply them if they make it harder to
use the tools for what their goal is.  I'm certainly not going to apply
patches to other trees from the scripts, etc.

Buildall itself is still maintained.  It does not get very many updates
but that is because it is close to perfect ;-)

On the other hand I'll be happy to help wherever I can.  Just Cc: me on
whatever comes up.

Segher