From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 7250] New: Cannot build with -std=c++11
Date: Mon, 30 Jun 2014 21:04:12 +0000 (UTC) [thread overview]
Message-ID: <bug-7250-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=7250
Summary: Cannot build with -std=c++11
Product: buildroot
Version: 2014.05
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: tarka.t.otter at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 5468
--> https://bugs.busybox.net/attachment.cgi?id=5468
c++11 test case
After building a buildroot toolchain based on GCC 4.8.3, it does not seem
possible to build any packages that require C++11 support.
Attached is a simple test case that compiles fine on my host machine with GCC
4.8.2 with -std=c+11, but fails to compile using the cross toolchain with the
same flag.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2014-06-30 21:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 21:04 bugzilla at busybox.net [this message]
2014-06-30 21:05 ` [Buildroot] [Bug 7250] Cannot build with -std=c++11 bugzilla at busybox.net
2014-06-30 21:13 ` bugzilla at busybox.net
2014-06-30 21:52 ` bugzilla at busybox.net
2014-07-01 18:47 ` bugzilla at busybox.net
2014-07-07 21:34 ` bugzilla at busybox.net
2014-07-08 21:06 ` bugzilla at busybox.net
2014-07-09 17:50 ` bugzilla at busybox.net
2014-08-09 15:23 ` bugzilla at busybox.net
2014-08-09 15:49 ` bugzilla at busybox.net
2014-08-09 20:11 ` bugzilla at busybox.net
2014-08-13 17:52 ` bugzilla at busybox.net
2014-08-17 7:44 ` bugzilla at busybox.net
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=bug-7250-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox