[MacPorts] #49273: clang-mp-3.7 and MACOSX_DEPLOYMENT_TARGET=10.3 do not mix

[Jeremy Huddleston Sequoia]

> On Oct 14, 2015, at 09:32, Jarkko Hietaniemi <jhi at iki.fi> wrote:
> 
>> 
>>  ld64 is the linker.  You can use variants to choose what the default
>>  linker is.  +ld64_latest should be preferred in most cases, but there is
>>  lag after Apple releases Xcode versions before we can update ld64-latest
>>  to the newest version, so ld64-xcode may be newer during that period.
> 
> FWIW, I now tested the "sudo port install ld64 +ld64_xcode" recipe, and verified that it works fine.  I may add this to the Darwin notes of
> Perl, since I'd never heard of this, and I do build Perl on Darwin quite often.
> 
>>  If you really want to support all systems, setting it 10.4 should suffice.
>> 
>>  If you want to cover the 99.9% case, setting it to 10.6 should suffice.
>> 
>>  10.8 and 10.9 as minimum requirements are starting to be come more popular
>>  as well, but the reasons for that probably don't impact perl too much.
>>  You may, however, want to consider 10.7 because I brought in a good
>>  portion of SUSv4 updates, some Libc API extensions from FreeBSD, NetBSD
>>  RBTrees, and other various Libc niceties.
> 
> Then there is the option of not specifying the target at all?  Or is that a bad idea?  (It means using the oslevel of the build system as the target, right?)
> 
> What exactly happens if something compiled with, say, 10.8 target, is run in, say, 10.7?  Will it run slow?  Or run wrong?  Or just not run?

If you build with a deployment target that is newer than the OS you run the built executable on, it won't run.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4118 bytes
Desc: not available
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20151014/7ae372f3/attachment-0001.p7s>