Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Silence the fix_prebinding log error System
If your system.log is filled with messages such as (running ls as installed by fink)...
Jan 5 18:27:24 x /usr/libexec/fix_prebinding: /sw/bin/ls could not be launched prebound.
Jan 5 18:27:24 x /usr/libexec/fix_prebinding: /sw/bin/ls couldn't be prebound in the past, and probably can't be prebound now.
Jan 5 18:27:24 x /usr/libexec/fix_prebinding: 2003-01-05 18:27:24 +0100: prebinding for ls done.
... then you might want to consider setting the environmental variable DYLD_NO_FIX_PREBINDING (any value will do), as described in the manual page for dyld(1).

Put export DYLD_NO_FIX_PREBINDING=true in .bash_profile, or setenv DYLD_NO_FIX_PREBINDING true in .login, depending on what shell and setup you use.

The downside is, of course, that no binaries launched from the shell will be prebound, but until there's a better way to silence fix_prebinding, I prefer being able to read my system.log.
    •    
  • Currently 1.50 / 5
  • 1
  • 2
  • 3
  • 4
  • 5
  (2 votes cast)
 
[8,790 views]  

Silence the fix_prebinding log error | 5 comments | Create New Account
Click here to return to the 'Silence the fix_prebinding log error' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Prebinding?
Authored by: signals on Jan 09, '03 11:17:32AM

I seem to be asking lots of potentially dumb questions today, but...

What exactly is "prebinding?" My system.log has quite a few of these errors, and I've never been able to figure out what they mean. Now a fix is posted with the following warning:

"The downside is, of course, that no binaries launched from the shell will be prebound"

But not knowing what "prebinding" means, I'm not sure what to make of the warning. I really feel like I've not been paying enough attention after reading the hints today. I usually understand them just fine ;-)

-Signals



[ Reply to This | # ]
Prebinding?
Authored by: robg on Jan 09, '03 11:40:15AM

Prebinding can speed application launching ... it basically lets the system associate required libraries with each particular app.

-rob.



[ Reply to This | # ]
Prebinding?
Authored by: kd7cyb on Jul 13, '03 06:54:24PM

Go to Apple's page below for a good description:

http://developer.apple.com/documentation/ReleaseNotes/Prebinding.html



[ Reply to This | # ]
Use environment.plist to stop completely
Authored by: sardu_mac on Jan 09, '03 01:45:50PM
Mac OS X will read environment variables from ~/.MacOSX/environment.plist if it exists.


The format is the same as all .plist files, so you can use Property List Editor if you have Developer Tools installed.
Sample file below.



<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>DYLD_NO_FIX_PREBINDING</key>
<string></string>
<key>LC_ALL</key>
<string>C</string>
</dict>
</plist>



The LC_ALL I have in there is for perl 5.8.0, ignore it (or leave it in if you're running 5.8.0).

[ Reply to This | # ]
Use grep to read system.log
Authored by: thatch on Jan 09, '03 08:10:26PM

Although the system with Jaguar does seem to waste an inordinate amount of time doing the fix_prebinding dance, it doesn't really take up that much CPU cycles or memory. And it does seem like all the binaries from fink stuff is what can't be prebound, over and over again, all day long. Maybe in the future, the system will make note of those files which can't be prebound and not keep on trying them forever.

In the mean time, if you don't want to read your system.log with all that nonsense, use grep to filter out what you want, if you have an idea of what that is. Globbing with grep will help too.



[ Reply to This | # ]