<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sat, Sep 20, 2014 at 7:43 PM, Ryan Schmidt <span dir="ltr"><<a href="mailto:ryandesign@macports.org" target="_blank">ryandesign@macports.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> Why does ld64 need the *-headers ports at all?<br>
<br>
</span>Good question. Jeremy?</blockquote></div><br>I expect it's common definitions for C++ exception handling/stack unwinding. ld64 needs it to generate the link time information needed to support it; the compilers possibly should use the same port but include their own currently, hence the conflict? Or, more likely, they're shared between ld64 and clang but gcc does its own thing and can't easily be fixed to use clang/llvm's.<br clear="all"><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>