New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
os x -- 10.6 -- generated the matplotlib font cache crashes sage #7022
Comments
This comment has been minimized.
This comment has been minimized.
comment:2
The spkg is here:
This supersedes what is at #6994. The attached package only patches Matplotlib on OS X 10.6 by changing one line to use |
comment:3
Doctesting reveals that just using FONTCONFIG is not enough, e.g., any saving to pdf still breaks. Here is the problem narrowed down more:
ft2font.so is a C extension in matplotlib. |
comment:4
above it should be
|
comment:5
How about
|
comment:7
I found yet another issue (X11 must be in the PATH), but this spkg fixes that issue too: http://wstein.org/home/wstein/patches/matplotlib-0.99.1.p1.spkg |
comment:8
OK, even this doesn't fix the problem on all machines. E.g., on bsd.math.washington.edu it does not fix the problem. |
comment:9
Comment -- upgrading freetype doesn't fix the problems at all. Also, upgrading freetype is itself broken, and the only workaround that I found that worked was to alias "rm" to be "rm -f" -- then freetype built and installed fine. |
comment:11
This spkg fixes the problems on all my test systems: http://sage.math.washington.edu/home/wstein/patches/matplotlib-0.99.1.p2.spkg All it does is take the plane vanilla matplotlib-0.99.1.spkg spkg and add a little script that simply rebuilds f2font.so again using exactly the same command lines used by distutils to build that extension. That's it. For some reason -- probably involving environment variables (?) -- this fixes the problem. I consider this a temporary 1-sage release solution until the matplotlib developers (or me) come up with a real fix. |
comment:12
By the way, here is a simple test that things are working:
|
comment:13
Looks good to me. Everything worked for me on bsd. |
Merged: Sage 4.1.2.rc0 |
Author: William Stein |
comment:14
Merged |
Reviewer: Mike Hansen |
comment:15
I'm still getting a crash with lines like these:
I made a related comment at #7095 because I didn't know about this ticket. Also, as opposed to this ticket, #7095 is still open, so further discussion should continue there (or on a new ticket?). |
comment:16
The matplotlib problem may be in its spkg file: it says
But with my computer, "uname -r" returns "10.2.0", not "10.0.0". How do you modify a shell script like this to make it work for a range of version numbers? (We don't just want "10.0.0" or "10.2.0", I'm guessing.) |
This is a huge problem and total blocker:
Ideas for solution:
(1) track down exactly where the problem happens in the matplotlib/freetype(?) code and fix it.
(2) Just ship the font cache with Sage until this gets resolved upstream
A working version of the fontcache is here:
http://wstein.org/home/wstein/tmp/fontList.cache
Component: graphics
Author: William Stein
Reviewer: Mike Hansen
Merged: Sage 4.1.2.rc0
Issue created by migration from https://trac.sagemath.org/ticket/7022
The text was updated successfully, but these errors were encountered: