configure fails - compiler help

Ryan Schmidt ryandesign at macports.org
Fri Oct 26 06:50:04 UTC 2018



On Oct 25, 2018, at 23:43, Ken Cunningham wrote:

> a little experimenting on 10.5 today shows this:
> 
> $ /usr/bin/ld
> ld warning: -arch not specified
> ld: no object files specified for inferred architecture i386
> 
> 
> $ /opt/local/bin/ld
> ld: warning: -arch not specified
> ld: warning: -macosx_version_min not specificed, assuming 10.6
> ld: no object files specified for inferred architecture i386
> 
> 
> 
> So - as you can see - MacPorts ld64 port on 10.5 will default to linking in 10.6 libraries if you don't specify otherwise.

That looks totally broken to me. I can't imagine why we would want that default. With every other tool we've run across, the default deployment target is 10.1 on Mac OS X 10.1 through 10.4, and equal to the OS version on 10.5 and later. That is what I would expect ld to do too.

We don't see this problem in MacPorts ports because we set the MACOSX_DEPLOYMENT_TARGET environment variable.

I wonder why the linker uses the flag "-macosx_version_min" when the compiler uses the flag "-mmacosx-version-min".

> This is probably not ideal behaviour on 10.5, but nobody is going to change those defaults now.

Why don't we?




More information about the macports-users mailing list