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
matplotlib-1.3.1 does not install #16002
Comments
comment:1
Hum...
When you say upgrading, you mean from sage 5.13? Then yes definitely. Or was this upgraded in place numerous times?
is not in this location in my sage install but in the freetype2 sub-folder. If you one in the this sub folder consider removing the one in local/include and try again. |
comment:2
OK, I'm going to reinstall. I'm upgrading sage from 6.2beta4, but you're right in that this has been gathering cruft for ages and I should probably rebuild it from scratch. |
comment:3
Certainly, but there may be something to fix in the upgrade process. The file I pointed out shouldn't be there and we may be able to do something about it. So I would very much like you to check there is another version in local/include/freetype2 and then remove the one in local/include and try again. |
comment:4
Not sure what you mean...
EDIT: Got it! Yes, it seems to build now. |
comment:5
You have both "local/include/ft2build.h" and "local/include/freetype2/ft2build.h". The first one shouldn't be there and is probably old cruft. I want you to remove it and retry to install matplotlib 1.3.1. |
comment:6
Didn't see your update. OK this now becomes a ticket to remove that files when you upgrade freetype. |
comment:7
Thanks, Francois, for acting on this (strictly speaking non-)issue! |
Author: John Palmieri |
Commit: |
Branch: u/jhpalmieri/ft2build |
comment:8
How about this as a fix: after freetype has been successfully installed, remove the old file ft2build.h? New commits:
|
New commits:
|
Changed branch from u/jhpalmieri/ft2build to u/jhpalmieri/freetype |
comment:10
I would do it before the install but in that case it is just a matter of taste. Can you bump the spkg because we want the thing to rebuild to remove the file before anyone gets hurt again. |
Changed branch from u/jhpalmieri/freetype to u/jhpalmieri/ft |
comment:11
Okay, I bumped the version number -- good point. By the way, I'm deleting the file after the install because if the installation fails, I don't want to break the old version. New commits:
|
comment:12
good point. positive that. |
comment:13
reviewer names, kids ;) |
Reviewer: François Bissey |
Changed branch from u/jhpalmieri/ft to |
comment:15
Replying to @vbraun:
yeah I am bad at those :) |
Changed commit from |
comment:16
Ah, kiwifb - is this likely the problem I am having at on my ancient Mac? Though you are right that I'm not upgrading... and the message was
I can open a ticket for this otherwise, but eventually I'll try this version just on some very strange off-chance... |
comment:17
I am fairly certain it isn't. It is very difficult to know what happened without going through the configuration step by step. I think it found an incorrect version of freetype but I am at a lose as to how it happens for you and not anyone else. You know the small revealing detail. |
comment:18
Replying to @kcrisman:
freetype changed it's header files recently breaking many downstream packages. For example, the patch to gimp is here and shows clearly what changed. |
comment:19
Thanks, ppurka. So are you saying that this is what happened? See #16047, where I think I have a lot more evidence you are right. |
This breaks the upgrade to 6.2.beta5.
Logfile: https://www.dropbox.com/s/wmfrp13mnm148i1/matplotlib-1.3.1.log
System is Ubuntu 12.04.4 LTS in a virtualbox on a 64bit machine. Would upgrading help?
CC: @jasongrout @vbraun @kiwifb @jhpalmieri
Component: packages: standard
Keywords: install, package, matplotlib
Author: John Palmieri
Branch:
bbffb65
Reviewer: François Bissey
Issue created by migration from https://trac.sagemath.org/ticket/16002
The text was updated successfully, but these errors were encountered: