crassipes-0.2.0 build failure

[drdeaton]

Crate name: Crassipes
Build failure link: https://docs.rs/crate/crassipes/0.2.0/builds/355997

Additional details: Its failing to build because a dependency, crs-bind, which is based directly on the crate vex-rt (which does build) isn't able to build due to code that is present in the original vex-rt crate. The documentation builds and displays fine both on my local machine and in Gitlab CI. crs-bind also builds and documents fine on its own.

[jyn514]

@Dysproh can you replicate this failure locally?

[drdeaton]

No

[jyn514]

@Dysproh do you have a lockfile, maybe? I suspect there's a transitive dependency that changed.

[drdeaton]

the lockfile being cargo.lock? From which project?

[Nemo157]

The build log looks odd to me, why is it Compiling crs-bind rather than just Checking it, it's a non-build dependency.

EDIT: Ah, it has a build script, that's probably what's being compiled and fails.

[drdeaton]

it has to run bindgen to create ffi bindings. Is there a better way to do this?

It still doesnt fail to doc on gitlab or my machine. Might this be an issue with the version of alloc or core used on docs.rs? Not exactly sure how the compiler decides on which version of those crates to use

[Nemo157]

The error is valid on some platforms and unrelated to the build-script or generated code.

In ptr::copy(cstring, s.as_mut_ptr(), len); the cstring: *const c_char and s: String, the String always has a u8 buffer while c_char is either i8 or u8 depending on platform.

cargo build --target x86_64-pc-windows-msvc fails similarly for me in crs-bind, I'm not sure why the default linux build failed since afaik that should be a u8 using platform, or why the crs-bind doc build itself succeeded for -msvc 😕

[drdeaton]

Thats interesting. Anyway, these crates should only be built ever for armv7a-vex-eabi, which is just armv7a-none-eabi afaik. Is there any way to make docs.rs only target that platform?

[Nemo157]

See the targets section in https://docs.rs/about/metadata

[drdeaton]

I tried using targets = ["armv7a-vex-eabi.json"] but now its giving me this: https://docs.rs/crate/crs-bind/0.1.5/builds/357704

[Nemo157]

The .cargo/config is stripped before the build, so -Zbuild-std isn't used, there's also no currently no way to pass custom arguments to cargo during the build.

@jyn514 do you think it might be appropriate to add cargo-args to the metadata in order to support flags like -Zbuild-std=std,alloc like this build would need?

[jyn514]

Sure, cargo-args seems useful.

[jyn514]

cargo-args was added in #1374, so you can start using -Z build-std now if you like.