qtkeychain: 0.7.0 -> 0.8.0, fix darwin build#36834
qtkeychain: 0.7.0 -> 0.8.0, fix darwin build#36834matthewbauer merged 2 commits intoNixOS:masterfrom
Conversation
There was a problem hiding this comment.
Would it make sense to set this globally? I think this is the behavior we always want but it might not make a difference for most CMake projects.
There was a problem hiding this comment.
I think so. At the least setting CMAKE_POLICY_WARNING_CMP0025 would be helpful for identifying this issue in other packages.
There was a problem hiding this comment.
Thanks! See #37015 for the PR making this the default.
There was a problem hiding this comment.
So after doing this, we still occasionally get issues like in:
Any ideas how to fix it?
|
@GrahamcOfBorg build qtkeychain |
|
Success on x86_64-darwin (full log) Attempted: qtkeychain Partial log (click to expand)
|
|
Success on x86_64-linux (full log) Attempted: qtkeychain Partial log (click to expand)
|
There was a problem hiding this comment.
Hmm, is 0.7.0 and 0.8.0 the same revision?
There was a problem hiding this comment.
Right, the unchanged hash is a mistake, apparently.
There was a problem hiding this comment.
Thing is I tested both versions with --check and neither gives a hash mismatch
There was a problem hiding this comment.
Yea I overlooked changing sha256. I was seeing some odd behavior though: changing sha256 controlled the version build, regardless of the value of rev, but it seems that a nix-collect-garbage may work around this.
- set correct
revandsha256(egv0.6.0and0sbgy1vxabcnn1qi9dfxi6yd0gbbqfgx7sj0c381mp4xay9fxl21) nix-build -A qtkeychain(successfully builds)- built version is
0.6.0(set(PACKAGE_VERSION "0.6.0")inresult/lib/cmake/QtKeychain/QtKeychainConfigVersion.cmake) - fudge the
revbut keepsha256(egrev -> v0.8.0) nix-build -A qtkeychain(successfully builds)- built version is still
0.6.0
I'll set the correct hash
There was a problem hiding this comment.
Fetches are hash-addressed ("fixed-output" in our terminology). If you have the specified hash in nix store, it will be used without any further checks.
There was a problem hiding this comment.
Ahhh :) I understand now, thanks!
There was a problem hiding this comment.
You can force a check with nix-build '<nixpkgs>' -A hello.src --check for example.
|
Failure on aarch64-linux (full log) Attempted: qtkeychain Partial log (click to expand)
|
The darwin build was failing for two reasons 1) cmake incorrectly detected the compiler 2) missing Frameworks /cc ZHF NixOS#36454
|
@GrahamcOfBorg build qtkeychain |
|
btw, tomahawk (which depends on this) fails due to not finding qtkeychain 0.8.0, but it is abandoned (tomahawk-player/tomahawk@c838959). |
|
@GrahamcOfBorg build qtkeychain |
|
Success on x86_64-linux (full log) Attempted: qtkeychain Partial log (click to expand)
|
|
Failure on x86_64-darwin (full log) Attempted: qtkeychain Partial log (click to expand)
|
|
Failure on aarch64-linux (full log) Attempted: qtkeychain Partial log (click to expand)
|
|
This broke the build of |
|
Okay opened issue: #37746 |
The darwin build was failing for two reasons
/cc ZHF #36454
Also related to #35444
Motivation for this change
Things done
build-use-sandboxinnix.confon non-NixOS)nix-shell -p nox --run "nox-review wip"this passes on NixOS but there are (still) failures on Darwin./result/bin/)