<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Sep 8, 2014 at 1:24 PM, Lawrence Velázquez <span dir="ltr"><<a href="mailto:larryv@macports.org" target="_blank">larryv@macports.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":2wz" class="a3s" style="overflow:hidden">That's true, but it's a red herring. If our libstdc++ wasn't broken, ports would not have to avoid it.<br>
<br>
Our actual problem is that none of the g++ compilers we distribute are viable because they don't use the system's C++ runtime. If we successfully move the whole operation over to libc++, they'd still be broken.<br></div></blockquote></div><div class="gmail_extra"><br></div>I think you have misunderstood the problem completely, unless you intend to conclude that everything before Mavericks must never even attempt to support C++11.<br><div><br></div>-- <br><div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net" target="_blank">ballbery@sinenomine.net</a></div><div>unix, openafs, kerberos, infrastructure, xmonad <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div>
</div></div>