[Fink-users] a hint regarding missing dylib files

[Mitchell L Model]

This is unofficial advice from an extensive user of fink but one who 
hasn't really figured out the whole package configuration and 
dependency mechanism.  It may only apply after previous failed 
attempts to install packages that install libraries or it may 
actually be a problem with the installation mechanism.

I have found that several times when a build stopped because it 
couldn't find a dylib, if I went to the directory where it was 
looking (usually /sw/lib) I find a symbolic link to an earlier 
version of the library than the one now installed.  Somehow the new 
library got installed without the symbolic link getting updated. 
Actually there are usually (always?) two symbolic links to be 
updated: one with no version number and one with just the first 
number of the version.  The situation is easily fixed by deleting the 
two symbolic links and relinking them to the current version of the 
library.  For instance, the most recent case I encountered was a 
failure to find libesd.dylib.  In /sw/lib there were the following 
files:

        libesd.0.2.35.dylib
        libesd.0.dylib -> libesd.0.2.32.dylib
        libesd.a
        libesd.dylib -> libesd.0.2.32.dylib
        libesd.la
Deleting the two symbolic links and relinking them to 
libesd.0.2.35.dylib fixed the problem.  I don't know if this is 
something that installation scripts or processes are supposed to 
handle or just some aberration caused by my relentless hacking, but 
it's happened several times.

-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
_______________________________________________
Fink-users mailing list
Fink-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-users