linux-kernel - Re: cross compilers [was build failure of sorts]

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: <20160621074307.GK30154@twins.programming.kicks-ass.net>
Date:	Tue, 21 Jun 2016 09:43:07 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Vineet Gupta <Vineet.Gupta1@...opsys.com>
Cc:	Cupertino Miranda <Cupertino.Miranda@...opsys.com>,
	Ingo Molnar <mingo@...nel.org>,
	Guenter Roeck <linux@...ck-us.net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-snps-arc@...ts.infradead.org" 
	<linux-snps-arc@...ts.infradead.org>,
	Michael Ellerman <michael@...erman.id.au>,
	Tony Breeds <tony@...eyournoodle.com>
Subject: Re: cross compilers [was build failure of sorts]

On Tue, Jun 21, 2016 at 05:29:28AM +0000, Vineet Gupta wrote:
> On Saturday 18 June 2016 03:47 PM, Peter Zijlstra wrote:
> > As you can see, arc doesn't even build upstream binutils :/
> > (binutils-2_26-branch as of today).
> 
> Hmm - we are still in fight w.r.t. upstreaming gcc fully (ARCv2 gcc support)
> although ARCompact has been there for some time. binutils upstream should work -
> I'll check why the buildall stuff fails.

I can run that build again and send you the resulting log files in
private.

> We currently have our tools on github but presume that won't work for you due to
> non canonical location / version !

Right, I have binutils and gcc git, I update those, checkout the latest
'stable' branches and run buildall.

And I do this maybe once or twice a year, mostly when I really need a
newer compiler -- this time I needed GCC-6 (I have 6.1.1 now) in order
to play with new inline asm bits.

Anything that fails, doesn't get compile coverage on my machines
(although the 0day built bot does catch some of the fallout).