Martin Spacek wrote:
Michael,
Sorry for the delay. Adding:
#include limits
to the top of path.cpp in rev5055 helps - most of the errors have
disappeared, but I still get this:
running build_ext
building 'matplotlib._path' extension
C:\bin\Microsoft Visual Studio .NET
The rcParam svg.embed_chars controls this behavior. I would assume it
is set differently on your Windows and Mac boxes.
When it is True, rather than outputting text blocks, it embeds the
characters as outlines. This means that the fonts do not have to be
installed just to view the SVG
Hi Mike,
Thanks for the tip. I tried it, but I get the following message:
Bad key svg.embed_chars on line 294 in
/Users/kghose/.matplotlib/matplotlibrc.
You probably need to get an updated matplotlibrc file from
http://matplotlib.sf.net/matplotlibrc or from the matplotlib source
distribution
Sorry. I mistyped. It's svg.embed_char_paths
Cheers,
Mike
Kaushik Ghose wrote:
Hi Mike,
Thanks for the tip. I tried it, but I get the following message:
Bad key svg.embed_chars on line 294 in
/Users/kghose/.matplotlib/matplotlibrc.
You probably need to get an updated matplotlibrc file
Thanks, that worked!
Small note, the example matplotlibrc file on the website
(http://matplotlib.sourceforge.net/matplotlibrc) as well as the one in the most
recent mac OS egg has svg.embed_chars.
Thanks
-Kaushik
Michael Droettboom wrote:
Sorry. I mistyped. It's svg.embed_char_paths
Yes. I'll fix that. Thanks.
Kaushik Ghose wrote:
Thanks, that worked!
Small note, the example matplotlibrc file on the website
(http://matplotlib.sourceforge.net/matplotlibrc) as well as the one in
the most recent mac OS egg has svg.embed_chars.
Thanks
-Kaushik
Michael Droettboom
Kaushik
If the source of your distribution is not an issue, I would recommend using
matplotlib-0.91.2-py2.5-macosx-10.3-fat.egg
Thanks, and I have had success with various packaged versions,
but I want to be able to update and compile the svn version
at will, just like I can under linux.
The internal compiler error is something we are all running into right now.
The only known fix is to run the build with the gcc flag -Os instead of
-O3. You should be able to do this by setting the environment during your
build:
CFLAGS=-Os python setup.py build
On Mon, Apr 21, 2008 at 8:24 PM,
On Tue, Apr 22, 2008 at 5:28 PM, Charlie Moad [EMAIL PROTECTED] wrote:
The internal compiler error is something we are all running into right now.
The only known fix is to run the build with the gcc flag -Os instead of
-O3. You should be able to do this by setting the environment during your
round() is defined in math.h so adding
#include math.h
to the top of the file might fix it.
Thanks for your patience!
Mike
Just tried the latest rev where you've added math.h to the top, still get the
same error. Apparently round isn't defined in math.h:
10 matches
Mail list logo
