New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing crates #23

Open
onur opened this Issue Aug 26, 2016 · 299 comments

Comments

Projects
None yet
@onur
Owner

onur commented Aug 26, 2016

Docs.rs may have failed to build some crates for various reasons (missing dependency on build machine or bad configuration etc).

You can report them into this issue.

@azerupi

This comment has been minimized.

Show comment
Hide comment
@onur

This comment has been minimized.

Show comment
Hide comment
@onur

onur Aug 26, 2016

Owner

There is a problem on crates that have url-0.5.9 dependency. If you check the build log cargo is returning error with: url-0.5.9/Cargo.toml:14:3 expected a newline after table definition. This is a warning when we use standalone cargo, but it is returning an Err as a library. I wasn't able to figure out how to bypass this.

Owner

onur commented Aug 26, 2016

There is a problem on crates that have url-0.5.9 dependency. If you check the build log cargo is returning error with: url-0.5.9/Cargo.toml:14:3 expected a newline after table definition. This is a warning when we use standalone cargo, but it is returning an Err as a library. I wasn't able to figure out how to bypass this.

@azerupi

This comment has been minimized.

Show comment
Hide comment
@azerupi

azerupi Aug 26, 2016

Indeed, I have seen this warning in my own crates too before. I am not sure there is a way around it, except maybe using a fork of url-0.5.9 with the fix and using Cargo replace. I wouldn't consider that a solution though 😉

I have also seen crates depending on compiler internals that did not compile with the particular nightly version used. diesel_codegen for example. But I guess making this work is a non-goal.

azerupi commented Aug 26, 2016

Indeed, I have seen this warning in my own crates too before. I am not sure there is a way around it, except maybe using a fork of url-0.5.9 with the fix and using Cargo replace. I wouldn't consider that a solution though 😉

I have also seen crates depending on compiler internals that did not compile with the particular nightly version used. diesel_codegen for example. But I guess making this work is a non-goal.

@dimbleby

This comment has been minimized.

Show comment
Hide comment
@dimbleby

dimbleby Aug 26, 2016

https://docs.rs/crate/c-ares-sys/ (and as a result, https://docs.rs/crate/c-ares/ too).

Need to install libtool to compile the C library being wrapped.

Or, install c-ares directly so that we find the package and don't need to compile our own version - either is supposed to work.

dimbleby commented Aug 26, 2016

https://docs.rs/crate/c-ares-sys/ (and as a result, https://docs.rs/crate/c-ares/ too).

Need to install libtool to compile the C library being wrapped.

Or, install c-ares directly so that we find the package and don't need to compile our own version - either is supposed to work.

@cuviper

This comment has been minimized.

Show comment
Hide comment
@cuviper

cuviper Aug 26, 2016

https://docs.rs/crate/probe/ appears to have only attempted a few older versions, which don't work with current nightly, but the current 0.1.6 should be fine.

cuviper commented Aug 26, 2016

https://docs.rs/crate/probe/ appears to have only attempted a few older versions, which don't work with current nightly, but the current 0.1.6 should be fine.

@onur

This comment has been minimized.

Show comment
Hide comment
@onur

onur Aug 27, 2016

Owner

@cuviper thanks for reporting. Looks like docs.rs returned IoError when trying to build probe 0.1.4+. I'll fix it tomorrow morning.

Owner

onur commented Aug 27, 2016

@cuviper thanks for reporting. Looks like docs.rs returned IoError when trying to build probe 0.1.4+. I'll fix it tomorrow morning.

@diwic

This comment has been minimized.

Show comment
Hide comment
@diwic

diwic Aug 27, 2016

First - cool stuff! :-)

Second, about https://docs.rs/crate/dbus/0.3.4

Package dbus-1 was not found in the pkg-config search path.
Perhaps you should add the directory containing 'dbus-1.pc'
to the PKG_CONFIG_PATH environment variable
No package 'dbus-1' found

https://docs.rs/crate/alsa/0.1.2 fails with the same error, but missing alsa.pc instead of dbus-1.pc.

Is there some way for me as crate author to indicate that docs.rs needs to install these before compiling my crates? Because this seems like it's not going to scale very well as the number of crates grow with the fast-growing Rust ecosystem...

diwic commented Aug 27, 2016

First - cool stuff! :-)

Second, about https://docs.rs/crate/dbus/0.3.4

Package dbus-1 was not found in the pkg-config search path.
Perhaps you should add the directory containing 'dbus-1.pc'
to the PKG_CONFIG_PATH environment variable
No package 'dbus-1' found

https://docs.rs/crate/alsa/0.1.2 fails with the same error, but missing alsa.pc instead of dbus-1.pc.

Is there some way for me as crate author to indicate that docs.rs needs to install these before compiling my crates? Because this seems like it's not going to scale very well as the number of crates grow with the fast-growing Rust ecosystem...

@lucab

This comment has been minimized.

Show comment
Hide comment
@lucab

lucab Aug 27, 2016

Thanks for running this service!

I noticed that systemd crates fails to build because of missing C development files: https://docs.rs/crate/systemd/0.0.10

This requires libsystemd-dev (or equivalent) on the building machine.

By the way, what is the OS of the building environment here? Does it have any package manager that could be re-used to install system dependencies on demand? I'm thinking about using the metadata table to encode this information to drive an external package manager.

lucab commented Aug 27, 2016

Thanks for running this service!

I noticed that systemd crates fails to build because of missing C development files: https://docs.rs/crate/systemd/0.0.10

This requires libsystemd-dev (or equivalent) on the building machine.

By the way, what is the OS of the building environment here? Does it have any package manager that could be re-used to install system dependencies on demand? I'm thinking about using the metadata table to encode this information to drive an external package manager.

@onur

This comment has been minimized.

Show comment
Hide comment
@onur

onur Aug 27, 2016

Owner

@cuviper for some reason cargo is not generating any documentation when we use target option with your crate. I fixed the IoError in docs.rs, probe is available now, but only default platform worked.

@diwic dbus and alsa building fine now.

@lucab docs.rs is using Debian. I am planning to add docs.rs metadata table to Cargo.toml, so people can define extra features and system dependencies.

BTW I installed systemd development files but looks like systemd crate (or one of its dependency) doesn't work with recent nightly.

Owner

onur commented Aug 27, 2016

@cuviper for some reason cargo is not generating any documentation when we use target option with your crate. I fixed the IoError in docs.rs, probe is available now, but only default platform worked.

@diwic dbus and alsa building fine now.

@lucab docs.rs is using Debian. I am planning to add docs.rs metadata table to Cargo.toml, so people can define extra features and system dependencies.

BTW I installed systemd development files but looks like systemd crate (or one of its dependency) doesn't work with recent nightly.

@nagisa

This comment has been minimized.

Show comment
Hide comment
@nagisa

nagisa Aug 28, 2016

@onur I see you’ve somehow ended up running build.rs stuff when generating documentation. That’s generally unnecessary for majority of crates (notable exceptions are the stuff which use syntex/lalrpop-like scheme to generate code) and plain rustdoc should generate documentation for these crates just fine without any of the dependency libraries existing.

nagisa commented Aug 28, 2016

@onur I see you’ve somehow ended up running build.rs stuff when generating documentation. That’s generally unnecessary for majority of crates (notable exceptions are the stuff which use syntex/lalrpop-like scheme to generate code) and plain rustdoc should generate documentation for these crates just fine without any of the dependency libraries existing.

@onur

This comment has been minimized.

Show comment
Hide comment
@onur

onur Aug 28, 2016

Owner

@nagisa I am not sure how to achieve that but I am using Cargo::ops::compile_pkg to generate documentation. This function is building docs.

Owner

onur commented Aug 28, 2016

@nagisa I am not sure how to achieve that but I am using Cargo::ops::compile_pkg to generate documentation. This function is building docs.

@nagisa

This comment has been minimized.

Show comment
Hide comment
@nagisa

nagisa commented Aug 28, 2016

@onur onur added the bug label Aug 29, 2016

@hoodie

This comment has been minimized.

Show comment
Hide comment
@hoodie

hoodie Aug 30, 2016

https://docs.rs/crate/notify-rust/3.1.1 failed to build, due to the same problems as dbus is there a way to manually trigger rebuilding?

hoodie commented Aug 30, 2016

https://docs.rs/crate/notify-rust/3.1.1 failed to build, due to the same problems as dbus is there a way to manually trigger rebuilding?

@onur

This comment has been minimized.

Show comment
Hide comment
@onur

onur Aug 30, 2016

Owner

@hoodie docs.rs has rebuilt every version of notify-rust.

I was planning to add a button to automate rebuild requests but I changed my mind. People can abuse this kind of feature.

Owner

onur commented Aug 30, 2016

@hoodie docs.rs has rebuilt every version of notify-rust.

I was planning to add a button to automate rebuild requests but I changed my mind. People can abuse this kind of feature.

@hoodie

This comment has been minimized.

Show comment
Hide comment
@hoodie

hoodie Aug 30, 2016

Perhaps there is a way to authenticate as the crate owner via github?

hoodie commented Aug 30, 2016

Perhaps there is a way to authenticate as the crate owner via github?

@msierks

This comment has been minimized.

Show comment
Hide comment

msierks commented Sep 1, 2016

@onur

This comment has been minimized.

Show comment
Hide comment
@onur

onur Sep 1, 2016

Owner

@msierks lua crate is looking for lua 5.3.3, and Debian only have lua 5.3.1. There is not much I can do in this case.

Owner

onur commented Sep 1, 2016

@msierks lua crate is looking for lua 5.3.3, and Debian only have lua 5.3.1. There is not much I can do in this case.

@hoodie

This comment has been minimized.

Show comment
Hide comment
@hoodie

hoodie Sep 1, 2016

this raises the question, do you build each crate completely or just run cargo doc? And if the latter, does cargo doc really need to have all build dependencies? This looks like a potential upstream improvement. Does it @steveklabnik?

hoodie commented Sep 1, 2016

this raises the question, do you build each crate completely or just run cargo doc? And if the latter, does cargo doc really need to have all build dependencies? This looks like a potential upstream improvement. Does it @steveklabnik?

@onur

This comment has been minimized.

Show comment
Hide comment
@onur

onur Sep 1, 2016

Owner

@hoodie cargo doc is building crate first.

Owner

onur commented Sep 1, 2016

@hoodie cargo doc is building crate first.

@msierks

This comment has been minimized.

Show comment
Hide comment
@msierks

msierks Sep 1, 2016

@onur hmm, well it appears the next release rust-lua will have lua 5.3.3 bundled with it. Someone correct me if I'm wrong.

msierks commented Sep 1, 2016

@onur hmm, well it appears the next release rust-lua will have lua 5.3.3 bundled with it. Someone correct me if I'm wrong.

@steveklabnik

This comment has been minimized.

Show comment
Hide comment
@steveklabnik

steveklabnik Sep 1, 2016

And if the latter, does cargo doc really need to have all build dependencies?

Yes, because in order to generate docs, it has to build the library, thanks to things like cfg.

steveklabnik commented Sep 1, 2016

And if the latter, does cargo doc really need to have all build dependencies?

Yes, because in order to generate docs, it has to build the library, thanks to things like cfg.

@bluss

This comment has been minimized.

Show comment
Hide comment
@bluss

bluss Sep 6, 2016

Contributor

Thanks for making a great service. https://docs.rs/crate/nodrop-union/0.1.8 simply needs a newer nightly to build. Will it be retried automatically?

Contributor

bluss commented Sep 6, 2016

Thanks for making a great service. https://docs.rs/crate/nodrop-union/0.1.8 simply needs a newer nightly to build. Will it be retried automatically?

@onur

This comment has been minimized.

Show comment
Hide comment
@onur

onur Sep 6, 2016

Owner

@bluss currently there is no way to trigger rebuilds automatically. I'll upgrade rustc to latest nightly tomorrow.

Owner

onur commented Sep 6, 2016

@bluss currently there is no way to trigger rebuilds automatically. I'll upgrade rustc to latest nightly tomorrow.

@dimbleby

This comment has been minimized.

Show comment
Hide comment
@dimbleby

dimbleby Sep 6, 2016

Any update on this?

dimbleby commented Sep 6, 2016

Any update on this?

@onur

This comment has been minimized.

Show comment
Hide comment
@onur

onur Sep 7, 2016

Owner

@bluss nodrop-union have docs now.

@dimbleby sorry I didn't see your first message, c-ares-sys and c-ares should work fine now.

Owner

onur commented Sep 7, 2016

@bluss nodrop-union have docs now.

@dimbleby sorry I didn't see your first message, c-ares-sys and c-ares should work fine now.

@dimbleby

This comment has been minimized.

Show comment
Hide comment
@dimbleby

dimbleby Sep 7, 2016

Great, many thanks!

dimbleby commented Sep 7, 2016

Great, many thanks!

@Robbepop

This comment has been minimized.

Show comment
Hide comment
@Robbepop

Robbepop Sep 12, 2016

docs.rs didn't recognize that I updated my crate Prophet from 0.0.1 to 0.0.2. It is an important update since many things (also documentation) have changed and because I yanked the old version.
docs.rs didn't list my crate in its recent released list, so I guess it was dropped or simply missed.
Is there anything I can do? At the moment I heavily depend on the great documentation generation of docs.rs. :)

Robbepop commented Sep 12, 2016

docs.rs didn't recognize that I updated my crate Prophet from 0.0.1 to 0.0.2. It is an important update since many things (also documentation) have changed and because I yanked the old version.
docs.rs didn't list my crate in its recent released list, so I guess it was dropped or simply missed.
Is there anything I can do? At the moment I heavily depend on the great documentation generation of docs.rs. :)

@onur

This comment has been minimized.

Show comment
Hide comment
@onur

onur Sep 12, 2016

Owner

sorry @Robbepop, I think I accidentally removed prophet from build queue while I was trying to remove google-* crates because of #46 yesterday. It is fixed now.

Owner

onur commented Sep 12, 2016

sorry @Robbepop, I think I accidentally removed prophet from build queue while I was trying to remove google-* crates because of #46 yesterday. It is fixed now.

@peterhuene

This comment has been minimized.

Show comment
Hide comment
@peterhuene

peterhuene Jul 28, 2018

Seconding what @konstin reported regarding proc macros: need the latest nightly (1.29) for crates such as azure-functions and azure-functions-codegen that have migrated to use_extern_macros.

peterhuene commented Jul 28, 2018

Seconding what @konstin reported regarding proc macros: need the latest nightly (1.29) for crates such as azure-functions and azure-functions-codegen that have migrated to use_extern_macros.

@DoumanAsh

This comment has been minimized.

Show comment
Hide comment
@DoumanAsh

DoumanAsh Aug 1, 2018

Well my crate got no docs, sad https://docs.rs/crate/yukikaze/0.0.1/builds

Error:

error[E0658]: access to extern crates through prelude is experimental (see issue #44660)
  |
  = help: add #![feature(extern_prelude)] to the crate attributes to enable

But I'm not sure from where it is coming from

DoumanAsh commented Aug 1, 2018

Well my crate got no docs, sad https://docs.rs/crate/yukikaze/0.0.1/builds

Error:

error[E0658]: access to extern crates through prelude is experimental (see issue #44660)
  |
  = help: add #![feature(extern_prelude)] to the crate attributes to enable

But I'm not sure from where it is coming from

@dvic

This comment has been minimized.

Show comment
Hide comment
@dvic

dvic Aug 6, 2018

@seanmonstar reqwest also fails with the error[E0658]: access to extern crates through prelude is experimental (see issue #44660) error: https://docs.rs/crate/reqwest/0.8.7/builds/110715.

dvic commented Aug 6, 2018

@seanmonstar reqwest also fails with the error[E0658]: access to extern crates through prelude is experimental (see issue #44660) error: https://docs.rs/crate/reqwest/0.8.7/builds/110715.

@mulimoen

This comment has been minimized.

Show comment
Hide comment
@mulimoen

mulimoen Aug 12, 2018

Failed to build https://docs.rs/crate/uvc-sys/0.1.0

The build fails due to libuvc not being installed

mulimoen commented Aug 12, 2018

Failed to build https://docs.rs/crate/uvc-sys/0.1.0

The build fails due to libuvc not being installed

@blueridanus

This comment has been minimized.

Show comment
Hide comment
@blueridanus

blueridanus Aug 15, 2018

https://crates.io/crates/h2 also fails to build with the same error as in previous comments:

error[E0658]: access to extern crates through prelude is experimental (see issue #44660)
  |
  = help: add #![feature(extern_prelude)] to the crate attributes to enable

thread 'main' panicked at 'Error(
    CargoError(
        ChainedError {
            error: Could not document `h2`.,
            cause: process didn't exit successfully: `rustdoc --crate-name h2 .cargo/registry/src/github.com-1ecc6299db9ec823/h2-0.1.12/src/lib.rs -o /home/cratesfyi/cratesfyi/doc -Z unstable-options --resource-suffix -20180602-1.28.0-dev-b9bf4f162 -L dependency=/home/cratesfyi/cratesfyi/debug/deps --extern fnv=/home/cratesfyi/cratesfyi/debug/deps/libfnv-faa257ace9f05d30.rlib --extern-version fnv=fnv,1.0.6 --extern tokio_io=/home/cratesfyi/cratesfyi/debug/deps/libtokio_io-25b4cc70b7f76370.rlib --extern-version tokio_io=tokio-io,0.1.7 --extern http=/home/cratesfyi/cratesfyi/debug/deps/libhttp-07e15073e011d227.rlib --extern-version http=http,0.1.10 --extern bytes=/home/cratesfyi/cratesfyi/debug/deps/libbytes-996bdd1cd39c08a8.rlib --extern-version bytes=bytes,0.4.9 --extern string=/home/cratesfyi/cratesfyi/debug/deps/libstring-2b2234c5d67ab57d.rlib --extern-version string=string,0.1.1 --extern indexmap=/home/cratesfyi/cratesfyi/debug/deps/libindexmap-f41d1eed9e1ac11e.rlib --extern-version indexmap=indexmap,1.0.1 --extern byteorder=/home/cratesfyi/cratesfyi/debug/deps/libbyteorder-35abf1ff955f78f5.rlib --extern-version byteorder=byteorder,1.2.4 --extern log=/home/cratesfyi/cratesfyi/debug/deps/liblog-c3ec1d3c60904ac4.rlib --extern-version log=log,0.4.3 --extern slab=/home/cratesfyi/cratesfyi/debug/deps/libslab-8bdcdf1795930a41.rlib --extern-version slab=slab,0.4.1 --extern futures=/home/cratesfyi/cratesfyi/debug/deps/libfutures-7c92a300de6e1cf8.rlib --extern-version futures=futures,0.1.23` (exit code: 101)
        }
    ),
    State {
        next_error: None,
        backtrace: None
    }
)', src/bin/cratesfyi.rs:142:13
note: Run with `RUST_BACKTRACE=1` for a backtrace.

blueridanus commented Aug 15, 2018

https://crates.io/crates/h2 also fails to build with the same error as in previous comments:

error[E0658]: access to extern crates through prelude is experimental (see issue #44660)
  |
  = help: add #![feature(extern_prelude)] to the crate attributes to enable

thread 'main' panicked at 'Error(
    CargoError(
        ChainedError {
            error: Could not document `h2`.,
            cause: process didn't exit successfully: `rustdoc --crate-name h2 .cargo/registry/src/github.com-1ecc6299db9ec823/h2-0.1.12/src/lib.rs -o /home/cratesfyi/cratesfyi/doc -Z unstable-options --resource-suffix -20180602-1.28.0-dev-b9bf4f162 -L dependency=/home/cratesfyi/cratesfyi/debug/deps --extern fnv=/home/cratesfyi/cratesfyi/debug/deps/libfnv-faa257ace9f05d30.rlib --extern-version fnv=fnv,1.0.6 --extern tokio_io=/home/cratesfyi/cratesfyi/debug/deps/libtokio_io-25b4cc70b7f76370.rlib --extern-version tokio_io=tokio-io,0.1.7 --extern http=/home/cratesfyi/cratesfyi/debug/deps/libhttp-07e15073e011d227.rlib --extern-version http=http,0.1.10 --extern bytes=/home/cratesfyi/cratesfyi/debug/deps/libbytes-996bdd1cd39c08a8.rlib --extern-version bytes=bytes,0.4.9 --extern string=/home/cratesfyi/cratesfyi/debug/deps/libstring-2b2234c5d67ab57d.rlib --extern-version string=string,0.1.1 --extern indexmap=/home/cratesfyi/cratesfyi/debug/deps/libindexmap-f41d1eed9e1ac11e.rlib --extern-version indexmap=indexmap,1.0.1 --extern byteorder=/home/cratesfyi/cratesfyi/debug/deps/libbyteorder-35abf1ff955f78f5.rlib --extern-version byteorder=byteorder,1.2.4 --extern log=/home/cratesfyi/cratesfyi/debug/deps/liblog-c3ec1d3c60904ac4.rlib --extern-version log=log,0.4.3 --extern slab=/home/cratesfyi/cratesfyi/debug/deps/libslab-8bdcdf1795930a41.rlib --extern-version slab=slab,0.4.1 --extern futures=/home/cratesfyi/cratesfyi/debug/deps/libfutures-7c92a300de6e1cf8.rlib --extern-version futures=futures,0.1.23` (exit code: 101)
        }
    ),
    State {
        next_error: None,
        backtrace: None
    }
)', src/bin/cratesfyi.rs:142:13
note: Run with `RUST_BACKTRACE=1` for a backtrace.
@kyrias

This comment has been minimized.

Show comment
Hide comment
@kyrias

kyrias Aug 18, 2018

proptest versions newer than 0.7.0 fail to be added to the database because the doc string used as the long description is longer than 51,200 bytes. (It's 53,518 bytes as of me writing this.)

kyrias commented Aug 18, 2018

proptest versions newer than 0.7.0 fail to be added to the database because the doc string used as the long description is longer than 51,200 bytes. (It's 53,518 bytes as of me writing this.)

@spease

This comment has been minimized.

Show comment
Hide comment
@spease

spease Aug 18, 2018

reqwest 0.8.8 is also failing to build, looks like the same error as 0.8.7
https://docs.rs/crate/reqwest/0.8.8/builds/113111

spease commented Aug 18, 2018

reqwest 0.8.8 is also failing to build, looks like the same error as 0.8.7
https://docs.rs/crate/reqwest/0.8.8/builds/113111

@thomaskrause

This comment has been minimized.

Show comment
Hide comment
@thomaskrause

thomaskrause Aug 20, 2018

graphannis 0.8.1 does not build because docs.rs uses the rust compiler 1.28.0-dev version instead of the released stable on. The compiler complains the global_allocator feature is not stabilized yet, which has been stabilized with 1.28 of rustc

https://docs.rs/crate/graphannis/0.8.1

https://docs.rs/crate/graphannis/0.8.1/builds/112947

thomaskrause commented Aug 20, 2018

graphannis 0.8.1 does not build because docs.rs uses the rust compiler 1.28.0-dev version instead of the released stable on. The compiler complains the global_allocator feature is not stabilized yet, which has been stabilized with 1.28 of rustc

https://docs.rs/crate/graphannis/0.8.1

https://docs.rs/crate/graphannis/0.8.1/builds/112947

@jendrikw

This comment has been minimized.

Show comment
Hide comment
@jendrikw

jendrikw Aug 21, 2018

From https://docs.rs/crate/cryptonight-rs/0.1.0/builds/113508:

running: "cc" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-g" "-m64" "-I" "src/vendor/crypto" "-I" "src/vendor/common" "-Wall" "-Wextra" "-maes" "-Ofast" "-fexceptions" "-o" "/home/cratesfyi/cratesfyi/debug/build/cryptonight-rs-2ca67d4bbcaa14da/out/src/vendor/chacha.o" "-c" "src/vendor/chacha.c"
cargo:warning=In file included from src/vendor/chacha.c:15:0:
cargo:warning=src/vendor/warnings.h:14:44: fatal error: boost/preprocessor/stringize.hpp: No such file or directory
cargo:warning= #include <boost/preprocessor/stringize.hpp>
cargo:warning=                                            ^
cargo:warning=compilation terminated.

jendrikw commented Aug 21, 2018

From https://docs.rs/crate/cryptonight-rs/0.1.0/builds/113508:

running: "cc" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-g" "-m64" "-I" "src/vendor/crypto" "-I" "src/vendor/common" "-Wall" "-Wextra" "-maes" "-Ofast" "-fexceptions" "-o" "/home/cratesfyi/cratesfyi/debug/build/cryptonight-rs-2ca67d4bbcaa14da/out/src/vendor/chacha.o" "-c" "src/vendor/chacha.c"
cargo:warning=In file included from src/vendor/chacha.c:15:0:
cargo:warning=src/vendor/warnings.h:14:44: fatal error: boost/preprocessor/stringize.hpp: No such file or directory
cargo:warning= #include <boost/preprocessor/stringize.hpp>
cargo:warning=                                            ^
cargo:warning=compilation terminated.
@paulocsanz

This comment has been minimized.

Show comment
Hide comment
@paulocsanz

paulocsanz Aug 22, 2018

https://docs.rs/crate/voluntary-servitude/1.0.2

Complains about using global_allocator, but it's stable.

paulocsanz commented Aug 22, 2018

https://docs.rs/crate/voluntary-servitude/1.0.2

Complains about using global_allocator, but it's stable.

@bodil

This comment has been minimized.

Show comment
Hide comment
@bodil

bodil Aug 30, 2018

im 12.0.0 also isn't building because of a feature that's just been stabilised in rustc 1.28: https://docs.rs/crate/im/12.0.0/builds/114882

bodil commented Aug 30, 2018

im 12.0.0 also isn't building because of a feature that's just been stabilised in rustc 1.28: https://docs.rs/crate/im/12.0.0/builds/114882

@azastrael

This comment has been minimized.

Show comment
Hide comment
@azastrael

azastrael Sep 1, 2018

Same issue as some people above (access to extern crates through prelude is experimental (see issue #44660)): https://docs.rs/crate/dolphin/0.1.0-alpha.1/builds/115238

azastrael commented Sep 1, 2018

Same issue as some people above (access to extern crates through prelude is experimental (see issue #44660)): https://docs.rs/crate/dolphin/0.1.0-alpha.1/builds/115238

@Kimundi

This comment has been minimized.

Show comment
Hide comment
@Kimundi

Kimundi Sep 3, 2018

I've got build errors due to using the new module system of the 2018 edition, see #231

Kimundi commented Sep 3, 2018

I've got build errors due to using the new module system of the 2018 edition, see #231

@timvisee

This comment has been minimized.

Show comment
Hide comment
@timvisee

timvisee Sep 4, 2018

Another extern_prelude error. Don't know where it's coming from.

I can't reproduce this locally, with any of the Rust versions I've tried.

    --- snip ---
error[E0658]: access to extern crates through prelude is experimental (see issue #44660)
  |
  = help: add #![feature(extern_prelude)] to the crate attributes to enable
    --- snip ---

https://docs.rs/crate/chbs/0.0.5/builds/115585


Edit: fixed it by removing these external links: gitlab.com/timvisee/chbs#6dda79e

timvisee commented Sep 4, 2018

Another extern_prelude error. Don't know where it's coming from.

I can't reproduce this locally, with any of the Rust versions I've tried.

    --- snip ---
error[E0658]: access to extern crates through prelude is experimental (see issue #44660)
  |
  = help: add #![feature(extern_prelude)] to the crate attributes to enable
    --- snip ---

https://docs.rs/crate/chbs/0.0.5/builds/115585


Edit: fixed it by removing these external links: gitlab.com/timvisee/chbs#6dda79e

@dtolnay

This comment has been minimized.

Show comment
Hide comment
@dtolnay

dtolnay Sep 8, 2018

For anyone seeing failures from features that have been stabilized -- usually those can be fixed like this.

# in Cargo.toml

[package.metadata.docs.rs]
rustdoc-args = ["--cfg", "docs_rs_workaround"]
// in src/lib.rs

#![cfg_attr(docs_rs_workaround, feature(/* whichever features */))]

dtolnay commented Sep 8, 2018

For anyone seeing failures from features that have been stabilized -- usually those can be fixed like this.

# in Cargo.toml

[package.metadata.docs.rs]
rustdoc-args = ["--cfg", "docs_rs_workaround"]
// in src/lib.rs

#![cfg_attr(docs_rs_workaround, feature(/* whichever features */))]

thomaskrause added a commit to corpus-tools/graphANNIS that referenced this issue Sep 11, 2018

spk added a commit to spk/reqwest that referenced this issue Sep 12, 2018

seanmonstar added a commit to seanmonstar/reqwest that referenced this issue Sep 12, 2018

@boomshroom

This comment has been minimized.

Show comment
Hide comment
@boomshroom

boomshroom Sep 13, 2018

https://docs.rs/crate/dumb-exec/0.0.4/builds/116783

Local builds of the docs work fine and the issue seems to entirely be at the fault of the futures library, but it was fixed in v0.3.0-alpha.5.

The same error occurs in the previous version of my crate and 0.0.4 was pushed specifically to fix it, which it failed to do.

boomshroom commented Sep 13, 2018

https://docs.rs/crate/dumb-exec/0.0.4/builds/116783

Local builds of the docs work fine and the issue seems to entirely be at the fault of the futures library, but it was fixed in v0.3.0-alpha.5.

The same error occurs in the previous version of my crate and 0.0.4 was pushed specifically to fix it, which it failed to do.

@RalfJung

This comment has been minimized.

Show comment
Hide comment
@RalfJung

RalfJung Sep 16, 2018

Latest version of vergen seems to be missing: https://docs.rs/vergen/ goes 404.

RalfJung commented Sep 16, 2018

Latest version of vergen seems to be missing: https://docs.rs/vergen/ goes 404.

@ryanisaacg

This comment has been minimized.

Show comment
Hide comment
@ryanisaacg

ryanisaacg Sep 16, 2018

Also getting errors due to features stabilized in 1.28

ryanisaacg commented Sep 16, 2018

Also getting errors due to features stabilized in 1.28

@Xoronic Xoronic referenced this issue Sep 16, 2018

Merged

Bump to version 0.3.0 #377

5 of 5 tasks complete
@gilrain

This comment has been minimized.

Show comment
Hide comment
@gilrain

gilrain commented Sep 17, 2018

https://docs.rs/crate/qmetaobject/

A custom build command failed.

@KizzyCode

This comment has been minimized.

Show comment
Hide comment
@KizzyCode

KizzyCode Sep 19, 2018

Is it possible to update to the current libsodium-version (1.0.16)? 1.0.11 is pretty old and a lot has changed since then... And my crate won't build with 1.0.11 😇

KizzyCode commented Sep 19, 2018

Is it possible to update to the current libsodium-version (1.0.16)? 1.0.11 is pretty old and a lot has changed since then... And my crate won't build with 1.0.11 😇

@gilrain

This comment has been minimized.

Show comment
Hide comment
@gilrain

gilrain Sep 24, 2018

https://docs.rs/crate/rusttype/0.7.2

Plus many crates that depend on rusttype.

gilrain commented Sep 24, 2018

https://docs.rs/crate/rusttype/0.7.2

Plus many crates that depend on rusttype.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment