-
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
x.py build no longer works with outdated submodules #57080
Comments
Oh, I guess that my test wasn't thorough enough. Posted my comments in #57082. |
./x.py used to automatically check out the right commit when a submodule was outdated and ./x.py build was run and submodules handling was enabled in config.toml (submodules = true). But it threw an error: [...] failed to run: git submodule -q sync --progress src/tools/clippy The commit removes the --progress from git submodule call. Fixes rust-lang#57080
x.py: fixup 6130fc8, fix submodule handling ./x.py used to automatically check out the right commit when a submodule was outdated and ./x.py build was run and submodules handling was enabled in config.toml (submodules = true). But it threw an error: [...] failed to run: git submodule -q sync --progress src/tools/clippy The commit removes the --progress from git submodule call. Fixes #57080
This still bit me yesterday.
#57082 only removed one of the two |
Just got nailed by this on a Debian install trying to custom compile Rust for MIPS. Removing the --progress argument got me past this, thanks @zackmdavis. |
If we fail to run with `--progress`, try running without instead. Fixes rust-lang#57080.
intelligently handle older version of git in bootstrap If we fail to run with `--progress`, try running without instead. Fixes #57080.
If a submodule is not up to date and I have
submodules = true
set in theconfig.toml
and run./x.py build
, crashes:This used to work before 16329b0 , probably caused by #56933
cc @clarcharr
The text was updated successfully, but these errors were encountered: