-
-
Notifications
You must be signed in to change notification settings - Fork 14.8k
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
rustPackages.clippy fails to compile: can't find crate fmt_macros #77358
Comments
rust-lang/rust-clippy#4651 points to rust-lang/rust#64823 being the root cause of this type of error - it looks like we'll need to pull in the |
rust-lang/rust#64823 was reverted in rust-lang/rust#65342 due to rust-lang/rust#65335 ... |
... and then re-applied with some changes: rust-lang/rust#65474. |
... and then in rust-lang/rust#67469, |
On the clippy side, this PR (re-)introduced the |
(Very tangentially related: https://guix.gnu.org/blog/2018/bootstrapping-rust/, https://github.com/thepowersgang/mrustc) |
There may be an alternative way of building clippy: together with rustc, via |
How does upstream build clippy? |
By enabling this option. |
Good question :) Looking into this, I filed rust-lang/rust-clippy#5037. clippy is referenced from the rust repository as a submodule.
The commit at which clippy is pinned in rust 1.40 is rust-lang/rust-clippy@c8e3cfb. Interestingly, that commit actually failed CI, though I can't tell why. |
Alternatively, as per my suggestion above: setting the |
@mati865, do you happen to know the entry point (a script or CI configuration) that is used to release clippy (as opposed to the CI in the clippy repo used for testing purposes)? |
@curiousleo Clippy is using unstable compiler API and thus is not meant to be built separately (stable and beta compilers will throw an error about unstable features unless unsupported hack is applied). AFAIK Clippy releases are done manually. |
Awesome, I missed that! I don't think the way the comments are phrased make this unambiguous. Okay, I'll see if I can get this to work using
Good to know. Thanks! |
I've managed to build Currently testing whether #77529 simply fixes this issue. |
#77529 will land in |
#77739 has been merged, and |
`rustPackages.clippy` exists in nixpkgs again: NixOS/nixpkgs#77358 (comment) Our nixpkgs pin is newer than when that change was merged. We also enabled cachix on macOS, so even if clippy had to be built, it can be cached.
Describe the bug
nix-build . -A rustPackages.clippy
fails onmaster
since e82fae1 with this error:To Reproduce
Steps to reproduce the behavior:
master
nix-build . -A rustPackages.clippy
Expected behavior
nix-build . -A rustPackages.clippy
should succeed.Additional context
I discovered this build failure in the context of #77327.
Metadata
Maintainer information:
The text was updated successfully, but these errors were encountered: