configure fails - compiler help
Ken Cunningham
ken.cunningham.webuse at gmail.com
Fri Oct 26 04:43:16 UTC 2018
On 2018-10-18, at 4:54 PM, Riccardo Mottola wrote:
> Hi Ken
>
> Ken Cunningham wrote:
>> I assume you're on 10.6.8 or newer -- clang and ld are thinking you are building against something newer than 10.5, so looking for the usual link libraries on 10.6.8.
>
> no.. the fact is that I am building directly on 10.5, not on 10.6 using a 10.5 SDK!
>
> could this be caused by macport clang 3.9?
>
>>
>> But the 10.5 SDK doesn't have that -lcrt1.10.6.o
>>
>> So -- it should work if you set the deployment target to 10.5.
>>
>> Adding a flag like this
>>
>> -mmacosx-version-min=10.5
>
> It did help pass this specific configure test, but if you read above, it is incosistent with your explanation.
>
> I may add, that the 10.5 is the one that causes the crashy TFF builds :)
>
> Riccardo
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.
This is probably not ideal behaviour on 10.5, but nobody is going to change those defaults now. So passing in the flag is the answer.
Ken
More information about the macports-users
mailing list