[30032] trunk/base/src/port1.0/portconfigure.tcl

[Kevin Ballard]

That's what I'm saying. Using the 10.4u SDK is causing an error where  
ld can't find -lcrt1.10.5.o, which exists on 10.5 and in the 10.5 SDK  
but not on the 10.4u SDK. I don't know why it's looking for - 
lcrt1.10.5.o instead of just -lcrt1.o (which exists on 10.4u), but  
unless you can figure that out, this is the best solution. And this  
shouldn't actually affect compatibility of universal binaries unless a  
dependent library's library id changes.

On Oct 18, 2007, at 3:51 PM, Ryan Schmidt wrote:

> On Oct 18, 2007, at 14:20, source_changes at macosforge.org wrote:
>
>> Revision: 30032
>>         http://trac.macosforge.org/projects/macports/changeset/30032
>> Author:   eridius at macports.org
>> Date:     2007-10-18 12:20:11 -0700 (Thu, 18 Oct 2007)
>>
>> Log Message:
>> -----------
>> Allow universal configure-based builds to work on Leopard
>>
>> Modified Paths:
>> --------------
>>   trunk/base/src/port1.0/portconfigure.tcl
>>
>> Modified: trunk/base/src/port1.0/portconfigure.tcl
>> ===================================================================
>> --- trunk/base/src/port1.0/portconfigure.tcl	2007-10-18 19:17:41  
>> UTC (rev 30031)
>> +++ trunk/base/src/port1.0/portconfigure.tcl	2007-10-18 19:20:11  
>> UTC (rev 30032)
>> @@ -68,11 +68,16 @@
>> default configure.macosx_deployment_target	{}
>>
>> # Universal options & default values.
>> +if {[file exists /Developer/SDKs/MacOSX10.5.sdk]} {
>> +    set sysroot "/Developer/SDKs/MacOSX10.5.sdk"
>> +} else {
>> +    set sysroot "/Developer/SDKs/MacOSX10.4u.sdk"
>> +}
>> options configure.universal_args		configure.universal_cflags  
>> configure.universal_cppflags configure.universal_cxxflags  
>> configure.universal_ldflags configure.universal_env
>> default configure.universal_args		--disable-dependency-tracking
>> -default configure.universal_cflags		{"-isysroot /Developer/SDKs/ 
>> MacOSX10.4u.sdk -arch i386 -arch ppc"}
>> +default configure.universal_cflags		{"-isysroot $sysroot -arch  
>> i386 -arch ppc"}
>> default configure.universal_cppflags	{}
>> -default configure.universal_cxxflags	{"-isysroot /Developer/SDKs/ 
>> MacOSX10.4u.sdk -arch i386 -arch ppc"}
>> +default configure.universal_cxxflags	{"-isysroot $sysroot -arch  
>> i386 -arch ppc"}
>> default configure.universal_ldflags		{"-arch i386 -arch ppc"}
>>
>> # Select a distinct compiler (C, C preprocessor, C++)
>
> Shouldn't we continue to use the 10.4 universal SDK, even on 10.5,  
> to make the most-compatible universal binaries possible? Or are you  
> saying that using the 10.4 universal SDK does not work on 10.5? That  
> would surprise me.
>

-- 
Kevin Ballard
http://kevin.sb.org
eridius at macports.org
http://www.tildesoft.com