Even if you have Fink's freetype2 installed, nothing will link to it until it is told to do so explicitly. Its compile-time interface is hidden in /sw/lib/freetype2/{bin,include,lib} which normally is not seen by the preprocessor/compiler/linker.
Fink's freetype2 is only there because a few packages specifically need a more recent version than the one that comes with Apple's X11. None of these packages has anything to do with nicotine, I think.
Nicotine's relation to libfreetype is via the pygtk python module, that is the pygtk2-py23 package, AFAICT. And that one shouldn't link to Fink's libfreetype at all. So for me it is still a mystery where Fink's freetype should come into the picture. From what you are telling, I think one can infer that your pygtk module must have been built while a different libfreetype.6.dylib was present than what you have now.
If compatibility means what it says, you might get away with the symlink hack, but it is bad style, because the headers will not match the library.
I definitely agree its bad style. But the fact is, I get a bus error when the symlink points to Apple's freetype library and it works when it points to Fink's. And libfreetype.6.dylib was definitely pointing to the X11R6 libraries when I built pygtk, so I agree this is all somewhat mysterious. I will try restoring the symlinks and doing a rebuild of pygtk-py23 and see if that resolves the problem.
------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
