-
Notifications
You must be signed in to change notification settings - Fork 104
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
Provide 64 bit bundle #33
Comments
The reason for the 32-bit package is that I don't know whether WSL is or will ever be available also for 32-bit systems. In that case it would be easier to provide a 32-bit build as "one size fits all". |
I agree it is bothersome and just dropping wslbridge into Cygwin64 and making a shortcut is easy enough. But one should wait to see after the official Creator's Update. But all indications show they are going to keep the 64 bit requirement. Feature freeze on the WSL component also took place about a month ago. |
Everything is saying "64 bit". :) |
Thanks, but the question wasn't whether anyone's particular installation is 64 bit. The link into MSDN above at least says that the beta version is only available in 64 bit (which I knew) but that does not indicate that a final release might not be available in 32 bit, too. |
Done with 0.7.6. |
Due to repeated issues with CygHeap when running 32 bit cygwin components on a 64 bit system I think it would be nice to provide a bundle that is built on 64 bit. This is the error that is asking you to rebaseall as if that is a real fix for anything.
wslbridge is already available for 64 bit and I have manually installed wslbridge in a Cygwin64 installation and have this working with mintty now.
Cygwin seemingly fixed some issue related to this early last year but I have had this issue at least twice the last couple of months. It just sometimes randomly happens on a fresh boot and the only solution is to reboot. With Cygwin64 this isn't an issue.
I have provided a 64 bit bundle here: https://saivert.com/files/wsltty64.zip
The text was updated successfully, but these errors were encountered: