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.19.0-dev (28a93c1f4 2017-05-31)
# docs.rs version cratesfyi 0.4.0-dev (bedcc0c 2017-06-01)
# build log Build failed, waiting for other jobs to finish... Updating registry `https://github.com/rust-lang/crates.io-index` Downloading elfutils v0.0.2 Fresh libc v0.2.23 Fresh pkg-config v0.3.9 Compiling libdw-sys v0.0.2 Compiling libelf-sys v0.0.2 Running `/home/cratesfyi/cratesfyi/debug/build/libdw-sys-200d0a0799c1e430/build-script-build` Running `/home/cratesfyi/cratesfyi/debug/build/libelf-sys-34fab19a3ed2aae2/build-script-build` error: failed to run custom build command for `libdw-sys v0.0.2` process didn't exit successfully: `/home/cratesfyi/cratesfyi/debug/build/libdw-sys-200d0a0799c1e430/build-script-build` (exit code: 101) --- stderr thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Failure { command: "\"pkg-config\" \"--libs\" \"--cflags\" \"libdw\"", output: Output { status: ExitStatus(ExitStatus(256)), stdout: "", stderr: "Package libdw was not found in the pkg-config search path.\nPerhaps you should add the directory containing `libdw.pc\'\nto the PKG_CONFIG_PATH environment variable\nNo package \'libdw\' found\n" } }', src/libcore/result.rs:859 note: Run with `RUST_BACKTRACE=1` for a backtrace. thread 'main' panicked at 'build failed', src/bin/cratesfyi.rs:136 note: Run with `RUST_BACKTRACE=1` for a backtrace.