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.
# rustc version
rustc 1.12.0-nightly (54c0dcfd6 2016-07-28)# docs.rs version
cratesfyi 0.2.0 (5dbd676 2016-07-30)# build log
Updating registry `https://github.com/rust-lang/crates.io-index`
Downloading libtar-sys v0.1.1
Compiling libtar-sys v0.1.1
Running `rustc .cargo/registry/src/github.com-1ecc6299db9ec823/libtar-sys-0.1.1/build.rs --crate-name build_script_build --crate-type bin -g --out-dir /home/cratesfyi/libtar-sys-0.1.1/debug/build/libtar-sys-caabce18706e42cf --emit=dep-info,link -L dependency=/home/cratesfyi/libtar-sys-0.1.1/debug -L dependency=/home/cratesfyi/libtar-sys-0.1.1/debug/deps`
.cargo/registry/src/github.com-1ecc6299db9ec823/libtar-sys-0.1.1/build.rs:11:42: 11:43 error: expected expression, found `]`
.cargo/registry/src/github.com-1ecc6299db9ec823/libtar-sys-0.1.1/build.rs:11 ($($arg:tt)*) => (&format!($($arg)*)[]);
^
thread 'main' panicked at 'ChainedError {
error: failed to compile `libtar-sys v0.1.1`, intermediate artifacts can be found at `/home/cratesfyi/libtar-sys-0.1.1`,
cause: ChainedError {
error: Could not compile `libtar-sys`.,
cause: Process didn't exit successfully: `rustc .cargo/registry/src/github.com-1ecc6299db9ec823/libtar-sys-0.1.1/build.rs --crate-name build_script_build --crate-type bin -g --out-dir /home/cratesfyi/libtar-sys-0.1.1/debug/build/libtar-sys-caabce18706e42cf --emit=dep-info,link -L dependency=/home/cratesfyi/libtar-sys-0.1.1/debug -L dependency=/home/cratesfyi/libtar-sys-0.1.1/debug/deps` (exit code: 101)
}
}', src/bin/cratesfyi.rs:119
note: Run with `RUST_BACKTRACE=1` for a backtrace.