Closed pvdrz closed 6 years ago
INFO:<unknown>: fingerprint error for log v0.3.9: RUSTFLAGS has changed
is RUSTFLAGS
changing?
Mach sets up RUSTFLAGS as part of the build; there's no reason it should be changing between identical builds.
Sure yeah, but Cargo thinks it's changing, so mind double checking that nothing is happening between to builds and indeed RUSTFLAGS
is exactly the same in back-to-back builds?
This occurs when @christianpoveda modifies a file from vim, and doesn't occur for non-Servo repositories. The working theory is that the automatic linter that is set up in vim runs a standard cargo check
, which would not use the same RUSTFLAGS that the mach tool sets up before invoking cargo. This would presumably lead cargo to see that RUSTFLAGS has changed the next time mach invokes the build.
yeah I changed to RLS and the problem dissapeared, sorry. For future vim users: this will happen if ALE is using cargo for linting, use RLS instead of cargo.
Hi, after talking for a while with jdm, he suggested this may be a good place to ask. When trying to build servo running
./mach build -d
(which uses cargo). It always starts from scratch (even if some dependencies were compiled succesfully).I don't know if it is relevant, but my fs is XFS. Here are the logs of
RUST_LOG=cargo::ops::cargo_rustc::fingerprint ./mach build -d
: