Hi Tom,
the fix seems to be renaming a couple files in /usr/local/lib
Yes, it seems that the latest FontForge installer pkg has some problems in dynamic libraries. For example, it installs libgdraw in a strange way:
<pre>
$ cd /usr/local/lib
$ ls libgdraw*dylib
lrwxr-xr-x 1 root wheel 20 7 4 23:18 libgdraw.1.dylib@ -> libgdraw.2.0.0.dylib
-rwxr-xr-x 1 root wheel 2043000 6 29 12:26 libgdraw.2.0.0.dylib*
lrwxr-xr-x 1 root wheel 20 7 4 23:18 libgdraw.dylib@ -> libgdraw.2.0.0.dylib</pre>
The symbolic link from 1.dylib to 2.0.0.dylib is just nonsense; it should be a link from 2.dylib to 2.0.0.dylib.
So instead of renaming the real library 2.0.0.dylib to 2.dylib, you may rename the link 1.dylib to 2.dylib. If you have already renamed 2.0.0.dylib to 2.dylib, then
<pre>
cd /usr/local/lib
mv libgdraw.2.dylib libgdraw.2.0.0.dylib # back to the original name
mv libgdraw.1.dylib libgdraw.2.dylib # correct the symlink name</pre>
The same applies to libgunicode.
PS
This problem has been already reported in Font Forge dev mailing list
http://sourceforge.net/mailarchive/forum.php?threadname=9CFB3F5B-AB28-4685-A87D-5C05C8F63812%40caltech.edu&forumname=fontforge-devel
http://sourceforge.net/mailarchive/forum.php?threadname=DD9C25C6-B53D-41D7-A71B-FFAE58F59A2B%40caltech.edu&forumname=fontforge-devel
PowerMacG4, PowerBookG4, iMac(C2D) Mac OS X (10.4.9)
Message was edited by: Jun T.
