Skip to content
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

Install is failing on a Debian sid on failed to read /root/rust/src/tools/rust-installer/Cargo.toml #42030

Closed
sylvestre opened this issue May 16, 2017 · 7 comments

Comments

@sylvestre
Copy link
Contributor

Trying to build following the documentation is failing on a Debian sid (aka unstable) in a chroot:

# ./x.py build && sudo ./x.py dist --install
info: looks like you are running this command under `sudo`
      and so in order to preserve your $HOME this will now
      use vendored sources by default. Note that if this
      does not work you should run a normal build first
      before running a command like `sudo make install`
downloading https://static.rust-lang.org/dist/2017-04-25/rust-std-beta-x86_64-unknown-linux-gnu.tar.gz
######################################################################## 100.0%
extracting /root/rust/build/cache/2017-04-25/rust-std-beta-x86_64-unknown-linux-gnu.tar.gz
downloading https://static.rust-lang.org/dist/2017-04-25/rustc-beta-x86_64-unknown-linux-gnu.tar.gz
######################################################################## 100.0%
extracting /root/rust/build/cache/2017-04-25/rustc-beta-x86_64-unknown-linux-gnu.tar.gz
downloading https://static.rust-lang.org/dist/2017-04-25/cargo-beta-x86_64-unknown-linux-gnu.tar.gz
######################################################################## 100.0%
extracting /root/rust/build/cache/2017-04-25/cargo-beta-x86_64-unknown-linux-gnu.tar.gz
error: failed to read `/root/rust/src/tools/rust-installer/Cargo.toml`

Caused by:
  No such file or directory (os error 2)
Build completed unsuccessfully in 0:00:56

Then, running

 git submodule update --init
./x.py build && sudo ./x.py dist --install

gives:

info: looks like you are running this command under `sudo`
      and so in order to preserve your $HOME this will now
      use vendored sources by default. Note that if this
      does not work you should run a normal build first
      before running a command like `sudo make install`
error: failed to load source for a dependency on `gcc`

Caused by:
  Unable to update registry https://github.com/rust-lang/crates.io-index

Caused by:
  failed to update replaced source `registry https://github.com/rust-lang/crates.io-index`

Caused by:
  failed to read root of directory source: /root/rust/src/vendor

To learn more, run the command again with --verbose.
Build completed unsuccessfully in 0:00:00

/root/rust/src/vendor doesn't exist

@est31
Copy link
Member

est31 commented May 16, 2017

Dupe of #40108

@sylvestre
Copy link
Contributor Author

the second part of my bug is a dupe, not the first one ( error: failed to read /root/rust/src/tools/rust-installer/Cargo.toml )

@cuviper
Copy link
Member

cuviper commented May 16, 2017

Ugh -- I added rust-installer to the main workspace, but that means bootstrap can't build at all when the workspace is incomplete, so we never get the chance to automatically update submodules.

@alexcrichton any suggestions?

@alexcrichton
Copy link
Member

Bah this actually isn't the first time we've hit this bug, I should have caught this in review!

@cuviper I think the solution is to move the submodule logic to the python x.py script instead of rustbuild itself, and that's currently happening as part of #40291, but if it happens ahead of that I think that'd also be ok!

@cuviper
Copy link
Member

cuviper commented May 16, 2017

You linked the #40291 issue twice -- is there a different number where the submodule logic is changing?

@alexcrichton
Copy link
Member

Oops sorry about that, the second link was intended to be #41639

@alexcrichton
Copy link
Member

#41639 has landed, so closing this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants