Skip to content
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

cxxsupport.cxx not found #2359

Closed
megies opened this issue Aug 30, 2013 · 4 comments
Closed

cxxsupport.cxx not found #2359

megies opened this issue Aug 30, 2013 · 4 comments
Labels
status: needs clarification Issues that need more information to resolve.
Milestone

Comments

@megies
Copy link
Contributor

megies commented Aug 30, 2013

Is matplotlib supposed to use its included cxxsupport.cxx file in case it is not present in the used python environment / system? If so, the lookup seems to fail in some cases. I can give directions how to reproduce (debian squeeze) if anybody is interested.

Also, the path that is fixed in

matplotlib/setupext.py

Lines 708 to 709 in 7d40606

# On Fedora 17, these files are installed in /usr/share/CXX
support_dir = '/usr/src/CXX'
is not valid for Debian. Debian has it in '/usr/share/python2.6/CXX' and (EDIT:) '/usr/share/python2.6/CXX' '/usr/share/python2.7/CXX' instead of '/usr/src/CXX'.

@mdboom
Copy link
Member

mdboom commented Aug 30, 2013

matplotlib is supposed to try to use a system PyCXX first, and fallback to the local installation if that fails. That doesn't always work, given the multitude of different ways that PyCXX is installed. PyCXX is adding support for pkg-config upstream, which should make things much better once that trickles out to the distributions.

You can also manually override to use the locally installed copy using setup.cfg.

Yes -- I'll need something to reproduce and the full build output.

EDIT: setup.cfg doesn't help here. I've been working on too many different things today ;)

@tacaswell
Copy link
Member

punting to 1.4.x due to lack of directions on how to reproduce.

@tacaswell tacaswell modified the milestones: v1.4.x, v1.4.0 Mar 8, 2014
@tacaswell
Copy link
Member

@mdboom This should be irrelevant now that you ripped pycxx out of the c++ layer?

Closing, please re-open if I am wrong.

@mdboom
Copy link
Member

mdboom commented Feb 9, 2015

Yes -- this still affects 1.4.x, but beyond that is a non-issue now that PyCXX is gone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: needs clarification Issues that need more information to resolve.
Projects
None yet
Development

No branches or pull requests

3 participants