install.command fails in update_dyld_shared_cache
WebKit for OS X Leopard
Status: Beta
Brought to you by:
internetzel
update_dyld_shared_cache as called at the end of the install.command fails on a PowerMac G4 under Mac OS X 10.5.8 because of an unresolved symbol; therefore /var/db/dyld/dyld_shared_cache_ppc will be deleted !
update_dyld_shared_cache failed: could not resolve _class_getInstanceMethod from /System/Library/PrivateFrameworks/DataDetectors.framework/Versions/A/DataDetectors in /System/Library/PrivateFrameworks/DataDetectors.framework/Versions/A/DataDetectors
Does this still happen after restarting and as the first thing running the install.command again?
Yes, install.command (from 600.5.17_2-Leopard-PowerPC) still fails when run right after a reboot. The uninstall.command works, i.e. update_dyld_shared_cache will recreate /var/db/dyld/dyld_shared_cache_ppc from the 10.5 frameworks.
The install.command from 537.78.2_4-(Snow)Leopard does work. I couldn't test 600.7.2-Leopard-PowerPC as the WebKit.app crashes after opening the main window - probably because of Glims judging from the system.log.
Could you please post the crash report?
I think it could help me in figuring out what's going wrong on your system.
Attached are an excerpt from the system.log and the two resulting crash reports.
Last edit: Fäustel 2015-04-26
The crash you get is caused by my the changes I introduced with [#86].
600.7.2_2 should have that fixed - please verify that it indeed doesn't crash anymore.
Related
Tickets:
#86The WebKit.app from 600.7.2_2 works again (but the install.command still fails as described).
update_dyld_shared_cache failing seems very strange to me - but that doesn't mean that the Leopard WebKit install has failed.
What happens if, after installing, restart and do "sudo update_dyld_shared_cache" in the Terminal?
I see the same behaviour on a machine other than my development machine.
The worst thing is that update_dyld_shared_cache will be called again by the system automatically after failing.
It's probably a bug in update_dyld_shared_cache. But you can work around it by removing (or commenting out) the line "/Applications/Mail.app/Contents/MacOS/Mail" from the file "/var/db/dyld/shared_region_roots/Applications.paths".
That way Apple Mail will launch a very little bit slower, but the system will be working fine again.
In order to comment the line out open the file using
"sudo pico /var/db/dyld/shared_region_roots/Applications.paths"
and add a "#" symbol as the first character in the line "/Applications/Mail.app/Contents/MacOS/Mail".
I'll soon release a version with an install/uninstall script that applies that workaround automatically.
600.7.2_3 should have this issue fixed.