> On Oct 14, 2015, at 09:32, Jarkko Hietaniemi <[email protected]> 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.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
