From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] AVR32 toolchain build failure
Date: Fri, 9 Aug 2013 22:29:06 +0200 [thread overview]
Message-ID: <20130809222906.16bb49ce@skate> (raw)
In-Reply-To: <CAAXf6LX6XCAwSXWtHPxkc7Q2+-pFeaGyuNO0k4ZRH-MdA3U5MQ@mail.gmail.com>
Dear Thomas De Schampheleire,
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.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-08-09 20:29 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 12:01 [Buildroot] AVR32 toolchain build failure Thomas De Schampheleire
2013-08-05 12:29 ` Thomas De Schampheleire
2013-08-06 9:27 ` Alexander Lukichev
2013-08-06 9:39 ` Alexander Lukichev
2013-08-06 14:40 ` Thomas De Schampheleire
2013-08-06 15:03 ` Thomas De Schampheleire
2013-08-08 15:35 ` Alexander Lukichev
2013-08-06 17:54 ` Thomas Petazzoni
2013-08-06 19:33 ` Thomas De Schampheleire
2013-08-07 7:05 ` Thomas De Schampheleire
2013-08-07 15:20 ` Thomas Petazzoni
2013-08-07 16:01 ` Thomas De Schampheleire
2013-08-07 18:20 ` Thomas De Schampheleire
2013-08-07 22:07 ` Thomas Petazzoni
2013-08-08 5:55 ` Thomas De Schampheleire
2013-08-08 7:21 ` Simon Dawson
2013-08-08 8:03 ` Thomas Petazzoni
2013-08-08 10:56 ` Gustavo Zacarias
2013-08-08 16:18 ` Simon Dawson
2013-08-08 17:57 ` Gustavo Zacarias
2013-08-08 17:59 ` Thomas Petazzoni
2013-08-13 6:15 ` Arnout Vandecappelle
2013-08-08 8:12 ` Thomas De Schampheleire
2013-08-08 16:09 ` Simon Dawson
2013-08-08 17:34 ` Thomas De Schampheleire
2013-08-08 17:57 ` Thomas Petazzoni
2013-08-08 18:05 ` Thomas De Schampheleire
2013-08-08 19:42 ` Simon Dawson
2013-08-08 20:09 ` Thomas De Schampheleire
2013-08-08 20:24 ` Thomas De Schampheleire
2013-08-08 22:22 ` Thiago A. Corrêa
2013-08-09 4:51 ` Alexander Lukichev
2013-08-09 7:16 ` Simon Dawson
2013-08-09 11:12 ` Thomas De Schampheleire
2013-08-09 20:29 ` Thomas Petazzoni [this message]
2013-08-09 22:34 ` Gustavo Zacarias
2013-08-08 7:29 ` Alexander Lukichev
2013-08-08 8:13 ` Thomas De Schampheleire
-- strict thread matches above, loose matches on Subject: below --
2013-11-13 21:36 Thomas Petazzoni
2013-11-14 8:53 ` Simon Dawson
2013-11-14 9:10 ` Thomas Petazzoni
2013-11-15 8:58 ` Simon Dawson
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=20130809222906.16bb49ce@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.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 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.