thread 'main' panicked at src/bootstrap/src/utils/helpers.rs:441:5

[psumbera]

Build on Solaris fails with:

Submodule path 'src/doc/rust-by-example': checked out '093397535b48ae13ec76bc526b7e6eb8c096a85c'
thread 'main' panicked at src/bootstrap/src/utils/helpers.rs:441:5:
std::fs::read_dir(dir) failed with No such file or directory (os error 2)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Build completed unsuccessfully in 0:03:34

MIght be related to #134967 ?!

[jieyouxu]

@psumbera does it repro if you git submodule deinit -f -all then try running the doc step again? Sometimes submodule checkouts can become funky, and the submodule can somehow become in a limbo state.

[onur-ozkan]

I assume you don't have some paths from .gitmodules file, which is not usual for building from source.

[psumbera]

I normally do just:
git clone https://github.com/rust-lang/rust.git /builds/rust-lang
Now when I do also:
cd /builds/rust-lang && git submodule update --init --recursive
it seems to build just fine...

Is there documentation how to properly clone Rust for build? So far my way was working...

[jieyouxu]

You should just be able to git clone without having to manually init submodules. ./x.py should automatically manage it for you, but sometimes submodule states can somehow become corrupted...

[jieyouxu]

FTR, I tried a fresh clone, and I wasn't able to repro (e.g. just ./x doc src/doc/rust-by-example, without manually init-ing submodules). I suspect you just got very unlucky with the submodule checkout. I'm going to close this as inactionable because we can't repro, but please re-open if this is still problematic for you.

[psumbera]

Ok, it may be difference too. For historical reasons I'm still using:
./configure --default-linker=gcc --release-channel=$RELEASE --enable-extended --tools="cargo,rustfmt"
gmake dist