ehuss
commented
3 years ago Which version of nightly are you using? The directory names were rearranged recently, and src/libstd is now library/std. Make sure the version of nightly cargo you are using is in sync with the version of rustc in the git directory. If you have the latest master, the current nightly is 2020-08-08. You can also build cargo manually from the rust source tree, though it won't be linked into the toolchain automatically (you can sym link it manually if you want).
cr1901
My Custom Rust
I have compiled my own Rust (commit 09f4c9f5082) in an attempt to test an LLVM patch for MSP430:
This Rust compiler's source directory symlinks directly to my git checkout of the rust source:
Attempt At Installing
rust-srcWhen I attempt to install
rust-srcviarustup, as recommended by the manual, I get the following error telling me exactly what I need is impossible:Okay, fair enough. Let's see what happens when I try building anyway:
Indeed, in my
msp430-fixtoolchain, thelibstddoesn't exist, while in mynightlytoolchain, the relevant directory does exist:Attempt At Manual Fix
At this point, because I'm desperate, I try to manually force the src directory the
msp430-fixtoolchain is using to have the layout thatcargoexpects:At which point the build bombs with this:
At This Point, I Decide To Open This Issue
I'm kind of stuck here. I need to be able to build my own libcore for testing, so I can test a patch against a target that does not get
libcore/libstdbuilt by default (not built because it's a cross target?). Butcargois going out of it's way to prevent me from doing so. In the pastxargohad an environment variable to set the source root to an external location (XARGO_RUST_SRC). However, it seemsxargohas completely stopped working recently, and thebuild-stdfeature does not have an equivalent environment variable.So... what am I doing wrong? Is there any possible workaround?