-
-
Notifications
You must be signed in to change notification settings - Fork 15k
something is weird about llvm submodule handling #124162
Copy link
Copy link
Open
Labels
C-bugCategory: This is a bug.Category: This is a bug.S-needs-reproStatus: This issue has no reproduction and needs a reproduction to make progress.Status: This issue has no reproduction and needs a reproduction to make progress.T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
Metadata
Metadata
Assignees
Labels
C-bugCategory: This is a bug.Category: This is a bug.S-needs-reproStatus: This issue has no reproduction and needs a reproduction to make progress.Status: This issue has no reproduction and needs a reproduction to make progress.T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
Type
Fields
Give feedbackNo fields configured for issues without a type.
I just observed the following:
I did a git pull and it downloaded a bunch of llvm submodule data.
Afterwards, I did an
x.py install, I'm not sure what happened with the llvm submodule but llvm did NOT get rebuilt, so probably nothing touched it?Then, I did another x.py install afterwards, without touching anything on the repo and THAT did start rebuilding llvm again.
I'm having a gut feeling that we should have had rebuilt llvm already on the first x.py install but I don't know what the underlying issue is.
cfg: