From: Peter Zijlstra <peterz@infradead.org>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: Cupertino Miranda <Cupertino.Miranda@synopsys.com>,
Ingo Molnar <mingo@kernel.org>,
Guenter Roeck <linux@roeck-us.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
Michael Ellerman <michael@ellerman.id.au>,
Tony Breeds <tony@bakeyournoodle.com>
Subject: Re: cross compilers [was build failure of sorts]
Date: Tue, 21 Jun 2016 11:45:37 +0200 [thread overview]
Message-ID: <20160621094537.GP30909@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <C2D7FE5348E1B147BCA15975FBA230750106944BC0@us01wembx1.internal.synopsys.com>
On Tue, Jun 21, 2016 at 09:28:56AM +0000, Vineet Gupta wrote:
> On Tuesday 21 June 2016 01:13 PM, Peter Zijlstra wrote:
> > 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.
>
> Thx for the off-list log. The issue is gdb not yet upstream. So it seems we will
> have to wait for things on upstreaming to settle down before I can formally update
> segher's scripts to support ARC.
Ah, lemme add --disable-gdb to the binutils build.
Should arc-*-* list gdb in their noconfigdirs like many other archs do
too?
next prev parent reply other threads:[~2016-06-21 9:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 14:36 Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()' Guenter Roeck
2016-06-17 14:39 ` Peter Zijlstra
2016-06-17 14:41 ` Peter Zijlstra
2016-06-17 14:52 ` Guenter Roeck
2016-06-17 15:00 ` Vineet Gupta
2016-06-17 15:22 ` Peter Zijlstra
2016-06-17 15:36 ` Vineet Gupta
2016-06-17 16:04 ` Ingo Molnar
2016-06-17 16:13 ` Peter Zijlstra
2016-06-17 20:22 ` Vineet Gupta
2016-06-17 21:27 ` Guenter Roeck
2016-06-18 7:05 ` Peter Zijlstra
2016-06-18 10:17 ` cross compilers [was build failure of sorts] Peter Zijlstra
2016-06-21 5:29 ` Vineet Gupta
2016-06-21 7:43 ` Peter Zijlstra
2016-06-21 9:28 ` Vineet Gupta
2016-06-21 9:45 ` Peter Zijlstra [this message]
2016-06-21 9:59 ` Vineet Gupta
2016-06-21 10:04 ` Peter Zijlstra
2016-06-22 10:04 ` Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()' Vineet Gupta
2016-06-22 10:24 ` Peter Zijlstra
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=20160621094537.GP30909@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Cupertino.Miranda@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=michael@ellerman.id.au \
--cc=mingo@kernel.org \
--cc=tony@bakeyournoodle.com \
/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