Yes, well I probably installed libfreetype myself, as part of the
source installs. I know very little about these internals, so I did
nothing "on purpose." It's disconcerting that the X11 update
overwrote things in this way. Luckily, it appears there are no other
side effects. The fix was possible because of good error reporting
Thanks for your comments.
At 7:53 AM -0800 11/22/06, Christopher Barker wrote:
>Tony Mannucci wrote:
>>If you saw my previous post about upgrading to XDarwin 1.1.3, and
>>breaking matplotlib, the following seems to work:
>>Soft-linking to libfreetype.6.3.8.dylib rather than
>>libfreetype.6.3.dylib (see below, copied from previous email).
>That's interesting. I don't have a 6.3.8, only 6.3 (and 6, linked to
>6.3). I did just install the latest Apple X11 update.
>Also, in the past, MPL has been know not to work with Apple's X11
>libfreetype. I wonder if you had installed 6.3.8 yourself. That
>would have explained it, in that usually if you install, for
>instance, 6.3.8, there would be a link from 6.3 to 6.3.8, which may
>have been what you linked to originally. Then, if Apple provided a
>new 6.3 with their X11, it overwrote yours.
>I do note that your 6.3.8 is MUCH larger than 6.3, which is a bit curious.
>Anyway, most of us end up linking MPL statically against a
>self-installed libfreetype, just for these reasons.
>Christopher Barker, Ph.D.
>Emergency Response Division
>NOAA/NOS/OR&R (206) 526-6959 voice
>7600 Sand Point Way NE (206) 526-6329 fax
>Seattle, WA 98115 (206) 526-6317 main reception
Supervisor, Ionospheric and Atmospheric Remote Sensing Group
Mail-Stop 138-308, Tel > (818) 354-1699
Jet Propulsion Laboratory, Fax > (818) 393-5115
California Institute of Technology, Email > Tony.Mannucci@...
4800 Oak Grove Drive, http://genesis.jpl.nasa.gov
Pasadena, CA 91109