Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 229599 - dev-python/matplotlib-0.98.0 - src/_wxagg.cpp:53:22: error: wx/image.h: No such file or directory
Summary: dev-python/matplotlib-0.98.0 - src/_wxagg.cpp:53:22: error: wx/image.h: No su...
Status: RESOLVED OBSOLETE
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Development (show other bugs)
Hardware: x86 Linux
: Normal normal (vote)
Assignee: Python Gentoo Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-26 13:36 UTC by afrodocter
Modified: 2015-03-20 12:37 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge log (matplotlib_bug_report.txt,82.11 KB, text/plain)
2008-06-30 12:46 UTC, afrodocter
Details

Note You need to log in before you can comment on or make changes to this bug.
Description afrodocter 2008-06-26 13:36:38 UTC
both matplotlib-0.91.2 and 0.98 both fail to build with error of 

src/_wxagg.cpp:144: error: expected initializer before '*' token
error: command 'i686-pc-linux-gnu-gcc' failed with exit status 1


Reproducible: Always

Steps to Reproduce:
1.emerge matplotlib 
2.
3.

Actual Results:  
both matplotlib-0.91.2 and 0.98 both fail to build with error of 

src/_wxagg.cpp:144: error: expected initializer before '*' token
error: command 'i686-pc-linux-gnu-gcc' failed with exit status 1


Expected Results:  
builds correctly
Comment 1 Carsten Lohrke (RETIRED) gentoo-dev 2008-06-26 16:30:29 UTC
- please attach error output, external links may be down or not reachable for other reasons.
Comment 2 afrodocter 2008-06-30 12:46:01 UTC
Created attachment 158955 [details]
emerge log
Comment 3 afrodocter 2008-06-30 13:19:33 UTC
setting wxagg= False in setup.cfg solves the compile issue, which might be obvious from the error.
Comment 4 Sébastien Fabbro (RETIRED) gentoo-dev 2008-07-02 16:04:24 UTC
Hi,

It works fine here. Could you tell which USE flags are enbicabled for matplotlib, and could you try with wxpython-2.8*

Thanks
Comment 5 Sébastien Fabbro (RETIRED) gentoo-dev 2008-08-28 13:41:05 UTC
> both matplotlib-0.91.2 and 0.98 both fail to build with error of 
> 
> src/_wxagg.cpp:144: error: expected initializer before '*' token
> error: command 'i686-pc-linux-gnu-gcc' failed with exit status 1


No news for more than 6 weeks.
Is it reproducible with matplotlib-0.91.4 or matplotlib-0.98.3? 
Thanks
Comment 6 Philippe Veber 2008-09-24 09:50:03 UTC
I had a very similar problem, and it could be solved just by re-emerging wxpython.  Unfortunately I've got no clue on the initial problem. 

HTH,
  Philippe.

Comment 7 xalan 2008-10-08 19:49:20 UTC
> I had a very similar problem, and it could be solved just by re-emerging
> wxpython.  Unfortunately I've got no clue on the initial problem. 
> 
> HTH,
>   Philippe.
> 

The problem is wxwidgets has multislot install. For eg. on my system there is 2.6 and 2.8 I was getting the same error as OP. Looking around I found that compiler was not able to find proper wx headers. eselect wxwidgets told me that no version was selected. I selected latest version as default, remerged matplotlib 0.98.3 and build was smooth. I did not have to remerge wxpython.

Catch: I don't know if eselecting a default wxwidget install will have side effects on other packages.

This info needs to be propagated to package maintainers of matplotlib, and may be wxpython and wxwidgets, if not already done
Comment 8 Sébastien Fabbro (RETIRED) gentoo-dev 2008-10-10 08:47:16 UTC
(In reply to comment #7)

> The problem is wxwidgets has multislot install.

I forced wxpython:2.8 in the matplotlib ebuilds. I tried with multiple wxwidgets/wxpython installed and it worked. I'm closing this one now, re-open if you still encounter problems.
Thanks all.
Comment 9 Benda Xu gentoo-dev 2013-07-04 03:00:03 UTC
Not sure if it is proper to reopen this bug.

I have tested matplotlib against wxpython:2.9. May be it's time to revert this hack?
Comment 10 Justin Lecher (RETIRED) gentoo-dev 2015-03-20 12:37:20 UTC
Please reopen if this problem still exists with version 1.4