From: vgupta@synopsys.com (Vineet Gupta)
To: linux-snps-arc@lists.infradead.org
Subject: Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()'
Date: Fri, 17 Jun 2016 22:22:46 +0200 [thread overview]
Message-ID: <57645C16.9040300@synopsys.com> (raw)
In-Reply-To: <20160617160438.GA24148@gmail.com>
On Friday 17 June 2016 06:04 PM, Ingo Molnar wrote:
>> I've misplaced my arc compiler, but does this make it go again?
> There's no arc compiler on korg's cross-building directory.
Yeah, I'd requested that a few times...
However we do have ARC kernels building at atleast 2 places
1. Guenther's build service which sent this error report
2. kisskb build by Michale Ellerman
Although I don't know if it is possible to download cross tools from either of above.
@Peter, upstream buildroot allows you to build toolchain for ARC ! Trust me it
does build :-)
WARNING: multiple messages have this Message-ID (diff)
From: Vineet Gupta <vgupta@synopsys.com>
To: Ingo Molnar <mingo@kernel.org>, Peter Zijlstra <peterz@infradead.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-snps-arc@lists.infradead.org,
Michael Ellerman <michael@ellerman.id.au>,
Tony Breeds <tony@bakeyournoodle.com>
Subject: Re: Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()'
Date: Fri, 17 Jun 2016 22:22:46 +0200 [thread overview]
Message-ID: <57645C16.9040300@synopsys.com> (raw)
In-Reply-To: <20160617160438.GA24148@gmail.com>
On Friday 17 June 2016 06:04 PM, Ingo Molnar wrote:
>> I've misplaced my arc compiler, but does this make it go again?
> There's no arc compiler on korg's cross-building directory.
Yeah, I'd requested that a few times...
However we do have ARC kernels building at atleast 2 places
1. Guenther's build service which sent this error report
2. kisskb build by Michale Ellerman
Although I don't know if it is possible to download cross tools from either of above.
@Peter, upstream buildroot allows you to build toolchain for ARC ! Trust me it
does build :-)
next prev parent reply other threads:[~2016-06-17 20:22 UTC|newest]
Thread overview: 42+ 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:36 ` Guenter Roeck
2016-06-17 14:39 ` Peter Zijlstra
2016-06-17 14:39 ` Peter Zijlstra
2016-06-17 14:41 ` Peter Zijlstra
2016-06-17 14:41 ` Peter Zijlstra
2016-06-17 14:52 ` Guenter Roeck
2016-06-17 14:52 ` Guenter Roeck
2016-06-17 15:00 ` Vineet Gupta
2016-06-17 15:00 ` Vineet Gupta
2016-06-17 15:22 ` Peter Zijlstra
2016-06-17 15:22 ` Peter Zijlstra
2016-06-17 15:36 ` Vineet Gupta
2016-06-17 15:36 ` Vineet Gupta
2016-06-17 16:04 ` Ingo Molnar
2016-06-17 16:04 ` Ingo Molnar
2016-06-17 16:13 ` Peter Zijlstra
2016-06-17 16:13 ` Peter Zijlstra
2016-06-17 20:22 ` Vineet Gupta [this message]
2016-06-17 20:22 ` Vineet Gupta
2016-06-17 21:27 ` Guenter Roeck
2016-06-17 21:27 ` Guenter Roeck
2016-06-18 7:05 ` Peter Zijlstra
2016-06-18 7:05 ` Peter Zijlstra
2016-06-18 10:17 ` cross compilers [was build failure of sorts] Peter Zijlstra
2016-06-18 10:17 ` Peter Zijlstra
2016-06-21 5:29 ` Vineet Gupta
2016-06-21 5:29 ` Vineet Gupta
2016-06-21 7:43 ` Peter Zijlstra
2016-06-21 7:43 ` Peter Zijlstra
2016-06-21 9:28 ` Vineet Gupta
2016-06-21 9:28 ` Vineet Gupta
2016-06-21 9:45 ` Peter Zijlstra
2016-06-21 9:45 ` Peter Zijlstra
2016-06-21 9:59 ` Vineet Gupta
2016-06-21 9:59 ` Vineet Gupta
2016-06-21 10:04 ` Peter Zijlstra
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:04 ` Vineet Gupta
2016-06-22 10:24 ` Peter Zijlstra
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=57645C16.9040300@synopsys.com \
--to=vgupta@synopsys.com \
--cc=linux-snps-arc@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.