|
From: Rita <rmo...@gm...> - 2013-08-06 12:39:44
|
Yes, I mean a self-built package. When linking I think setupext.py is using /usr/lib and /usr/local/lib first, instead it should use PKG_CONFIG_PATH and then /usr/lib and then /usr/local/lib. Basically, the ordering or linking matters. I hope that helps. This isnt a big deal but just though I put out the solution. On Mon, Aug 5, 2013 at 10:29 AM, Michael Droettboom <md...@st...> wrote: > On 08/03/2013 07:50 AM, Rita wrote: > > Same problem in Linux also. Here is what I did to fix it: Remove the > freetype/fontconfig rpm from my local install (yum remove) and then place > the proper PKG_CONFIG_PATH to point to my remote freetype/fontconfig. > > > By remote, you mean self-built, rather than from a package? > > > The problem is there is a bug with setupext.py. We ought to prepend > PKG_CONFIG_PATH in the gcc compile statement. I hope this helps. > > > Can you elaborate? The setupext.py just calls whatever pkg-config is > first on the PATH, which should then in turn obey PKG_CONFIG_PATH. If the > user needs a custom PKG_CONFIG_PATH, it is generally the resposibility of > the user to set it correctly -- and matplotlib's build system should (and > does) use it. Or maybe I'm just misunderstanding what you're suggesting. > > Cheers, > Mike > > > > > > > > On Fri, Aug 2, 2013 at 6:53 AM, Andrew Jaffe <a.h...@gm...> wrote: > >> Hi, >> >> >> On 01/08/2013 19:06, Michael Droettboom wrote: >> > On behalf of a veritable army of super coders, I'm pleased to announce >> > the release of matplotlib 1.3.0. >> >> Two issues on OSX 10.8.4. I had been previously using the dmg installer. >> Lacking that, I tried easy-install and pip install, both of which gave >> me the following problems: >> >> - I needed to set CC=clang >> - When attempting to load matplotlib, I got the following error: >> >> >> /Volumes/Data/Users/jaffe/Library/Python/2.7/lib/python/site-packages/matplotlib/font_manager.py >> in <module>() >> 51 import matplotlib >> 52 from matplotlib import afm >> ---> 53 from matplotlib import ft2font >> 54 from matplotlib import rcParams, get_cachedir >> 55 from matplotlib.cbook import is_string_like >> >> ImportError: >> >> dlopen(/Volumes/Data/Users/jaffe/Library/Python/2.7/lib/python/site-packages/matplotlib/ft2font.so, >> 2): Symbol not found: _FT_Attach_File >> Referenced from: >> >> /Volumes/Data/Users/jaffe/Library/Python/2.7/lib/python/site-packages/matplotlib/ft2font.so >> Expected in: flat namespace >> in >> >> /Volumes/Data/Users/jaffe/Library/Python/2.7/lib/python/site-packages/matplotlib/ft2font.so >> >> >> This is a freetype problem, probably an incompatible version somewhere. >> Ideas? >> >> Andrew >> >> >> >> >> ------------------------------------------------------------------------------ >> Get your SQL database under version control now! >> Version control is standard for application code, but databases havent >> caught up. So what steps can you take to put your SQL databases under >> version control? Why should you start doing it? Read more to find out. >> >> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk >> _______________________________________________ >> Matplotlib-users mailing list >> Mat...@li... >> https://lists.sourceforge.net/lists/listinfo/matplotlib-users >> > > > > -- > --- Get your facts first, then you can distort them as you please.-- > > > ------------------------------------------------------------------------------ > Get your SQL database under version control now! > Version control is standard for application code, but databases havent > caught up. So what steps can you take to put your SQL databases under > version control? Why should you start doing it? Read more to find out.http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk > > > > _______________________________________________ > Matplotlib-users mailing lis...@li...://lists.sourceforge.net/lists/listinfo/matplotlib-users > > > > > ------------------------------------------------------------------------------ > Get your SQL database under version control now! > Version control is standard for application code, but databases havent > caught up. So what steps can you take to put your SQL databases under > version control? Why should you start doing it? Read more to find out. > http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users > > -- --- Get your facts first, then you can distort them as you please.-- |