-
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
[taglib] build failure #24616
Comments
Logs? Be aware that all those changes are tested by CI. For me it works as expected from a clean vcpkg.
|
Sorry, I didn't reproduce your problem locally, can you provide your error log? Could you please use the latest vcpkg and try again?
Try steps:
|
also the |
I looked at the logs, the relevant error message was:
After some research I came across this comment. It's an issue related to the system clock being out of sync. Apparently, Ninja has a problem with this for some reason. I dual boot with Linux which uses UTC instead of local time for the system clock, and I also recently traveled to a different timezone but didn't update the settings. Not sure which of those was the culprit, but I went into the Windows settings updated the timezone and synced the time and now it builds fine. Not sure why it built successfully with the git tag 2022.04.12 with the clock out of sync. Perhaps some change to the Ninja config? @Neumann-A I apologize for falsely assuming that the previously mentioned commit was causing this issue and tagging you here. |
Ninja is designed for speed and simplicity. It is "relying on simple dependencies between file timestamps" i.e. it expects that generated files' timestamps are newer than their sources' timestamps. |
Host Environment
To Reproduce
Steps to reproduce the behavior:
./vcpkg install taglib --triplet=x64-windows
Failure logs
Additional context
I built taglib a couple weeks ago with no issue. I'm trying to build again today on a different PC and I get the build failure as shown above. I did some investigation and there haven't been any recent commits on the
taglib
port, but there have been several for its dependencyvcpkg-cmake
. This one in particular looks suspicious as it changed thevcpkg_execute_build_process
function which is the most recent failure in the stack trace. Not sure how to confirm this is causing the issue.@Neumann-A
@BillyONeal
Workaround
For a workaround, I started a new vcpkg root based on the most recent git tag, 2022.04.12.
Then bootstrap and run the
vcpkg install
command, and it successfully builds.The text was updated successfully, but these errors were encountered: