Build failed. If you want to re-trigger a documentation build, you can do it here. You can find more information on docs.rs builds documentation on the builds page.
# pre-build errors
command failed: exit status: 101
error: failed to run `rustc` to learn about target-specific information
Caused by:
process didn't exit successfully: `/home/cratesfyi/workspace-builder/rustup-home/toolchains/nightly-x86_64-unknown-linux-gnu/bin/rustc - --crate-name ___ --print=file-names --target i586-pc-windows-msvc --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=split-debuginfo --print=crate-name --print=cfg -Wwarnings` (exit status: 1)
--- stderr
error: error loading target specification: could not find specification for target "i586-pc-windows-msvc"
|
= help: run `rustc --print target-list` for a list of built-in targets
Stack backtrace:
0: anyhow::error::<impl core::convert::From<E> for anyhow::Error>::from
1: rustwide::prepare::fetch_deps
2: rustwide::build::Build::fetch_build_std_dependencies
3: docs_rs::docbuilder::rustwide_builder::RustwideBuilder::build_package_inner::{{closure}}
4: rustwide::build::BuildDirectory::run
5: docs_rs::docbuilder::rustwide_builder::RustwideBuilder::build_package
6: docs_rs::utils::queue_builder::queue_builder
7: cratesfyi::main
8: std::sys::backtrace::__rust_begin_short_backtrace
9: std::rt::lang_start::{{closure}}
10: std::rt::lang_start_internal
11: main
12: __libc_start_main
at /build/glibc-uZu3wS/glibc-2.27/csu/../csu/libc-start.c:310:0
13: _start