-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Install Error in Synology DSM 6.0 #3588
Comments
Hi there, could you please edit your issue post to include the versions of the three things listed above? |
@rmcgibbo is |
@rubyon what operating system and version thereof are you using? Can you also post the output of the shell command @Ivoz Right. It looks like it's not flexible enough -- perhaps some versions of glibc that we haven't tested previously use a different format of the version string. Knowing the output of the above commands would help decide what the best course is (the options I think are either to return |
Also ccing @njsmith. |
@rmcgibbo please show this...
My operating system is Synology DSM 6.0 (NAS) with Intel CPU |
Is this actually a linux? |
Appears to be "glibc linaro": https://releases.linaro.org/14.11/components/toolchain/glibc-linaro/ Appears to be only for ARM devices, so a quick hack would be to skip the |
...actually, looking at @rubyon: Can you also paste the output of |
Oh, reading comprehension fail, I see that you already said that it's an Intel CPU :-) |
Downstream forks/redistributors of glibc apparently sometimes add junk onto the end of the version number -- e.g. Linaro glibc might have a version number like "2.20-2014.11". This makes the glibc version number parsing code ignore the rest of the string after the minor version number, to be robust against Linaro's current usage, as well as whatever exciting new weirdnesses that other redistributors might come up with in the future. Fixes: pypagh-3588
Here's some info related to this issue. I too have a Synology NAS and upgraded to their disk station manager (DSM) 6.0 software. This system comes with Python 2.7.11 installed by default and you have the option to install Python 3.5.1. Neither versions come with pip installed BUT it's easy to get pip now because of PEP 453. So you can just do a: python -m ensurepip to get pip installed and you don't have to download and run get-pip.py anymore. The pip that's installed in Python 3.5.1 after doing ensurepip is version 7.1.2. This version works with Python 3.5.1 but what I found out is that if you upgrade to the latest version of pip, version 8.1.1, pip breaks and doesn't work. You get the error mentioned above. So the question is, is this going to be fixed in 8.1.2? FYI, as another piece of information I upgrade pip to 8.0.0 and it works, I then tried upgrading to 8.1.0 and it broke. So it appears that this broke somewhere in either 8.0.1, 8.0.2, 8.0.3 or 8.1.0. And again it's also broke in 8.1.1 |
@jschlade: Thanks for the info! And yeah, what broke is that pip 8.1 added support for "manylinux" wheels (see PEP 513), so that you'll be able to download linux wheels directly from pypi instead of having to compile them from scratch. The problem is that the code that tries to check whether your system is actually compatible with the manylinux spec (and in particular, has a new enough glibc) was not prepared for the unusual patched glibc that Synology is shipping. There's a proposed fix in #3590, and it'll probably be fixed in the next pip release -- but the pip maintainers are very busy, so it might take a little while before they have time to review the patch and then to make a release. |
FYI - if this helps root@DISKSTATION://volume1/@appstore/py3k/usr/local/bin# uname -a |
@njsmith thank you for the 411. Looks like I could upgrade to 8.0.3 and wait for this fix. It's just an old habit that I always upgrade my packages to the latest releases... as I've never had an issue like this. :-) Another piece of food for thought is, if pip is now that way to install packages, if pip breaks like this, there's no way to revert back to an older release. I had no choice but to hack my Python 3.5.1 site-packages directory and rm -fR pip and pip-8.x.x.dist-info directories and then do python -m ensurepip again to get to a version of pip that works. I'm not sure if this was the right way but it worked for me. So it would be good to let users know what the correct, forcible way to remove pip is, if needed, in case of emergencies. |
In this case you could also "fix" pip on your machine without upgrading or On Fri, Mar 25, 2016 at 1:21 PM, jschlade notifications@github.com wrote:
-Robert |
@rmcgibbo thanks for this info |
I have the exact same problem on synology |
@rmcgibbo where do i get this file? |
@varwone On my Synology DS713+ I put the file at |
Hi guys, I have related problem. I have been using shadowsocks server in my 214PLAY before upgrade to DSM6. It seems DSM6 break the Python and I struggled to install the shadowsocks server in DSM6 with rmcgibbo suggested method. The following is what I did to install the shadowsocks server in DSM6 : Using PuTTY connect to my 214PLAY and login as admin then :
when start the shadowsocks server, I got the following error :
I tried PIP install crypto but the result still the same, anyone can help? |
@irblue you likely want the openssl package installed, possibly the dev package as well. |
@Ivoz Sorry for being a newbie with Python :(, I tried install the openssl but no successful :
Thank you in advance for any guidance. |
Tried PIP install pyopenssl, still having error :
|
That message would seem to imply that you don't have gcc (properly) |
@irblue, openssl is a linux system / distribution package, not one that is in PyPI/pip can install. |
I am still having this issue. Is there anyone who knows of a solution? |
Still get the same issue
|
you can install the compiler for your NAS here: http://sourceforge.net/projects/dsgpl |
Finally, I solved this problem by installing gcc in see http://www.cphub.net add source to Package Center
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Description:
PIP Install Error
What I've run:
The text was updated successfully, but these errors were encountered: