[Buildroot] AVR32 toolchain build failure

[Thomas De Schampheleire]

On Fri, Aug 9, 2013 at 9:16 AM, Simon Dawson <spdawson at gmail.com> wrote:
> Hi Thomas,
>
> On 8 August 2013 21:09, Thomas De Schampheleire
> <patrickdepinguin+buildroot at gmail.com> wrote:
>> So you are saying that if I upgrade my host gcc (the native one) to
>> 4.6, that the cross AVR32 gcc will build successfully, and not suffer
>> from the relocation truncation messages?
>
> I believe so, yes.

I can now also confirm that setting HOSTCC and HOSTCXX explicitly to
gcc-4.6 and g++-4.8, is the key to getting C++ support to build for
AVR32.

One approach to guard against such problems is to check this in
dependencies.sh/mk: if AVR32 is selected with C++ toolchain support,
and the host gcc is newer than 4.6 (or maybe newer-or-equal-than
4.7.0; not sure where the problem was introduced), then we bail out
and ask the user to either disable C++ support, set their host
compiler to an older version, or select another architecture (kidding
about that last one, of course).

Another solution, but way overkill IMO, is to build a host-gcc 4.6
first if no suitable gcc can be found (in the avr32 + C++ support
case).

What do you all think?