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]

Message-ID: <20170219082028.GC2379@lianli.shorne-pla.net>
Date:   Sun, 19 Feb 2017 17:20:28 +0900
From:   Stafford Horne <shorne@...il.com>
To:     fengguang.wu@...el.com
Cc:     Openrisc <openrisc@...ts.librecores.org>,
        linux-kernel@...r.kernel.org, Guenter Roeck <linux@...ck-us.net>
Subject: Re: Crosstool/kbuild-all toolchain updates

Ping?

On Wed, Feb 01, 2017 at 07:44:38AM +0900, Stafford Horne wrote:
> Hi Fengguang/All,
> 
> I am working as the OpenRISC linux kernel maintainer.  Currently in
> linux-next our patches are causing kbuild test robot to fail.
> 
> This is because the patches are taking advantage of 2 'new' (2 year old)
> instrucions (l.swa/l.lwa) and the build robots, as far as I can tell,
> use the 'make.cross' [0] build script from lkp-tests.git.  These point
> to the crosstools [1] toolchains maintained by Tony.
> 
> I sent a mail to Tony who maintains the crosstools but I didn't get a
> reply and it seems he is not longer working on them [1].
> 
> I think our options are:
> 
>   1. Update 'make.cross' to point somewhere else for openrisc
>   2. Update and maintain crosstools
> 
> For 1. its trvial but, maybe not the best solution.
> 
> For 2. I created new crosstool builds for openrisc [3]. The way the
> crosstools are maintained is via a patches.tar file and it seem a custom
> buildall script.  I dont see the source for that custom script anywhere.
> 
> I am thinking I could help to update and 'opensource' the crosstool
> build scripts to make it easier for everyone to update toolchains by
> sending patches.
> 
> But, I would need access to crosstool on kernel.org and an OK from
> everyone.
> 
> Any opinions? Questions?
> 
> -Stafford
> 
> [0] https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/tree/sbin/make.cross
> [1] https://www.kernel.org/pub/tools/crosstool/
> [2] https://marc.info/?l=linux-kernel&m=146406282809809&w=1
> [3] http://shorne.noip.me/crosstool/files/

Any thought on this?

I create a patch to do 1. Update make.cross to point to openrisc
binaries. I hope you found it on the list:

  https://lkml.org/lkml/2017/2/19/12

-Stafford