-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
python x.py check
always rebuilds rustc_llvm
on Windows
#92369
Comments
Can you please show your |
This is # Includes one of the default files in src/bootstrap/defaults
profile = "compiler"
changelog-seen = 2 The output of x.py check is what you would expect, except for rustc_llvm(build) starts at 306 and has to go up to 317 in modules. |
How can you be certain that you and I expect the same thing? :-) Also, it's apparent to me now that I don't actually know the purpose of rustc_llvm. Does compiling this crate result in compiling all of LLVM from source? Or is it just a small utility crate that doesn't take much time to compile at all? |
Oh, then I'm lost on what you mean. |
Oh I was replying to how you said "the output is what you'd expect." I wanted to caution against using that as justification to not show what I requested, since maybe what I'd expect is different from what you'd expect. |
The main thing that's out of the ordinary is that every time it's rebuilt, the only thing that I would say is weird about the output. |
And my point is I don't understand why that is weird. This is probably because I don't actually understand what the rustc_llvm crate does exactly (can you answer the question that I asked here?) And furthermore, there could be things in the output that you don't think are out of the ordinary, but somebody else might see it and be able to say that it explains something. Maybe it's not true in this case, but continuing to go back and forth rather than just providing the output as requested seems counterproductive. There are also details of your issue that still aren't clear. When you say "every time it's rebuilt," does that mean even when you do |
If you can run with |
Sorry for all the confusion! Here's the result of that:
Even with no code changes, I get this every time I rerun the command. After just re-running and changing some code, it's proving to be flakey, happening every now and then. From what I'm seeing in the error I think that Cargo is thinking a dependency changed when in reality it hasn't. |
The problem is caused by CFG_LLVM_ROOT changing, but it's not clear why that case change would happen. -c:\\Users\\milo5\\Desktop\\GitHub\\rust\\build\\x86_64-pc-windows-msvc\\ci-llvm/bin\\llvm-config.exe
+C:\\Users\\milo5\\Desktop\\GitHub\\rust\\build\\x86_64-pc-windows-msvc\\ci-llvm/bin\\llvm-config.exe That value is parsed from config.toml, I think, so presumably you're running something in the background like rust-analyzer which is using a different config.toml? Or something Windows-specific is happening that causes case changes, which is also possible I suppose. |
This seems to only happen when I have VSCode open... I think rust-analyzer and a combination of Windows being bad is causing this. |
#88310 now that it is in the merge queue could possibly fix this. Not sure though, I'll test when merged. |
…k-Simulacrum Don't set RUSTC in the bootstrap build script We no longer use this for anything since https://github.com/rust-lang/rust/pull/98483/files#diff-7eddc76f1be9eca2599a9ae58c65ffe247fbdff9b02ef687439894cab9afe749L781. Remove it, so that we spuriously rebuild bootstrap fewer times on Windows (where PATH changes often). Helps with rust-lang#92369. cc rust-lang#102266 r? `@Mark-Simulacrum`
…k-Simulacrum Don't set RUSTC in the bootstrap build script We no longer use this for anything since https://github.com/rust-lang/rust/pull/98483/files#diff-7eddc76f1be9eca2599a9ae58c65ffe247fbdff9b02ef687439894cab9afe749L781. Remove it, so that we spuriously rebuild bootstrap fewer times on Windows (where PATH changes often). Helps with rust-lang#92369. cc rust-lang#102266 r? ``@Mark-Simulacrum``
@Milo123459 can you confirm if this is fixed? |
Yeah, it's fixed. |
I have forked the rust repository, and I made a change. When running
python x.py check
,rustc_llvm
always rebuilds.The text was updated successfully, but these errors were encountered: