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.17.0-nightly (134c4a0f0 2017-03-20)
# docs.rs version cratesfyi 0.3.2 (56e5d46 2017-03-20)
# 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 Compiling libc v0.2.21 Compiling pkg-config v0.3.9 Running `rustc --crate-name libc .cargo/registry/src/github.com-1ecc6299db9ec823/libc-0.2.21/src/lib.rs --crate-type lib --emit=dep-info,link -C debuginfo=2 --cfg 'feature="default"' --cfg 'feature="use_std"' -C metadata=5dc7b85e748840b4 -C extra-filename=-5dc7b85e748840b4 --out-dir /home/cratesfyi/elfutils-0.0.2/debug/deps -L dependency=/home/cratesfyi/elfutils-0.0.2/debug/deps --cap-lints allow` Running `rustc --crate-name pkg_config .cargo/registry/src/github.com-1ecc6299db9ec823/pkg-config-0.3.9/src/lib.rs --crate-type lib --emit=dep-info,link -C debuginfo=2 -C metadata=af8168308ca6d27e -C extra-filename=-af8168308ca6d27e --out-dir /home/cratesfyi/elfutils-0.0.2/debug/deps -L dependency=/home/cratesfyi/elfutils-0.0.2/debug/deps --cap-lints allow` Compiling libdw-sys v0.0.2 Compiling libelf-sys v0.0.2 Running `rustc --crate-name build_script_build .cargo/registry/src/github.com-1ecc6299db9ec823/libdw-sys-0.0.2/build.rs --crate-type bin --emit=dep-info,link -C debuginfo=2 -C metadata=a50067904478f741 -C extra-filename=-a50067904478f741 --out-dir /home/cratesfyi/elfutils-0.0.2/debug/build/libdw-sys-a50067904478f741 -L dependency=/home/cratesfyi/elfutils-0.0.2/debug/deps --extern pkg_config=/home/cratesfyi/elfutils-0.0.2/debug/deps/libpkg_config-af8168308ca6d27e.rlib --cap-lints allow` Running `rustc --crate-name build_script_build .cargo/registry/src/github.com-1ecc6299db9ec823/libelf-sys-0.0.2/build.rs --crate-type bin --emit=dep-info,link -C debuginfo=2 -C metadata=d3750fb9f7628783 -C extra-filename=-d3750fb9f7628783 --out-dir /home/cratesfyi/elfutils-0.0.2/debug/build/libelf-sys-d3750fb9f7628783 -L dependency=/home/cratesfyi/elfutils-0.0.2/debug/deps --extern pkg_config=/home/cratesfyi/elfutils-0.0.2/debug/deps/libpkg_config-af8168308ca6d27e.rlib --cap-lints allow` Running `/home/cratesfyi/elfutils-0.0.2/debug/build/libelf-sys-d3750fb9f7628783/build-script-build` Running `/home/cratesfyi/elfutils-0.0.2/debug/build/libdw-sys-a50067904478f741/build-script-build` error: failed to run custom build command for `libelf-sys v0.0.2` process didn't exit successfully: `/home/cratesfyi/elfutils-0.0.2/debug/build/libelf-sys-d3750fb9f7628783/build-script-build` (exit code: 101) --- stderr thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Failure { command: "\"pkg-config\" \"--libs\" \"--cflags\" \"libelf\"", output: Output { status: ExitStatus(ExitStatus(256)), stdout: "", stderr: "Package libelf was not found in the pkg-config search path.\nPerhaps you should add the directory containing `libelf.pc\'\nto the PKG_CONFIG_PATH environment variable\nNo package \'libelf\' found\n" } }', /checkout/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.