On Feb 3, 2005, at 20:07, Chris Barker wrote:
Bob Ippolito wrote:
You have three options:
- make sure the dylibs aren't sitting around in the same location as
the .a, and make sure the .a's path is preferred (you could make a
local dir, -L to it, symlink the archives in)
I'm going to give this a
Bob Ippolito wrote:
You have three options:
- make sure the dylibs aren't sitting around in the same location as the
.a, and make sure the .a's path is preferred (you could make a local
dir, -L to it, symlink the archives in)
I'm going to give this a try.
- change the setup.py relatively signific
On Feb 3, 2005, at 19:07, Chris Barker wrote:
I posted a note here the other day about a matplotlib binary. I've
discovered a problem with it. Apparently, it has linked against the
libfreetype in /usr/X11. That means it will work fine on a system with
Apple's X11 installed (like mine or the firs
Hi all,
I posted a note here the other day about a matplotlib binary. I've
discovered a problem with it. Apparently, it has linked against the
libfreetype in /usr/X11. That means it will work fine on a system with
Apple's X11 installed (like mine or the first system I tested it on).
So, the que
