All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Cavallari <Nicolas.Cavallari@green-communications.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 6/7] libsigrok: enable building C++ bindings
Date: Mon, 23 Feb 2015 12:23:17 +0100	[thread overview]
Message-ID: <54EB0DA5.1040406@green-communications.fr> (raw)
In-Reply-To: <20150220193035.7f90d46f@free-electrons.com>

On 20/02/2015 19:30, Thomas Petazzoni wrote:
> Moreover, you make this apparently depend on the selected C library.
> But isn't C++11 support purely a gcc problem ?

This software uses std::stod, which suffers from the same problem as
std::to_string with uclibc : GCC currently requires a lot more than
necessary to enable it.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58393

So it's just a matter of updating buildroot's
850-libstdcxx-uclibc-c99.patch. Again.

  reply	other threads:[~2015-02-23 11:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20 12:28 [Buildroot] [PATCH 0/7] sigrok fixes and pulseview package Bartosz Golaszewski
2015-02-20 12:28 ` [Buildroot] [PATCH 1/7] libsigrok: remove --disable-udev from CONF_OPTS Bartosz Golaszewski
2015-02-20 12:28 ` [Buildroot] [PATCH 2/7] libserialport: drop untrue statement from Config.in help Bartosz Golaszewski
2015-02-20 12:28 ` [Buildroot] [PATCH 3/7] libsigrok: don't select libserialport in Config.in Bartosz Golaszewski
2015-02-20 12:28 ` [Buildroot] [PATCH 4/7] autoconf-archive: new package Bartosz Golaszewski
2015-02-20 18:28   ` Thomas Petazzoni
2015-02-20 12:29 ` [Buildroot] [PATCH 5/7] libsigrok: bump git commit tag Bartosz Golaszewski
2015-02-20 12:29 ` [Buildroot] [PATCH 6/7] libsigrok: enable building C++ bindings Bartosz Golaszewski
2015-02-20 18:30   ` Thomas Petazzoni
2015-02-23 11:23     ` Nicolas Cavallari [this message]
2015-02-20 12:29 ` [Buildroot] [PATCH 7/7] pulseview: new package Bartosz Golaszewski
2015-02-20 18:15 ` [Buildroot] [PATCH 0/7] sigrok fixes and pulseview package Thomas Petazzoni

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=54EB0DA5.1040406@green-communications.fr \
    --to=nicolas.cavallari@green-communications.fr \
    --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.