-
-
Notifications
You must be signed in to change notification settings - Fork 6
Cargo clippy with cargo-sysroot warns on sysroot #6
Comments
Gonna need more information here, as i'm unable to reproduce, and have never had that happen before. |
Here's steps to reproduce. I'm running on macOS 11.0.1
You can also see the output here, as I first noticed on CI. https://github.com/EmbarkStudios/rust-gpu/runs/1418118000?check_suite_focus=true#step:8:333 |
Does not reproduce on my machine, clippy ran successfully. For reference I'm on Arch Linux, if that makes any difference. |
Hmm, okay. I can reproduce it here, so I'll try to debug this later this week. |
Apologies, seems I out the branch wrong. I'm getting failures, but nothing mentioning core, "Error loading target specification: Could not find specification for target "spirv-unknown-unknown"". |
That's actually a different bug, the rustc flags in the builder aren't working. |
Yeah oops, I noticed that. Fixed in 48f811f |
Now it seems to be linker errors
|
I have a fix for that locally one moment. |
@DianaNites Okay it's working now so running |
Clippy now successfully runs, and i'm not seeing any clippy warnings from the sysroot, just all the dependencies? |
Ah build output, If I insert a panic into the build script I see non-fatal clippy warnings. No idea why thats happening.. |
I’ll investigate more tomorrow, but I would hazard to guess it’s something with flags and or |
Potnentially related: EmbarkStudios/rust-gpu#294 |
Cause is probably the new Removing it from the env should probably fix it |
Should be fixed now but I can't test so |
Hey while working on EmbarkStudios/rust-gpu#239 I noticed that when running
cargo clippy
on a project that usescargo-sysroot
in a build script will also run clippy on core, which isn't ideal since there's a lot of warnings, and there's not much I as a user can do about it. It would be nice if clippy didn't warn about sysroot.The text was updated successfully, but these errors were encountered: