[Bug libstdc++/53838] _GLIBCXX_DEBUG and empty ostringstream
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53838 --- Comment #7 from Jonathan Wakely redi at gcc dot gnu.org --- 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 reports that show up for related search terms?
[Bug libstdc++/53838] _GLIBCXX_DEBUG and empty ostringstream
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53838 --- Comment #8 from Jonathan Wakely redi at gcc dot gnu.org --- 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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53838 Tomalak Geret'kal tom at kera dot name changed: What|Removed |Added CC||tom at kera dot name --- Comment #6 from Tomalak Geret'kal tom at kera dot name --- Not a GCC bug? Really? I beg to differ. - Bug 54173 - Bug 33021 - Bug 64504
[Bug libstdc++/53838] _GLIBCXX_DEBUG and empty ostringstream
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53838 --- Comment #4 from Akim Demaille akim.demaille at gmail dot com 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 MacPorts, and (ii), no, the linking is properly done with the MacPorts' version of stdlibc++: also when trying your example the resuling binary is linked to _our_ gcc's C++-lib So really, there seem to be something weird about this on OS X, as indeed is shown in other tickets. What course of action would you recommend?
[Bug libstdc++/53838] _GLIBCXX_DEBUG and empty ostringstream
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53838 --- Comment #5 from Jonathan Wakely redi at gcc dot gnu.org 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 us to do, it's an issue with the macports build, not GCC. If they want to report a different bug about --enable-fully-dynamic-string that's a separate issue and will be dealt with if it's reported properly.
[Bug libstdc++/53838] _GLIBCXX_DEBUG and empty ostringstream
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53838 --- Comment #1 from Jonathan Wakely redi at gcc dot gnu.org 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 use the same setting for --enable-fully-dynamic-string as the system libs.
[Bug libstdc++/53838] _GLIBCXX_DEBUG and empty ostringstream
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53838 Andrew Pinski pinskia at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||INVALID --- Comment #2 from Andrew Pinski pinskia at gcc dot gnu.org 2012-07-03 13:55:05 UTC --- Not a GCC bug as Mac OS X's installed libstdc++ is built with --enable-fully-dynamic-string while the mac ports one is not.
[Bug libstdc++/53838] _GLIBCXX_DEBUG and empty ostringstream
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53838 --- Comment #3 from Jonathan Wakely redi at gcc dot gnu.org 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.
