-
-
Notifications
You must be signed in to change notification settings - Fork 13.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
Build failure: pkgsCross.aarch64-multiplatform.qt5.qtsvg #269756
Comments
Checking out one commit before #264903 shows that it's not the cause, the error is a bit different though
|
Caused by 68cc025 @alyssais reported the issue in the pr #246022 (comment) Will be fixed by the CC @amjoseph-nixpkgs |
Yeah, I've seen this too and I have a bunch of messy hacks in my local tree to work around it. I am really burned out on QT cross compiling stuff. I need to not think about it for a few weeks. It's really draining. |
Well, I have to say that the strict check in The problem here is in
(A shameless plug of #267311 from where this snippet will hopefully be gone soon.) |
Which will probably pull qmake-the-binary out of the PATH and also break the build. Another piece of the puzzle is UPD: And I'm completely forgetting that qmake-the-binary itself relies on this baked-in XSPEC. So we can't really use the binary from So maybe the right solution for mixed-arch packages is to force a UPD: Ah, yeah, we're already doing this, but in |
And if somebody uses UPD: Except that I can't find a way to get the proper version of |
ffado uses wrapQtAppsHook in nativeBuildInputs, but and wrapQtAppsHook depends on qtsvg, but buildPackages.qt5.qtsvg doesn't build when cross compiling. So even in the canExecute case, we can't do this. Link: NixOS#269756
ffado uses wrapQtAppsHook in nativeBuildInputs, but and wrapQtAppsHook depends on qtsvg, but buildPackages.qt5.qtsvg doesn't build when cross compiling. So even in the canExecute case, we can't do this. Link: #269756
I've noticed the same thing when cross compiling Steam on aarch64-linux with |
The text was updated successfully, but these errors were encountered: