Open ghost opened 9 years ago
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 ~]$ tail -n1 .bashrc export PATH="~/bin:${PATH}"
[conky@alpha ~]$ ls -la ~/bin total 8 drwxr-xr-x 2 conky conky 4096 Mar 14 19:00 . drwx------ 9 conky conky 4096 Mar 14 19:31 .. lrwxrwxrwx 1 conky conky 16 Mar 14 19:00 cython -> /usr/bin/cython2 lrwxrwxrwx 1 conky conky 19 Mar 14 19:00 cythonize -> /usr/bin/cythonize2 lrwxrwxrwx 1 conky conky 16 Mar 14 18:58 python -> /usr/bin/python2
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:
[conky@alpha ~]$ cat /usr/bin/cython
#!/usr/bin/python3
# EASY-INSTALL-ENTRY-SCRIPT: 'Cython==0.22','console_scripts','cython'
__requires__ = 'Cython==0.22'
import sys
from pkg_resources import load_entry_point
if __name__ == '__main__':
sys.exit(
load_entry_point('Cython==0.22', 'console_scripts', 'cython')()
)
[conky@alpha ~]$ diff /usr/bin/cython /usr/bin/cython2
1c1
< #!/usr/bin/python3
---
> #!/usr/bin/python2
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.