Build error: thread 'main' panicked, No such file or directory about rav1e HOT 12 CLOSED

Ah. It's probably rustdoc then. I think built collects version information by executing rustdoc -V, so not having it installed could cause that error too.

from rav1e.

Failed to acquire build-time information: Os { code: 2, kind: NotFound, message: "No such file or directory" }

This means that the following line in the build script failed:

built::write_built_file().expect("Failed to acquire build-time information");

built writes some information to a file, so NotFound here indicates that this writing failed. Is it possible that the docker container is configured in a way that could prevent file writes? It might also be a bug in built.

from rav1e.

Do you know where it would be trying to write to? Is there a way to control that?

from rav1e.

Also, is this an error in writing an error message, in which case we still need to solve the "Failed to acquire build-time information" message?

from rav1e.

Also, is this an error in writing an error message, in which case we still need to solve the "Failed to acquire build-time information" message?

No, the error is "Failed to acquire build-time information". The message after that is the inner error message, which tells us why it failed to acquire build-time information: IO error OS { kind: NotFound, ... }.

Do you know where it would be trying to write to?

It tries to write to a temporary directory created for the build. It's the OUT_DIR (more info here and here, ctrl-f for OUT_DIR). The name follows the pattern <project root>/target/release/build/rav1e-<some hex>/out, but changes between compilations.

Is there a way to control that?

The out dir is inside the target folder used during compilation. I don't think you can set the OUT_DIR directly, but moving the target folder (e.g. by setting CARGO_TARGET_DIR) should move everything including OUT_DIR.

from rav1e.

Okay, apparently our docker images have no read-only partitions, so that shouldn't be an issue.

I'm still not sure what build-time information it failed to acquire though. Is it possible there is a missing dependency? If I'm able to reproduce locally with docker, what steps can I take to debug this? The error message doesn't even tell me what file it's trying to read/write...

from rav1e.

Possibly related to lukaslueg/built#14, I wish the error message was a little more helpful...

from rav1e.

Found a fix. If I build rust with developer tools (clippy, rustdoc, rustfmt, rust-analyzer) then the build succeeds. Does that sound right?

from rav1e.

Thanks, that clears that up! I'm new to the rust build system so I'm not sure if/where the dependency on rustdoc is listed. I'll chalk this one up to rust needing better error messages. Thanks again for the help!

from rav1e.

Does this need a bump in built right now?

from rav1e.

I'm afraid so

from rav1e.

@lu-zero, bumped to 0.7.2

from rav1e.