[Bug libstdc++/53838] _GLIBCXX_DEBUG and empty ostringstream

2015-04-02 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53838 --- Comment #8 from Jonathan Wakely --- i.e. do you have the exact commands to build a gcc that shows the problem? So it can be reproduced from a clean source tarball, without external dependencies.

[Bug libstdc++/53838] _GLIBCXX_DEBUG and empty ostringstream

2015-04-02 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53838 --- Comment #7 from Jonathan Wakely --- One of those bugs is apparently not present in 4.2 or later, are you sure it's the same? Do you have a reproducible testcase to show the bug, not just "use macports, it breaks"? or only links to other repo

[Bug libstdc++/53838] _GLIBCXX_DEBUG and empty ostringstream

2015-04-02 Thread tom at kera dot name
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53838 Tomalak Geret'kal changed: What|Removed |Added CC||tom at kera dot name --- Comment #6

[Bug libstdc++/53838] _GLIBCXX_DEBUG and empty ostringstream

2012-07-19 Thread redi at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53838 --- Comment #5 from Jonathan Wakely 2012-07-19 13:36:42 UTC --- (In reply to comment #4) > What course of action would you recommend? I don't understand what the comments in the macports trac mean, but as far as I'm concerned there's nothing for

[Bug libstdc++/53838] _GLIBCXX_DEBUG and empty ostringstream

2012-07-19 Thread akim.demaille at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53838 --- Comment #4 from Akim Demaille 2012-07-19 13:16:23 UTC --- Hi People, I have therefore reported this to MacPorts, see http://trac.macports.org/ticket/35070 . The outcome is that (i) with --enable-fully-dynamic-string fails to build on MacPor

[Bug libstdc++/53838] _GLIBCXX_DEBUG and empty ostringstream

2012-07-03 Thread redi at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53838 --- Comment #3 from Jonathan Wakely 2012-07-03 14:48:38 UTC --- Andrew, I'm not actually sure about that, see https://trac.macports.org/ticket/22234 But in any case, it's a problem with MacPorts' GCC package not FSF's GCC.

[Bug libstdc++/53838] _GLIBCXX_DEBUG and empty ostringstream

2012-07-03 Thread pinskia at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53838 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|

[Bug libstdc++/53838] _GLIBCXX_DEBUG and empty ostringstream

2012-07-03 Thread redi at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53838 --- Comment #1 from Jonathan Wakely 2012-07-03 11:52:17 UTC --- This is not a GCC bug, please report it to MacPorts not here. At a guess I'd say you're linking to the system libstdc++.so not the one from your mp builds, and the mp builds do not