-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
vcpkg hangs when when installing any package #3391
Comments
I too experience the same problem. vckpg hangs the OS when I tried to install caffe2 package! |
Maybe it's related to this issue? |
@vnen , I can't reproduce your issue with the latest vcpkg:2018.11.23-nohash and Win10 1809(build 17763.316), I think this issue has been fixed, could you help confirm? If this issue was fixed, please close this issue. Thank you. |
Tried today with latest commit (f9c461c). I've been more patient now and discovered that it finishes but takes way too long (9min when installing OpenSSL, 11.2min installing curl). It stops on the I think the time it takes to finish is still an issue, but if it's supposed to take that long then you may close the issue. Again, maybe is an issue with CMake (I have version 3.13.4 installed), but I'm not sure how to pinpoint the source of the stall. Log of installing openssl and curl
|
Tested with the latest vcpkg, I got below results: Elapsed time for package zlib:x86-windows: 44.02 s Please try to install them again, if the installation time is reduced, please close this issue. |
@vnen, thanks for posting this issue and your patience. Please feel free to reopen it if this is still a problem for you. |
|
I'm using the latest vcpkg (a9d989e) with Windows 10 (build 16299.371) and every time I try to install a package it hangs forever in one of the steps.
Looking at the task manager, I noticed that there's a cmake process without any activity. Maybe it's a problem with CMake? I have the version 3.11.1 of CMake installed.
If I kill the cmake process, vcpkg stops with
BUILD_FAILED
message.The text was updated successfully, but these errors were encountered: