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
Build configure fails due to missing Cargo #3772
Comments
Indeed yeah Cargo is required to compile Cargo. In future Rust releases we'll have In general though having an existing Rust install when compiling from source should work just fine, no need to avoid it. |
Thanks @alexcrichton |
@alexcrichton is there an issue for this? |
@0joshuaolson1 it's currently present on the master branch of rust-lang/rust |
That started with this commit, right? I see Can I use the cargo build outside of Docker if my machine is the right arch? |
Sorry I'm not really sure what you're asking? How does this relate to this issue? |
I was interested in learning how to use this to compile Cargo without Cargo. |
Unfortunately that's not really supported right now, if you're looking to port Cargo to a new platform you'll need to do so through cross-compilation. |
Thanks. |
I've noticed the Cargo documentation seems to require Cargo already installed on the system. Even so that the build instructions have a no-cargo scenario, if I run
./configure
it fails with the following error:In my case I compiled Rust from source, which doesn't have Cargo included anymore. Also as far as I know it is a bad practice to have a pre-existing Rust install (such as via rustup) when compiling Rust and Cargo. In any case, I couldn't figure out from the makefile or the docs if I really need to install Cargo before I build the project.
For clarity - my intention is to build Cargo (and Rust) from source.
What do you recommend?
The text was updated successfully, but these errors were encountered: