macosx_deployment_target 10.5 does not result in "-mmacosx-version-min=10.5"

[wlipa (Bill Lipa)]

I set macosx_deployment_target 10.5 in macports.conf in order to build a version of ruby 1.9.2 for deployment to client machines that may be back on 10.5.

The binaries are linked against the 10.5 SDK correctly, and it almost works. The only problem is that the "-mmacosx-version-min=10.5" argument does not appear to be passed to the linker.

This results in binaries that contain linker sections that are unintelligible on 10.5. Normally this doesn't matter and they do run. However, they can't be ad-hoc codesigned due to the unrecognized sections, so the firewall won't recognize the binaries. Also, dynamic libraries such as native components of ruby gems can't be loaded.

[jmroot (Joshua Root)]

We do set MACOSX_DEPLOYMENT_TARGET which is equivalent. In any case, targeting anything other than the build machine is not a supported configuration.