-
Notifications
You must be signed in to change notification settings - Fork 42
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 fails on Cygwin #282
Comments
Are you still unable to install the cli v2 on Cygwin? I would recommend trying this suggestion from stackoverflow:
Please let us know if that doesn't work for you |
Hi @jmklix , I've left Windows for Fedora and don't have this issue any longer. I create wheels/install from source now. But this issue is from AWSCRT io using edge triggered epoll on Linux, which isn't portable/available on Cygwin, vs using something that would be cross platform portable like libevent, asio, llibuv, libxev, etc. Cygwin is very Linux/UNIX like but it doesn't support epoll currently. Essentially, AWSCRT doesn't support Cygwin in any meaningful way. It's major brand Linux, macOS and Windows and that's it. Installing AWSCLI in the way you describe, installs AWSCLI into Windows and not Cygwin (per se). I understand I might be splitting hairs, but Windows isn't Cygwin and Cygwin isn't Windows. Generally speaking, to be happy using Cygwin, end-users would want programs installed in the Cygwin environment and not in Windows (to be used by pathing in Cygwin). Then there's line endings, quoting issues, piping issues when using AWSCLI for Windows from Cygwin. It's just a pain to deal with this way. Thanks, |
I was updating my AWSCLI v2 from 2.1.29 to 2.2.3 and I got this AWSCRT build/install error:
Basic Python information:
The text was updated successfully, but these errors were encountered: