-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Closed
Description
$ cargo --version
cargo 0.21.0-nightly (50b1c24d1 2017-06-17)
$ systeminfo
OS Name: Microsoft Windows 10 Pro
OS Version: 10.0.15063 N/A Build 15063
On the latest nightly
toolchain cargo
doesn't seem to emit any output on my Windows 10 machine, except when I run cargo --version
for some reason.
The command is actually executed, it's just the output that isn't showing up.
Using --verbose
doesn't make a difference. rustc
does seem fine.
Everything is fine in cargo 0.20.0-nightly (0d0f3baad 2017-06-13)
. I haven't tested any other platforms yet.
Expected
Typical output when running commands:
$ cargo
Rust's package manager
Usage:
cargo <command> [<args>...]
cargo [options]
Options:
-h, --help Display this message
-V, --version Print version info and exit
--list List installed commands
--explain CODE Run `rustc --explain CODE`
-v, --verbose ... Use verbose output (-vv very verbose/build.rs output)
-q, --quiet No output printed to stdout
--color WHEN Coloring: auto, always, never
--frozen Require Cargo.lock and cache are up to date
--locked Require Cargo.lock is up to date
Some common cargo commands are (see all commands with --list):
build Compile the current project
check Analyze the current project and report errors, but don't build object files
clean Remove the target directory
doc Build this project's and its dependencies' documentation
new Create a new cargo project
init Create a new cargo project in an existing directory
run Build and execute src/main.rs
test Run the tests
bench Run the benchmarks
update Update dependencies listed in Cargo.lock
search Search registry for crates
publish Package and upload this project to the registry
install Install a Rust binary
$
Actual
Nothing. Command-line crickets:
$ cargo
$
Commands like build
, run
and test
also produce no output.
EFanZh
Metadata
Metadata
Assignees
Labels
No labels