From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gustavo Zacarias Date: Fri, 09 Aug 2013 19:34:36 -0300 Subject: [Buildroot] AVR32 toolchain build failure In-Reply-To: <20130809222906.16bb49ce@skate> References: <20130807172033.564940d1@skate> <20130808000726.66ab7194@skate> <20130809222906.16bb49ce@skate> Message-ID: <52056E7C.4000804@zacarias.com.ar> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net On 08/09/2013 05:29 PM, Thomas Petazzoni wrote: > On Fri, 9 Aug 2013 13:12:51 +0200, Thomas De Schampheleire wrote: > >> 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). > > That's the only reasonable solution I believe. Not really, for me: gcc version 4.6.3 (Gentoo 4.6.3 p1.10, pie-0.5.2) Fails miserably on any situation, even the most bare (non c++/wchar/nls/ipv6/rpc) configuration. If it's the USE flags (pretty default), some gentoo patches to gcc or what else i don't know, but i can't get past gcc-initial (this being the current stable on the normal architectures). Regards.