-
Bug
-
Resolution: Fixed
-
Normal
-
None
-
None
-
Install Rust 1.69.0 and then emerge media-video/rav1e
-
blocks upgrade to rust-1.69.0
During the testing of FL-11236 I discovered that media-video/rav1e-0.6.4 fails to compile with Rust 1.69.0 rustc but because of a custom build script failing due to missing file:
Running `/var/tmp/portage/media-video/rav1e-0.6.4/work/rav1e-0.6.4/target/release/build/rav1e-78c1dc5502d868c8/build-script-build` error: failed to run custom build command for `rav1e v0.6.4 (/var/tmp/portage/media-video/rav1e-0.6.4/work/rav1e-0.6.4)` Caused by: process didn't exit successfully: `/var/tmp/portage/media-video/rav1e-0.6.4/work/rav1e-0.6.4/target/release/build/rav1e-78c1dc5502d868c8/build-script-build` (exit status: 101) --- stderr thread 'main' panicked at 'Failed to acquire build-time information: Os { code: 2, kind: NotFound, message: "No such file or directory" }', build.rs:241:29 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace * ERROR: media-video/rav1e-0.6.4::media-kit failed (compile phase): * cargo build failed * * Call stack: * ebuild.sh, line 93: Called src_compile * environment, line 1334: Called die * The specific snippet of code: * cargo build ${args} || die "cargo build failed
The culprit is the newest autogenned version of rav1e 0.6.4 released 14 days ago: https://crates.io/crates/rav1e/versions
That upstream crate release's source code needs to be investigated to determine what is required for the custom cargo build script to run (will require and understanding of Rust). Specifically this is the line in the upstream build.rs that is throwing the error: thread 'main' panicked at 'Failed to acquire build-time information: Os { code: 2, kind: NotFound, message: "No such file or directory" }', build.rs:241:29
One mitigation would be to version lock the autogen to version 0.6.3 while we troubleshoot or alternatively determined the requirements of the build script and adjust the ebuild appropriately.
