-
Notifications
You must be signed in to change notification settings - Fork 35
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
pip install centrosome tries compiling *.c #48
Comments
I think the culprit is here: |
I tried "pip install centrosome" on our Centos 6.5 / Python 2.7 here and it worked. I am guessing that there is a difference in the way setuptools parses the cython extension commands between mine and yours. Can you do: pip freeze |
You can try out my fix like this:
|
my pip version is 7.1.2
gave the following, different error:
|
after attempting to install centrosome i ran
cycler==0.9.0 |
@tischi your setuptools is ancient - from 2009. Cython is pretty old too. I would upgrade both inside your virtualenv. The directions for setuptools are here: https://pypi.python.org/pypi/setuptools
Cython can be upgraded like this:
I think you should be good after that. |
now it worked! Successfully installed centrosome-1.0.3however, i had to slightly change the upgrade of setuptools: update setuptools
|
From Christian Tischner:
(pip install centrosome)
now i did it again with the --system-site-packages and it ran quite far....till i got below error. I ran pip being inside the virtualenv...do i maybe have to explicitly tell it that it should install everything into the virtualenv and not globally?!
building '*' extension
gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/g/software/linux/pack/python-2.7/lib/python2.7/site-packages/numpy/core/include -Icentrosome/include -I/g/software/linux/pack/python-2.7/include/python2.7 -c centrosome/.c -o build/temp.linux-x86_64-2.7/centrosome/.o
gcc: centrosome/*.c: No such file or directory
gcc: no input files
error: command 'gcc' failed with exit status 1
The text was updated successfully, but these errors were encountered: