It seems that the failure corresponds with the move to building docs for LLVM-11 by default. I tried running the docs build script with the last nightly that succeeded on docs.rs and it still fails (I don't have LLVM-11 on my local machine), so I don't think it has to do with a change to cargo or even to docs.rs.

I believe the default docs.rs docker container is https://github.com/rust-lang/crates-build-env , which by default runs apt-get install llvm (https://github.com/rust-lang/crates-build-env/blob/f93739b81540357d178fe00fcd1f033f13ed622b/packages.txt#L991) and the ubuntu 20.04 llvm package depends on llvm-10 or higher (from my local machine):

hudson: ~/code_repos/haybale (master) $ apt depends llvm
llvm
  Depends: llvm-runtime (= 1:10.0-50~exp1)
  Depends: llvm-10 (>= 10~)

so I am guessing that the llvm-sys issue you linked was not actually the right fix, and only works because the docs.rs build does have a system LLVM-10 present, even though the doc cfg is not actually being set correctly.

So a quick fix is probably to change back Cargo.toml

[package.metadata.docs.rs]
# Generate docs.rs documentation with the llvm-10 feature
features = ["llvm-10"]

until a working fix is committed to the llvm-sys crate.

Uh oh!

Docs do not build for 0.6.2 #13

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions