-
Notifications
You must be signed in to change notification settings - Fork 10
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
improper .so output name #6
Comments
this issue also affects pymumble as well- the same behaviour is encountered when building pycelt and pyopus, etc. |
Are you sure you are not using python 3.4 with Cython ? It seems to be a new naming convention for .so libraries introduced in python 3.2 (PEP 3149 https://www.python.org/dev/peps/pep-3149/). the cpython-34m means that is was compiled for CPython 3.4... |
right and that's what i thought too, except i have my $PATH to use cython 2: [conky@alpha [conky@alpha ~]$ ls -la ~/bin so it feels like something...environmental? or cached from a failed run? or something. any ideas? (this may, now that i'm thinking about it, may be what's causing the bug i reported in parallel to pymumble- or at least could be part of it.) |
sorry, some further clarification:
|
make gives the following, e.g.:
sound_add.cpython-34m.so
instead of:
sound_add.so
at which point i have to stop, ln -s the existing .so to the name expected, and run make again.
The text was updated successfully, but these errors were encountered: