Opened 8 years ago

Closed 7 years ago

Last modified 7 years ago

#16002 closed defect (fixed)

matplotlib-1.3.1 does not install

Reported by: darij Owned by:
Priority: critical Milestone: sage-6.2
Component: packages: standard Keywords: install, package, matplotlib
Cc: jason, vbraun, fbissey, jhpalmieri Merged in:
Authors: John Palmieri Reviewers: François Bissey
Report Upstream: N/A Work issues:
Branch: bbffb65 (Commits, GitHub, GitLab) Commit:
Dependencies: Stopgaps:

Status badges

Description

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?

Change History (19)

comment:1 Changed 8 years ago by fbissey

Hum...

building 'matplotlib.ft2font' extension
creating build/temp.linux-i686-2.7
creating build/temp.linux-i686-2.7/src
creating build/temp.linux-i686-2.7/CXX
gcc -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_matplotlib_ft2font_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -I/home/darij/gitsage/sage-5.13.beta1/local/lib/python2.7/site-packages/numpy/core/include -I/home/darij/gitsage/sage-5.13.beta1/local/include -I. -I/home/darij/gitsage/sage-5.13.beta1/local/include/freetype2 -I/home/darij/gitsage/sage-5.13.beta1/local/include/python2.7 -c src/ft2font.cpp -o build/temp.linux-i686-2.7/src/ft2font.o
In file included from src/ft2font.h:16:0,
                 from src/ft2font.cpp:3:
/home/darij/gitsage/sage-5.13.beta1/local/include/ft2build.h
:56:38: fatal error: freetype/config/ftheader.h: No such file or directory
compilation terminated.
error: command 'gcc' failed with exit status 1

When you say upgrading, you mean from sage 5.13? Then yes definitely. Or was this upgraded in place numerous times? It looks to me like there is cruft in your install:

/home/darij/gitsage/sage-5.13.beta1/local/include/ft2build.h

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 Changed 8 years ago by darij

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 Changed 8 years ago by fbissey

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 Changed 8 years ago by darij

Not sure what you mean...

darij@travis-virtualbox:~/gitsage/sage-5.13.beta1/local/include/freetype2$ ls
config      ftautoh.h   ftbzip2.h     ftcid.h     ftglyph.h  ftincrem.h  ftmac.h     ftotval.h   ftsizes.h   ftsystem.h  ftwinfnt.h  tttables.h
freetype.h  ftbbox.h    ftcache.h     fterrdef.h  ftgxval.h  ftlcdfil.h  ftmm.h      ftoutln.h   ftsnames.h  fttrigon.h  ftxf86.h    tttags.h
ft2build.h  ftbdf.h     ftcffdrv.h    fterrors.h  ftgzip.h   ftlist.h    ftmodapi.h  ftpfr.h     ftstroke.h  ftttdrv.h   t1tables.h  ttunpat.h
ftadvanc.h  ftbitmap.h  ftchapters.h  ftgasp.h    ftimage.h  ftlzw.h     ftmoderr.h  ftrender.h  ftsynth.h   fttypes.h   ttnameid.h

EDIT: Got it! Yes, it seems to build now.

Last edited 8 years ago by darij (previous) (diff)

comment:5 Changed 8 years ago by fbissey

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 Changed 8 years ago by fbissey

Didn't see your update. OK this now becomes a ticket to remove that files when you upgrade freetype.

comment:7 Changed 8 years ago by darij

Thanks, Francois, for acting on this (strictly speaking non-)issue!

comment:8 Changed 7 years ago by jhpalmieri

  • Authors set to John Palmieri
  • Branch set to u/jhpalmieri/ft2build
  • Commit set to ab0970abeea7a9aec5439051a62b26427dc3d456
  • Status changed from new to needs_review

How about this as a fix: after freetype has been successfully installed, remove the old file ft2build.h?


New commits:

ab0970aRemove old version of ft2build.h

comment:9 Changed 7 years ago by jhpalmieri

  • Branch changed from u/jhpalmieri/ft2build to u/jhpalmieri/freetype
  • Commit changed from ab0970abeea7a9aec5439051a62b26427dc3d456 to 73a128af28cec5507648bf3e65a5886c3b5c0da8

New commits:

73a128aRemove old version of ft2build.h

comment:10 Changed 7 years ago by fbissey

  • Status changed from needs_review to needs_work

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.

comment:11 Changed 7 years ago by jhpalmieri

  • Branch changed from u/jhpalmieri/freetype to u/jhpalmieri/ft
  • Commit changed from 73a128af28cec5507648bf3e65a5886c3b5c0da8 to bbffb655f0fe7c4050b0972210a4804d613fd31d
  • Status changed from needs_work to needs_review

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:

bbffb65Remove old version of ft2build.h
Last edited 7 years ago by jhpalmieri (previous) (diff)

comment:12 Changed 7 years ago by fbissey

  • Status changed from needs_review to positive_review

good point. positive that.

comment:13 follow-up: Changed 7 years ago by vbraun

  • Reviewers set to François Bissey

reviewer names, kids ;)

comment:14 Changed 7 years ago by vbraun

  • Branch changed from u/jhpalmieri/ft to bbffb655f0fe7c4050b0972210a4804d613fd31d
  • Resolution set to fixed
  • Status changed from positive_review to closed

comment:15 in reply to: ↑ 13 Changed 7 years ago by fbissey

  • Commit bbffb655f0fe7c4050b0972210a4804d613fd31d deleted

Replying to vbraun:

reviewer names, kids ;)

yeah I am bad at those :)

comment:16 follow-up: Changed 7 years ago by kcrisman

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*

              freetype: no  [The C/C++ header for freetype2 (ft2build.h)
                        could not be found.  You may need to install the
                        development package.]

I can open a ticket for this otherwise, but eventually I'll try this version just on some very strange off-chance...

Last edited 7 years ago by kcrisman (previous) (diff)

comment:17 Changed 7 years ago by fbissey

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 in reply to: ↑ 16 Changed 7 years ago by ppurka

Replying to kcrisman:

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*

              freetype: no  [The C/C++ header for freetype2 (ft2build.h)
                        could not be found.  You may need to install the
                        development package.]

I can open a ticket for this otherwise, but eventually I'll try this version just on some very strange off-chance...

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 Changed 7 years ago by kcrisman

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.

Note: See TracTickets for help on using tickets.