-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
[darknet] build failure #16011
Comments
@kunyue001 ,please make sure your vcpkg is latest, and I can confirm you downloaded package is broken.Can you please test if you can extract C:/Users/Kun/vcpkg/downloads/temp/darknet-cache/yolov4-tiny.weights manually? |
Exactly as @JonLiu1993 said. You need to do a |
I have tired git pull in the vcpkg folder. PS C:\Users\Kun\vcpkg> git pull File does not have expected hash:
The file may have been corrupted in transit. This can be caused by Call Stack (most recent call first): Error: Building package darknet:x64-windows failed with: BUILD_FAILED I can find the file: |
I have updated it using git pull. It gives me the same error. |
Yes you're right. I don't know what happened. Might be that github modified the archive somehow? I already have a darknet update PR in the pipeline, I will add correct hashes! |
@kunyue001 ,After @cenit 's pr merge, you can update vcpkg and try again. |
Did anyone solve this trouble? I can't install darknet on local machine |
Make sure that you have the latest portfiles by doing a |
Does not work to me in any of the cases mentioned above. |
Possiable solution to the issue:
@@kunyue001 @soltkreig, we have already fixed this issue on master, please reopen this issue if the issue persist. |
This issue fixed by PR #15296 |
@PhoebeHui we need to add a version string to the downloaded filename ( Since the filename is the same, vcpkg doesn't know that it has to re-download the file.
|
Host Environment
Windows
To Reproduce
Steps to reproduce the behavior:
./vcpkg install xxxx
Failure logs
Additional context
Add any other context about the problem here, such as what you have already tried to resolve the issue.
The text was updated successfully, but these errors were encountered: