Skip to content

Linking errors, probably from "remove lapack linking" branch #342

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.

Sign up for GitHub

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

Jump to bottom
Open
matthew-brett opened this issue Aug 25, 2015 · 2 comments
Open

Linking errors, probably from "remove lapack linking" branch #342

matthew-brett opened this issue Aug 25, 2015 · 2 comments

Comments

@matthew-brett
Copy link
Member

Before we merged #328 - we weren't getting any link errors - see https://travis-ci.org/nipy/nipy/builds/56913971

After we merged #328 - the Python 3 build broke down, probably for unrelated reasons - see #338 .

Re-enabling the Python 3 build (#341) we now have 12 linking errors - see : https://travis-ci.org/matthew-brett/nipy/jobs/77184112

Errors are of form:

ImportError: /home/travis/build/matthew-brett/nipy/venv/lib/python3.4/site-packages/nipy/labs/utils/routines.cpython-34m.so: undefined symbol: PyCObject_AsVoidPtr

This is only for Python 3 - no link errors for Python 2:

https://travis-ci.org/matthew-brett/nipy/jobs/77184109

@alexis-roche - I think these are from the lapack merge - is that possible?
@alexis-roche
Copy link
Member

Oh, yes, this is due to a change in the Python C API from 2.7 to 3. My code uses Python CObjects, which turn out to be deprecated as of Python 2.7, and are probably no longer supported in Python 3 (https://docs.python.org/2/c-api/cobject.html). I think I see how to fix this using the new "PyCapsule" object, and will submit a patch later this week.

@matthew-brett
Copy link
Member Author

Thanks - that would be very helpful...

@matthew-brett matthew-brett mentioned this issue Aug 27, 2015
Merged
matthew-brett added a commit that referenced this issue Aug 31, 2015
@matthew-brett
Merge pull request #346 from matthew-brett/reverting-lapack-refactor
c9520f4 
MRG: revert lapack refactor for compatibility

Lapack refactor increases our scipy dependency to 0.13 (see gh-344) and causes
some build errors (see gh-342).

Revert for now, so we can reconsider how best to fix up gh-328.

As discussed in gh-344.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@matthew-brett @alexis-roche