Bookmark this site!

2007-07-17

dependent dylib is not prebound

Is your Mac sluggish and running slow?

Are your Office apps refusing to run?

Your automated prebinding updates may be failing.

Run the command
sudo update_prebinding -debug -root / -force
If you get the following error:

dyld: re-prebound: 0x90bee000 /usr/lib/libgcc_s.1.dylib
update_prebinding: error: dependent dylib is not prebound
update_prebinding: error 256 running update_prebinding_core
then edit the update-prebinding-paths file (this has the list of files to prebind: the one that fails is immediately after the last one to succeed)
sudo emacs /var/db/dyld/update-prebinding-paths.txt
Search for libgcc_s.1.dylib, and comment out the next line (by adding the #) so it reads
#/Applications/Utilities/Java/Java Web \ Start.app/Contents/Resources/Java/libmacjavaws.jnilib
Save the file, then try updating the prebindings again. For me, the next (and final) failure was after libjsound.jnilib. So I comment out the following line
#/System/Library/Frameworks/\
JavaVM.framework/Versions/1.3.1/Libraries/librealawt.jnilib
On the next try everything else went through. My Powerbook is much snappier.

It seems that you may need to reinstall Flash Player after doing this. Try the Adobe Shockwave and Flash player test to check. First uninstall previous versions. Shockwave will still only work if you run your browser under Rosetta. Flash is Universal

12 comments:

Peter said...

This happened to me after the most recent software update. The solution worked, thank you!

rberger said...

Thank you, thank you, thank you!!!!!

I wasted over 5 hours before I found your post that immediately solved my problem of not being able to start Quicken 2007 (and probably other Rosetta based apps if I had any).

newmac said...

Hi,

I tried what you said but as I'm a bit of a novice, I don't know how to save the update-prebinding-paths.txt after adding the #.

Please advise

Cheers

Newmac

Sam said...

This worked like a charm, thank you! I spent way too much time on this.

Michael Fourman said...

Hi newmac!

The short answer is C-x C-s

You should understand this once you've read the rest of this comment!

To get a tutorial, once Emacs is running hold the 'ctrl' key (control) and hit 'h'. Release the 'ctrl' key then hit 't'.

This will bring up an emacs tutorial.

In emacs-speak, this key sequence is written
C-h t

C-x C-s saves the text you are working on

C-x C-c quits emacs

If you're going to use emacs, you probably want to print a reference card.

sgorappa said...

Yes, It worked! Thank you! I was having trouble getting SilverKeeper to launch on my Intel mac after the QT 7.2 update. I spent all day trying to fix the problem and commenting out the two lines worked.

Anonymous said...

Thank you,

great help.
But what was the problem?
I assume this comes from the QuickTime 7.2 update.

Georg

rbfraven said...

Thanks very much for posting this! It solved my Word 2004 problem of using excessive CPU. The problem showed up after upgrading to 10.4.10, and applying updates QT 7.2, and Office 11.3.6 on my 500Mhz G4 Powerbook. No other app was affected. I found your solution referenced in a recent post to http://groups.google.com/group/microsoft.public.mac.office. In my case, the problem files were in the /usr/X11R6/lib directory. I spent a lot of time looking for a solution in the past couple of months. Would be very interesting to me to know what led to this non-obvious solution.

jarppe said...

I have tried to solve this for long time now, and tried many different solution proposals with no help. Finally I found your solution and it worked. Thank you very much!

-jarppe

Graham said...

You are a hero. Like others I have wasted hours on this problem, your solution seems to work perfectly (Microsoft Office is working again as is "Mac Label Expert" which presumably needs Rosetta).
My only change from your methodology was to use TextMate to edit the file as I can't manage emacs in the Terminal (other amateur meddlers may find TextMate a useful alternative to emacs)

Anonymous said...

Excellent! Many thanks for posting this, had cost me way too much time already.

Dave (a former student of yours, btw. Funny to find this blog just through googling for a solution)

Anonymous said...

Mac has a security problem in the linkage for going to the desktop & it is a serious one.