[Adium-devl] Fwd: CrashLog from Beta15RC3

[David Smith]

	I wonder if it's because it was built on Intel? (CB's machine). All  
previous b15 release candidates were built on my PPC machine.

						David

On Nov 8, 2006, at 5:44 PM, Evan Schoenberg wrote:

>
> On Nov 8, 2006, at 7:40 PM, David Smith wrote:
>
>>> Nov  8 19:06:17 Shangra-La /Applications/Adium.app/Contents/MacOS/
>>> Adium: objc: Both /Applications/Adium.app/Contents/MacOS/Adium and /
>>> Applications/Adium.app/Contents/MacOS/../Frameworks/Adium.framework/
>>> Versions/A/Adium have implementations of class KNShelfSplitView.
>>>
>>> Nov  8 19:06:17 Shangra-La /Applications/Adium.app/Contents/MacOS/
>>> Adium: objc: Using implementation from /Applications/Adium.app/
>>> Contents/MacOS/../Frameworks/Adium.framework/Versions/A/Adium.
>>>
> Fixed this warning-not-error part in [18164].
>
>>>
>>> dyld: /Applications/Adium.app/Contents/MacOS/Adium Undefined  
>>> symbols:
>>>
>>> AIUtilities undefined reference to ___stderrp expected to be
>>> defined in /usr/lib/libSystem.B.dylib
> [evands:Mukluk] [20:29:45] [Wed Nov 08] [/Developer/SDKs/ 
> MacOSX10.3.9.sdk/usr/lib]
> => nm libSystem.B.dylib  | grep stderrp
> <no output>
>
> [evands:Mukluk] [20:29:02] [Wed Nov 08] [/usr/lib]
> => nm libSystem.B.dylib  | grep stderrp
>          U ___stderrp
>          U ___stderrp
>          U ___stderrp
> a0001b90 D ___stderrp
>
> It's indeed legitimately a symbol not in 10.3.
>
> In Adium 0.8x, we were compiling like so:
> GCC_VERSION_i386 = 4.0
> GCC_VERSION_ppc = 3.3
> MACOSX_DEPLOYMENT_TARGET_i386 = 10.4
> MACOSX_DEPLOYMENT_TARGET_ppc = 10.2
> SDKROOT_i386 = /Developer/SDKs/MacOSX10.4u.sdk
>
> In Adium 1.0 at present, we compile like so:
> GCC_VERSION = 4.0
> MACOSX_DEPLOYMENT_TARGET_i386 = 10.4
> MACOSX_DEPLOYMENT_TARGET_ppc = 10.3
> SDKROOT_i386 = /Developer/SDKs/MacOSX10.4u.sdk
>
> So the GCC version is 4.0 across the board instead of 3.3 for the  
> ppc part.  I don't think that changed between 1.0b14 and now,  
> though... could someone do an svn update -r and see if it did?  (as  
> far as I can tell, AIUtilities is compiling the same as Adium  
> proper... so I'm not sure why the link error is reported in  
> AIUtilities, in any case).
>
> -Evan