Snow Leopard upgrade: Aperture does not start

30.August 2009 – 14:26

Directly after installing Snow Leopard, Aperture crashed at every launch attempt. The relevant part of the crash report is:

Dyld Error Message:

Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager

Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture

Reason: image not found

It turned out the upgrade silently nuked a bunch of optional Apple frameworks in /Library/Frameworks/, on my machine the PluginManager.framework (required by Aperture) and a bunch of WebObjects related libraries. Restoring /Library/Frameworks/PluginManager.framework with TimeMachine fixed the crash.

Snow Leopard upgrade: 3rd party log-folders in /var/logs cleanup

30.August 2009 – 14:17

One year back when I upgraded my iMac from Tiger to Leopard, the pimped-personal-websharing apache I used for svn access failed big time to launch because the svn libraries were incompatible to Leopards more recent build.

Last years fix was to get rid of most of the third party stuff and simply create an additional subversion-server-only apache configuration.

Upgrading to Snow Leopard gave me a unresponsive machine with rapidly increasing process ids again. A quick look in the console revealed tons of messages like:”org.apache.httpd.svn_instance[3761] (2)No such file or directory: httpd: could not open error log file /var/log/apache4svn/error.log”

So fortunately instead of a binary incompatibility the system upgrade simply “cleaned” the /var/log directory and with it my /var/log/apache4svn directory, and recreating the directory brought apache up again.

Pimp-My-Xcode-SDK

24.April 2008 – 22:34

Recently I sent a tiny bugfixed build to a customer – just to get a phone call some minutes later it doesn’t even launch on his test machine. What happened? A quick glance at Console.app revealed that dyld complains his 10.4.8 (unpatched) machine is missing the CoreVideo framework. 

Odd enough, nothing besides a handful of lines was changed from the last, working build. The only change was that in the meantime Leopard arrived and I produced the new version with Xcode 3. Rebooting on Tiger and rebuilding with Xcode 2.4 produced an working build. Applying QuickTime and the OS X 10.4.11 updates allows the new build to launch – but is a management nightmare for the 100 target MacMinis that run without any network or administrative access.

Today I was asked to provide another build, now equipped with a post-Leopard MacBook that does not like my Tiger installation DVD any more. Time for the real fix. The shortcut – simply copying the Xcode 2.4 SDK version to the 2.5 installation – fails as gcc won’t resolve stdarg.h etc. due to the new Developer Tools relocatable folder structure.

After some more investigation it turned out QuartzCore.framework differs in the SDKs. With the following steps it is possible to get a backward compatible SDK:

  • create a copy of the Xcode 3  MacOSX10.4u.sdk – I called mine Fixed_MacOSX10.4u.sdk
  • replace the QuartzCore.framework with the version from the Xcode 2.4.1 installation
  • open SDKSettings.plist in your pimped SDK copy
  • change the name value to something unique – I used Mac OS X 10.4 (Universal,Compatible) 
  • in projects that need a build backward compatible to 10.4.0, change the SDK to Mac OS X 10.4 (Universal,Compatible)  instead of the regular SDK.

 

blog setup…

1.February 2008 – 11:49

So here is yet another shiny new blog.  I’m not sure where the blogging journey will go to and if I keep coming up with content. Probably there will be some software development and photography related articles.