Will binaries built in 10.6 still run in 10.5?

Ryan Schmidt ryandesign at macports.org
Sun Oct 3 23:44:51 PDT 2010

On Oct 3, 2010, at 22:52, Nikos Chantziaras wrote:
> I tried this and added "macosx_deployment_target 10.5".  However, the wrong compilers are used then.  Instead of:
>  /usr/libexec/gcc/i686-apple-darwin10/4.2.1
>  /usr/libexec/gcc/ppc-apple-darwin10/4.2.1
> for Intel and PowerPC respectively, these are used:
>  /usr/libexec/gcc/i686-apple-darwin10/4.0.1
>  /usr/libexec/gcc/ppc-apple-darwin10/4.0.1
> Is there a way to change that and use 4.2.1?  AFAIK, 4.0.1 is only for OS X older than 10.5.  When "macosx_deployment_target 10.5" is set, the compiler should be 4.2.1.

Apple gcc 4.2.1 became available on Leopard, but was not the default until Snow Leopard. In Leopard and Tiger, the default compiler is Apple gcc 4.0.1. There isn't a switch in MacPorts to tell it to globally use a different compiler; individual ports decide what compiler they should use (which is usually the default one on the given version of Mac OS X, unless there's a specific reason why that won't work).

More information about the macports-users mailing list