<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 2017-04-18, at 8:54 AM, Mojca Miklavec wrote:</div><blockquote type="cite"><div><blockquote type="cite"><br></blockquote><blockquote type="cite">After coming across this issue one too many times for my own liking, and changing several dozen ports as you have done, I finally just patched clang to make it default to add -stdlib=lilbc++ by default on all systems, which solves this issue once and forever.<br></blockquote><br>That doesn't sound too bad :)<br></div></blockquote><blockquote type="cite"><div>I wonder if we should introduce a variant of the compiler to do just that :)<br></div></blockquote><div><br></div><div><br></div><div>I do find this helps a lot with the stdlib hiccups on older systems, and i plan to continue to use it, but I understand concerns about changing default behaviour of compilers. Jeremy has previously indicated privately to me that he wasn't too keen on the idea due to possible unexpected consequences of changing default behaviour, and this is a respectable point coming from the honcho himself.</div><div><br></div><div>As a counter argument, changing one compiler default to what is the current expected behaviour seems a lot easier than updating an uncertain number out of 21,000 ports, some of which (WxWidgets, for example) turn out to be rather messy to fix properly.</div><div><br></div><div>It would be quite easy to make it a variant if desired - just one patchfile to optionally add. I leave this up to the collective to decide.</div><div><br></div><blockquote type="cite"><div><font class="Apple-style-span" color="#000000"><br></font>You have just been nominated to fix this bug:<br> <a href="https://trac.macports.org/ticket/53634">https://trac.macports.org/ticket/53634</a><br>Thanks in advance :)<br></div></blockquote><div><br></div><div>:> I'll take a look.</div><br></div><div>Ken</div><br></body></html>