<br><br>El martes, 26 de abril de 2016, Ryan Schmidt <<a href="mailto:ryandesign@macports.org">ryandesign@macports.org</a>> escribió:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
On Apr 26, 2016, at 4:31 PM, César wrote:<br>
<br>
> After installing GCC 5.3.0 in Tiger, I realized that if I invoke ld from the command line, I'm actually invoking /opt/local/bin/ld. I realize that GCC 5.3.0 may require a newer linker than the default in Xcode for Tiger, but even if I select GCC 4.0.1 as the current compiler, ld still invokes /opt/local/bin/ld.<br>
><br>
> Is there any way I can select /usr/bin/ld as the default linker when I'm not using GCC 5.3.0?<br>
<br>
Tiger is so old that all the compilers included in its Xcode are too old and buggy for MacPorts to use. So MacPorts installs and uses the apple-gcc42 port and uses that compiler to build all ports on Tiger (unless a port specifies otherwise). The apple-gcc42 port requires the ld64 port, which is where /opt/local/bin/ld comes from. You should probably use /opt/local/bin/ld and the gcc installed by the apple-gcc42 port, even for things you compile on Tiger outside of MacPorts, rather than the ancient versions that come in Tiger's Xcode.<br>
</blockquote><div><br></div><div>Yes, that's reasonable, but I like the flexibility of being able to use the Tiger's Xcode tools versions if I need it for testing or for comparisons. Isn't it possible to revert to the Xcode linker with the same ease I can select the active GCC version?</div><div><br></div><div>Thanks,</div><div><br></div><div>César</div><div><br></div><div><br></div>