From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: <linux-snps-arc@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jeff Moyer <jmoyer@redhat.com>,
"Alexey Brodkin" <Alexey.Brodkin@synopsys.com>
Subject: Re: Build failure in linux mainline when building arcv2 images
Date: Fri, 29 Jul 2016 15:46:30 -0700 [thread overview]
Message-ID: <1cc37edf-d48e-9b98-1bb6-f20e319cf12b@synopsys.com> (raw)
In-Reply-To: <20160729214854.GA21977@roeck-us.net>
On 07/29/2016 02:48 PM, Guenter Roeck wrote:
>>>> Yeah there's a 4.8.5 based one (referred to as GNU 2016.03) - will prebuilt
>>>> toolchain suffice or would you prefer building on your own. Prebuilt could be
>>>> found below.
>>>>
>>>> https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/releases/tag/arc-2016.03
>>>>
>>>>
>>>> For building on your own, Alexey can point to upstream buildroot which enabled
>>>> 2016.03 tools.
>>>>
>>>
>>> Unfortunately, I get the same error when using "arc-linux-gcc.br_real (Buildroot
>>> 2016.05) 4.8.5".
>>
>> Weird - I don't see this when building mainline of now using prebuilt 2016.03
>> tools on github . I'm building axs103_smp_defconfig.
>>
> What exactly is prebuilt 2016.03 based on ?
GNU 2016.03 based tools - but not built with BR, but with our internal scripts
(toolchain repo on github) - although it doesn't really matter,
> The arc tree on github only has an
> arc-2016.02 branch. I tried it, but it reports the same error. I also tried
> abrodkin-arc-2016.03, but it doesn't build for me.
I think github buildroot repo for ARC is kind of stale - Alexey would know more.
>> What exact buildroot commit did u use to build your tools BTW - I can try and
>> replicate that here !
>>
> I used buildroot 2016.05.
So I'm looking at upstream buildroot but something is weird is happening - friday
woes maybe.
What you want is
2016-05-19 09439560b9f9 toolchain: bump ARC tools to arc-2016.03 release
which seems to be present in released 2016.05, but when I checkout 2016.05 tag (or
aa6fd11feebff) that patch is not there !
Sorry we would have to defer this to next week or when Alexey takes a look.
-Vineet
next prev parent reply other threads:[~2016-07-29 22:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 3:23 Guenter Roeck
2016-07-29 5:20 ` Vineet Gupta
2016-07-29 13:43 ` Guenter Roeck
2016-07-29 20:03 ` Vineet Gupta
2016-07-29 21:48 ` Guenter Roeck
2016-07-29 22:46 ` Vineet Gupta [this message]
2016-07-30 4:27 ` Guenter Roeck
2016-08-01 9:53 ` Alexey Brodkin
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=1cc37edf-d48e-9b98-1bb6-f20e319cf12b@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=linux@roeck-us.net \
/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
all inboxes | Powered by JetHome®