ARCv2 testing exposure (Re: arc build failures in -next due to ARCv2 patch)

From: Vineet Gupta
Date: Mon Aug 31 2015 - 06:35:50 EST

Hi Guenter,

On Sunday 28 June 2015 08:46 PM, Vineet Gupta wrote:
> On Saturday 27 June 2015 07:46 PM, Guenter Roeck wrote:

>>> >> Thx for reporting the issue - I have pushed a fix (also attached) which shd cure
>>> >> it (don't have exactly similar oldish gcc at hand).
>> >
>> > Not that old, really, it just isn't configured for ARCv2. Question is if I need two
>> > separate compilers or if I can configure it to support both v1 and v2.
> The compiler itself can support both - however issue is multilib'ing / libgcc. The
> elf32 compiler is multilib'ed - but we've been using the uclibc compiler (with
> just the right toggles) to build the kernel as well (to avoid having to use 2
> toolchains for kernel / user etc).
> long story short - ATM, we need 2 different compilers to build legacy ARCompact,
> and newer ARCv2.

I was wondering about ARCv2 coverage in your build service. Do you have the needed
2nd toolchain for ARCv2 as well. If not can u add it please.

To build one, you could use upstream buildroot or the legacy scripts at


Or if you so prefer, we also have prebuilt toolchains in github releases.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at