Chris,
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 w
One more note:
Christopher Barker wrote:
> I wonder if you had installed 6.3.8 yourself.
If you did, it really should have been put in /usr/local/ somewhere --
then you wouldn't risk conflicts with Apple's version.
-Chris
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
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
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
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).
Thanks for that Apple!
-Tony
> >>> import numpy as N
N
