<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><br><div><div>On 2018-04-10, at 11:47 AM, Rainer Müller wrote:</div><blockquote type="cite"><div><blockquote type="cite"><font class="Apple-style-span" color="#000000"><br></font></blockquote><blockquote type="cite">I don't want to release 2.4.3 with the libstdc++ ABI issue unanswered. I believe it will cause problems.<br></blockquote><br>Then we should revert this change for 2.4.3 and we have one more reason<br>to go for a 2.4.4 release.<br><br>Rainer<br></div></blockquote></div><br><div><br></div><div>I would have like to set libgcc to ABI4 mode, at least on PPC, to fix this forever, but Jeremy felt this was undesirable. Perhaps we might still consider doing that, though, at least on PPC.</div><div><br></div><div>Two other easy options: </div><div><br></div><div>1. add the required *ABI=0 flag by default to all cxx builds on PPC. This would be completely fine I believe. More desirable.</div><div><br></div><div><br></div><div>2. wait for builds to fail to link (they will, on 10.6 to 10.8 and PPC if the linking doesn't work, as we have all seen) then add the cxx11 PortGroup as we do now when we see this failure. Less desirable.</div><div><br></div><div><br></div><div><br></div><div>or revert it if you want, and we can do it some day in the future.</div><div><br></div><div>Best,</div><div><br></div><div>ken</div><div><br></div><div><br></div><div>Ken</div></body></html>