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 Updating registry `https://github.com/rust-lang/crates.io-index` Downloading javascriptcore-sys v0.0.2 Fresh pkg-config v0.3.9 Compiling javascriptcore-sys v0.0.2 Running `rustc --crate-name build_script_build .cargo/registry/src/github.com-1ecc6299db9ec823/javascriptcore-sys-0.0.2/build.rs --crate-type bin --emit=dep-info,link -C debuginfo=2 -C metadata=7ae3d5f297816108 -C extra-filename=-7ae3d5f297816108 --out-dir /home/cratesfyi/cratesfyi/debug/build/javascriptcore-sys-7ae3d5f297816108 -L dependency=/home/cratesfyi/cratesfyi/debug/deps --extern pkg_config=/home/cratesfyi/cratesfyi/debug/deps/libpkg_config-fdeeca4d6057a82a.rlib --extern-version pkg_config=pkg-config,0.3.9 --cap-lints allow` Running `/home/cratesfyi/cratesfyi/debug/build/javascriptcore-sys-7ae3d5f297816108/build-script-build` thread 'main' panicked at 'Human( failed to run custom build command for `javascriptcore-sys v0.0.2` process didn't exit successfully: `/home/cratesfyi/cratesfyi/debug/build/javascriptcore-sys-7ae3d5f297816108/build-script-build` (exit code: 101) --- stderr thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Failure { command: "\"pkg-config\" \"--libs\" \"--cflags\" \"javascriptcoregtk-3.0\"", output: Output { status: ExitStatus(ExitStatus(256)), stdout: "", stderr: "Package javascriptcoregtk-3.0 was not found in the pkg-config search path.\nPerhaps you should add the directory containing `javascriptcoregtk-3.0.pc\'\nto the PKG_CONFIG_PATH environment variable\nNo package \'javascriptcoregtk-3.0\' found\n" } }', src/libcore/result.rs:859 note: Run with `RUST_BACKTRACE=1` for a backtrace. )', src/bin/cratesfyi.rs:136 note: Run with `RUST_BACKTRACE=1` for a backtrace.