[qt5-base:x64-windows] build failure #12341
Assignees
Labels
category:port-bug
The issue is with a library, which is something the port should already support
requires:repro
The issue is not currently repro-able
Comments
Nothing to see here. qt5-imageformats is sometimes a bit flaky and just need to be rerun and the qt5-base regression is a download failure of winflexbison. I also get the warnings: but the build succeeds. I also see the *.json files in the buildtree being generated. hmm... |
From #12229 (comment): Update qt5-base build-depends to include zstd. (Currently trying to find the place actually introducing zstd; actually it is a hidden dependency. Qt tests if it is available and if it is it will just use it without any way to deactivate/toggle it.....) |
|
@JackBoosY why requires:repro? |
|
@cenit Because I can't reproduce this issue on my machine: |
JackBoosY
added
the
category:port-bug
|
yes. I delete it. |
|
@cenit is this still an issue? If yes could you attach both logs (err and out) ? |
|
yes still an issue, I can't use any qt5 project on windows via vcpkg from master anymore build-x64-windows-dbg-err.log |
|
Have you tried without the symlink? I see The first path is also very long. |
|
I launched the build from C:\src, which is a subst of C:\Users\ssinigar\Codice, I don't know how it also expanded it to the full path. Also, no problem with any other port which has the infamous maximum path length |
|
How did you subst that? I always get a "invalid paramter error C:\src" if i try to |
|
after testing your |
|
Let me investigate my own setup then. Thanks for taking time to already test many configs |
|
@cenit: I assume you found a solution? (switching to |
|
Yes it was a symlink and not a junction. Strangely enough it fails mixing the two paths. I was able to complete the build from the original (even if longer) folder |
|
the problem is still here ,please open it @cenit |
|
jom 1.1.3 - empower your cores |
|
@introspection3 This is an unofficial issue, please open a new issue to report that. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Host Environment
To Reproduce
Steps to reproduce the behavior:
./vcpkg upgrade --no-dry-runFailure logs
Additional context
Upgrading my vcpkg install folder today, with the QT5 port updated to 5.15 #11596 , lead to failure.
Re-launching the installation gives the same failure.
Other issues regarding latest qt5 update are also emerging from ci #12229 #11130
The text was updated successfully, but these errors were encountered: